sr
stringlengths 9
9
| prompt_software
stringlengths 815
57.9k
| prompt_product
stringlengths 807
36.2k
| Customer_Symptom__c
stringlengths 253
14.2k
| Description
stringlengths 33
14k
| Resolution_Summary__c
stringlengths 7
7.89k
| Problem_Description__c
stringlengths 3
5.37k
| Product_Name__c
stringlengths 8
22
| SW_Version__c
stringlengths 3
42
| Case_Close_SW_Version__c
stringlengths 3
18
| CXSAT_Score__c
stringlengths 3
5
| Priority
stringclasses 3
values | Health_Score__c
stringclasses 2
values | Underlying_Cause__c
stringclasses 9
values | Product_Family__c
stringclasses 11
values | Technology_Text__c
stringclasses 10
values | Sub_Technology_Text__c
stringlengths 3
89
| SW_Product__c
stringlengths 3
18
| Problem_Code_Description__c
stringclasses 7
values | Sub_Technology_Description__c
stringlengths 3
89
| Technology_Description__c
stringclasses 10
values | HW_Product__c
stringlengths 3
18
| Automation_Level__c
stringclasses 9
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
695109716 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
17.3.23 - - - -
+ as per discussion with rep, it is agreed upon for soft closure
10.3.23 - - - -
+ 2nd follow up
7.3.23 - - - -
+ 1st follow up
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable. We should monitor them.
#show switch stack-ports summary – will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that a you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
10.3.23 - - - -
+ 2nd follow up
7.3.23 - - - -
+ 1st follow up
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable. We should monitor them.
#show switch stack-ports summary – will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that a you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
Hope you are doing good.
After TAC analysis, below is the summary report:
//
As I understand it, you are observing stack issues.
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable.
We should monitor them.
#show switch stack-ports summary - will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcdets.cisco.com%2Fapps%2Fdumpcr%3F%26content%3Dsummary%26format%3Dhtml%26identifier%3DCSCvw90216&data=05%7C01%7Cmohamedissam.niyamathullah%40ncs.com.sg%7Cf6f55778cc244ffe4fc508db160d5841%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638128018828469927%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=05NTrndwFHh5jVSRghLnTcdCJ1hTAFhrdFN%2Fx4zDTn8%3D&reserved=0>
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbst.cloudapps.cisco.com%2Fbugsearch%2Fbug%2FCSCwa14578&data=05%7C01%7Cmohamedissam.niyamathullah%40ncs.com.sg%7Cf6f55778cc244ffe4fc508db160d5841%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638128018828469927%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zvPY6QbVsIwOwWwnuB9eVLPjVgNhr%2FiZnubXuyh93Mk%3D&reserved=0> - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
Regarding port 3/0/11, do observe it flapping,
Feb 22 2023 17:34:55.656 SGT: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/11, changed state to up
Feb 22 2023 17:34:56.657 SGT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/11, changed state to up
Feb 22 2023 17:35:40.786 SGT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/11, changed state to down
Feb 22 2023 17:35:41.787 SGT: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/11, changed state to down
Please investigate the cable and RJ45 connector on both sides.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Fsupport%2Fdocs%2Fswitches%2Fcatalyst-9300-series-switches%2F214814-recommended-releases-for-catalyst-9200-9.html&data=05%7C01%7Cmohamedissam.niyamathullah%40ncs.com.sg%7Cf6f55778cc244ffe4fc508db160d5841%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638128018828469927%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1wfS1ak1q%2Bfy51GaG%2FUVjfsvOZ0h3B6xccBoWb3PH60%3D&reserved=0>
//
Please let us know if you need Webex to schedule with TAC now.
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable. We should monitor them.
#show switch stack-ports summary – will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that a you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Stack port disconnects and reconnects again on its own. Need assistance to find out cause of the issue
Stack port disconnects and reconnects again on its own. Need assistance to find out cause of the issue
timestamp : 2023-03-20T12:21:45.000+0000 || updatedby : gikeshav || type : RESOLUTION SUMMARY || visibility : External || details : closed after 3 strikes | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
17.3.23 - - - -
+ as per discussion with rep, it is agreed upon for soft closure
10.3.23 - - - -
+ 2nd follow up
7.3.23 - - - -
+ 1st follow up
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable. We should monitor them.
#show switch stack-ports summary – will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that a you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
10.3.23 - - - -
+ 2nd follow up
7.3.23 - - - -
+ 1st follow up
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable. We should monitor them.
#show switch stack-ports summary – will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that a you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
Hope you are doing good.
After TAC analysis, below is the summary report:
//
As I understand it, you are observing stack issues.
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable.
We should monitor them.
#show switch stack-ports summary - will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcdets.cisco.com%2Fapps%2Fdumpcr%3F%26content%3Dsummary%26format%3Dhtml%26identifier%3DCSCvw90216&data=05%7C01%7Cmohamedissam.niyamathullah%40ncs.com.sg%7Cf6f55778cc244ffe4fc508db160d5841%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638128018828469927%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=05NTrndwFHh5jVSRghLnTcdCJ1hTAFhrdFN%2Fx4zDTn8%3D&reserved=0>
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbst.cloudapps.cisco.com%2Fbugsearch%2Fbug%2FCSCwa14578&data=05%7C01%7Cmohamedissam.niyamathullah%40ncs.com.sg%7Cf6f55778cc244ffe4fc508db160d5841%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638128018828469927%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zvPY6QbVsIwOwWwnuB9eVLPjVgNhr%2FiZnubXuyh93Mk%3D&reserved=0> - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
Regarding port 3/0/11, do observe it flapping,
Feb 22 2023 17:34:55.656 SGT: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/11, changed state to up
Feb 22 2023 17:34:56.657 SGT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/11, changed state to up
Feb 22 2023 17:35:40.786 SGT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/11, changed state to down
Feb 22 2023 17:35:41.787 SGT: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/11, changed state to down
Please investigate the cable and RJ45 connector on both sides.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Fsupport%2Fdocs%2Fswitches%2Fcatalyst-9300-series-switches%2F214814-recommended-releases-for-catalyst-9200-9.html&data=05%7C01%7Cmohamedissam.niyamathullah%40ncs.com.sg%7Cf6f55778cc244ffe4fc508db160d5841%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638128018828469927%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1wfS1ak1q%2Bfy51GaG%2FUVjfsvOZ0h3B6xccBoWb3PH60%3D&reserved=0>
//
Please let us know if you need Webex to schedule with TAC now.
This is regarding Case Number 695109716, which you opened with Cisco Systems.
My name is Georgi Borisov and I'm the Customer Support Engineer who owns your case.
I am sending this e-mail as the initial point of contact to let you know that I have accepted your case, and also to give you information on how to contact me.
As I understand it, you are observing stack issues.
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable.
We should monitor them.
#show switch stack-ports summary - will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216<http://cdets.cisco.com/apps/dumpcr?&content=summary&format=html&identifier=CSCvw90216>
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
Regarding port 3/0/11, do observe it flapping,
Feb 22 2023 17:34:55.656 SGT: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/11, changed state to up
Feb 22 2023 17:34:56.657 SGT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/11, changed state to up
Feb 22 2023 17:35:40.786 SGT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/11, changed state to down
Feb 22 2023 17:35:41.787 SGT: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/11, changed state to down
Please investigate the cable and RJ45 connector on both sides.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
Apologize for not reaching out sooner, I was in a meeting that took longer than expected.
My shift is from Mon - Fri - 11am-7:00pm CST, if you need assistance in your time zone please contact our CIN agents to reuque the case to an available engineer in your timezone.
Please do not hesitate to contact me for any questions or concerns.
Based on the provided documentation,
------------------ show switch stack-ports summary ------------------
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 100cm Yes Yes Yes 2 No
1/2 OK 6 300cm Yes Yes Yes 1 No
2/1 OK 3 100cm Yes Yes Yes 1 No
2/2 OK 1 100cm Yes Yes Yes 1 No
3/1 OK 4 100cm Yes Yes Yes 1 No
3/2 OK 2 100cm Yes Yes Yes 2 No
4/1 OK 5 100cm Yes Yes Yes 1 No
4/2 OK 3 100cm Yes Yes Yes 3 No
5/1 OK 6 100cm Yes Yes Yes 1 No
5/2 OK 4 100cm Yes Yes Yes 2 No
6/1 OK 1 300cm Yes Yes Yes 2 No
6/2 OK 5 100cm Yes Yes Yes 1 No
Stack ports of all 6 switches in the tsack seem stable. We should monitor them.
#show switch stack-ports summary – will display if there were any changes on that specific link.
The following defect was found On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally CSCvw90216
The switch is also affected by this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa14578 - realted to the memory leak and the reload of switch 2.
Unfortunately, all the logs are from Feb 22, however noted that a you have a logging server, if possible to provide me the logs for that date and the specific hour, for further investigation.
As this stack is affected by 2 defects, my recommendation would be to upgrade to golden fixed release https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended-releases-for-catalyst-9200-9.html
I did the analysis of the provided show tech, it seems that this is related to a bug.
Can you check if related?
On Cat9200(stack),trap ciscoStackWiseMIB.0.0.6 (cswStackMemberRemoved) unable created normally
CSCvw90216
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Stack port disconnects and reconnects again on its own. Need assistance to find out cause of the issue
Stack port disconnects and reconnects again on its own. Need assistance to find out cause of the issue
timestamp : 2023-03-20T12:21:45.000+0000 || updatedby : gikeshav || type : RESOLUTION SUMMARY || visibility : External || details : closed after 3 strikes | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Stack port disconnects and reconnects again on its own. Need assistance to find out cause of the issue | Stack port disconnects and reconnects again on its own. Need assistance to find out cause of the issue | timestamp : 2023-03-20T12:21:45.000+0000 || updatedby : gikeshav || type : RESOLUTION SUMMARY || visibility : External || details : closed after 3 strikes | nan | C9300-48U | cat9k_iosxe.16.12.04.SPA.bin | nan | nan | 3 | nan | Software Bug | C9300 | LAN Switching | Cat9300 | nan | nan | nan | nan | nan | nan |
693988553 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Configuration Assistance
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Configurations are different between running-config and startup-config after reboot the switch.
Configurations are different between running-config and startup-config after reboot the switch.
Advised to verify show run all output for default configuration. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Configuration Assistance
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Configurations are different between running-config and startup-config after reboot the switch.
Configurations are different between running-config and startup-config after reboot the switch.
Advised to verify show run all output for default configuration. | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Configuration Assistance
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Configurations are different between running-config and startup-config after reboot the switch. | Configurations are different between running-config and startup-config after reboot the switch. | Advised to verify show run all output for default configuration. | Configurations are different between running-config and startup-config after reboot the c9300 switch. | C9300-48U-A | nan | nan | 82.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | C9300 | LAN Switching | Cat9300 | 01tA0000000huG8IAI | Configuration Assistance | Cat9300 | LAN Switching | 01t15000005W1eHAAS | nan |
693929980 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: THIRD_PARTY_PRODUCT_SW/ 16.03.01/ 16.07.02/ 122.33 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Software Version: -- => 17.3.4a
Technology: Router and IOS-XE Architecture
Subtechnology: IOS-XE Memory Leaks
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: OSPF and BGP reset on SDA Borders
OSPF and BGP reset on SDA Borders
timestamp : 2023-01-09T13:29:50.000+0000 || updatedby : akbashir || type : RESOLUTION SUMMARY || visibility : External || details : No Response from
Closing as per 3 strike | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: THIRD_PARTY_PRODUCT_HW/ VS-C6509E-S720-10G/ CSR-ASR1K2-CHT1-1/ ASR1009-X Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Router and IOS-XE Architecture
Subtechnology: IOS-XE Memory Leaks
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: OSPF and BGP reset on SDA Borders
OSPF and BGP reset on SDA Borders
timestamp : 2023-01-09T13:29:50.000+0000 || updatedby : akbashir || type : RESOLUTION SUMMARY || visibility : External || details : No Response from
Closing as per 3 strike | Technology: Router and IOS-XE Architecture
Subtechnology: IOS-XE Memory Leaks
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: OSPF and BGP reset on SDA Borders | OSPF and BGP reset on SDA Borders | timestamp : 2023-01-09T13:29:50.000+0000 || updatedby : akbashir || type : RESOLUTION SUMMARY || visibility : External || details : No Response from
Closing as per 3 strike | nan | ASR1009-X | asr1001x-universalk9.16.07.02.SPA.bin | nan | nan | 3 | nan | Configuration Assistance (process not intuitive, too complex, inconsistent...) | ASR1000 | Routing Protocols (Includes NAT and HSRP) | BGP | nan | nan | nan | nan | nan | nan |
694642521 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
8.10.185.3 special image shared with customer with bug fixes for AP crash issue
Thank you for your email.
We received an update form our escalation team and we have opened two new bugs internally to further investigate and below is the status:
1
AP BIZ2-04-AP24
Kernel Panic/ PC is at __udelay+0x30/0x48
1.
0xffffffc000338900 __udelay + 0x30
2.
0xffffffbffc44d52c osl_delay + 0x2c
New bug - CSCwe91301 for further investigation
2
AP TB-02-AP04
Kernel Panic/ PC is at get_partial_node.isra.24+0x140/0x288
1.
0xffffffc000088d30 dump_backtrace + 0x150
2.
0xffffffc000088e94 show_stack + 0x20
3.
0xffffffc000668b30 dump_stack + 0xb0
4.
0xffffffc000156058 print_bad_pte + 0x1d0
5.
0xffffffc0001579cc unmap_single_vma + 0x5d0
6.
0xffffffc0001582d8 unmap_vmas + 0x68
7.
0xffffffc00015f9b4 exit_mmap + 0xf8
8.
0xffffffc00009c354 mmput + 0x118
9.
0xffffffc0000a0afc do_exit + 0x8e0
10.
0xffffffc0000a120c do_group_exit + 0xb0
11.
0xffffffc0000a1290 __wake_up_parent + 0x28
New bug - CSCwe91264 for further investigation
3
AP ERC-02-AP49
CALLBACK FULL Reset Radio
Unable to Decode
Collect all .txt from /storages/cores/
AP ERC-02-AP51
CALLBACK FULL Reset Radio
Unable to Decode
Collect all .txt from /storages/cores/
AP ERC-B1-AP03
CALLBACK FULL Reset Radio
Unable to Decode
Collect all .txt from /storages/cores/
The below 3 AP crashes belong to AP model 1810W, which is EOL.
I will further check with the team internally to see how we can proceed on this:
4
AP i4-05-AP55
Kernel Panic/ PC is at skb_recycler_alloc+0x84/0x2e4
1.
0xc039a954 skb_recycler_alloc + 0x84
2.
0xc037bbe0 dev_alloc_skb_poolid + 0x24
3.
0xbfbe9678 __adf_nbuf_alloc + 0x28
4.
0xbfccff54 wbuf_alloc + 0x5c
5.
0xbfd08e2c wmi_buf_alloc + 0x20
6.
0xbfcf8fb4 wmi_unified_set_qboost_param + 0x30
7.
0xbfcf904c qboost_config + 0x18
8.
0xbfcf92d8 ol_ath_net80211_newassoc + 0x288
9.
0xbfc6a65c ieee80211_mlme_recv_assoc_request + 0x418
10.
0xbfc1ed5c ieee80211_ucfg_splitmac_add_client + 0xc3c
11.
0xbfcb8d04 acfg_add_client + 0x280
12.
0xbfcb92dc acfg_handle_vap_ioctl + 0x10c
13.
0xbfca73b4 ieee80211_ioctl + 0x2720
14.
0xc038962c dev_ifsioc + 0x300
15.
0xc0389db8 dev_ioctl + 0x764
16.
0xc0372e80 sock_ioctl + 0x260
17.
0xc0104730 do_vfs_ioctl + 0x5a0
18.
0xc01047b8 sys_ioctl + 0x3c
19.
0xc000e680 ret_fast_syscall + 0x0
AP i4-05-AP55
Kernel Panic/ PC is at skb_recycler_alloc+0x84/0x2e4
1.
0xc039a954 skb_recycler_alloc + 0x84
2.
0xc037bbe0 dev_alloc_skb_poolid + 0x24
3.
0xbfbe9678 __adf_nbuf_alloc + 0x28
4.
0xbfccff54 wbuf_alloc + 0x5c
5.
0xbfd08e2c wmi_buf_alloc + 0x20
6.
0xbfcf8fb4 wmi_unified_set_qboost_param + 0x30
7.
0xbfcf904c qboost_config + 0x18
8.
0xbfcf92d8 ol_ath_net80211_newassoc + 0x288
9.
0xbfc6a65c ieee80211_mlme_recv_assoc_request + 0x418
10.
0xbfc1ed5c ieee80211_ucfg_splitmac_add_client + 0xc3c
11.
0xbfcb8d04 acfg_add_client + 0x280
12.
0xbfcb92dc acfg_handle_vap_ioctl + 0x10c
13.
0xbfca73b4 ieee80211_ioctl + 0x2720
14.
0xc038962c dev_ifsioc + 0x300
15.
0xc0389db8 dev_ioctl + 0x764
16.
0xc0372e80 sock_ioctl + 0x260
17.
0xc0104730 do_vfs_ioctl + 0x5a0
18.
0xc01047b8 sys_ioctl + 0x3c
19.
0xc000e680 ret_fast_syscall + 0x0
AP CELC-03-AP11
Kernel Panic/ PC is at skb_recycler_alloc+0x84/0x2e4
1.
0xc039a954 skb_recycler_alloc + 0x84
2.
0xc037bbe0 dev_alloc_skb_poolid + 0x24
3.
0xbfbe9678 __adf_nbuf_alloc + 0x28
4.
0xbfd34cac htt_h2t_dbg_stats_get + 0x6c
5.
0xbfd2c218 ol_txrx_fw_stats_get + 0x110
6.
0xbfcd94c0 ol_ath_fw_stats_timeout + 0xb0
7.
0xc006b664 run_timer_softirq + 0x168
8.
0xc0065ba0 __do_softirq + 0xf4
9.
0xc0066070 irq_exit + 0x54
10.
0xc000ef5c handle_IRQ + 0x88
11.
0xc00085ec gic_handle_irq + 0x94
12.
0xc000e340 __irq_svc + 0x40
The below two AP crashes are still being investigated upon and will have an update shortly.
5
AP IT-01-AP13
Kernel Panic/ PC is at misc_open+0x48/0x198
0xffffffc0003d01c8 misc_open + 0x48
0xffffffc0003d01b0 misc_open + 0x30
AP E1-05-AP08
Kernel Panic/ PC is at misc_open+0x48/0x198
1.
0xffffffc0003d01c8 misc_open + 0x48
2.
0xffffffc0003d01b0 misc_open + 0x30
Could you please help me collect all .txt files from /storages/cores/ from the 3 Aps (AP ERC-02-AP49, AP ERC-02-AP51 & AP ERC-B1-AP03) so I can share it with our team for further analysis.
Please let me know your availability so I can collect the required logs.
Please feel free to let me know if you have any further queries.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Recommended to upgrade the SDA WLC to 8.10.181 as well.
jan 27th : crash file of 9120 has
from crash file
PC is at rb_
next+0xc/0x6c
LR is at pick_next_task_fair+0x4
8/0x160.
CSCwa34136 Cisco 3802 FQI/NMI reset at rb_next+0xc
the fix is to upgrade to 8.10.171
During the upgrade customer was facing FN - 72524.
Customer will perform the upgrade from 6 PM SGT to next day 7 AM SGT. They plan to do reboots at 12 midnight of 24th feb and 25th feb.
Commsbridge - CRQ000002047334 - WLC (.13) Upgrade to 8.10.183
Hosted by Samuel Foo
https://techdynamicpteltd.my.webex.com/techdynamicpteltd.my/j.php?MTID=mb7f4582654ff010cfd61f959ef1cf2ed
Saturday, February 18, 2023 11:00 PM | 8 hours | (UTC+08:00) Kuala Lumpur, Singapore
Meeting number: 2550 952 0840
Password: iuMJ34W3bJR (48653493 from phones and video systems)
Join by video system
Dial [email protected]
You can also dial 173.243.2.68 and enter your meeting number.
Join by phone
+1-650-479-3208 United States Toll
Access code: 255 095 20840
Only CSCvz08781 is fixed on 8.5.171, though Wism2 is not mentioned under the list of products on this bug.
Please feel free to let me know if you have any further queries.
Thanks Sharath for an update.
Can you confirm if below bugs are fixed in 8.5.171.0
MPSH issue bug https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvz08781<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fbst.cloudapps.cisco.com%2fbugsearch%2fbug%2fCSCvz08781&umid=75439d08-7787-4ffb-a34a-787b5c768898&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-04efa1002c98d5b739f3adb9e569602d457457fe>
Logs :-
Nov 22 11:08:12 kernel: [*11/22/2022 11:08:12.9134] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=67
Nov 22 11:08:12 kernel: [*11/22/2022 11:08:12.9135]
Nov 22 11:08:15 kernel: [*11/22/2022 11:08:15.8115] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=8, NumofPendingMsgs=70
Nov 22 11:08:15 kernel: [*11/22/2022 11:08:15.8115]
Nov 22 11:08:18 kernel: [*11/22/2022 11:08:18.7069] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=11, NumofPendingMsgs=73
Nov 22 11:08:18 kernel: [*11/22/2022 11:08:18.7069]
Nov 22 11:08:21 kernel: [*11/22/2022 11:08:21.6039] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=11, NumofPendingMsgs=73
Nov 22 11:08:21 kernel: [*11/22/2022 11:08:21.6039]
Nov 22 11:08:24 kernel: [*11/22/2022 11:08:24.4998] Max retransmission count exceeded, going back to DISCOVER mode.
CLIB issue bug https://bst.cisco.com/bugsearch/bug/CSCvy37953
Logs :-
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00ac] ClientHello
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] dtls_connectionDB_add_connection: Added Connection 0x54aaea00 Server [172.18.240.26]:5246 Client [10.253.159.139]:5256
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] create_dtls_connection: Creating DTLS Ctrl Connection 0x54aaea00
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0012] DTLS connection created sucessfully local_ip: 10.253.159.139 local_port: 5256 peer_ip: 172.18.240.26 peer_port: 5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0022] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.159.139]:5256(0)--[172.18.240.26]:5246(0) [10.253.159.139]:5256--[172.18.240.26]:5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0022] dtls_connection_find_using_link_info: Searching connection [10.253.159.139]:5256--[172.18.240.26]:5246, result 0x54aaea00
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0023] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0023] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 002f] HelloVerifyRequest
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0024] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0024] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00cc] ClientHello
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0025] dtls_process_packet: SSL get error rc 5
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0031] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.159.139]:5256(0)--[172.18.240.26]:5246(0) [10.253.159.139]:5256--[172.18.240.26]:5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0032] dtls_connection_find_using_link_info: Searching connection [10.253.159.139]:5256--[172.18.240.26]:5246, result 0x54aaea00
I had a check internally and found that Wism2 is EOL and end of support and hence 8.10.183 is not available.
The last version released for Wism2 was 8.5.171.
Please feel free to let me know if you have any further queries.
Can we get 8.10.183.0 for wism2.
Its urgent.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Recommended to upgrade the SDA WLC to 8.10.181 as well.
jan 27th : crash file of 9120 has
from crash file
PC is at rb_
next+0xc/0x6c
LR is at pick_next_task_fair+0x4
8/0x160.
CSCwa34136 Cisco 3802 FQI/NMI reset at rb_next+0xc
the fix is to upgrade to 8.10.171
During the upgrade customer was facing FN - 72524.
While uploading the image to the WLC.
We are observing that AP’s are taking too much of time in predownloading.
We are upgrading from 8.10.162.0 to 8.10.183.0.
(TLDC-WLC1) >show ap image all
Total number of APs..............................
1340
Number of APs
Initiated.......................................
2
Downloading.....................................
0
Predownloading..................................
1000
Completed predownloading........................
0
Not Supported...................................
0
Failed to Predownload...........................
0
Predownload Predownload Flexconnect
AP Name Primary Image Backup Image Status Version Next Retry Time Retry Count Predownload
------------------ -------------- -------------- --------------- -------------- ---------------- ------------ --------------
RC1_DH-02-AP07 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
RC1_DH-02-AP08 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
RC1-02-AP01 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
SDE1-04-AP03 8.10.162.0 8.3.150.6 Waiting 8.10.183.0 01:12:02 2
RC1-02-AP10 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
RC1-02-AP09 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
RC1-02-AP06 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
SDE3-03-AP16 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
RC2-GF-AP14 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
SDE3-02-AP06 8.10.162.0 8.10.130.0 Predownloading 8.10.183.0 NA 0
Please join zoom meeting.
Join Zoom Meeting
https://nus-sg.zoom.us/j/84695360268?pwd=Sng1Tk16R1dNZXVoaGhtSTFjUVZuQT09
Meeting ID: 846 9536 0268
Passcode: 239230
To join using H.323: https://wiki.nus.edu.sg/display/cit/Making+H.323+or+SIP+Calls
Please note that this website may contain links to other websites not maintained by NUS.
Such third party websites are subject to their own data protection and privacy practices and you are encouraged to examine the privacy policies of those websites.
The session may be recorded and the recordings will be distributed/published by the organiser to the participants.
If you have any concerns on the recordings, please contact the organiser.
Only email address, first/last name will automatically be recorded but other information such as company name, telephone and/or profile picture can also be recorded, if required, during the session recording.
My name is Juan Felipe, and I have ownership of Service Request 694642521.
I am sending this e-mail as an initial point of contact.
Problem Description:
Initial issue:
When we had more number of clients connected to the APs(around 70-80 clients), few of them stopped catering to clients and after a reboot clients connected fine.
The crash was generated after rebooting the Aps to restore the network.
You had a fabric setup with over 4000+ Aps.
jan 30th : pinged internal to DE to find out if bug is fixed for 8.10.183
Here is a brief summary of our call:
1.
There is a query from Biswajit.
Can we upgrade the WLC 8.10.181.4 to 8.10.183.0, since 8.10.181.0 is deferred.
I believe the answer is Yes but wanted to double confirm from Cisco TAC.
I just got a confirmation from the DE team that 8.10.183.0 will be supported with DNAC 2.2.2.9 .
Compatibility Matrix should be updated by this week.
Please feel free to let us know if you have any further queries.
You are right.
I have requested for compatibility between DNAC 2.2.2.9 and wlc 8.10.183.
I will keep you updated as soon as I hear from the DE team.
Please correct , we need compatibility conformation on DNAC 2.2.2.9 with 8.10.183.0 from Cisco.
I just had a call with TAC engineer.
TAC confirmed on 2802i CCLIB certificate issue under https://bst.cisco.com/bugsearch/bug/CSCvy37953 buggy behaviour.
This issue is fixed under 8.10.171.0 and expected to have fix on 8.10.183.0.
TAC will share the findings shortly with logs.
Yes, Testing was done on 26th JAN for POVWLC1 and 4.
Below is the snippet.
Conclusion :- No compatibility issues found between 2.2.2.9 and 8.10.183.0.
+Baby John
Hi Satyam, you have tested this OS 8.10.183 in POV environment with DNAC 2.2.2.9 , did you find any issues ? Pls share.
I apologize for the confusion.
Yes, are you right 8.10.183 is not in the list of supported release for DNAC 2.2.2.9.
Since, 8.10.181 has been deferred and is not available for download, please allow me a day time so I can check with DNAC DE team if they can include 8.10.183 in the compatibility matrix and also get a confirmation if they have done some testing so you can proceed with the upgrade.
Please feel free to let us know if you have any further queries.
I also just noticed the same.
Below screenshot shared is from 2.3.3.6 ( by TAC ) but I concur checking the same for 2.2.2.9 compatibility with 8.10.183.0.
I have reached out Cisco TM on the same and expected to get response in 30 mins from TAC.
Hi Satyam / Sharath
Do note that the current production DNAC is on ver 2.2.2.9.
however, 8.10.183 is not in the compatibility list with DNAC 2.2.2.9 officially.
Cisco team, please advise if we still can proceed with the WLC firmware upgrade.
[Icon Description automatically generated]
I have a discussion with the DE, and yes the fix for the bug Is integrated to release 8.10.183 as well.
AP crash issue
Initial issue:
When we had more number of clients connected to the APs(around 70-80 clients), few of them stopped catering to clients and after a reboot clients connected fine. The crash was generated after rebooting the Aps to restore the network.
You had a fabric setup with over 4000+ Aps.
jan 30th : pinged internal to DE to find out if bug is fixed for 8.10.183
Here is a brief summary of our call:
1. You had 4-5 Ap crashes which were 2802i AP modes and we collected the crash logs and tech support logs from the affected APs.
2. Since you wanted SDA team to look into the fabric part to figure out if the are any issues with the routing part, I involved my SDA team on call.
3. As per our SDA teams analysis, the fabric underlaying path is not a traditional design and my colleague will give you more details about his findings and next plan of action.
Can we say if the bug is fixed in earlier release i.e.
8.10.168.0 and 8.10.171.0 which both are deferred now, will be fixed in 8.10.183.0.
Urgently.
The code 8.10.183 is currently not listed in the integrated releases for this bug.
Thanks for your support !!
Can you also confirm that this fix is integrated in 8.10.183.0.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Recommended to upgrade the SDA WLC to 8.10.181 as well.
jan 27th : crash file of 9120 has
from crash file
PC is at rb_
next+0xc/0x6c
LR is at pick_next_task_fair+0x4
8/0x160.
CSCwa34136 Cisco 3802 FQI/NMI reset at rb_next+0xc
the fix is to upgrade to 8.10.171
the fix is to upgrade to 8.10.171 for the crash info seen for 9120 AP
Thank you for your email.
In this case I would recommend upgrading to 8.10.183 version which is the recommended version.
Here is the compatibility matrix for your reference:
Since the defect CSCvx96224 is fixed on 8.10.181.x, it is by default committed on 8.10.183.
Here is the link to 8.10.183 version:
https://software.cisco.com/download/home/286284728/type/280926587/release/8.10.183.0
Let me know if you are unable to download it, so I can publish it for you.
Please feel free to let me know if you have any further queries.
I can see that 8.10.181.0 is marked deferred now due to ongoing different bug CSCwd80290 <https://bst.cisco.com/bugsearch/bug/CSCwd80290> .
It is not available to download.
https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.181.0?releaseIndicator=DEFERRED
Could you confirm that what can be done next ?
Hey Sharath,
Thanks for your confirmation and I hope everything is fine at your place.
In this case we can proceed with adoption of 8.10.181.0 instead escalation image 8.10.181.4.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue
For CAPWAP traffic from WLC to AP takes path from Edge which might be the reason for CAPWAP keepalives to get dropped
Fro traffic from WLC to AP, we checked packet capture on AP connected port and we see source as a FE.
Frame 20642: 173 bytes on wire (1384 bits), 173 bytes captured (1384 bits) on interface \Device\NPF_{F90C5072-EDB0-4466-991E-486944B5A317}, id 0
Ethernet II, Src: Cisco_9a:32:c0 (70:79:b3:9a:32:c0), Dst: Cisco_36:70:e7 (f8:7a:41:36:70:e7)
Internet Protocol Version 4, Src: 172.18.1.2, Dst: 172.18.1.61
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 159
Identification: 0x81b3 (33203)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 250
Protocol: UDP (17)
Header Checksum: 0xa41e [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.1.2
Destination Address: 172.18.1.61
User Datagram Protocol, Src Port: 65419, Dst Port: 4789
Virtual eXtensible Local Area Network
Ethernet II, Src: Cisco_9f:00:00 (00:00:0c:9f:00:00), Dst: ba:25:cd:f4:ad:38 (ba:25:cd:f4:ad:38)
Internet Protocol Version 4, Src: 172.18.240.13, Dst: 10.253.144.11
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 109
Identification: 0x50bf (20671)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 251
Protocol: UDP (17)
Header Checksum: 0xf77f [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.240.13
Destination Address: 10.253.144.11
User Datagram Protocol, Src Port: 5246, Dst Port: 5252
Control And Provisioning of Wireless Access Points - Control
Preamble
Datagram Transport Layer Security
Dec 1st 2022:
radio reloaded: sensord cmd(0x03) failed slot 1
[cmd timeout] wifi1: 0x9184=unknown intCode:0x1184 last 0x801c=SetRadio
The crash signature matches the bug mentioned below which has a fix in 10.8.171.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224
Informed customer to upgrade WLC to 8.10.181 which is DNAC 2.3 compatible
Informed customer that bug on CSCvx96224 is fixed on 8.10.181.0
I apologize, I was on an emergency leave.
I had a check internally and I can confirm that the bug CSCvx96224<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224> is fixed on 8.10.181.0.
Please feel free to let me know if you have any further queries and I will be glad to assist.
Can you confirm if the 8.10.181.0 has the fix of affected bug “bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224” because I cannot see this bug under resolved caveats in the release notes https://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn810mr8.html
We need conformation form cisco that bug fix is in 8.10.181.0 before adoption.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue
For CAPWAP traffic from WLC to AP takes path from Edge which might be the reason for CAPWAP keepalives to get dropped
Fro traffic from WLC to AP, we checked packet capture on AP connected port and we see source as a FE.
Frame 20642: 173 bytes on wire (1384 bits), 173 bytes captured (1384 bits) on interface \Device\NPF_{F90C5072-EDB0-4466-991E-486944B5A317}, id 0
Ethernet II, Src: Cisco_9a:32:c0 (70:79:b3:9a:32:c0), Dst: Cisco_36:70:e7 (f8:7a:41:36:70:e7)
Internet Protocol Version 4, Src: 172.18.1.2, Dst: 172.18.1.61
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 159
Identification: 0x81b3 (33203)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 250
Protocol: UDP (17)
Header Checksum: 0xa41e [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.1.2
Destination Address: 172.18.1.61
User Datagram Protocol, Src Port: 65419, Dst Port: 4789
Virtual eXtensible Local Area Network
Ethernet II, Src: Cisco_9f:00:00 (00:00:0c:9f:00:00), Dst: ba:25:cd:f4:ad:38 (ba:25:cd:f4:ad:38)
Internet Protocol Version 4, Src: 172.18.240.13, Dst: 10.253.144.11
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 109
Identification: 0x50bf (20671)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 251
Protocol: UDP (17)
Header Checksum: 0xf77f [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.240.13
Destination Address: 10.253.144.11
User Datagram Protocol, Src Port: 5246, Dst Port: 5252
Control And Provisioning of Wireless Access Points - Control
Preamble
Datagram Transport Layer Security
Dec 1st 2022:
radio reloaded: sensord cmd(0x03) failed slot 1
[cmd timeout] wifi1: 0x9184=unknown intCode:0x1184 last 0x801c=SetRadio
The crash signature matches the bug mentioned below which has a fix in 10.8.171.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224
Informed customer to upgrade WLC to 8.10.181 which is DNAC 2.3 compatible
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Recommended to upgrade the SDA WLC to 8.10.181 as well.
Hope you are doing well!.
I just received a confirmation that you can upgrade the WLC to 8.10.181.
Our SDA team ran a sanity check with version 8.10.181.0 and everything works fine with DNAC.
I would request you to go ahead with upgrading to 8.10.181.0.
Please feel free to let me know if you have any further queries.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue
For CAPWAP traffic from WLC to AP takes path from Edge which might be the reason for CAPWAP keepalives to get dropped
Fro traffic from WLC to AP, we checked packet capture on AP connected port and we see source as a FE.
Frame 20642: 173 bytes on wire (1384 bits), 173 bytes captured (1384 bits) on interface \Device\NPF_{F90C5072-EDB0-4466-991E-486944B5A317}, id 0
Ethernet II, Src: Cisco_9a:32:c0 (70:79:b3:9a:32:c0), Dst: Cisco_36:70:e7 (f8:7a:41:36:70:e7)
Internet Protocol Version 4, Src: 172.18.1.2, Dst: 172.18.1.61
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 159
Identification: 0x81b3 (33203)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 250
Protocol: UDP (17)
Header Checksum: 0xa41e [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.1.2
Destination Address: 172.18.1.61
User Datagram Protocol, Src Port: 65419, Dst Port: 4789
Virtual eXtensible Local Area Network
Ethernet II, Src: Cisco_9f:00:00 (00:00:0c:9f:00:00), Dst: ba:25:cd:f4:ad:38 (ba:25:cd:f4:ad:38)
Internet Protocol Version 4, Src: 172.18.240.13, Dst: 10.253.144.11
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 109
Identification: 0x50bf (20671)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 251
Protocol: UDP (17)
Header Checksum: 0xf77f [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.240.13
Destination Address: 10.253.144.11
User Datagram Protocol, Src Port: 5246, Dst Port: 5252
Control And Provisioning of Wireless Access Points - Control
Preamble
Datagram Transport Layer Security
Dec 1st 2022:
radio reloaded: sensord cmd(0x03) failed slot 1
[cmd timeout] wifi1: 0x9184=unknown intCode:0x1184 last 0x801c=SetRadio
The crash signature matches the bug mentioned below which has a fix in 10.8.171.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224
Requested SDWAN team to share the 8.10.181 compatible firmware for SDWAN
Hi Vaibhav / Sharath / Kishor / Ramya,
Greetings !
As per understand provided on below mail trail it seems that we cannot have a stable SDI environment due to compatibility issues due to https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224 bug is fixed in 8.10.181.4 which is not a SDI compatible.
@Kishorbabu C (kishobab)<mailto:[email protected]> and @Ramya M (ramym)<mailto:[email protected]> Please discuss internally and share an approach to get a fixed image from DE BU.
Suggestions :-
* Either 8.10.151.0 - which is SDA compatible image can have the SMU patch for this bug.
* Or 8.10.181.4 - can be engineered for SDA.
I checked and even for latest DNAC release 2.3.x ( 2.3.3.5 and 2.3.4) , I do not see 8.10.181.4 as supported/recommended image for SDA.
Thank you for the update.
Glad to hear that the Aps are stable now after the upgrade.
Let me request my colleague from SDA to assist with the compatible version.
@Vibhav Shinde (vibshind)<mailto:[email protected]>,
Could you please assist us with the 8.10.181.4 compatible versions for SDN?.
Thanks for your response.
I hope you would be doing well now.
As an update I would like to inform you that we have upgraded our on production WLC (TLDC-WLC2) to 8.10.181.4.
So far we have not received any issues of AP resetting capwap tunnel or radio resets causing client disconnections.
But upgrading WLC to fix code and migrating impacted site AP's to fixed WLC code is workaround approach which cannot be taken forward.
We require 8.10.181.4 compatible versions for SDN ( Fabric ) WLC's ( 8540's AirOS ) for long term solution.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue
For CAPWAP traffic from WLC to AP takes path from Edge which might be the reason for CAPWAP keepalives to get dropped
Fro traffic from WLC to AP, we checked packet capture on AP connected port and we see source as a FE.
Frame 20642: 173 bytes on wire (1384 bits), 173 bytes captured (1384 bits) on interface \Device\NPF_{F90C5072-EDB0-4466-991E-486944B5A317}, id 0
Ethernet II, Src: Cisco_9a:32:c0 (70:79:b3:9a:32:c0), Dst: Cisco_36:70:e7 (f8:7a:41:36:70:e7)
Internet Protocol Version 4, Src: 172.18.1.2, Dst: 172.18.1.61
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 159
Identification: 0x81b3 (33203)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 250
Protocol: UDP (17)
Header Checksum: 0xa41e [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.1.2
Destination Address: 172.18.1.61
User Datagram Protocol, Src Port: 65419, Dst Port: 4789
Virtual eXtensible Local Area Network
Ethernet II, Src: Cisco_9f:00:00 (00:00:0c:9f:00:00), Dst: ba:25:cd:f4:ad:38 (ba:25:cd:f4:ad:38)
Internet Protocol Version 4, Src: 172.18.240.13, Dst: 10.253.144.11
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 109
Identification: 0x50bf (20671)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 251
Protocol: UDP (17)
Header Checksum: 0xf77f [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.240.13
Destination Address: 10.253.144.11
User Datagram Protocol, Src Port: 5246, Dst Port: 5252
Control And Provisioning of Wireless Access Points - Control
Preamble
Datagram Transport Layer Security
Dec 1st 2022:
radio reloaded: sensord cmd(0x03) failed slot 1
[cmd timeout] wifi1: 0x9184=unknown intCode:0x1184 last 0x801c=SetRadio
The crash signature matches the bug mentioned below which has a fix in 10.8.171.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224
Hi Ameera, we discussed the bug fixed engineering image is 8.10.181.4 (right ?)
We also discussed there is no fixed image for SDA, and Sharath shall help in getting engineering image for SDA WLC( presently running on 8.10.151.0 with DNAC 2.2.2.9).
Regarding packets drops against below logs, Cisco found this is happening when there is a load, which is causing the AP to go down.
That is the BUG.
Confirmed by Oliver( in CC) that when load is not there, packet drop also not there.
BUG description: Cisco Aironet Access Point (AP) radio may trigger a device to reload under certain conditions of high device data utilization leading to packet drops
Nov 22 11:08:24 kernel: [*11/22/2022 11:08:24.4998] Max retransmission count exceeded, going back to DISCOVER mode.
* Why are we saying that there is network issue (This could be due to packet drop between WLC and AP and suggested collecting caps.) ?
Is Cisco not convinced about the bug ? Pls clarify.
NCS maintenance team, Pls follow up with Cisco to get the image.
Thanks for the time on the call.
As summary:
* The logs from one AP is showing a wired side issue that the AP is losing the keep-alive packet and reached the max retransmissions.
* This could be due to packet drop between WLC and AP and suggested collecting caps.
* From WLC side we can increase the AP count and intervals :
* https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/configuration-guide/b_cg81/b_cg81_chapter_01111001.pdf
Nov 22 11:08:12 kernel: [*11/22/2022 11:08:12.9134] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=67
Nov 22 11:08:12 kernel: [*11/22/2022 11:08:12.9135]
Nov 22 11:08:15 kernel: [*11/22/2022 11:08:15.8115] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=8, NumofPendingMsgs=70
Nov 22 11:08:15 kernel: [*11/22/2022 11:08:15.8115]
Nov 22 11:08:18 kernel: [*11/22/2022 11:08:18.7069] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=11, NumofPendingMsgs=73
Nov 22 11:08:18 kernel: [*11/22/2022 11:08:18.7069]
Nov 22 11:08:21 kernel: [*11/22/2022 11:08:21.6039] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=11, NumofPendingMsgs=73
Nov 22 11:08:21 kernel: [*11/22/2022 11:08:21.6039]
Nov 22 11:08:24 kernel: [*11/22/2022 11:08:24.4998] Max retransmission count exceeded, going back to DISCOVER mode.
* Regarding the AP crash we can see we are hitting this bug https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvz08781 which is fixed on the latest on 8.10.
As we agreed @Sharath Chandrashekar (sharcha2)<mailto:[email protected]> will reach the escalation team to check the below thing related to the bug:
* What is the amount of data/clients that the AP can handle before it crash .
* We need a fixed version that is compatible with a fabric network and DNAC version 2.2.2.9.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
For CAPWAP traffic from WLC to AP takes path from Edge which might be the reason for CAPWAP keepalives to get dropped
Fro traffic from WLC to AP, we checked packet capture on AP connected port and we see source as a FE.
Frame 20642: 173 bytes on wire (1384 bits), 173 bytes captured (1384 bits) on interface \Device\NPF_{F90C5072-EDB0-4466-991E-486944B5A317}, id 0
Ethernet II, Src: Cisco_9a:32:c0 (70:79:b3:9a:32:c0), Dst: Cisco_36:70:e7 (f8:7a:41:36:70:e7)
Internet Protocol Version 4, Src: 172.18.1.2, Dst: 172.18.1.61
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 159
Identification: 0x81b3 (33203)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 250
Protocol: UDP (17)
Header Checksum: 0xa41e [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.1.2
Destination Address: 172.18.1.61
User Datagram Protocol, Src Port: 65419, Dst Port: 4789
Virtual eXtensible Local Area Network
Ethernet II, Src: Cisco_9f:00:00 (00:00:0c:9f:00:00), Dst: ba:25:cd:f4:ad:38 (ba:25:cd:f4:ad:38)
Internet Protocol Version 4, Src: 172.18.240.13, Dst: 10.253.144.11
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x18 (DSCP: Unknown, ECN: Not-ECT)
Total Length: 109
Identification: 0x50bf (20671)
010. .... = Flags: 0x2, Don't fragment
...0 0000 0000 0000 = Fragment Offset: 0
Time to Live: 251
Protocol: UDP (17)
Header Checksum: 0xf77f [validation disabled]
[Header checksum status: Unverified]
Source Address: 172.18.240.13
Destination Address: 10.253.144.11
User Datagram Protocol, Src Port: 5246, Dst Port: 5252
Control And Provisioning of Wireless Access Points - Control
Preamble
Datagram Transport Layer Security
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
For CAPWAP traffic from WLC to AP takes path from Edge which might be the reason for CAPWAP keepalives to get dropped
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Software Failure
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted.
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Software Failure
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted.
Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted.
timestamp : 2023-07-20T04:31:04.000+0000 || updatedby : sharcha2 || type : RESOLUTION SUMMARY || visibility : External || details : 8.10.185.3 special image shared with customer with bug fixes for AP crash issue | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Thank you for your email.
We received an update form our escalation team and we have opened two new bugs internally to further investigate and below is the status:
1
AP BIZ2-04-AP24
Kernel Panic/ PC is at __udelay+0x30/0x48
1.
0xffffffc000338900 __udelay + 0x30
2.
0xffffffbffc44d52c osl_delay + 0x2c
New bug - CSCwe91301 for further investigation
2
AP TB-02-AP04
Kernel Panic/ PC is at get_partial_node.isra.24+0x140/0x288
1.
0xffffffc000088d30 dump_backtrace + 0x150
2.
0xffffffc000088e94 show_stack + 0x20
3.
0xffffffc000668b30 dump_stack + 0xb0
4.
0xffffffc000156058 print_bad_pte + 0x1d0
5.
0xffffffc0001579cc unmap_single_vma + 0x5d0
6.
0xffffffc0001582d8 unmap_vmas + 0x68
7.
0xffffffc00015f9b4 exit_mmap + 0xf8
8.
0xffffffc00009c354 mmput + 0x118
9.
0xffffffc0000a0afc do_exit + 0x8e0
10.
0xffffffc0000a120c do_group_exit + 0xb0
11.
0xffffffc0000a1290 __wake_up_parent + 0x28
New bug - CSCwe91264 for further investigation
3
AP ERC-02-AP49
CALLBACK FULL Reset Radio
Unable to Decode
Collect all .txt from /storages/cores/
AP ERC-02-AP51
CALLBACK FULL Reset Radio
Unable to Decode
Collect all .txt from /storages/cores/
AP ERC-B1-AP03
CALLBACK FULL Reset Radio
Unable to Decode
Collect all .txt from /storages/cores/
The below 3 AP crashes belong to AP model 1810W, which is EOL.
I will further check with the team internally to see how we can proceed on this:
4
AP i4-05-AP55
Kernel Panic/ PC is at skb_recycler_alloc+0x84/0x2e4
1.
0xc039a954 skb_recycler_alloc + 0x84
2.
0xc037bbe0 dev_alloc_skb_poolid + 0x24
3.
0xbfbe9678 __adf_nbuf_alloc + 0x28
4.
0xbfccff54 wbuf_alloc + 0x5c
5.
0xbfd08e2c wmi_buf_alloc + 0x20
6.
0xbfcf8fb4 wmi_unified_set_qboost_param + 0x30
7.
0xbfcf904c qboost_config + 0x18
8.
0xbfcf92d8 ol_ath_net80211_newassoc + 0x288
9.
0xbfc6a65c ieee80211_mlme_recv_assoc_request + 0x418
10.
0xbfc1ed5c ieee80211_ucfg_splitmac_add_client + 0xc3c
11.
0xbfcb8d04 acfg_add_client + 0x280
12.
0xbfcb92dc acfg_handle_vap_ioctl + 0x10c
13.
0xbfca73b4 ieee80211_ioctl + 0x2720
14.
0xc038962c dev_ifsioc + 0x300
15.
0xc0389db8 dev_ioctl + 0x764
16.
0xc0372e80 sock_ioctl + 0x260
17.
0xc0104730 do_vfs_ioctl + 0x5a0
18.
0xc01047b8 sys_ioctl + 0x3c
19.
0xc000e680 ret_fast_syscall + 0x0
AP i4-05-AP55
Kernel Panic/ PC is at skb_recycler_alloc+0x84/0x2e4
1.
0xc039a954 skb_recycler_alloc + 0x84
2.
0xc037bbe0 dev_alloc_skb_poolid + 0x24
3.
0xbfbe9678 __adf_nbuf_alloc + 0x28
4.
0xbfccff54 wbuf_alloc + 0x5c
5.
0xbfd08e2c wmi_buf_alloc + 0x20
6.
0xbfcf8fb4 wmi_unified_set_qboost_param + 0x30
7.
0xbfcf904c qboost_config + 0x18
8.
0xbfcf92d8 ol_ath_net80211_newassoc + 0x288
9.
0xbfc6a65c ieee80211_mlme_recv_assoc_request + 0x418
10.
0xbfc1ed5c ieee80211_ucfg_splitmac_add_client + 0xc3c
11.
0xbfcb8d04 acfg_add_client + 0x280
12.
0xbfcb92dc acfg_handle_vap_ioctl + 0x10c
13.
0xbfca73b4 ieee80211_ioctl + 0x2720
14.
0xc038962c dev_ifsioc + 0x300
15.
0xc0389db8 dev_ioctl + 0x764
16.
0xc0372e80 sock_ioctl + 0x260
17.
0xc0104730 do_vfs_ioctl + 0x5a0
18.
0xc01047b8 sys_ioctl + 0x3c
19.
0xc000e680 ret_fast_syscall + 0x0
AP CELC-03-AP11
Kernel Panic/ PC is at skb_recycler_alloc+0x84/0x2e4
1.
0xc039a954 skb_recycler_alloc + 0x84
2.
0xc037bbe0 dev_alloc_skb_poolid + 0x24
3.
0xbfbe9678 __adf_nbuf_alloc + 0x28
4.
0xbfd34cac htt_h2t_dbg_stats_get + 0x6c
5.
0xbfd2c218 ol_txrx_fw_stats_get + 0x110
6.
0xbfcd94c0 ol_ath_fw_stats_timeout + 0xb0
7.
0xc006b664 run_timer_softirq + 0x168
8.
0xc0065ba0 __do_softirq + 0xf4
9.
0xc0066070 irq_exit + 0x54
10.
0xc000ef5c handle_IRQ + 0x88
11.
0xc00085ec gic_handle_irq + 0x94
12.
0xc000e340 __irq_svc + 0x40
The below two AP crashes are still being investigated upon and will have an update shortly.
5
AP IT-01-AP13
Kernel Panic/ PC is at misc_open+0x48/0x198
0xffffffc0003d01c8 misc_open + 0x48
0xffffffc0003d01b0 misc_open + 0x30
AP E1-05-AP08
Kernel Panic/ PC is at misc_open+0x48/0x198
1.
0xffffffc0003d01c8 misc_open + 0x48
2.
0xffffffc0003d01b0 misc_open + 0x30
Could you please help me collect all .txt files from /storages/cores/ from the 3 Aps (AP ERC-02-AP49, AP ERC-02-AP51 & AP ERC-B1-AP03) so I can share it with our team for further analysis.
Please let me know your availability so I can collect the required logs.
Please feel free to let me know if you have any further queries.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Recommended to upgrade the SDA WLC to 8.10.181 as well.
jan 27th : crash file of 9120 has
from crash file
PC is at rb_
next+0xc/0x6c
LR is at pick_next_task_fair+0x4
8/0x160.
CSCwa34136 Cisco 3802 FQI/NMI reset at rb_next+0xc
the fix is to upgrade to 8.10.171
During the upgrade customer was facing FN - 72524.
Customer will perform the upgrade from 6 PM SGT to next day 7 AM SGT. They plan to do reboots at 12 midnight of 24th feb and 25th feb.
I had a check internally and found that Wism2 is EOL and end of support and hence 8.10.183 is not available.
The last version released for Wism2 was 8.5.171.
Please feel free to let me know if you have any further queries.
Can we get 8.10.183.0 for wism2.
Its urgent.
Findings from crash logs:
1. From the two AP crash logs, it looks like they have different crash signatures.
Decoding one of the crash signatures, we found it to be similar to bug CSCvz08781, for which the solution is to upgrade to 8.10.161.
2. Since we were not able to find a hit for the second crash, we will have a discussion internally to see if this is a new issue.
Recommended to upgrade the SDA WLC to 8.10.181 as well.
jan 27th : crash file of 9120 has
from crash file
PC is at rb_
next+0xc/0x6c
LR is at pick_next_task_fair+0x4
8/0x160.
CSCwa34136 Cisco 3802 FQI/NMI reset at rb_next+0xc
the fix is to upgrade to 8.10.171
During the upgrade customer was facing FN - 72524.
There is a query from Biswajit.
Can we upgrade the WLC 8.10.181.4 to 8.10.183.0, since 8.10.181.0 is deferred.
I believe the answer is Yes but wanted to double confirm from Cisco TAC.
I just got a confirmation from the DE team that 8.10.183.0 will be supported with DNAC 2.2.2.9 .
Compatibility Matrix should be updated by this week.
Please feel free to let us know if you have any further queries.
You are right.
I have requested for compatibility between DNAC 2.2.2.9 and wlc 8.10.183.
I will keep you updated as soon as I hear from the DE team.
Please correct , we need compatibility conformation on DNAC 2.2.2.9 with 8.10.183.0 from Cisco.
Yes, Testing was done on 26th JAN for POVWLC1 and 4.
Below is the snippet.
Conclusion :- No compatibility issues found between 2.2.2.9 and 8.10.183.0.
+Baby John
Hi Satyam, you have tested this OS 8.10.183 in POV environment with DNAC 2.2.2.9 , did you find any issues ? Pls share.
I apologize for the confusion.
Yes, are you right 8.10.183 is not in the list of supported release for DNAC 2.2.2.9.
Since, 8.10.181 has been deferred and is not available for download, please allow me a day time so I can check with DNAC DE team if they can include 8.10.183 in the compatibility matrix and also get a confirmation if they have done some testing so you can proceed with the upgrade.
Please feel free to let us know if you have any further queries.
I also just noticed the same.
Below screenshot shared is from 2.3.3.6 ( by TAC ) but I concur checking the same for 2.2.2.9 compatibility with 8.10.183.0.
I have reached out Cisco TM on the same and expected to get response in 30 mins from TAC.
Hi Satyam / Sharath
Do note that the current production DNAC is on ver 2.2.2.9.
however, 8.10.183 is not in the compatibility list with DNAC 2.2.2.9 officially.
Cisco team, please advise if we still can proceed with the WLC firmware upgrade.
[Icon Description automatically generated]
Can we say if the bug is fixed in earlier release i.e.
8.10.168.0 and 8.10.171.0 which both are deferred now, will be fixed in 8.10.183.0.
Urgently.
Hope you are doing well!.
I just received a confirmation that you can upgrade the WLC to 8.10.181.
Our SDA team ran a sanity check with version 8.10.181.0 and everything works fine with DNAC.
I would request you to go ahead with upgrading to 8.10.181.0.
Please feel free to let me know if you have any further queries.
Hi Vaibhav / Sharath / Kishor / Ramya,
Greetings !
As per understand provided on below mail trail it seems that we cannot have a stable SDI environment due to compatibility issues due to https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224 bug is fixed in 8.10.181.4 which is not a SDI compatible.
@Kishorbabu C (kishobab)<mailto:[email protected]> and @Ramya M (ramym)<mailto:[email protected]> Please discuss internally and share an approach to get a fixed image from DE BU.
Suggestions :-
* Either 8.10.151.0 - which is SDA compatible image can have the SMU patch for this bug.
* Or 8.10.181.4 - can be engineered for SDA.
I checked and even for latest DNAC release 2.3.x ( 2.3.3.5 and 2.3.4) , I do not see 8.10.181.4 as supported/recommended image for SDA.
Thank you for the update.
Glad to hear that the Aps are stable now after the upgrade.
Let me request my colleague from SDA to assist with the compatible version.
@Vibhav Shinde (vibshind)<mailto:[email protected]>,
Could you please assist us with the 8.10.181.4 compatible versions for SDN?.
Thanks for your response.
I hope you would be doing well now.
As an update I would like to inform you that we have upgraded our on production WLC (TLDC-WLC2) to 8.10.181.4.
So far we have not received any issues of AP resetting capwap tunnel or radio resets causing client disconnections.
But upgrading WLC to fix code and migrating impacted site AP's to fixed WLC code is workaround approach which cannot be taken forward.
We require 8.10.181.4 compatible versions for SDN ( Fabric ) WLC's ( 8540's AirOS ) for long term solution.
I apologize for the delay.
I was on a medical leave for the past couple of days.
I analysed the AP13 crash logs and found that the reason the crash is radio slot 1 reload due to:
radio reloaded: sensord cmd(0x03) failed slot 1
[cmd timeout] wifi1: 0x9184=unknown intCode:0x1184 last 0x801c=SetRadio
The crash signature matches the bug mentioned below which has a fix in 10.8.171.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx96224
Could you please let me know if you upgraded the test WLC to the escalation image 8.10.181.4 and still see issues with crash or clients unable to connect?.
Please feel free to let me know if you have any further queries and I will be glad to assist you.
Hi Ameera, we discussed the bug fixed engineering image is 8.10.181.4 (right ?)
We also discussed there is no fixed image for SDA, and Sharath shall help in getting engineering image for SDA WLC( presently running on 8.10.151.0 with DNAC 2.2.2.9).
Regarding packets drops against below logs, Cisco found this is happening when there is a load, which is causing the AP to go down.
That is the BUG.
Confirmed by Oliver( in CC) that when load is not there, packet drop also not there.
BUG description: Cisco Aironet Access Point (AP) radio may trigger a device to reload under certain conditions of high device data utilization leading to packet drops
Nov 22 11:08:24 kernel: [*11/22/2022 11:08:24.4998] Max retransmission count exceeded, going back to DISCOVER mode.
* Why are we saying that there is network issue (This could be due to packet drop between WLC and AP and suggested collecting caps.) ?
Is Cisco not convinced about the bug ? Pls clarify.
NCS maintenance team, Pls follow up with Cisco to get the image.
Thanks for the time on the call.
As summary:
* The logs from one AP is showing a wired side issue that the AP is losing the keep-alive packet and reached the max retransmissions.
* This could be due to packet drop between WLC and AP and suggested collecting caps.
* From WLC side we can increase the AP count and intervals :
* https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/configuration-guide/b_cg81/b_cg81_chapter_01111001.pdf
Nov 22 11:08:12 kernel: [*11/22/2022 11:08:12.9134] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=67
Nov 22 11:08:12 kernel: [*11/22/2022 11:08:12.9135]
Nov 22 11:08:15 kernel: [*11/22/2022 11:08:15.8115] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=8, NumofPendingMsgs=70
Nov 22 11:08:15 kernel: [*11/22/2022 11:08:15.8115]
Nov 22 11:08:18 kernel: [*11/22/2022 11:08:18.7069] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=11, NumofPendingMsgs=73
Nov 22 11:08:18 kernel: [*11/22/2022 11:08:18.7069]
Nov 22 11:08:21 kernel: [*11/22/2022 11:08:21.6039] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=11, NumofPendingMsgs=73
Nov 22 11:08:21 kernel: [*11/22/2022 11:08:21.6039]
Nov 22 11:08:24 kernel: [*11/22/2022 11:08:24.4998] Max retransmission count exceeded, going back to DISCOVER mode.
* Regarding the AP crash we can see we are hitting this bug https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvz08781 which is fixed on the latest on 8.10.
As we agreed @Sharath Chandrashekar (sharcha2)<mailto:[email protected]> will reach the escalation team to check the below thing related to the bug:
* What is the amount of data/clients that the AP can handle before it crash .
* We need a fixed version that is compatible with a fabric network and DNAC version 2.2.2.9.
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Software Failure
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted.
Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted.
timestamp : 2023-07-20T04:31:04.000+0000 || updatedby : sharcha2 || type : RESOLUTION SUMMARY || visibility : External || details : 8.10.185.3 special image shared with customer with bug fixes for AP crash issue | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Software Failure
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted. | Problem Description :- Clients unable to connect to an AP suspecting AP crash.
Setup :- SDA
WLC :- 172.18.240.13 – 8.10.151.0
DNAC :- 172.18.12.35
Impacted Location :- Global/NUS_fabric1/KR-SCIYIH/SCIYIH-MPSH/SCIYIH-MPSH2
AP’s impacted :-
1. MPSH2-02-AP20 - 10.253.152.238
2. MPSH2-02-AP22 - 10.253.190.6
3. MPSH2-02-AP23
Observations :-
AT approximately 9:15 am SGT we got a complaint that client are not able to connect to NUS SSID.
We saw checked in Prime and found that AP 22 and AP 20 getting alert for crash.
Checked and collected logs for AP 10.253.152.238.
After checking further, we can see many AP’s got rebooted. | timestamp : 2023-07-20T04:31:04.000+0000 || updatedby : sharcha2 || type : RESOLUTION SUMMARY || visibility : External || details : 8.10.185.3 special image shared with customer with bug fixes for AP crash issue | nan | AIR-AP2802I-S-K9 | ap3g3-ME-3800-k9w8-ubifs-8.10.185.0.img | nan | nan | 2 | nan | Software Bug | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | nan | nan | nan | nan | nan | nan |
694907945 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 3.0.0.458/ 2.7.0.356/ 3.0.0.448/ 3.0.0.458/ 3.0.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Good day!
I went through the support bundle you provided.
Please find my analysis below:
This device is showing evidence of encountering CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>: Java minimum heap value is to low which can lead to excessive garbage collection
Symptoms seen:
Authentication step latency on multiple policy evaluation steps.
High average request latency during times of peak load.
Authentication request latency does not recover until after the system is reloaded.
Mitigation:
Apply the universal hotfix to all nodes in the deployment and when available apply the patch with the fix for the installed ISE version.
The details of which are mentioned in my previous email to you as well.
Please find the log snippet below:
- ./ise-support-bundle-hsdc-pan-nac01-nusnggk-01-30-2023-23-17/support/showtech/showtech.out - The regex highlighted below detects the iseadminportal service starting with the low java Xms value:
32086: iseadminportal 39346 60.8 4.4 27227720 4319240 Sl Jan 18 7-07:12:48 \_ jsvc.exec -java-home /opt/CSCOcpm/jre -server -user iseadminportal -outfile /opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/logs/catalina.out -errfile /opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/logs/catalina.out -pidfile /var/run/catalina.pid -Xms256m -Xmx21474836480 -XX:MaxGCPauseMillis=500 -XX:MetaspaceSize=512M -XX:MaxMetaspaceSize=512M -XX:MaxDirectMemorySize=2g -XX:+DisableExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/localdisk/corefiles -XX:OnOutOfMemoryError=/opt/CSCOcpm/bin/iseoomrestart.sh -XX:ErrorFile=/localdisk/corefiles/hs_err_pid%p.log -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -verbose:gc -Xloggc:/localdisk/gc/gc_app.log.20230118232240 -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:GCLogFileSize=3M -XX:NumberOfGCLogFiles=31 -XX:+PrintGCApplicationStoppedTime -Dsun.rmi.dgc.client.gcInterval=1800000 -Dsun.rmi.dgc.server.gcInterval=1800000 -Djdk.nio.maxCachedBufferSize=1000000 -Ddisable.logs.transaction=true -DisSSLEnabled=true -Ddb.configurations=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/db.properties -Dlog4j.configuration=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/log4j.xml -Doracle.jms.minSleepTime=200 -Doracle.jms.maxSleepTime=500 -DUSERTYPE_FILTER=NSFEndPointType -Dcom.cisco.cpm.provisioning.filesaverlocation=/tmp/download -Dpdp.heartbeat.cfg=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/pdp_hb_config.xml -Dise.access.map=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/access-map.xml -Drbac.superadmin.accesscheck.on=true -Dcom.cisco.cpm.version=3.0.0.458 -Dcom.cisco.cpm.udipid=SNS-3655-K9 -Dcom.cisco.cpm.udivid=A0 -Dcom.cisco.cpm.udisn=WZP23040NF3 -Dcom.cisco.cpm.udipt=UCS -Dcom.cisco.cpm.osversion=3.0.8.091 -DREPLIC_TRANSPORT_TYPE=JGroup -Dfake.pipmgr=true -DnoContextCopy=true -DlicenseSleepTime=24 -Djavax.net.ssl.keyStore=NONE -Djavax.net.ssl.keyStoreType=PKCS11 -Dise.fipsMode=false -Djdk.tls.ephemeralDHKeySize=2048 -Dorg.terracotta.quartz.skipUpdateCheck=true -Dreplication.monitor.on=true -Dorg.owasp.esapi.SecurityConfiguration=org.owasp.esapi.reference.DefaultSecurityConfiguration -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -Dsmack.debugEnabled=true -Dsmack.debuggerClass=org.jivesoftware.smackx.debugger.slf4j.SLF4JSmackDebugger -Djgroups.logging.log_factory_class=com.cisco.epm.logging.CustomLoggerFactoryForJgroups -DsslEnabledProtocolsMediumSecurity=TLSv1,TLSv1.1,TLSv1.2 -DsslEnabledProtocolsHighSecurity=TLSv1.1,TLSv1.2 -Doracle.jdbc.autoCommitSpecCompliant=false -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true -Dorg.jboss.logging.provider=log4j -DMntSessionDirectory.fetchAmount=10000 -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -Dio.netty.allocator.numDirectArenas=0 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=127.0.0.1 -Dcom.sun.management.jmxremote.rmi.port=9999 -Dcom.sun.management.jmxremote.local.only=false -XX:OnError=/usr/bin/sudo /opt/CSCOcpm/bin/isegencore.sh %p -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/conf/logging.properties -Dfile.encoding=UTF-8 -Dorg.terracotta.quartz.skipUpdateCheck=true -Dnet.sf.ehcache.skipUpdateCheck=true -Dorg.quartz.scheduler.skipUpdateCheck=true -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2 -DPROFILER_ROOT=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30 -javaagent:/opt/CSCOcpm/appsrv/apache-tomcat/lib/javaagent.jar -Djava.endorsed.dirs= -classpath /opt/system/java/lib/CARSJava-2.0-api.jar:/opt/system/java/lib/CARSJava-2.0-impl.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/bin/bootstrap.jar:/opt/CSCOcpm/prrt/lib/prrt-interface.jar:/opt/CSCOcpm/prrt/lib/prrt-flowapi.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/lib/log4j-rolling-appender-20131024-2017.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/lib/log4j-1.2.17.jar:/opt/TimesTen/tt1121/lib/ttjdbc6.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/bin/tomcat-juli.jar -Dcatalina.base=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30 -Dcatalina.home=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30 -Djava.io.tmpdir=/opt/CSCOcpm/temp -Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger org.apache.catalina.startup.Bootstrap start
This is a confirmation that you are still hitting the bug CSCwd45843<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbst.cloudapps.cisco.com%2Fbugsearch%2Fbug%2FCSCwd45843&data=05%7C01%7Cgeorgekingsley.paulsundararaj%40ncs.com.sg%7C9e66dfb8dca349ae8ab408daf9b8acd7%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638096868815388131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=c41EUSmTYxeI5W4su6ayOkPnH0BKumDN6gs68zO3GgY%3D&reserved=0>.
The hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsoftware.cisco.com%2Fdownload%2Fhome%2F283801620%2Ftype%2F283802505%2Frelease%2FHP-CSCwd45843&data=05%7C01%7Cgeorgekingsley.paulsundararaj%40ncs.com.sg%7C9e66dfb8dca349ae8ab408daf9b8acd7%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638096868815388131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=C3zMOOmCfs%2BFFLKXys0s1mPQmal8tOhej1odqqEnOww%3D&reserved=0>.
Please do let me know if you have any further queries or concerns on the same.
Update 25th Jan:
Please find my analysis below:
From the tech top output we see a high CPU is consumed by the jsvc process:
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 12:34:09 up 450 days, 15:44, 2 users, load average: 15.65, 16.77, 17.33
Tasks: 628 total, 1 running, 627 sleeping, 0 stopped, 0 zombie
%Cpu(s): 80.9 us, 1.1 sy, 0.0 ni, 17.6 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13726596 free, 38382248 used, 45327204 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42646812 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80839 iseadmi+ 20 0 30.4g 9.3g 40464 S 1794 10.0 296801:20 jsvc
60426 iseelas+ 20 0 18.0g 16.3g 472868 S 100.0 17.5 71810:49 java
115925 iserabb+ 20 0 2884300 1.0g 2692 S 52.9 1.1 2961:51 beam.smp
3896 root 20 0 164760 2688 1576 R 11.8 0.0 0:00.03 top
1 root 20 0 195436 6776 3108 S 0.0 0.0 402:34.45 systemd
2 root 20 0 0 0 0 S 0.0 0.0 3:30.34 kthreadd
4 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0+
6 root 20 0 0 0 0 S 0.0 0.0 106:27.39 ksoftirqd+
7 root rt 0 0 0 0 S 0.0 0.0 0:50.52 migration+
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root 20 0 0 0 0 S 0.0 0.0 1720:11 rcu_sched
10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 lru-add-d+
11 root rt 0 0 0 0 S 0.0 0.0 2:12.02 watchdog/0
12 root rt 0 0 0 0 S 0.0 0.0 2:15.41 watchdog/1
13 root rt 0 0 0 0 S 0.0 0.0 0:51.29 migration+
14 root 20 0 0 0 0 S 0.0 0.0 87:25.21 ksoftirqd+
On further checking the sub process ID we see the following PIDs are consuming the CPU threads: (Omitted some lined for brevity)
sh-4.2# top -H -p 80839
top - 12:52:56 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1707 total, 18 running, 1689 sleeping, 0 stopped, 0 zombie
%Cpu(s): 64.8 us, 1.6 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13678112 free, 38274636 used, 45483300 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42754628 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80854 iseadmi+ 20 0 30.4g 9.3g 40816 R 72.2 10.0 13611:41 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:51 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:17 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:29 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80850 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:25 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:47 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13613:02 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:11 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:31 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:00 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:45 jsvc
top - 12:52:59 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1710 total, 1 running, 1709 sleeping, 0 stopped, 0 zombie
%Cpu(s): 69.7 us, 0.6 sy, 0.0 ni, 29.4 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13669704 free, 38280428 used, 45485916 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42749708 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80846 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:54 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13611:33 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:11 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:20 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:31 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:14 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:15 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:49 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:04 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:02 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:14 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:29 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:33 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.2 10.0 13611:44 jsvc
top - 12:53:02 up 450 days, 16:03, 6 users, load average: 18.13, 16.74, 16.72
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 67.5 us, 1.1 sy, 0.0 ni, 31.1 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
KiB Mem : 97436048 total, 13651640 free, 38298472 used, 45485936 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42730576 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80850 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.9 10.0 13612:30 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:56 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:22 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:33 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:52 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:16 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:13 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:56 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13613:17 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:32 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:35 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13613:06 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:46 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:36 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:04 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13612:50 jsvc
top - 12:53:05 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 70.4 us, 0.6 sy, 0.0 ni, 28.8 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13647332 free, 38299860 used, 45488856 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42729004 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:54 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:18 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:38 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:16 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:34 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:59 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:25 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:36 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:20 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:09 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:48 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:07 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:59 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:19 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:38 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.2 10.0 13612:19 jsvc
top - 12:53:08 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1712 total, 18 running, 1694 sleeping, 0 stopped, 0 zombie
%Cpu(s): 66.5 us, 1.5 sy, 0.0 ni, 31.6 id, 0.1 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13645540 free, 38302700 used, 45487808 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42726808 avail Mem
From catalina.out we observed the following:
We see the that the following Garbage collector threads are consuming high CPU:
"main" #1 prio=5 os_prio=0 tid=0x0000000002313000 nid=0x13bc7 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"VM Thread" os_prio=0 tid=0x0000000002642000 nid=0x13be2 runnable
"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002325800 nid=0x13bce runnable
"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002327800 nid=0x13bcf runnable
"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x0000000002329000 nid=0x13bd0 runnable
"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x000000000232b000 nid=0x13bd1 runnable
"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x000000000232d000 nid=0x13bd2 runnable
"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x000000000232f000 nid=0x13bd3 runnable
"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x0000000002330800 nid=0x13bd4 runnable
"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x0000000002332800 nid=0x13bd5 runnable
"GC task thread#8 (ParallelGC)" os_prio=0 tid=0x0000000002334800 nid=0x13bd6 runnable
"GC task thread#9 (ParallelGC)" os_prio=0 tid=0x0000000002336000 nid=0x13bd7 runnable
"GC task thread#10 (ParallelGC)" os_prio=0 tid=0x0000000002338000 nid=0x13bd8 runnable
"GC task thread#11 (ParallelGC)" os_prio=0 tid=0x000000000233a000 nid=0x13bd9 runnable
"GC task thread#12 (ParallelGC)" os_prio=0 tid=0x000000000233b800 nid=0x13bda runnable
"GC task thread#13 (ParallelGC)" os_prio=0 tid=0x000000000233d800 nid=0x13bdb runnable
"GC task thread#14 (ParallelGC)" os_prio=0 tid=0x000000000233f800 nid=0x13bdc runnable
"GC task thread#15 (ParallelGC)" os_prio=0 tid=0x0000000002341000 nid=0x13bdd runnable
"GC task thread#16 (ParallelGC)" os_prio=0 tid=0x0000000002343000 nid=0x13bde runnable
"GC task thread#17 (ParallelGC)" os_prio=0 tid=0x0000000002345000 nid=0x13bdf runnable
"VM Periodic Task Thread" os_prio=0 tid=0x0000000002ac3800 nid=0x13cd6 waiting on condition
JNI global references: 3603
Heap
PSYoungGen total 79872K, used 288K [0x0000000635d80000, 0x000000063b280000, 0x00000007e0800000)
eden space 72704K, 0% used [0x0000000635d80000,0x0000000635dc8230,0x000000063a480000)
from space 7168K, 0% used [0x000000063ab80000,0x000000063ab80000,0x000000063b280000)
to space 7168K, 0% used [0x000000063a480000,0x000000063a480000,0x000000063ab80000)
ParOldGen total 2978304K, used 2963138K [0x00000002e0800000, 0x0000000396480000, 0x0000000635d80000)
object space 2978304K, 99% used [0x00000002e0800000,0x00000003955b0b70,0x0000000396480000)
Metaspace used 335348K, capacity 357063K, committed 358016K, reserved 1370112K
class space used 33786K, capacity 37225K, committed 37504K, reserved 1048576K
Garbage collector usage in RHEL: As long as an object is being referenced, the JVM considers it alive. Once an object is no longer referenced and therefore is not reachable by the application code, the garbage collector removes it and reclaims the unused memory. The reason GC is using more CPU cycles is that its aggressively reclaiming a huge amount of Objects which are not referenced anymore.
From the Catalina.out file we could see also the VCS threads being blocked:
"VCSPersistEventHandler-1-thread-1" #1920 prio=5 os_prio=0 tid=0x00007f42c5a27800 nid=0x185d7 waiting for monitor entry [0x00007f4224182000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.elasticsearch.action.bulk.BulkProcessor.internalAdd(BulkProcessor.java:287)
- waiting to lock <0x00000002ef9a1a28> (a org.elasticsearch.action.bulk.BulkProcessor)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:272)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:268)
at com.cisco.ise.vcs.crud.ESBulkProcessor.processRequest(ESBulkProcessor.java:122)
- locked <0x00000002ef51a570> (a com.cisco.ise.vcs.crud.ESBulkProcessor)
at com.cisco.ise.vcs.crud.VCSCrudProcessor.upsertBulkData(VCSCrudProcessor.java:98)
- locked <0x0000000308461c08> (a com.cisco.ise.vcs.crud.VCSCrudProcessor)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.updateContextRepository(VCSPersistEventHandler.java:147)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.handleEvent(VCSPersistEventHandler.java:113)
at com.cisco.ise.vcs.event.VCSEventHandler.run(VCSEventHandler.java:130)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Because of the above observations we see that you are encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>;. There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
Good day!
Thanks for the files you attached so far and I was able to come to a root cause of the issue.
Please find my analysis below:
From the tech top output we see a high CPU is consumed by the jsvc process:
hsdc-pan-nac01/admin# tech top
Invoking tech top.
Press Control-C to interrupt.
top - 12:34:09 up 450 days, 15:44, 2 users, load average: 15.65, 16.77, 17.33
Tasks: 628 total, 1 running, 627 sleeping, 0 stopped, 0 zombie
%Cpu(s): 80.9 us, 1.1 sy, 0.0 ni, 17.6 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13726596 free, 38382248 used, 45327204 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42646812 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80839 iseadmi+ 20 0 30.4g 9.3g 40464 S 1794 10.0 296801:20 jsvc
60426 iseelas+ 20 0 18.0g 16.3g 472868 S 100.0 17.5 71810:49 java
115925 iserabb+ 20 0 2884300 1.0g 2692 S 52.9 1.1 2961:51 beam.smp
3896 root 20 0 164760 2688 1576 R 11.8 0.0 0:00.03 top
1 root 20 0 195436 6776 3108 S 0.0 0.0 402:34.45 systemd
2 root 20 0 0 0 0 S 0.0 0.0 3:30.34 kthreadd
4 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0+
6 root 20 0 0 0 0 S 0.0 0.0 106:27.39 ksoftirqd+
7 root rt 0 0 0 0 S 0.0 0.0 0:50.52 migration+
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root 20 0 0 0 0 S 0.0 0.0 1720:11 rcu_sched
10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 lru-add-d+
11 root rt 0 0 0 0 S 0.0 0.0 2:12.02 watchdog/0
12 root rt 0 0 0 0 S 0.0 0.0 2:15.41 watchdog/1
13 root rt 0 0 0 0 S 0.0 0.0 0:51.29 migration+
14 root 20 0 0 0 0 S 0.0 0.0 87:25.21 ksoftirqd+
On further checking the sub process ID we see the following PIDs are consuming the CPU threads: (Omitted some lined for brevity)
sh-4.2# top -H -p 80839
top - 12:52:56 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1707 total, 18 running, 1689 sleeping, 0 stopped, 0 zombie
%Cpu(s): 64.8 us, 1.6 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13678112 free, 38274636 used, 45483300 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42754628 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80854 iseadmi+ 20 0 30.4g 9.3g 40816 R 72.2 10.0 13611:41 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:51 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:17 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:29 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80850 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:25 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:47 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13613:02 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:11 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:31 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:00 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:45 jsvc
top - 12:52:59 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1710 total, 1 running, 1709 sleeping, 0 stopped, 0 zombie
%Cpu(s): 69.7 us, 0.6 sy, 0.0 ni, 29.4 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13669704 free, 38280428 used, 45485916 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42749708 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80846 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:54 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13611:33 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:11 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:20 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:31 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:14 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:15 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:49 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:04 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:02 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:14 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:29 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:33 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.2 10.0 13611:44 jsvc
top - 12:53:02 up 450 days, 16:03, 6 users, load average: 18.13, 16.74, 16.72
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 67.5 us, 1.1 sy, 0.0 ni, 31.1 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
KiB Mem : 97436048 total, 13651640 free, 38298472 used, 45485936 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42730576 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80850 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.9 10.0 13612:30 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:56 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:22 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:33 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:52 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:16 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:13 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:56 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13613:17 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:32 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:35 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13613:06 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:46 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:36 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:04 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13612:50 jsvc
top - 12:53:05 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 70.4 us, 0.6 sy, 0.0 ni, 28.8 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13647332 free, 38299860 used, 45488856 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42729004 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:54 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:18 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:38 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:16 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:34 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:59 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:25 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:36 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:20 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:09 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:48 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:07 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:59 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:19 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:38 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.2 10.0 13612:19 jsvc
top - 12:53:08 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1712 total, 18 running, 1694 sleeping, 0 stopped, 0 zombie
%Cpu(s): 66.5 us, 1.5 sy, 0.0 ni, 31.6 id, 0.1 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13645540 free, 38302700 used, 45487808 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42726808 avail Mem
From catalina.out we observed the following:
We see the that the following Garbage collector threads are consuming high CPU:
"main" #1 prio=5 os_prio=0 tid=0x0000000002313000 nid=0x13bc7 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"VM Thread" os_prio=0 tid=0x0000000002642000 nid=0x13be2 runnable
"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002325800 nid=0x13bce runnable
"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002327800 nid=0x13bcf runnable
"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x0000000002329000 nid=0x13bd0 runnable
"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x000000000232b000 nid=0x13bd1 runnable
"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x000000000232d000 nid=0x13bd2 runnable
"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x000000000232f000 nid=0x13bd3 runnable
"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x0000000002330800 nid=0x13bd4 runnable
"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x0000000002332800 nid=0x13bd5 runnable
"GC task thread#8 (ParallelGC)" os_prio=0 tid=0x0000000002334800 nid=0x13bd6 runnable
"GC task thread#9 (ParallelGC)" os_prio=0 tid=0x0000000002336000 nid=0x13bd7 runnable
"GC task thread#10 (ParallelGC)" os_prio=0 tid=0x0000000002338000 nid=0x13bd8 runnable
"GC task thread#11 (ParallelGC)" os_prio=0 tid=0x000000000233a000 nid=0x13bd9 runnable
"GC task thread#12 (ParallelGC)" os_prio=0 tid=0x000000000233b800 nid=0x13bda runnable
"GC task thread#13 (ParallelGC)" os_prio=0 tid=0x000000000233d800 nid=0x13bdb runnable
"GC task thread#14 (ParallelGC)" os_prio=0 tid=0x000000000233f800 nid=0x13bdc runnable
"GC task thread#15 (ParallelGC)" os_prio=0 tid=0x0000000002341000 nid=0x13bdd runnable
"GC task thread#16 (ParallelGC)" os_prio=0 tid=0x0000000002343000 nid=0x13bde runnable
"GC task thread#17 (ParallelGC)" os_prio=0 tid=0x0000000002345000 nid=0x13bdf runnable
"VM Periodic Task Thread" os_prio=0 tid=0x0000000002ac3800 nid=0x13cd6 waiting on condition
JNI global references: 3603
Heap
PSYoungGen total 79872K, used 288K [0x0000000635d80000, 0x000000063b280000, 0x00000007e0800000)
eden space 72704K, 0% used [0x0000000635d80000,0x0000000635dc8230,0x000000063a480000)
from space 7168K, 0% used [0x000000063ab80000,0x000000063ab80000,0x000000063b280000)
to space 7168K, 0% used [0x000000063a480000,0x000000063a480000,0x000000063ab80000)
ParOldGen total 2978304K, used 2963138K [0x00000002e0800000, 0x0000000396480000, 0x0000000635d80000)
object space 2978304K, 99% used [0x00000002e0800000,0x00000003955b0b70,0x0000000396480000)
Metaspace used 335348K, capacity 357063K, committed 358016K, reserved 1370112K
class space used 33786K, capacity 37225K, committed 37504K, reserved 1048576K
Garbage collector usage in RHEL: As long as an object is being referenced, the JVM considers it alive.
Once an object is no longer referenced and therefore is not reachable by the application code, the garbage collector removes it and reclaims the unused memory.
The reason GC is using more CPU cycles is that its aggressively reclaiming a huge amount of Objects which are not referenced anymore.
From the Catalina.out file we could see also the VCS threads being blocked:
"VCSPersistEventHandler-1-thread-1" #1920 prio=5 os_prio=0 tid=0x00007f42c5a27800 nid=0x185d7 waiting for monitor entry [0x00007f4224182000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.elasticsearch.action.bulk.BulkProcessor.internalAdd(BulkProcessor.java:287)
- waiting to lock <0x00000002ef9a1a28> (a org.elasticsearch.action.bulk.BulkProcessor)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:272)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:268)
at com.cisco.ise.vcs.crud.ESBulkProcessor.processRequest(ESBulkProcessor.java:122)
- locked <0x00000002ef51a570> (a com.cisco.ise.vcs.crud.ESBulkProcessor)
at com.cisco.ise.vcs.crud.VCSCrudProcessor.upsertBulkData(VCSCrudProcessor.java:98)
- locked <0x0000000308461c08> (a com.cisco.ise.vcs.crud.VCSCrudProcessor)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.updateContextRepository(VCSPersistEventHandler.java:147)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.handleEvent(VCSPersistEventHandler.java:113)
at com.cisco.ise.vcs.event.VCSEventHandler.run(VCSEventHandler.java:130)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Because of the above observations we see that you are encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>.
There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
Do let me know if you have any further queries or concerns.
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE - High Load Average for ISE PAN node
ISE - High Load Average for ISE PAN node
timestamp : 2023-02-27T01:52:17.000+0000 || updatedby : rupespat || type : RESOLUTION SUMMARY || visibility : External || details : observations we see that CU is encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>;. There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
======
No response from CU since 9th February 23, closing the case after 3 strike and manager followup | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: SNS-3655-K9/ SNS-3695-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Good day!
I went through the support bundle you provided.
Please find my analysis below:
This device is showing evidence of encountering CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>: Java minimum heap value is to low which can lead to excessive garbage collection
Symptoms seen:
Authentication step latency on multiple policy evaluation steps.
High average request latency during times of peak load.
Authentication request latency does not recover until after the system is reloaded.
Mitigation:
Apply the universal hotfix to all nodes in the deployment and when available apply the patch with the fix for the installed ISE version.
The details of which are mentioned in my previous email to you as well.
Please find the log snippet below:
- ./ise-support-bundle-hsdc-pan-nac01-nusnggk-01-30-2023-23-17/support/showtech/showtech.out - The regex highlighted below detects the iseadminportal service starting with the low java Xms value:
32086: iseadminportal 39346 60.8 4.4 27227720 4319240 Sl Jan 18 7-07:12:48 \_ jsvc.exec -java-home /opt/CSCOcpm/jre -server -user iseadminportal -outfile /opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/logs/catalina.out -errfile /opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/logs/catalina.out -pidfile /var/run/catalina.pid -Xms256m -Xmx21474836480 -XX:MaxGCPauseMillis=500 -XX:MetaspaceSize=512M -XX:MaxMetaspaceSize=512M -XX:MaxDirectMemorySize=2g -XX:+DisableExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/localdisk/corefiles -XX:OnOutOfMemoryError=/opt/CSCOcpm/bin/iseoomrestart.sh -XX:ErrorFile=/localdisk/corefiles/hs_err_pid%p.log -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -verbose:gc -Xloggc:/localdisk/gc/gc_app.log.20230118232240 -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:GCLogFileSize=3M -XX:NumberOfGCLogFiles=31 -XX:+PrintGCApplicationStoppedTime -Dsun.rmi.dgc.client.gcInterval=1800000 -Dsun.rmi.dgc.server.gcInterval=1800000 -Djdk.nio.maxCachedBufferSize=1000000 -Ddisable.logs.transaction=true -DisSSLEnabled=true -Ddb.configurations=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/db.properties -Dlog4j.configuration=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/log4j.xml -Doracle.jms.minSleepTime=200 -Doracle.jms.maxSleepTime=500 -DUSERTYPE_FILTER=NSFEndPointType -Dcom.cisco.cpm.provisioning.filesaverlocation=/tmp/download -Dpdp.heartbeat.cfg=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/pdp_hb_config.xml -Dise.access.map=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/config/access-map.xml -Drbac.superadmin.accesscheck.on=true -Dcom.cisco.cpm.version=3.0.0.458 -Dcom.cisco.cpm.udipid=SNS-3655-K9 -Dcom.cisco.cpm.udivid=A0 -Dcom.cisco.cpm.udisn=WZP23040NF3 -Dcom.cisco.cpm.udipt=UCS -Dcom.cisco.cpm.osversion=3.0.8.091 -DREPLIC_TRANSPORT_TYPE=JGroup -Dfake.pipmgr=true -DnoContextCopy=true -DlicenseSleepTime=24 -Djavax.net.ssl.keyStore=NONE -Djavax.net.ssl.keyStoreType=PKCS11 -Dise.fipsMode=false -Djdk.tls.ephemeralDHKeySize=2048 -Dorg.terracotta.quartz.skipUpdateCheck=true -Dreplication.monitor.on=true -Dorg.owasp.esapi.SecurityConfiguration=org.owasp.esapi.reference.DefaultSecurityConfiguration -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -Dsmack.debugEnabled=true -Dsmack.debuggerClass=org.jivesoftware.smackx.debugger.slf4j.SLF4JSmackDebugger -Djgroups.logging.log_factory_class=com.cisco.epm.logging.CustomLoggerFactoryForJgroups -DsslEnabledProtocolsMediumSecurity=TLSv1,TLSv1.1,TLSv1.2 -DsslEnabledProtocolsHighSecurity=TLSv1.1,TLSv1.2 -Doracle.jdbc.autoCommitSpecCompliant=false -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true -Dorg.jboss.logging.provider=log4j -DMntSessionDirectory.fetchAmount=10000 -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -Dio.netty.allocator.numDirectArenas=0 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=127.0.0.1 -Dcom.sun.management.jmxremote.rmi.port=9999 -Dcom.sun.management.jmxremote.local.only=false -XX:OnError=/usr/bin/sudo /opt/CSCOcpm/bin/isegencore.sh %p -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/conf/logging.properties -Dfile.encoding=UTF-8 -Dorg.terracotta.quartz.skipUpdateCheck=true -Dnet.sf.ehcache.skipUpdateCheck=true -Dorg.quartz.scheduler.skipUpdateCheck=true -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2 -DPROFILER_ROOT=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30 -javaagent:/opt/CSCOcpm/appsrv/apache-tomcat/lib/javaagent.jar -Djava.endorsed.dirs= -classpath /opt/system/java/lib/CARSJava-2.0-api.jar:/opt/system/java/lib/CARSJava-2.0-impl.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/bin/bootstrap.jar:/opt/CSCOcpm/prrt/lib/prrt-interface.jar:/opt/CSCOcpm/prrt/lib/prrt-flowapi.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/lib/log4j-rolling-appender-20131024-2017.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/lib/log4j-1.2.17.jar:/opt/TimesTen/tt1121/lib/ttjdbc6.jar:/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30/bin/tomcat-juli.jar -Dcatalina.base=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30 -Dcatalina.home=/opt/CSCOcpm/appsrv/apache-tomcat-9.0.30 -Djava.io.tmpdir=/opt/CSCOcpm/temp -Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger org.apache.catalina.startup.Bootstrap start
This is a confirmation that you are still hitting the bug CSCwd45843<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbst.cloudapps.cisco.com%2Fbugsearch%2Fbug%2FCSCwd45843&data=05%7C01%7Cgeorgekingsley.paulsundararaj%40ncs.com.sg%7C9e66dfb8dca349ae8ab408daf9b8acd7%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638096868815388131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=c41EUSmTYxeI5W4su6ayOkPnH0BKumDN6gs68zO3GgY%3D&reserved=0>.
The hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsoftware.cisco.com%2Fdownload%2Fhome%2F283801620%2Ftype%2F283802505%2Frelease%2FHP-CSCwd45843&data=05%7C01%7Cgeorgekingsley.paulsundararaj%40ncs.com.sg%7C9e66dfb8dca349ae8ab408daf9b8acd7%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638096868815388131%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=C3zMOOmCfs%2BFFLKXys0s1mPQmal8tOhej1odqqEnOww%3D&reserved=0>.
Please do let me know if you have any further queries or concerns on the same.
Update 25th Jan:
Please find my analysis below:
From the tech top output we see a high CPU is consumed by the jsvc process:
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 12:34:09 up 450 days, 15:44, 2 users, load average: 15.65, 16.77, 17.33
Tasks: 628 total, 1 running, 627 sleeping, 0 stopped, 0 zombie
%Cpu(s): 80.9 us, 1.1 sy, 0.0 ni, 17.6 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13726596 free, 38382248 used, 45327204 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42646812 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80839 iseadmi+ 20 0 30.4g 9.3g 40464 S 1794 10.0 296801:20 jsvc
60426 iseelas+ 20 0 18.0g 16.3g 472868 S 100.0 17.5 71810:49 java
115925 iserabb+ 20 0 2884300 1.0g 2692 S 52.9 1.1 2961:51 beam.smp
3896 root 20 0 164760 2688 1576 R 11.8 0.0 0:00.03 top
1 root 20 0 195436 6776 3108 S 0.0 0.0 402:34.45 systemd
2 root 20 0 0 0 0 S 0.0 0.0 3:30.34 kthreadd
4 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0+
6 root 20 0 0 0 0 S 0.0 0.0 106:27.39 ksoftirqd+
7 root rt 0 0 0 0 S 0.0 0.0 0:50.52 migration+
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root 20 0 0 0 0 S 0.0 0.0 1720:11 rcu_sched
10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 lru-add-d+
11 root rt 0 0 0 0 S 0.0 0.0 2:12.02 watchdog/0
12 root rt 0 0 0 0 S 0.0 0.0 2:15.41 watchdog/1
13 root rt 0 0 0 0 S 0.0 0.0 0:51.29 migration+
14 root 20 0 0 0 0 S 0.0 0.0 87:25.21 ksoftirqd+
On further checking the sub process ID we see the following PIDs are consuming the CPU threads: (Omitted some lined for brevity)
sh-4.2# top -H -p 80839
top - 12:52:56 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1707 total, 18 running, 1689 sleeping, 0 stopped, 0 zombie
%Cpu(s): 64.8 us, 1.6 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13678112 free, 38274636 used, 45483300 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42754628 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80854 iseadmi+ 20 0 30.4g 9.3g 40816 R 72.2 10.0 13611:41 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:51 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:17 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:29 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80850 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:25 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:47 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13613:02 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:11 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:31 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:00 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:45 jsvc
top - 12:52:59 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1710 total, 1 running, 1709 sleeping, 0 stopped, 0 zombie
%Cpu(s): 69.7 us, 0.6 sy, 0.0 ni, 29.4 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13669704 free, 38280428 used, 45485916 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42749708 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80846 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:54 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13611:33 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:11 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:20 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:31 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:14 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:15 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:49 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:04 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:02 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:14 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:29 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:33 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.2 10.0 13611:44 jsvc
top - 12:53:02 up 450 days, 16:03, 6 users, load average: 18.13, 16.74, 16.72
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 67.5 us, 1.1 sy, 0.0 ni, 31.1 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
KiB Mem : 97436048 total, 13651640 free, 38298472 used, 45485936 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42730576 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80850 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.9 10.0 13612:30 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:56 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:22 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:33 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:52 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:16 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:13 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:56 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13613:17 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:32 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:35 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13613:06 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:46 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:36 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:04 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13612:50 jsvc
top - 12:53:05 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 70.4 us, 0.6 sy, 0.0 ni, 28.8 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13647332 free, 38299860 used, 45488856 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42729004 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:54 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:18 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:38 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:16 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:34 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:59 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:25 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:36 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:20 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:09 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:48 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:07 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:59 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:19 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:38 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.2 10.0 13612:19 jsvc
top - 12:53:08 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1712 total, 18 running, 1694 sleeping, 0 stopped, 0 zombie
%Cpu(s): 66.5 us, 1.5 sy, 0.0 ni, 31.6 id, 0.1 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13645540 free, 38302700 used, 45487808 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used. 42726808 avail Mem
From catalina.out we observed the following:
We see the that the following Garbage collector threads are consuming high CPU:
"main" #1 prio=5 os_prio=0 tid=0x0000000002313000 nid=0x13bc7 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"VM Thread" os_prio=0 tid=0x0000000002642000 nid=0x13be2 runnable
"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002325800 nid=0x13bce runnable
"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002327800 nid=0x13bcf runnable
"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x0000000002329000 nid=0x13bd0 runnable
"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x000000000232b000 nid=0x13bd1 runnable
"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x000000000232d000 nid=0x13bd2 runnable
"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x000000000232f000 nid=0x13bd3 runnable
"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x0000000002330800 nid=0x13bd4 runnable
"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x0000000002332800 nid=0x13bd5 runnable
"GC task thread#8 (ParallelGC)" os_prio=0 tid=0x0000000002334800 nid=0x13bd6 runnable
"GC task thread#9 (ParallelGC)" os_prio=0 tid=0x0000000002336000 nid=0x13bd7 runnable
"GC task thread#10 (ParallelGC)" os_prio=0 tid=0x0000000002338000 nid=0x13bd8 runnable
"GC task thread#11 (ParallelGC)" os_prio=0 tid=0x000000000233a000 nid=0x13bd9 runnable
"GC task thread#12 (ParallelGC)" os_prio=0 tid=0x000000000233b800 nid=0x13bda runnable
"GC task thread#13 (ParallelGC)" os_prio=0 tid=0x000000000233d800 nid=0x13bdb runnable
"GC task thread#14 (ParallelGC)" os_prio=0 tid=0x000000000233f800 nid=0x13bdc runnable
"GC task thread#15 (ParallelGC)" os_prio=0 tid=0x0000000002341000 nid=0x13bdd runnable
"GC task thread#16 (ParallelGC)" os_prio=0 tid=0x0000000002343000 nid=0x13bde runnable
"GC task thread#17 (ParallelGC)" os_prio=0 tid=0x0000000002345000 nid=0x13bdf runnable
"VM Periodic Task Thread" os_prio=0 tid=0x0000000002ac3800 nid=0x13cd6 waiting on condition
JNI global references: 3603
Heap
PSYoungGen total 79872K, used 288K [0x0000000635d80000, 0x000000063b280000, 0x00000007e0800000)
eden space 72704K, 0% used [0x0000000635d80000,0x0000000635dc8230,0x000000063a480000)
from space 7168K, 0% used [0x000000063ab80000,0x000000063ab80000,0x000000063b280000)
to space 7168K, 0% used [0x000000063a480000,0x000000063a480000,0x000000063ab80000)
ParOldGen total 2978304K, used 2963138K [0x00000002e0800000, 0x0000000396480000, 0x0000000635d80000)
object space 2978304K, 99% used [0x00000002e0800000,0x00000003955b0b70,0x0000000396480000)
Metaspace used 335348K, capacity 357063K, committed 358016K, reserved 1370112K
class space used 33786K, capacity 37225K, committed 37504K, reserved 1048576K
Garbage collector usage in RHEL: As long as an object is being referenced, the JVM considers it alive. Once an object is no longer referenced and therefore is not reachable by the application code, the garbage collector removes it and reclaims the unused memory. The reason GC is using more CPU cycles is that its aggressively reclaiming a huge amount of Objects which are not referenced anymore.
From the Catalina.out file we could see also the VCS threads being blocked:
"VCSPersistEventHandler-1-thread-1" #1920 prio=5 os_prio=0 tid=0x00007f42c5a27800 nid=0x185d7 waiting for monitor entry [0x00007f4224182000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.elasticsearch.action.bulk.BulkProcessor.internalAdd(BulkProcessor.java:287)
- waiting to lock <0x00000002ef9a1a28> (a org.elasticsearch.action.bulk.BulkProcessor)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:272)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:268)
at com.cisco.ise.vcs.crud.ESBulkProcessor.processRequest(ESBulkProcessor.java:122)
- locked <0x00000002ef51a570> (a com.cisco.ise.vcs.crud.ESBulkProcessor)
at com.cisco.ise.vcs.crud.VCSCrudProcessor.upsertBulkData(VCSCrudProcessor.java:98)
- locked <0x0000000308461c08> (a com.cisco.ise.vcs.crud.VCSCrudProcessor)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.updateContextRepository(VCSPersistEventHandler.java:147)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.handleEvent(VCSPersistEventHandler.java:113)
at com.cisco.ise.vcs.event.VCSEventHandler.run(VCSEventHandler.java:130)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Because of the above observations we see that you are encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>;. There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
Good day!
Thanks for the files you attached so far and I was able to come to a root cause of the issue.
Please find my analysis below:
From the tech top output we see a high CPU is consumed by the jsvc process:
hsdc-pan-nac01/admin# tech top
Invoking tech top.
Press Control-C to interrupt.
top - 12:34:09 up 450 days, 15:44, 2 users, load average: 15.65, 16.77, 17.33
Tasks: 628 total, 1 running, 627 sleeping, 0 stopped, 0 zombie
%Cpu(s): 80.9 us, 1.1 sy, 0.0 ni, 17.6 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13726596 free, 38382248 used, 45327204 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42646812 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80839 iseadmi+ 20 0 30.4g 9.3g 40464 S 1794 10.0 296801:20 jsvc
60426 iseelas+ 20 0 18.0g 16.3g 472868 S 100.0 17.5 71810:49 java
115925 iserabb+ 20 0 2884300 1.0g 2692 S 52.9 1.1 2961:51 beam.smp
3896 root 20 0 164760 2688 1576 R 11.8 0.0 0:00.03 top
1 root 20 0 195436 6776 3108 S 0.0 0.0 402:34.45 systemd
2 root 20 0 0 0 0 S 0.0 0.0 3:30.34 kthreadd
4 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0+
6 root 20 0 0 0 0 S 0.0 0.0 106:27.39 ksoftirqd+
7 root rt 0 0 0 0 S 0.0 0.0 0:50.52 migration+
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root 20 0 0 0 0 S 0.0 0.0 1720:11 rcu_sched
10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 lru-add-d+
11 root rt 0 0 0 0 S 0.0 0.0 2:12.02 watchdog/0
12 root rt 0 0 0 0 S 0.0 0.0 2:15.41 watchdog/1
13 root rt 0 0 0 0 S 0.0 0.0 0:51.29 migration+
14 root 20 0 0 0 0 S 0.0 0.0 87:25.21 ksoftirqd+
On further checking the sub process ID we see the following PIDs are consuming the CPU threads: (Omitted some lined for brevity)
sh-4.2# top -H -p 80839
top - 12:52:56 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1707 total, 18 running, 1689 sleeping, 0 stopped, 0 zombie
%Cpu(s): 64.8 us, 1.6 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13678112 free, 38274636 used, 45483300 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42754628 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80854 iseadmi+ 20 0 30.4g 9.3g 40816 R 72.2 10.0 13611:41 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:51 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:17 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:29 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80850 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:25 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:12 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:47 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13613:02 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:11 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:31 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13611:00 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 40816 R 66.7 10.0 13612:45 jsvc
top - 12:52:59 up 450 days, 16:03, 6 users, load average: 17.88, 16.67, 16.70
Threads: 1710 total, 1 running, 1709 sleeping, 0 stopped, 0 zombie
%Cpu(s): 69.7 us, 0.6 sy, 0.0 ni, 29.4 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13669704 free, 38280428 used, 45485916 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42749708 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80846 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:54 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13611:33 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.9 10.0 13612:11 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:20 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:31 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:14 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:15 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:49 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:04 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13611:02 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13613:14 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:29 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.6 10.0 13612:33 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 40816 S 83.2 10.0 13611:44 jsvc
top - 12:53:02 up 450 days, 16:03, 6 users, load average: 18.13, 16.74, 16.72
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 67.5 us, 1.1 sy, 0.0 ni, 31.1 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
KiB Mem : 97436048 total, 13651640 free, 38298472 used, 45485936 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42730576 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80850 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.9 10.0 13612:30 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:56 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:22 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:33 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:17 jsvc
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:52 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:16 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:13 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13611:56 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13613:17 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:32 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.6 10.0 13612:35 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13613:06 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:46 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:36 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13611:04 jsvc
80858 iseadmi+ 20 0 30.4g 9.3g 41072 R 75.2 10.0 13612:50 jsvc
top - 12:53:05 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1713 total, 18 running, 1695 sleeping, 0 stopped, 0 zombie
%Cpu(s): 70.4 us, 0.6 sy, 0.0 ni, 28.8 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 97436048 total, 13647332 free, 38299860 used, 45488856 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42729004 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
80852 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:54 jsvc
80855 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:18 jsvc
80856 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13611:38 jsvc
80859 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:16 jsvc
80862 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.8 10.0 13612:34 jsvc
80846 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:59 jsvc
80847 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:25 jsvc
80848 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:36 jsvc
80851 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:20 jsvc
80853 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:09 jsvc
80854 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:48 jsvc
80857 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:07 jsvc
80860 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13611:59 jsvc
80861 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13613:19 jsvc
80863 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.5 10.0 13612:38 jsvc
80849 iseadmi+ 20 0 30.4g 9.3g 41072 R 84.2 10.0 13612:19 jsvc
top - 12:53:08 up 450 days, 16:03, 6 users, load average: 18.20, 16.78, 16.74
Threads: 1712 total, 18 running, 1694 sleeping, 0 stopped, 0 zombie
%Cpu(s): 66.5 us, 1.5 sy, 0.0 ni, 31.6 id, 0.1 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem : 97436048 total, 13645540 free, 38302700 used, 45487808 buff/cache
KiB Swap: 8191996 total, 7797512 free, 394484 used.
42726808 avail Mem
From catalina.out we observed the following:
We see the that the following Garbage collector threads are consuming high CPU:
"main" #1 prio=5 os_prio=0 tid=0x0000000002313000 nid=0x13bc7 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"VM Thread" os_prio=0 tid=0x0000000002642000 nid=0x13be2 runnable
"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002325800 nid=0x13bce runnable
"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002327800 nid=0x13bcf runnable
"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x0000000002329000 nid=0x13bd0 runnable
"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x000000000232b000 nid=0x13bd1 runnable
"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x000000000232d000 nid=0x13bd2 runnable
"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x000000000232f000 nid=0x13bd3 runnable
"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x0000000002330800 nid=0x13bd4 runnable
"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x0000000002332800 nid=0x13bd5 runnable
"GC task thread#8 (ParallelGC)" os_prio=0 tid=0x0000000002334800 nid=0x13bd6 runnable
"GC task thread#9 (ParallelGC)" os_prio=0 tid=0x0000000002336000 nid=0x13bd7 runnable
"GC task thread#10 (ParallelGC)" os_prio=0 tid=0x0000000002338000 nid=0x13bd8 runnable
"GC task thread#11 (ParallelGC)" os_prio=0 tid=0x000000000233a000 nid=0x13bd9 runnable
"GC task thread#12 (ParallelGC)" os_prio=0 tid=0x000000000233b800 nid=0x13bda runnable
"GC task thread#13 (ParallelGC)" os_prio=0 tid=0x000000000233d800 nid=0x13bdb runnable
"GC task thread#14 (ParallelGC)" os_prio=0 tid=0x000000000233f800 nid=0x13bdc runnable
"GC task thread#15 (ParallelGC)" os_prio=0 tid=0x0000000002341000 nid=0x13bdd runnable
"GC task thread#16 (ParallelGC)" os_prio=0 tid=0x0000000002343000 nid=0x13bde runnable
"GC task thread#17 (ParallelGC)" os_prio=0 tid=0x0000000002345000 nid=0x13bdf runnable
"VM Periodic Task Thread" os_prio=0 tid=0x0000000002ac3800 nid=0x13cd6 waiting on condition
JNI global references: 3603
Heap
PSYoungGen total 79872K, used 288K [0x0000000635d80000, 0x000000063b280000, 0x00000007e0800000)
eden space 72704K, 0% used [0x0000000635d80000,0x0000000635dc8230,0x000000063a480000)
from space 7168K, 0% used [0x000000063ab80000,0x000000063ab80000,0x000000063b280000)
to space 7168K, 0% used [0x000000063a480000,0x000000063a480000,0x000000063ab80000)
ParOldGen total 2978304K, used 2963138K [0x00000002e0800000, 0x0000000396480000, 0x0000000635d80000)
object space 2978304K, 99% used [0x00000002e0800000,0x00000003955b0b70,0x0000000396480000)
Metaspace used 335348K, capacity 357063K, committed 358016K, reserved 1370112K
class space used 33786K, capacity 37225K, committed 37504K, reserved 1048576K
Garbage collector usage in RHEL: As long as an object is being referenced, the JVM considers it alive.
Once an object is no longer referenced and therefore is not reachable by the application code, the garbage collector removes it and reclaims the unused memory.
The reason GC is using more CPU cycles is that its aggressively reclaiming a huge amount of Objects which are not referenced anymore.
From the Catalina.out file we could see also the VCS threads being blocked:
"VCSPersistEventHandler-1-thread-1" #1920 prio=5 os_prio=0 tid=0x00007f42c5a27800 nid=0x185d7 waiting for monitor entry [0x00007f4224182000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.elasticsearch.action.bulk.BulkProcessor.internalAdd(BulkProcessor.java:287)
- waiting to lock <0x00000002ef9a1a28> (a org.elasticsearch.action.bulk.BulkProcessor)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:272)
at org.elasticsearch.action.bulk.BulkProcessor.add(BulkProcessor.java:268)
at com.cisco.ise.vcs.crud.ESBulkProcessor.processRequest(ESBulkProcessor.java:122)
- locked <0x00000002ef51a570> (a com.cisco.ise.vcs.crud.ESBulkProcessor)
at com.cisco.ise.vcs.crud.VCSCrudProcessor.upsertBulkData(VCSCrudProcessor.java:98)
- locked <0x0000000308461c08> (a com.cisco.ise.vcs.crud.VCSCrudProcessor)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.updateContextRepository(VCSPersistEventHandler.java:147)
at com.cisco.ise.vcs.event.handler.VCSPersistEventHandler.handleEvent(VCSPersistEventHandler.java:113)
at com.cisco.ise.vcs.event.VCSEventHandler.run(VCSEventHandler.java:130)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Because of the above observations we see that you are encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>.
There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
Do let me know if you have any further queries or concerns.
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE - High Load Average for ISE PAN node
ISE - High Load Average for ISE PAN node
timestamp : 2023-02-27T01:52:17.000+0000 || updatedby : rupespat || type : RESOLUTION SUMMARY || visibility : External || details : observations we see that CU is encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>;. There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
======
No response from CU since 9th February 23, closing the case after 3 strike and manager followup | Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE - High Load Average for ISE PAN node | ISE - High Load Average for ISE PAN node | timestamp : 2023-02-27T01:52:17.000+0000 || updatedby : rupespat || type : RESOLUTION SUMMARY || visibility : External || details : observations we see that CU is encountering the bug CSCwd45843<https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843>;. There is a hotfix available for this bug:
https://software.cisco.com/download/home/283801620/type/283802505/release/HP-CSCwd45843
This is a generic HP and can be applied on any version and is available in CCO site, you could install it on all the nodes and monitor.
But we would suggests to install patch 6 first and then install this HP.
This bug is addressed in ISE 3.0 p7 which is yet to be released, until then you can install patch 6 first and then the HP over it.
======
No response from CU since 9th February 23, closing the case after 3 strike and manager followup | nan | SNS-3655-K9 | ise-3.0.0.458.SPA.x86_64.iso | nan | nan | 3 | nan | Configuration Assistance (process not intuitive, too complex, inconsistent...) | CISE | Identity Services Engine (ISE) - 3.0 | ISE Performance (High CPU / Memory / IO / GUI Slowness) | nan | nan | nan | nan | nan | nan |
694068972 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 9.16.2.3/ 9.14.2.4/ 9.14.2.4/ 9.14.1 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Security - Network Firewalls and Intrusion Prevention Systems
Subtechnology: Adaptive Security Appliance (ASA) non-VPN problem
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: FPRUHI
Software Version: N/A
Router/Node Name: N/A
Problem Details: FPR9K-SM-36 Network traffic issue
FPR9K-SM-36 Network traffic issue
timestamp : 2022-12-06T16:39:12.000+0000 || updatedby : dhanukri || type : RESOLUTION SUMMARY || visibility : External || details : Closing the case as there is no response from customer | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: FPR9K-SM-36/ FPR-C9300-AC/ FPR1150-ASA-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Security - Network Firewalls and Intrusion Prevention Systems
Subtechnology: Adaptive Security Appliance (ASA) non-VPN problem
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: FPRUHI
Software Version: N/A
Router/Node Name: N/A
Problem Details: FPR9K-SM-36 Network traffic issue
FPR9K-SM-36 Network traffic issue
timestamp : 2022-12-06T16:39:12.000+0000 || updatedby : dhanukri || type : RESOLUTION SUMMARY || visibility : External || details : Closing the case as there is no response from customer | Technology: Security - Network Firewalls and Intrusion Prevention Systems
Subtechnology: Adaptive Security Appliance (ASA) non-VPN problem
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: FPRUHI
Software Version: N/A
Router/Node Name: N/A
Problem Details: FPR9K-SM-36 Network traffic issue | FPR9K-SM-36 Network traffic issue | timestamp : 2022-12-06T16:39:12.000+0000 || updatedby : dhanukri || type : RESOLUTION SUMMARY || visibility : External || details : Closing the case as there is no response from customer | nan | FPR9K-SM-36 | cisco-asa.9.14.2.4.SPA.csp | nan | nan | 3 | nan | Configuration Assistance (process not intuitive, too complex, inconsistent...) | FPRUHI | Adaptive Security Appliance | ASA Firepower Devices - Non-VPN | nan | nan | nan | nan | nan | nan |
694571397 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 17.03.04a/ 17.3.5/ 2.2.2.8 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - LAN Automation (SDA)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - LAN Automation (SDA)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose
Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose
timestamp : 2022-12-30T13:30:48.000+0000 || updatedby : agarroab || type : RESOLUTION SUMMARY || visibility : External || details : There are CRC errors in line interface card
After the card was replaced, there are no more CRC errors.
Faulty card returned successfully. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: ASR1009-X Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - LAN Automation (SDA)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose
Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose
timestamp : 2022-12-30T13:30:48.000+0000 || updatedby : agarroab || type : RESOLUTION SUMMARY || visibility : External || details : There are CRC errors in line interface card
After the card was replaced, there are no more CRC errors.
Faulty card returned successfully. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - LAN Automation (SDA)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose | Hi,
we have observer this issue before and last time after change the SFP the issue was resolved. Please check the SR 693710312 & 694133288. however this time we have change the SFP and Fiber cable as well still the CRC is coming.
I am attaching the logs on testing time.
Device info:
ASR1009-X
Cisco IOS XE Software, Version 17.03.04a
Note: now we administrator shut the port.
Thanks,
Emrose | timestamp : 2022-12-30T13:30:48.000+0000 || updatedby : agarroab || type : RESOLUTION SUMMARY || visibility : External || details : There are CRC errors in line interface card
After the card was replaced, there are no more CRC errors.
Faulty card returned successfully. | nan | ASR1009-X | asr1000rpx86-universalk9.17.03.04a.SPA.bin | nan | nan | 3 | nan | Hardware Failure | ASR1000 | Cisco DNA Center - On-Prem | Cisco DNA Center - LAN Automation (SDA) | nan | nan | nan | nan | nan | nan |
694925542 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Software Version: -- => 16.12.1s
Technology: LAN Switching
Subtechnology: Cat3850 - Switching Issues
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: C9300 SDA FE - %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 1 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 1 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.537 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 7 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.537 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 7 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.508 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 6 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.509 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 6 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.505 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.506 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 4 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.544 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 3 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.544 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 3 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 2 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 2 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.510 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 5 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.510 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 5 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.522 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 8 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.523 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 8 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
C9300 SDA FE - %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 1 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 1 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.537 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 7 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.537 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 7 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.508 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 6 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.509 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 6 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.505 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.506 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 4 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.544 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 3 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.544 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 3 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 2 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 2 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.510 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 5 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.510 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 5 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.522 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 8 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.523 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 8 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
timestamp : 2023-02-14T13:36:10.000+0000 || updatedby : jasterry || type : RESOLUTION SUMMARY || visibility : External || details : Customer stopped responding. Believe that there is an issue with Arp traffic being programmed correctly. closed with 3 strike | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat3850 - Switching Issues
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: C9300 SDA FE - %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 1 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 1 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.537 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 7 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.537 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 7 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.508 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 6 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.509 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 6 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.505 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.506 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 4 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.544 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 3 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.544 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 3 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 2 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 2 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.510 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 5 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.510 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 5 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.522 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 8 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.523 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 8 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
C9300 SDA FE - %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 1 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 1 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.537 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 7 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.537 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 7 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.508 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 6 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.509 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 6 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.505 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.506 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 4 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.544 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 3 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.544 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 3 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 2 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 2 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.510 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 5 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.510 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 5 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.522 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 8 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.523 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 8 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
timestamp : 2023-02-14T13:36:10.000+0000 || updatedby : jasterry || type : RESOLUTION SUMMARY || visibility : External || details : Customer stopped responding. Believe that there is an issue with Arp traffic being programmed correctly. closed with 3 strike | Technology: LAN Switching
Subtechnology: Cat3850 - Switching Issues
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: C9300 SDA FE - %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 1 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 1 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.537 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 7 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.537 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 7 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.508 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 6 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.509 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 6 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.505 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.506 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 4 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.544 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 3 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.544 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 3 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 2 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 2 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.510 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 5 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.510 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 5 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.522 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 8 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.523 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 8 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed | C9300 SDA FE - %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 1 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 1 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.537 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 7 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.537 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 7 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.508 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 6 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.509 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 6 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.505 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.506 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 4 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.544 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 3 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.544 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 3 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.547 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 2 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.548 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 2 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.510 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 5 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.510 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 5 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed
Jan 19 2023 09:06:16.522 SGT: %FED_L3_ERRMSG-3-RSRC_ERR: Switch 8 R0/0: fed: Failed to allocate hardware resource for adj entry - rc:1
Jan 19 2023 09:06:16.523 SGT: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch 8 R0/0: fman_fp_image: adj 0x125c5, Flags Midchain download to DP failed | timestamp : 2023-02-14T13:36:10.000+0000 || updatedby : jasterry || type : RESOLUTION SUMMARY || visibility : External || details : Customer stopped responding. Believe that there is an issue with Arp traffic being programmed correctly. closed with 3 strike | nan | C9300-48U | cat9k_iosxe.17.06.02.SPA.bin | nan | nan | 3 | nan | Software -not a bug (scalability, version selection, install/upgrade help...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | nan | nan | nan | nan | nan | nan |
694935054 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
* After doing internal research, it seems you are hitting bug "CSCvy37953." This bug is only for CoS Ap's.
* This bug is fixed in 8.10MR7 as per developers, and it should also be fixed in 8.10.183.0.
* As you are already planning to go to 8.10.183.0, which is also the TAC recommended code, you can safely upgrade the WLC, which should fix our current issue.
Thank you for your time on Webex today.
Analysis from the logs:
We observe below error logs on the ap:
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0202] 2023-02-03 12:24:55 Application has no active session to process TAMC_CMD_RSA_PRIVATE_ENCR
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0215] 1957087432:error:14099006:lib(20):func(153):reason(6):NA:0:
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0215] dtls_process_packet: Error connecting TLS context
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0216] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.190.103]:5256(0)--[172.18.240.25]:5246(0) [10.253.190.103]:5256--[172.18.240.25]:5246
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0216] wtpDtlsCallback: DTLS-Ctrl Connection 0x55ec2a00 closed
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0216] dtls_free_connection: Free done...
for connection 0x55ec2a00
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0220] dtls_connectionDB_del_connection: Deleted Connection 0x55ec2a00, Server [172.18.240.25]:5246, Client [10.253.190.103]:5256, Count 0, rc_return 2
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0220]
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0220] DTLS: Error while processing DTLS packet 0x55f35000.
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0003] CAPWAP State: DTLS Setup
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0010] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00ac] ClientHello
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] dtls_connectionDB_add_connection: Added Connection 0x54aaea00 Server [172.18.240.26]:5246 Client [10.253.159.139]:5256
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] create_dtls_connection: Creating DTLS Ctrl Connection 0x54aaea00
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0012] DTLS connection created sucessfully local_ip: 10.253.159.139 local_port: 5256 peer_ip: 172.18.240.26 peer_port: 5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0022] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.159.139]:5256(0)--[172.18.240.26]:5246(0) [10.253.159.139]:5256--[172.18.240.26]:5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0022] dtls_connection_find_using_link_info: Searching connection [10.253.159.139]:5256--[172.18.240.26]:5246, result 0x54aaea00
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0023] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0023] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 002f] HelloVerifyRequest
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0024] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0024] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00cc] ClientHello
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0025] dtls_process_packet: SSL get error rc 5
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0031] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.159.139]:5256(0)--[172.18.240.26]:5246(0) [10.253.159.139]:5256--[172.18.240.26]:5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0032] dtls_connection_find_using_link_info: Searching connection [10.253.159.139]:5256--[172.18.240.26]:5246, result 0x54aaea00
* When AP wants to join a WLC, it will send a discovery message to known WLCs and wait for their response.
After that, it does a DTLS handshake where it exchanges certificates, and the AP and WLC go through the joining process, with the AP successfully joining the WLC.
* In our case, Ap is going through the discovery process and establishing the handshake, but the certificates are not being exchanged and showing the error "dtls_process_packet: SSL get error RC5".
* But after rebooting the AP, it is establishing the connection and joining the WLC successfully.
* After doing internal research, it seems you are hitting bug "CSCvy37953." This bug is only for CoS Ap's.
* This bug is fixed in 8.10MR7 as per developers, and it should also be fixed in 8.10.183.0.
* As you are already planning to go to 8.10.183.0, which is also the TAC recommended code, you can safely upgrade the WLC, which should fix our current issue.
Feel free to mail me for any queries.
I hope you are doing well.
After a lot of internal research, I found similar cases, and the issue was fixed after upgrading the WLC to 8.10.171.0.
I suggest you please upgrade the WL to 8.10.171.0.
What are the reasons reflected on the logs for unstable DTLS sessions.
Please share an ETA for analysis.
Did you checked the certificate issue while AP joining.
Please understand the urgency here as we are in middle of 8.10.183.0 adoption and every day new issues are making us unconfident about the same.
Also please share the hierarchy for further escalations as I cant see your manager email address in your Cisco signatures.
Thank you for your time on Webex today.
Wlc – 8540
Ap’s – 2802i
Code – 8.10.161.0
Ap’s are disconnecting from the network intermittently.
Four problematic APs are connected to the same switch.
From support bundle:
Jan 266 16:43:38 kernel: [*01/26/2023 16:43:38.2076] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=165, NumofPendingMsgs=10
Jan 26 16:43:38 kernel: [*01/26/2023 16:43:38.2076]
Jan 26 16:43:41 kernel: [*01/26/2023 16:43:41.0587] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=165, NumofPendingMsgs=10
Jan 26 16:43:41 kernel: [*01/26/2023 16:43:41.0587] Jan 26 16:43:43 kernel: [*01/26/2023 16:43:43.9100] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=165, NumofPendingMsgs=10
Jan 26 16:43:43 kernel: [*01/26/2023 16:43:43.9100] Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7607] Max retransmission count exceeded, going back to DISCOVER mode.
J
Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7610] GOING BACK TO DISCOVER MODE
Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7889]
Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7890] CAPWAP State: DTLS Teardown
* I see AP is sending "keep alive" packets to the WLC, but it didn't get any response back.
As AP has not received any response back from the WLC, it has disconnected from it and gone into discovery mode again.
* As shown below, after 27 seconds, AP has rejoined the WLC (TLDC-WLC1).
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.0003] CAPWAP State: DTLS Setup
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7718]
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7718] CAPWAP State: Join
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7751] Sending Join request to 172.18.240.25 through port 5264
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7899] Join Response from 172.18.240.25
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7899] AC accepted join request with result code: 0
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.8030] Received wlcType 0, timer 30
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9319]
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9319] CAPWAP State: Image Data
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9323] AP image version 8.10.162.0 backup 8.10.181.4, Controller 8.10.162.0
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9323] Version is the same, do not need update.
Jan 26 16:44:13 upgrade: Script called with args:[NO_UPGRADE]
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9606] upgrade.sh: Script called with args:[NO_UPGRADE]
Jan 26 16:44:14 kernel: [*01/26/2023 16:44:14.0186] do NO_UPGRADE, part1 is active part
Jan 26 16:44:14 kernel: [*01/26/2023 16:44:14.0290]
Jan 26 16:44:14 kernel: [*01/26/2023 16:44:14.0290] CAPWAP State: Configure
Jan 26 16:44:14 syslog: Check lagloadbalance setting flex mode 0 cfg 0 linkstate 0 ap_type 56
Jan 26 16:44:15 kernel: [*01/26/2023 16:44:15.2540] DOT11_CFG[1]: Starting radio 1
Jan 26 16:44:15 kernel: [*01/26/2023 16:44:15.8898] 1:change to DFS channel 64, CAC for 60 seconds.
Jan 26 16:44:15 kernel: [*01/26/2023 16:44:15.9449] DOT11_DRV[1]: Started Radio 1
Jan 26 16:44:17 kernel: [*01/26/2023 16:44:17.3088] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jan 26 16:44:17 kernel: [*01/26/2023 16:44:17.3089] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jan 26 16:44:17 kernel: [*01/26/2023 16:44:17.3089] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jan 26 16:44:18 kernel: [*01/26/2023 16:44:18.7411] Null cert id for TLV_AP_CACERTS_CONFIG_PAYLOAD
Jan 26 16:44:20 kernel: [*01/26/2023 16:44:20.1457]
Jan 26 16:44:20 kernel: [*01/26/2023 16:44:20.1457] CAPWAP State: Run
Jan 26 16:44:20 kernel: [*01/26/2023 16:44:20.1940] AP has joined controller TLDC-WLC1
* Again after 4 mins, ap disconnected from the wlc again as it didn’t get any keep-alive response.
Jan 26 16:48:27 kernel: [*01/26/2023 16:48:27.5214] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=101, NumofPendingMsgs=15
Jan 26 16:48:27 kernel: [*01/26/2023 16:48:27.5214]
Jan 26 16:48:30 kernel: [*01/26/2023 16:48:30.3725] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=101, NumofPendingMsgs=15
Jan 26 16:48:30 kernel: [*01/26/2023 16:48:30.3725]
Jan 26 16:48:33 kernel: [*01/26/2023 16:48:33.2237] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=101, NumofPendingMsgs=15
Jan 26 16:48:33 kernel: [*01/26/2023 16:48:33.2237]
Jan 26 16:48:36 kernel: [*01/26/2023 16:48:36.0745] Max retransmission count exceeded, going back to DISCOVER mode.
* The max retransmission is most likely the keep-alives once the DTLS connection is established with the WLC.
Once these heartbeats are not talking two-way, the AP/WLC will both complain that the AP has reached max transmissions.
The WLC will remove the AP entry and the AP will re-start the discovery/join process.
* If ap and wlc are in 2 different locations, there must have been brief period of network latency between ap and wlc that caused aps to disassociate from wlc.
* Please increase the retransmission parameters from the gui > wireless > global configuration > AP Retransmit Config Parameters > Ap retransmit count – 8 and interval – 5
* We need to check if the WLC is getting these keep-alive packets or not.
If yes, we need to check if it is responding back or not.
Enter the following commands when the problem occurs again:
From wlc:
* Debug mac addr <Base Radio MAC of the AP>
* Debug mac addr <ethernet mac of the AP>
* Debug capwap dtls-keepalive enable
From ap:
* Debug capwap client keepalive enable
Run these commands for some time until the disassociation happens again, then disable the debugging with "debug disable-all."
* Even after WLC responds, if AP didn’t receive it, we need to check where the drop is as the response is not reaching AP.
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: AP's in central library are facing issues joining back to WLC
AP's in central library are facing issues joining back to WLC
timestamp : 2023-02-28T01:04:20.000+0000 || updatedby : sherholm || type : RESOLUTION SUMMARY || visibility : External || details : Standby SR monitored till customer requested closure date. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Thank you for your time on Webex today.
Analysis from the logs:
We observe below error logs on the ap:
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0202] 2023-02-03 12:24:55 Application has no active session to process TAMC_CMD_RSA_PRIVATE_ENCR
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0215] 1957087432:error:14099006:lib(20):func(153):reason(6):NA:0:
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0215] dtls_process_packet: Error connecting TLS context
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0216] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.190.103]:5256(0)--[172.18.240.25]:5246(0) [10.253.190.103]:5256--[172.18.240.25]:5246
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0216] wtpDtlsCallback: DTLS-Ctrl Connection 0x55ec2a00 closed
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0216] dtls_free_connection: Free done...
for connection 0x55ec2a00
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0220] dtls_connectionDB_del_connection: Deleted Connection 0x55ec2a00, Server [172.18.240.25]:5246, Client [10.253.190.103]:5256, Count 0, rc_return 2
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0220]
Feb 3 12:24:55 kernel: [*02/03/2023 12:24:55.0220] DTLS: Error while processing DTLS packet 0x55f35000.
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0003] CAPWAP State: DTLS Setup
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0010] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00ac] ClientHello
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] dtls_connectionDB_add_connection: Added Connection 0x54aaea00 Server [172.18.240.26]:5246 Client [10.253.159.139]:5256
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0011] create_dtls_connection: Creating DTLS Ctrl Connection 0x54aaea00
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0012] DTLS connection created sucessfully local_ip: 10.253.159.139 local_port: 5256 peer_ip: 172.18.240.26 peer_port: 5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0022] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.159.139]:5256(0)--[172.18.240.26]:5246(0) [10.253.159.139]:5256--[172.18.240.26]:5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0022] dtls_connection_find_using_link_info: Searching connection [10.253.159.139]:5256--[172.18.240.26]:5246, result 0x54aaea00
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0023] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0023] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 002f] HelloVerifyRequest
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0024] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0024] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00cc] ClientHello
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0025] dtls_process_packet: SSL get error rc 5
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0031] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.253.159.139]:5256(0)--[172.18.240.26]:5246(0) [10.253.159.139]:5256--[172.18.240.26]:5246
Feb 2 21:07:49 kernel: [*02/02/2023 21:07:49.0032] dtls_connection_find_using_link_info: Searching connection [10.253.159.139]:5256--[172.18.240.26]:5246, result 0x54aaea00
* When AP wants to join a WLC, it will send a discovery message to known WLCs and wait for their response.
After that, it does a DTLS handshake where it exchanges certificates, and the AP and WLC go through the joining process, with the AP successfully joining the WLC.
* In our case, Ap is going through the discovery process and establishing the handshake, but the certificates are not being exchanged and showing the error "dtls_process_packet: SSL get error RC5".
* But after rebooting the AP, it is establishing the connection and joining the WLC successfully.
* After doing internal research, it seems you are hitting bug "CSCvy37953." This bug is only for CoS Ap's.
* This bug is fixed in 8.10MR7 as per developers, and it should also be fixed in 8.10.183.0.
* As you are already planning to go to 8.10.183.0, which is also the TAC recommended code, you can safely upgrade the WLC, which should fix our current issue.
Feel free to mail me for any queries.
Thank you for your time on Webex today.
Wlc – 8540
Ap’s – 2802i
Code – 8.10.161.0
Ap’s are disconnecting from the network intermittently.
Four problematic APs are connected to the same switch.
From support bundle:
Jan 266 16:43:38 kernel: [*01/26/2023 16:43:38.2076] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=165, NumofPendingMsgs=10
Jan 26 16:43:38 kernel: [*01/26/2023 16:43:38.2076]
Jan 26 16:43:41 kernel: [*01/26/2023 16:43:41.0587] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=165, NumofPendingMsgs=10
Jan 26 16:43:41 kernel: [*01/26/2023 16:43:41.0587] Jan 26 16:43:43 kernel: [*01/26/2023 16:43:43.9100] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=165, NumofPendingMsgs=10
Jan 26 16:43:43 kernel: [*01/26/2023 16:43:43.9100] Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7607] Max retransmission count exceeded, going back to DISCOVER mode.
J
Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7610] GOING BACK TO DISCOVER MODE
Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7889]
Jan 26 16:43:46 kernel: [*01/26/2023 16:43:46.7890] CAPWAP State: DTLS Teardown
* I see AP is sending "keep alive" packets to the WLC, but it didn't get any response back.
As AP has not received any response back from the WLC, it has disconnected from it and gone into discovery mode again.
* As shown below, after 27 seconds, AP has rejoined the WLC (TLDC-WLC1).
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.0003] CAPWAP State: DTLS Setup
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7718]
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7718] CAPWAP State: Join
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7751] Sending Join request to 172.18.240.25 through port 5264
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7899] Join Response from 172.18.240.25
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.7899] AC accepted join request with result code: 0
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.8030] Received wlcType 0, timer 30
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9319]
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9319] CAPWAP State: Image Data
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9323] AP image version 8.10.162.0 backup 8.10.181.4, Controller 8.10.162.0
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9323] Version is the same, do not need update.
Jan 26 16:44:13 upgrade: Script called with args:[NO_UPGRADE]
Jan 26 16:44:13 kernel: [*01/26/2023 16:44:13.9606] upgrade.sh: Script called with args:[NO_UPGRADE]
Jan 26 16:44:14 kernel: [*01/26/2023 16:44:14.0186] do NO_UPGRADE, part1 is active part
Jan 26 16:44:14 kernel: [*01/26/2023 16:44:14.0290]
Jan 26 16:44:14 kernel: [*01/26/2023 16:44:14.0290] CAPWAP State: Configure
Jan 26 16:44:14 syslog: Check lagloadbalance setting flex mode 0 cfg 0 linkstate 0 ap_type 56
Jan 26 16:44:15 kernel: [*01/26/2023 16:44:15.2540] DOT11_CFG[1]: Starting radio 1
Jan 26 16:44:15 kernel: [*01/26/2023 16:44:15.8898] 1:change to DFS channel 64, CAC for 60 seconds.
Jan 26 16:44:15 kernel: [*01/26/2023 16:44:15.9449] DOT11_DRV[1]: Started Radio 1
Jan 26 16:44:17 kernel: [*01/26/2023 16:44:17.3088] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jan 26 16:44:17 kernel: [*01/26/2023 16:44:17.3089] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jan 26 16:44:17 kernel: [*01/26/2023 16:44:17.3089] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jan 26 16:44:18 kernel: [*01/26/2023 16:44:18.7411] Null cert id for TLV_AP_CACERTS_CONFIG_PAYLOAD
Jan 26 16:44:20 kernel: [*01/26/2023 16:44:20.1457]
Jan 26 16:44:20 kernel: [*01/26/2023 16:44:20.1457] CAPWAP State: Run
Jan 26 16:44:20 kernel: [*01/26/2023 16:44:20.1940] AP has joined controller TLDC-WLC1
* Again after 4 mins, ap disconnected from the wlc again as it didn’t get any keep-alive response.
Jan 26 16:48:27 kernel: [*01/26/2023 16:48:27.5214] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=101, NumofPendingMsgs=15
Jan 26 16:48:27 kernel: [*01/26/2023 16:48:27.5214]
Jan 26 16:48:30 kernel: [*01/26/2023 16:48:30.3725] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=101, NumofPendingMsgs=15
Jan 26 16:48:30 kernel: [*01/26/2023 16:48:30.3725]
Jan 26 16:48:33 kernel: [*01/26/2023 16:48:33.2237] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=101, NumofPendingMsgs=15
Jan 26 16:48:33 kernel: [*01/26/2023 16:48:33.2237]
Jan 26 16:48:36 kernel: [*01/26/2023 16:48:36.0745] Max retransmission count exceeded, going back to DISCOVER mode.
* The max retransmission is most likely the keep-alives once the DTLS connection is established with the WLC.
Once these heartbeats are not talking two-way, the AP/WLC will both complain that the AP has reached max transmissions.
The WLC will remove the AP entry and the AP will re-start the discovery/join process.
* If ap and wlc are in 2 different locations, there must have been brief period of network latency between ap and wlc that caused aps to disassociate from wlc.
* Please increase the retransmission parameters from the gui > wireless > global configuration > AP Retransmit Config Parameters > Ap retransmit count – 8 and interval – 5
* We need to check if the WLC is getting these keep-alive packets or not.
If yes, we need to check if it is responding back or not.
Enter the following commands when the problem occurs again:
From wlc:
* Debug mac addr <Base Radio MAC of the AP>
* Debug mac addr <ethernet mac of the AP>
* Debug capwap dtls-keepalive enable
From ap:
* Debug capwap client keepalive enable
Run these commands for some time until the disassociation happens again, then disable the debugging with "debug disable-all."
* Even after WLC responds, if AP didn’t receive it, we need to check where the drop is as the response is not reaching AP.
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: AP's in central library are facing issues joining back to WLC
AP's in central library are facing issues joining back to WLC
timestamp : 2023-02-28T01:04:20.000+0000 || updatedby : sherholm || type : RESOLUTION SUMMARY || visibility : External || details : Standby SR monitored till customer requested closure date. | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: AP's in central library are facing issues joining back to WLC | AP's in central library are facing issues joining back to WLC | timestamp : 2023-02-28T01:04:20.000+0000 || updatedby : sherholm || type : RESOLUTION SUMMARY || visibility : External || details : Standby SR monitored till customer requested closure date. | nan | THIRD_PARTY_PRODUCT_HW | THIRD_PARTY_PRODUCT_SW | nan | nan | 3 | nan | Software -not a bug (scalability, version selection, install/upgrade help...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | nan | nan | nan | nan | nan | nan |
695268540 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
resolved issue
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication
This observed on switches upgraded from 16.12.4 to 17.6.4.
Though the radius status is UP, but Platform State from SMD is DEAD (for both radius/aaa servers)
IT-03-CNT-ES3#show aaa servers | inc auth-port|State|SMD
RADIUS: id 1, priority 1, host 172.19.208.9, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.9
State: current UP, duration 646545s, previous duration 14s
Platform State from SMD: current DEAD, duration 0s, previous duration 102s
SMD Platform Dead: total time 184899s, count 6970
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 56, current 0 total 967
SMD Platform : max 272, current 2 total 33225
RADIUS: id 2, priority 2, host 172.19.208.25, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.25
State: current UP, duration 646540s, previous duration 20s
Platform State from SMD: current DEAD, duration 132s, previous duration 181s
SMD Platform Dead: total time 456112s, count 2735
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 29, current 1 total 5330
SMD Platform : max 140, current 6 total 28472
SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication
This observed on switches upgraded from 16.12.4 to 17.6.4.
Though the radius status is UP, but Platform State from SMD is DEAD (for both radius/aaa servers)
IT-03-CNT-ES3#show aaa servers | inc auth-port|State|SMD
RADIUS: id 1, priority 1, host 172.19.208.9, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.9
State: current UP, duration 646545s, previous duration 14s
Platform State from SMD: current DEAD, duration 0s, previous duration 102s
SMD Platform Dead: total time 184899s, count 6970
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 56, current 0 total 967
SMD Platform : max 272, current 2 total 33225
RADIUS: id 2, priority 2, host 172.19.208.25, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.25
State: current UP, duration 646540s, previous duration 20s
Platform State from SMD: current DEAD, duration 132s, previous duration 181s
SMD Platform Dead: total time 456112s, count 2735
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 29, current 1 total 5330
SMD Platform : max 140, current 6 total 28472
resolved issue | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication
This observed on switches upgraded from 16.12.4 to 17.6.4.
Though the radius status is UP, but Platform State from SMD is DEAD (for both radius/aaa servers)
IT-03-CNT-ES3#show aaa servers | inc auth-port|State|SMD
RADIUS: id 1, priority 1, host 172.19.208.9, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.9
State: current UP, duration 646545s, previous duration 14s
Platform State from SMD: current DEAD, duration 0s, previous duration 102s
SMD Platform Dead: total time 184899s, count 6970
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 56, current 0 total 967
SMD Platform : max 272, current 2 total 33225
RADIUS: id 2, priority 2, host 172.19.208.25, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.25
State: current UP, duration 646540s, previous duration 20s
Platform State from SMD: current DEAD, duration 132s, previous duration 181s
SMD Platform Dead: total time 456112s, count 2735
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 29, current 1 total 5330
SMD Platform : max 140, current 6 total 28472
SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication
This observed on switches upgraded from 16.12.4 to 17.6.4.
Though the radius status is UP, but Platform State from SMD is DEAD (for both radius/aaa servers)
IT-03-CNT-ES3#show aaa servers | inc auth-port|State|SMD
RADIUS: id 1, priority 1, host 172.19.208.9, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.9
State: current UP, duration 646545s, previous duration 14s
Platform State from SMD: current DEAD, duration 0s, previous duration 102s
SMD Platform Dead: total time 184899s, count 6970
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 56, current 0 total 967
SMD Platform : max 272, current 2 total 33225
RADIUS: id 2, priority 2, host 172.19.208.25, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.25
State: current UP, duration 646540s, previous duration 20s
Platform State from SMD: current DEAD, duration 132s, previous duration 181s
SMD Platform Dead: total time 456112s, count 2735
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 29, current 1 total 5330
SMD Platform : max 140, current 6 total 28472
resolved issue | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication
This observed on switches upgraded from 16.12.4 to 17.6.4.
Though the radius status is UP, but Platform State from SMD is DEAD (for both radius/aaa servers)
IT-03-CNT-ES3#show aaa servers | inc auth-port|State|SMD
RADIUS: id 1, priority 1, host 172.19.208.9, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.9
State: current UP, duration 646545s, previous duration 14s
Platform State from SMD: current DEAD, duration 0s, previous duration 102s
SMD Platform Dead: total time 184899s, count 6970
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 56, current 0 total 967
SMD Platform : max 272, current 2 total 33225
RADIUS: id 2, priority 2, host 172.19.208.25, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.25
State: current UP, duration 646540s, previous duration 20s
Platform State from SMD: current DEAD, duration 132s, previous duration 181s
SMD Platform Dead: total time 456112s, count 2735
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 29, current 1 total 5330
SMD Platform : max 140, current 6 total 28472 | SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication
This observed on switches upgraded from 16.12.4 to 17.6.4.
Though the radius status is UP, but Platform State from SMD is DEAD (for both radius/aaa servers)
IT-03-CNT-ES3#show aaa servers | inc auth-port|State|SMD
RADIUS: id 1, priority 1, host 172.19.208.9, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.9
State: current UP, duration 646545s, previous duration 14s
Platform State from SMD: current DEAD, duration 0s, previous duration 102s
SMD Platform Dead: total time 184899s, count 6970
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 56, current 0 total 967
SMD Platform : max 272, current 2 total 33225
RADIUS: id 2, priority 2, host 172.19.208.25, auth-port 1812, acct-port 1813, hostname dnac-radius_172.19.208.25
State: current UP, duration 646540s, previous duration 20s
Platform State from SMD: current DEAD, duration 132s, previous duration 181s
SMD Platform Dead: total time 456112s, count 2735
Platform State from WNCD (1) : current UP
Platform State from WNCD (2) : current UP
Platform State from WNCD (3) : current UP
Platform State from WNCD (4) : current UP
Platform State from WNCD (5) : current UP
Platform State from WNCD (6) : current UP
Platform State from WNCD (7) : current UP
Platform State from WNCD (8) : current UP, duration 0s, previous duration 0s
SMD Platform : max 29, current 1 total 5330
SMD Platform : max 140, current 6 total 28472 | resolved issue | SDA Fabric Edge - Intermittent AAA Server Down status impacting user/device authentication | C9300-48U-A | 17.6.4 | 17.6.4 | 59.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | 01t6R000006k8XpQAI | Error Messages, Logs, Debugs | Cisco Software-Defined Access (SDA Wired) | Cisco DNA Center - On-Prem | 01t15000005W0LTAA0 | nan |
694952109 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
From: [email protected]
To: "Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)" <[email protected]>,Dubey Satyam <[email protected]>,"Karthikeyan Muthu (karmuth2)" <[email protected]>,"[email protected]" <[email protected]>
Cc: "Mohamed Issam Niyamathullah (NCS)" <[email protected]>,"Alejo Jay Mark Arcilia (NCS)" <[email protected]>,"Tan Wei Heng (NCS)" <[email protected]>,CCE Wipro NET <[email protected]>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Karanam.
Thank you.
Hi Satyam,
Do u need anything else? If not I will proceed to close this case. Thank You.
Best,
VJ
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]>
Sent: Tuesday, 7 February 2023 12:49 pm
To: VJ Vijayadas (NCS) <[email protected]>; Dubey Satyam <[email protected]>; Karthikeyan Muthu (karmuth2) <[email protected]>; [email protected]
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]>; Alejo Jay Mark Arcilia (NCS) <[email protected]>; Tan Wei Heng (NCS) <[email protected]>; CCE Wipro NET <[email protected]>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
Good day,
Please find reasons for disconnections for SDA and Non SDA environment.
CO_CLIENT_DELETE_REASON_SESSION_TIMEOUT > Session timeout> Client is deleted due to session time out. Time out occurs because of termination when no user is responding or answering.
CO_CLIENT_DELETE_REASON_IDLE_TIMEOUT> Idle timeout> Client is deleted due to session idle time out . Session time out occurs because idle time out occurs at Client not responding.
If any querys/ Issues please feel free to reach back to us.
Have a great day 😊
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cisco.com%2Fweb%2Fabout%2Fdoing_business%2Flegal%2Fcri%2Findex.html&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TMO4VFLd8NpyrIoufRJTS758%2BSb7nFceexhguMMSMvE%3D&reserved=0> for Company Registration Information.
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: 06 February 2023 11:34
To: Dubey Satyam <[email protected]<mailto:[email protected]>>; Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Karnam,
Could you share the delete reasons known from such issues for sda and non sda client connectivity environment?
Best,
VJ
From: Dubey Satyam <[email protected]<mailto:[email protected]>>
Sent: Monday, 6 February 2023 1:59 pm
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
We have got the clarity on the case to adjust session timeout. We are into discussion for adoption of this workaround.
My ask on last call was to share the delete reasons known from such issues for sda and non sda client connectivity environment.
This is still pending from Karnam. Once this info is provided. Please proceed with closure.
Regards,
Satyam Dubey | National University of Singapore | Architecture & Operations |
Desk Phone: (+65)-81506893| Email: [email protected]<mailto:[email protected]>
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: Monday, 6 February 2023 11:29 am
To: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
- External Email -
Hi Satyam,
Do you require any other assistance regarding this case? if not, we will proceed to close this ticket. Thank You.
Best,
VJ
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>
Sent: Monday, 6 February 2023 10:38 am
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
Good day,
I hope you are doing great,
Can I know is there any assistance required on this case?
If any queries/ Issues please feel free to reach back to us.
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ssgFp7%2FUAWmtzhqAeXThl3oV2c4Dl4%2Bhdu%2Fromfc5Aw%3D&reserved=0> for Company Registration Information.
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)
Sent: 02 February 2023 08:03
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
HI VJ,
Good day,
Thanks for your time over call,
Please find call summary,
As per discussion over call, Session time out should be configured to 84000 seconds and 3600 idle time out.
Current configuration 7200 is minimum session time out time,
Please update Session time out and idle time out as per best practice.
Attached link for reference:
Cisco Wireless LAN Controller (WLC) Configuration Best Practices - Cisco<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttps%25253A%25252F%25252Fwww.cisco.com%25252Fc%25252Fen%25252Fus%25252Ftd%25252Fdocs%25252Fwireless%25252Fcontroller%25252Ftechnotes%25252F8-6%25252Fb_Cisco_Wireless_LAN_Controller_Configuration_Best_Practices.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253dbl61KB9krPuB2HovEcBPPtq%25252BrKu3hTzZjT3fedcDQDA%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-4d77f7350e6280d16e1161e378aa6a914f848465&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r43FOFLAqMfGwHxsum76UZeaZhSING1KWqVbfMh%2F8k4%3D&reserved=0>
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ssgFp7%2FUAWmtzhqAeXThl3oV2c4Dl4%2Bhdu%2Fromfc5Aw%3D&reserved=0> for Company Registration Information.
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)
Sent: 01 February 2023 10:15
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
HI VJ,
Good day,
Please join the session.
https://cisco.webex.com/ciscosales/j.php?MTID=m2cc007e651c8ae9736187f43fc025c18<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttps%25253A%25252F%25252Fcisco.webex.com%25252Fciscosales%25252Fj.php%25253FMTID%25253Dm2cc007e651c8ae9736187f43fc025c18%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253dHBcUEAOWmyA02ca%25252BDjHi1KjjOXrP1ClQbSRVgc8TeVw%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-062aae967eb8c0846313395fd450b7010d517101&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Fzu8kgX1LJInuU%2FInBITTXw5oUX2QolBWwQ52%2BYXvfI%3D&reserved=0>.
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ssgFp7%2FUAWmtzhqAeXThl3oV2c4Dl4%2Bhdu%2Fromfc5Aw%3D&reserved=0> for Company Registration Information.
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)
Sent: 01 February 2023 07:40
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi VJ,
Good day,
Sure will have session at 12 Noon.
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947760277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cKtCjdcN4RoUli30pjcRcYVVLtQNCxS2buFd177mUdk%3D&reserved=0> for Company Registration Information.
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: 01 February 2023 07:22
To: Dubey Satyam <[email protected]<mailto:[email protected]>>; Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Karanam,
Please do confirm your availability for today at 12 noon SGT time. Please also send the Webex meeting link. Thank you.
Best,
VJ
From: Dubey Satyam <[email protected]<mailto:[email protected]>>
Sent: Tuesday, 31 January 2023 5:46 pm
To: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi Karnam,
I understand you were busy today.
I am available tomorrow at 12 noon SGT.
Regards,
Satyam Dubey | National University of Singapore | Architecture & Operations |
Desk Phone: (+65)-81506893| Email: [email protected]<mailto:[email protected]>
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>
Sent: Tuesday, 31 January 2023 4:09 pm
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
- External Email -
HI Satyam,
Good day,
Can we have session Tomorrow at 10 AM IST?
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttps%25253A%25252F%25252Fddec1-0-en-ctp.trendmicro.com%25252Fwis%25252Fclicktime%25252Fv1%25252Fquery%25253Furl%25253Dhttp%2525253a%2525252f%2525252fwww.cisco.com%2525252fweb%2525252fabout%2525252fdoing_business%2525252flegal%2525252fcri%2525252findex.html%252526umid%25253D72662d66-9684-4ef8-abee-d45b9d63eb6e%252526auth%25253D32813f2e647ebb91b39d0b35ac97db1efa82dd64-b539bcf3bc3e4dcf17e4f42207be4cf2da93c523%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253dQn8cMd5AFiEcSneteK9GMUReuL8%25252FaPJa1z5AJ%25252Fs3qSM%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-388e8af5373285eacf5dba6d40e257c29b0cf14d&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947760277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Rt1wKAYwB4uAwGLvlIbXjuqHHgJn0UY7IssGASK6X3c%3D&reserved=0> for Company Registration Information.
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: 31 January 2023 13:37
To: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Satyam,
Could you confirm your availability for tomorrow?
Best,
VJ
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>
Sent: Tuesday, 31 January 2023 4:04 pm
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
Good day,
Apologies for delay today,
Can we have session tomorrow ?
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to recei
The E-mail body was longer than 32KB, So it was added as an Attachment (20230206-225245899_mail.txt).
File Name:20230206-225245876_image001.gif
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d91fab68d9015699401a
File Name:20230206-225245891_image002.gif
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d921ab68d9015699401c
File Name:20230206-225245894_image003.png
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d923fa32462b94404da4
File Name:20230206-225245899_mail.txt
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d925fa32462b94404da8
Software Version: -- => 8.10.162.0
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB.
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB.
Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB.
timestamp : 2023-02-11T02:22:40.000+0000 || updatedby : kasimha || type : RESOLUTION SUMMARY || visibility : External || details : Please find call summary,
As per discussion over call, Session time out should be configured to 84000 seconds and 3600 idle time out.
Current configuration 7200 is minimum session time out time,
Please update Session time out and idle time out as per best practice.
Attached link for reference:
Cisco Wireless LAN Controller (WLC) Configuration Best Practices - Cisco | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
From: [email protected]
To: "Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)" <[email protected]>,Dubey Satyam <[email protected]>,"Karthikeyan Muthu (karmuth2)" <[email protected]>,"[email protected]" <[email protected]>
Cc: "Mohamed Issam Niyamathullah (NCS)" <[email protected]>,"Alejo Jay Mark Arcilia (NCS)" <[email protected]>,"Tan Wei Heng (NCS)" <[email protected]>,CCE Wipro NET <[email protected]>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Karanam.
Thank you.
Hi Satyam,
Do u need anything else? If not I will proceed to close this case. Thank You.
Best,
VJ
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]>
Sent: Tuesday, 7 February 2023 12:49 pm
To: VJ Vijayadas (NCS) <[email protected]>; Dubey Satyam <[email protected]>; Karthikeyan Muthu (karmuth2) <[email protected]>; [email protected]
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]>; Alejo Jay Mark Arcilia (NCS) <[email protected]>; Tan Wei Heng (NCS) <[email protected]>; CCE Wipro NET <[email protected]>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
Good day,
Please find reasons for disconnections for SDA and Non SDA environment.
CO_CLIENT_DELETE_REASON_SESSION_TIMEOUT > Session timeout> Client is deleted due to session time out. Time out occurs because of termination when no user is responding or answering.
CO_CLIENT_DELETE_REASON_IDLE_TIMEOUT> Idle timeout> Client is deleted due to session idle time out . Session time out occurs because idle time out occurs at Client not responding.
If any querys/ Issues please feel free to reach back to us.
Have a great day 😊
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cisco.com%2Fweb%2Fabout%2Fdoing_business%2Flegal%2Fcri%2Findex.html&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TMO4VFLd8NpyrIoufRJTS758%2BSb7nFceexhguMMSMvE%3D&reserved=0> for Company Registration Information.
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: 06 February 2023 11:34
To: Dubey Satyam <[email protected]<mailto:[email protected]>>; Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Karnam,
Could you share the delete reasons known from such issues for sda and non sda client connectivity environment?
Best,
VJ
From: Dubey Satyam <[email protected]<mailto:[email protected]>>
Sent: Monday, 6 February 2023 1:59 pm
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
We have got the clarity on the case to adjust session timeout. We are into discussion for adoption of this workaround.
My ask on last call was to share the delete reasons known from such issues for sda and non sda client connectivity environment.
This is still pending from Karnam. Once this info is provided. Please proceed with closure.
Regards,
Satyam Dubey | National University of Singapore | Architecture & Operations |
Desk Phone: (+65)-81506893| Email: [email protected]<mailto:[email protected]>
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: Monday, 6 February 2023 11:29 am
To: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
- External Email -
Hi Satyam,
Do you require any other assistance regarding this case? if not, we will proceed to close this ticket. Thank You.
Best,
VJ
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>
Sent: Monday, 6 February 2023 10:38 am
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
Good day,
I hope you are doing great,
Can I know is there any assistance required on this case?
If any queries/ Issues please feel free to reach back to us.
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ssgFp7%2FUAWmtzhqAeXThl3oV2c4Dl4%2Bhdu%2Fromfc5Aw%3D&reserved=0> for Company Registration Information.
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)
Sent: 02 February 2023 08:03
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
HI VJ,
Good day,
Thanks for your time over call,
Please find call summary,
As per discussion over call, Session time out should be configured to 84000 seconds and 3600 idle time out.
Current configuration 7200 is minimum session time out time,
Please update Session time out and idle time out as per best practice.
Attached link for reference:
Cisco Wireless LAN Controller (WLC) Configuration Best Practices - Cisco<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttps%25253A%25252F%25252Fwww.cisco.com%25252Fc%25252Fen%25252Fus%25252Ftd%25252Fdocs%25252Fwireless%25252Fcontroller%25252Ftechnotes%25252F8-6%25252Fb_Cisco_Wireless_LAN_Controller_Configuration_Best_Practices.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253dbl61KB9krPuB2HovEcBPPtq%25252BrKu3hTzZjT3fedcDQDA%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-4d77f7350e6280d16e1161e378aa6a914f848465&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r43FOFLAqMfGwHxsum76UZeaZhSING1KWqVbfMh%2F8k4%3D&reserved=0>
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ssgFp7%2FUAWmtzhqAeXThl3oV2c4Dl4%2Bhdu%2Fromfc5Aw%3D&reserved=0> for Company Registration Information.
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)
Sent: 01 February 2023 10:15
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
HI VJ,
Good day,
Please join the session.
https://cisco.webex.com/ciscosales/j.php?MTID=m2cc007e651c8ae9736187f43fc025c18<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttps%25253A%25252F%25252Fcisco.webex.com%25252Fciscosales%25252Fj.php%25253FMTID%25253Dm2cc007e651c8ae9736187f43fc025c18%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253dHBcUEAOWmyA02ca%25252BDjHi1KjjOXrP1ClQbSRVgc8TeVw%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-062aae967eb8c0846313395fd450b7010d517101&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Fzu8kgX1LJInuU%2FInBITTXw5oUX2QolBWwQ52%2BYXvfI%3D&reserved=0>.
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947604043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ssgFp7%2FUAWmtzhqAeXThl3oV2c4Dl4%2Bhdu%2Fromfc5Aw%3D&reserved=0> for Company Registration Information.
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco)
Sent: 01 February 2023 07:40
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi VJ,
Good day,
Sure will have session at 12 Noon.
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttp%25253A%25252F%25252Fwww.cisco.com%25252Fweb%25252Fabout%25252Fdoing_business%25252Flegal%25252Fcri%25252Findex.html%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253d5EB9zhbRctNQHjLTCZyAl5LSCGwDy%25252FONagz4RviFfTQ%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-22fdb2439cb33c1ab5c3d5ff1e22201c5da83495&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947760277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cKtCjdcN4RoUli30pjcRcYVVLtQNCxS2buFd177mUdk%3D&reserved=0> for Company Registration Information.
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: 01 February 2023 07:22
To: Dubey Satyam <[email protected]<mailto:[email protected]>>; Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Karanam,
Please do confirm your availability for today at 12 noon SGT time. Please also send the Webex meeting link. Thank you.
Best,
VJ
From: Dubey Satyam <[email protected]<mailto:[email protected]>>
Sent: Tuesday, 31 January 2023 5:46 pm
To: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi Karnam,
I understand you were busy today.
I am available tomorrow at 12 noon SGT.
Regards,
Satyam Dubey | National University of Singapore | Architecture & Operations |
Desk Phone: (+65)-81506893| Email: [email protected]<mailto:[email protected]>
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>
Sent: Tuesday, 31 January 2023 4:09 pm
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
- External Email -
HI Satyam,
Good day,
Can we have session Tomorrow at 10 AM IST?
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fddec1-0-en-ctp.trendmicro.com%2Fwis%2Fclicktime%2Fv1%2Fquery%3Furl%3Dhttps%253a%252f%252fapc01.safelinks.protection.outlook.com%252f%253furl%253dhttps%25253A%25252F%25252Fddec1-0-en-ctp.trendmicro.com%25252Fwis%25252Fclicktime%25252Fv1%25252Fquery%25253Furl%25253Dhttp%2525253a%2525252f%2525252fwww.cisco.com%2525252fweb%2525252fabout%2525252fdoing_business%2525252flegal%2525252fcri%2525252findex.html%252526umid%25253D72662d66-9684-4ef8-abee-d45b9d63eb6e%252526auth%25253D32813f2e647ebb91b39d0b35ac97db1efa82dd64-b539bcf3bc3e4dcf17e4f42207be4cf2da93c523%2526data%253d05%25257C01%25257Cvj.vijayadas%252540ncs.com.sg%25257Ca2133a262a064a82dae508db07eb2b6a%25257Cca90d8f589634b6ebca99ac468bcc7a8%25257C1%25257C0%25257C638112478927901895%25257CUnknown%25257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%25253D%25257C3000%25257C%25257C%25257C%2526sdata%253dQn8cMd5AFiEcSneteK9GMUReuL8%25252FaPJa1z5AJ%25252Fs3qSM%25253D%2526reserved%253d0%26umid%3D3584dd66-fcee-46bc-9e92-375d49bad412%26auth%3D32813f2e647ebb91b39d0b35ac97db1efa82dd64-388e8af5373285eacf5dba6d40e257c29b0cf14d&data=05%7C01%7Cvj.vijayadas%40ncs.com.sg%7C75e5480bd68d42d6074208db08c6bb92%7Cca90d8f589634b6ebca99ac468bcc7a8%7C1%7C0%7C638113421947760277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Rt1wKAYwB4uAwGLvlIbXjuqHHgJn0UY7IssGASK6X3c%3D&reserved=0> for Company Registration Information.
From: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>
Sent: 31 January 2023 13:37
To: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
Hi Satyam,
Could you confirm your availability for tomorrow?
Best,
VJ
From: Karanam Sujith Simha -X (kasimha - ALLEGIS SERVICES INDIA PRIVATE LIMITED at Cisco) <[email protected]<mailto:[email protected]>>
Sent: Tuesday, 31 January 2023 4:04 pm
To: VJ Vijayadas (NCS) <[email protected]<mailto:[email protected]>>; Dubey Satyam <[email protected]<mailto:[email protected]>>; Karthikeyan Muthu (karmuth2) <[email protected]<mailto:[email protected]>>
Cc: Mohamed Issam Niyamathullah (NCS) <[email protected]<mailto:[email protected]>>; Alejo Jay Mark Arcilia (NCS) <[email protected]<mailto:[email protected]>>; Tan Wei Heng (NCS) <[email protected]<mailto:[email protected]>>; CCE Wipro NET <[email protected]<mailto:[email protected]>>
Subject: RE: SR 694952109 Helpdesk#NCS#23478883 : Client while connecting to the AP 2802-S-K9 is facing issue after periodic time
[External email] Please be cautious when clicking on any links or attachments.
________________________________
Hi VJ,
Good day,
Apologies for delay today,
Can we have session tomorrow ?
Thanks & Regards,
[Icon Description automatically generated]
Sujith Simha Karanam
[email protected]<mailto:[email protected]>
Cisco TAC|Wireless
Planned Leaves:
INDIA: +91 80 44263151
SHIFT:
Sunday – Thursday,9AM - 5AM US(EDT)
Monday- Friday ,6:30AM-2:30PM (IST)
Monday- Friday,12:00AM-8 PM (AEDT)
Monday- Friday,9AM- 5 PM (SGT)
Manager:
Ramya M
[email protected]<mailto:[email protected]>
Tech Leads:
[email protected]<mailto:[email protected]>
[signature_281047838]Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to recei
The E-mail body was longer than 32KB, So it was added as an Attachment (20230206-225245899_mail.txt).
File Name:20230206-225245876_image001.gif
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d91fab68d9015699401a
File Name:20230206-225245891_image002.gif
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d921ab68d9015699401c
File Name:20230206-225245894_image003.png
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d923fa32462b94404da4
File Name:20230206-225245899_mail.txt
https://mycase.cloudapps.cisco.com/694952109/attach?fileID=63e1d925fa32462b94404da8
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB.
Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB.
timestamp : 2023-02-11T02:22:40.000+0000 || updatedby : kasimha || type : RESOLUTION SUMMARY || visibility : External || details : Please find call summary,
As per discussion over call, Session time out should be configured to 84000 seconds and 3600 idle time out.
Current configuration 7200 is minimum session time out time,
Please update Session time out and idle time out as per best practice.
Attached link for reference:
Cisco Wireless LAN Controller (WLC) Configuration Best Practices - Cisco | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB. | Hi Support,
Please find below info.
- What is current version of WLC? – 8.10.162.0
- Is this only having this issue with connected client? – we are observing this from multiple clients across 2802i’s.
- Were there any changes in config/topo in prior this issue. - None
- What is the impact? How many users affected. - VIP’s in CLIB. | timestamp : 2023-02-11T02:22:40.000+0000 || updatedby : kasimha || type : RESOLUTION SUMMARY || visibility : External || details : Please find call summary,
As per discussion over call, Session time out should be configured to 84000 seconds and 3600 idle time out.
Current configuration 7200 is minimum session time out time,
Please update Session time out and idle time out as per best practice.
Attached link for reference:
Cisco Wireless LAN Controller (WLC) Configuration Best Practices - Cisco | nan | AIR-CT8540-K9Z | MFG_CTVM_SMALL_8.10.171.0.iso | nan | nan | 3 | nan | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | nan | nan | nan | nan | nan | nan |
694831371 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 2.2.3.4/ 16.12.04/ 2.1.2.7/ 2.2.2.9/ 2.2.2.8/ 1.3.1.4/ 2.3.3.4/ 2.3.3.7/ 2.2.2.8/ 1.3.3.7/ 17.03.03/ 2.1.2.7/ 1.3.3.7/ 2.2.2.9/ 2.3.3.7/ 16.12.4/ 2.2.3.5/ 2.2.3.6/ 2.2.2.9/ 4.0.4b/ 2.2.3.4/ 2.2.2.8/ 2.1.2.6/ 2.2.3.5 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
9300-48U Version 16.12.
DNAC 2.2.2.9
Thanks for your time during Webex session today.
Please find a brief summary below:
DNAC version: 2.2.2.9
ISE version: 2.7
NETCONF not working for switches when customer is using TACACS credentials and it works fine when local credentials are used.
On switch logs we are seeing following message:
Jan 8 2023 13:58:22.107 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:49803 for netconf over ssh.
Jan 8 2023 13:58:27.304 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:10261 for netconf over ssh.
We added following AAA config on switch and NETCONF started working using TACACS credentials:
aaa authentication login default group dnac-network-tacacs-group local
aaa authorization exec default group dnac-network-tacacs-group local if-authenticated
This is an expected behaviour with NETCONF while using TACACS credentials as documented under https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy47909 and we need to continue using workaround by applying above AAA commands using a CLI template to all switches where NETCONF will be enabled.
I will work with Dev team to updated affected version for this bug.
Regarding the other issue where DNAC is unable to login to switch using NETCONF when TACACS credentials are used we found that AAA request hits deny shell access rule because remote address is missing in the request due to which it cannot match same permit rule which is used when you use your own TACACS credential.
I will work with Manjunath to validate this behaviour in lab and see if we are able to replicate same.
Please upload all the debugs and sessions logs regarding this issue to the TAC case.
Please find below the requested details.
1.
Which DNAC version are you running?
2.2.2.9
2.
Could you please briefly describe the Business Impact this issue has on your operations (Low / Medium / High)?
Medium
1.
Is this a single node or a three-node cluster?
3-node cluster
1.
Is your appliance a DN1 or DN2?
DN2
1.
Please let me know your availability for a call.
You can send me the invitie
Software Version: -- => 2.2.2.9
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
timestamp : 2023-04-25T03:36:32.000+0000 || updatedby : bochinna || type : RESOLUTION SUMMARY || visibility : External || details : Resolution Summary
=====================
When DNAC ssh’s to NAD on the traditional port, its passes through and Inventory collection and other automation feature works as anticipated. However, when its SSH’s over 830 on Netconf, it’s gets denied.
The denial occurs because Netconf yang packet doesn’t contain remote address (DNAC address) in the TACAS request. This is a known behavior, and an enhancement has been raised for this CSCvx47585 | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN1-HW-APL/ DN2-HW-APL/ DN2-HW-APL-XL/ C9300-48UN/ DN2-HW-APL-L/ DN2-HW-APL-U/ C9300-48U Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Resolution Summary
=====================
When DNAC ssh’s to NAD on the traditional port, its passes through and Inventory collection and other automation feature works as anticipated. However, when its SSH’s over 830 on Netconf, it’s gets denied.
The denial occurs because Netconf yang packet doesn’t contain remote address (DNAC address) in the TACAS request. This is a known behavior, and an enhancement has been raised for this CSCvx47585
Thanks for the case closure confirmation over WebExTeams on the 18th April.
It’s always a pleasure working with you and looking forward to work with you in the future 😊
I will proceed to close this SR.
It’s me again.
How are we tracking on this SR?
Have you upgraded the test switch to 17.4 or 17.6 version.
If so, please test Netconf ssh and let you know if you require further assistance.
NETCONF not working for switches when customer is using TACACS credentials and it works fine when local credentials are used.
%DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:54946 for netconf over ssh.
This is a known issue, Defect ID has been provided to the customer.
SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
9300-48U Version 16.12.
DNAC 2.2.2.9
This is a known issue, Defect ID has been provided to the customer.
TAC to provide a patched list for the defect
Thanks for the update and it was lovely connecting with you over the Webex.
I understand that you have the below safety net measure to secure any ssh request that reaches ISE with DNAC managed username.
When DNAC ssh’s to NAD on the traditional port, its passes through and Inventory collection and other automation feature works as anticipated.
However, when its SSH’s over 830 on Netconf, it’s gets denied.
The denial occurs because Netconf yang packet doesn’t conatin remote address (DNAC address) in the TACAS request.
This is a known behaviour and an enhancement has been raised for this
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx47585
Please allow me to identify if the patched versions work and suggest you one.
This case has been already updated.
Below is the update:
We appreciate your continuous patience working with Cisco Sydney TAC on this SR.
I have taken over this SR from Hitesh.
Please allow me to review the case, work with Hitesh to clarify the case details should it be required and come back to you with an action plan.
As per your usual communication preference, I’ll reach out to you on Webex teams.
To work with Manjunath and validate this behaviour in lab and see if we are able to replicate same where remote address is missing when we use TACACS credential from DNAC
Need to request for a lab again and perform testing
To work with Manjunath and validate this behaviour in lab and see if we are able to replicate same where remote address is missing when we use TACACS credential from DNAC
Pending device availability in lab
NETCONF not working for switches when customer is using TACACS credentials and it works fine when local credentials are used.
On switch logs we are seeing following message:
Jan 8 2023 13:58:22.107 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:49803 for netconf over ssh.
Jan 8 2023 13:58:27.304 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:10261 for netconf over ssh.
We added following AAA config on switch and NETCONF started working using TACACS credentials:
aaa authentication login default group dnac-network-tacacs-group local
aaa authorization exec default group dnac-network-tacacs-group local if-authenticated
This is an expected issue as of today and a enhancement was raised to improve this under https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy47909 but till date behaviour is still same. We need to use CLI template during switch provision in order to apply these 2 commands.
Regarding the other issue where DNAC is unable to login to switch using NETCONF when TACACS credential is used we found that AAA request hits deny shell access rule because remote address is missing in the request due to which it cannot match same permit rule which is used when you use your own TACACS credential. However, when George uses his own TACACS credential it seems to have remote address of DNAC due to which it matches correct authorization rule and gets permitted.
To work with Manjunath and validate this behaviour in lab and see if we are able to replicate same where remote address is missing when we use TACACS credential from DNAC
Thanks for your time during Webex session today.
Please find a brief summary below:
DNAC version: 2.2.2.9
ISE version: 2.7
NETCONF not working for switches when customer is using TACACS credentials and it works fine when local credentials are used.
On switch logs we are seeing following message:
Jan 8 2023 13:58:22.107 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:49803 for netconf over ssh.
Jan 8 2023 13:58:27.304 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:10261 for netconf over ssh.
We added following AAA config on switch and NETCONF started working using TACACS credentials:
aaa authentication login default group dnac-network-tacacs-group local
aaa authorization exec default group dnac-network-tacacs-group local if-authenticated
This is an expected behaviour with NETCONF while using TACACS credentials as documented under https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy47909 and we need to continue using workaround by applying above AAA commands using a CLI template to all switches where NETCONF will be enabled.
I will work with Dev team to updated affected version for this bug.
Regarding the other issue where DNAC is unable to login to switch using NETCONF when TACACS credentials are used we found that AAA request hits deny shell access rule because remote address is missing in the request due to which it cannot match same permit rule which is used when you use your own TACACS credential.
I will work with Manjunath to validate this behaviour in lab and see if we are able to replicate same.
Please upload all the debugs and sessions logs regarding this issue to the TAC case.
NETCONF not working for switches when customer is using TACACS credentials and it works fine when local credentials are used.
On switch logs we are seeing following message:
Jan 8 2023 13:58:22.107 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:49803 for netconf over ssh.
Jan 8 2023 13:58:27.304 SGT: %DMI-5-AUTHENTICATION_FAILED: Switch 1 R0/0: dmiauthd: Authentication failure from 172.18.12.20:10261 for netconf over ssh.
We added following AAA config on switch and NETCONF started working using TACACS credentials:
aaa authentication login default group dnac-network-tacacs-group local
aaa authorization exec default group dnac-network-tacacs-group local if-authenticated
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
-- Do not delete or change any of the following text.
User [email protected] requested TAC Connect bot to requeue case 694831371. Current time is outside the case owner's working hours (12:30 - 16:30 Tuesday - Saturday IST) and hence the case is requeued without contacting the case owner [email protected]. Please contact customer using their phone which is their preferred contact preference.
User [email protected] informed TAC Connect Bot that the case summary was not useful. Please update the case 694831371 with the latest GCI. Thanks!
Hope you are doing well.
This is Saurabh Khillare from the DNA Solution Support team; I will be the engineer assisting you with this service request.
I am sending this out as an initial point of contact to let you know that I have accepted your case and to give you information on how to contact me.
You can find my contact details and working hours in the signature of this email.
Is the device under managed state in DNAC inventory?
Are you able to SSH normally? Via 22 port
Does the user have priv 15?
Was this working earlier?
User [email protected] requested TAC Connect bot to requeue case 694831371 and decided not to contact current case owner. Please contact customer using their phone which is their preferred contact preference.
Lets have the call on Friday.
Is it ok a call for tomorrow at 9:00 AM CST?
Please find below the requested details.
1.
Which DNAC version are you running?
2.2.2.9
2.
Could you please briefly describe the Business Impact this issue has on your operations (Low / Medium / High)?
Medium
1.
Is this a single node or a three-node cluster?
3-node cluster
1.
Is your appliance a DN1 or DN2?
DN2
1.
Please let me know your availability for a call.
You can send me the invitie
Problem Details: SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
$ ssh [email protected] -p 830 netconf
[email protected]'s password:
Permission denied, please try again.
[email protected]'s password:
You can now upload files to the case using FTP/FTPS/SCP/SFTP/HTTPS protocols and the following details:
Hostname: cxd.cisco.com
Username: 694831371
Password: i62rW1A7tWv5A7Np
Please note:
1. When uploading to HTTPS the path must be set to /home/<filename>, for all other protocols the path is always '/<filename>'
2. Empty files, that is files with a size of 0 Bytes, will not be attached and will be deleted automatically.
Software Version: -- => 2.2.2.9
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication
timestamp : 2023-04-25T03:36:32.000+0000 || updatedby : bochinna || type : RESOLUTION SUMMARY || visibility : External || details : Resolution Summary
=====================
When DNAC ssh’s to NAD on the traditional port, its passes through and Inventory collection and other automation feature works as anticipated. However, when its SSH’s over 830 on Netconf, it’s gets denied.
The denial occurs because Netconf yang packet doesn’t contain remote address (DNAC address) in the TACAS request. This is a known behavior, and an enhancement has been raised for this CSCvx47585 | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication | SDA DNAC - C9300 NETCONF SSH access not working using TACACS authentication | timestamp : 2023-04-25T03:36:32.000+0000 || updatedby : bochinna || type : RESOLUTION SUMMARY || visibility : External || details : Resolution Summary
=====================
When DNAC ssh’s to NAD on the traditional port, its passes through and Inventory collection and other automation feature works as anticipated. However, when its SSH’s over 830 on Netconf, it’s gets denied.
The denial occurs because Netconf yang packet doesn’t contain remote address (DNAC address) in the TACAS request. This is a known behavior, and an enhancement has been raised for this CSCvx47585 | nan | C9300-48U | cat9k_iosxe.16.12.04.SPA.bin | nan | nan | 3 | nan | Software Bug | DNAHW | Cisco DNA Center - On-Prem | Cisco DNA Center - Infrastructure (Services, UI, API, etc.) | nan | nan | nan | nan | nan | nan |
694105276 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Software Version: -- => 16.12.4
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10
SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10
timestamp : 2022-09-20T02:32:40.000+0000 || updatedby : josandov || type : RESOLUTION SUMMARY || visibility : External || details : Review IPDT configuration, command pushed seems to be expected.
Requested additional information about observed MAC Flood evidence.
Pending logs about MAC flooding | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10
SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10
timestamp : 2022-09-20T02:32:40.000+0000 || updatedby : josandov || type : RESOLUTION SUMMARY || visibility : External || details : Review IPDT configuration, command pushed seems to be expected.
Requested additional information about observed MAC Flood evidence.
Pending logs about MAC flooding | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10 | SDA - Fabric Edge C9300 experiencing MAC flooding from specific ports and observing inconsistent in device-tracking IPDT policy applied to ports. We see inconsistent in the IPDT policy applied to the ports. Some switch ports are configured with IPDT_POLICY and some are with IPDT_MAX_10.
- whether the IPDT policy differs based on the code the device is running.
- whether the IPDT policy 'limit address-count' can help to address the MAC flooding issue.
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Gi1/0/1 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/2 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/3 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/5 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/8 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/9 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/10 PORT IPDT_POLICY Device-tracking vlan all
Gi1/0/11 PORT IPDT_POLICY Device-tracking vlan all
CELS-02-CNT-ES1#show device-tracking policy IPDT_MAX_10
Policy IPDT_MAX_10 configuration:
security-level guard
device-role node
gleaning from Neighbor Discovery
gleaning from DHCP
gleaning from ARP
gleaning from DHCP4
NOT gleaning from protocol unkn
limit address-count 10
tracking enable
Policy IPDT_MAX_10 is applied on the following targets:
Target Type Policy Feature Target range
Ap1/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap2/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap3/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap4/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap5/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/32 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/42 PORT IPDT_MAX_10 Device-tracking vlan all
Gi6/0/44 PORT IPDT_MAX_10 Device-tracking vlan all
Ap6/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/37 PORT IPDT_MAX_10 Device-tracking vlan all
Gi7/0/39 PORT IPDT_MAX_10 Device-tracking vlan all
Ap7/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Ap8/0/1 PORT IPDT_MAX_10 Device-tracking vlan all
Checked one of the switch (S13-02-CNT-ES2) running code 16.12.3s, all ports are configured with IPDT_MAX_10 | timestamp : 2022-09-20T02:32:40.000+0000 || updatedby : josandov || type : RESOLUTION SUMMARY || visibility : External || details : Review IPDT configuration, command pushed seems to be expected.
Requested additional information about observed MAC Flood evidence.
Pending logs about MAC flooding | nan | C9300-48U | cat9k_iosxe.16.12.04.SPA.bin | nan | nan | 3 | nan | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | nan | nan | nan | nan | nan | nan |
694482515 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Admin Access
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE- Admin/Portal wild card certificate not getting imported to secondary MNT node
We have totally 12 ISE nodes in the deployment (2 PAN, 2 MNT + 8 PSNs). The wild certificates are getting imported to all nodes in the deployment, except the secondary MNT node (hdsc-mnt-nac01)
ISE- Admin/Portal wild card certificate not getting imported to secondary MNT node
We have totally 12 ISE nodes in the deployment (2 PAN, 2 MNT + 8 PSNs). The wild certificates are getting imported to all nodes in the deployment, except the secondary MNT node (hdsc-mnt-nac01)
workaround for that is by,
First deregistering the affected node from the ISE cluster,
Then importing the certificate into the deployment,
And then adding the secondary monitoring node back to the deployment and synching up the nodes. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: SNS-3695-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Admin Access
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE- Admin/Portal wild card certificate not getting imported to secondary MNT node
We have totally 12 ISE nodes in the deployment (2 PAN, 2 MNT + 8 PSNs). The wild certificates are getting imported to all nodes in the deployment, except the secondary MNT node (hdsc-mnt-nac01)
ISE- Admin/Portal wild card certificate not getting imported to secondary MNT node
We have totally 12 ISE nodes in the deployment (2 PAN, 2 MNT + 8 PSNs). The wild certificates are getting imported to all nodes in the deployment, except the secondary MNT node (hdsc-mnt-nac01)
workaround for that is by,
First deregistering the affected node from the ISE cluster,
Then importing the certificate into the deployment,
And then adding the secondary monitoring node back to the deployment and synching up the nodes. | Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Admin Access
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE- Admin/Portal wild card certificate not getting imported to secondary MNT node
We have totally 12 ISE nodes in the deployment (2 PAN, 2 MNT + 8 PSNs). The wild certificates are getting imported to all nodes in the deployment, except the secondary MNT node (hdsc-mnt-nac01) | ISE- Admin/Portal wild card certificate not getting imported to secondary MNT node
We have totally 12 ISE nodes in the deployment (2 PAN, 2 MNT + 8 PSNs). The wild certificates are getting imported to all nodes in the deployment, except the secondary MNT node (hdsc-mnt-nac01) | workaround for that is by,
First deregistering the affected node from the ISE cluster,
Then importing the certificate into the deployment,
And then adding the secondary monitoring node back to the deployment and synching up the nodes. | ISE- Admin/Portal wild card certificate not getting import to secondary MNT. | SNS-3695-K9 | nan | nan | 36.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | CISE | Identity Services Engine (ISE) - 3.0 | ISE Admin Access | 01tA0000000huFmIAI | Error Messages, Logs, Debugs | ISE Admin Access | Identity Services Engine (ISE) - 3.0 | 01tA0000000huFSIAY | TARPIT: PARTIAL |
694140893 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 3.0.0.458/ 2.7.0.356/ 3.0.0.448/ 3.0.0.458/ 3.0.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
High CPU Load on PAN node
The Tech top output does not show the process iseadmin+
Platform: SNS-3655-K9
Version: 3.0.0.458
Patch: 3
Serial Number WZP23040NF3
Disk: 1198 GB
CPU_Cores: 24
RAM: 93 GB
Deployment:
- hsdc-pan-nac01: Primary PAN,PXG
- tldc-rad-nac01: PSN
- hsdc-rad-nac03: PSN
- tldc-rad-nac02: PSN
- tldc-mnt-nac01: MNT
- tldc-rad-nac04: PSN
- hsdc-rad-nac04: PSN
- hsdc-mnt-nac01: MNT
- tldc-pan-nac01: PAN,PXG
- hsdc-rad-nac02: PSN
- hsdc-rad-nac01: PSN
- tldc-rad-nac03: PSN
Software Version: -- => 3.0.0.458
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE - High CPU load on Primary PAN node
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 13:40:56 up 303 days, 16:51, 2 users, load average: 18.38, 15.73, 13.35
Tasks: 642 total, 1 running, 641 sleeping, 0 stopped, 0 zombie
%Cpu0 : 23.2 us, 1.3 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 30.0 us, 0.3 sy, 0.0 ni, 69.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu2 : 32.1 us, 0.3 sy, 0.0 ni, 67.2 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu3 : 45.3 us, 0.7 sy, 0.0 ni, 54.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 80.5 us, 0.0 sy, 0.0 ni, 19.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 77.5 us, 0.3 sy, 0.0 ni, 22.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 81.4 us, 0.0 sy, 0.0 ni, 18.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 46.7 us, 0.0 sy, 0.0 ni, 53.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu8 : 87.4 us, 0.0 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu9 : 70.6 us, 0.3 sy, 0.0 ni, 29.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu10 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu11 : 91.1 us, 0.3 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu12 : 68.1 us, 0.3 sy, 0.0 ni, 31.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu13 : 40.2 us, 0.3 sy, 0.0 ni, 59.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu14 : 75.8 us, 0.0 sy, 0.0 ni, 24.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu15 : 63.5 us, 0.0 sy, 0.0 ni, 36.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu16 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu17 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu18 : 83.4 us, 0.3 sy, 0.0 ni, 16.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu19 : 54.3 us, 0.0 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu20 : 90.7 us, 0.0 sy, 0.0 ni, 9.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu21 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu22 : 91.4 us, 0.0 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu23 : 87.0 us, 0.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 97436048 total, 14773332 free, 31670192 used, 50992524 buff/cache
KiB Swap: 8191996 total, 7989884 free, 202112 used. 47788736 avail Mem
ISE - High CPU load on Primary PAN node
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 13:40:56 up 303 days, 16:51, 2 users, load average: 18.38, 15.73, 13.35
Tasks: 642 total, 1 running, 641 sleeping, 0 stopped, 0 zombie
%Cpu0 : 23.2 us, 1.3 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 30.0 us, 0.3 sy, 0.0 ni, 69.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu2 : 32.1 us, 0.3 sy, 0.0 ni, 67.2 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu3 : 45.3 us, 0.7 sy, 0.0 ni, 54.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 80.5 us, 0.0 sy, 0.0 ni, 19.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 77.5 us, 0.3 sy, 0.0 ni, 22.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 81.4 us, 0.0 sy, 0.0 ni, 18.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 46.7 us, 0.0 sy, 0.0 ni, 53.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu8 : 87.4 us, 0.0 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu9 : 70.6 us, 0.3 sy, 0.0 ni, 29.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu10 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu11 : 91.1 us, 0.3 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu12 : 68.1 us, 0.3 sy, 0.0 ni, 31.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu13 : 40.2 us, 0.3 sy, 0.0 ni, 59.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu14 : 75.8 us, 0.0 sy, 0.0 ni, 24.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu15 : 63.5 us, 0.0 sy, 0.0 ni, 36.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu16 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu17 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu18 : 83.4 us, 0.3 sy, 0.0 ni, 16.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu19 : 54.3 us, 0.0 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu20 : 90.7 us, 0.0 sy, 0.0 ni, 9.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu21 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu22 : 91.4 us, 0.0 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu23 : 87.0 us, 0.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 97436048 total, 14773332 free, 31670192 used, 50992524 buff/cache
KiB Swap: 8191996 total, 7989884 free, 202112 used. 47788736 avail Mem
timestamp : 2023-01-09T15:54:07.000+0000 || updatedby : surymish || type : RESOLUTION SUMMARY || visibility : External || details : No response from Cu since dec 10th | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: SNS-3655-K9/ SNS-3695-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
High CPU Load on PAN node
The Tech top output does not show the process iseadmin+
Platform: SNS-3655-K9
Version: 3.0.0.458
Patch: 3
Serial Number WZP23040NF3
Disk: 1198 GB
CPU_Cores: 24
RAM: 93 GB
Deployment:
- hsdc-pan-nac01: Primary PAN,PXG
- tldc-rad-nac01: PSN
- hsdc-rad-nac03: PSN
- tldc-rad-nac02: PSN
- tldc-mnt-nac01: MNT
- tldc-rad-nac04: PSN
- hsdc-rad-nac04: PSN
- hsdc-mnt-nac01: MNT
- tldc-pan-nac01: PAN,PXG
- hsdc-rad-nac02: PSN
- hsdc-rad-nac01: PSN
- tldc-rad-nac03: PSN
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE - High CPU load on Primary PAN node
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 13:40:56 up 303 days, 16:51, 2 users, load average: 18.38, 15.73, 13.35
Tasks: 642 total, 1 running, 641 sleeping, 0 stopped, 0 zombie
%Cpu0 : 23.2 us, 1.3 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 30.0 us, 0.3 sy, 0.0 ni, 69.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu2 : 32.1 us, 0.3 sy, 0.0 ni, 67.2 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu3 : 45.3 us, 0.7 sy, 0.0 ni, 54.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 80.5 us, 0.0 sy, 0.0 ni, 19.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 77.5 us, 0.3 sy, 0.0 ni, 22.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 81.4 us, 0.0 sy, 0.0 ni, 18.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 46.7 us, 0.0 sy, 0.0 ni, 53.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu8 : 87.4 us, 0.0 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu9 : 70.6 us, 0.3 sy, 0.0 ni, 29.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu10 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu11 : 91.1 us, 0.3 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu12 : 68.1 us, 0.3 sy, 0.0 ni, 31.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu13 : 40.2 us, 0.3 sy, 0.0 ni, 59.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu14 : 75.8 us, 0.0 sy, 0.0 ni, 24.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu15 : 63.5 us, 0.0 sy, 0.0 ni, 36.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu16 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu17 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu18 : 83.4 us, 0.3 sy, 0.0 ni, 16.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu19 : 54.3 us, 0.0 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu20 : 90.7 us, 0.0 sy, 0.0 ni, 9.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu21 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu22 : 91.4 us, 0.0 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu23 : 87.0 us, 0.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 97436048 total, 14773332 free, 31670192 used, 50992524 buff/cache
KiB Swap: 8191996 total, 7989884 free, 202112 used. 47788736 avail Mem
ISE - High CPU load on Primary PAN node
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 13:40:56 up 303 days, 16:51, 2 users, load average: 18.38, 15.73, 13.35
Tasks: 642 total, 1 running, 641 sleeping, 0 stopped, 0 zombie
%Cpu0 : 23.2 us, 1.3 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 30.0 us, 0.3 sy, 0.0 ni, 69.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu2 : 32.1 us, 0.3 sy, 0.0 ni, 67.2 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu3 : 45.3 us, 0.7 sy, 0.0 ni, 54.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 80.5 us, 0.0 sy, 0.0 ni, 19.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 77.5 us, 0.3 sy, 0.0 ni, 22.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 81.4 us, 0.0 sy, 0.0 ni, 18.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 46.7 us, 0.0 sy, 0.0 ni, 53.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu8 : 87.4 us, 0.0 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu9 : 70.6 us, 0.3 sy, 0.0 ni, 29.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu10 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu11 : 91.1 us, 0.3 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu12 : 68.1 us, 0.3 sy, 0.0 ni, 31.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu13 : 40.2 us, 0.3 sy, 0.0 ni, 59.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu14 : 75.8 us, 0.0 sy, 0.0 ni, 24.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu15 : 63.5 us, 0.0 sy, 0.0 ni, 36.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu16 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu17 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu18 : 83.4 us, 0.3 sy, 0.0 ni, 16.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu19 : 54.3 us, 0.0 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu20 : 90.7 us, 0.0 sy, 0.0 ni, 9.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu21 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu22 : 91.4 us, 0.0 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu23 : 87.0 us, 0.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 97436048 total, 14773332 free, 31670192 used, 50992524 buff/cache
KiB Swap: 8191996 total, 7989884 free, 202112 used. 47788736 avail Mem
timestamp : 2023-01-09T15:54:07.000+0000 || updatedby : surymish || type : RESOLUTION SUMMARY || visibility : External || details : No response from Cu since dec 10th | Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: ISE - High CPU load on Primary PAN node
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 13:40:56 up 303 days, 16:51, 2 users, load average: 18.38, 15.73, 13.35
Tasks: 642 total, 1 running, 641 sleeping, 0 stopped, 0 zombie
%Cpu0 : 23.2 us, 1.3 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 30.0 us, 0.3 sy, 0.0 ni, 69.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu2 : 32.1 us, 0.3 sy, 0.0 ni, 67.2 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu3 : 45.3 us, 0.7 sy, 0.0 ni, 54.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 80.5 us, 0.0 sy, 0.0 ni, 19.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 77.5 us, 0.3 sy, 0.0 ni, 22.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 81.4 us, 0.0 sy, 0.0 ni, 18.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 46.7 us, 0.0 sy, 0.0 ni, 53.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu8 : 87.4 us, 0.0 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu9 : 70.6 us, 0.3 sy, 0.0 ni, 29.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu10 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu11 : 91.1 us, 0.3 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu12 : 68.1 us, 0.3 sy, 0.0 ni, 31.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu13 : 40.2 us, 0.3 sy, 0.0 ni, 59.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu14 : 75.8 us, 0.0 sy, 0.0 ni, 24.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu15 : 63.5 us, 0.0 sy, 0.0 ni, 36.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu16 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu17 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu18 : 83.4 us, 0.3 sy, 0.0 ni, 16.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu19 : 54.3 us, 0.0 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu20 : 90.7 us, 0.0 sy, 0.0 ni, 9.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu21 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu22 : 91.4 us, 0.0 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu23 : 87.0 us, 0.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 97436048 total, 14773332 free, 31670192 used, 50992524 buff/cache
KiB Swap: 8191996 total, 7989884 free, 202112 used. 47788736 avail Mem | ISE - High CPU load on Primary PAN node
hsdc-pan-nac01/admin# tech top
Invoking tech top. Press Control-C to interrupt.
top - 13:40:56 up 303 days, 16:51, 2 users, load average: 18.38, 15.73, 13.35
Tasks: 642 total, 1 running, 641 sleeping, 0 stopped, 0 zombie
%Cpu0 : 23.2 us, 1.3 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 30.0 us, 0.3 sy, 0.0 ni, 69.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu2 : 32.1 us, 0.3 sy, 0.0 ni, 67.2 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu3 : 45.3 us, 0.7 sy, 0.0 ni, 54.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 80.5 us, 0.0 sy, 0.0 ni, 19.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 77.5 us, 0.3 sy, 0.0 ni, 22.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 81.4 us, 0.0 sy, 0.0 ni, 18.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 46.7 us, 0.0 sy, 0.0 ni, 53.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu8 : 87.4 us, 0.0 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu9 : 70.6 us, 0.3 sy, 0.0 ni, 29.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu10 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu11 : 91.1 us, 0.3 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu12 : 68.1 us, 0.3 sy, 0.0 ni, 31.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu13 : 40.2 us, 0.3 sy, 0.0 ni, 59.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu14 : 75.8 us, 0.0 sy, 0.0 ni, 24.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu15 : 63.5 us, 0.0 sy, 0.0 ni, 36.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu16 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu17 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu18 : 83.4 us, 0.3 sy, 0.0 ni, 16.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu19 : 54.3 us, 0.0 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu20 : 90.7 us, 0.0 sy, 0.0 ni, 9.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu21 : 91.7 us, 0.0 sy, 0.0 ni, 8.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu22 : 91.4 us, 0.0 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu23 : 87.0 us, 0.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 97436048 total, 14773332 free, 31670192 used, 50992524 buff/cache
KiB Swap: 8191996 total, 7989884 free, 202112 used. 47788736 avail Mem | timestamp : 2023-01-09T15:54:07.000+0000 || updatedby : surymish || type : RESOLUTION SUMMARY || visibility : External || details : No response from Cu since dec 10th | nan | SNS-3655-K9 | ise-2.7.0.356.SPA.x86_64.iso | nan | nan | 3 | nan | Configuration Assistance (process not intuitive, too complex, inconsistent...) | CISE | Identity Services Engine (ISE) - 3.0 | ISE Performance (High CPU / Memory / IO / GUI Slowness) | nan | nan | nan | nan | nan | nan |
694888348 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Software Version: -- => 16.12.4
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE C9300 - Device is Experiencing TCAM Exhaustion 97.0%. Layer2 TCAM Usage
Total Mac Addresses for this criterion: 583
Total Mac Addresses installed by LISP: REMOTE: 32768
E1-07-CNT-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 29060/1023
ERC-01-CNT2-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 30542/1024
SDA FE C9300 - Device is Experiencing TCAM Exhaustion 97.0%. Layer2 TCAM Usage
Total Mac Addresses for this criterion: 583
Total Mac Addresses installed by LISP: REMOTE: 32768
E1-07-CNT-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 29060/1023
ERC-01-CNT2-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 30542/1024
timestamp : 2023-02-10T13:20:08.000+0000 || updatedby : karanand || type : RESOLUTION SUMMARY || visibility : External || details : Closing the case as we have not had any response to the email over multiple attempts. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE C9300 - Device is Experiencing TCAM Exhaustion 97.0%. Layer2 TCAM Usage
Total Mac Addresses for this criterion: 583
Total Mac Addresses installed by LISP: REMOTE: 32768
E1-07-CNT-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 29060/1023
ERC-01-CNT2-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 30542/1024
SDA FE C9300 - Device is Experiencing TCAM Exhaustion 97.0%. Layer2 TCAM Usage
Total Mac Addresses for this criterion: 583
Total Mac Addresses installed by LISP: REMOTE: 32768
E1-07-CNT-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 29060/1023
ERC-01-CNT2-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 30542/1024
timestamp : 2023-02-10T13:20:08.000+0000 || updatedby : karanand || type : RESOLUTION SUMMARY || visibility : External || details : Closing the case as we have not had any response to the email over multiple attempts. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE C9300 - Device is Experiencing TCAM Exhaustion 97.0%. Layer2 TCAM Usage
Total Mac Addresses for this criterion: 583
Total Mac Addresses installed by LISP: REMOTE: 32768
E1-07-CNT-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 29060/1023
ERC-01-CNT2-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 30542/1024 | SDA FE C9300 - Device is Experiencing TCAM Exhaustion 97.0%. Layer2 TCAM Usage
Total Mac Addresses for this criterion: 583
Total Mac Addresses installed by LISP: REMOTE: 32768
E1-07-CNT-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 29060/1023
ERC-01-CNT2-ES1#show platform hardware fed switch active fwd-asic resource tcam utilization | inc Unicast
Unicast MAC addresses 32768/1024 30542/1024 | timestamp : 2023-02-10T13:20:08.000+0000 || updatedby : karanand || type : RESOLUTION SUMMARY || visibility : External || details : Closing the case as we have not had any response to the email over multiple attempts. | nan | C9300-48U | cat9k_iosxe.16.12.04.SPA.bin | nan | nan | 3 | nan | Usability -other than config (product hard to use, no console port...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | nan | nan | nan | nan | nan | nan |
695942943 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 9.16.2.3/ 9.14.2.4/ 9.14.2.4/ 9.14.1 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Adaptive Security Appliance
Subtechnology: ASA Firepower Devices - Non-VPN
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: FPRUHI
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Team,
We are seeing that the some connections are getting dropped and the packets are note seen on interfaces.
PFA image
Source : 172.24.140.69
Destination : 10.245.0.114
Port : 7236
Will atach the captures and logs to the case..
Hi Team,
We are seeing that the some connections are getting dropped and the packets are note seen on interfaces.
PFA image
Source : 172.24.140.69
Destination : 10.245.0.114
Port : 7236
Will atach the captures and logs to the case..
Configuration changes that need to be done:-
policy-map global_policy
no class tcp_bypass
!
class any-tcp
set connection advanced-options tcp-state-bypas
!
wr mem
Verification:-
show runn policy-map
show connection
show connection detail
It was asked to close the service request further. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: FPR9K-SM-36/ FPR-C9300-AC/ FPR1150-ASA-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Adaptive Security Appliance
Subtechnology: ASA Firepower Devices - Non-VPN
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: FPRUHI
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Team,
We are seeing that the some connections are getting dropped and the packets are note seen on interfaces.
PFA image
Source : 172.24.140.69
Destination : 10.245.0.114
Port : 7236
Will atach the captures and logs to the case..
Hi Team,
We are seeing that the some connections are getting dropped and the packets are note seen on interfaces.
PFA image
Source : 172.24.140.69
Destination : 10.245.0.114
Port : 7236
Will atach the captures and logs to the case..
Configuration changes that need to be done:-
policy-map global_policy
no class tcp_bypass
!
class any-tcp
set connection advanced-options tcp-state-bypas
!
wr mem
Verification:-
show runn policy-map
show connection
show connection detail
It was asked to close the service request further. | Technology: Adaptive Security Appliance
Subtechnology: ASA Firepower Devices - Non-VPN
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: FPRUHI
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Team,
We are seeing that the some connections are getting dropped and the packets are note seen on interfaces.
PFA image
Source : 172.24.140.69
Destination : 10.245.0.114
Port : 7236
Will atach the captures and logs to the case.. | Hi Team,
We are seeing that the some connections are getting dropped and the packets are note seen on interfaces.
PFA image
Source : 172.24.140.69
Destination : 10.245.0.114
Port : 7236
Will atach the captures and logs to the case.. | Configuration changes that need to be done:-
policy-map global_policy
no class tcp_bypass
!
class any-tcp
set connection advanced-options tcp-state-bypas
!
wr mem
Verification:-
show runn policy-map
show connection
show connection detail
It was asked to close the service request further. | Connections getting drop on firepower running ASA | FPR-C9300-AC | 9.14(2)4 | 9.14(2)4 | 54.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | FPRUHI | Adaptive Security Appliance | ASA Firepower Devices - Non-VPN | 01t1C000006E6CbQAK | Error Messages, Logs, Debugs | ASA Firepower Devices - Non-VPN | Adaptive Security Appliance | 01t15000004dGB5AAM | CaseClosureFieldAutomation: Partial |
694624943 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Many Guest connecting to NUS_Guest WiFi are having intermittent internet connection.\
(TLDC-WL-WLC01) >show client detail c4:23:60:f8:68:9e
Client MAC Address............................... c4:23:60:f8:68:9e
Client Username ................................. c4:23:60:f8:68:9e
Client Webauth Username ......................... c4:23:60:f8:68:9e
Hostname: .......................................
Device Type: .................................... Unclassified
AP MAC Address................................... 84:f1:47:6c:bb:a0
AP Name.......................................... BIZ1-02-AP09
AP radio slot Id................................. 1
Client State..................................... Associated
User Authenticated by ........................... RADIUS Server
Client User Group................................ c4:23:60:f8:68:9e
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 17
Wireless LAN Network Name (SSID)................. NUS_Guest
Wireless LAN Profile Name........................ NUS_Guest_NUS_fa_F_a317b737
WLAN Profile check for roaming................... Disabled
Hotspot (802.11u)................................ Not Supported
Connected For ................................... 78 secs
BSSID............................................ 84:f1:47:6c:bb:ae
Channel.......................................... 64
IP Address....................................... 10.244.8.1
Gateway Address.................................. 10.244.0.1
Netmask.......................................... 255.255.192.0
--More-- or (q)uit
IPv6 Address..................................... fe80::c50c:74bb:1203:3386
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Client IPSK-TAG.................................. N/A
Status Code...................................... 0
Session Timeout.................................. 43200
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
Avg Uplink data Rate............................. 0
Burst Uplink data Rate........................... 0
Avg Uplink Real time data Rate................... 0
Burst Uplink Real Time data Rate................. 0
802.1P Priority Tag.............................. disabled
Security Group Tag............................... 6
KTS CAC Capability............................... No
Qos Map Capability............................... Yes
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
--More-- or (q)uit
Current Rate..................................... 12.0
Supported Rates.................................. 6.0,12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ No
Policy Manager State............................. WEBAUTH_REQD
Pre-auth IPv4 ACL Name........................... none
Pre-auth IPv4 ACL Applied Status................. Unavailable
Pre-auth IPv6 ACL Name........................... none
Pre-auth IPv6 ACL Applied Status................. Unavailable
Pre-auth Flex IPv4 ACL Name...................... none
Pre-auth Flex IPv4 ACL Applied Status............ Unavailable
Pre-auth Flex IPv6 ACL Name...................... none
Pre-auth Flex IPv6 ACL Applied Status............ Unavailable
Pre-auth redirect URL............................ none
Audit Session ID................................. none
AAA Role Type.................................... none
Acct Interim Interval............................ 0
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
AAA FlexConnect ACL Applied Status............... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
--More-- or (q)uit
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Post-auth Flex IPv6 ACL Name..................... none
Post-auth Flex IPv6 ACL Applied Status........... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
URL ACL Name..................................... none
URL ACL Applied Status........................... Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Disabled
mDNS Profile Name................................ none
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ management
VLAN............................................. 390
Quarantine VLAN.................................. 0
Access VLAN...................................... 390
Local Bridging VLAN.............................. 390
Client Capabilities:
--More-- or (q)uit
Radio Capability........................... 802.11ax
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 250
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Implemented
Non-Operable Channels............................ None
Non-Prefer Channels.............................. None
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
DNS Server details:
DNS server IP ............................. 0.0.0.0
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
--More-- or (q)uit
Client Dhcp Required: True
Allowed (URL)IP Addresses
-------------------------
AVC Profile Name: ............................... none
OpenDns Profile Name: ........................... none
Fastlane Client: ................................ No
Max DSCP: ....................................... 0
Nas Identifier: ................................. TLDC-WL-WLC01
Fabric Configuration
--------------------
Fabric Status: .................................. Enabled
Vnid: ........................................... 8211
Client RLOC IP registered to MS: ................ 172.18.1.133
Clients RLOC IP : .............................. 172.18.1.133
Fabric Flex Avc Policy Name: ....................
Fabric Statistics
--------------------
Primary Map Server : 172.18.0.129
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
--More-- or (q)uit
ms_stattype_registrations_deregistrations.... 0
Secondary Map Server : 172.18.0.130
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
ms_stattype_registrations_deregistrations.... 0
Client Statistics:
Number of Bytes Received................... 432456
Number of Bytes Sent....................... 401863
Total Number of Bytes Sent................. 401863
Total Number of Bytes Recv................. 432456
Number of Bytes Sent (last 90s)............ 51897
Number of Bytes Recv (last 90s)............ 53360
Number of Packets Received................. 3591
Number of Packets Sent..................... 3812
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
--More-- or (q)uit
Number of Data Retries..................... 435
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -64 dBm
Signal to Noise Ratio...................... 30 dB
Client Detected as Inactive................ No
Client RBACL Statistics:
Number of RBACL Allowed Packets............ 0
Number of RBACL Denied Packets............. 0
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
--More-- or (q)uit
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
BIZ1-02-AP10(slot 0)
antenna0: 35 secs ago.................... -45 dBm
antenna1: 35 secs ago.................... -45 dBm
BIZ1-02-AP10(slot 1)
antenna0: 80 secs ago.................... -43 dBm
antenna1: 80 secs ago.................... -43 dBm
BIZ1-02-AP15(slot 0)
antenna0: 35 secs ago.................... -75 dBm
antenna1: 35 secs ago.................... -75 dBm
BIZ1-02-AP15(slot 1)
antenna0: 80 secs ago.................... -80 dBm
antenna1: 80 secs ago.................... -80 dBm
BIZ1-02-AP24(slot 0)
antenna0: 130 secs ago................... -79 dBm
--More-- or (q)uit
antenna1: 130 secs ago................... -79 dBm
BIZ1-03-AP11(slot 0)
antenna0: 35 secs ago.................... -82 dBm
antenna1: 35 secs ago.................... -82 dBm
BIZ1-02-AP09(slot 0)
antenna0: 130 secs ago................... -48 dBm
antenna1: 130 secs ago................... -48 dBm
BIZ1-02-AP09(slot 1)
antenna0: 79 secs ago.................... -58 dBm
antenna1: 79 secs ago.................... -58 dBm
BIZ1-02-AP07(slot 1)
antenna0: 31 secs ago.................... -69 dBm
antenna1: 31 secs ago.................... -69 dBm
BIZ1-01-AP10(slot 0)
antenna0: 34 secs ago.................... -79 dBm
antenna1: 34 secs ago.................... -79 dBm
BIZ1-01-AP11(slot 0)
antenna0: 34 secs ago.................... -80 dBm
antenna1: 34 secs ago.................... -80 dBm
BIZ1-03-AP10(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-03-AP13(slot 0)
--More-- or (q)uit
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP13(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-02-AP14(slot 0)
antenna0: 130 secs ago................... -68 dBm
antenna1: 130 secs ago................... -68 dBm
BIZ1-02-AP14(slot 1)
antenna0: 33 secs ago.................... -71 dBm
antenna1: 33 secs ago.................... -71 dBm
BIZ1-03-AP12(slot 0)
antenna0: 130 secs ago................... -80 dBm
antenna1: 130 secs ago................... -80 dBm
BIZ1-03-AP12(slot 1)
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP12(slot 1)
antenna0: 79 secs ago.................... -55 dBm
antenna1: 79 secs ago.................... -55 dBm
BIZ1-01-AP02(slot 0)
antenna0: 35 secs ago.................... -80 dBm
antenna1: 35 secs ago.................... -80 dBm
--More-- or (q)uit
BIZ1-02-AP08(slot 0)
antenna0: 34 secs ago.................... -49 dBm
antenna1: 34 secs ago.................... -49 dBm
BIZ1-02-AP08(slot 1)
antenna0: 33 secs ago.................... -67 dBm
antenna1: 33 secs ago.................... -67 dBm
BIZ1-02-AP11(slot 0)
antenna0: 34 secs ago.................... -36 dBm
antenna1: 34 secs ago.................... -36 dBm
BIZ1-02-AP11(slot 1)
antenna0: 79 secs ago.................... -38 dBm
antenna1: 79 secs ago.................... -38 dBm
(TLDC-WL-WLC01) >
Many Guest connecting to NUS_Guest WiFi are having intermittent internet connection.\
(TLDC-WL-WLC01) >show client detail c4:23:60:f8:68:9e
Client MAC Address............................... c4:23:60:f8:68:9e
Client Username ................................. c4:23:60:f8:68:9e
Client Webauth Username ......................... c4:23:60:f8:68:9e
Hostname: .......................................
Device Type: .................................... Unclassified
AP MAC Address................................... 84:f1:47:6c:bb:a0
AP Name.......................................... BIZ1-02-AP09
AP radio slot Id................................. 1
Client State..................................... Associated
User Authenticated by ........................... RADIUS Server
Client User Group................................ c4:23:60:f8:68:9e
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 17
Wireless LAN Network Name (SSID)................. NUS_Guest
Wireless LAN Profile Name........................ NUS_Guest_NUS_fa_F_a317b737
WLAN Profile check for roaming................... Disabled
Hotspot (802.11u)................................ Not Supported
Connected For ................................... 78 secs
BSSID............................................ 84:f1:47:6c:bb:ae
Channel.......................................... 64
IP Address....................................... 10.244.8.1
Gateway Address.................................. 10.244.0.1
Netmask.......................................... 255.255.192.0
--More-- or (q)uit
IPv6 Address..................................... fe80::c50c:74bb:1203:3386
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Client IPSK-TAG.................................. N/A
Status Code...................................... 0
Session Timeout.................................. 43200
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
Avg Uplink data Rate............................. 0
Burst Uplink data Rate........................... 0
Avg Uplink Real time data Rate................... 0
Burst Uplink Real Time data Rate................. 0
802.1P Priority Tag.............................. disabled
Security Group Tag............................... 6
KTS CAC Capability............................... No
Qos Map Capability............................... Yes
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
--More-- or (q)uit
Current Rate..................................... 12.0
Supported Rates.................................. 6.0,12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ No
Policy Manager State............................. WEBAUTH_REQD
Pre-auth IPv4 ACL Name........................... none
Pre-auth IPv4 ACL Applied Status................. Unavailable
Pre-auth IPv6 ACL Name........................... none
Pre-auth IPv6 ACL Applied Status................. Unavailable
Pre-auth Flex IPv4 ACL Name...................... none
Pre-auth Flex IPv4 ACL Applied Status............ Unavailable
Pre-auth Flex IPv6 ACL Name...................... none
Pre-auth Flex IPv6 ACL Applied Status............ Unavailable
Pre-auth redirect URL............................ none
Audit Session ID................................. none
AAA Role Type.................................... none
Acct Interim Interval............................ 0
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
AAA FlexConnect ACL Applied Status............... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
--More-- or (q)uit
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Post-auth Flex IPv6 ACL Name..................... none
Post-auth Flex IPv6 ACL Applied Status........... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
URL ACL Name..................................... none
URL ACL Applied Status........................... Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Disabled
mDNS Profile Name................................ none
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ management
VLAN............................................. 390
Quarantine VLAN.................................. 0
Access VLAN...................................... 390
Local Bridging VLAN.............................. 390
Client Capabilities:
--More-- or (q)uit
Radio Capability........................... 802.11ax
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 250
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Implemented
Non-Operable Channels............................ None
Non-Prefer Channels.............................. None
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
DNS Server details:
DNS server IP ............................. 0.0.0.0
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
--More-- or (q)uit
Client Dhcp Required: True
Allowed (URL)IP Addresses
-------------------------
AVC Profile Name: ............................... none
OpenDns Profile Name: ........................... none
Fastlane Client: ................................ No
Max DSCP: ....................................... 0
Nas Identifier: ................................. TLDC-WL-WLC01
Fabric Configuration
--------------------
Fabric Status: .................................. Enabled
Vnid: ........................................... 8211
Client RLOC IP registered to MS: ................ 172.18.1.133
Clients RLOC IP : .............................. 172.18.1.133
Fabric Flex Avc Policy Name: ....................
Fabric Statistics
--------------------
Primary Map Server : 172.18.0.129
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
--More-- or (q)uit
ms_stattype_registrations_deregistrations.... 0
Secondary Map Server : 172.18.0.130
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
ms_stattype_registrations_deregistrations.... 0
Client Statistics:
Number of Bytes Received................... 432456
Number of Bytes Sent....................... 401863
Total Number of Bytes Sent................. 401863
Total Number of Bytes Recv................. 432456
Number of Bytes Sent (last 90s)............ 51897
Number of Bytes Recv (last 90s)............ 53360
Number of Packets Received................. 3591
Number of Packets Sent..................... 3812
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
--More-- or (q)uit
Number of Data Retries..................... 435
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -64 dBm
Signal to Noise Ratio...................... 30 dB
Client Detected as Inactive................ No
Client RBACL Statistics:
Number of RBACL Allowed Packets............ 0
Number of RBACL Denied Packets............. 0
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
--More-- or (q)uit
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
BIZ1-02-AP10(slot 0)
antenna0: 35 secs ago.................... -45 dBm
antenna1: 35 secs ago.................... -45 dBm
BIZ1-02-AP10(slot 1)
antenna0: 80 secs ago.................... -43 dBm
antenna1: 80 secs ago.................... -43 dBm
BIZ1-02-AP15(slot 0)
antenna0: 35 secs ago.................... -75 dBm
antenna1: 35 secs ago.................... -75 dBm
BIZ1-02-AP15(slot 1)
antenna0: 80 secs ago.................... -80 dBm
antenna1: 80 secs ago.................... -80 dBm
BIZ1-02-AP24(slot 0)
antenna0: 130 secs ago................... -79 dBm
--More-- or (q)uit
antenna1: 130 secs ago................... -79 dBm
BIZ1-03-AP11(slot 0)
antenna0: 35 secs ago.................... -82 dBm
antenna1: 35 secs ago.................... -82 dBm
BIZ1-02-AP09(slot 0)
antenna0: 130 secs ago................... -48 dBm
antenna1: 130 secs ago................... -48 dBm
BIZ1-02-AP09(slot 1)
antenna0: 79 secs ago.................... -58 dBm
antenna1: 79 secs ago.................... -58 dBm
BIZ1-02-AP07(slot 1)
antenna0: 31 secs ago.................... -69 dBm
antenna1: 31 secs ago.................... -69 dBm
BIZ1-01-AP10(slot 0)
antenna0: 34 secs ago.................... -79 dBm
antenna1: 34 secs ago.................... -79 dBm
BIZ1-01-AP11(slot 0)
antenna0: 34 secs ago.................... -80 dBm
antenna1: 34 secs ago.................... -80 dBm
BIZ1-03-AP10(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-03-AP13(slot 0)
--More-- or (q)uit
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP13(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-02-AP14(slot 0)
antenna0: 130 secs ago................... -68 dBm
antenna1: 130 secs ago................... -68 dBm
BIZ1-02-AP14(slot 1)
antenna0: 33 secs ago.................... -71 dBm
antenna1: 33 secs ago.................... -71 dBm
BIZ1-03-AP12(slot 0)
antenna0: 130 secs ago................... -80 dBm
antenna1: 130 secs ago................... -80 dBm
BIZ1-03-AP12(slot 1)
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP12(slot 1)
antenna0: 79 secs ago.................... -55 dBm
antenna1: 79 secs ago.................... -55 dBm
BIZ1-01-AP02(slot 0)
antenna0: 35 secs ago.................... -80 dBm
antenna1: 35 secs ago.................... -80 dBm
--More-- or (q)uit
BIZ1-02-AP08(slot 0)
antenna0: 34 secs ago.................... -49 dBm
antenna1: 34 secs ago.................... -49 dBm
BIZ1-02-AP08(slot 1)
antenna0: 33 secs ago.................... -67 dBm
antenna1: 33 secs ago.................... -67 dBm
BIZ1-02-AP11(slot 0)
antenna0: 34 secs ago.................... -36 dBm
antenna1: 34 secs ago.................... -36 dBm
BIZ1-02-AP11(slot 1)
antenna0: 79 secs ago.................... -38 dBm
antenna1: 79 secs ago.................... -38 dBm
(TLDC-WL-WLC01) >
Issue: Guest Clients were not able to connect due to the captive portal not redirecting.
Steps Taken:
* Assessed logs collected from cu and found some bugs which match the issue:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvh20238
* Asked customer to implement following workaround:
-Remove the ACL from the FlexConnect Group and add it again.
OR
-Reboot the AP.
===============
Customer will be monitoring the issue and will open a new case if issue arises. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Many Guest connecting to NUS_Guest WiFi are having intermittent internet connection.\
(TLDC-WL-WLC01) >show client detail c4:23:60:f8:68:9e
Client MAC Address............................... c4:23:60:f8:68:9e
Client Username ................................. c4:23:60:f8:68:9e
Client Webauth Username ......................... c4:23:60:f8:68:9e
Hostname: .......................................
Device Type: .................................... Unclassified
AP MAC Address................................... 84:f1:47:6c:bb:a0
AP Name.......................................... BIZ1-02-AP09
AP radio slot Id................................. 1
Client State..................................... Associated
User Authenticated by ........................... RADIUS Server
Client User Group................................ c4:23:60:f8:68:9e
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 17
Wireless LAN Network Name (SSID)................. NUS_Guest
Wireless LAN Profile Name........................ NUS_Guest_NUS_fa_F_a317b737
WLAN Profile check for roaming................... Disabled
Hotspot (802.11u)................................ Not Supported
Connected For ................................... 78 secs
BSSID............................................ 84:f1:47:6c:bb:ae
Channel.......................................... 64
IP Address....................................... 10.244.8.1
Gateway Address.................................. 10.244.0.1
Netmask.......................................... 255.255.192.0
--More-- or (q)uit
IPv6 Address..................................... fe80::c50c:74bb:1203:3386
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Client IPSK-TAG.................................. N/A
Status Code...................................... 0
Session Timeout.................................. 43200
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
Avg Uplink data Rate............................. 0
Burst Uplink data Rate........................... 0
Avg Uplink Real time data Rate................... 0
Burst Uplink Real Time data Rate................. 0
802.1P Priority Tag.............................. disabled
Security Group Tag............................... 6
KTS CAC Capability............................... No
Qos Map Capability............................... Yes
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
--More-- or (q)uit
Current Rate..................................... 12.0
Supported Rates.................................. 6.0,12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ No
Policy Manager State............................. WEBAUTH_REQD
Pre-auth IPv4 ACL Name........................... none
Pre-auth IPv4 ACL Applied Status................. Unavailable
Pre-auth IPv6 ACL Name........................... none
Pre-auth IPv6 ACL Applied Status................. Unavailable
Pre-auth Flex IPv4 ACL Name...................... none
Pre-auth Flex IPv4 ACL Applied Status............ Unavailable
Pre-auth Flex IPv6 ACL Name...................... none
Pre-auth Flex IPv6 ACL Applied Status............ Unavailable
Pre-auth redirect URL............................ none
Audit Session ID................................. none
AAA Role Type.................................... none
Acct Interim Interval............................ 0
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
AAA FlexConnect ACL Applied Status............... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
--More-- or (q)uit
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Post-auth Flex IPv6 ACL Name..................... none
Post-auth Flex IPv6 ACL Applied Status........... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
URL ACL Name..................................... none
URL ACL Applied Status........................... Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Disabled
mDNS Profile Name................................ none
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ management
VLAN............................................. 390
Quarantine VLAN.................................. 0
Access VLAN...................................... 390
Local Bridging VLAN.............................. 390
Client Capabilities:
--More-- or (q)uit
Radio Capability........................... 802.11ax
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 250
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Implemented
Non-Operable Channels............................ None
Non-Prefer Channels.............................. None
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
DNS Server details:
DNS server IP ............................. 0.0.0.0
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
--More-- or (q)uit
Client Dhcp Required: True
Allowed (URL)IP Addresses
-------------------------
AVC Profile Name: ............................... none
OpenDns Profile Name: ........................... none
Fastlane Client: ................................ No
Max DSCP: ....................................... 0
Nas Identifier: ................................. TLDC-WL-WLC01
Fabric Configuration
--------------------
Fabric Status: .................................. Enabled
Vnid: ........................................... 8211
Client RLOC IP registered to MS: ................ 172.18.1.133
Clients RLOC IP : .............................. 172.18.1.133
Fabric Flex Avc Policy Name: ....................
Fabric Statistics
--------------------
Primary Map Server : 172.18.0.129
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
--More-- or (q)uit
ms_stattype_registrations_deregistrations.... 0
Secondary Map Server : 172.18.0.130
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
ms_stattype_registrations_deregistrations.... 0
Client Statistics:
Number of Bytes Received................... 432456
Number of Bytes Sent....................... 401863
Total Number of Bytes Sent................. 401863
Total Number of Bytes Recv................. 432456
Number of Bytes Sent (last 90s)............ 51897
Number of Bytes Recv (last 90s)............ 53360
Number of Packets Received................. 3591
Number of Packets Sent..................... 3812
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
--More-- or (q)uit
Number of Data Retries..................... 435
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -64 dBm
Signal to Noise Ratio...................... 30 dB
Client Detected as Inactive................ No
Client RBACL Statistics:
Number of RBACL Allowed Packets............ 0
Number of RBACL Denied Packets............. 0
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
--More-- or (q)uit
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
BIZ1-02-AP10(slot 0)
antenna0: 35 secs ago.................... -45 dBm
antenna1: 35 secs ago.................... -45 dBm
BIZ1-02-AP10(slot 1)
antenna0: 80 secs ago.................... -43 dBm
antenna1: 80 secs ago.................... -43 dBm
BIZ1-02-AP15(slot 0)
antenna0: 35 secs ago.................... -75 dBm
antenna1: 35 secs ago.................... -75 dBm
BIZ1-02-AP15(slot 1)
antenna0: 80 secs ago.................... -80 dBm
antenna1: 80 secs ago.................... -80 dBm
BIZ1-02-AP24(slot 0)
antenna0: 130 secs ago................... -79 dBm
--More-- or (q)uit
antenna1: 130 secs ago................... -79 dBm
BIZ1-03-AP11(slot 0)
antenna0: 35 secs ago.................... -82 dBm
antenna1: 35 secs ago.................... -82 dBm
BIZ1-02-AP09(slot 0)
antenna0: 130 secs ago................... -48 dBm
antenna1: 130 secs ago................... -48 dBm
BIZ1-02-AP09(slot 1)
antenna0: 79 secs ago.................... -58 dBm
antenna1: 79 secs ago.................... -58 dBm
BIZ1-02-AP07(slot 1)
antenna0: 31 secs ago.................... -69 dBm
antenna1: 31 secs ago.................... -69 dBm
BIZ1-01-AP10(slot 0)
antenna0: 34 secs ago.................... -79 dBm
antenna1: 34 secs ago.................... -79 dBm
BIZ1-01-AP11(slot 0)
antenna0: 34 secs ago.................... -80 dBm
antenna1: 34 secs ago.................... -80 dBm
BIZ1-03-AP10(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-03-AP13(slot 0)
--More-- or (q)uit
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP13(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-02-AP14(slot 0)
antenna0: 130 secs ago................... -68 dBm
antenna1: 130 secs ago................... -68 dBm
BIZ1-02-AP14(slot 1)
antenna0: 33 secs ago.................... -71 dBm
antenna1: 33 secs ago.................... -71 dBm
BIZ1-03-AP12(slot 0)
antenna0: 130 secs ago................... -80 dBm
antenna1: 130 secs ago................... -80 dBm
BIZ1-03-AP12(slot 1)
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP12(slot 1)
antenna0: 79 secs ago.................... -55 dBm
antenna1: 79 secs ago.................... -55 dBm
BIZ1-01-AP02(slot 0)
antenna0: 35 secs ago.................... -80 dBm
antenna1: 35 secs ago.................... -80 dBm
--More-- or (q)uit
BIZ1-02-AP08(slot 0)
antenna0: 34 secs ago.................... -49 dBm
antenna1: 34 secs ago.................... -49 dBm
BIZ1-02-AP08(slot 1)
antenna0: 33 secs ago.................... -67 dBm
antenna1: 33 secs ago.................... -67 dBm
BIZ1-02-AP11(slot 0)
antenna0: 34 secs ago.................... -36 dBm
antenna1: 34 secs ago.................... -36 dBm
BIZ1-02-AP11(slot 1)
antenna0: 79 secs ago.................... -38 dBm
antenna1: 79 secs ago.................... -38 dBm
(TLDC-WL-WLC01) >
Many Guest connecting to NUS_Guest WiFi are having intermittent internet connection.\
(TLDC-WL-WLC01) >show client detail c4:23:60:f8:68:9e
Client MAC Address............................... c4:23:60:f8:68:9e
Client Username ................................. c4:23:60:f8:68:9e
Client Webauth Username ......................... c4:23:60:f8:68:9e
Hostname: .......................................
Device Type: .................................... Unclassified
AP MAC Address................................... 84:f1:47:6c:bb:a0
AP Name.......................................... BIZ1-02-AP09
AP radio slot Id................................. 1
Client State..................................... Associated
User Authenticated by ........................... RADIUS Server
Client User Group................................ c4:23:60:f8:68:9e
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 17
Wireless LAN Network Name (SSID)................. NUS_Guest
Wireless LAN Profile Name........................ NUS_Guest_NUS_fa_F_a317b737
WLAN Profile check for roaming................... Disabled
Hotspot (802.11u)................................ Not Supported
Connected For ................................... 78 secs
BSSID............................................ 84:f1:47:6c:bb:ae
Channel.......................................... 64
IP Address....................................... 10.244.8.1
Gateway Address.................................. 10.244.0.1
Netmask.......................................... 255.255.192.0
--More-- or (q)uit
IPv6 Address..................................... fe80::c50c:74bb:1203:3386
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Client IPSK-TAG.................................. N/A
Status Code...................................... 0
Session Timeout.................................. 43200
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
Avg Uplink data Rate............................. 0
Burst Uplink data Rate........................... 0
Avg Uplink Real time data Rate................... 0
Burst Uplink Real Time data Rate................. 0
802.1P Priority Tag.............................. disabled
Security Group Tag............................... 6
KTS CAC Capability............................... No
Qos Map Capability............................... Yes
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
--More-- or (q)uit
Current Rate..................................... 12.0
Supported Rates.................................. 6.0,12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ No
Policy Manager State............................. WEBAUTH_REQD
Pre-auth IPv4 ACL Name........................... none
Pre-auth IPv4 ACL Applied Status................. Unavailable
Pre-auth IPv6 ACL Name........................... none
Pre-auth IPv6 ACL Applied Status................. Unavailable
Pre-auth Flex IPv4 ACL Name...................... none
Pre-auth Flex IPv4 ACL Applied Status............ Unavailable
Pre-auth Flex IPv6 ACL Name...................... none
Pre-auth Flex IPv6 ACL Applied Status............ Unavailable
Pre-auth redirect URL............................ none
Audit Session ID................................. none
AAA Role Type.................................... none
Acct Interim Interval............................ 0
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
AAA FlexConnect ACL Applied Status............... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
--More-- or (q)uit
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Post-auth Flex IPv6 ACL Name..................... none
Post-auth Flex IPv6 ACL Applied Status........... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
URL ACL Name..................................... none
URL ACL Applied Status........................... Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Disabled
mDNS Profile Name................................ none
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ management
VLAN............................................. 390
Quarantine VLAN.................................. 0
Access VLAN...................................... 390
Local Bridging VLAN.............................. 390
Client Capabilities:
--More-- or (q)uit
Radio Capability........................... 802.11ax
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 250
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Implemented
Non-Operable Channels............................ None
Non-Prefer Channels.............................. None
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
DNS Server details:
DNS server IP ............................. 0.0.0.0
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
--More-- or (q)uit
Client Dhcp Required: True
Allowed (URL)IP Addresses
-------------------------
AVC Profile Name: ............................... none
OpenDns Profile Name: ........................... none
Fastlane Client: ................................ No
Max DSCP: ....................................... 0
Nas Identifier: ................................. TLDC-WL-WLC01
Fabric Configuration
--------------------
Fabric Status: .................................. Enabled
Vnid: ........................................... 8211
Client RLOC IP registered to MS: ................ 172.18.1.133
Clients RLOC IP : .............................. 172.18.1.133
Fabric Flex Avc Policy Name: ....................
Fabric Statistics
--------------------
Primary Map Server : 172.18.0.129
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
--More-- or (q)uit
ms_stattype_registrations_deregistrations.... 0
Secondary Map Server : 172.18.0.130
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
ms_stattype_registrations_deregistrations.... 0
Client Statistics:
Number of Bytes Received................... 432456
Number of Bytes Sent....................... 401863
Total Number of Bytes Sent................. 401863
Total Number of Bytes Recv................. 432456
Number of Bytes Sent (last 90s)............ 51897
Number of Bytes Recv (last 90s)............ 53360
Number of Packets Received................. 3591
Number of Packets Sent..................... 3812
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
--More-- or (q)uit
Number of Data Retries..................... 435
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -64 dBm
Signal to Noise Ratio...................... 30 dB
Client Detected as Inactive................ No
Client RBACL Statistics:
Number of RBACL Allowed Packets............ 0
Number of RBACL Denied Packets............. 0
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
--More-- or (q)uit
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
BIZ1-02-AP10(slot 0)
antenna0: 35 secs ago.................... -45 dBm
antenna1: 35 secs ago.................... -45 dBm
BIZ1-02-AP10(slot 1)
antenna0: 80 secs ago.................... -43 dBm
antenna1: 80 secs ago.................... -43 dBm
BIZ1-02-AP15(slot 0)
antenna0: 35 secs ago.................... -75 dBm
antenna1: 35 secs ago.................... -75 dBm
BIZ1-02-AP15(slot 1)
antenna0: 80 secs ago.................... -80 dBm
antenna1: 80 secs ago.................... -80 dBm
BIZ1-02-AP24(slot 0)
antenna0: 130 secs ago................... -79 dBm
--More-- or (q)uit
antenna1: 130 secs ago................... -79 dBm
BIZ1-03-AP11(slot 0)
antenna0: 35 secs ago.................... -82 dBm
antenna1: 35 secs ago.................... -82 dBm
BIZ1-02-AP09(slot 0)
antenna0: 130 secs ago................... -48 dBm
antenna1: 130 secs ago................... -48 dBm
BIZ1-02-AP09(slot 1)
antenna0: 79 secs ago.................... -58 dBm
antenna1: 79 secs ago.................... -58 dBm
BIZ1-02-AP07(slot 1)
antenna0: 31 secs ago.................... -69 dBm
antenna1: 31 secs ago.................... -69 dBm
BIZ1-01-AP10(slot 0)
antenna0: 34 secs ago.................... -79 dBm
antenna1: 34 secs ago.................... -79 dBm
BIZ1-01-AP11(slot 0)
antenna0: 34 secs ago.................... -80 dBm
antenna1: 34 secs ago.................... -80 dBm
BIZ1-03-AP10(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-03-AP13(slot 0)
--More-- or (q)uit
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP13(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-02-AP14(slot 0)
antenna0: 130 secs ago................... -68 dBm
antenna1: 130 secs ago................... -68 dBm
BIZ1-02-AP14(slot 1)
antenna0: 33 secs ago.................... -71 dBm
antenna1: 33 secs ago.................... -71 dBm
BIZ1-03-AP12(slot 0)
antenna0: 130 secs ago................... -80 dBm
antenna1: 130 secs ago................... -80 dBm
BIZ1-03-AP12(slot 1)
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP12(slot 1)
antenna0: 79 secs ago.................... -55 dBm
antenna1: 79 secs ago.................... -55 dBm
BIZ1-01-AP02(slot 0)
antenna0: 35 secs ago.................... -80 dBm
antenna1: 35 secs ago.................... -80 dBm
--More-- or (q)uit
BIZ1-02-AP08(slot 0)
antenna0: 34 secs ago.................... -49 dBm
antenna1: 34 secs ago.................... -49 dBm
BIZ1-02-AP08(slot 1)
antenna0: 33 secs ago.................... -67 dBm
antenna1: 33 secs ago.................... -67 dBm
BIZ1-02-AP11(slot 0)
antenna0: 34 secs ago.................... -36 dBm
antenna1: 34 secs ago.................... -36 dBm
BIZ1-02-AP11(slot 1)
antenna0: 79 secs ago.................... -38 dBm
antenna1: 79 secs ago.................... -38 dBm
(TLDC-WL-WLC01) >
Issue: Guest Clients were not able to connect due to the captive portal not redirecting.
Steps Taken:
* Assessed logs collected from cu and found some bugs which match the issue:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvh20238
* Asked customer to implement following workaround:
-Remove the ACL from the FlexConnect Group and add it again.
OR
-Reboot the AP.
===============
Customer will be monitoring the issue and will open a new case if issue arises. | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Many Guest connecting to NUS_Guest WiFi are having intermittent internet connection.\
(TLDC-WL-WLC01) >show client detail c4:23:60:f8:68:9e
Client MAC Address............................... c4:23:60:f8:68:9e
Client Username ................................. c4:23:60:f8:68:9e
Client Webauth Username ......................... c4:23:60:f8:68:9e
Hostname: .......................................
Device Type: .................................... Unclassified
AP MAC Address................................... 84:f1:47:6c:bb:a0
AP Name.......................................... BIZ1-02-AP09
AP radio slot Id................................. 1
Client State..................................... Associated
User Authenticated by ........................... RADIUS Server
Client User Group................................ c4:23:60:f8:68:9e
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 17
Wireless LAN Network Name (SSID)................. NUS_Guest
Wireless LAN Profile Name........................ NUS_Guest_NUS_fa_F_a317b737
WLAN Profile check for roaming................... Disabled
Hotspot (802.11u)................................ Not Supported
Connected For ................................... 78 secs
BSSID............................................ 84:f1:47:6c:bb:ae
Channel.......................................... 64
IP Address....................................... 10.244.8.1
Gateway Address.................................. 10.244.0.1
Netmask.......................................... 255.255.192.0
--More-- or (q)uit
IPv6 Address..................................... fe80::c50c:74bb:1203:3386
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Client IPSK-TAG.................................. N/A
Status Code...................................... 0
Session Timeout.................................. 43200
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
Avg Uplink data Rate............................. 0
Burst Uplink data Rate........................... 0
Avg Uplink Real time data Rate................... 0
Burst Uplink Real Time data Rate................. 0
802.1P Priority Tag.............................. disabled
Security Group Tag............................... 6
KTS CAC Capability............................... No
Qos Map Capability............................... Yes
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
--More-- or (q)uit
Current Rate..................................... 12.0
Supported Rates.................................. 6.0,12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ No
Policy Manager State............................. WEBAUTH_REQD
Pre-auth IPv4 ACL Name........................... none
Pre-auth IPv4 ACL Applied Status................. Unavailable
Pre-auth IPv6 ACL Name........................... none
Pre-auth IPv6 ACL Applied Status................. Unavailable
Pre-auth Flex IPv4 ACL Name...................... none
Pre-auth Flex IPv4 ACL Applied Status............ Unavailable
Pre-auth Flex IPv6 ACL Name...................... none
Pre-auth Flex IPv6 ACL Applied Status............ Unavailable
Pre-auth redirect URL............................ none
Audit Session ID................................. none
AAA Role Type.................................... none
Acct Interim Interval............................ 0
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
AAA FlexConnect ACL Applied Status............... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
--More-- or (q)uit
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Post-auth Flex IPv6 ACL Name..................... none
Post-auth Flex IPv6 ACL Applied Status........... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
URL ACL Name..................................... none
URL ACL Applied Status........................... Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Disabled
mDNS Profile Name................................ none
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ management
VLAN............................................. 390
Quarantine VLAN.................................. 0
Access VLAN...................................... 390
Local Bridging VLAN.............................. 390
Client Capabilities:
--More-- or (q)uit
Radio Capability........................... 802.11ax
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 250
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Implemented
Non-Operable Channels............................ None
Non-Prefer Channels.............................. None
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
DNS Server details:
DNS server IP ............................. 0.0.0.0
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
--More-- or (q)uit
Client Dhcp Required: True
Allowed (URL)IP Addresses
-------------------------
AVC Profile Name: ............................... none
OpenDns Profile Name: ........................... none
Fastlane Client: ................................ No
Max DSCP: ....................................... 0
Nas Identifier: ................................. TLDC-WL-WLC01
Fabric Configuration
--------------------
Fabric Status: .................................. Enabled
Vnid: ........................................... 8211
Client RLOC IP registered to MS: ................ 172.18.1.133
Clients RLOC IP : .............................. 172.18.1.133
Fabric Flex Avc Policy Name: ....................
Fabric Statistics
--------------------
Primary Map Server : 172.18.0.129
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
--More-- or (q)uit
ms_stattype_registrations_deregistrations.... 0
Secondary Map Server : 172.18.0.130
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
ms_stattype_registrations_deregistrations.... 0
Client Statistics:
Number of Bytes Received................... 432456
Number of Bytes Sent....................... 401863
Total Number of Bytes Sent................. 401863
Total Number of Bytes Recv................. 432456
Number of Bytes Sent (last 90s)............ 51897
Number of Bytes Recv (last 90s)............ 53360
Number of Packets Received................. 3591
Number of Packets Sent..................... 3812
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
--More-- or (q)uit
Number of Data Retries..................... 435
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -64 dBm
Signal to Noise Ratio...................... 30 dB
Client Detected as Inactive................ No
Client RBACL Statistics:
Number of RBACL Allowed Packets............ 0
Number of RBACL Denied Packets............. 0
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
--More-- or (q)uit
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
BIZ1-02-AP10(slot 0)
antenna0: 35 secs ago.................... -45 dBm
antenna1: 35 secs ago.................... -45 dBm
BIZ1-02-AP10(slot 1)
antenna0: 80 secs ago.................... -43 dBm
antenna1: 80 secs ago.................... -43 dBm
BIZ1-02-AP15(slot 0)
antenna0: 35 secs ago.................... -75 dBm
antenna1: 35 secs ago.................... -75 dBm
BIZ1-02-AP15(slot 1)
antenna0: 80 secs ago.................... -80 dBm
antenna1: 80 secs ago.................... -80 dBm
BIZ1-02-AP24(slot 0)
antenna0: 130 secs ago................... -79 dBm
--More-- or (q)uit
antenna1: 130 secs ago................... -79 dBm
BIZ1-03-AP11(slot 0)
antenna0: 35 secs ago.................... -82 dBm
antenna1: 35 secs ago.................... -82 dBm
BIZ1-02-AP09(slot 0)
antenna0: 130 secs ago................... -48 dBm
antenna1: 130 secs ago................... -48 dBm
BIZ1-02-AP09(slot 1)
antenna0: 79 secs ago.................... -58 dBm
antenna1: 79 secs ago.................... -58 dBm
BIZ1-02-AP07(slot 1)
antenna0: 31 secs ago.................... -69 dBm
antenna1: 31 secs ago.................... -69 dBm
BIZ1-01-AP10(slot 0)
antenna0: 34 secs ago.................... -79 dBm
antenna1: 34 secs ago.................... -79 dBm
BIZ1-01-AP11(slot 0)
antenna0: 34 secs ago.................... -80 dBm
antenna1: 34 secs ago.................... -80 dBm
BIZ1-03-AP10(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-03-AP13(slot 0)
--More-- or (q)uit
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP13(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-02-AP14(slot 0)
antenna0: 130 secs ago................... -68 dBm
antenna1: 130 secs ago................... -68 dBm
BIZ1-02-AP14(slot 1)
antenna0: 33 secs ago.................... -71 dBm
antenna1: 33 secs ago.................... -71 dBm
BIZ1-03-AP12(slot 0)
antenna0: 130 secs ago................... -80 dBm
antenna1: 130 secs ago................... -80 dBm
BIZ1-03-AP12(slot 1)
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP12(slot 1)
antenna0: 79 secs ago.................... -55 dBm
antenna1: 79 secs ago.................... -55 dBm
BIZ1-01-AP02(slot 0)
antenna0: 35 secs ago.................... -80 dBm
antenna1: 35 secs ago.................... -80 dBm
--More-- or (q)uit
BIZ1-02-AP08(slot 0)
antenna0: 34 secs ago.................... -49 dBm
antenna1: 34 secs ago.................... -49 dBm
BIZ1-02-AP08(slot 1)
antenna0: 33 secs ago.................... -67 dBm
antenna1: 33 secs ago.................... -67 dBm
BIZ1-02-AP11(slot 0)
antenna0: 34 secs ago.................... -36 dBm
antenna1: 34 secs ago.................... -36 dBm
BIZ1-02-AP11(slot 1)
antenna0: 79 secs ago.................... -38 dBm
antenna1: 79 secs ago.................... -38 dBm
(TLDC-WL-WLC01) > | Many Guest connecting to NUS_Guest WiFi are having intermittent internet connection.\
(TLDC-WL-WLC01) >show client detail c4:23:60:f8:68:9e
Client MAC Address............................... c4:23:60:f8:68:9e
Client Username ................................. c4:23:60:f8:68:9e
Client Webauth Username ......................... c4:23:60:f8:68:9e
Hostname: .......................................
Device Type: .................................... Unclassified
AP MAC Address................................... 84:f1:47:6c:bb:a0
AP Name.......................................... BIZ1-02-AP09
AP radio slot Id................................. 1
Client State..................................... Associated
User Authenticated by ........................... RADIUS Server
Client User Group................................ c4:23:60:f8:68:9e
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 17
Wireless LAN Network Name (SSID)................. NUS_Guest
Wireless LAN Profile Name........................ NUS_Guest_NUS_fa_F_a317b737
WLAN Profile check for roaming................... Disabled
Hotspot (802.11u)................................ Not Supported
Connected For ................................... 78 secs
BSSID............................................ 84:f1:47:6c:bb:ae
Channel.......................................... 64
IP Address....................................... 10.244.8.1
Gateway Address.................................. 10.244.0.1
Netmask.......................................... 255.255.192.0
--More-- or (q)uit
IPv6 Address..................................... fe80::c50c:74bb:1203:3386
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Client IPSK-TAG.................................. N/A
Status Code...................................... 0
Session Timeout.................................. 43200
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Avg data Rate.................................... 0
Burst data Rate.................................. 0
Avg Real time data Rate.......................... 0
Burst Real Time data Rate........................ 0
Avg Uplink data Rate............................. 0
Burst Uplink data Rate........................... 0
Avg Uplink Real time data Rate................... 0
Burst Uplink Real Time data Rate................. 0
802.1P Priority Tag.............................. disabled
Security Group Tag............................... 6
KTS CAC Capability............................... No
Qos Map Capability............................... Yes
WMM Support...................................... Enabled
APSD ACs....................................... BK BE VI VO
--More-- or (q)uit
Current Rate..................................... 12.0
Supported Rates.................................. 6.0,12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ No
Policy Manager State............................. WEBAUTH_REQD
Pre-auth IPv4 ACL Name........................... none
Pre-auth IPv4 ACL Applied Status................. Unavailable
Pre-auth IPv6 ACL Name........................... none
Pre-auth IPv6 ACL Applied Status................. Unavailable
Pre-auth Flex IPv4 ACL Name...................... none
Pre-auth Flex IPv4 ACL Applied Status............ Unavailable
Pre-auth Flex IPv6 ACL Name...................... none
Pre-auth Flex IPv6 ACL Applied Status............ Unavailable
Pre-auth redirect URL............................ none
Audit Session ID................................. none
AAA Role Type.................................... none
Acct Interim Interval............................ 0
Local Policy Applied............................. none
IPv4 ACL Name.................................... none
AAA FlexConnect ACL Applied Status............... Unavailable
IPv4 ACL Applied Status.......................... Unavailable
--More-- or (q)uit
IPv6 ACL Name.................................... none
IPv6 ACL Applied Status.......................... Unavailable
Post-auth Flex IPv6 ACL Name..................... none
Post-auth Flex IPv6 ACL Applied Status........... Unavailable
Layer2 ACL Name.................................. none
Layer2 ACL Applied Status........................ Unavailable
URL ACL Name..................................... none
URL ACL Applied Status........................... Unavailable
Client Type...................................... SimpleIP
mDNS Status...................................... Disabled
mDNS Profile Name................................ none
No. of mDNS Services Advertised.................. 0
Policy Type...................................... N/A
Encryption Cipher................................ None
Protected Management Frame ...................... No
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ management
VLAN............................................. 390
Quarantine VLAN.................................. 0
Access VLAN...................................... 390
Local Bridging VLAN.............................. 390
Client Capabilities:
--More-- or (q)uit
Radio Capability........................... 802.11ax
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Not implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 250
Fast BSS Transition........................ Not implemented
11v BSS Transition......................... Implemented
Non-Operable Channels............................ None
Non-Prefer Channels.............................. None
Client Wifi Direct Capabilities:
WFD capable................................ No
Manged WFD capable......................... No
Cross Connection Capable................... No
Support Concurrent Operation............... No
Fast BSS Transition Details:
DNS Server details:
DNS server IP ............................. 0.0.0.0
DNS server IP ............................. 0.0.0.0
Assisted Roaming Prediction List details:
--More-- or (q)uit
Client Dhcp Required: True
Allowed (URL)IP Addresses
-------------------------
AVC Profile Name: ............................... none
OpenDns Profile Name: ........................... none
Fastlane Client: ................................ No
Max DSCP: ....................................... 0
Nas Identifier: ................................. TLDC-WL-WLC01
Fabric Configuration
--------------------
Fabric Status: .................................. Enabled
Vnid: ........................................... 8211
Client RLOC IP registered to MS: ................ 172.18.1.133
Clients RLOC IP : .............................. 172.18.1.133
Fabric Flex Avc Policy Name: ....................
Fabric Statistics
--------------------
Primary Map Server : 172.18.0.129
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
--More-- or (q)uit
ms_stattype_registrations_deregistrations.... 0
Secondary Map Server : 172.18.0.130
ms_stattype_registrations_sent............... 1
ms_stattype_deregistrations_sent............. 0
ms_stattype_registrations_successful......... 1
ms_stattype_registrations_rejected........... 0
ms_stattype_registrations_deregistrations.... 0
Client Statistics:
Number of Bytes Received................... 432456
Number of Bytes Sent....................... 401863
Total Number of Bytes Sent................. 401863
Total Number of Bytes Recv................. 432456
Number of Bytes Sent (last 90s)............ 51897
Number of Bytes Recv (last 90s)............ 53360
Number of Packets Received................. 3591
Number of Packets Sent..................... 3812
Number of Interim-Update Sent.............. 0
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Request Msg Failures......... 0
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
--More-- or (q)uit
Number of Data Retries..................... 435
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 0
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of RA Packets Dropped............... 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -64 dBm
Signal to Noise Ratio...................... 30 dB
Client Detected as Inactive................ No
Client RBACL Statistics:
Number of RBACL Allowed Packets............ 0
Number of RBACL Denied Packets............. 0
Client Rate Limiting Statistics:
Number of Data Packets Received............ 0
Number of Data Rx Packets Dropped.......... 0
Number of Data Bytes Received.............. 0
Number of Data Rx Bytes Dropped............ 0
Number of Realtime Packets Received........ 0
Number of Realtime Rx Packets Dropped...... 0
Number of Realtime Bytes Received.......... 0
Number of Realtime Rx Bytes Dropped........ 0
--More-- or (q)uit
Number of Data Packets Sent................ 0
Number of Data Tx Packets Dropped.......... 0
Number of Data Bytes Sent.................. 0
Number of Data Tx Bytes Dropped............ 0
Number of Realtime Packets Sent............ 0
Number of Realtime Tx Packets Dropped...... 0
Number of Realtime Bytes Sent.............. 0
Number of Realtime Tx Bytes Dropped........ 0
Nearby AP Statistics:
BIZ1-02-AP10(slot 0)
antenna0: 35 secs ago.................... -45 dBm
antenna1: 35 secs ago.................... -45 dBm
BIZ1-02-AP10(slot 1)
antenna0: 80 secs ago.................... -43 dBm
antenna1: 80 secs ago.................... -43 dBm
BIZ1-02-AP15(slot 0)
antenna0: 35 secs ago.................... -75 dBm
antenna1: 35 secs ago.................... -75 dBm
BIZ1-02-AP15(slot 1)
antenna0: 80 secs ago.................... -80 dBm
antenna1: 80 secs ago.................... -80 dBm
BIZ1-02-AP24(slot 0)
antenna0: 130 secs ago................... -79 dBm
--More-- or (q)uit
antenna1: 130 secs ago................... -79 dBm
BIZ1-03-AP11(slot 0)
antenna0: 35 secs ago.................... -82 dBm
antenna1: 35 secs ago.................... -82 dBm
BIZ1-02-AP09(slot 0)
antenna0: 130 secs ago................... -48 dBm
antenna1: 130 secs ago................... -48 dBm
BIZ1-02-AP09(slot 1)
antenna0: 79 secs ago.................... -58 dBm
antenna1: 79 secs ago.................... -58 dBm
BIZ1-02-AP07(slot 1)
antenna0: 31 secs ago.................... -69 dBm
antenna1: 31 secs ago.................... -69 dBm
BIZ1-01-AP10(slot 0)
antenna0: 34 secs ago.................... -79 dBm
antenna1: 34 secs ago.................... -79 dBm
BIZ1-01-AP11(slot 0)
antenna0: 34 secs ago.................... -80 dBm
antenna1: 34 secs ago.................... -80 dBm
BIZ1-03-AP10(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-03-AP13(slot 0)
--More-- or (q)uit
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP13(slot 0)
antenna0: 34 secs ago.................... -66 dBm
antenna1: 34 secs ago.................... -66 dBm
BIZ1-02-AP14(slot 0)
antenna0: 130 secs ago................... -68 dBm
antenna1: 130 secs ago................... -68 dBm
BIZ1-02-AP14(slot 1)
antenna0: 33 secs ago.................... -71 dBm
antenna1: 33 secs ago.................... -71 dBm
BIZ1-03-AP12(slot 0)
antenna0: 130 secs ago................... -80 dBm
antenna1: 130 secs ago................... -80 dBm
BIZ1-03-AP12(slot 1)
antenna0: 80 secs ago.................... -84 dBm
antenna1: 80 secs ago.................... -84 dBm
BIZ1-02-AP12(slot 1)
antenna0: 79 secs ago.................... -55 dBm
antenna1: 79 secs ago.................... -55 dBm
BIZ1-01-AP02(slot 0)
antenna0: 35 secs ago.................... -80 dBm
antenna1: 35 secs ago.................... -80 dBm
--More-- or (q)uit
BIZ1-02-AP08(slot 0)
antenna0: 34 secs ago.................... -49 dBm
antenna1: 34 secs ago.................... -49 dBm
BIZ1-02-AP08(slot 1)
antenna0: 33 secs ago.................... -67 dBm
antenna1: 33 secs ago.................... -67 dBm
BIZ1-02-AP11(slot 0)
antenna0: 34 secs ago.................... -36 dBm
antenna1: 34 secs ago.................... -36 dBm
BIZ1-02-AP11(slot 1)
antenna0: 79 secs ago.................... -38 dBm
antenna1: 79 secs ago.................... -38 dBm
(TLDC-WL-WLC01) > | Issue: Guest Clients were not able to connect due to the captive portal not redirecting.
Steps Taken:
* Assessed logs collected from cu and found some bugs which match the issue:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvh20238
* Asked customer to implement following workaround:
-Remove the ACL from the FlexConnect Group and add it again.
OR
-Reboot the AP.
===============
Customer will be monitoring the issue and will open a new case if issue arises. | Guest SSID connected users, Captive portal is not redicrecting. | AIR-CT8540-K9 | 8.10.151.0 | 8.10.151.0 | 100.0 | 3 | 100.0 | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t1C000006EB81QAG | Error Messages, Logs, Debugs | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t15000004dDRMAA2 | nan |
695069319 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.5.140.0/ NA - RMA/ 16.12.4/ 8.10.161.0/ 15.3.3 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: C9120AX
Software Version: 8.10.151.0
Router/Node Name: TLDC-WL-WLC02
Problem Details: AP is up on switch side but dissociated from WLC, which cause service disruption.
AP is up on switch side but dissociated from WLC, which cause service disruption.
closing | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-K9/ AIR-CT5520-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: C9120AX
Software Version: 8.10.151.0
Router/Node Name: TLDC-WL-WLC02
Problem Details: AP is up on switch side but dissociated from WLC, which cause service disruption.
AP is up on switch side but dissociated from WLC, which cause service disruption.
closing | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: C9120AX
Software Version: 8.10.151.0
Router/Node Name: TLDC-WL-WLC02
Problem Details: AP is up on switch side but dissociated from WLC, which cause service disruption. | AP is up on switch side but dissociated from WLC, which cause service disruption. | closing | AP disconnected from WLC.
We see drops on the switchport. | C9120AXI-S | 16.12.4 | 16.12.4 | 13.0 | 3 | 100.0 | Software Bug | C9120AX | Wireless | 9120AX Series Access Point | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | 9120AX Series Access Point | Wireless | 01t15000004dDRMAA2 | SHERLOCK: PARTIAL |
695644022 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
qcsone-md
What Tasks are In-Progress:
No response from the customer, following up.
* Replace PSU1 with a known good power supply
* As your WLC pair is in a HA, so testing this on the standby should also be fine.
* Please note the power supply in 8540 is hot swappable, so just replacing the “Off” one on the secondary chassis and test it with a good power and let me know accordingly.
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C240M4/install/C240M4/replace.html#pgfId-1250643<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwww.cisco.com%2fc%2fen%2fus%2ftd%2fdocs%2funified%5fcomputing%2fucs%2fc%2fhw%2fC240M4%2finstall%2fC240M4%2freplace.html%23pgfId%2d1250643&umid=1728aed3-08ab-40d2-a28f-fa02560ef4c3&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-1a67cb564e81a96e3d0c5ca3b5810635aafcce7c>;
I would recommend to perform this test during off hours and let us know accordingly.
Bug: CSCvy72527 (https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy72527<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fbst.cloudapps.cisco.com%2fbugsearch%2fbug%2fCSCvy72527&umid=1728aed3-08ab-40d2-a28f-fa02560ef4c3&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-2845f1cca7d4a50adb9fb745ee84df25e40bc8c5>;)
Summary of Completed Tasks and Troubleshooting:
As per the WLC the PSU is reported as Present, OFF and as per below:
(TLDC-WL-WLC02) >show imm chassis power-supply
PSU1_POUT | 29h | ok | 10.1 | 0 Watts
PSU2_POUT | 2Fh | ok | 10.2 | 56 Watts
POWER_USAGE | C1h | ok | 7.0 | 64 Watts
PSU1_PIN | C2h | ok | 10.1 | 0 Watts
PSU2_PIN | C3h | ok | 10.2 | 64 Watts
Power Supply 1................................... Present, Off
Power Supply 2................................... Present, OK
qcsone-md
Hardware:
8540
Software:
8.10.183
Symptoms:
PSU status on the WLC is incorrect, Present OFF however its in working condition
qcsone-md
What Tasks are In-Progress:
* Replace PSU1 with a known good power supply
* As your WLC pair is in a HA, so testing this on the standby should also be fine.
* Please note the power supply in 8540 is hot swappable, so just replacing the “Off” one on the secondary chassis and test it with a good power and let me know accordingly.
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C240M4/install/C240M4/replace.html#pgfId-1250643<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwww.cisco.com%2fc%2fen%2fus%2ftd%2fdocs%2funified%5fcomputing%2fucs%2fc%2fhw%2fC240M4%2finstall%2fC240M4%2freplace.html%23pgfId%2d1250643&umid=1728aed3-08ab-40d2-a28f-fa02560ef4c3&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-1a67cb564e81a96e3d0c5ca3b5810635aafcce7c>;
I would recommend to perform this test during off hours and let us know accordingly.
Bug: CSCvy72527 (https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy72527<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fbst.cloudapps.cisco.com%2fbugsearch%2fbug%2fCSCvy72527&umid=1728aed3-08ab-40d2-a28f-fa02560ef4c3&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-2845f1cca7d4a50adb9fb745ee84df25e40bc8c5>;)
Summary of Completed Tasks and Troubleshooting:
As per the WLC the PSU is reported as Present, OFF and as per below:
(TLDC-WL-WLC02) >show imm chassis power-supply
PSU1_POUT | 29h | ok | 10.1 | 0 Watts
PSU2_POUT | 2Fh | ok | 10.2 | 56 Watts
POWER_USAGE | C1h | ok | 7.0 | 64 Watts
PSU1_PIN | C2h | ok | 10.1 | 0 Watts
PSU2_PIN | C3h | ok | 10.2 | 64 Watts
Power Supply 1................................... Present, Off
Power Supply 2................................... Present, OK
qcsone-md
Hardware:
8540
Software:
8.10.183
Symptoms:
PSU status on the WLC is incorrect, Present OFF however its in working condition.
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: WLC 8540 PSU power supply present but OFF, psu led is green
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: WLC 8540 PSU power supply present but OFF, psu led is green
WLC 8540 PSU power supply present but OFF, psu led is green
timestamp : 2023-07-04T09:50:15.000+0000 || updatedby : kishank || type : RESOLUTION SUMMARY || visibility : External || details : closing case threes strikes. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: WLC 8540 PSU power supply present but OFF, psu led is green
WLC 8540 PSU power supply present but OFF, psu led is green
timestamp : 2023-07-04T09:50:15.000+0000 || updatedby : kishank || type : RESOLUTION SUMMARY || visibility : External || details : closing case threes strikes. | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: WLC 8540 PSU power supply present but OFF, psu led is green | WLC 8540 PSU power supply present but OFF, psu led is green | timestamp : 2023-07-04T09:50:15.000+0000 || updatedby : kishank || type : RESOLUTION SUMMARY || visibility : External || details : closing case threes strikes. | nan | AIR-CT8540-CA-K9 | MFG_CTVM_SMALL_8.10.183.0.iso | nan | nan | 3 | nan | Configuration Assistance (process not intuitive, too complex, inconsistent...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | nan | nan | nan | nan | nan | nan |
695960852 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 9.16.2.3/ 9.14.2.4/ 9.14.2.4/ 9.14.1 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Adaptive Security Appliance
Subtechnology: ASA Firepower Devices - Non-VPN
Problem Code: Configuration Assistance
Product: NA
Product Family: FPRLOW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Team,
Afternoon, may we check what the heat generated (Btu/hours) for the FPR1150-ASA-K9?
Serial Number: JMX2716X0JJ
Thanks!
regards
Guan
Hi Team,
Afternoon, may we check what the heat generated (Btu/hours) for the FPR1150-ASA-K9?
Serial Number: JMX2716X0JJ
Thanks!
regards
Guan
Required information has been shared to calculate the BTU and attached the Watt to BTU converter for reference.
* I'm proceeding with the closure of this case after your confirmation in the last mail. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: FPR9K-SM-36/ FPR-C9300-AC/ FPR1150-ASA-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Adaptive Security Appliance
Subtechnology: ASA Firepower Devices - Non-VPN
Problem Code: Configuration Assistance
Product: NA
Product Family: FPRLOW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Team,
Afternoon, may we check what the heat generated (Btu/hours) for the FPR1150-ASA-K9?
Serial Number: JMX2716X0JJ
Thanks!
regards
Guan
Hi Team,
Afternoon, may we check what the heat generated (Btu/hours) for the FPR1150-ASA-K9?
Serial Number: JMX2716X0JJ
Thanks!
regards
Guan
Required information has been shared to calculate the BTU and attached the Watt to BTU converter for reference.
* I'm proceeding with the closure of this case after your confirmation in the last mail. | Technology: Adaptive Security Appliance
Subtechnology: ASA Firepower Devices - Non-VPN
Problem Code: Configuration Assistance
Product: NA
Product Family: FPRLOW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Team,
Afternoon, may we check what the heat generated (Btu/hours) for the FPR1150-ASA-K9?
Serial Number: JMX2716X0JJ
Thanks!
regards
Guan | Hi Team,
Afternoon, may we check what the heat generated (Btu/hours) for the FPR1150-ASA-K9?
Serial Number: JMX2716X0JJ
Thanks!
regards
Guan | Required information has been shared to calculate the BTU and attached the Watt to BTU converter for reference.
* I'm proceeding with the closure of this case after your confirmation in the last mail. | we are deploying the ASA in our client server room and we need to submit the heat generated in btu/hours for the equipment | FPR1150-ASA-K9 | 9.16(2)3 | 9.16(2)3 | 75.0 | 4 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | FPRLOW | Adaptive Security Appliance | ASA Firepower Devices - Non-VPN | 01t6R000007BkD2QAK | Configuration Assistance | ASA Firepower Devices - Non-VPN | Adaptive Security Appliance | 01t1C000006UmrUQAS | CaseClosureFieldAutomation: Partial |
695684373 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 7.7.1/ 6.3.3/ 7.3.2/ NA - RMA/ 7.3.2 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: XR-Routing-Platforms
Subtechnology: ASR 9000 Series - Hardware failures, Environmental Issues (Power, Fans, etc)
Problem Code: Hardware Failure
Product: NA
Product Family: ASR9KFM
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi cisco support,
We observed that standby RSP (RSP1) was auto reloaded in ASR9006 router. Please find attached logs and investigate the root cause.
0/RSP0/ADMIN0:Jun 13 12:07:49.613 SGT: rvm_mgr[3921]: %PKT_INFRA-RVM_MGR-3-ERROR : Admin and Service VM down on card 0/RSP1, reloading card..
0/RSP0/ADMIN0:Jun 13 12:07:49.616 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/RSP1
0/RSP0/ADMIN0:Jun 13 12:07:54.764 SGT: esdma[5174]: %INFRA-ESDMA-6-ESD_CONN_LOST : ESDMA lost connection with esd at 0/RP1/RP-SW1
RP/0/RSP0/CPU0:Jun 13 12:08:29.623 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-NO_CB : No completion notification received for update message 4035
RP/0/RSP0/CPU0:Jun 13 12:08:43.159 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-SEND_FAILED : Failed to send update: rc 0xb (Resource temporarily unavailable)
0/RSP0/ADMIN0:Jun 13 12:08:54.663 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 55 has changed. New Link state DOWN, Admin state: UP
0/0/ADMIN0:Jun 13 12:08:54.662 SGT: esd[3510]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 58 has changed. New Link state DOWN, Admin state: UP
0/RSP0/ADMIN0:Jun 13 12:08:54.664 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 54 has changed. New Link state DOWN, Admin state: UP
RP/0/RSP0/CPU0:Jun 13 12:08:54.679 SGT: rmf_svr[288]: %HA-REDCON-1-STANDBY_NOT_READY : standby card is NOT ready
0/RSP0/ADMIN0:Jun 13 12:08:54.668 SGT: canbus_driver[3894]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP1 CBC-0, reset reason CPU_RESET_POR (0x05000000)
0/RSP0/ADMIN0:Jun 13 12:08:54.670 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-6-HW_EVENT : Rcvd HW event HW_EVENT_RESET, event_reason_str 'HW Event RESET' for card 0/RSP1
RP/0/RSP0/CPU0:Jun 13 12:08:54.694 SGT: bpm[1102]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(S)inst-id 0, Connection Closed
RP/0/RSP0/CPU0:Jun 13 12:08:54.706 SGT: rmf_svr[288]: %HA-REDCON-6-STANDBY_CONNECTION_DOWN : connection to standby card is DOWN
Hi cisco support,
We observed that standby RSP (RSP1) was auto reloaded in ASR9006 router. Please find attached logs and investigate the root cause.
0/RSP0/ADMIN0:Jun 13 12:07:49.613 SGT: rvm_mgr[3921]: %PKT_INFRA-RVM_MGR-3-ERROR : Admin and Service VM down on card 0/RSP1, reloading card..
0/RSP0/ADMIN0:Jun 13 12:07:49.616 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/RSP1
0/RSP0/ADMIN0:Jun 13 12:07:54.764 SGT: esdma[5174]: %INFRA-ESDMA-6-ESD_CONN_LOST : ESDMA lost connection with esd at 0/RP1/RP-SW1
RP/0/RSP0/CPU0:Jun 13 12:08:29.623 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-NO_CB : No completion notification received for update message 4035
RP/0/RSP0/CPU0:Jun 13 12:08:43.159 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-SEND_FAILED : Failed to send update: rc 0xb (Resource temporarily unavailable)
0/RSP0/ADMIN0:Jun 13 12:08:54.663 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 55 has changed. New Link state DOWN, Admin state: UP
0/0/ADMIN0:Jun 13 12:08:54.662 SGT: esd[3510]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 58 has changed. New Link state DOWN, Admin state: UP
0/RSP0/ADMIN0:Jun 13 12:08:54.664 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 54 has changed. New Link state DOWN, Admin state: UP
RP/0/RSP0/CPU0:Jun 13 12:08:54.679 SGT: rmf_svr[288]: %HA-REDCON-1-STANDBY_NOT_READY : standby card is NOT ready
0/RSP0/ADMIN0:Jun 13 12:08:54.668 SGT: canbus_driver[3894]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP1 CBC-0, reset reason CPU_RESET_POR (0x05000000)
0/RSP0/ADMIN0:Jun 13 12:08:54.670 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-6-HW_EVENT : Rcvd HW event HW_EVENT_RESET, event_reason_str 'HW Event RESET' for card 0/RSP1
RP/0/RSP0/CPU0:Jun 13 12:08:54.694 SGT: bpm[1102]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(S)inst-id 0, Connection Closed
RP/0/RSP0/CPU0:Jun 13 12:08:54.706 SGT: rmf_svr[288]: %HA-REDCON-6-STANDBY_CONNECTION_DOWN : connection to standby card is DOWN
Rvm_mgr (Remote VM manager), is a rack scoped service which runs only on RPs maintaining HBs (Heartbeats) with XR VMs on remote cards. This process caters to two simultaneous faults in the system.
* The two faults are, the process misses 3 HBs with remote XR VM, and Sysadmin VM on the remote card is down too. In case of such double failure, rvm_mgr takes action of reloading the remote card as a recovery mechanism.
* The connectivity failure between the cards was further confirmed from the below ping report, when the first HB is missed with XR VM, ping test is recorded.
* If ping result says 100% packet loss, this means there is communication failure.
Start:
2023-06-13-12:07:12:272349058 PING 192.0.4.4 (192.0.4.4) 56(84) bytes of data. ---
192.0.4.4 ping statistics ---
50 packets transmitted, 0 received, 100% packet loss, time 5271ms
Finish: 2023-06-13-12:07:27:552267057
* The node is stable for 25 days, if there is any sort of hardware failure we should see recurrence but that didn't happen.
* Considering all of the situations, we suspect that the admin VM of RP1 encountered a transient issue at the control plane to cause HB loss further. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: ASR-9006/ A9K-RSP880-SE/ ASR-9904/ ASR-9006-FAN-V2/ A9K-RSP880-TR Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: XR-Routing-Platforms
Subtechnology: ASR 9000 Series - Hardware failures, Environmental Issues (Power, Fans, etc)
Problem Code: Hardware Failure
Product: NA
Product Family: ASR9KFM
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi cisco support,
We observed that standby RSP (RSP1) was auto reloaded in ASR9006 router. Please find attached logs and investigate the root cause.
0/RSP0/ADMIN0:Jun 13 12:07:49.613 SGT: rvm_mgr[3921]: %PKT_INFRA-RVM_MGR-3-ERROR : Admin and Service VM down on card 0/RSP1, reloading card..
0/RSP0/ADMIN0:Jun 13 12:07:49.616 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/RSP1
0/RSP0/ADMIN0:Jun 13 12:07:54.764 SGT: esdma[5174]: %INFRA-ESDMA-6-ESD_CONN_LOST : ESDMA lost connection with esd at 0/RP1/RP-SW1
RP/0/RSP0/CPU0:Jun 13 12:08:29.623 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-NO_CB : No completion notification received for update message 4035
RP/0/RSP0/CPU0:Jun 13 12:08:43.159 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-SEND_FAILED : Failed to send update: rc 0xb (Resource temporarily unavailable)
0/RSP0/ADMIN0:Jun 13 12:08:54.663 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 55 has changed. New Link state DOWN, Admin state: UP
0/0/ADMIN0:Jun 13 12:08:54.662 SGT: esd[3510]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 58 has changed. New Link state DOWN, Admin state: UP
0/RSP0/ADMIN0:Jun 13 12:08:54.664 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 54 has changed. New Link state DOWN, Admin state: UP
RP/0/RSP0/CPU0:Jun 13 12:08:54.679 SGT: rmf_svr[288]: %HA-REDCON-1-STANDBY_NOT_READY : standby card is NOT ready
0/RSP0/ADMIN0:Jun 13 12:08:54.668 SGT: canbus_driver[3894]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP1 CBC-0, reset reason CPU_RESET_POR (0x05000000)
0/RSP0/ADMIN0:Jun 13 12:08:54.670 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-6-HW_EVENT : Rcvd HW event HW_EVENT_RESET, event_reason_str 'HW Event RESET' for card 0/RSP1
RP/0/RSP0/CPU0:Jun 13 12:08:54.694 SGT: bpm[1102]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(S)inst-id 0, Connection Closed
RP/0/RSP0/CPU0:Jun 13 12:08:54.706 SGT: rmf_svr[288]: %HA-REDCON-6-STANDBY_CONNECTION_DOWN : connection to standby card is DOWN
Hi cisco support,
We observed that standby RSP (RSP1) was auto reloaded in ASR9006 router. Please find attached logs and investigate the root cause.
0/RSP0/ADMIN0:Jun 13 12:07:49.613 SGT: rvm_mgr[3921]: %PKT_INFRA-RVM_MGR-3-ERROR : Admin and Service VM down on card 0/RSP1, reloading card..
0/RSP0/ADMIN0:Jun 13 12:07:49.616 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/RSP1
0/RSP0/ADMIN0:Jun 13 12:07:54.764 SGT: esdma[5174]: %INFRA-ESDMA-6-ESD_CONN_LOST : ESDMA lost connection with esd at 0/RP1/RP-SW1
RP/0/RSP0/CPU0:Jun 13 12:08:29.623 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-NO_CB : No completion notification received for update message 4035
RP/0/RSP0/CPU0:Jun 13 12:08:43.159 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-SEND_FAILED : Failed to send update: rc 0xb (Resource temporarily unavailable)
0/RSP0/ADMIN0:Jun 13 12:08:54.663 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 55 has changed. New Link state DOWN, Admin state: UP
0/0/ADMIN0:Jun 13 12:08:54.662 SGT: esd[3510]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 58 has changed. New Link state DOWN, Admin state: UP
0/RSP0/ADMIN0:Jun 13 12:08:54.664 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 54 has changed. New Link state DOWN, Admin state: UP
RP/0/RSP0/CPU0:Jun 13 12:08:54.679 SGT: rmf_svr[288]: %HA-REDCON-1-STANDBY_NOT_READY : standby card is NOT ready
0/RSP0/ADMIN0:Jun 13 12:08:54.668 SGT: canbus_driver[3894]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP1 CBC-0, reset reason CPU_RESET_POR (0x05000000)
0/RSP0/ADMIN0:Jun 13 12:08:54.670 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-6-HW_EVENT : Rcvd HW event HW_EVENT_RESET, event_reason_str 'HW Event RESET' for card 0/RSP1
RP/0/RSP0/CPU0:Jun 13 12:08:54.694 SGT: bpm[1102]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(S)inst-id 0, Connection Closed
RP/0/RSP0/CPU0:Jun 13 12:08:54.706 SGT: rmf_svr[288]: %HA-REDCON-6-STANDBY_CONNECTION_DOWN : connection to standby card is DOWN
Rvm_mgr (Remote VM manager), is a rack scoped service which runs only on RPs maintaining HBs (Heartbeats) with XR VMs on remote cards. This process caters to two simultaneous faults in the system.
* The two faults are, the process misses 3 HBs with remote XR VM, and Sysadmin VM on the remote card is down too. In case of such double failure, rvm_mgr takes action of reloading the remote card as a recovery mechanism.
* The connectivity failure between the cards was further confirmed from the below ping report, when the first HB is missed with XR VM, ping test is recorded.
* If ping result says 100% packet loss, this means there is communication failure.
Start:
2023-06-13-12:07:12:272349058 PING 192.0.4.4 (192.0.4.4) 56(84) bytes of data. ---
192.0.4.4 ping statistics ---
50 packets transmitted, 0 received, 100% packet loss, time 5271ms
Finish: 2023-06-13-12:07:27:552267057
* The node is stable for 25 days, if there is any sort of hardware failure we should see recurrence but that didn't happen.
* Considering all of the situations, we suspect that the admin VM of RP1 encountered a transient issue at the control plane to cause HB loss further. | Technology: XR-Routing-Platforms
Subtechnology: ASR 9000 Series - Hardware failures, Environmental Issues (Power, Fans, etc)
Problem Code: Hardware Failure
Product: NA
Product Family: ASR9KFM
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi cisco support,
We observed that standby RSP (RSP1) was auto reloaded in ASR9006 router. Please find attached logs and investigate the root cause.
0/RSP0/ADMIN0:Jun 13 12:07:49.613 SGT: rvm_mgr[3921]: %PKT_INFRA-RVM_MGR-3-ERROR : Admin and Service VM down on card 0/RSP1, reloading card..
0/RSP0/ADMIN0:Jun 13 12:07:49.616 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/RSP1
0/RSP0/ADMIN0:Jun 13 12:07:54.764 SGT: esdma[5174]: %INFRA-ESDMA-6-ESD_CONN_LOST : ESDMA lost connection with esd at 0/RP1/RP-SW1
RP/0/RSP0/CPU0:Jun 13 12:08:29.623 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-NO_CB : No completion notification received for update message 4035
RP/0/RSP0/CPU0:Jun 13 12:08:43.159 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-SEND_FAILED : Failed to send update: rc 0xb (Resource temporarily unavailable)
0/RSP0/ADMIN0:Jun 13 12:08:54.663 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 55 has changed. New Link state DOWN, Admin state: UP
0/0/ADMIN0:Jun 13 12:08:54.662 SGT: esd[3510]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 58 has changed. New Link state DOWN, Admin state: UP
0/RSP0/ADMIN0:Jun 13 12:08:54.664 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 54 has changed. New Link state DOWN, Admin state: UP
RP/0/RSP0/CPU0:Jun 13 12:08:54.679 SGT: rmf_svr[288]: %HA-REDCON-1-STANDBY_NOT_READY : standby card is NOT ready
0/RSP0/ADMIN0:Jun 13 12:08:54.668 SGT: canbus_driver[3894]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP1 CBC-0, reset reason CPU_RESET_POR (0x05000000)
0/RSP0/ADMIN0:Jun 13 12:08:54.670 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-6-HW_EVENT : Rcvd HW event HW_EVENT_RESET, event_reason_str 'HW Event RESET' for card 0/RSP1
RP/0/RSP0/CPU0:Jun 13 12:08:54.694 SGT: bpm[1102]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(S)inst-id 0, Connection Closed
RP/0/RSP0/CPU0:Jun 13 12:08:54.706 SGT: rmf_svr[288]: %HA-REDCON-6-STANDBY_CONNECTION_DOWN : connection to standby card is DOWN | Hi cisco support,
We observed that standby RSP (RSP1) was auto reloaded in ASR9006 router. Please find attached logs and investigate the root cause.
0/RSP0/ADMIN0:Jun 13 12:07:49.613 SGT: rvm_mgr[3921]: %PKT_INFRA-RVM_MGR-3-ERROR : Admin and Service VM down on card 0/RSP1, reloading card..
0/RSP0/ADMIN0:Jun 13 12:07:49.616 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-4-CARD_RELOAD : Reloading card 0/RSP1
0/RSP0/ADMIN0:Jun 13 12:07:54.764 SGT: esdma[5174]: %INFRA-ESDMA-6-ESD_CONN_LOST : ESDMA lost connection with esd at 0/RP1/RP-SW1
RP/0/RSP0/CPU0:Jun 13 12:08:29.623 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-NO_CB : No completion notification received for update message 4035
RP/0/RSP0/CPU0:Jun 13 12:08:43.159 SGT: sysdb_svr_admin[298]: %LIBRARY-REPLICATOR-7-SEND_FAILED : Failed to send update: rc 0xb (Resource temporarily unavailable)
0/RSP0/ADMIN0:Jun 13 12:08:54.663 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 55 has changed. New Link state DOWN, Admin state: UP
0/0/ADMIN0:Jun 13 12:08:54.662 SGT: esd[3510]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 58 has changed. New Link state DOWN, Admin state: UP
0/RSP0/ADMIN0:Jun 13 12:08:54.664 SGT: esd[3902]: %INFRA-ESD-6-PORT_STATE_CHANGE_LINK_DOWN : The physical link state of the control ethernet switch port 54 has changed. New Link state DOWN, Admin state: UP
RP/0/RSP0/CPU0:Jun 13 12:08:54.679 SGT: rmf_svr[288]: %HA-REDCON-1-STANDBY_NOT_READY : standby card is NOT ready
0/RSP0/ADMIN0:Jun 13 12:08:54.668 SGT: canbus_driver[3894]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP1 CBC-0, reset reason CPU_RESET_POR (0x05000000)
0/RSP0/ADMIN0:Jun 13 12:08:54.670 SGT: shelf_mgr[3924]: %INFRA-SHELF_MGR-6-HW_EVENT : Rcvd HW event HW_EVENT_RESET, event_reason_str 'HW Event RESET' for card 0/RSP1
RP/0/RSP0/CPU0:Jun 13 12:08:54.694 SGT: bpm[1102]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(S)inst-id 0, Connection Closed
RP/0/RSP0/CPU0:Jun 13 12:08:54.706 SGT: rmf_svr[288]: %HA-REDCON-6-STANDBY_CONNECTION_DOWN : connection to standby card is DOWN | Rvm_mgr (Remote VM manager), is a rack scoped service which runs only on RPs maintaining HBs (Heartbeats) with XR VMs on remote cards. This process caters to two simultaneous faults in the system.
* The two faults are, the process misses 3 HBs with remote XR VM, and Sysadmin VM on the remote card is down too. In case of such double failure, rvm_mgr takes action of reloading the remote card as a recovery mechanism.
* The connectivity failure between the cards was further confirmed from the below ping report, when the first HB is missed with XR VM, ping test is recorded.
* If ping result says 100% packet loss, this means there is communication failure.
Start:
2023-06-13-12:07:12:272349058 PING 192.0.4.4 (192.0.4.4) 56(84) bytes of data. ---
192.0.4.4 ping statistics ---
50 packets transmitted, 0 received, 100% packet loss, time 5271ms
Finish: 2023-06-13-12:07:27:552267057
* The node is stable for 25 days, if there is any sort of hardware failure we should see recurrence but that didn't happen.
* Considering all of the situations, we suspect that the admin VM of RP1 encountered a transient issue at the control plane to cause HB loss further. | Problem description:
------------------
Node Name: JE_GP_ASR_R02
Hardware: ASR-9006
Software: NA
Issue : Standby RSP 1 got auto-reloaded | A9K-RSP880-TR | 7.3.2 | 7.3.2 | 42.0 | 3 | 100.0 | Hardware - non-failure (limits exceeded, not enough memory, missing parts...) | ASR9KFM | XR-Routing-Platforms | ASR 9000 Series - Hardware failures, Environmental Issues (Power, Fans, etc) | 01t6R000007Bn2OQAS | Hardware Failure | ASR 9000 Series - Hardware failures, Environmental Issues (Power, Fans, etc) | XR-Routing-Platforms | 01tA0000000kmQpIAI | IRE: PARTIAL;SHERLOCK: PARTIAL;CaseClosureFieldAutomation: Partial |
694168349 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC,
For some reason, clients are not able to get IP address on a specific WiFi6 AP. Clients can connect and get IP address when connecting to a different WiFi6 AP.
Pls assign this case to Singapore Timezone TAC
logs from the client laptop when connecting on the problematic WiFi6 AP
C:\Users\P0104884>netsh wlan show interface
There is 1 interface on the system:
Name : Wi-Fi 2
Description : Intel(R) Wireless-AC 9560 160MHz
GUID : dc942dc5-f675-4d00-b042-fe9e06ead97c
Physical address : 80:32:53:d8:8a:ab
State : connected
SSID : NUS
BSSID : f0:1d:2d:ba:ba:0f
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 100
Receive rate (Mbps) : 300
Transmit rate (Mbps) : 400
Signal : 89%
Profile : NUS
Hosted network status : Not available
Wireless LAN adapter Wi-Fi 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 80-32-53-D8-8A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b016:7822:bb77:cf9c%31(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.207.156(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 444609107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E9-D1-F0-48-BA-4E-51-49-14
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Hi TAC,
For some reason, clients are not able to get IP address on a specific WiFi6 AP. Clients can connect and get IP address when connecting to a different WiFi6 AP.
Pls assign this case to Singapore Timezone TAC
logs from the client laptop when connecting on the problematic WiFi6 AP
C:\Users\P0104884>netsh wlan show interface
There is 1 interface on the system:
Name : Wi-Fi 2
Description : Intel(R) Wireless-AC 9560 160MHz
GUID : dc942dc5-f675-4d00-b042-fe9e06ead97c
Physical address : 80:32:53:d8:8a:ab
State : connected
SSID : NUS
BSSID : f0:1d:2d:ba:ba:0f
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 100
Receive rate (Mbps) : 300
Transmit rate (Mbps) : 400
Signal : 89%
Profile : NUS
Hosted network status : Not available
Wireless LAN adapter Wi-Fi 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 80-32-53-D8-8A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b016:7822:bb77:cf9c%31(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.207.156(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 444609107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E9-D1-F0-48-BA-4E-51-49-14
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Issue resolved.
Ref the Latest GCI | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC,
For some reason, clients are not able to get IP address on a specific WiFi6 AP. Clients can connect and get IP address when connecting to a different WiFi6 AP.
Pls assign this case to Singapore Timezone TAC
logs from the client laptop when connecting on the problematic WiFi6 AP
C:\Users\P0104884>netsh wlan show interface
There is 1 interface on the system:
Name : Wi-Fi 2
Description : Intel(R) Wireless-AC 9560 160MHz
GUID : dc942dc5-f675-4d00-b042-fe9e06ead97c
Physical address : 80:32:53:d8:8a:ab
State : connected
SSID : NUS
BSSID : f0:1d:2d:ba:ba:0f
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 100
Receive rate (Mbps) : 300
Transmit rate (Mbps) : 400
Signal : 89%
Profile : NUS
Hosted network status : Not available
Wireless LAN adapter Wi-Fi 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 80-32-53-D8-8A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b016:7822:bb77:cf9c%31(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.207.156(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 444609107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E9-D1-F0-48-BA-4E-51-49-14
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Hi TAC,
For some reason, clients are not able to get IP address on a specific WiFi6 AP. Clients can connect and get IP address when connecting to a different WiFi6 AP.
Pls assign this case to Singapore Timezone TAC
logs from the client laptop when connecting on the problematic WiFi6 AP
C:\Users\P0104884>netsh wlan show interface
There is 1 interface on the system:
Name : Wi-Fi 2
Description : Intel(R) Wireless-AC 9560 160MHz
GUID : dc942dc5-f675-4d00-b042-fe9e06ead97c
Physical address : 80:32:53:d8:8a:ab
State : connected
SSID : NUS
BSSID : f0:1d:2d:ba:ba:0f
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 100
Receive rate (Mbps) : 300
Transmit rate (Mbps) : 400
Signal : 89%
Profile : NUS
Hosted network status : Not available
Wireless LAN adapter Wi-Fi 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 80-32-53-D8-8A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b016:7822:bb77:cf9c%31(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.207.156(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 444609107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E9-D1-F0-48-BA-4E-51-49-14
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Issue resolved.
Ref the Latest GCI | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC,
For some reason, clients are not able to get IP address on a specific WiFi6 AP. Clients can connect and get IP address when connecting to a different WiFi6 AP.
Pls assign this case to Singapore Timezone TAC
logs from the client laptop when connecting on the problematic WiFi6 AP
C:\Users\P0104884>netsh wlan show interface
There is 1 interface on the system:
Name : Wi-Fi 2
Description : Intel(R) Wireless-AC 9560 160MHz
GUID : dc942dc5-f675-4d00-b042-fe9e06ead97c
Physical address : 80:32:53:d8:8a:ab
State : connected
SSID : NUS
BSSID : f0:1d:2d:ba:ba:0f
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 100
Receive rate (Mbps) : 300
Transmit rate (Mbps) : 400
Signal : 89%
Profile : NUS
Hosted network status : Not available
Wireless LAN adapter Wi-Fi 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 80-32-53-D8-8A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b016:7822:bb77:cf9c%31(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.207.156(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 444609107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E9-D1-F0-48-BA-4E-51-49-14
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled | Hi TAC,
For some reason, clients are not able to get IP address on a specific WiFi6 AP. Clients can connect and get IP address when connecting to a different WiFi6 AP.
Pls assign this case to Singapore Timezone TAC
logs from the client laptop when connecting on the problematic WiFi6 AP
C:\Users\P0104884>netsh wlan show interface
There is 1 interface on the system:
Name : Wi-Fi 2
Description : Intel(R) Wireless-AC 9560 160MHz
GUID : dc942dc5-f675-4d00-b042-fe9e06ead97c
Physical address : 80:32:53:d8:8a:ab
State : connected
SSID : NUS
BSSID : f0:1d:2d:ba:ba:0f
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 100
Receive rate (Mbps) : 300
Transmit rate (Mbps) : 400
Signal : 89%
Profile : NUS
Hosted network status : Not available
Wireless LAN adapter Wi-Fi 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 80-32-53-D8-8A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b016:7822:bb77:cf9c%31(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.207.156(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 444609107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E9-D1-F0-48-BA-4E-51-49-14
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled | Issue resolved.
Ref the Latest GCI | Clients not able to connect specific SSID. | AIR-CT8540-K9 | 12.0(13)W5(19b) | 12.0(13)W5(19b) | 24.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t1C0000065Y1wQAE | Error Messages, Logs, Debugs | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t1C000006WMdqQAG | SHERLOCK: PARTIAL |
694111541 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 2.2.3.4/ 16.12.04/ 2.1.2.7/ 2.2.2.9/ 2.2.2.8/ 1.3.1.4/ 2.3.3.4/ 2.3.3.7/ 2.2.2.8/ 1.3.3.7/ 17.03.03/ 2.1.2.7/ 1.3.3.7/ 2.2.2.9/ 2.3.3.7/ 16.12.4/ 2.2.3.5/ 2.2.3.6/ 2.2.2.9/ 4.0.4b/ 2.2.3.4/ 2.2.2.8/ 2.1.2.6/ 2.2.3.5 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: We are running DNA center version 2.2.2.9 and have configured SGACLs for micro-segmentation.
We have enabled logging for some of the ACL entries but are not able to view the relevant traffic flow on DNA center.
We are running DNA center version 2.2.2.9 and have configured SGACLs for micro-segmentation.
We have enabled logging for some of the ACL entries but are not able to view the relevant traffic flow on DNA center.
Issue was resolved after rediscovering the device with Netconf. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN1-HW-APL/ DN2-HW-APL/ DN2-HW-APL-XL/ C9300-48UN/ DN2-HW-APL-L/ DN2-HW-APL-U/ C9300-48U Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: We are running DNA center version 2.2.2.9 and have configured SGACLs for micro-segmentation.
We have enabled logging for some of the ACL entries but are not able to view the relevant traffic flow on DNA center.
We are running DNA center version 2.2.2.9 and have configured SGACLs for micro-segmentation.
We have enabled logging for some of the ACL entries but are not able to view the relevant traffic flow on DNA center.
Issue was resolved after rediscovering the device with Netconf. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: We are running DNA center version 2.2.2.9 and have configured SGACLs for micro-segmentation.
We have enabled logging for some of the ACL entries but are not able to view the relevant traffic flow on DNA center. | We are running DNA center version 2.2.2.9 and have configured SGACLs for micro-segmentation.
We have enabled logging for some of the ACL entries but are not able to view the relevant traffic flow on DNA center. | Issue was resolved after rediscovering the device with Netconf. | On DNA center, unable to view the traffic flows related to micro-segmentation | DN2-HW-APL-XL | 16.12.4 | 16.12.4 | 40.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | DNAHW | Cisco DNA Center - On-Prem | Cisco DNA Center - Infrastructure (Services, UI, API, etc.) | 01t6R000006EH5aQAG | Error Messages, Logs, Debugs | Cisco DNA Center - Infrastructure (Services, UI, API, etc.) | Cisco DNA Center - On-Prem | 01t15000005W0LTAA0 | SHERLOCK: PARTIAL |
694641874 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
++ Tejas from Wireless TAC Team
Thank you for your time on the call today.
As per our session, it was seen that many AP’s were crashing over the last 1 week on the Cisco 8540 Wireless Controller running version 8.10.151.0.
We have seen the crash happening 2 models of AP’s on call ( 9120AXI Access Point , 2800I Access Point ).
The AP’s are currently managed successfully on the WLC.
The WLC and the AP’s are also reachable and Managed on DNAC.
Since this has been isolated to be a Platform issue, @Tejas Pillaiah (tpillaia)<mailto:[email protected]> from Wireless Team will be taking over this case and assisting you further.
Thank you for your patience.
Please feel free to let me know if you have any other queries.
Multiple AP's that are associated to the AP's have crashed.
Cisco 8540 Wireless Controller . Version : 8.10.151.0
Issue has been seen for 9120AXI Access Point 2800I Access Point so far.
Software Version: -- => 8.10.151.0
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA Fabric AP - Frequent crash for random APs connected to WLC.13
SDA Fabric AP - Frequent crash for random APs connected to WLC.13
timestamp : 2022-12-09T08:05:04.000+0000 || updatedby : sasengar || type : RESOLUTION SUMMARY || visibility : External || details : Opened in Error | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA Fabric AP - Frequent crash for random APs connected to WLC.13
SDA Fabric AP - Frequent crash for random APs connected to WLC.13
timestamp : 2022-12-09T08:05:04.000+0000 || updatedby : sasengar || type : RESOLUTION SUMMARY || visibility : External || details : Opened in Error | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA Fabric AP - Frequent crash for random APs connected to WLC.13 | SDA Fabric AP - Frequent crash for random APs connected to WLC.13 | timestamp : 2022-12-09T08:05:04.000+0000 || updatedby : sasengar || type : RESOLUTION SUMMARY || visibility : External || details : Opened in Error | nan | AIR-CT8540-K9 | AIR-CT8540-K9-8-10-151-0.aes | nan | nan | 3 | nan | Software -not a bug (scalability, version selection, install/upgrade help...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | nan | nan | nan | nan | nan | nan |
695579249 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 2.2.3.6/ 2.2.3.6/ 2.3.3.7/ 2.2.2.9 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wireless)
Problem Code: Software Failure
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
1. New Sites/Floors cannot be provisioned to wlc - "No configuration was generated"
Because of that, new APs for that new floors cannot be provisioned, error is "NCWL10802: The site(s) YNC-RC2-02 is not managed by any Wireless Controllers. Please provision a Wireless Controller and specify the site(s) as Managed AP Location(s)."
2. Unexpected/unintended/Unrelated commands came out during the first provision to WLCs after the upgrade
Refer to attached word file for detail explanation with screenshots and config preview files.
DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
1. New Sites/Floors cannot be provisioned to wlc - "No configuration was generated"
Because of that, new APs for that new floors cannot be provisioned, error is "NCWL10802: The site(s) YNC-RC2-02 is not managed by any Wireless Controllers. Please provision a Wireless Controller and specify the site(s) as Managed AP Location(s)."
2. Unexpected/unintended/Unrelated commands came out during the first provision to WLCs after the upgrade
Refer to attached word file for detail explanation with screenshots and config preview files.
Issue : WLC Provisioning failed on DNAC
DNAC Version : 2.3.3.7 ( DN2-HW-APL-XL ) , 3 Node Cluster
On 4th of July Night at Singapore Time, the WLC was provisioned with additional Managed AP Locations where it was stuck for 9 Hours.
The Provision failed after 9 Hours of waiting with the below error :
A screenshot of a computer
Description automatically generated
The RCA Logs were generated after the failure for further investigation
The BU Escalation Team were involved and after analysis the Root Cause was identified as seen below :
Issue triggered due to duplication data in DB, resulting in Network Programmer running out of memory.
CSCwf89617 is addressed in 2.3.3.7. The fix is applicable only for WLC provisioning flows done after upgrading to 2.3.3.7.
The duplicated data is present in database prior to the Upgrade to 2.3.3.7
new defect CSCwd49629 is raised to handle the old stale entries in DB which might be carried forward after during upgrade to 2.3.3.7 and which are not handled by CSCwf89617.
The Workaround that was provided to resolve this issue is as follows :
Prune the DCS table to nullify the data, to clear the duplicated data.
Increase memory of network-programmer and spf-service
Subsequent sessions involved applying the workaround and provisioning the WLC’s which all resulted in success. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL/ DN2-HW-APL-XL Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wireless)
Problem Code: Software Failure
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
1. New Sites/Floors cannot be provisioned to wlc - "No configuration was generated"
Because of that, new APs for that new floors cannot be provisioned, error is "NCWL10802: The site(s) YNC-RC2-02 is not managed by any Wireless Controllers. Please provision a Wireless Controller and specify the site(s) as Managed AP Location(s)."
2. Unexpected/unintended/Unrelated commands came out during the first provision to WLCs after the upgrade
Refer to attached word file for detail explanation with screenshots and config preview files.
DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
1. New Sites/Floors cannot be provisioned to wlc - "No configuration was generated"
Because of that, new APs for that new floors cannot be provisioned, error is "NCWL10802: The site(s) YNC-RC2-02 is not managed by any Wireless Controllers. Please provision a Wireless Controller and specify the site(s) as Managed AP Location(s)."
2. Unexpected/unintended/Unrelated commands came out during the first provision to WLCs after the upgrade
Refer to attached word file for detail explanation with screenshots and config preview files.
Issue : WLC Provisioning failed on DNAC
DNAC Version : 2.3.3.7 ( DN2-HW-APL-XL ) , 3 Node Cluster
On 4th of July Night at Singapore Time, the WLC was provisioned with additional Managed AP Locations where it was stuck for 9 Hours.
The Provision failed after 9 Hours of waiting with the below error :
A screenshot of a computer
Description automatically generated
The RCA Logs were generated after the failure for further investigation
The BU Escalation Team were involved and after analysis the Root Cause was identified as seen below :
Issue triggered due to duplication data in DB, resulting in Network Programmer running out of memory.
CSCwf89617 is addressed in 2.3.3.7. The fix is applicable only for WLC provisioning flows done after upgrading to 2.3.3.7.
The duplicated data is present in database prior to the Upgrade to 2.3.3.7
new defect CSCwd49629 is raised to handle the old stale entries in DB which might be carried forward after during upgrade to 2.3.3.7 and which are not handled by CSCwf89617.
The Workaround that was provided to resolve this issue is as follows :
Prune the DCS table to nullify the data, to clear the duplicated data.
Increase memory of network-programmer and spf-service
Subsequent sessions involved applying the workaround and provisioning the WLC’s which all resulted in success. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wireless)
Problem Code: Software Failure
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
1. New Sites/Floors cannot be provisioned to wlc - "No configuration was generated"
Because of that, new APs for that new floors cannot be provisioned, error is "NCWL10802: The site(s) YNC-RC2-02 is not managed by any Wireless Controllers. Please provision a Wireless Controller and specify the site(s) as Managed AP Location(s)."
2. Unexpected/unintended/Unrelated commands came out during the first provision to WLCs after the upgrade
Refer to attached word file for detail explanation with screenshots and config preview files. | DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
1. New Sites/Floors cannot be provisioned to wlc - "No configuration was generated"
Because of that, new APs for that new floors cannot be provisioned, error is "NCWL10802: The site(s) YNC-RC2-02 is not managed by any Wireless Controllers. Please provision a Wireless Controller and specify the site(s) as Managed AP Location(s)."
2. Unexpected/unintended/Unrelated commands came out during the first provision to WLCs after the upgrade
Refer to attached word file for detail explanation with screenshots and config preview files. | Issue : WLC Provisioning failed on DNAC
DNAC Version : 2.3.3.7 ( DN2-HW-APL-XL ) , 3 Node Cluster
On 4th of July Night at Singapore Time, the WLC was provisioned with additional Managed AP Locations where it was stuck for 9 Hours.
The Provision failed after 9 Hours of waiting with the below error :
A screenshot of a computer
Description automatically generated
The RCA Logs were generated after the failure for further investigation
The BU Escalation Team were involved and after analysis the Root Cause was identified as seen below :
Issue triggered due to duplication data in DB, resulting in Network Programmer running out of memory.
CSCwf89617 is addressed in 2.3.3.7. The fix is applicable only for WLC provisioning flows done after upgrading to 2.3.3.7.
The duplicated data is present in database prior to the Upgrade to 2.3.3.7
new defect CSCwd49629 is raised to handle the old stale entries in DB which might be carried forward after during upgrade to 2.3.3.7 and which are not handled by CSCwf89617.
The Workaround that was provided to resolve this issue is as follows :
Prune the DCS table to nullify the data, to clear the duplicated data.
Increase memory of network-programmer and spf-service
Subsequent sessions involved applying the workaround and provisioning the WLC’s which all resulted in success. | DNAC Provision Issues after upgraded to Version 2.3.3.7-72328
Client is unable to provision a 5540 WLC.
He stated that during the previous BEMS interaction they needed to add the new sites in the Cisco DNA Center hierarchy and then provision the WLC so it can manage those sites.
They could successfully add the new sites.
Now they wanted to provision the WLC (without doing any changes, just adding the new sites to be managed) and the provisioning is stucked here:
The client requested a WebEx when the provisioning was not moving after over 2 hours of waiting.
I took a fresh set of RCA and checked the SPF logs:
2023-07-04 12:53:23,353 | WARN | -service-manager-notify-1 | | c.c.g.a.i.GrapevineMessageListener | Error org.springframework.amqp.AmqpIllegalStateException was thrown for message handler of APSoftDeleteNotificationMessage {context={public={AuditParentCorrelationContext=null, AuditSourceIp=null, RBACSecurityContext=eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ0ZW5hbnQtY29tbW9uLXV0aWwiLCJhdXRoU291cmNlIjoiaW50ZXJuYWwiLCJ0ZW5hbnROYW1lIjoiVE5UMCIsInJvbGVzIjpbIjVkYjdiN2MwMTJmM2JkMDBjYzExNWY3YyJdLCJ0ZW5hbnRJZCI6IjVkYjdiN2JlMTJmM2JkMDBjYzExNWY3NyIsImV4cCI6MTY4ODQ3ODgwMywiaWF0IjoxNjg4NDc1MjAzLCJqdGkiOiJkNDgyYjYwNi1mYzhhLTQzMmItYWIxYy1jNmJhYjdjNTE1MjMiLCJ1c2VybmFtZSI6InRlbmFudC1jb21tb24tdXRpbCJ9.NWMFAsmWwPXuOngo1-uDNcgn5Dx-AuVMKNKNxPMzDjYHrNOikoGnj_y7-1VrV6PQNZEai-P6adE1P2IsPGv2jvlzEEXBXIkOGpy2bkkZ8YKkN54OlmvosG00R9EQlNg-1TxzT4GSUfr8Ii-c_5QNS3xHfMprwoHfzLtyjPfGK-CMTEyK5ixsx4q45PNKQ4NGZDoHVewJkinv-Zy5vZISAdPVaf2ylJ-R8eBvij8eVZWvqSJOAjH9QB-wf-TaI1KmA8MDcDgm_E8QeBUry2s-L9EfH1o9-Y1c0In1iVx9rDHMYC8PLSKSyFomCjg17T_Zyc9rwPCN-Di2ozZGc4XaPQ, accept-language=en_US, AuditCorrelationContext=14e0f0a1-ab0b-43eb-9d53-3cbd25a95ad9}}, replyToChain=null, version=0, payload=Request [WLC Device IP=172.18.240.16]Request [WLC Device ID=a19ede95-f7b2-45d1-9f56-b13d762a4593]Request [AP Device IP=10.253.135.167]Request [AP Device ID=756c7953-6a8c-4bd8-89f3-a8140a1ff7b0]Request [AP Mac Address=84:f1:47:6b:2b:c0]}. |
org.springframework.amqp.AmqpIllegalStateException: Unable to find suitable REQUEST handler for requestKey=com.cisco.enc.inventory.api.notifications.APSoftDeleteNotificationMessage
at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.getRequestHandler(GrapevineMessageListener.java:457) ~[message-queue-sdk-7.0.518.62181.jar:7.0.518.62181]
at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.invokeHandler_aroundBody0(GrapevineMessageListener.java:432) ~[message-queue-sdk-7.0.518.62181.jar:7.0.518.62181]
at com.cisco.grapevine.amqp.impl.GrapevineMessageListener$AjcClosure1.run(GrapevineMessageListener.java:1) ~[na:7.0.518.62181]
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) ~[aspectjtools-1.8.13.jar:na]
at com.cisco.enc.i18n.localization.aop.EnableI18nOnRequestHandler.getEmptyResponse(EnableI18nOnRequestHandler.java:26) ~[i18n-7.1.518.62181.jar:7.1.518.62181]
at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.invokeHandler(GrapevineMessageListener.java:398) ~[message-queue-sdk-7.0.518.62181.jar:7.0.518.62181]
at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.onMessage(GrapevineMessageListener.java:236) ~[message-queue-sdk-7.0.518.62181.jar:7.0.518.62181]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:546) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:472) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$001(SimpleMessageListenerContainer.java:61) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$1.invokeListener(SimpleMessageListenerContainer.java:110) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.invokeListener(SimpleMessageListenerContainer.java:611) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.executeListener(AbstractMessageListenerContainer.java:454) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.doReceiveAndExecute(SimpleMessageListenerContainer.java:474) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.receiveAndExecute(SimpleMessageListenerContainer.java:458) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$300(SimpleMessageListenerContainer.java:61) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.run(SimpleMessageListenerContainer.java:551) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
It is worth noting that the WLC was not sending assurance data to Cisco DNA Center and the WSA service was disabled.
We forced pushed telemetry. After that WSA and assurance became Active to this WLC.
Not sure if this can cause a block in the provisioning task. | DN2-HW-APL-XL | 2.3.3.7 | 2.3.3.7 | 47.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | DNAHW | Cisco DNA Center - On-Prem | Cisco DNA Center - Provisioning | 01t6R000007PJzCQAW | Error Messages, Logs, Debugs | Cisco DNA Center - Provisioning | Cisco DNA Center - On-Prem | 01t1C0000061ceEQAQ | SHERLOCK: PARTIAL |
695605404 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: Wireless Access Point disassociation/Flap
Wireless Access Point disassociation/Flap
The issue with respect to Ap flapping.
The Ap was going down due to Max retransmission. The issue was isolated to be on the switch end.
Once the switch was upgrade to 17.x firmware the issue is resolved.
RCA was provided to customer. Based on approval from them closing the case | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: Wireless Access Point disassociation/Flap
Wireless Access Point disassociation/Flap
The issue with respect to Ap flapping.
The Ap was going down due to Max retransmission. The issue was isolated to be on the switch end.
Once the switch was upgrade to 17.x firmware the issue is resolved.
RCA was provided to customer. Based on approval from them closing the case | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: Wireless Access Point disassociation/Flap | Wireless Access Point disassociation/Flap | The issue with respect to Ap flapping.
The Ap was going down due to Max retransmission. The issue was isolated to be on the switch end.
Once the switch was upgrade to 17.x firmware the issue is resolved.
RCA was provided to customer. Based on approval from them closing the case | Product: NA
Product Family: AIRCTA2
Software Version: 8.10.183.0
Router/Node Name: N/A
Problem Details: Wireless Access Point disassociation/Flap | AIR-CT8540-K9 | 16.12.3s | 16.12.3s | 52.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t1C000004GjbyQAC | Error Messages, Logs, Debugs | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t1C000006WMdqQAG | nan |
695138158 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
1. The issue was resolved after upgrading the devices to a cisco-suggested release.
2. The previous IOS being run on the devices was EoL and hence likely causing an unknown bug and hence the issue.
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-16/eos-eol-notice-c51-744154.html
++ okay with case closure after monitoring
++ thank you
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768.
SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768.
1. The issue was resolved after upgrading the devices to a cisco-suggested release.
2. The previous IOS being run on the devices was EoL and hence likely causing an unknown bug and hence the issue.
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-16/eos-eol-notice-c51-744154.html
++ okay with case closure after monitoring
++ thank you | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768.
SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768.
1. The issue was resolved after upgrading the devices to a cisco-suggested release.
2. The previous IOS being run on the devices was EoL and hence likely causing an unknown bug and hence the issue.
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-16/eos-eol-notice-c51-744154.html
++ okay with case closure after monitoring
++ thank you | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768. | SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768. | 1. The issue was resolved after upgrading the devices to a cisco-suggested release.
2. The previous IOS being run on the devices was EoL and hence likely causing an unknown bug and hence the issue.
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-16/eos-eol-notice-c51-744154.html
++ okay with case closure after monitoring
++ thank you | SDA FE - TCAM Exhaustion 96.0%, layer2 TCAM Usage is more than the limit
Map cache entries have exceeded limit. The maximum number of MAC addresses has been reached:32768. | C9300-48U-A | 16.12.4 | 16.12.4 | 73.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | Cisco Software-Defined Access (SDA Wired) | Cisco DNA Center - On-Prem | 01t15000005W0LTAA0 | SHERLOCK: PARTIAL |
695618886 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 2.2.2.9/ 2.2.2.9/ 2.1.2.7/ 16.12.01s/ 2.1.2.7/ 4.0.4b/ PRODUCT_NOT_FOUND/ 17.3.3/ 1.3.3.9/ 17.3.4a/ 1.3.3.7/ 2.2.3.6/ 2.2.2.3/ 2.1.2.0/ 2.1.2.7 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wireless)
Problem Code: Configuration Assistance
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Cannot see any DSCP marking after applying QoS policy to wireless SSID.
Cannot see any DSCP marking after applying QoS policy to wireless SSID.
++ each wireless profile can push the maximum of 32 applications only. As of now all the wired applications are working fine without any issue and markings are happening.
we checked the supportive document and its the expected behaviour for wireless having the cap of 32 applications. this will not be able to modify/edit as we have seen and from below document.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/Enterprise-Mobility-8-5-Design-Guide/Enterprise_Mobility_8-5_Deployment_Guide/ch5_QoS.html
++ we have filed a enhancement request to modify these applications and below bug can track this.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwf67618 | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-AP2802I-S-K9/ DN2-HW-APL-XL/ DN2-HW-APL/ DN2-HW-APL-L/ AIR-CT8540-K9/ UCSC-C480-M5/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wireless)
Problem Code: Configuration Assistance
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Cannot see any DSCP marking after applying QoS policy to wireless SSID.
Cannot see any DSCP marking after applying QoS policy to wireless SSID.
++ each wireless profile can push the maximum of 32 applications only. As of now all the wired applications are working fine without any issue and markings are happening.
we checked the supportive document and its the expected behaviour for wireless having the cap of 32 applications. this will not be able to modify/edit as we have seen and from below document.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/Enterprise-Mobility-8-5-Design-Guide/Enterprise_Mobility_8-5_Deployment_Guide/ch5_QoS.html
++ we have filed a enhancement request to modify these applications and below bug can track this.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwf67618 | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wireless)
Problem Code: Configuration Assistance
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Cannot see any DSCP marking after applying QoS policy to wireless SSID. | Cannot see any DSCP marking after applying QoS policy to wireless SSID. | ++ each wireless profile can push the maximum of 32 applications only. As of now all the wired applications are working fine without any issue and markings are happening.
we checked the supportive document and its the expected behaviour for wireless having the cap of 32 applications. this will not be able to modify/edit as we have seen and from below document.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/Enterprise-Mobility-8-5-Design-Guide/Enterprise_Mobility_8-5_Deployment_Guide/ch5_QoS.html
++ we have filed a enhancement request to modify these applications and below bug can track this.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwf67618 | Not able to see any DSCP marking after applying QoS policy to wireless SSID. | DN2-HW-APL-XL | 17.3.4a | 17.3.4a | 71.0 | 3 | 100.0 | Software Bug | DNAHW | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wireless) | 01t6R000005tUMBQA2 | Configuration Assistance | Cisco Software-Defined Access (SDA Wireless) | Cisco DNA Center - On-Prem | 01tA0000002qQtWIAU | nan |
695443169 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
looks like the traffic is not forwarded to the 6800 on the po20
from the packet capture we see that ARP flooding is happening on the outgoing interface of po20 but not seen on the 6800
- looks like platform issue for now as inter SDA communication is happening but l2 is broken between traditional and SDA.
-Software of Switch is in older code 16.12.1s
-Pending upgrade of L2Border device.
-All working after upgrade to o 17.6.4
-ok to close
Technology: LAN Switching
Subtechnology: CAT 9500 Unexpected Reboot
Problem Code: Software Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA L2 border switch (model 9500) stack running version 16.12.1s is using L2 flooding for a vlan/subnet. For this particular subnet, the L2 border seems not forwarding the arp requests and hence client in the same vlan are not able to communicate.
SDA L2 border switch (model 9500) stack running version 16.12.1s is using L2 flooding for a vlan/subnet. For this particular subnet, the L2 border seems not forwarding the arp requests and hence client in the same vlan are not able to communicate.
looks like the traffic is not forwarded to the 6800 on the po20
from the packet capture we see that ARP flooding is happening on the outgoing interface of po20 but not seen on the 6800
- looks like platform issue for now as inter SDA communication is happening but l2 is broken between traditional and SDA.
-Software of Switch is in older code 16.12.1s
-Pending upgrade of L2Border device.
-All working after upgrade to o 17.6.4
-ok to close | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
looks like the traffic is not forwarded to the 6800 on the po20
from the packet capture we see that ARP flooding is happening on the outgoing interface of po20 but not seen on the 6800
- looks like platform issue for now as inter SDA communication is happening but l2 is broken between traditional and SDA.
-Software of Switch is in older code 16.12.1s
-Pending upgrade of L2Border device.
-All working after upgrade to o 17.6.4
-ok to close
Technology: LAN Switching
Subtechnology: CAT 9500 Unexpected Reboot
Problem Code: Software Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA L2 border switch (model 9500) stack running version 16.12.1s is using L2 flooding for a vlan/subnet. For this particular subnet, the L2 border seems not forwarding the arp requests and hence client in the same vlan are not able to communicate.
SDA L2 border switch (model 9500) stack running version 16.12.1s is using L2 flooding for a vlan/subnet. For this particular subnet, the L2 border seems not forwarding the arp requests and hence client in the same vlan are not able to communicate.
looks like the traffic is not forwarded to the 6800 on the po20
from the packet capture we see that ARP flooding is happening on the outgoing interface of po20 but not seen on the 6800
- looks like platform issue for now as inter SDA communication is happening but l2 is broken between traditional and SDA.
-Software of Switch is in older code 16.12.1s
-Pending upgrade of L2Border device.
-All working after upgrade to o 17.6.4
-ok to close | Technology: LAN Switching
Subtechnology: CAT 9500 Unexpected Reboot
Problem Code: Software Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA L2 border switch (model 9500) stack running version 16.12.1s is using L2 flooding for a vlan/subnet. For this particular subnet, the L2 border seems not forwarding the arp requests and hence client in the same vlan are not able to communicate. | SDA L2 border switch (model 9500) stack running version 16.12.1s is using L2 flooding for a vlan/subnet. For this particular subnet, the L2 border seems not forwarding the arp requests and hence client in the same vlan are not able to communicate. | looks like the traffic is not forwarded to the 6800 on the po20
from the packet capture we see that ARP flooding is happening on the outgoing interface of po20 but not seen on the 6800
- looks like platform issue for now as inter SDA communication is happening but l2 is broken between traditional and SDA.
-Software of Switch is in older code 16.12.1s
-Pending upgrade of L2Border device.
-All working after upgrade to o 17.6.4
-ok to close | SDA L2 border switch seems not forwarding the ARP requests between SDA network - L2 flooding vlan/subnet and traditional network.
HW/SW details:
DNAC 3-node Cluster running 2.2.2.9.
C9500-48Y4C switch stack running IOS-XE 16.12.1s (CUST-SPECIAL:V1612_1S_CSCVR77599_2)
Further details:
It is a production environment which was working without problems for more than 2 years
Is seems that issue was triggered after SDA L2 border switch experienced a power outage around 9 weeks ago
Issue currently affecting one VLAN/VN.
The VN name is res_access_VN and the VLAN name is vl_sciyih_bms (which is vlan 7 in the L2 handoff) and in SDA fabric it is vlan 1102
It was used a couple of devices in the same subnet for testing purposes:
---> Device A on SDA network -------- 172.25.57.100 (Source IP)
---> Device B on traditional -------- 172.25.56.11 (Destination IP)
Device A is behind FE switch (ip: 172.18.1.61) and device B is on traditional network behind L2 switch (ip:172.18.112.141).
Business Impact: * Is the network or users affected at this point?
Yes. The meter systems (using exiBACNet) are not able to communicate and receive data. | C9300-48U-A | Gibraltar-16.12.1s | Gibraltar-16.12.1s | 60.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | 01t1C000004ah02QAA | Error Messages, Logs, Debugs | Cisco Software-Defined Access (SDA Wired) | Cisco DNA Center - On-Prem | 01t15000005W0LRAA0 | SHERLOCK: PARTIAL |
695810508 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 122.33/ 15.5.1 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat6500/6800 (Supervisor 2T) VSS
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C6800MD
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi, user requires a root cause analysis for why the distribution switch rebooted unexpectedly on its own.
Thank you
Hi, user requires a root cause analysis for why the distribution switch rebooted unexpectedly on its own.
Thank you
++No crashfile generated.
++Concluded as soft parity error. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: VS-C6509E-S720-10G/ C6807-XL Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat6500/6800 (Supervisor 2T) VSS
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C6800MD
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi, user requires a root cause analysis for why the distribution switch rebooted unexpectedly on its own.
Thank you
Hi, user requires a root cause analysis for why the distribution switch rebooted unexpectedly on its own.
Thank you
++No crashfile generated.
++Concluded as soft parity error. | Technology: LAN Switching
Subtechnology: Cat6500/6800 (Supervisor 2T) VSS
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C6800MD
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi, user requires a root cause analysis for why the distribution switch rebooted unexpectedly on its own.
Thank you | Hi, user requires a root cause analysis for why the distribution switch rebooted unexpectedly on its own.
Thank you | ++No crashfile generated.
++Concluded as soft parity error. | ++ Distribution Switch Reboot Automatically. | C6807-XL | 15.5(1)SY3 | 15.5(1)SY3 | 70.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | C6800MD | LAN Switching | Cat6500/6800 Unexpected Reboot | 01t1C000005yOfqQAE | Software Failure | Cat6500/6800 Unexpected Reboot | LAN Switching | 01t15000004dPUOAA2 | SHERLOCK: FULL;CaseClosureFieldAutomation: Partial |
694180161 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Cisco C9300-48U Switch output drops on AP interface, suspected cause of users disconnections.
over 100 APs are affected.
Cisco C9300-48U Switch output drops on AP interface, suspected cause of users disconnections.
over 100 APs are affected.
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
Gi1/0/1 0 0 0 0 0 52624298
Gi1/0/2 0 0 0 0 0 52168180
Gi1/0/3 0 0 0 0 0 53547902
Gi1/0/4 0 0 0 0 0 53849947
Gi1/0/5 0 0 0 0 0 53014579
Gi1/0/6 0 0 0 0 0 49926547
Gi1/0/7 0 0 0 0 0 53680013
** As per the above outputs, I could see that drops value are ideally the same.
** These output drops will not be related to the random disconnect as we are not seeing AP getting disconnected from the WLC.
** So the output drops will not be a direct issue of wireless users' disconnection. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Cisco C9300-48U Switch output drops on AP interface, suspected cause of users disconnections.
over 100 APs are affected.
Cisco C9300-48U Switch output drops on AP interface, suspected cause of users disconnections.
over 100 APs are affected.
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
Gi1/0/1 0 0 0 0 0 52624298
Gi1/0/2 0 0 0 0 0 52168180
Gi1/0/3 0 0 0 0 0 53547902
Gi1/0/4 0 0 0 0 0 53849947
Gi1/0/5 0 0 0 0 0 53014579
Gi1/0/6 0 0 0 0 0 49926547
Gi1/0/7 0 0 0 0 0 53680013
** As per the above outputs, I could see that drops value are ideally the same.
** These output drops will not be related to the random disconnect as we are not seeing AP getting disconnected from the WLC.
** So the output drops will not be a direct issue of wireless users' disconnection. | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Cisco C9300-48U Switch output drops on AP interface, suspected cause of users disconnections.
over 100 APs are affected. | Cisco C9300-48U Switch output drops on AP interface, suspected cause of users disconnections.
over 100 APs are affected. | Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
Gi1/0/1 0 0 0 0 0 52624298
Gi1/0/2 0 0 0 0 0 52168180
Gi1/0/3 0 0 0 0 0 53547902
Gi1/0/4 0 0 0 0 0 53849947
Gi1/0/5 0 0 0 0 0 53014579
Gi1/0/6 0 0 0 0 0 49926547
Gi1/0/7 0 0 0 0 0 53680013
** As per the above outputs, I could see that drops value are ideally the same.
** These output drops will not be related to the random disconnect as we are not seeing AP getting disconnected from the WLC.
** So the output drops will not be a direct issue of wireless users' disconnection. | Output drops on AP connected interfaces | C9300-48U-A | 16.12.4 | 16.12.4 | 49.0 | 3 | 100.0 | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | C9300 | LAN Switching | Cat9300 | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | Cat9300 | LAN Switching | 01t15000005W0LTAA0 | IRE: PARTIAL;SHERLOCK: PARTIAL |
694914231 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Hardware Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]
Hardware Failure
Please go ahead and close this case.
Hi Jimmy Tey,
All of the parts in RMA(s) 802711026 have been successfully delivered.
If you believe you are missing a part, or if a replacement part has arrived damaged or non-operational, please contact us within the next 24 hours.
If we do not receive a response from you in the next 24 hours, we will assume all is well and will proceed to close out this RMA.
RETURNING PARTS:
**** IT IS VERY IMPORTANT THAT YOU RETURN ONLY THE PART(s) ORDERED.****
For return shipments, only ship back the same parts that are received.
Please do not ship back any accessories such as cables, rack mounts,
manuals, CD's.
These accessories are only shipped with original shipments not with
Replacement parts.
Also, for modular replacements, all non-faulty
components will need to be swapped from the old device to the replacement
device.
This includes: WIC's; Network-Modules (NM's); Port Adapters (PA's); Memory; etc).
--------------------------------------------------------------------------------------------------------------------
To get the latest status on your RMA or on the return shipment you may
contact Cisco's Logistics or Asset Recovery department and reference your RMA#.
LOGISTICS: E-Mail <mailto:[email protected]> [email protected] or Phone
1-800-553-2447 Opt 4
ASSET RECOVERY: E-Mail <mailto:[email protected]>
[email protected] or Phone 1-800-800-1180 x67284, Opt 4
Delivery ID - 162474231 ;
Received By - Jimmy ;
Received On - 30-Jan-2023 09:03:06 GMT ;
POD Complete on - 30-Jan-2023 09:03:06 GMT ;
Tracking Number(s)- 145806011 ;
Line: 1.1 ; Product: C9300-NM-8X= ; Qty: 1 ;
***ORDER 802711026 END OF NOTIFICATION.
*** RMA/SVO 802711026 POD completed on 30-JAN-23 (GMT).
Please refer to:
https://ibpm.cisco.com/rma/home/?&&OrderNumber=802711026
ORDER NUMBER: 802711026
CREATED DATE: 27-Jan-2023 05:17:00 GMT
CREATED BY: [email protected] (JHWATSON)
SERVICE LEVEL: Advance Replacement - Warranty Same Day Ship
NOTIFICATION SENT TO:[email protected];[email protected]
NOTIFICATION SENT TIME: 27-Jan-2023 08:29:25 GMT
Your shipment is on its way:
Delivery ID - 162474231 ;
Shipped Date- 27-Jan-2023 08:27:42 GMT ;
Carrier- DSC ;
Tracking Number(s)- 145806011 ;
Line: 1.1 ; Product: C9300-NM-8X= ; Qty: 1 ; License Transfer:
Ship to Address:
NCS PTE LTD
5 ANG MO KIO STREET 62 NCS HUB
SINGAPORE,,569141
SG
Ship to Contact:
NAME: Samuel Tan/23458623
PHONE: +6587504718
LicenseTransfer Note
If the transfer of the license was requested during RMA creation, the acknowledgmentcontact will receive a separate email within 24 hours containing the new license keys and instructions.
If the transfer of the license was not requestedor the email with license key was not received, please follow the instructions below:
1.Log into the Licensing Portal
2.Under Manage, go to Devices, then Actions, then RMA.
3.Follow the on-screen prompts and enter the required information.
For additional information, please see below or [email protected] licensing support.
Document: License Registration Portal Basic User Guide
Video: How to generate a license for a failed device using the RMA function
Additional information: License Registration Portal Help page
Source PID: C9300-NM-8X= ;
Source Serial Number: FOC24424RV0 ;
Destination PID: C9300-NM-8X= ;
Destination Serial Number: FOC2633359Z ;
We were unable to verify the accuracy of the Source Serial Number. Please be sure to validate the Serial Numbers prior to using the RMA License Transfer tool to ensure a successful software license transfer.
***ORDER 802711026 END OF NOTIFICATION.
ORDER NUMBER: 802711026
CREATED DATE: 27-Jan-2023 05:17:00 GMT
CREATED BY: [email protected] (JHWATSON)
SERVICE LEVEL: Advance Replacement - Warranty Same Day Ship
NOTIFICATION SENT TO:[email protected];[email protected]
NOTIFICATION SENT TIME: 27-Jan-2023 05:34:33 GMT
***Parts ETA:***
Delivery ID: 162474231 ; ETA: 30-Jan-2023 09:00:00 GMT ;
Line: 1.1 ; Product: C9300-NM-8X= ; Qty: 1 ;
Ship to Address:
NCS PTE LTD
5 ANG MO KIO STREET 62 NCS HUB
SINGAPORE,,569141
SG
Ship to Contact:
NAME: Samuel Tan/23458623
PHONE: +6587504718
***ORDER 802711026 END OF NOTIFICATION.
Hi Pratishtha Yadav,
RMA 802711026 submitted.
Company Name:
Company Address:
SVO Access Enabled: false
City:
Cisco.com Id:
State/Province:
Name:
Zip Code:
Country:
Contact Name:
Email:
Sales Order #:
Comments for Person Receiving Shipment:
Special Shipping Instructions:
ORDER NUMBER: 802711026
CREATED DATE: 27-Jan-2023 05:17:00 GMT
CREATED BY: [email protected] (JHWATSON)
SERVICE LEVEL: Advance Replacement - Warranty Same Day Ship
NOTIFICATION SENT TO:[email protected];[email protected]
NOTIFICATION SENT TIME: 27-Jan-2023 05:17:56 GMT
Ship to Address:
NCS PTE LTD
5 ANG MO KIO STREET 62 NCS HUB
SINGAPORE,,569141
SG
Ship to Contact:
NAME: Samuel Tan/23458623
PHONE: +6587504718
Failure Code: OHW4 - HW Fail - Boot Up
SVO Status URL: https://ibpm.cisco.com/rma/home/?OrderNumber=802711026
***Parts Ordered:***
Line: 1.1 ; Product: C9300-NM-8X= ; Qty: 1 ;
***ORDER Return Line Detail:***
Scheduled Return Date: 06-Feb-2023 05:35:19 GMT ;
Line: 2.1 ; Product: C9300-NM-8X= ; Qty: 1 ;
Serial Number(s): FOC24424RV0 ;
*** ORDER 802711026 END OF NOTIFICATION.
Thank you for taking time to share all the relevant information.
The RMA Creation has been initiated by concerned engineer.
Please use below link to track the progress of request.
https://ibpm.cisco.com/rma/home/?RMANumber=802711026
Your recent RMA#802711026 is handed off.
Please use the RMA completion link to submit the order.
*** ACTIONS PENDING RMA REQUESTER ***
Order handoff email has been sent to the Order Requester to complete the order submission.
NOTIFICATION SENT TO: [email protected]
NOTIFICATION SENT TIME: 27-Jan-2023 04:15:14 GMT
Order completion link :
https://ibpm.cisco.com/rma/home/?RMANumber=802711026
Resolution Summary:
Automatic RMA submitted for C9300-NM-8X=
Action Plan:
An RMA has been generated.
Shipping & Delivery Info: Not Available Customer to fill out RMA details
The case will be closed 24-48 hours after the RMA is fulfilled or expired.
*** ACTIONS PENDING RMA REQUESTER ***
Order handoff email has been sent to the Order Requester to complete the order submission.
NOTIFICATION SENT TO: [email protected]
NOTIFICATION SENT TIME: 27-Jan-2023 04:15:14 GMT
Order completion link :
https://ibpm.cisco.com/rma/home/?RMANumber=802711026
*********************************************************************************************
Draft ORDER NUMBER: 802711026
Draft ORDER INITIATED BY (Order creator): (jhwatson)
Order Details:
Serial Number: FOC24424RV0 ; Product: C9300-NM-8X= ; Contract: WARRANTY ; Service Level: Advance Replacement - Warranty Same Day Ship ; Qty: 1 ; Labor: No ;
Note: If this Order has multiple service levels, it will be split into separate Order numbers at Order review & submit (during Order submission)
*** ORDER 802711026 END OF NOTIFICATION.
Problem Description:
The IRE process has identified Hardware Failure
Current Status:
Decision: ADHOC-RMA
Status: DRAFT_RMA_COMPLETED
Shipping & Delivery Info: Not Available
Please refer the attachment.
Please assist.
3rd follow up.
Could you please help us provide below outputs.
This would help us better to isolate the issue.
* show environment
* show module
Please follow up.
18th January, 2023
Sent IR
Asked below questions -
Before proceeding we would need to do some checks. Could you please share below information-
1. How long have you been facing this issue? Was it a working setup or a new setup?
2. What is the LED status of the module.
3. Have you done any recent changes in the network?
4. Is the power cable connected properly?
5. Did you try connecting the switch to a known working power source and power socket with known working power cables?
6. Please share a snapshot of the front and back panel of the device with the power cables connected?
7. Do you want to share any additional information ?
19th January, 2023
Got below response-
1. How long have you been facing this issue? Was it a working setup or a new setup? Issue noticed for a week, this 10G network module is not detected. This is existing setup. Was working fine previously.
2. What is the LED status of the module. No LED status.
3. Have you done any recent changes in the network? No changes.
4. Is the power cable connected properly? Verified power cable are working. Also Have tried use with our other spare module and is that is OK. however this still not Woking
5. Did you try connecting the switch to a known working power source and power socket with known working power cables? Yes have tried also reseating the module doesn’t work.
19th January, 2023
Asked for below output
show environment
show module
show tech
21st January, 2023
Sent a follow up email for above outputs.
23rd January, 2023
Sent follow up email.
2nd follow up.
Could you please share output for "show tech" as this would help us understand if there are any logs generated.
18th January, 2023
Sent IR
Asked below questions -
Before proceeding we would need to do some checks. Could you please share below information-
1. How long have you been facing this issue? Was it a working setup or a new setup?
2. What is the LED status of the module.
3. Have you done any recent changes in the network?
4. Is the power cable connected properly?
5. Did you try connecting the switch to a known working power source and power socket with known working power cables?
6. Please share a snapshot of the front and back panel of the device with the power cables connected?
7. Do you want to share any additional information ?
19th January, 2023
Got below response-
1. How long have you been facing this issue? Was it a working setup or a new setup? Issue noticed for a week, this 10G network module is not detected. This is existing setup. Was working fine previously.
2. What is the LED status of the module. No LED status.
3. Have you done any recent changes in the network? No changes.
4. Is the power cable connected properly? Verified power cable are working. Also Have tried use with our other spare module and is that is OK. however this still not Woking
5. Did you try connecting the switch to a known working power source and power socket with known working power cables? Yes have tried also reseating the module doesn’t work.
19th January, 2023
Asked for below output
show environment
show module
show tech
21st January, 2023
Sent a follow up email for above outputs.
Hope you are doing well.
This is a follow up email to check if you got a chance to collect outputs for previously mentioned commands.
This would help us understand if there are any logs generated.
20th January, 2023
waiting on customer response.
Unable to detect module C9300-NM-8X= on Cat9300
18th January, 2023
Sent IR
Asked below questions -
Before proceeding we would need to do some checks. Could you please share below information-
1. How long have you been facing this issue? Was it a working setup or a new setup?
2. What is the LED status of the module.
3. Have you done any recent changes in the network?
4. Is the power cable connected properly?
5. Did you try connecting the switch to a known working power source and power socket with known working power cables?
6. Please share a snapshot of the front and back panel of the device with the power cables connected?
7. Do you want to share any additional information ?
19th January, 2023
Got below response-
1. How long have you been facing this issue? Was it a working setup or a new setup? Issue noticed for a week, this 10G network module is not detected. This is existing setup. Was working fine previously.
2. What is the LED status of the module. No LED status.
3. Have you done any recent changes in the network? No changes.
4. Is the power cable connected properly? Verified power cable are working. Also Have tried use with our other spare module and is that is OK. however this still not Woking
5. Did you try connecting the switch to a known working power source and power socket with known working power cables? Yes have tried also reseating the module doesn’t work.
19th January, 2023
Asked for below output
show environment
show module
show tech
Sent IR
Asked below questions -
Before proceeding we would need to do some checks. Could you please share below information-
1. How long have you been facing this issue? Was it a working setup or a new setup?
2. What is the LED status of the module.
3. Have you done any recent changes in the network?
4. Is the power cable connected properly?
5. Did you try connecting the switch to a known working power source and power socket with known working power cables?
6. Please share a snapshot of the front and back panel of the device with the power cables connected?
7. Do you want to share any additional information ?
Got below response-
1. How long have you been facing this issue? Was it a working setup or a new setup? Issue noticed for a week, this 10G network module is not detected. This is existing setup. Was working fine previously.
2. What is the LED status of the module. No LED status.
3. Have you done any recent changes in the network? No changes.
4. Is the power cable connected properly? Verified power cable are working. Also Have tried use with our other spare module and is that is OK. however this still not Woking
5. Did you try connecting the switch to a known working power source and power socket with known working power cables? Yes have tried also reseating the module doesn’t work.
Asked for below output
show environment
show module
show tech
Unable to detect module C9300-NM-8X= on Cat9300.
Thanks for sharing this information.
Could you also please share outputs for below commands:-
* show environment
* show module
Hi Pratishtha Yadav,
1.
How long have you been facing this issue? Was it a working setup or a new setup? Issue noticed for a week, this 10G network module is not detected.
This is existing setup.
Was working fine previously.
2.
What is the LED status of the module.
No LED status.
3.
Have you done any recent changes in the network? No changes.
4.
Is the power cable connected properly? Verified power cable are working.
Also Have tried use with our other spare module and is that is OK.
however this still not Woking
5.
Did you try connecting the switch to a known working power source and power socket with known working power cables? Yes have tried also reseating the module doesn't work.
Please assist.
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect.
no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]<mailto:[email protected]>
I am Pratishtha Yadav from CISCO TAC Asia-Pacific LAN Switching team.
I have the ownership of your service request with SR: 694914231.
I will be closely working with you towards the final resolution of this service request.
I have reviewed the case.
Based on the case notes, here is my understanding of the issue.
Problem Description:
Unable to detect module C9300-NM-8X= on Cat9300.
Action Plan:
Before proceeding we would need to do some checks.
Could you please share below information-
1.
How long have you been facing this issue? Was it a working setup or a new setup?
2.
What is the LED status of the module.
3.
Have you done any recent changes in the network?
4.
Is the power cable connected properly?
5.
Did you try connecting the switch to a known working power source and power socket with known working power cables?
6.
Please share a snapshot of the front and back panel of the device with the power cables connected?
7.
Do you want to share any additional information ?
While replying to my emails, please include a copy to [email protected]<mailto:[email protected]> or use reply-all to ensure that all our conversation regarding the case are attached to the case notes automatically.
My contact details and shift hours are mentioned below.
In case, if you need immediate attention outside of my working hours, please call on below TAC frontline contact numbers to have your SR transferred to an on-shift engineer.
You can now upload files to the case using FTP/FTPS/SCP/SFTP/HTTPS protocols and the following details:
Hostname: cxd.cisco.com
Username: 694914231
Password: BaRevshKZ7BXl7Gz
Please note:
1. When uploading to HTTPS the path must be set to /home/<filename>, for all other protocols the path is always '/<filename>'
2. Empty files, that is files with a size of 0 Bytes, will not be attached and will be deleted automatically.
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Hardware Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Hardware Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]
Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]
timestamp : 2023-01-27T04:15:20.000+0000 || updatedby : jhwatson || type : Resolution Summary || visibility : External || details : Resolution Summary:
Automatic RMA submitted for C9300-NM-8X= | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Hardware Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]
Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected]
timestamp : 2023-01-27T04:15:20.000+0000 || updatedby : jhwatson || type : Resolution Summary || visibility : External || details : Resolution Summary:
Automatic RMA submitted for C9300-NM-8X= | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Hardware Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected] | Hi TAC Team,
Please kindly help to raise an RMA for below details.
[Please reply-to-all, so that all the concerned parties in the cc: list also be kept in loop]
CCO ID# SCSLIMITED
P/N# C9300-NM-8X
Faulty S/N# FOC24424RV0
Fault# Unable to detect. no output.
Qty# 01EA
Ship To Address:
NCS PTE LTD
5 ANG MO KIO STREET 62
NCS HUB
SINGAPORE 569141
Ship To Contact# Samuel Tan/Case# 23458623
Phone# +65 87504718
Email# [email protected] | timestamp : 2023-01-27T04:15:20.000+0000 || updatedby : jhwatson || type : Resolution Summary || visibility : External || details : Resolution Summary:
Automatic RMA submitted for C9300-NM-8X= | nan | C9300-NM-8X | NA - RMA | nan | nan | 3 | nan | Hardware Failure | C9300 | LAN Switching | Cat9300 | nan | nan | nan | nan | nan | nan |
695138053 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Cu acknowledged closure as Cu planning to connect both WLCs' RP ports back to back using fiber link and media converter which will take some time. If post connecting WLC back to back issue reoccur Cu will reach out to us
-------------
Cu had query, answered the same
-------------
2nd follow up done
----------
1st follow up done
-----------
Cu reverted back with query, answered the same
------------
3rd follow up done
--------------
2nd follow up
-------------
1st follow up done
-------------
Cu to increase the HA keep alive timers
--------------
Issue is occurring due to RP link latency.
Asked Cu to increase the HA timers and check if issue still persist.
In case issue still persist, we need to connect devices back to back to check if the issue is due to WLC
------------
From the logs, shared the analysis
requested for redundancy summary to check the HA keep alive timer configuration
------------
Sent IR
Since the reset date was 2021, asked Cu when was the issue last happened.
Asked for latest tech-support and support bundle from WLC.
-------------------------
Reference case:
692758235
Next Action plan was shared:
1. Work with your network team to traverse the entire topology between the wireless controllers and check all network devices in the path to verify that the WLC RP VLAN is not added as an SVI on any of these. We will further have to validate that only the WLC mac-address is being learnt on the VLAN on all network devices which can be confirmed by taking a ‘show mac-address table’ output from all the intermediate switches.
2. Another recommendation by the internal team is to disable the ‘Gateway reachability check’ under WLC->Controller->Redundancy. By disabling this feature, we can confirm if the issue arises due to intermittent reachability loss of the standby to its gateway. If that is the cause, then disabling the feature will not lead to any further reboots of the WLC. However, if the WLC reboots post disabling this feature, then we can ignore this cause. Please note that this test can best be confirmed when the issue is frequent. As I understand from our last call, the WLC has been stable for over the past 4 months, hence to get the best results, perform this test when issue has resurfaced. Also, note that disabling this feature will cause a reboot of the controllers, so please plan to make this change during a downtime.
Cu to update if they have tried disabling the gateway reachability check and post changes what was the observation
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: While performing firmware upgrade, the WLC reset with the error below:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11)
Reset time : Sat Dec 18 02:11:51 2021
Trace back : 0x8f5754 0x1e1af9a 0x1ea0b04 0x1e8f251 0x1e95ad6 0x1e8b99e 0x1e23d97 0x7dff 0xe898d
Kindly assign this ticket to APAC support as the client wished to get RCA on this issue
Reference case number: 692758235
Derek
+6590129432
While performing firmware upgrade, the WLC reset with the error below:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11)
Reset time : Sat Dec 18 02:11:51 2021
Trace back : 0x8f5754 0x1e1af9a 0x1ea0b04 0x1e8f251 0x1e95ad6 0x1e8b99e 0x1e23d97 0x7dff 0xe898d
Kindly assign this ticket to APAC support as the client wished to get RCA on this issue
Reference case number: 692758235
Derek
+6590129432
* Logs indicating Standby was rebooting due to due to RP link latency try increasing the HA timers configure on your WLC, and check if the issue still persist.
Please find the process below to achieve the same:
Via GUI:
Controller > Redundancy > Global Configuration >
Keep Alive Timer: 500-800 millisecond.
Keep Alive Retries: 8-10 retries.
Via CLI:
(Cisco Controller) >config redundancy timer keep-alive-timer <timer msecs>
(Cisco Controller) >config redundancy retries keep-alive-retry <retry count>
* We can test connecting both WLC back to back and test if issue arises again, I understand it won’t be convenient but to conclude it to be a hardware issue we need to test the behavior by connecting both WLC back to back (or keeping max distance to 100 meters as we know: A direct physical connection between Active and Standby Redundant Ports is highly recommended. The distance between the connections can go up to 100 meters at per Ethernet cable standards.
* We can monitor the frequency of issue > Accordingly we can predict the next trigger for the issue so we can check the L1 connectivity (where the packets are getting dropped) also as previously suggested Work with your network team to traverse the entire topology between the wireless controllers and check all network devices in the path to verify that the WLC RP VLAN is not added as an SVI on any of these. We will further have to validate that only the WLC mac-address is being learnt on the VLAN on all network devices which can be confirmed by taking a ‘show mac-address table’ output from all the intermediate switches. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: While performing firmware upgrade, the WLC reset with the error below:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11)
Reset time : Sat Dec 18 02:11:51 2021
Trace back : 0x8f5754 0x1e1af9a 0x1ea0b04 0x1e8f251 0x1e95ad6 0x1e8b99e 0x1e23d97 0x7dff 0xe898d
Kindly assign this ticket to APAC support as the client wished to get RCA on this issue
Reference case number: 692758235
Derek
+6590129432
While performing firmware upgrade, the WLC reset with the error below:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11)
Reset time : Sat Dec 18 02:11:51 2021
Trace back : 0x8f5754 0x1e1af9a 0x1ea0b04 0x1e8f251 0x1e95ad6 0x1e8b99e 0x1e23d97 0x7dff 0xe898d
Kindly assign this ticket to APAC support as the client wished to get RCA on this issue
Reference case number: 692758235
Derek
+6590129432
* Logs indicating Standby was rebooting due to due to RP link latency try increasing the HA timers configure on your WLC, and check if the issue still persist.
Please find the process below to achieve the same:
Via GUI:
Controller > Redundancy > Global Configuration >
Keep Alive Timer: 500-800 millisecond.
Keep Alive Retries: 8-10 retries.
Via CLI:
(Cisco Controller) >config redundancy timer keep-alive-timer <timer msecs>
(Cisco Controller) >config redundancy retries keep-alive-retry <retry count>
* We can test connecting both WLC back to back and test if issue arises again, I understand it won’t be convenient but to conclude it to be a hardware issue we need to test the behavior by connecting both WLC back to back (or keeping max distance to 100 meters as we know: A direct physical connection between Active and Standby Redundant Ports is highly recommended. The distance between the connections can go up to 100 meters at per Ethernet cable standards.
* We can monitor the frequency of issue > Accordingly we can predict the next trigger for the issue so we can check the L1 connectivity (where the packets are getting dropped) also as previously suggested Work with your network team to traverse the entire topology between the wireless controllers and check all network devices in the path to verify that the WLC RP VLAN is not added as an SVI on any of these. We will further have to validate that only the WLC mac-address is being learnt on the VLAN on all network devices which can be confirmed by taking a ‘show mac-address table’ output from all the intermediate switches. | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: While performing firmware upgrade, the WLC reset with the error below:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11)
Reset time : Sat Dec 18 02:11:51 2021
Trace back : 0x8f5754 0x1e1af9a 0x1ea0b04 0x1e8f251 0x1e95ad6 0x1e8b99e 0x1e23d97 0x7dff 0xe898d
Kindly assign this ticket to APAC support as the client wished to get RCA on this issue
Reference case number: 692758235
Derek
+6590129432 | While performing firmware upgrade, the WLC reset with the error below:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11)
Reset time : Sat Dec 18 02:11:51 2021
Trace back : 0x8f5754 0x1e1af9a 0x1ea0b04 0x1e8f251 0x1e95ad6 0x1e8b99e 0x1e23d97 0x7dff 0xe898d
Kindly assign this ticket to APAC support as the client wished to get RCA on this issue
Reference case number: 692758235
Derek
+6590129432 | * Logs indicating Standby was rebooting due to due to RP link latency try increasing the HA timers configure on your WLC, and check if the issue still persist.
Please find the process below to achieve the same:
Via GUI:
Controller > Redundancy > Global Configuration >
Keep Alive Timer: 500-800 millisecond.
Keep Alive Retries: 8-10 retries.
Via CLI:
(Cisco Controller) >config redundancy timer keep-alive-timer <timer msecs>
(Cisco Controller) >config redundancy retries keep-alive-retry <retry count>
* We can test connecting both WLC back to back and test if issue arises again, I understand it won’t be convenient but to conclude it to be a hardware issue we need to test the behavior by connecting both WLC back to back (or keeping max distance to 100 meters as we know: A direct physical connection between Active and Standby Redundant Ports is highly recommended. The distance between the connections can go up to 100 meters at per Ethernet cable standards.
* We can monitor the frequency of issue > Accordingly we can predict the next trigger for the issue so we can check the L1 connectivity (where the packets are getting dropped) also as previously suggested Work with your network team to traverse the entire topology between the wireless controllers and check all network devices in the path to verify that the WLC RP VLAN is not added as an SVI on any of these. We will further have to validate that only the WLC mac-address is being learnt on the VLAN on all network devices which can be confirmed by taking a ‘show mac-address table’ output from all the intermediate switches. | Hardware: AIR-CT8540-K9
Issue: HA are losing reachability and the WLCs are reloading with the following reason:
Reset reason : Peer-RMI, peer-RP and management default gateway are reachable ,(Version: 8.10.130.11) | AIR-CT8540-K9 | 8.10.183.0 | 8.10.183.0 | 71.0 | 3 | 100.0 | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t6R000007OTqHQAW | Error Messages, Logs, Debugs | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t15000004dDRMAA2 | nan |
694913120 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 17.03.04a/ 17.3.4a Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Workaround is provided for the issue. Cu will upgrade the router in May.
Technology: Router and IOS Architecture
Subtechnology: Memory Allocation Failure
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H
Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H
Workaround is provided for the issue. Cu will upgrade the router in May. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: ASR1002-HX/ ASR1009-X Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Router and IOS Architecture
Subtechnology: Memory Allocation Failure
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H
Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H
Workaround is provided for the issue. Cu will upgrade the router in May. | Technology: Router and IOS Architecture
Subtechnology: Memory Allocation Failure
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H | Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H | Workaround is provided for the issue. Cu will upgrade the router in May. | Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: Critical - QFP 0 IRAM(EXMEM) at 98 percent, exceeds critical level 95
HSDC-DBN-RTR01#show platform hardware qfp active infrastructure exmem statistics
QFP exmem statistics
Type: Name: DRAM, QFP: 0
Total: 8589934592
InUse: 3510652928
Free: 5079281664
Lowest free water mark: 5071855616
Type: Name: IRAM, QFP: 0
Total: 134217728
InUse: 132231168
Free: 1986560
Lowest free water mark: 1986560
Type: Name: SRAM, QFP: 0
Total: 0
InUse: 0
Free: 0
Lowest free water mark: 0
HSDC-DBN-RTR01# show platform resources
**State Acronym: H - Healthy, W - Warning, C - Critical
Resource Usage Max Warning Critical State
----------------------------------------------------------------------------------------------------
RP0 (ok, active) H
Control Processor 1.23% 100% 80% 90% H
DRAM 4143MB(6%) 63417MB 88% 93% H
bootflash 3969MB(58%) 6840MB 88% 93% H
harddisk 32MB(0%) 93836MB 88% 93% H
ESP0(ok, active) C
Control Processor 1.32% 100% 80% 90% H
DRAM 1253MB(3%) 32015MB 88% 93% H
QFP C
TCAM 64cells(0%) 1048576cells 65% 85% H
DRAM 3428372KB(40%) 8388608KB 85% 95% H
IRAM 129132KB(98%) 131072KB 85% 95% C
CPU Utilization 7.00% 100% 90% 95% H
Pkt Buf Mem (0) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (1) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (2) 67KB(0%) 524288KB 85% 95% H
Pkt Buf Mem (3) 67KB(0%) 524288KB 85% 95% H
SIP0 H
Control Processor 9.61% 100% 80% 90% H
DRAM 687MB(35%) 1955MB 88% 93% H
SIP1 H
Control Processor 3.20% 100% 80% 90% H
DRAM 626MB(32%) 1955MB 88% 93% H | ASR1009-X | 17.3.4a | 17.3.4a | 72.0 | 3 | 100.0 | Software Bug | ASR1000 | Router and IOS-XE Architecture | IOS-XE - NETCONF and RESTCONF and YANG | 01t6R000005tULsQAM | Configuration Assistance | IOS-XE - NETCONF and RESTCONF and YANG | Router and IOS-XE Architecture | 01t15000004dDisAAE | SHERLOCK: PARTIAL |
695146873 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Server rebooted automatically due to critical software exception. Would like to confirm the cause.
Server rebooted automatically due to critical software exception. Would like to confirm the cause.
Thanks you for sharing the show tech and the system report files.
Hardware : C9300-48U
Software : 16.12.04
------------------ show logging onboard switch 1 uptime detail ------------------
--------------------------------------------------------------------------------
UPTIME SUMMARY INFORMATION
--------------------------------------------------------------------------------
First customer power on : 03/13/2021 04:48:04
Total uptime : 1 years 36 weeks 5 days 11 hours 21 minutes
Total downtime : 0 years 13 weeks 4 days 10 hours 10 minutes
Number of resets : 16
Number of slot changes : 0
Current reset reason : Critical software exception
Current reset timestamp : 02/24/2023 16:20:01
Current slot : 1
Chassis type : 99
Current uptime : 0 years 0 weeks 4 days 10 hours 0 minutes
--------------------------------------------------------------------------------
Decoded stack traces:
1. 0x56053df14014 <BE> access_tunnel_oqueue
2. 0x5605403754ce <BE> datagram_out
3. 0x56053de73413 <BE> pm_vlan_bridge_or_compute_port_set
4. 0x56053de735ed <BE> pm_vlan_bridge_packet
5. 0x56053df881e6 <BE> arp_snoop_process
From the decoded stack traces looks like we are hitting the below defect:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu93346<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fapc01.safelinks.protection.outlook.com%2f%3furl%3dhttps%253A%252F%252Fddec1%2d0%2den%2dctp.trendmicro.com%252Fwis%252Fclicktime%252Fv1%252Fquery%253Furl%253Dhttps%25253a%25252f%25252fapc01.safelinks.protection.outlook.com%25252f%25253furl%25253dhttps%2525253A%2525252F%2525252Fbst.cloudapps.cisco.com%2525252Fbugsearch%2525252Fbug%2525252FCSCvu93346%252526data%25253d05%2525257C01%2525257Ckeane.phua.caijun%25252540ncs.com.sg%2525257C5fa4762486cb4121d02f08db1f989197%2525257Cca90d8f589634b6ebca99ac468bcc7a8%2525257C1%2525257C0%2525257C638138512367379254%2525257CUnknown%2525257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%2525253D%2525257C3000%2525257C%2525257C%2525257C%252526sdata%25253d20QWTMRQAf9JUG5ddM0%2525252FhzKGlOBzdODQSVwwTTXgbes%2525253D%252526reserved%25253d0%2526umid%253D7534ffb8%2de466%2d4e12%2da569%2d231f9b03e0e1%2526auth%253D32813f2e647ebb91b39d0b35ac97db1efa82dd64%2d097b8edbb06a5ebfbc12c8981b429ff594e539d1%26data%3d05%257C01%257Cgeorgekingsley.paulsundararaj%2540ncs.com.sg%257Cc6e89c2ed32e4d21c91208db1f9bf30a%257Cca90d8f589634b6ebca99ac468bcc7a8%257C1%257C0%257C638138526885301089%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%257C%257C%257C%26sdata%3dEmVZCmiW9o0%252FLqF7AmsAZOQoAWcm1JDQusNWxScP3t0%253D%26reserved%3d0&umid=48f669ec-c0e9-4e2c-b663-a06eb2569ec1&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-563a432c0d33496048faedcfe67aae8255142649>;
You can also find the known fixed releases for this bug from the known fixed releases box, and the only way to mitigate this bug will be by upgrading the device to known fixed release.
The crash is happening after DNAC makes some interface changes and pushes to the switch's configuration. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Server rebooted automatically due to critical software exception. Would like to confirm the cause.
Server rebooted automatically due to critical software exception. Would like to confirm the cause.
Thanks you for sharing the show tech and the system report files.
Hardware : C9300-48U
Software : 16.12.04
------------------ show logging onboard switch 1 uptime detail ------------------
--------------------------------------------------------------------------------
UPTIME SUMMARY INFORMATION
--------------------------------------------------------------------------------
First customer power on : 03/13/2021 04:48:04
Total uptime : 1 years 36 weeks 5 days 11 hours 21 minutes
Total downtime : 0 years 13 weeks 4 days 10 hours 10 minutes
Number of resets : 16
Number of slot changes : 0
Current reset reason : Critical software exception
Current reset timestamp : 02/24/2023 16:20:01
Current slot : 1
Chassis type : 99
Current uptime : 0 years 0 weeks 4 days 10 hours 0 minutes
--------------------------------------------------------------------------------
Decoded stack traces:
1. 0x56053df14014 <BE> access_tunnel_oqueue
2. 0x5605403754ce <BE> datagram_out
3. 0x56053de73413 <BE> pm_vlan_bridge_or_compute_port_set
4. 0x56053de735ed <BE> pm_vlan_bridge_packet
5. 0x56053df881e6 <BE> arp_snoop_process
From the decoded stack traces looks like we are hitting the below defect:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu93346<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fapc01.safelinks.protection.outlook.com%2f%3furl%3dhttps%253A%252F%252Fddec1%2d0%2den%2dctp.trendmicro.com%252Fwis%252Fclicktime%252Fv1%252Fquery%253Furl%253Dhttps%25253a%25252f%25252fapc01.safelinks.protection.outlook.com%25252f%25253furl%25253dhttps%2525253A%2525252F%2525252Fbst.cloudapps.cisco.com%2525252Fbugsearch%2525252Fbug%2525252FCSCvu93346%252526data%25253d05%2525257C01%2525257Ckeane.phua.caijun%25252540ncs.com.sg%2525257C5fa4762486cb4121d02f08db1f989197%2525257Cca90d8f589634b6ebca99ac468bcc7a8%2525257C1%2525257C0%2525257C638138512367379254%2525257CUnknown%2525257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%2525253D%2525257C3000%2525257C%2525257C%2525257C%252526sdata%25253d20QWTMRQAf9JUG5ddM0%2525252FhzKGlOBzdODQSVwwTTXgbes%2525253D%252526reserved%25253d0%2526umid%253D7534ffb8%2de466%2d4e12%2da569%2d231f9b03e0e1%2526auth%253D32813f2e647ebb91b39d0b35ac97db1efa82dd64%2d097b8edbb06a5ebfbc12c8981b429ff594e539d1%26data%3d05%257C01%257Cgeorgekingsley.paulsundararaj%2540ncs.com.sg%257Cc6e89c2ed32e4d21c91208db1f9bf30a%257Cca90d8f589634b6ebca99ac468bcc7a8%257C1%257C0%257C638138526885301089%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%257C%257C%257C%26sdata%3dEmVZCmiW9o0%252FLqF7AmsAZOQoAWcm1JDQusNWxScP3t0%253D%26reserved%3d0&umid=48f669ec-c0e9-4e2c-b663-a06eb2569ec1&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-563a432c0d33496048faedcfe67aae8255142649>;
You can also find the known fixed releases for this bug from the known fixed releases box, and the only way to mitigate this bug will be by upgrading the device to known fixed release.
The crash is happening after DNAC makes some interface changes and pushes to the switch's configuration. | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Server rebooted automatically due to critical software exception. Would like to confirm the cause. | Server rebooted automatically due to critical software exception. Would like to confirm the cause. | Thanks you for sharing the show tech and the system report files.
Hardware : C9300-48U
Software : 16.12.04
------------------ show logging onboard switch 1 uptime detail ------------------
--------------------------------------------------------------------------------
UPTIME SUMMARY INFORMATION
--------------------------------------------------------------------------------
First customer power on : 03/13/2021 04:48:04
Total uptime : 1 years 36 weeks 5 days 11 hours 21 minutes
Total downtime : 0 years 13 weeks 4 days 10 hours 10 minutes
Number of resets : 16
Number of slot changes : 0
Current reset reason : Critical software exception
Current reset timestamp : 02/24/2023 16:20:01
Current slot : 1
Chassis type : 99
Current uptime : 0 years 0 weeks 4 days 10 hours 0 minutes
--------------------------------------------------------------------------------
Decoded stack traces:
1. 0x56053df14014 <BE> access_tunnel_oqueue
2. 0x5605403754ce <BE> datagram_out
3. 0x56053de73413 <BE> pm_vlan_bridge_or_compute_port_set
4. 0x56053de735ed <BE> pm_vlan_bridge_packet
5. 0x56053df881e6 <BE> arp_snoop_process
From the decoded stack traces looks like we are hitting the below defect:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu93346<https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fapc01.safelinks.protection.outlook.com%2f%3furl%3dhttps%253A%252F%252Fddec1%2d0%2den%2dctp.trendmicro.com%252Fwis%252Fclicktime%252Fv1%252Fquery%253Furl%253Dhttps%25253a%25252f%25252fapc01.safelinks.protection.outlook.com%25252f%25253furl%25253dhttps%2525253A%2525252F%2525252Fbst.cloudapps.cisco.com%2525252Fbugsearch%2525252Fbug%2525252FCSCvu93346%252526data%25253d05%2525257C01%2525257Ckeane.phua.caijun%25252540ncs.com.sg%2525257C5fa4762486cb4121d02f08db1f989197%2525257Cca90d8f589634b6ebca99ac468bcc7a8%2525257C1%2525257C0%2525257C638138512367379254%2525257CUnknown%2525257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%2525253D%2525257C3000%2525257C%2525257C%2525257C%252526sdata%25253d20QWTMRQAf9JUG5ddM0%2525252FhzKGlOBzdODQSVwwTTXgbes%2525253D%252526reserved%25253d0%2526umid%253D7534ffb8%2de466%2d4e12%2da569%2d231f9b03e0e1%2526auth%253D32813f2e647ebb91b39d0b35ac97db1efa82dd64%2d097b8edbb06a5ebfbc12c8981b429ff594e539d1%26data%3d05%257C01%257Cgeorgekingsley.paulsundararaj%2540ncs.com.sg%257Cc6e89c2ed32e4d21c91208db1f9bf30a%257Cca90d8f589634b6ebca99ac468bcc7a8%257C1%257C0%257C638138526885301089%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%257C%257C%257C%26sdata%3dEmVZCmiW9o0%252FLqF7AmsAZOQoAWcm1JDQusNWxScP3t0%253D%26reserved%3d0&umid=48f669ec-c0e9-4e2c-b663-a06eb2569ec1&auth=32813f2e647ebb91b39d0b35ac97db1efa82dd64-563a432c0d33496048faedcfe67aae8255142649>;
You can also find the known fixed releases for this bug from the known fixed releases box, and the only way to mitigate this bug will be by upgrading the device to known fixed release.
The crash is happening after DNAC makes some interface changes and pushes to the switch's configuration. | Cisco Switch rebooted | C9300-48U-A | 16.12.4 | 16.12.4 | 73.0 | 3 | 100.0 | Software Bug | C9300 | LAN Switching | Cat9300 | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | Cat9300 | LAN Switching | 01t15000005W0LTAA0 | SHERLOCK: PARTIAL |
695503784 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Router and IOS-XE Architecture
Subtechnology: IOS-XEISSU Upgrade
Problem Code: Install, uninstall, or Upgrade
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: TAC Support for SDA Fabric Border Nodes upgrade from 16.12.1s to 17.6.4
Issue SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT)
TAC Support for SDA Fabric Border Nodes upgrade from 16.12.1s to 17.6.4
Issue SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT)
CSCwf44649 - Customer was hitting the following bug - after multiple MW we were able to get them past the issue and successfully update their fabric | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Router and IOS-XE Architecture
Subtechnology: IOS-XEISSU Upgrade
Problem Code: Install, uninstall, or Upgrade
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: TAC Support for SDA Fabric Border Nodes upgrade from 16.12.1s to 17.6.4
Issue SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT)
TAC Support for SDA Fabric Border Nodes upgrade from 16.12.1s to 17.6.4
Issue SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT)
CSCwf44649 - Customer was hitting the following bug - after multiple MW we were able to get them past the issue and successfully update their fabric | Technology: Router and IOS-XE Architecture
Subtechnology: IOS-XEISSU Upgrade
Problem Code: Install, uninstall, or Upgrade
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: TAC Support for SDA Fabric Border Nodes upgrade from 16.12.1s to 17.6.4
Issue SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT) | TAC Support for SDA Fabric Border Nodes upgrade from 16.12.1s to 17.6.4
Issue SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT) | CSCwf44649 - Customer was hitting the following bug - after multiple MW we were able to get them past the issue and successfully update their fabric | Customer requires TAC Support to complete a software upgrade for SDA Fabric Border Nodes from 16.12.1s > 17.6.4.
Issue is similar to SRs: 692159335, 693041357, 693101485
Change start time: 13-May-2023 19:00 SGT (07:00 PM SGT) | ASR1009-X | 17.6.4 | 17.6.4 | 37.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | ASR1000 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | 01t6R000006k8PsQAI | Install, uninstall, or Upgrade | Cisco Software-Defined Access (SDA Wired) | Cisco DNA Center - On-Prem | 01t15000004dDisAAE | SHERLOCK: PARTIAL;CaseClosureFieldAutomation: Partial |
694745866 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE - Specific VLAN Anycast Gateway not reachable for connected endpoints
Device-tracking pointing to wrong MAC address and Tunnel Interface
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
1071 0000.0c9f.f48e CP_LEARN Tu0
SDA FE - Specific VLAN Anycast Gateway not reachable for connected endpoints
Device-tracking pointing to wrong MAC address and Tunnel Interface
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
1071 0000.0c9f.f48e CP_LEARN Tu0
1. CSCvq05985 Since we are seeing DT pointing to Tunnel0 or any random interface
Workaround –
a. Clear device-tracking database mac <>
b. Device-tracking database binding vlan <vlan no > <svi ip> interface vlan <vlan no> <mac>
Or
c. Upgrade to fixed release.
2. CSCvm86310 Since there were some DT entries pointing to 0000.0000.00fd mac
Unfortunately there is no workaround for this. I checked for customer cases where this issue was hit and the clearing device-tracking/ resetting the SVI resolved the issue. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE - Specific VLAN Anycast Gateway not reachable for connected endpoints
Device-tracking pointing to wrong MAC address and Tunnel Interface
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
1071 0000.0c9f.f48e CP_LEARN Tu0
SDA FE - Specific VLAN Anycast Gateway not reachable for connected endpoints
Device-tracking pointing to wrong MAC address and Tunnel Interface
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
1071 0000.0c9f.f48e CP_LEARN Tu0
1. CSCvq05985 Since we are seeing DT pointing to Tunnel0 or any random interface
Workaround –
a. Clear device-tracking database mac <>
b. Device-tracking database binding vlan <vlan no > <svi ip> interface vlan <vlan no> <mac>
Or
c. Upgrade to fixed release.
2. CSCvm86310 Since there were some DT entries pointing to 0000.0000.00fd mac
Unfortunately there is no workaround for this. I checked for customer cases where this issue was hit and the clearing device-tracking/ resetting the SVI resolved the issue. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE - Specific VLAN Anycast Gateway not reachable for connected endpoints
Device-tracking pointing to wrong MAC address and Tunnel Interface
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
1071 0000.0c9f.f48e CP_LEARN Tu0 | SDA FE - Specific VLAN Anycast Gateway not reachable for connected endpoints
Device-tracking pointing to wrong MAC address and Tunnel Interface
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
1071 0000.0c9f.f48e CP_LEARN Tu0 | 1. CSCvq05985 Since we are seeing DT pointing to Tunnel0 or any random interface
Workaround –
a. Clear device-tracking database mac <>
b. Device-tracking database binding vlan <vlan no > <svi ip> interface vlan <vlan no> <mac>
Or
c. Upgrade to fixed release.
2. CSCvm86310 Since there were some DT entries pointing to 0000.0000.00fd mac
Unfortunately there is no workaround for this. I checked for customer cases where this issue was hit and the clearing device-tracking/ resetting the SVI resolved the issue. | - Endpoints are not able to reach specific VLAN gateway.
- Customer observes that device tracking database entry for this gateway is pointing incorrectly to an unrelated interface.
```
H20-01-CNT-ES1#sh device-tracking data address 172.27.64.1
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
ARP 172.27.64.1 bce7.122d.408a Tu0 1071 0005 102s REACHABLE 143 s
H20-01-CNT-ES1#show ip arp vrf admin_VN vlan 1071
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.27.64.1 - 0000.0c9f.f48e ARPA Vlan1071
``` | C9300-48U-A | 16.12.4 | 16.12.4 | 77.0 | 3 | 100.0 | Software Bug | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | Cisco Software-Defined Access (SDA Wired) | Cisco DNA Center - On-Prem | 01t15000005W0LTAA0 | nan |
694540632 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down.
We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down.
+++ As per logs. I don’t see any error related to behaviour we observed on the switch .
+++ Ideally such behaviour could have been result of memory leak, switch getting stuck in state, hardware programming error , or any unknown bugs.
+++ Since we had reloaded without collecting logs which needed to pin point such cases , we will not be able to proceed further .
+++ My best suggestion here would be to upgrade the Switch to latest stable code so that we can avoid any old known issue on 16.12.3.
Below is latest Stable Cisco Suggested code for this Switch ,
https://software.cisco.com/download/home/286314027/type/282046477/release/Bengaluru-17.6.4 | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down.
We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down.
+++ As per logs. I don’t see any error related to behaviour we observed on the switch .
+++ Ideally such behaviour could have been result of memory leak, switch getting stuck in state, hardware programming error , or any unknown bugs.
+++ Since we had reloaded without collecting logs which needed to pin point such cases , we will not be able to proceed further .
+++ My best suggestion here would be to upgrade the Switch to latest stable code so that we can avoid any old known issue on 16.12.3.
Below is latest Stable Cisco Suggested code for this Switch ,
https://software.cisco.com/download/home/286314027/type/282046477/release/Bengaluru-17.6.4 | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down. | We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down. | +++ As per logs. I don’t see any error related to behaviour we observed on the switch .
+++ Ideally such behaviour could have been result of memory leak, switch getting stuck in state, hardware programming error , or any unknown bugs.
+++ Since we had reloaded without collecting logs which needed to pin point such cases , we will not be able to proceed further .
+++ My best suggestion here would be to upgrade the Switch to latest stable code so that we can avoid any old known issue on 16.12.3.
Below is latest Stable Cisco Suggested code for this Switch ,
https://software.cisco.com/download/home/286314027/type/282046477/release/Bengaluru-17.6.4 | We found UP link is UP but switch was unreachable. OSPF was down. uplink ports shows green light. service also get down. | C9300-48U-A | 16.12.3s | 16.12.3s | 79.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | C9300 | LAN Switching | Cat9300 | 01t1C000004GjbyQAC | Error Messages, Logs, Debugs | Cat9300 | LAN Switching | 01t15000005W0LTAA0 | nan |
694515784 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - AP disconnected from WLC alert on DNAC
SDA - AP disconnected from WLC alert on DNAC
Customer gaev confirmation on the closure | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - AP disconnected from WLC alert on DNAC
SDA - AP disconnected from WLC alert on DNAC
Customer gaev confirmation on the closure | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA - AP disconnected from WLC alert on DNAC | SDA - AP disconnected from WLC alert on DNAC | Customer gaev confirmation on the closure | SDA - AP disconnected from WLC alert on DNAC | AIR-CT8540-K9 | 17.3.5b | 17.3.5b | 53.0 | 3 | 100.0 | Interoperability/Compatibility (Cisco to Cisco or Cisco to 3rd Party) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t6R000006k5BEQAY | Error Messages, Logs, Debugs | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t15000004n996AAA | SHERLOCK: PARTIAL |
694180958 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Switch CPU high and ospf neighbor flapping and neighbor frequently down.
Switch CPU high and ospf neighbor flapping and neighbor frequently down.
W have seen high cpu and ospf flapp
We suggested cli. To get top cpu results
Sw(config)# process cpu threshold type total rising 70 interval 5 falling 50 interval 5
After monitoring we see that the device is stable | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Switch CPU high and ospf neighbor flapping and neighbor frequently down.
Switch CPU high and ospf neighbor flapping and neighbor frequently down.
W have seen high cpu and ospf flapp
We suggested cli. To get top cpu results
Sw(config)# process cpu threshold type total rising 70 interval 5 falling 50 interval 5
After monitoring we see that the device is stable | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Switch CPU high and ospf neighbor flapping and neighbor frequently down. | Switch CPU high and ospf neighbor flapping and neighbor frequently down. | W have seen high cpu and ospf flapp
We suggested cli. To get top cpu results
Sw(config)# process cpu threshold type total rising 70 interval 5 falling 50 interval 5
After monitoring we see that the device is stable | ospf flapp | C9300-48U-A | 16.12.4 | 16.12.4 | 73.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | C9300 | LAN Switching | Cat9300 | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | Cat9300 | LAN Switching | 01t15000005W0LTAA0 | IRE: PARTIAL |
695940399 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 8.4.2/ 8.2.3/ 7.3.5/ 9.3.9/ 7.3.7 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Data Center and Storage Networking
Subtechnology: Nexus 7000 Series Switch - Interface, Port Channel (inc. VPC), Trunk, VLAN, Spanning Tree
Problem Code: Configuration Assistance
Product: NA
Product Family: N7000
Software Version: N/A
Router/Node Name: N/A
Problem Details: User requires support to establish an uplink between core switches, both of which are running VTP Mode Servers.
User requires support to establish an uplink between core switches, both of which are running VTP Mode Servers.
proceeding with closer with customer consent | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: N77-C7710/ N77-SUP2E Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Data Center and Storage Networking
Subtechnology: Nexus 7000 Series Switch - Interface, Port Channel (inc. VPC), Trunk, VLAN, Spanning Tree
Problem Code: Configuration Assistance
Product: NA
Product Family: N7000
Software Version: N/A
Router/Node Name: N/A
Problem Details: User requires support to establish an uplink between core switches, both of which are running VTP Mode Servers.
User requires support to establish an uplink between core switches, both of which are running VTP Mode Servers.
proceeding with closer with customer consent | Technology: Data Center and Storage Networking
Subtechnology: Nexus 7000 Series Switch - Interface, Port Channel (inc. VPC), Trunk, VLAN, Spanning Tree
Problem Code: Configuration Assistance
Product: NA
Product Family: N7000
Software Version: N/A
Router/Node Name: N/A
Problem Details: User requires support to establish an uplink between core switches, both of which are running VTP Mode Servers. | User requires support to establish an uplink between core switches, both of which are running VTP Mode Servers. | proceeding with closer with customer consent | Hardware:
N77-C7710
Symptoms:
new config spanning tree issue impact check | N77-C7710 | 9.3(9)EFT | 9.3(9)EFT | 81.0 | 3 | 100.0 | Documentation/Tools (incomplete, too complex...) | N7000 | Data Center and Storage Networking | Nexus 7000 Series Switch - Interface, Port Channel (inc. VPC), Trunk, VLAN, Spanning Tree | 01t6R000007By8nQAC | Error Messages, Logs, Debugs | Nexus 7000 Series Switch - Interface, Port Channel (inc. VPC), Trunk, VLAN, Spanning Tree | Data Center and Storage Networking | 01tA0000002q8pGIAQ | SHERLOCK: PARTIAL |
695571422 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 15.5.1/ 155.1/ THIRD_PARTY_PRODUCT_SW/ 152.1/ 151.2/ 155.1/ NA - RMA/ 15.5.1 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat6500/6800 (Supervisor 2T) VSS
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C6800MD
Software Version: N/A
Router/Node Name: N/A
Problem Details: We need assistance to fix this issue.
We need assistance to fix this issue.
As per my understanding post switch reload supervisors have been replaced and the IOS version running on the switch is 15.5(1)SY1 is old one.
Due to fewer logs outputs, it will not be possible to provide a pinpoint issue and as you are running an old IOS version,
it could be affected by several defects. It is recommended to upgrade the IOS version to the suggested one. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C6807-XL/ C6800-32P10G-XL/ C6800-SUP6T/ C6800-SUP6T-XL/ C6800-SUP6T-XL=/ C6807-DNA-A Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat6500/6800 (Supervisor 2T) VSS
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C6800MD
Software Version: N/A
Router/Node Name: N/A
Problem Details: We need assistance to fix this issue.
We need assistance to fix this issue.
As per my understanding post switch reload supervisors have been replaced and the IOS version running on the switch is 15.5(1)SY1 is old one.
Due to fewer logs outputs, it will not be possible to provide a pinpoint issue and as you are running an old IOS version,
it could be affected by several defects. It is recommended to upgrade the IOS version to the suggested one. | Technology: LAN Switching
Subtechnology: Cat6500/6800 (Supervisor 2T) VSS
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C6800MD
Software Version: N/A
Router/Node Name: N/A
Problem Details: We need assistance to fix this issue. | We need assistance to fix this issue. | As per my understanding post switch reload supervisors have been replaced and the IOS version running on the switch is 15.5(1)SY1 is old one.
Due to fewer logs outputs, it will not be possible to provide a pinpoint issue and as you are running an old IOS version,
it could be affected by several defects. It is recommended to upgrade the IOS version to the suggested one. | Urgent - C6800-SUP6T-XL Link Down | C6800-SUP6T-XL | 15.5(1)SY1 | 15.5(1)SY1 | 61.0 | 3 | 100.0 | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | C6800MD | LAN Switching | Cat6800 (Supervisor 6T) VSS | 01t15000005WPxkAAG | Configuration Assistance | Cat6800 (Supervisor 6T) VSS | LAN Switching | 01t15000004dPUOAA2 | nan |
695816345 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Hi NCS and Baby Team,
Thank you for your time on call.
As per you request, we are keeping this case under S2 for now.
Please find the summary of the call and the next action below:
Issue Reported: The standby controller gone to “Maintenance” Mode.
Summary:
Observed that the standby controller is on Maintenance mode (CT8540 - 8.10.183.0)
Analysed the logs and found that the standby controller sync failed and timeout for the XML config and result in the Cert Failed aswell as below
Reset reason : Certificate transfer from Active to Standby failed ,(Version: 8.10.183.0)
Reset time : Mon Jul 10 09:28:41 2023
Trace back : 0x8f9abc 0x1e2f80a 0x1eb54d4 0x1eaacf4 0x1eaa4a6 0x1ea0413 0x1e38647 0x7dff 0xe898d
Jul 10 15:40:16.800 :Previous State: RED_XML_TRANSFER_FAILED_STATE, Event:RED_XML_TRANSFER_MASTER_TMOUT_SM_EVENT
Jul 10 15:40:16.800 :Current State RED_XML_TRANSFER_DONE_STATE
Jul 10 15:40:16.800 :----------------------------------------------------------------
*rmgrMain: Jul 10 15:40:16.828: Send Role Negotiation payload to peer
Role Negotiation timeout.
Didn't find Peer..
The above logs indicates, the issue could be from the Redundant Port connection between Active and Standby so the result in XML file sync up failed and Master timeout.
As per the information on call, the Redundant Port is not back to back connection and the connection on through distributed switches.
As per the recommendation from Cisco , the RP connection needs to be connected directly between two controllers as a permanent solution.
Please Refer > https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-7/High_Availability_DG.html#pgfId-91515
As you have provided the bug CSCvq95397, it is also related to RP connection issue and it was on Unreproduceable state due to the RP connection is not back to back.
Next Plan of Action:
For time being, if the RP connection is coming UP and there is a proper RP communication, Please try the following action
Please bring down the RP port before doing the below action;
1.
Need to bring down the RP Port
2.
Make the reachability to mgmt IP address for Standby controller (Unique IP)
3.
Disable the port connection and HA SSO
4.
Reload the standby controller
5.
Bring UP the standby as standalone controller.
6.
Reconfigure the HA SSO with RP interface UP.
7.
If the above steps are failed, Please change the switch port of RP connection.
8.
Permanent solution to connect RP back to Back.
Please refer the below document for configuration and scenario;
https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/8540-WLC-DG/b_Cisco-8540-WLC-deployment-guide.html#concept_C0A18A765999461BA204F8BEF444D71E
+ @Muhammad Hilmi Bin Zainal<mailto:[email protected]>
We would like to reschedule the call to 9pm SGT tomorrow as requested by customer.
Here are some additional details:
* Are we able to take console access to the standby controller? yes
* Is there any service impact during the time of you have observed the issue? No as 1 wlc is still running
* May I know what is the software version running on the controllers? 8.10.183
* May I know total number of APs working on the active? 4600
* I hope now the standby controller is on standalone mode, can we take the console to the controller and take the below output? Yes
* May I know what is the LED light status of the standby chassis? All green
1.
We console and notice wlc is in maintenance mode and config looks ok
2.
We reboot and this message keep prompting “[PM] RP KA bitmap=0000, RMI KA bitmap=FFFF, GW KA bitmap=FFFF” and we cant ping the management ip and the redundancy didn’t came up.
3.
The we tried remove all cables and reboot the wlc.
Now its in active and standalone.
Ps – attached is the show tech before we reboot the wlc and logs after we reboot
May I check with you is there any additional logs needed before the troubleshooting session?
Kindly wait for response from TAC.
Hi Yokeswaran and Png Ting,
As per customer, we shall proceed tomorrow 9pm SGT.
Before that, what are the logs you need before we start the call tomorrow?
Are we able to take console access to the standby controller?
yes
Is there any service impact during the time of you have observed the issue?
No as 1 wlc is still running
May I know what is the software version running on the controllers?
8.10.183
May I know total number of APs working on the active?
4600
I hope now the standby controller is on standalone mode, can we take the console to the controller and take the below output? yes
May I know what is the LED light status of the standby chassis?
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Model No.: AIR-CT8540-K9
SN: FCH2324V04H
standby controller got disconnected and we discover that it went to maintenance mode
Tried restart the WLC and the redundancy is still not establish After restart,WLC is up and in active state.
Model No.: AIR-CT8540-K9
SN: FCH2324V04H
standby controller got disconnected and we discover that it went to maintenance mode
Tried restart the WLC and the redundancy is still not establish After restart,WLC is up and in active state.
timestamp : 2023-07-23T19:30:49.000+0000 || updatedby : mepalaci || type : RESOLUTION SUMMARY || visibility : External || details : Requested to change the SFP and RJ45 to Fiber connector between the Switch and Primary controller (TLDC) _ its looks like L1 issue between two controllers on RP connection.
2 Brand new cables have been use to replace previous cables on switch
After change on cables and make port channel up, connection to HA SSO form correctly with no issues. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Model No.: AIR-CT8540-K9
SN: FCH2324V04H
standby controller got disconnected and we discover that it went to maintenance mode
Tried restart the WLC and the redundancy is still not establish After restart,WLC is up and in active state.
Model No.: AIR-CT8540-K9
SN: FCH2324V04H
standby controller got disconnected and we discover that it went to maintenance mode
Tried restart the WLC and the redundancy is still not establish After restart,WLC is up and in active state.
timestamp : 2023-07-23T19:30:49.000+0000 || updatedby : mepalaci || type : RESOLUTION SUMMARY || visibility : External || details : Requested to change the SFP and RJ45 to Fiber connector between the Switch and Primary controller (TLDC) _ its looks like L1 issue between two controllers on RP connection.
2 Brand new cables have been use to replace previous cables on switch
After change on cables and make port channel up, connection to HA SSO form correctly with no issues. | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: Model No.: AIR-CT8540-K9
SN: FCH2324V04H
standby controller got disconnected and we discover that it went to maintenance mode
Tried restart the WLC and the redundancy is still not establish After restart,WLC is up and in active state. | Model No.: AIR-CT8540-K9
SN: FCH2324V04H
standby controller got disconnected and we discover that it went to maintenance mode
Tried restart the WLC and the redundancy is still not establish After restart,WLC is up and in active state. | timestamp : 2023-07-23T19:30:49.000+0000 || updatedby : mepalaci || type : RESOLUTION SUMMARY || visibility : External || details : Requested to change the SFP and RJ45 to Fiber connector between the Switch and Primary controller (TLDC) _ its looks like L1 issue between two controllers on RP connection.
2 Brand new cables have been use to replace previous cables on switch
After change on cables and make port channel up, connection to HA SSO form correctly with no issues. | nan | AIR-CT8540-K9 | crete-single_8-10-183-0.img | nan | nan | 3 | nan | Configuration Assistance (process not intuitive, too complex, inconsistent...) | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | nan | nan | nan | nan | nan | nan |
695077555 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 17.03.04a/ 17.3.4a Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed w/o Customer Confirm
++ Regarding the punt inject drops:
Feb 8 2023 05:57:56.583 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:090 TS:00031241039764900733 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/0 src ip: 172.18.1.98
Feb 8 2023 06:02:01.780 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:030 TS:00031241284970959902 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.134
show platform software punt-policer drop-only
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1. To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.currently process that is causing more CPU utilisation is BGP router but not sure when its 90% need to take a capture when its 90 percent.
LDC-CN-RTR01#sh processes cpu sorted
CPU utilization for five seconds: 66%/1%; one minute: 65%; five minutes: 64%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
722 2491375244 645632249 3858 54.43% 50.97% 50.59% 0 BGP Router
396 1358881623 1928116369 704 6.00% 7.08% 6.99% 0 LISP control
134 490160586 3276638596 0 2.56% 2.39% 2.40% 0 IOSXE-RP Punt Se
333 127630648 370024659 344 1.20% 1.34% 1.38% 0 IP RIB Update
228 5908 5801 1018 0.15% 1.07% 0.66% 2 SSH Process
306 15299251 276586916 55 0.15% 0.09% 0.08% 0 TCP Timer
152 22577584 3548004 6363 0.15% 0.07% 0.05% 0 Compute load av
BGP router process, Calculates the best BGP path and processes any route churn. It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
To get more details we need to enable debugs on the router.
Increase Interface Input Queues
If BGP advertises thousands of routes to many peers, TCP must transmit thousands of packets in a short duration. The BGP peers receive these packets and send TCP acknowledgements to the BGP speaker that advertises, which causes the BGP speaker to receive a flood of TCP ACKs in a short period of time. If the ACKs arrive at a rate that is too high for the route processor, packets back up in inbound interface queues. By default, router interfaces use an input queue size of 75 packets. In addition, special control packets such as BGP UPDATES use a special queue with Selective Packet Discard (SPD). This special queue holds 100 packets. When BGP convergence, happens TCP ACKs can fill quickly the 175 spots of input buffering and the new packets that arrive must be dropped. On routers with 15 or more BGP peers and exchange of the full Internet routing table, over 10,000 drops per interface per minute can be seen. Here is example output from a router 15 minutes after reboot:
Router#show interface pos 8/0 | include input queue
Output queue 0/40, 0 drops; input queue 0/75, 278637 drops
Router#
If you increase the interface input queue depth (with the hold-queue in command) it helps reduce the number of dropped TCP ACKs, which reduces the amount of work BGP must do to converge. Normally, a value of 1000 resolves problems caused by input queue drops.
These are described in below doc and matches the issue we are seeing, there could be some peers which are advertising the routes in continuous interval.
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html
++ Suggest increasing input que to 1000
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Please capture the below logs when CPU is over 90% to check further.
Show process cpu sorted
show bgp neighbors
show bgp all summary | i table
show bgp vpnv4 unicast all neighbors
show bgp all summary
show platform software punt-policer drop-only
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show logging
Good day!
Iam proceeding for closure it is always a pleasure to help.
however, if you need anything in future, please don't hesitate to contact me.
My working hours and call back number are listed below.
Additionally, you may re-open the case within 14 days if you require further assistance on the same issue.
You can simply reply to this email and case will get re-open automatically.
Good day !
This a follow up- email since there was no furhter updates
I want to be in touch with you and understand if you have any further queries related to the case, please let me know if you have any, I will be happy to help.
If you have no further queries, please confirm If I could proceed for case closure.
Good day!
My name is Kala and I am manager for Routing/WAN team in APAC time zone.
This is regarding the SR: 695077555, owned by my engineer Jobin George.
I am writing this email to you as it seems, he hasn’t been able to establish successful communication with you.
I am not sure if this issue is resolved, please let us know, we will be glad to assist.
If you are currently busy with other engagements, you could opt to temporarily close this case and re-work with us, when you have appropriate time.
Looking forward to your response.
Thank you!
Assuring best service.
XX-MESSAGE-FROM-SHERLOCK---LOOPED-DATA-XX
XX-MESSAGE-FROM-SHERLOCK---LOOPED-DATA-XX
XX-MESSAGE-FROM-SHERLOCK---LOOPED-DATA-XX
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1.
To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.
In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.
Also increase the input que size of tengig 0/1/0 and 0/1/1 to 1000 and observe if there is any input que drops on the interface.
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
+++ customer to apply the change
++ call scheduled for 3pm SGT on 08/03 Wed
++ Logs needed when CPU spikes ( 90% )are observed. checking with end customer for enabling the bgp debugs to get more information on the BGP updates. We will also take platform and EPC captures for bgp packets during this window.
Aug 18 2022 04:18:49.487 UTC: %BGP-3-NOTIFICATION: sent to neighbor 172.18.0.131 4/0 (hold time expired) 0 bytes
Aug 18 2022 04:18:49.487 UTC: %BGP-5-NBR_RESET: Neighbor 172.18.0.131 reset (BGP Notification sent)
Aug 18 2022 04:18:49.511 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.131 Down BGP Notification sent
Aug 18 2022 04:18:49.511 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.131 VPNv4 Unicast topology base removed from session BGP Notification sent
Aug 18 2022 04:18:49.511 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.131 IPv4 Unicast topology base removed from session BGP Notification sent
Aug 18 2022 04:22:17.016 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.0 Thread:115 TS:00018015331484357227 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.133
Aug 18 2022 04:27:24.223 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.131 Up
BGP is flapping when CPU is spiking and there are also CPU PUNT drops. For further analysis please configure the below EEM script on the router to capture the logs at the time of CPU spike events.
LDC-CN-RTR01#sh processes cpu sorted
CPU utilization for five seconds: 66%/1%; one minute: 65%; five minutes: 64%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
722 2491375244 645632249 3858 54.43% 50.97% 50.59% 0 BGP Router
396 1358881623 1928116369 704 6.00% 7.08% 6.99% 0 LISP control
134 490160586 3276638596 0 2.56% 2.39% 2.40% 0 IOSXE-RP Punt Se
333 127630648 370024659 344 1.20% 1.34% 1.38% 0 IP RIB Update
228 5908 5801 1018 0.15% 1.07% 0.66% 2 SSH Process
306 15299251 276586916 55 0.15% 0.09% 0.08% 0 TCP Timer
152 22577584 3548004 6363 0.15% 0.07% 0.05% 0 Compute load av
BGP router process, Calculates the best BGP path and processes any route churn. It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
To get more details we need to enable debugs on the router.
Increase Interface Input Queues
If BGP advertises thousands of routes to many peers, TCP must transmit thousands of packets in a short duration. The BGP peers receive these packets and send TCP acknowledgements to the BGP speaker that advertises, which causes the BGP speaker to receive a flood of TCP ACKs in a short period of time. If the ACKs arrive at a rate that is too high for the route processor, packets back up in inbound interface queues. By default, router interfaces use an input queue size of 75 packets. In addition, special control packets such as BGP UPDATES use a special queue with Selective Packet Discard (SPD). This special queue holds 100 packets. When BGP convergence, happens TCP ACKs can fill quickly the 175 spots of input buffering and the new packets that arrive must be dropped. On routers with 15 or more BGP peers and exchange of the full Internet routing table, over 10,000 drops per interface per minute can be seen. Here is example output from a router 15 minutes after reboot:
Router#show interface pos 8/0 | include input queue
Output queue 0/40, 0 drops; input queue 0/75, 278637 drops
Router#
If you increase the interface input queue depth (with the hold-queue in command) it helps reduce the number of dropped TCP ACKs, which reduces the amount of work BGP must do to converge. Normally, a value of 1000 resolves problems caused by input queue drops.
These are described in below doc and matches the issue we are seeing, there could be some peers which are advertising the routes in continuous interval.
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html
++ Suggest increasing input que to 1000
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Please capture the below logs when CPU is over 90%
Show process cpu sorted
show bgp neighbors
show bgp all summary | i table
show bgp vpnv4 unicast all neighbors
show bgp all summary
show platform software punt-policer drop-only
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show logging
Thanks for your time on call today.
As discussed, the currently process that is causing more CPU utilisation is BGP router but not sure when its 90% need to take a capture when its 90 percent.
LDC-CN-RTR01#sh processes cpu sorted
CPU utilization for five seconds: 66%/1%; one minute: 65%; five minutes: 64%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
722 2491375244 645632249 3858 54.43% 50.97% 50.59% 0 BGP Router
396 1358881623 1928116369 704 6.00% 7.08% 6.99% 0 LISP control
134 490160586 3276638596 0 2.56% 2.39% 2.40% 0 IOSXE-RP Punt Se
333 127630648 370024659 344 1.20% 1.34% 1.38% 0 IP RIB Update
228 5908 5801 1018 0.15% 1.07% 0.66% 2 SSH Process
306 15299251 276586916 55 0.15% 0.09% 0.08% 0 TCP Timer
152 22577584 3548004 6363 0.15% 0.07% 0.05% 0 Compute load av
BGP router process, Calculates the best BGP path and processes any route churn.
It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
To get more details we need to enable debugs on the router.
Increase Interface Input Queues
If BGP advertises thousands of routes to many peers, TCP must transmit thousands of packets in a short duration.
The BGP peers receive these packets and send TCP acknowledgements to the BGP speaker that advertises, which causes the BGP speaker to receive a flood of TCP ACKs in a short period of time.
If the ACKs arrive at a rate that is too high for the route processor, packets back up in inbound interface queues.
By default, router interfaces use an input queue size of 75 packets.
In addition, special control packets such as BGP UPDATES use a special queue with Selective Packet Discard (SPD).
This special queue holds 100 packets.
When BGP convergence, happens TCP ACKs can fill quickly the 175 spots of input buffering and the new packets that arrive must be dropped.
On routers with 15 or more BGP peers and exchange of the full Internet routing table, over 10,000 drops per interface per minute can be seen.
Here is example output from a router 15 minutes after reboot:
Router#show interface pos 8/0 | include input queue
Output queue 0/40, 0 drops; input queue 0/75, 278637 drops
Router#
If you increase the interface input queue depth (with the hold-queue in command) it helps reduce the number of dropped TCP ACKs, which reduces the amount of work BGP must do to converge.
Normally, a value of 1000 resolves problems caused by input queue drops.
These are described in below doc and matches the issue we are seeing, there could be some peers which are advertising the routes in continuous interval.
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html
++ Suggest increasing input que to 1000
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Please capture the below logs when CPU is over 90%
Show process cpu sorted
show bgp neighbors
show bgp all summary | i table
show bgp vpnv4 unicast all neighbors
show bgp all summary
show platform software punt-policer drop-only
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show logging
Please capture and attach the above logs when CPU spikes ( 90% )are observed.
Meanwhile please check with end customer for enabling the bgp debugs to get more information on the BGP updates.
We will also take platform and EPC captures for bgp packets during this window.
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36 Edg/110.0.1587.63
File Name: 172.18.0.129_08032023_1526.log
File Type: log_values
File Description: Session Logs
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=640842d74fd96f04ac51d777
File Upload Date / Time: Wed Mar 08 2023 16:09:59 GMT+0800 (Singapore Standard Time) - COMPLETED
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36 Edg/110.0.1587.63
File Name: 172.18.0.129_08032023_1506.log
File Type: log_values
File Description: Session Logs
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=640842c92063184ac91a1360
File Upload Date / Time: Wed Mar 08 2023 16:09:46 GMT+0800 (Singapore Standard Time) - COMPLETED
File Name: 172.18.0.130_08032023_1506.log
File Type: log_values
File Description: Session Logs
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=640842ce4fd96f04ac51d75d
File Upload Date / Time: Wed Mar 08 2023 16:09:50 GMT+0800 (Singapore Standard Time) - COMPLETED
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1.
To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.
In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.
Also increase the input que size of tengig 0/1/0 and 0/1/1 to 1000 and observe if there is any input que drops on the interface.
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
+++ customer to apply the change
++ call scheduled for 3pm SGT on 08/03 Wed
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1.
To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.
In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.
Also increase the input que size of tengig 0/1/0 and 0/1/1 to 1000 and observe if there is any input que drops on the interface.
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
+++ customer to apply the change
++ call scheduled for 3pm SGT on 07/03
Please use the below webex link for the same.
https://cisco.webex.com/ciscosales/j.php?MTID=m873ae5931a775d47f4d08e29ce0f8235
Please share us webex link ....
Good day!
Thanks for the update, I will be available for webex session 3pm Tomorrow.
Can we have a Webex call tomorrow 3PM SGT time ??
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1.
To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.
In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.
Also increase the input que size of tengig 0/1/0 and 0/1/1 to 1000 and observe if there is any input que drops on the interface.
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
+++ customer to apply the changes.
Good day!!
I want to be in touch with you and understand if you have applied the suggested config changes on the router.
Please share an update to proceed further once you are available.
Let me check with customer and let you know asap.
Good day!
There is no impact.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
->this will generate logs on the router when the CPU rises to 90 and with the top process.
Increase the input buffer que size on both tengig 0/1/0 and 0/1/1 interfaces to reduce the input que drops.
interface tenGigabitEthernet 0/1/0
hold-queue 1000 in
Please share me the below outputs after adding the above commands once the CPU spike is observed.
Clear logging, clear counters tengig 0/1/0, clear counters tengig 0/11
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show platform software punt-policer drop-only
show process cpu sorted
show process cpu history
Show logging.
Is there any impact for below config?
2.
In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.
Also increase the input que size of tengig 0/1/0 and 0/1/1 to 1000 and observe if there is any input que drops on the interface.
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1.
To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.
In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.
Also increase the input que size of tengig 0/1/0 and 0/1/1 to 1000 and observe if there is any input que drops on the interface.
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Good day!
The last logs for punt policer drops were on Feb 8th that is when the BGP has also flapped.
erver hostname/domain name
Feb 7 2023 17:12:09.768 UTC: %SMART_LIC-3-COMM_FAILED: Communications failure with the Cisco Smart License Utility (CSLU) : Unable to resolve server hostname/domain name
Feb 8 2023 05:49:29.574 UTC: %BGP-3-NOTIFICATION: sent to neighbor 172.18.0.133 4/0 (hold time expired) 0 bytes
Feb 8 2023 05:49:43.674 UTC: %BGP-5-NBR_RESET: Neighbor 172.18.0.133 reset (BGP Notification sent)
Feb 8 2023 05:49:43.705 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.133 Down BGP Notification sent
Feb 8 2023 05:49:43.705 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.133 VPNv4 Unicast topology base removed from session BGP Notification sent
Feb 8 2023 05:49:43.705 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.133 IPv4 Unicast topology base removed from session BGP Notification sent
Feb 8 2023 05:53:41.872 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.0 Thread:161 TS:00031240785043225194 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/0 src ip: 172.18.0.131
Feb 8 2023 05:57:50.740 UTC: %BGP-5-NBR_RESET: Neighbor 172.18.0.133 active reset (BGP Notification sent)
Feb 8 2023 05:57:50.740 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.133 Up
Feb 8 2023 05:57:56.583 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:090 TS:00031241039764900733 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/0 src ip: 172.18.1.98
Feb 8 2023 06:02:01.780 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:030 TS:00031241284970959902 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.134
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1.
To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic.
When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed.
Currently the high priority traffic threshold is 5000
Good day!
Thanks for the shared logs, I am working on it will be updating you on my findings.
We have uploaded the required logs.
Regarding the 172.18.0.133 this is a Border Node had BGP peer with this Control Node.
User: 00u547cgp4nzef79z5d7
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
File Name: TLDC-CN-RTR01-23-feb-2023-TAC-Log.log
File Type: web_uploaded
File Description:
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=63f6ff30857e5c4ff6d78a9e
File Upload Date / Time: Thu Feb 23 2023 13:52:58 GMT+0800 (Singapore Standard Time) - COMPLETED
configure the below EEM script on the router to capture the logs at the time of CPU spike events.
event manager applet ASR_High_CPU authorization bypass
event snmp oid 1.3.6.1.4.1.9.2.1.56 get-type next entry-op ge entry-val "85" exit-time 30 poll-interval 1
action 1.0 syslog msg "High cpu detected. Please check bootflash:cpuinfo.txt"
action 2.0 cli command "enable"
action 3.0 cli command "term exec prompt timestamp"
action 4.0 cli command "show processes cpu sorted | append bootflash:cpuinfo.txt"
action 5.0 cli command "show process memory sorted | append bootflash:cpuinfo.txt"
action 5.4 cli command "show bgp all sum | append bootflash:cpuinfo.txt"
action 6.0 cli command "show platform hardware qfp active statistics drop | append bootflash:cpuinfo.txt"
action 7.1 cli command "show platform software punt-policer drop-only | append bootflash:cpuinfo.txt"
action 7.2 cli command "show platform hardware qfp active datapath utilization | append bootflash:cpuinfo.txt"
action 7.3 cli command "show process cpu hist | append bootflash:cpuinfo.txt"
action 7.7 cli command "show logging | append bootflash:cpuinfo.txt"
action 8.0 cli command "end"
++ Customer has not applied the EEM script
++ Aksed customer for more logs
Please share me the below logs from the router to check further
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show platform software punt-policer drop-only
show platform hardware qfp active interface if-name ten 0/1/0 statistics
show platform hardware qfp active interface if-name ten 0/1/1 statistics
show interfaces tenGigabitEthernet 0/1/0 accounting
show interfaces tenGigabitEthernet 0/1/1 accounting
show interfaces TenGigabitEthernet 0/1/0 stats
show interfaces TenGigabitEthernet 0/1/1 stats
show ip arp tenGigabitEthernet 0/1/0
show ip arp tenGigabitEthernet 0/1/1
show process cpu history
show logging
Good day!!
I have gone through the logs,I need more logs to further proceed on this case.
packets are getting dropped due to buffer que id full as there are more packets received at the interface level.
TenGigabitEthernet0/1/0 is up, line protocol is up
Hardware is BUILT-IN-EPA-8x10G, address is dc8c.3793.c910 (bia dc8c.3793.c910)
Internet address is 172.18.12.65/30
MTU 9212 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Input queue: 0/375/14668/0 (size/max/drops/flushes); Total output drops: 0 >> input que drops
Queueing strategy: fifo
TenGigabitEthernet0/1/1 is up, line protocol is up
Hardware is BUILT-IN-EPA-8x10G, address is dc8c.3793.c911 (bia dc8c.3793.c911)
Input queue: 0/375/10951/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
also please turn of any debugging you are current running on this router to capture more logs
>>show debugging , undebug all
Please share me the below logs from the router to check further
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show platform software punt-policer drop-only
show platform hardware qfp active interface if-name ten 0/1/0 statistics
show platform hardware qfp active interface if-name ten 0/1/1 statistics
show interfaces tenGigabitEthernet 0/1/0 accounting
show interfaces tenGigabitEthernet 0/1/1 accounting
show interfaces TenGigabitEthernet 0/1/0 stats
show interfaces TenGigabitEthernet 0/1/1 stats
show ip arp tenGigabitEthernet 0/1/0
show ip arp tenGigabitEthernet 0/1/1
show process cpu history
show logging
In addition please let me know which devices are connected to ten gig 0/1/0 and 0/1/1 and details on src ip: 172.18.0.133 which is attached to TenGigabitEthernet0/1/1.
We have uploaded the logs that we collected when CPU was high.
Hope you will get all your required output.
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
File Name: 172.18.0.130_14022023_1457.log
File Type: show_tech
File Description:
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=63f595e7b39e646169f216f6
File Upload Date / Time: Wed Feb 22 2023 12:12:21 GMT+0800 (Singapore Standard Time) - COMPLETED
File Name: 172.18.0.129_14022023_1456.log
File Type: show_tech
File Description:
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=63f595ebc029371c310e914c
File Upload Date / Time: Wed Feb 22 2023 12:12:28 GMT+0800 (Singapore Standard Time) - COMPLETED
My Colleague "George Kingsley" will share you the logs, we had collected those in the incident time.
To configure EEM script we need customer permission and set a schedule to configure.
As we had the logs that we collected on incident time so hope that will serve your requirements.
configure the below EEM script on the router to capture the logs at the time of CPU spike events.
event manager applet ASR_High_CPU authorization bypass
event snmp oid 1.3.6.1.4.1.9.2.1.56 get-type next entry-op ge entry-val "85" exit-time 30 poll-interval 1
action 1.0 syslog msg "High cpu detected. Please check bootflash:cpuinfo.txt"
action 2.0 cli command "enable"
action 3.0 cli command "term exec prompt timestamp"
action 4.0 cli command "show processes cpu sorted | append bootflash:cpuinfo.txt"
action 5.0 cli command "show process memory sorted | append bootflash:cpuinfo.txt"
action 5.4 cli command "show bgp all sum | append bootflash:cpuinfo.txt"
action 6.0 cli command "show platform hardware qfp active statistics drop | append bootflash:cpuinfo.txt"
action 7.1 cli command "show platform software punt-policer drop-only | append bootflash:cpuinfo.txt"
action 7.2 cli command "show platform hardware qfp active datapath utilization | append bootflash:cpuinfo.txt"
action 7.3 cli command "show process cpu hist | append bootflash:cpuinfo.txt"
action 7.7 cli command "show logging | append bootflash:cpuinfo.txt"
action 8.0 cli command "end"
++ CPU Logs pending from customer
Good day! , Thanks please share me the logs cpuinfo.txt which will be added to bootflash for further analysis.
Please help to share the incident time logs.
We had collected the logs when incident was happened, George will share the log.
Hope that will be helpful for you to check the root cause.
configure the below EEM script on the router to capture the logs at the time of CPU spike events.
event manager applet ASR_High_CPU authorization bypass
event snmp oid 1.3.6.1.4.1.9.2.1.56 get-type next entry-op ge entry-val "85" exit-time 30 poll-interval 1
action 1.0 syslog msg "High cpu detected. Please check bootflash:cpuinfo.txt"
action 2.0 cli command "enable"
action 3.0 cli command "term exec prompt timestamp"
action 4.0 cli command "show processes cpu sorted | append bootflash:cpuinfo.txt"
action 5.0 cli command "show process memory sorted | append bootflash:cpuinfo.txt"
action 5.4 cli command "show bgp all sum | append bootflash:cpuinfo.txt"
action 6.0 cli command "show platform hardware qfp active statistics drop | append bootflash:cpuinfo.txt"
action 7.1 cli command "show platform software punt-policer drop-only | append bootflash:cpuinfo.txt"
action 7.2 cli command "show platform hardware qfp active datapath utilization | append bootflash:cpuinfo.txt"
action 7.3 cli command "show process cpu hist | append bootflash:cpuinfo.txt"
action 7.7 cli command "show logging | append bootflash:cpuinfo.txt"
action 8.0 cli command "end"
Aug 18 2022 04:18:49.487 UTC: %BGP-3-NOTIFICATION: sent to neighbor 172.18.0.131 4/0 (hold time expired) 0 bytes
Aug 18 2022 04:18:49.487 UTC: %BGP-5-NBR_RESET: Neighbor 172.18.0.131 reset (BGP Notification sent)
Aug 18 2022 04:18:49.511 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.131 Down BGP Notification sent
Aug 18 2022 04:18:49.511 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.131 VPNv4 Unicast topology base removed from session BGP Notification sent
Aug 18 2022 04:18:49.511 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.131 IPv4 Unicast topology base removed from session BGP Notification sent
Aug 18 2022 04:22:17.016 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.0 Thread:115 TS:00018015331484357227 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.133
Aug 18 2022 04:27:24.223 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.131 Up
BGP is flapping when CPU is spiking and there are also CPU PUNT drops. For further analysis please configure the below EEM script on the router to capture the logs at the time of CPU spike events.
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100%
Good day!!
Thanks for the shared details, I can see below logs on the router.
Aug 18 2022 04:18:49.487 UTC: %BGP-3-NOTIFICATION: sent to neighbor 172.18.0.131 4/0 (hold time expired) 0 bytes
Aug 18 2022 04:18:49.487 UTC: %BGP-5-NBR_RESET: Neighbor 172.18.0.131 reset (BGP Notification sent)
Aug 18 2022 04:18:49.511 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.131 Down BGP Notification sent
Aug 18 2022 04:18:49.511 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.131 VPNv4 Unicast topology base removed from session BGP Notification sent
Aug 18 2022 04:18:49.511 UTC: %BGP_SESSION-5-ADJCHANGE: neighbor 172.18.0.131 IPv4 Unicast topology base removed from session BGP Notification sent
Aug 18 2022 04:22:17.016 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.0 Thread:115 TS:00018015331484357227 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.133
Aug 18 2022 04:27:24.223 UTC: %BGP-5-ADJCHANGE: neighbor 172.18.0.131 Up
BGP is flapping when CPU is spiking and there are also CPU PUNT drops.
For further analysis please configure the below EEM script on the router to capture the logs at the time of CPU spike events.
event manager applet ASR_High_CPU authorization bypass
event snmp oid 1.3.6.1.4.1.9.2.1.56 get-type next entry-op ge entry-val "85" exit-time 30 poll-interval 1
action 1.0 syslog msg "High cpu detected.
Please check bootflash:cpuinfo.txt"
action 2.0 cli command "enable"
action 3.0 cli command "term exec prompt timestamp"
action 4.0 cli command "show processes cpu sorted | append bootflash:cpuinfo.txt"
action 5.0 cli command "show process memory sorted | append bootflash:cpuinfo.txt"
action 5.4 cli command "show bgp all sum | append bootflash:cpuinfo.txt"
action 6.0 cli command "show platform hardware qfp active statistics drop | append bootflash:cpuinfo.txt"
action 7.1 cli command "show platform software punt-policer drop-only | append bootflash:cpuinfo.txt"
action 7.2 cli command "show platform hardware qfp active datapath utilization | append bootflash:cpuinfo.txt"
action 7.3 cli command "show process cpu hist | append bootflash:cpuinfo.txt"
action 7.7 cli command "show logging | append bootflash:cpuinfo.txt"
action 8.0 cli command "end"
The logs will be added to cpuinfo.txt file on the router flash memory.
Please share the same once the Event is triggered.
I have sent you CPU history you can find its happening very frequently.
It's an existing node and did do any config change.
We are observing 100% cpu and that's the main concern.
In addition, we have two nodes, and both have the high CPU.
I have already attached show tech and show processes cpu you can check.
Good Day!!
My name is Jobin, and I am sending you this e-mail to let you know that I have taken the ownership of this SR 695077555
As I have understood you are seeing issues with High CPU, please allow me some time go to through the logs will come back to you with an update.
Please let me know
1.
How frequently are you facing this issue ?
2.
Have you done any configuration changes ?
3.
Is it a new setup or the existing one ?
4.
Please explain the issue in brief.
Also, to help me better understand the urgency of this case, please briefly describe the business impact this issue has on your operations.
Note: Use "Reply All" function of your email program to ensure timely response for your queries
User: 00u547cgp4nzef79z5d7
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
File Name: sh-tech
File Type: web_uploaded
File Description:
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=63edd0feed79e76571433d48
File Upload Date / Time: Thu Feb 16 2023 14:45:22 GMT+0800 (Singapore Standard Time) - COMPLETED
You can now upload files to the case using FTP/FTPS/SCP/SFTP/HTTPS protocols and the following details:
Hostname: cxd.cisco.com
Username: 695077555
Password: O0QZpidf97QSUmC9
Please note:
1. When uploading to HTTPS the path must be set to /home/<filename>, for all other protocols the path is always '/<filename>'
2. Empty files, that is files with a size of 0 Bytes, will not be attached and will be deleted automatically.
User: 00u547cgp4nzef79z5d7
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
File Name: TLDC-CN-RTR01
File Type: web_uploaded
File Description:
File Link: https://mycase.cloudapps.cisco.com/695077555/attach?fileID=63edd0507ca83e7a3ae69e23
File Upload Date / Time: Thu Feb 16 2023 14:42:30 GMT+0800 (Singapore Standard Time) - COMPLETED
Hello Md Ali Emrose Khan,
This is confirmation that Case Number 695077555 was successfully opened with the Cisco Technical Assistance Center.
Case details:
Case: 695077555
Case Subject: Control Node CPU getting high (more than 90%)
Severity: 3
Status: Open
Please REPLY ALL to this email so that updates you make will be reflected in the case notes.
To manage this case, you can use:
Technology: Router and IOS Architecture
Subtechnology: IOS High CPU
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100%
Technology: Router and IOS Architecture
Subtechnology: IOS High CPU
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100%
we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100%
timestamp : 2023-03-30T12:49:59.000+0000 || updatedby : jobingeo || type : RESOLUTION SUMMARY || visibility : External || details : ++ Regarding the punt inject drops:
Feb 8 2023 05:57:56.583 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:090 TS:00031241039764900733 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/0 src ip: 172.18.1.98
Feb 8 2023 06:02:01.780 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:030 TS:00031241284970959902 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.134
show platform software punt-policer drop-only
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1. To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.currently process that is causing more CPU utilisation is BGP router but not sure when its 90% need to take a capture when its 90 percent.
LDC-CN-RTR01#sh processes cpu sorted
CPU utilization for five seconds: 66%/1%; one minute: 65%; five minutes: 64%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
722 2491375244 645632249 3858 54.43% 50.97% 50.59% 0 BGP Router
396 1358881623 1928116369 704 6.00% 7.08% 6.99% 0 LISP control
134 490160586 3276638596 0 2.56% 2.39% 2.40% 0 IOSXE-RP Punt Se
333 127630648 370024659 344 1.20% 1.34% 1.38% 0 IP RIB Update
228 5908 5801 1018 0.15% 1.07% 0.66% 2 SSH Process
306 15299251 276586916 55 0.15% 0.09% 0.08% 0 TCP Timer
152 22577584 3548004 6363 0.15% 0.07% 0.05% 0 Compute load av
BGP router process, Calculates the best BGP path and processes any route churn. It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
To get more details we need to enable debugs on the router.
Increase Interface Input Queues
If BGP advertises thousands of routes to many peers, TCP must transmit thousands of packets in a short duration. The BGP peers receive these packets and send TCP acknowledgements to the BGP speaker that advertises, which causes the BGP speaker to receive a flood of TCP ACKs in a short period of time. If the ACKs arrive at a rate that is too high for the route processor, packets back up in inbound interface queues. By default, router interfaces use an input queue size of 75 packets. In addition, special control packets such as BGP UPDATES use a special queue with Selective Packet Discard (SPD). This special queue holds 100 packets. When BGP convergence, happens TCP ACKs can fill quickly the 175 spots of input buffering and the new packets that arrive must be dropped. On routers with 15 or more BGP peers and exchange of the full Internet routing table, over 10,000 drops per interface per minute can be seen. Here is example output from a router 15 minutes after reboot:
Router#show interface pos 8/0 | include input queue
Output queue 0/40, 0 drops; input queue 0/75, 278637 drops
Router#
If you increase the interface input queue depth (with the hold-queue in command) it helps reduce the number of dropped TCP ACKs, which reduces the amount of work BGP must do to converge. Normally, a value of 1000 resolves problems caused by input queue drops.
These are described in below doc and matches the issue we are seeing, there could be some peers which are advertising the routes in continuous interval.
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html
++ Suggest increasing input que to 1000
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Please capture the below logs when CPU is over 90% to check further.
Show process cpu sorted
show bgp neighbors
show bgp all summary | i table
show bgp vpnv4 unicast all neighbors
show bgp all summary
show platform software punt-policer drop-only
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show logging | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: ASR1002-HX/ ASR1009-X Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Router and IOS Architecture
Subtechnology: IOS High CPU
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100%
we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100%
timestamp : 2023-03-30T12:49:59.000+0000 || updatedby : jobingeo || type : RESOLUTION SUMMARY || visibility : External || details : ++ Regarding the punt inject drops:
Feb 8 2023 05:57:56.583 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:090 TS:00031241039764900733 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/0 src ip: 172.18.1.98
Feb 8 2023 06:02:01.780 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:030 TS:00031241284970959902 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.134
show platform software punt-policer drop-only
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1. To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.currently process that is causing more CPU utilisation is BGP router but not sure when its 90% need to take a capture when its 90 percent.
LDC-CN-RTR01#sh processes cpu sorted
CPU utilization for five seconds: 66%/1%; one minute: 65%; five minutes: 64%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
722 2491375244 645632249 3858 54.43% 50.97% 50.59% 0 BGP Router
396 1358881623 1928116369 704 6.00% 7.08% 6.99% 0 LISP control
134 490160586 3276638596 0 2.56% 2.39% 2.40% 0 IOSXE-RP Punt Se
333 127630648 370024659 344 1.20% 1.34% 1.38% 0 IP RIB Update
228 5908 5801 1018 0.15% 1.07% 0.66% 2 SSH Process
306 15299251 276586916 55 0.15% 0.09% 0.08% 0 TCP Timer
152 22577584 3548004 6363 0.15% 0.07% 0.05% 0 Compute load av
BGP router process, Calculates the best BGP path and processes any route churn. It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
To get more details we need to enable debugs on the router.
Increase Interface Input Queues
If BGP advertises thousands of routes to many peers, TCP must transmit thousands of packets in a short duration. The BGP peers receive these packets and send TCP acknowledgements to the BGP speaker that advertises, which causes the BGP speaker to receive a flood of TCP ACKs in a short period of time. If the ACKs arrive at a rate that is too high for the route processor, packets back up in inbound interface queues. By default, router interfaces use an input queue size of 75 packets. In addition, special control packets such as BGP UPDATES use a special queue with Selective Packet Discard (SPD). This special queue holds 100 packets. When BGP convergence, happens TCP ACKs can fill quickly the 175 spots of input buffering and the new packets that arrive must be dropped. On routers with 15 or more BGP peers and exchange of the full Internet routing table, over 10,000 drops per interface per minute can be seen. Here is example output from a router 15 minutes after reboot:
Router#show interface pos 8/0 | include input queue
Output queue 0/40, 0 drops; input queue 0/75, 278637 drops
Router#
If you increase the interface input queue depth (with the hold-queue in command) it helps reduce the number of dropped TCP ACKs, which reduces the amount of work BGP must do to converge. Normally, a value of 1000 resolves problems caused by input queue drops.
These are described in below doc and matches the issue we are seeing, there could be some peers which are advertising the routes in continuous interval.
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html
++ Suggest increasing input que to 1000
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Please capture the below logs when CPU is over 90% to check further.
Show process cpu sorted
show bgp neighbors
show bgp all summary | i table
show bgp vpnv4 unicast all neighbors
show bgp all summary
show platform software punt-policer drop-only
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show logging | Technology: Router and IOS Architecture
Subtechnology: IOS High CPU
Problem Code: Software Failure
Product: NA
Product Family: ASR1000
Software Version: N/A
Router/Node Name: N/A
Problem Details: we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100% | we observing control node CPU getting high. we have two control node and both are getting High some time it reached 100% | timestamp : 2023-03-30T12:49:59.000+0000 || updatedby : jobingeo || type : RESOLUTION SUMMARY || visibility : External || details : ++ Regarding the punt inject drops:
Feb 8 2023 05:57:56.583 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:090 TS:00031241039764900733 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/0 src ip: 172.18.1.98
Feb 8 2023 06:02:01.780 UTC: %IOSXE-5-PLATFORM: R0/0: cpp_cp: QFP:0.1 Thread:030 TS:00031241284970959902 %PUNT_INJECT-5-DROP_PUNT_CAUSE: punt policer drops packets, cause: for-us-data (0xb) from TenGigabitEthernet0/1/1 src ip: 172.18.0.134
show platform software punt-policer drop-only
Per Punt-Cause Policer Configuration and Packet Counters
Punt Config Rate(pps) Conform Packets Dropped Packets Config Burst(pkts) Config Alert
Cause Description Normal High Normal High Normal High Normal High Normal High
-------------------------------------------------------------------------------------------------------------------------------------------------------------
11 For-us data 40000 5000 384699812 14399195415 0 611103 40000 5000 Off Off
1. To identify the packets that is causing the CPU spike, we need to enable the below debugs, please note these debugs can be run during the production and non-service impacting.
Conft
Ip access list extended TAC
Permit ip any any
debug platform condition ipv4 access-list TAC both
debug platform packet-trace packet 8192 circular fia-trace
debug platform packet-trace punt code 11
debug platform packet-trace copy packet both size 256 L3
once the punt logs are observed please run the below commands and share the tac.txt file for further analysis.
show platform packet-trace statistics | app tac.txt
show platform packet-trace summary | app tac.txt
show platform packet-trace packet all | app tac.txt ( wait for some time for router to copy all the packets )
show platform hardware qfp active infrastructure punt config cause 11 | app tac.txt
show platform software punt-policer drop-only | app tac.txt
Punt-policer is enabled by default, and it polices all the control plane punted traffic. When traffic for a specific punt cause exceeds the configured value, the packets will be dropped, and a log message printed, punt policer is enabled to control the CPU from becoming overwhelmed. Currently the high priority traffic threshold is 5000
As we see the high priority packets are dropped, we can increase the threshold to 15000 and see if there is any drops. ( this can be applied later after getting the logs from debugs)
Conf t
#Platform punt-policer 11 15000 high
2.In addition, please configure this command to monitor which process is taking the more CPU load.
process cpu threshold type total rising 90 interval 5 falling 50 intervals 5
3.currently process that is causing more CPU utilisation is BGP router but not sure when its 90% need to take a capture when its 90 percent.
LDC-CN-RTR01#sh processes cpu sorted
CPU utilization for five seconds: 66%/1%; one minute: 65%; five minutes: 64%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
722 2491375244 645632249 3858 54.43% 50.97% 50.59% 0 BGP Router
396 1358881623 1928116369 704 6.00% 7.08% 6.99% 0 LISP control
134 490160586 3276638596 0 2.56% 2.39% 2.40% 0 IOSXE-RP Punt Se
333 127630648 370024659 344 1.20% 1.34% 1.38% 0 IP RIB Update
228 5908 5801 1018 0.15% 1.07% 0.66% 2 SSH Process
306 15299251 276586916 55 0.15% 0.09% 0.08% 0 TCP Timer
152 22577584 3548004 6363 0.15% 0.07% 0.05% 0 Compute load av
BGP router process, Calculates the best BGP path and processes any route churn. It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
To get more details we need to enable debugs on the router.
Increase Interface Input Queues
If BGP advertises thousands of routes to many peers, TCP must transmit thousands of packets in a short duration. The BGP peers receive these packets and send TCP acknowledgements to the BGP speaker that advertises, which causes the BGP speaker to receive a flood of TCP ACKs in a short period of time. If the ACKs arrive at a rate that is too high for the route processor, packets back up in inbound interface queues. By default, router interfaces use an input queue size of 75 packets. In addition, special control packets such as BGP UPDATES use a special queue with Selective Packet Discard (SPD). This special queue holds 100 packets. When BGP convergence, happens TCP ACKs can fill quickly the 175 spots of input buffering and the new packets that arrive must be dropped. On routers with 15 or more BGP peers and exchange of the full Internet routing table, over 10,000 drops per interface per minute can be seen. Here is example output from a router 15 minutes after reboot:
Router#show interface pos 8/0 | include input queue
Output queue 0/40, 0 drops; input queue 0/75, 278637 drops
Router#
If you increase the interface input queue depth (with the hold-queue in command) it helps reduce the number of dropped TCP ACKs, which reduces the amount of work BGP must do to converge. Normally, a value of 1000 resolves problems caused by input queue drops.
These are described in below doc and matches the issue we are seeing, there could be some peers which are advertising the routes in continuous interval.
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html
++ Suggest increasing input que to 1000
interface tenGigabitEthernet 0/1/0
#hold-queue 1000 in
Please capture the below logs when CPU is over 90% to check further.
Show process cpu sorted
show bgp neighbors
show bgp all summary | i table
show bgp vpnv4 unicast all neighbors
show bgp all summary
show platform software punt-policer drop-only
show interfaces tenGigabitEthernet 0/1/0 | i que
show interfaces tenGigabitEthernet 0/1/1 | i que
show platform hardware qfp active statistics drop detail
show logging | nan | ASR1002-HX | asr1000-universalk9.17.03.04a.SPA.bin | nan | nan | 3 | nan | Debug/Diagnostic Capability (missing, incomplete, cryptic...) | ASR1000 | Router and IOS-XE Architecture | IOS-XE - NETCONF and RESTCONF and YANG | nan | nan | nan | nan | nan | nan |
694117912 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 2.2.3.4/ 16.12.04/ 2.1.2.7/ 2.2.2.9/ 2.2.2.8/ 1.3.1.4/ 2.3.3.4/ 2.3.3.7/ 2.2.2.8/ 1.3.3.7/ 17.03.03/ 2.1.2.7/ 1.3.3.7/ 2.2.2.9/ 2.3.3.7/ 16.12.4/ 2.2.3.5/ 2.2.3.6/ 2.2.2.9/ 4.0.4b/ 2.2.3.4/ 2.2.2.8/ 2.1.2.6/ 2.2.3.5 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Wearing a larger form for the below issue:
A big educational institution a cherished customer is observing this issue on a 3 node DNAC in 2.2.2.9 where port assignment provisioning removing radius config and reapplying the same in global config of the switch .
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
Some of the swicthes CU tested is exhibiting this behaviour. Attaching the show-tech from the switch to the case. This is first port provisioning done for the switch after update from 2.1.2.7 to 2.2.2.9
Host onboarding attempted for interface GigabitEthernet1/0/40
Upgrade of DNAC from 2.1.2.7 to 2.2.2.9 (16-18 Jul). Now when we do port provisioning, we observed this issue.
Please find below the information.
1.
Do all devices exhibit this behaviour ? What is the show run of this switch ? What are the last provisioning done for this device ?
Some of those we tested is exhibit this behaviour.
I have attached the show-tech from the switch to the case.
This is first port provisioning done for the switch after update from 2.1.2.7 to 2.2.2.9
2.
Is DNAC single node or three node cluster and what is the current version of DNAC?
3-node cluster
3.
Which interface was configured here ?
interface GigabitEthernet1/0/40
4.
Any recent changes post which this has been observed ? Since when did this start ?
Upgrade of DNAC from 2.1.2.7 to 2.2.2.9 (16-18 Jul).
Today when we do port provisioning, we observed this issue.
5.
Please collect and upload a RCA file to case
I will get it uploaded.
I will upload the other command output as well.
I have already uploaded DNAC screenshot, DNAC logs and FE/switch logs.
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC - Port Assignment provisioning removing radius config and reapplying the same
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
DNAC - Port Assignment provisioning removing radius config and reapplying the same
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
timestamp : 2022-09-07T12:12:02.000+0000 || updatedby : asechatu || type : RESOLUTION SUMMARY || visibility : External || details : after three attempts of reaching out to the customer he did not provide me the RCA to relay to the development engineers.
I will go ahead and close this case as the customer was unresponsive | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN1-HW-APL/ DN2-HW-APL/ DN2-HW-APL-XL/ C9300-48UN/ DN2-HW-APL-L/ DN2-HW-APL-U/ C9300-48U Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
After reproducing the issue we need the RCA .
Unfortunately we cannot proceed any further without it.
.:|:.:|:.
I have filled a new defect but with the RCA not uploaded I feel the logs would have got rolled over. Can you try the host onboarding again and collect the RCA ? Please help us with supporting logs also.
I have filled a new defect but with the RCA not uploaded I feel the logs would have got rolled over.
Can you try the host onboarding again and collect the RCA ? Please help us with supporting logs also.
.:|:.:|:.
Need to check for the following after an internal discussion
Do I need file a new defect or in some use cases this is okay ? Anyways assistance of this will really be helpful.
Wearing a larger form for the below issue:
A big educational institution a cherished customer is observing this issue on a 3 node DNAC in 2.2.2.9 where port assignment provisioning removing radius config and reapplying the same in global config of the switch .
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
Some of the swicthes CU tested is exhibiting this behaviour. Attaching the show-tech from the switch to the case. This is first port provisioning done for the switch after update from 2.1.2.7 to 2.2.2.9
Host onboarding attempted for interface GigabitEthernet1/0/40
Upgrade of DNAC from 2.1.2.7 to 2.2.2.9 (16-18 Jul). Now when we do port provisioning, we observed this issue.
For the last 3 days , I tried reaching out toa developer that handled a previous defect like this.
They haven’t replied to me.
I will reach out to bigger forum today and see response.
.:|:.:|:.
Please update the status.
Please find below the information.
1.
Do all devices exhibit this behaviour ? What is the show run of this switch ? What are the last provisioning done for this device ?
Some of those we tested is exhibit this behaviour.
I have attached the show-tech from the switch to the case.
This is first port provisioning done for the switch after update from 2.1.2.7 to 2.2.2.9
2.
Is DNAC single node or three node cluster and what is the current version of DNAC?
3-node cluster
3.
Which interface was configured here ?
interface GigabitEthernet1/0/40
4.
Any recent changes post which this has been observed ? Since when did this start ?
Upgrade of DNAC from 2.1.2.7 to 2.2.2.9 (16-18 Jul).
Today when we do port provisioning, we observed this issue.
5.
Please collect and upload a RCA file to case
I will get it uploaded.
I will upload the other command output as well.
I have already uploaded DNAC screenshot, DNAC logs and FE/switch logs.
Thank you for contacting Cisco Technical Support.
My name is Aseem and I will be working closely with you towards resolving this case.
I have gone through the case notes and inferred the following: -
Problem Description: DNAC - Port Assignment provisioning removing radius config and reapplying the same
Symptoms:
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
Action Plan:
To assist me with investigating this issue, are you able to please provide information/confirmation on the below points:
1.
Do all devices exhibit this behaviour ? What is the show run of this switch ? What are the last provisioning done for this device ?
2.
Is DNAC single node or three node cluster and what is the current version of DNAC?
3.
Which interface was configured here ?
4.
Any recent changes post which this has been observed ? Since when did this start ?
5.
Please collect and upload a RCA file to case
(For generation you need to just enter the command “rca “ one by one on all nodes and then extract from the DNAC refer section Extract the RCA file on a Windows computer in below document)
Reference 'How to Generate and Extract Root Cause Analysis (RCA) file from Digital Network Architecture (DNA) Center.': https://www.cisco.com/c/en/us/support/docs/cloud-systems-management/dna-center/213926-how-to-generate-and-extract-root-cause-a.html
8.
Please collect and send the following output from the maglev CLI:
a.
maglev package status
b.
magctl appstack status
c.
magctl appstack status | grep -v -E '([0-9]+)/\1.*Running'
d.
magctl node status
e.
magctl node display
f.
etcdctl cluster-health
Business Impact: Please provide what is the business impact ?
:|:.:|:.
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
File Name: 172.18.1.11_19082022_1643.log
File Type: log_values
File Description: show tech
File Link: https://mycase.cloudapps.cisco.com/694117912/attach?fileID=62ff52428a2e49561792555e
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
File Name: 694117912_DNAC_Provisiong_output.docx
File Type: log_values
File Description: DNAC & FE Logs
File Link: https://mycase.cloudapps.cisco.com/694117912/attach?fileID=62ff51e189279911bfcc6256
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
File Name: 694117912_172.18.1.11-19082022-095738.txt
File Type: log_values
File Description: DNAC & FE Logs
File Link: https://mycase.cloudapps.cisco.com/694117912/attach?fileID=62ff51dffdf3e35f19fc22d2
User: 00us9gpwj1wne67ev5d6
Email: [email protected]
File uploaded from Support Case Manager
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
File Name: 694117912_DNAC_Provisiong_logs.txt
File Type: log_values
File Description: DNAC & FE Logs
File Link: https://mycase.cloudapps.cisco.com/694117912/attach?fileID=62ff51dc32a485058cd97430
You can now upload files to the case using FTP/FTPS/SCP/SFTP/HTTPS protocols and the following details:
Hostname: cxd.cisco.com
Username: 694117912
Password: F0Tr1BXWcHVkhz8d
Please note:
1. When uploading to HTTPS the path must be set to /home/<filename>, for all other protocols the path is always '/<filename>'
2. Empty files, that is files with a size of 0 Bytes, will not be attached and will be deleted automatically.
Hello George Kingsley Paul Sundararaj,
This is confirmation that Case Number 694117912 was successfully opened with the Cisco Technical Assistance Center.
Case details:
Case: 694117912
Case Subject: DNAC - Port Assignment provisioning removing radius config and reapplying the same
Severity: 3
Status: Open
Please REPLY ALL to this email so that updates you make will be reflected in the case notes.
To manage this case, you can use:
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC - Port Assignment provisioning removing radius config and reapplying the same
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
DNAC - Port Assignment provisioning removing radius config and reapplying the same
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
timestamp : 2022-09-07T12:12:02.000+0000 || updatedby : asechatu || type : RESOLUTION SUMMARY || visibility : External || details : after three attempts of reaching out to the customer he did not provide me the RCA to relay to the development engineers.
I will go ahead and close this case as the customer was unresponsive | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Infrastructure (Services, UI, API, etc.)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC - Port Assignment provisioning removing radius config and reapplying the same
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit | DNAC - Port Assignment provisioning removing radius config and reapplying the same
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config)#no radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.9
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.9 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit
E2-03-CNT-ES2(config)#radius server dnac-radius_172.19.208.25
E2-03-CNT-ES2(config-radius-server)#address ipv4 172.19.208.25 auth-port 1812 acct-port 1813
E2-03-CNT-ES2(config-radius-server)#pac key 7 ******
E2-03-CNT-ES2(config-radius-server)#retransmit 3
E2-03-CNT-ES2(config-radius-server)#timeout 4
E2-03-CNT-ES2(config-radius-server)#automate-tester username dummy ignore-acct-port probe-on
E2-03-CNT-ES2(config-radius-server)#exit | timestamp : 2022-09-07T12:12:02.000+0000 || updatedby : asechatu || type : RESOLUTION SUMMARY || visibility : External || details : after three attempts of reaching out to the customer he did not provide me the RCA to relay to the development engineers.
I will go ahead and close this case as the customer was unresponsive | nan | DN1-HW-APL | DNAC-SW-2.2.2.9.bin | nan | nan | 3 | nan | Software Bug | C9300 | Cisco DNA Center - On-Prem | Cisco DNA Center - Infrastructure (Services, UI, API, etc.) | nan | nan | nan | nan | nan | nan |
694208469 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ 16.12.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9000 - Unexpected Reboot
Problem Code: Software Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: 9300 Switch reboot with the reason of "stack merge due to incompatibility". And in the show_version output, it only shows 5 switches, it actually have 7 switches stack.
9300 Switch reboot with the reason of "stack merge due to incompatibility". And in the show_version output, it only shows 5 switches, it actually have 7 switches stack.
Post reseating stack cables, switch stable | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U/ C9300-48U-A Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9000 - Unexpected Reboot
Problem Code: Software Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: 9300 Switch reboot with the reason of "stack merge due to incompatibility". And in the show_version output, it only shows 5 switches, it actually have 7 switches stack.
9300 Switch reboot with the reason of "stack merge due to incompatibility". And in the show_version output, it only shows 5 switches, it actually have 7 switches stack.
Post reseating stack cables, switch stable | Technology: LAN Switching
Subtechnology: Cat9000 - Unexpected Reboot
Problem Code: Software Failure
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: 9300 Switch reboot with the reason of "stack merge due to incompatibility". And in the show_version output, it only shows 5 switches, it actually have 7 switches stack. | 9300 Switch reboot with the reason of "stack merge due to incompatibility". And in the show_version output, it only shows 5 switches, it actually have 7 switches stack. | Post reseating stack cables, switch stable | Switch crashed | C9300-48U-A | 16.12.4 | 16.12.4 | 71.0 | 3 | 100.0 | Software Bug | C9300 | LAN Switching | Cat9000 - Unexpected Reboot | 01t1C000006fIcDQAU | Software Failure | Cat9000 - Unexpected Reboot | LAN Switching | 01t15000005W0LTAA0 | SHERLOCK: PARTIAL |
694249113 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 16.12.04/ NA - COMPONENT ONLY/ THIRD_PARTY_PRODUCT_SW/ NA - RMA/ 16.12.04/ 3.2.3o/ 15.0.2/ 16.06.07/ 16.12.03s/ 1/ 16.06.08/ 16.12.1s/ 17.03.05/ 16.12.4/ 16.9.5/ 16.12.01s/ PRODUCT_NOT_FOUND/ 16.3.5/ 16.12.3s/ 16.09.02/ 16.12.3a/ 16.12.1s/ 17.6.4 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
We have observed in 9300 switch log Power Device detected: Cisco PD and remove.
we checked interface is down. not sure about this alarm could you please help to explain and do t-shoot.
CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
Hi,
We have observed in 9300 switch log Power Device detected: Cisco PD and remove.
we checked interface is down. not sure about this alarm could you please help to explain and do t-shoot.
CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
--on the device we were observing multiple logs, even when there is nothing connected on the port.
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
--we collected the Techsupport and on further validation, we see the option to disable the inline power to get rid of the issue and since the code which is running is an old code we suggested to upgrade.
--we were not able to upgrade as end customer wants to know the exact bug.
--collected the required data and figured out the issue to be known bug on the code CSCvv91944, for which we have a workaround in place and for the permanent fix upgrade is needed. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: C9300-48U-A/ C9300-48U/ THIRD_PARTY_PRODUCT_HW/ UCS-FI-6454/ C9300-NM-8X/ PWR-C1-1100WAC Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
We have observed in 9300 switch log Power Device detected: Cisco PD and remove.
we checked interface is down. not sure about this alarm could you please help to explain and do t-shoot.
CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
Hi,
We have observed in 9300 switch log Power Device detected: Cisco PD and remove.
we checked interface is down. not sure about this alarm could you please help to explain and do t-shoot.
CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
--on the device we were observing multiple logs, even when there is nothing connected on the port.
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
--we collected the Techsupport and on further validation, we see the option to disable the inline power to get rid of the issue and since the code which is running is an old code we suggested to upgrade.
--we were not able to upgrade as end customer wants to know the exact bug.
--collected the required data and figured out the issue to be known bug on the code CSCvv91944, for which we have a workaround in place and for the permanent fix upgrade is needed. | Technology: LAN Switching
Subtechnology: Cat9300
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi,
We have observed in 9300 switch log Power Device detected: Cisco PD and remove.
we checked interface is down. not sure about this alarm could you please help to explain and do t-shoot.
CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected | Hi,
We have observed in 9300 switch log Power Device detected: Cisco PD and remove.
we checked interface is down. not sure about this alarm could you please help to explain and do t-shoot.
CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected | --on the device we were observing multiple logs, even when there is nothing connected on the port.
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected
--we collected the Techsupport and on further validation, we see the option to disable the inline power to get rid of the issue and since the code which is running is an old code we suggested to upgrade.
--we were not able to upgrade as end customer wants to know the exact bug.
--collected the required data and figured out the issue to be known bug on the code CSCvv91944, for which we have a workaround in place and for the permanent fix upgrade is needed. | CELS-04-CNT-ES1#show interfaces Gi1/0/14
GigabitEthernet1/0/14 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is f8a7.3a1a.848e (bia f8a7.3a1a.848e)
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
CELS-04-CNT-ES1#show power inline gigabitEthernet 1/0/14
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/14 auto off 0.0 n/a n/a 60.0
CELS-04-CNT-ES1#
Sep 13 2022 01:51:39.024 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:52.649 UTC: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: Cisco PD
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/14: PD removed
Sep 13 2022 01:51:54.009 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/14: Power Controller reports power Tstart error detected | C9300-48U-A | 16.12.4 | 16.12.4 | 37.0 | 3 | 100.0 | Software Bug | C9300 | LAN Switching | Cat9300 | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | Cat9300 | LAN Switching | 01t15000005W0LTAA0 | nan |
695545329 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1.3.3.7/ 2.2.3.6/ 16.12.04/ 2.3.3.6/ 2.3.3.7.72323/ 2.3.3.7/ 2.1.2.7/ 2.3.3.7.72328/ 2.3.3.4/ 2.2.2.9/ 2.1.2.7 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Assurance
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC - Wireless Assurance Data unavailable post upgrade from 2.2.2.9 to 2.3.3.7
(TLDC-WL-WLC01) >show network assurance summary
Server url............................. https://172.18.12.19
Wsa Service............................ Disabled
NAC Data Publish Status:
Current State....................... Idle
Last Error.......................... Mon May 15 20:28:53 2023 Un-Authorized JWT Token
Last Success........................ Mon May 15 20:41:12 2023
Last 5XX server response............ An invalid response was received from the backend service. Please refer to the backend service's logs for more details.
JWT Token Config.................... JWT Auth Configured
JWT Last Success.................... Mon May 15 20:28:53 2023
JWT Last Failure.................... Sun May 7 15:28:07 2023 Received server response code (0)
Sensor Backhaul settings:
Ssid................................ Not Configured
Authentication...................... Open
Sensor provisioning:
Status.............................. Disabled
Interface Name...................... None
WLAN ID............................. None
SSID................................ None
DNAC - Wireless Assurance Data unavailable post upgrade from 2.2.2.9 to 2.3.3.7
(TLDC-WL-WLC01) >show network assurance summary
Server url............................. https://172.18.12.19
Wsa Service............................ Disabled
NAC Data Publish Status:
Current State....................... Idle
Last Error.......................... Mon May 15 20:28:53 2023 Un-Authorized JWT Token
Last Success........................ Mon May 15 20:41:12 2023
Last 5XX server response............ An invalid response was received from the backend service. Please refer to the backend service's logs for more details.
JWT Token Config.................... JWT Auth Configured
JWT Last Success.................... Mon May 15 20:28:53 2023
JWT Last Failure.................... Sun May 7 15:28:07 2023 Received server response code (0)
Sensor Backhaul settings:
Ssid................................ Not Configured
Authentication...................... Open
Sensor provisioning:
Status.............................. Disabled
Interface Name...................... None
WLAN ID............................. None
SSID................................ None
Following is the case summary:
Problem Description:
- DNAC Wireless Assurance health score shows 0 after May 15 9:00 PM SGT.
- Issue seen after provisioning the WLC.
- **Provisioning time:** May 15 @ 12:53 UTC.
Setup Info:
- DNAC version: 2.3.3.7
- WLC we are focusing:
- **Hostname:** TLDC-WL-WLC01
- **IP:** 172.18.240.13
- **HW/SW:** AIR-CT8540-K9 / 8.10.183.0
Tshoot/Analysis:
- We have seen that Wireless assurance is missing in DNAC since around May 15 9:00 PM SGT.
- Checking WLC configuration we see that it is disabled.
- Checking DNAC site settings we see that Wireless telemetry is disabled.
- We also observed that around 8:53 PM SGT, the WLC was provisioned as part of another activity.
- Suspect that the WLC was provisioned with Wireless telemetry disabled as per the site settings configured in DNAC.
- However, the audit log details, or configuration preview do not indicate that wireless assurance was disabled.
- You forced pushed the telemetry settings to WLC [172.18.240.13] during MW on 20 May. However that does not seem to enable the WSA service on the WLC.
- On further analysis, identified following defects which have been root caused to CSCvk62901 libssh2 library upgrade for WLC
CSCvq42714 WLC WSA service is disabled after discovery and provisioning due to which it says unmonitored
CSCvp20941 Assurance configs are not getting pushed to WLC.
- engaged Sudhanshu from WLC team who validated this in lab and it was working as expected.
- In order to further isolate the issue and he requested following details.
o Save the putty session of WLC and run the below debugs on WLC.
show logging config-history
debug emweb web enable
debug pm pki enable
o Trigger the issue by doing 'Update Telemetry Settings' --> "Force Configuration push" from DNAC.
o After running the above debugs commands on WLC and triggering the issue from DNAC, wait for 10 min to collect the outputs on WLC, then close the SSH session and share the file.
o From DNAC side, upload the RCA file.
- As per your last update,
Telemetry Settings for wlc01 had been updated on 4th of July and assurance got enabled for that WLC since then.
- As per your request we monitored the status by end of the week and did not receive any further issues reported. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ C9300-48U/ C6807-DNA-A Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Assurance
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC - Wireless Assurance Data unavailable post upgrade from 2.2.2.9 to 2.3.3.7
(TLDC-WL-WLC01) >show network assurance summary
Server url............................. https://172.18.12.19
Wsa Service............................ Disabled
NAC Data Publish Status:
Current State....................... Idle
Last Error.......................... Mon May 15 20:28:53 2023 Un-Authorized JWT Token
Last Success........................ Mon May 15 20:41:12 2023
Last 5XX server response............ An invalid response was received from the backend service. Please refer to the backend service's logs for more details.
JWT Token Config.................... JWT Auth Configured
JWT Last Success.................... Mon May 15 20:28:53 2023
JWT Last Failure.................... Sun May 7 15:28:07 2023 Received server response code (0)
Sensor Backhaul settings:
Ssid................................ Not Configured
Authentication...................... Open
Sensor provisioning:
Status.............................. Disabled
Interface Name...................... None
WLAN ID............................. None
SSID................................ None
DNAC - Wireless Assurance Data unavailable post upgrade from 2.2.2.9 to 2.3.3.7
(TLDC-WL-WLC01) >show network assurance summary
Server url............................. https://172.18.12.19
Wsa Service............................ Disabled
NAC Data Publish Status:
Current State....................... Idle
Last Error.......................... Mon May 15 20:28:53 2023 Un-Authorized JWT Token
Last Success........................ Mon May 15 20:41:12 2023
Last 5XX server response............ An invalid response was received from the backend service. Please refer to the backend service's logs for more details.
JWT Token Config.................... JWT Auth Configured
JWT Last Success.................... Mon May 15 20:28:53 2023
JWT Last Failure.................... Sun May 7 15:28:07 2023 Received server response code (0)
Sensor Backhaul settings:
Ssid................................ Not Configured
Authentication...................... Open
Sensor provisioning:
Status.............................. Disabled
Interface Name...................... None
WLAN ID............................. None
SSID................................ None
Following is the case summary:
Problem Description:
- DNAC Wireless Assurance health score shows 0 after May 15 9:00 PM SGT.
- Issue seen after provisioning the WLC.
- **Provisioning time:** May 15 @ 12:53 UTC.
Setup Info:
- DNAC version: 2.3.3.7
- WLC we are focusing:
- **Hostname:** TLDC-WL-WLC01
- **IP:** 172.18.240.13
- **HW/SW:** AIR-CT8540-K9 / 8.10.183.0
Tshoot/Analysis:
- We have seen that Wireless assurance is missing in DNAC since around May 15 9:00 PM SGT.
- Checking WLC configuration we see that it is disabled.
- Checking DNAC site settings we see that Wireless telemetry is disabled.
- We also observed that around 8:53 PM SGT, the WLC was provisioned as part of another activity.
- Suspect that the WLC was provisioned with Wireless telemetry disabled as per the site settings configured in DNAC.
- However, the audit log details, or configuration preview do not indicate that wireless assurance was disabled.
- You forced pushed the telemetry settings to WLC [172.18.240.13] during MW on 20 May. However that does not seem to enable the WSA service on the WLC.
- On further analysis, identified following defects which have been root caused to CSCvk62901 libssh2 library upgrade for WLC
CSCvq42714 WLC WSA service is disabled after discovery and provisioning due to which it says unmonitored
CSCvp20941 Assurance configs are not getting pushed to WLC.
- engaged Sudhanshu from WLC team who validated this in lab and it was working as expected.
- In order to further isolate the issue and he requested following details.
o Save the putty session of WLC and run the below debugs on WLC.
show logging config-history
debug emweb web enable
debug pm pki enable
o Trigger the issue by doing 'Update Telemetry Settings' --> "Force Configuration push" from DNAC.
o After running the above debugs commands on WLC and triggering the issue from DNAC, wait for 10 min to collect the outputs on WLC, then close the SSH session and share the file.
o From DNAC side, upload the RCA file.
- As per your last update,
Telemetry Settings for wlc01 had been updated on 4th of July and assurance got enabled for that WLC since then.
- As per your request we monitored the status by end of the week and did not receive any further issues reported. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Assurance
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: DNAC - Wireless Assurance Data unavailable post upgrade from 2.2.2.9 to 2.3.3.7
(TLDC-WL-WLC01) >show network assurance summary
Server url............................. https://172.18.12.19
Wsa Service............................ Disabled
NAC Data Publish Status:
Current State....................... Idle
Last Error.......................... Mon May 15 20:28:53 2023 Un-Authorized JWT Token
Last Success........................ Mon May 15 20:41:12 2023
Last 5XX server response............ An invalid response was received from the backend service. Please refer to the backend service's logs for more details.
JWT Token Config.................... JWT Auth Configured
JWT Last Success.................... Mon May 15 20:28:53 2023
JWT Last Failure.................... Sun May 7 15:28:07 2023 Received server response code (0)
Sensor Backhaul settings:
Ssid................................ Not Configured
Authentication...................... Open
Sensor provisioning:
Status.............................. Disabled
Interface Name...................... None
WLAN ID............................. None
SSID................................ None | DNAC - Wireless Assurance Data unavailable post upgrade from 2.2.2.9 to 2.3.3.7
(TLDC-WL-WLC01) >show network assurance summary
Server url............................. https://172.18.12.19
Wsa Service............................ Disabled
NAC Data Publish Status:
Current State....................... Idle
Last Error.......................... Mon May 15 20:28:53 2023 Un-Authorized JWT Token
Last Success........................ Mon May 15 20:41:12 2023
Last 5XX server response............ An invalid response was received from the backend service. Please refer to the backend service's logs for more details.
JWT Token Config.................... JWT Auth Configured
JWT Last Success.................... Mon May 15 20:28:53 2023
JWT Last Failure.................... Sun May 7 15:28:07 2023 Received server response code (0)
Sensor Backhaul settings:
Ssid................................ Not Configured
Authentication...................... Open
Sensor provisioning:
Status.............................. Disabled
Interface Name...................... None
WLAN ID............................. None
SSID................................ None | Following is the case summary:
Problem Description:
- DNAC Wireless Assurance health score shows 0 after May 15 9:00 PM SGT.
- Issue seen after provisioning the WLC.
- **Provisioning time:** May 15 @ 12:53 UTC.
Setup Info:
- DNAC version: 2.3.3.7
- WLC we are focusing:
- **Hostname:** TLDC-WL-WLC01
- **IP:** 172.18.240.13
- **HW/SW:** AIR-CT8540-K9 / 8.10.183.0
Tshoot/Analysis:
- We have seen that Wireless assurance is missing in DNAC since around May 15 9:00 PM SGT.
- Checking WLC configuration we see that it is disabled.
- Checking DNAC site settings we see that Wireless telemetry is disabled.
- We also observed that around 8:53 PM SGT, the WLC was provisioned as part of another activity.
- Suspect that the WLC was provisioned with Wireless telemetry disabled as per the site settings configured in DNAC.
- However, the audit log details, or configuration preview do not indicate that wireless assurance was disabled.
- You forced pushed the telemetry settings to WLC [172.18.240.13] during MW on 20 May. However that does not seem to enable the WSA service on the WLC.
- On further analysis, identified following defects which have been root caused to CSCvk62901 libssh2 library upgrade for WLC
CSCvq42714 WLC WSA service is disabled after discovery and provisioning due to which it says unmonitored
CSCvp20941 Assurance configs are not getting pushed to WLC.
- engaged Sudhanshu from WLC team who validated this in lab and it was working as expected.
- In order to further isolate the issue and he requested following details.
o Save the putty session of WLC and run the below debugs on WLC.
show logging config-history
debug emweb web enable
debug pm pki enable
o Trigger the issue by doing 'Update Telemetry Settings' --> "Force Configuration push" from DNAC.
o After running the above debugs commands on WLC and triggering the issue from DNAC, wait for 10 min to collect the outputs on WLC, then close the SSH session and share the file.
o From DNAC side, upload the RCA file.
- As per your last update,
Telemetry Settings for wlc01 had been updated on 4th of July and assurance got enabled for that WLC since then.
- As per your request we monitored the status by end of the week and did not receive any further issues reported. | - DNAC Wireless Assurance health score shows 0 after May 15 9:00 PM SGT.
- Issue seen after provisioning the WLC.
- DNAC version: 2.3.3.7
- WLC we are focusing:
- **Hostname:** TLDC-WL-WLC01
- **IP:** 172.18.240.13
- **HW/SW:** AIR-CT8540-K9 / 8.10.183.0
- **Provisioning time:** May 15 @ 12:53 UTC. | DN2-HW-APL-XL | 2.3.3.7 | 2.3.3.7 | 70.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | DNAHW | Cisco DNA Center - On-Prem | Cisco DNA Center - Assurance | 01t6R000007PJzCQAW | Error Messages, Logs, Debugs | Cisco DNA Center - Assurance | Cisco DNA Center - On-Prem | 01t1C000006B44HQAS | SHERLOCK: PARTIAL |
695648768 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: AP is connected to controller TLDC-WL-WLC02. refer to attached ap log.
From AP log,
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.7390] CAPWAP State: Run
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.8130] AP has joined controller TLDC-WL-WLC02
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Warning, unencrypted data keepalive failed
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830]
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:01:05 kernel: [*06/06/2023 17:01:05.6600] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:02:30 kernel: [*06/06/2023 17:02:30.6790] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:05:18 kernel: [*06/06/2023 17:05:18.6760] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:06:42 kernel: [*06/06/2023 17:06:42.6610] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:08:06 kernel: [*06/06/2023 17:08:06.6610] Going to restart CAPWAP (reason : data keepalive not received)...
AP is connected to controller TLDC-WL-WLC02. refer to attached ap log.
From AP log,
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.7390] CAPWAP State: Run
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.8130] AP has joined controller TLDC-WL-WLC02
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Warning, unencrypted data keepalive failed
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830]
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:01:05 kernel: [*06/06/2023 17:01:05.6600] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:02:30 kernel: [*06/06/2023 17:02:30.6790] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:05:18 kernel: [*06/06/2023 17:05:18.6760] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:06:42 kernel: [*06/06/2023 17:06:42.6610] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:08:06 kernel: [*06/06/2023 17:08:06.6610] Going to restart CAPWAP (reason : data keepalive not received)...
APs disjoin while being a part of a fabric network.
Issue occurs in 16.12.x, post upgrade to 17.6.4 it has been stable.
Presently we are not seeing any AP flaps for the last 2 months after the image upgrade of the fabric edge(FE) to 17.6.4. The action plan has been shared as part of the RCA readout and in the slide deck, the logs to be collected and shared have been noted in case an issue is seen on the 17.6.4 image in the future | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: AP is connected to controller TLDC-WL-WLC02. refer to attached ap log.
From AP log,
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.7390] CAPWAP State: Run
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.8130] AP has joined controller TLDC-WL-WLC02
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Warning, unencrypted data keepalive failed
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830]
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:01:05 kernel: [*06/06/2023 17:01:05.6600] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:02:30 kernel: [*06/06/2023 17:02:30.6790] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:05:18 kernel: [*06/06/2023 17:05:18.6760] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:06:42 kernel: [*06/06/2023 17:06:42.6610] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:08:06 kernel: [*06/06/2023 17:08:06.6610] Going to restart CAPWAP (reason : data keepalive not received)...
AP is connected to controller TLDC-WL-WLC02. refer to attached ap log.
From AP log,
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.7390] CAPWAP State: Run
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.8130] AP has joined controller TLDC-WL-WLC02
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Warning, unencrypted data keepalive failed
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830]
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:01:05 kernel: [*06/06/2023 17:01:05.6600] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:02:30 kernel: [*06/06/2023 17:02:30.6790] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:05:18 kernel: [*06/06/2023 17:05:18.6760] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:06:42 kernel: [*06/06/2023 17:06:42.6610] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:08:06 kernel: [*06/06/2023 17:08:06.6610] Going to restart CAPWAP (reason : data keepalive not received)...
APs disjoin while being a part of a fabric network.
Issue occurs in 16.12.x, post upgrade to 17.6.4 it has been stable.
Presently we are not seeing any AP flaps for the last 2 months after the image upgrade of the fabric edge(FE) to 17.6.4. The action plan has been shared as part of the RCA readout and in the slide deck, the logs to be collected and shared have been noted in case an issue is seen on the 17.6.4 image in the future | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: AP is connected to controller TLDC-WL-WLC02. refer to attached ap log.
From AP log,
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.7390] CAPWAP State: Run
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.8130] AP has joined controller TLDC-WL-WLC02
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Warning, unencrypted data keepalive failed
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830]
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:01:05 kernel: [*06/06/2023 17:01:05.6600] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:02:30 kernel: [*06/06/2023 17:02:30.6790] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:05:18 kernel: [*06/06/2023 17:05:18.6760] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:06:42 kernel: [*06/06/2023 17:06:42.6610] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:08:06 kernel: [*06/06/2023 17:08:06.6610] Going to restart CAPWAP (reason : data keepalive not received)... | AP is connected to controller TLDC-WL-WLC02. refer to attached ap log.
From AP log,
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.7390] CAPWAP State: Run
Jun 6 09:02:57 kernel: [*06/06/2023 17:02:57.8130] AP has joined controller TLDC-WL-WLC02
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Warning, unencrypted data keepalive failed
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830]
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:01:05 kernel: [*06/06/2023 17:01:05.6600] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:02:30 kernel: [*06/06/2023 17:02:30.6790] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:03:54 kernel: [*06/06/2023 17:03:54.6830] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:05:18 kernel: [*06/06/2023 17:05:18.6760] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:06:42 kernel: [*06/06/2023 17:06:42.6610] Going to restart CAPWAP (reason : data keepalive not received)...
Jun 6 09:08:06 kernel: [*06/06/2023 17:08:06.6610] Going to restart CAPWAP (reason : data keepalive not received)... | APs disjoin while being a part of a fabric network.
Issue occurs in 16.12.x, post upgrade to 17.6.4 it has been stable.
Presently we are not seeing any AP flaps for the last 2 months after the image upgrade of the fabric edge(FE) to 17.6.4. The action plan has been shared as part of the RCA readout and in the slide deck, the logs to be collected and shared have been noted in case an issue is seen on the 17.6.4 image in the future | SDA AP Flapping Continuously | AIR-CT8540-K9 | 16.12.4 | 16.12.4 | 62.0 | 3 | 100.0 | Software Bug | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t1C000006fIcDQAU | Error Messages, Logs, Debugs | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t15000004dDRMAA2 | CaseClosureFieldAutomation: Partial |
694180060 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 3.0.0.458/ 2.7.0.356/ 3.0.0.448/ 3.0.0.458/ 3.0.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: Slow Replication Error for MNT node
Message=Node hsdc-mnt-nac01 has slow replication since this node is not consuming messages for past 1829 minutes
Slow Replication Error for MNT node
Message=Node hsdc-mnt-nac01 has slow replication since this node is not consuming messages for past 1829 minutes
Problem Description:
====================
Slow Replication Error for MNT node
Troubleshooting/ Steps taken:
===========
- we collected the SB from the MNT node, but it wasn’t attached to case.
- customer found that replication ports weren’t opened for the MNT node on the firewall.
- post fixing it slow replication error was fixed and no more observed.
Resolution:
============
Opening the replication ports on the firewall. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: SNS-3655-K9/ SNS-3695-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: Slow Replication Error for MNT node
Message=Node hsdc-mnt-nac01 has slow replication since this node is not consuming messages for past 1829 minutes
Slow Replication Error for MNT node
Message=Node hsdc-mnt-nac01 has slow replication since this node is not consuming messages for past 1829 minutes
Problem Description:
====================
Slow Replication Error for MNT node
Troubleshooting/ Steps taken:
===========
- we collected the SB from the MNT node, but it wasn’t attached to case.
- customer found that replication ports weren’t opened for the MNT node on the firewall.
- post fixing it slow replication error was fixed and no more observed.
Resolution:
============
Opening the replication ports on the firewall. | Technology: Identity Services Engine (ISE) - 3.0
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: Slow Replication Error for MNT node
Message=Node hsdc-mnt-nac01 has slow replication since this node is not consuming messages for past 1829 minutes | Slow Replication Error for MNT node
Message=Node hsdc-mnt-nac01 has slow replication since this node is not consuming messages for past 1829 minutes | Problem Description:
====================
Slow Replication Error for MNT node
Troubleshooting/ Steps taken:
===========
- we collected the SB from the MNT node, but it wasn’t attached to case.
- customer found that replication ports weren’t opened for the MNT node on the firewall.
- post fixing it slow replication error was fixed and no more observed.
Resolution:
============
Opening the replication ports on the firewall. | Slow Replication Error for MNT node | SNS-3695-K9 | 3.0.0-BETA-DROP4 | 3.0.0-BETA-DROP4 | 60.0 | 3 | 100.0 | Software -not a bug (scalability, version selection, install/upgrade help...) | CISE | Identity Services Engine (ISE) - 3.0 | ISE Performance (High CPU / Memory / IO / GUI Slowness) | 01t1C000006Dwc3QAC | Error Messages, Logs, Debugs | ISE Performance (High CPU / Memory / IO / GUI Slowness) | Identity Services Engine (ISE) - 3.0 | 01t1C000006BE4YQAW | nan |
694925180 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 2.2.2.9/ 2.2.2.8/ 1.3.3.7/ 2.2.3.6/ 1.3.3.7 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
We saw that WLC is continious sync . It does not go into managed state it keeps synching itself
From the logs we are seeing this info :
105 | 2023-04-19 02:54:20,889 | INFO | pository Unloading Thread | | XDE.runtime | Unloaded 2 function sets |
| 106 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 107 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 108 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 109 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 110 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 111 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 112 | 2023-04-19 02:54:31,236 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Building associations complete. Total time :89369 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
| 113 | 2023-04-19 02:54:31,246 | INFO | ICE Service - CPU 7 | | c.c.e.i.util.ShardOwnerValidator | Device: e1c7b3c8-7674-4d31-91f5-8cfb7cc1637a is owned by this instance of inventory service |
| 114 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Collector context is set to ignore the Serialnumber change for 11381375 | MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational, mid=2
| 115 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | 172.18.240.13 persistObjects called with addMap size = 0, updateSet size = 4685, sameSet size = 37568, and tenant from collection context = 5db7b7be12f3bd00cc115f77 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
We got to know that AP are continuously getting disconnected and getting connected back due to this the WLC in DNAC is kept in synching process as event based sync happens in DNAC . Once the frequent ap disconnect issue is resolved we are able to see WLC goes back into managed state
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Discovery and Inventory
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Fabric WLC got stuck on the syncing process for more than 4 hours since raising this TAC case
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant
Fabric WLC got stuck on the syncing process for more than 4 hours since raising this TAC case
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant
We saw that WLC is continious sync . It does not go into managed state it keeps synching itself
From the logs we are seeing this info :
105 | 2023-04-19 02:54:20,889 | INFO | pository Unloading Thread | | XDE.runtime | Unloaded 2 function sets |
| 106 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 107 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 108 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 109 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 110 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 111 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 112 | 2023-04-19 02:54:31,236 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Building associations complete. Total time :89369 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
| 113 | 2023-04-19 02:54:31,246 | INFO | ICE Service - CPU 7 | | c.c.e.i.util.ShardOwnerValidator | Device: e1c7b3c8-7674-4d31-91f5-8cfb7cc1637a is owned by this instance of inventory service |
| 114 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Collector context is set to ignore the Serialnumber change for 11381375 | MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational, mid=2
| 115 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | 172.18.240.13 persistObjects called with addMap size = 0, updateSet size = 4685, sameSet size = 37568, and tenant from collection context = 5db7b7be12f3bd00cc115f77 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
We got to know that AP are continuously getting disconnected and getting connected back due to this the WLC in DNAC is kept in synching process as event based sync happens in DNAC . Once the frequent ap disconnect issue is resolved we are able to see WLC goes back into managed state | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Discovery and Inventory
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Fabric WLC got stuck on the syncing process for more than 4 hours since raising this TAC case
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant
Fabric WLC got stuck on the syncing process for more than 4 hours since raising this TAC case
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant
We saw that WLC is continious sync . It does not go into managed state it keeps synching itself
From the logs we are seeing this info :
105 | 2023-04-19 02:54:20,889 | INFO | pository Unloading Thread | | XDE.runtime | Unloaded 2 function sets |
| 106 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 107 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 108 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 109 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 110 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 111 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 112 | 2023-04-19 02:54:31,236 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Building associations complete. Total time :89369 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
| 113 | 2023-04-19 02:54:31,246 | INFO | ICE Service - CPU 7 | | c.c.e.i.util.ShardOwnerValidator | Device: e1c7b3c8-7674-4d31-91f5-8cfb7cc1637a is owned by this instance of inventory service |
| 114 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Collector context is set to ignore the Serialnumber change for 11381375 | MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational, mid=2
| 115 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | 172.18.240.13 persistObjects called with addMap size = 0, updateSet size = 4685, sameSet size = 37568, and tenant from collection context = 5db7b7be12f3bd00cc115f77 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
We got to know that AP are continuously getting disconnected and getting connected back due to this the WLC in DNAC is kept in synching process as event based sync happens in DNAC . Once the frequent ap disconnect issue is resolved we are able to see WLC goes back into managed state | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco DNA Center - Discovery and Inventory
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: DNAHW
Software Version: N/A
Router/Node Name: N/A
Problem Details: Fabric WLC got stuck on the syncing process for more than 4 hours since raising this TAC case
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant | Fabric WLC got stuck on the syncing process for more than 4 hours since raising this TAC case
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant | We saw that WLC is continious sync . It does not go into managed state it keeps synching itself
From the logs we are seeing this info :
105 | 2023-04-19 02:54:20,889 | INFO | pository Unloading Thread | | XDE.runtime | Unloaded 2 function sets |
| 106 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 107 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 108 | 2023-04-19 02:54:20,919 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 109 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.impl.InventoryServiceImpl | getDeviceId: Fetched ManagedElementInterface Id 11381375 |
| 110 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.util.EventSyncTracker | Delaying sync request for 11381375 as continuous event based sync detected for the device. Event based sync requests in queue :1 |
| 111 | 2023-04-19 02:54:30,948 | INFO | pool-24-thread-1 | | c.c.e.i.n.p.APTrapEventProcessor | It is detected that the device went through continuous event based sync, so delaying the sync request 172.18.240.13 |
| 112 | 2023-04-19 02:54:31,236 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Building associations complete. Total time :89369 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
| 113 | 2023-04-19 02:54:31,246 | INFO | ICE Service - CPU 7 | | c.c.e.i.util.ShardOwnerValidator | Device: e1c7b3c8-7674-4d31-91f5-8cfb7cc1637a is owned by this instance of inventory service |
| 114 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | Collector context is set to ignore the Serialnumber change for 11381375 | MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational, mid=2
| 115 | 2023-04-19 02:54:31,247 | INFO | ICE Service - CPU 7 | | com.cisco.xmp.inventory | 172.18.240.13 persistObjects called with addMap size = 0, updateSet size = 4685, sameSet size = 37568, and tenant from collection context = 5db7b7be12f3bd00cc115f77 | mid=2, MSGNAME=XICE_GENERIC_MSG_INF_02, ch=com.cisco.xmp.inventory, sev=informational
We got to know that AP are continuously getting disconnected and getting connected back due to this the WLC in DNAC is kept in synching process as event based sync happens in DNAC . Once the frequent ap disconnect issue is resolved we are able to see WLC goes back into managed state | The customer is having issues with a wireless controller that's been showing in syncing status for more than 4 hours.
TLDC-WL-WLC01
172.18.240.13 Wireless Controller
Reachable
Managed
Syncing...
Non-Compliant
Cisco DNA center 2.2.2.9 | DN2-HW-APL-XL | 2.2.2.9 | 2.2.2.9 | 38.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | DNAHW | Cisco DNA Center - On-Prem | Cisco DNA Center - Discovery and Inventory | 01t6R000006k0UEQAY | Error Messages, Logs, Debugs | Cisco DNA Center - Discovery and Inventory | Cisco DNA Center - On-Prem | 01t1C0000061ceHQAQ | SHERLOCK: PARTIAL |
694870141 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: NA - COMPONENT ONLY/ 16.12.3s/ 2.3.3.3/ 17.6.4/ 16.12.4/ 2.2.2.5/ 1.3.3.6/ 16.12.03s/ 16.12.01s/ 16.12.04/ 16.12.1s/ 2.2.3.3/ THIRD_PARTY_PRODUCT_SW/ 16.12.1s/ 1.3.3.7/ 1.3.3.9/ 2.3.3.7/ 2.1.2.7/ 2.2.3.6/ 17.06.02 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Resolution Summary
======================
UH-01-CNT-ES01#show mac address-table | count 1/0/48
Number of lines which match regexp = 8641 <<<
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48 | count 1/0/48
Number of lines which match regexp = 1024 <<<<
UH-01-CNT-ES01#
UH-01-CNT-ES01#show device-tracking database interface gigabitEthernet 1/0/48
portDB has 2 entries for interface Gi1/0/48, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.127.229 040e.3cbf.445c Gi1/0/48 1071 0025 1s REACHABLE 312 s(1592 s)
ND FE80::BD38:83C:446E:DA13 040e.3cbf.445c Gi1/0/48 1071 0005 37s REACHABLE 269 s try 0
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int gi1/0/48
Building configuration...
Current configuration : 258 bytes
!
interface GigabitEthernet1/0/48
switchport mode access
device-tracking attach-policy IPDT_POLICY
dot1x timeout tx-period 7
dot1x max-reauth-req 3
source template DefaultWiredDot1xClosedAuth
spanning-tree portfast
spanning-tree bpduguard enable
end
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int vlan 1071
Building configuration...
Current configuration : 377 bytes
!
interface Vlan1071
description Configured from Cisco DNA-Center
mac-address 0000.0c9f.f48e
vrf forwarding admin_VN
ip address 172.27.64.1 255.255.192.0
ip helper-address 172.19.208.10
ip helper-address 172.19.50.39
ip helper-address 172.19.215.140
no ip redirects
ip route-cache same-interface
no lisp mobility liveness test
lisp mobility vl_admin_wired-IPV4
end
UH-01-CNT-ES01#sh device-sensor cache in gi1/0/48
Device: 040e.3cbf.445c on port GigabitEthernet1/0/48
----------------------------------------------------------------------------
Proto Type:Name Len Value Text
DHCP 55:parameter-request-list 16 37 0E 01 03 06 0F 1F 21 2B 7......!+
2C 2E 2F 77 79 F9 FC ,./wyy.
DHCP 60:class-identifier 10 3C 08 4D 53 46 54 20 35 2E <.MSFT 5.
30 0
DHCP 12:host-name 16 0C 0E 75 63 69 2D 74 63 6B ..uci-tck
68 70 65 6C 69 74 65 hpelite
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48
Summary:
MAC_Address Port_Id Profile Name Device Name
==========================================================================
0000.0000.0001 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0022 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0101 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0104 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0107 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.010b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0111 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0118 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0119 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.011a GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0122 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0123 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0129 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.012d GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0135 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013c GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0142 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0147 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.014f GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0154 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0163 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.016b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0171 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
As with the recent occurrence – we don’t have output of the MAC’s incrementing and the packet capture doesn’t show those macs as stated above.
USC-02-CNT-ES01#
071 feed.8542.9fc2 STATIC Gi3/0/17
1071 fef4.2a1b.bd4e STATIC Gi3/0/17
Total Mac Addresses for this criterion: 3296 <<<<
USC-02-CNT-ES01#
USC-02-CNT-ES01#show device-tracking database interface gigabitEthernet 3/0/17
portDB has 2 entries for interface Gi3/0/17, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.112.101 b445.066a.b212 Gi3/0/17 1071 0025 23s REACHABLE 286 s try 0(1004 s)
ND FE80::9353:5FED:DD96:E6B2 b445.066a.b212 Gi3/0/17 1071 0005 19s REACHABLE 283 s
USC-02-CNT-ES01#show ip dhcp snooping binding interface gigabitEthernet 3/0/17
MacAddress IpAddress Lease(sec) Type VLAN Interface
------------------ --------------- ---------- ------------- ---- --------------------
B4:45:06:6A:B2:12 172.27.112.101 987 dhcp-snooping 1071 GigabitEthernet3/0/17
Total number of bindings: 1
1) This could be either no bogus mac addresses being sent from PC to switch during capture
2) To rule this out, when the issue re-occurs, please perform a simultaneous capture on the switch and PC.
a. Run the mac count command on the switch multiple times to show the mac addresses are incrementing.
b. As workaround we tested by setting a client connected interface on one the switch from mult-auth to single-auth
i. You may follow this during the next occurrence of the mac increments are spiking the CPU.
Techno-L3-Test#show authentication sessions interface gigabitEthernet 1/0/9 details
<SNIP>
Oper host mode: multi-auth <<<<<<<
<SNIP>
Techno-L3-Test(config)#int gi1/0/9
Techno-L3-Test(config-if)#shut
Techno-L3-Test(config-if)#access-session host-mode single-host <<<<
Techno-L3-Test(config-if)#no shut
Techno-L3-Test(config-if)#end
Techno-L3-Test#show mac address-table interface gigabitEthernet 1/0/9
<SNIP>
Oper host mode: single-host <<<<<<
<SNIP>
Customer requested to close this SR.
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE C9300 - MAC Flooding from specific port
SDA FE C9300 - MAC Flooding from specific port
Resolution Summary
======================
UH-01-CNT-ES01#show mac address-table | count 1/0/48
Number of lines which match regexp = 8641 <<<
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48 | count 1/0/48
Number of lines which match regexp = 1024 <<<<
UH-01-CNT-ES01#
UH-01-CNT-ES01#show device-tracking database interface gigabitEthernet 1/0/48
portDB has 2 entries for interface Gi1/0/48, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.127.229 040e.3cbf.445c Gi1/0/48 1071 0025 1s REACHABLE 312 s(1592 s)
ND FE80::BD38:83C:446E:DA13 040e.3cbf.445c Gi1/0/48 1071 0005 37s REACHABLE 269 s try 0
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int gi1/0/48
Building configuration...
Current configuration : 258 bytes
!
interface GigabitEthernet1/0/48
switchport mode access
device-tracking attach-policy IPDT_POLICY
dot1x timeout tx-period 7
dot1x max-reauth-req 3
source template DefaultWiredDot1xClosedAuth
spanning-tree portfast
spanning-tree bpduguard enable
end
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int vlan 1071
Building configuration...
Current configuration : 377 bytes
!
interface Vlan1071
description Configured from Cisco DNA-Center
mac-address 0000.0c9f.f48e
vrf forwarding admin_VN
ip address 172.27.64.1 255.255.192.0
ip helper-address 172.19.208.10
ip helper-address 172.19.50.39
ip helper-address 172.19.215.140
no ip redirects
ip route-cache same-interface
no lisp mobility liveness test
lisp mobility vl_admin_wired-IPV4
end
UH-01-CNT-ES01#sh device-sensor cache in gi1/0/48
Device: 040e.3cbf.445c on port GigabitEthernet1/0/48
----------------------------------------------------------------------------
Proto Type:Name Len Value Text
DHCP 55:parameter-request-list 16 37 0E 01 03 06 0F 1F 21 2B 7......!+
2C 2E 2F 77 79 F9 FC ,./wyy.
DHCP 60:class-identifier 10 3C 08 4D 53 46 54 20 35 2E <.MSFT 5.
30 0
DHCP 12:host-name 16 0C 0E 75 63 69 2D 74 63 6B ..uci-tck
68 70 65 6C 69 74 65 hpelite
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48
Summary:
MAC_Address Port_Id Profile Name Device Name
==========================================================================
0000.0000.0001 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0022 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0101 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0104 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0107 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.010b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0111 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0118 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0119 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.011a GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0122 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0123 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0129 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.012d GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0135 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013c GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0142 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0147 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.014f GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0154 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0163 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.016b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0171 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
As with the recent occurrence – we don’t have output of the MAC’s incrementing and the packet capture doesn’t show those macs as stated above.
USC-02-CNT-ES01#
071 feed.8542.9fc2 STATIC Gi3/0/17
1071 fef4.2a1b.bd4e STATIC Gi3/0/17
Total Mac Addresses for this criterion: 3296 <<<<
USC-02-CNT-ES01#
USC-02-CNT-ES01#show device-tracking database interface gigabitEthernet 3/0/17
portDB has 2 entries for interface Gi3/0/17, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.112.101 b445.066a.b212 Gi3/0/17 1071 0025 23s REACHABLE 286 s try 0(1004 s)
ND FE80::9353:5FED:DD96:E6B2 b445.066a.b212 Gi3/0/17 1071 0005 19s REACHABLE 283 s
USC-02-CNT-ES01#show ip dhcp snooping binding interface gigabitEthernet 3/0/17
MacAddress IpAddress Lease(sec) Type VLAN Interface
------------------ --------------- ---------- ------------- ---- --------------------
B4:45:06:6A:B2:12 172.27.112.101 987 dhcp-snooping 1071 GigabitEthernet3/0/17
Total number of bindings: 1
1) This could be either no bogus mac addresses being sent from PC to switch during capture
2) To rule this out, when the issue re-occurs, please perform a simultaneous capture on the switch and PC.
a. Run the mac count command on the switch multiple times to show the mac addresses are incrementing.
b. As workaround we tested by setting a client connected interface on one the switch from mult-auth to single-auth
i. You may follow this during the next occurrence of the mac increments are spiking the CPU.
Techno-L3-Test#show authentication sessions interface gigabitEthernet 1/0/9 details
<SNIP>
Oper host mode: multi-auth <<<<<<<
<SNIP>
Techno-L3-Test(config)#int gi1/0/9
Techno-L3-Test(config-if)#shut
Techno-L3-Test(config-if)#access-session host-mode single-host <<<<
Techno-L3-Test(config-if)#no shut
Techno-L3-Test(config-if)#end
Techno-L3-Test#show mac address-table interface gigabitEthernet 1/0/9
<SNIP>
Oper host mode: single-host <<<<<<
<SNIP>
Customer requested to close this SR. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: DN2-HW-APL-XL/ ASR1009-X/ C9300-48U/ DN1-HW-APL/ C9500-48Y4C/ THIRD_PARTY_PRODUCT_HW/ C9300-48U-A/ ASR1002-HX Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE C9300 - MAC Flooding from specific port
SDA FE C9300 - MAC Flooding from specific port
Resolution Summary
======================
UH-01-CNT-ES01#show mac address-table | count 1/0/48
Number of lines which match regexp = 8641 <<<
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48 | count 1/0/48
Number of lines which match regexp = 1024 <<<<
UH-01-CNT-ES01#
UH-01-CNT-ES01#show device-tracking database interface gigabitEthernet 1/0/48
portDB has 2 entries for interface Gi1/0/48, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.127.229 040e.3cbf.445c Gi1/0/48 1071 0025 1s REACHABLE 312 s(1592 s)
ND FE80::BD38:83C:446E:DA13 040e.3cbf.445c Gi1/0/48 1071 0005 37s REACHABLE 269 s try 0
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int gi1/0/48
Building configuration...
Current configuration : 258 bytes
!
interface GigabitEthernet1/0/48
switchport mode access
device-tracking attach-policy IPDT_POLICY
dot1x timeout tx-period 7
dot1x max-reauth-req 3
source template DefaultWiredDot1xClosedAuth
spanning-tree portfast
spanning-tree bpduguard enable
end
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int vlan 1071
Building configuration...
Current configuration : 377 bytes
!
interface Vlan1071
description Configured from Cisco DNA-Center
mac-address 0000.0c9f.f48e
vrf forwarding admin_VN
ip address 172.27.64.1 255.255.192.0
ip helper-address 172.19.208.10
ip helper-address 172.19.50.39
ip helper-address 172.19.215.140
no ip redirects
ip route-cache same-interface
no lisp mobility liveness test
lisp mobility vl_admin_wired-IPV4
end
UH-01-CNT-ES01#sh device-sensor cache in gi1/0/48
Device: 040e.3cbf.445c on port GigabitEthernet1/0/48
----------------------------------------------------------------------------
Proto Type:Name Len Value Text
DHCP 55:parameter-request-list 16 37 0E 01 03 06 0F 1F 21 2B 7......!+
2C 2E 2F 77 79 F9 FC ,./wyy.
DHCP 60:class-identifier 10 3C 08 4D 53 46 54 20 35 2E <.MSFT 5.
30 0
DHCP 12:host-name 16 0C 0E 75 63 69 2D 74 63 6B ..uci-tck
68 70 65 6C 69 74 65 hpelite
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48
Summary:
MAC_Address Port_Id Profile Name Device Name
==========================================================================
0000.0000.0001 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0022 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0101 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0104 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0107 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.010b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0111 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0118 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0119 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.011a GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0122 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0123 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0129 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.012d GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0135 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013c GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0142 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0147 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.014f GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0154 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0163 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.016b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0171 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
As with the recent occurrence – we don’t have output of the MAC’s incrementing and the packet capture doesn’t show those macs as stated above.
USC-02-CNT-ES01#
071 feed.8542.9fc2 STATIC Gi3/0/17
1071 fef4.2a1b.bd4e STATIC Gi3/0/17
Total Mac Addresses for this criterion: 3296 <<<<
USC-02-CNT-ES01#
USC-02-CNT-ES01#show device-tracking database interface gigabitEthernet 3/0/17
portDB has 2 entries for interface Gi3/0/17, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.112.101 b445.066a.b212 Gi3/0/17 1071 0025 23s REACHABLE 286 s try 0(1004 s)
ND FE80::9353:5FED:DD96:E6B2 b445.066a.b212 Gi3/0/17 1071 0005 19s REACHABLE 283 s
USC-02-CNT-ES01#show ip dhcp snooping binding interface gigabitEthernet 3/0/17
MacAddress IpAddress Lease(sec) Type VLAN Interface
------------------ --------------- ---------- ------------- ---- --------------------
B4:45:06:6A:B2:12 172.27.112.101 987 dhcp-snooping 1071 GigabitEthernet3/0/17
Total number of bindings: 1
1) This could be either no bogus mac addresses being sent from PC to switch during capture
2) To rule this out, when the issue re-occurs, please perform a simultaneous capture on the switch and PC.
a. Run the mac count command on the switch multiple times to show the mac addresses are incrementing.
b. As workaround we tested by setting a client connected interface on one the switch from mult-auth to single-auth
i. You may follow this during the next occurrence of the mac increments are spiking the CPU.
Techno-L3-Test#show authentication sessions interface gigabitEthernet 1/0/9 details
<SNIP>
Oper host mode: multi-auth <<<<<<<
<SNIP>
Techno-L3-Test(config)#int gi1/0/9
Techno-L3-Test(config-if)#shut
Techno-L3-Test(config-if)#access-session host-mode single-host <<<<
Techno-L3-Test(config-if)#no shut
Techno-L3-Test(config-if)#end
Techno-L3-Test#show mac address-table interface gigabitEthernet 1/0/9
<SNIP>
Oper host mode: single-host <<<<<<
<SNIP>
Customer requested to close this SR. | Technology: Cisco DNA Center - On-Prem
Subtechnology: Cisco Software-Defined Access (SDA Wired)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: C9300
Software Version: N/A
Router/Node Name: N/A
Problem Details: SDA FE C9300 - MAC Flooding from specific port | SDA FE C9300 - MAC Flooding from specific port | Resolution Summary
======================
UH-01-CNT-ES01#show mac address-table | count 1/0/48
Number of lines which match regexp = 8641 <<<
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48 | count 1/0/48
Number of lines which match regexp = 1024 <<<<
UH-01-CNT-ES01#
UH-01-CNT-ES01#show device-tracking database interface gigabitEthernet 1/0/48
portDB has 2 entries for interface Gi1/0/48, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.127.229 040e.3cbf.445c Gi1/0/48 1071 0025 1s REACHABLE 312 s(1592 s)
ND FE80::BD38:83C:446E:DA13 040e.3cbf.445c Gi1/0/48 1071 0005 37s REACHABLE 269 s try 0
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int gi1/0/48
Building configuration...
Current configuration : 258 bytes
!
interface GigabitEthernet1/0/48
switchport mode access
device-tracking attach-policy IPDT_POLICY
dot1x timeout tx-period 7
dot1x max-reauth-req 3
source template DefaultWiredDot1xClosedAuth
spanning-tree portfast
spanning-tree bpduguard enable
end
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh run int vlan 1071
Building configuration...
Current configuration : 377 bytes
!
interface Vlan1071
description Configured from Cisco DNA-Center
mac-address 0000.0c9f.f48e
vrf forwarding admin_VN
ip address 172.27.64.1 255.255.192.0
ip helper-address 172.19.208.10
ip helper-address 172.19.50.39
ip helper-address 172.19.215.140
no ip redirects
ip route-cache same-interface
no lisp mobility liveness test
lisp mobility vl_admin_wired-IPV4
end
UH-01-CNT-ES01#sh device-sensor cache in gi1/0/48
Device: 040e.3cbf.445c on port GigabitEthernet1/0/48
----------------------------------------------------------------------------
Proto Type:Name Len Value Text
DHCP 55:parameter-request-list 16 37 0E 01 03 06 0F 1F 21 2B 7......!+
2C 2E 2F 77 79 F9 FC ,./wyy.
DHCP 60:class-identifier 10 3C 08 4D 53 46 54 20 35 2E <.MSFT 5.
30 0
DHCP 12:host-name 16 0C 0E 75 63 69 2D 74 63 6B ..uci-tck
68 70 65 6C 69 74 65 hpelite
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#
UH-01-CNT-ES01#sh devi classifier att in gi1/0/48
Summary:
MAC_Address Port_Id Profile Name Device Name
==========================================================================
0000.0000.0001 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0022 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0101 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0104 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0107 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.010b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0111 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0118 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0119 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.011a GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0122 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0123 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0129 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.012d GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0135 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.013c GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0142 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0147 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.014f GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0154 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0163 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.016b GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
0000.0000.0171 GigabitEthernet1/0/48 Un-Classified Device XEROX CORPORATION
As with the recent occurrence – we don’t have output of the MAC’s incrementing and the packet capture doesn’t show those macs as stated above.
USC-02-CNT-ES01#
071 feed.8542.9fc2 STATIC Gi3/0/17
1071 fef4.2a1b.bd4e STATIC Gi3/0/17
Total Mac Addresses for this criterion: 3296 <<<<
USC-02-CNT-ES01#
USC-02-CNT-ES01#show device-tracking database interface gigabitEthernet 3/0/17
portDB has 2 entries for interface Gi3/0/17, 2 dynamic
Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created
Preflevel flags (prlvl):
0001:MAC and LLA match 0002:Orig trunk 0004:Orig access
0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned
0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned
Network Layer Address Link Layer Address Interface vlan prlvl age state Time left
DH4 172.27.112.101 b445.066a.b212 Gi3/0/17 1071 0025 23s REACHABLE 286 s try 0(1004 s)
ND FE80::9353:5FED:DD96:E6B2 b445.066a.b212 Gi3/0/17 1071 0005 19s REACHABLE 283 s
USC-02-CNT-ES01#show ip dhcp snooping binding interface gigabitEthernet 3/0/17
MacAddress IpAddress Lease(sec) Type VLAN Interface
------------------ --------------- ---------- ------------- ---- --------------------
B4:45:06:6A:B2:12 172.27.112.101 987 dhcp-snooping 1071 GigabitEthernet3/0/17
Total number of bindings: 1
1) This could be either no bogus mac addresses being sent from PC to switch during capture
2) To rule this out, when the issue re-occurs, please perform a simultaneous capture on the switch and PC.
a. Run the mac count command on the switch multiple times to show the mac addresses are incrementing.
b. As workaround we tested by setting a client connected interface on one the switch from mult-auth to single-auth
i. You may follow this during the next occurrence of the mac increments are spiking the CPU.
Techno-L3-Test#show authentication sessions interface gigabitEthernet 1/0/9 details
<SNIP>
Oper host mode: multi-auth <<<<<<<
<SNIP>
Techno-L3-Test(config)#int gi1/0/9
Techno-L3-Test(config-if)#shut
Techno-L3-Test(config-if)#access-session host-mode single-host <<<<
Techno-L3-Test(config-if)#no shut
Techno-L3-Test(config-if)#end
Techno-L3-Test#show mac address-table interface gigabitEthernet 1/0/9
<SNIP>
Oper host mode: single-host <<<<<<
<SNIP>
Customer requested to close this SR. | Problem Described
===================
SDA FE C9300 - MAC Flooding from specific port | C9300-48U-A | 16.12.3s | 16.12.3s | 70.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | C9300 | Cisco DNA Center - On-Prem | Cisco Software-Defined Access (SDA Wired) | 01t1C000004GjbyQAC | Error Messages, Logs, Debugs | Cisco Software-Defined Access (SDA Wired) | Cisco DNA Center - On-Prem | 01t15000005W0LTAA0 | SHERLOCK: PARTIAL |
694498853 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 1/ 8.10.151.0/ 8.10.171.0/ 802.11AC/ 8.5.171.0/ 8.10.183.0/ 8.10.130.0/ 8.10.171.0/ THIRD_PARTY_PRODUCT_SW/ 8.5.135.0/ 8.3.143.0/ NA-CIN_CLOSE_SW/ 8.5.140.0/ 4.0.1a/ WLC CLIENT INTEROP/ 12.0.13/ 8.5.151.0/ 8.4/ 120.13/ 8.5.160.0/ 8.10.151.0/ 8.3.143.0/ 8.3.131.0/ 8.3.150.0/ 8.5.135.0/ 8.5.161.0/ 8.10.185.0/ 8.2.166.0/ 8.5.140.0/ 8.5.151.0/ 8.3.150.0/ 16.12.3s/ WLC RRM/RF/CLEANAIR/ 8.5.151.0/ 8.10.130.0/ NA - COMPONENT ONLY/ 8.10.162.0/ 8.3.140.0/ 8.10.150.0/ 8.10.183.0/ 8.10.161.0/ 8.10.185.0/ 8.5.151.0/ 16.12.4/ 17.3.5b/ 8.10.183.0/ 8.10.171.0/ 8.5.171.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
refer the latest GCI
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC.
Previous case - 694189183
LT19-01-AP10#ping 172.18.240.13
Sending 5, 100-byte ICMP Echos to 172.18.240.13, timeout is 2 seconds
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.576/0.659/0.854 ms
LT19-01-AP10#
(TLDC-WL-WLC01) >grep include LT19-01-AP10 "show ap join stats summary all"
Press any key to continue..
bc:5a:56:f0:c2:60 N A LT19-01-AP10 10.253.179.36 Not Joined
There are 1 lines matching the pattern LT19-01-AP10
(TLDC-WL-WLC01) >
We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC.
Previous case - 694189183
LT19-01-AP10#ping 172.18.240.13
Sending 5, 100-byte ICMP Echos to 172.18.240.13, timeout is 2 seconds
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.576/0.659/0.854 ms
LT19-01-AP10#
(TLDC-WL-WLC01) >grep include LT19-01-AP10 "show ap join stats summary all"
Press any key to continue..
bc:5a:56:f0:c2:60 N A LT19-01-AP10 10.253.179.36 Not Joined
There are 1 lines matching the pattern LT19-01-AP10
(TLDC-WL-WLC01) >
refer the latest GCI | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: AIR-CT8540-1K-K9/ AIR-CT8540-K9/ NA-CIN_CLOSE_HW/ C9120AXI-S/ THIRD_PARTY_PRODUCT_HW/ AIR-CT8540-CA-K9/ AIR-AP2802I-S-K9/ AIR-CT8540-K9Z/ AIR-BZL-C240M4/ DN2-HW-APL-XL/ WLC-AP-T/ AIR-CT8540-SW-8.2 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC.
Previous case - 694189183
LT19-01-AP10#ping 172.18.240.13
Sending 5, 100-byte ICMP Echos to 172.18.240.13, timeout is 2 seconds
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.576/0.659/0.854 ms
LT19-01-AP10#
(TLDC-WL-WLC01) >grep include LT19-01-AP10 "show ap join stats summary all"
Press any key to continue..
bc:5a:56:f0:c2:60 N A LT19-01-AP10 10.253.179.36 Not Joined
There are 1 lines matching the pattern LT19-01-AP10
(TLDC-WL-WLC01) >
We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC.
Previous case - 694189183
LT19-01-AP10#ping 172.18.240.13
Sending 5, 100-byte ICMP Echos to 172.18.240.13, timeout is 2 seconds
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.576/0.659/0.854 ms
LT19-01-AP10#
(TLDC-WL-WLC01) >grep include LT19-01-AP10 "show ap join stats summary all"
Press any key to continue..
bc:5a:56:f0:c2:60 N A LT19-01-AP10 10.253.179.36 Not Joined
There are 1 lines matching the pattern LT19-01-AP10
(TLDC-WL-WLC01) >
refer the latest GCI | Technology: Wireless
Subtechnology: 8540 Series Wireless LAN Controller (AIR-CT8540)
Problem Code: Interoperability
Product: NA
Product Family: AIRCTA2
Software Version: N/A
Router/Node Name: N/A
Problem Details: We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC.
Previous case - 694189183
LT19-01-AP10#ping 172.18.240.13
Sending 5, 100-byte ICMP Echos to 172.18.240.13, timeout is 2 seconds
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.576/0.659/0.854 ms
LT19-01-AP10#
(TLDC-WL-WLC01) >grep include LT19-01-AP10 "show ap join stats summary all"
Press any key to continue..
bc:5a:56:f0:c2:60 N A LT19-01-AP10 10.253.179.36 Not Joined
There are 1 lines matching the pattern LT19-01-AP10
(TLDC-WL-WLC01) > | We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC.
Previous case - 694189183
LT19-01-AP10#ping 172.18.240.13
Sending 5, 100-byte ICMP Echos to 172.18.240.13, timeout is 2 seconds
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.576/0.659/0.854 ms
LT19-01-AP10#
(TLDC-WL-WLC01) >grep include LT19-01-AP10 "show ap join stats summary all"
Press any key to continue..
bc:5a:56:f0:c2:60 N A LT19-01-AP10 10.253.179.36 Not Joined
There are 1 lines matching the pattern LT19-01-AP10
(TLDC-WL-WLC01) > | refer the latest GCI | Problem Details: We are noticing that some 2800 series APs are not able to join the WLC. APs are up and reachable from the network but shows down on the WLC. | AIR-CT8540-K9 | 8.10.185.0 | 8.10.185.0 | 16.0 | 3 | 100.0 | Software Bug | AIRCTA2 | Wireless | 8540 Series Wireless LAN Controller (AIR-CT8540) | 01t6R000007PZHhQAO | Interoperability | 8540 Series Wireless LAN Controller (AIR-CT8540) | Wireless | 01t15000004dDRMAA2 | SHERLOCK: PARTIAL |
694069586 | Question: Which software version is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY software version should be selected from the given software version list: 2.6.0.156/ 2.6.0 Response in this JSON format:
{"software_version": "","explanation": "", "summary": ""}
Closed
Technology: Identity Services Engine (ISE) - 2.6 and Prior
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
We are facing very slowness issue accessing PAN node GUI. Need TAC assistance to investigate on this. I will attach some of show output in case portal. Thanks.
Hi Support,
We are facing very slowness issue accessing PAN node GUI. Need TAC assistance to investigate on this. I will attach some of show output in case portal. Thanks.
Collected Show-tech from CLI.
Device uptime is 225 days.
Observed high load average usage.
Suggested for reloading the device.
Issue resolved after reload, proceeding towards case closure with Vijay's consent. | Question: Which product is principally discussed in these documents?
Answer "NONE" if you cannot find answer in the given documents.
The ONLY product name should be selected from the given product name list: SNS-3595-K9 Response in this JSON format:
{"product_name": "","explanation": "", "summary": ""}
Technology: Identity Services Engine (ISE) - 2.6 and Prior
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
We are facing very slowness issue accessing PAN node GUI. Need TAC assistance to investigate on this. I will attach some of show output in case portal. Thanks.
Hi Support,
We are facing very slowness issue accessing PAN node GUI. Need TAC assistance to investigate on this. I will attach some of show output in case portal. Thanks.
Collected Show-tech from CLI.
Device uptime is 225 days.
Observed high load average usage.
Suggested for reloading the device.
Issue resolved after reload, proceeding towards case closure with Vijay's consent. | Technology: Identity Services Engine (ISE) - 2.6 and Prior
Subtechnology: ISE Performance (High CPU / Memory / IO / GUI Slowness)
Problem Code: Error Messages, Logs, Debugs
Product: NA
Product Family: CISE
Software Version: N/A
Router/Node Name: N/A
Problem Details: Hi Support,
We are facing very slowness issue accessing PAN node GUI. Need TAC assistance to investigate on this. I will attach some of show output in case portal. Thanks. | Hi Support,
We are facing very slowness issue accessing PAN node GUI. Need TAC assistance to investigate on this. I will attach some of show output in case portal. Thanks. | Collected Show-tech from CLI.
Device uptime is 225 days.
Observed high load average usage.
Suggested for reloading the device.
Issue resolved after reload, proceeding towards case closure with Vijay's consent. | ISE GUI slowness issue. | SNS-3595-K9 | 2.6.0 | 2.6.0 | 85.0 | 3 | 100.0 | Configuration Assistance (process not intuitive, too complex, inconsistent...) | CISE | Identity Services Engine (ISE) - 2.6 and Prior | ISE Performance (High CPU / Memory / IO / GUI Slowness) | 01t1C000006XIP9QAO | Error Messages, Logs, Debugs | ISE Performance (High CPU / Memory / IO / GUI Slowness) | Identity Services Engine (ISE) - 2.6 and Prior | 01tA0000002qmXqIAI | nan |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.