12-01-2020 10:27 AM - edited 12-02-2020 09:07 AM
Take the opportunity to reach out to our expert and discuss best practices regarding on how to troubleshoot a live network and identify the root cause easily. Learn more about Serviceability and how to provide full access to the administrator in order to allow a total control. You can post questions regarding Polaris IOS-XE 17.3.1 and Catalyst 9x00 series features combined to 5G adoption or WiFI6 as well. Join the discusson and ask Aaron!
To participate in this event, please use the button below to ask your questions
Ask questions from Tuesday 1st to Friday 11th of December, 2020
12-02-2020 09:06 AM - edited 12-02-2020 09:07 AM
Hi Aaron ( @acespede )
Thanks for providing such a great session, we have learned lots.
Please help us to answer the following question from the live session:
12-08-2020 03:35 PM
Hello,
I'm not aware if IOS XR has something similar to the serviceability features but I know about the i.e XR embedded packet tracer tool, here you can see information about that:
https://xrdocs.io/asr9k//tutorials/xr-embedded-packet-tracer/
Thank you!
Aarón Céspedes V.
12-02-2020 09:24 AM
Hi Aaron,
The webcast was great, thank you for the recording!
I have an additional question, could a SPF/PSV or NETDR CPU capture cause high CPU utilization/crash of the switch?
Thank you
12-06-2020 07:00 AM
Hello jossanc3,
One of the goals with the serviceability features is that we can use them under live environments hence we expect these group of features to work as designed without causing a major outage to the switch where we're using them.
Now, for SPF support on C9200/C9500H&C9600 (added in 17.2); we identified some issues when using this feature (affecting 17.3.1) but we managed to fix them and I've tested it with C9200/C9500H using 17.3.2a (some scenarios like tracing ICMP, L2 mcast flow) and is working just fine.
Last but not least, we always encourage our customers to use the features and if they identify problems/misbehavior, etc. we can have a Cisco TAC case open in order to further isolate the fault and fix it in order to continue using the features.
Thank you!
Aarón Céspedes V.
12-04-2020 03:21 PM
Thank you for the opportunity to post some additional questions. I would like to know if you are you constantly improving the show tech-support packages (adding additional CLIs)?
Daniel
12-06-2020 06:47 AM
Hello Dani Ma,
Regarding your question about improving the show tech-support packages for the different features; yes, often there are continued improvements after the initial release.
Thank you!
Aarón Céspedes V.
12-08-2020 02:23 PM
Hello,
By collecting the trace archive file, could we create a high CPU event or anything similar?
Thanks,
John
12-08-2020 03:21 PM
Hello John,
Thank you for your question!
No, collecting the trace file should not cause a high CPU event or anything similar.
Aarón Céspedes V.
12-10-2020 11:31 PM
After setting the fed punt trace to debug or verbose level, is there a way to move it back to default?
12-11-2020 05:19 PM
Hi Jessica,
Yes, we can move the traces to different levels and then back to default, i.e.
C9500-32C_SVL#set platform software trace fed swi active punt debug
C9500-32C_SVL#sho platform software trace level fed swi active | in punt
punt Debug
C9500-32C_SVL#set plat sof tra fed swi active punt notice
C9500-32C_SVL#sho platform software trace level fed swi active | in punt
punt Notice
C9500-32C_SVL#
Thank you.
Aaron Cespedes V.
12-11-2020 03:51 PM
12-11-2020 05:15 PM
Hello Alain,
Best practice is to move it back to default (notice) and avoid having the trace logs to be flooded with not required data.
Thank you.
Aaron Cespedes V.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide