Re: [c-nsp] Nexus debug output
Works like a chm! Thanks Tim! -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: Tuesday, January 03, 2012 5:54 PM To: b...@bobsinclair.net; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] Nexus debug output Hi Bob, Try using the "debug-filter" options - eg, if you're debugging ospf in vrf foo: debug-filter ip ospf vrf foo debug ip ospf adj The debug-filters are really pretty powerful, it helps you narrow down the debugs to just what you're looking for. Filters are available for most L3 protocols & infrastructure. Hope that helps, Tim At 02:37 PM 1/3/2012, Bob Sinclair stated: >Thanks Tim! That was it. Huge help! > >I can also now debug activity in a non-default VDC, but only for >activity on default vrf interfaces. That seems like a real limitation, >but I cannot find any vrf keywords on debug commands. I also tried >changing routing-context to the non-default vrf, but that did not help. >Any way to debug activity in the non-default vrfs? For example, debug ip ospf events? > >Thanks! > >-Original Message- >From: Tim Stevenson >[<mailto:tstev...@cisco.com>mailto:tstev...@cisco.com] >Sent: Tuesday, January 03, 2012 4:32 PM >To: b...@bobsinclair.net; cisco-nsp@puck.nether.net >Subject: Re: [c-nsp] Nexus debug output > >Hi Bob, > >What are you pinging? I assume it's something out the mgmt0 interface. >In this case, debug ip packet detail will not generate any output - >many debugs are applicable to the inband interface only (as in this case). > >One alternative if you want to capture mgmt0 traffic is to use the >ethanalyzer, eg something like: > >ethan local int mgmt capture-filter "icmp" limit-captured-frames 20 >detail > bootflash:foo > >etc. > >Or, if you're just trying to see how the debug logfile works, ping >something connected to something other than mgmt0. > >Hope that helps, >Tim > > >At 12:46 PM 1/3/2012, Bob Sinclair stated: > >Hi, > > > > > > > >I am not able to see any debug output on my Nexus 7K. I am logged > >into the default VDC as netadmin. I have set up a debug logfile. > >But when, for example, I turn on 'debug ip packet' then try a ping I > >get nothing from 'show debug logfile mydebugs' I have searched > >command references, config guides and googled, to no avail. > > > > > > > >Any help would be most appreciated. > > > > > > > >C1-Default# sh debug > > > > > >Output forwarded to file mydebugs (size: 4194304 bytes) > > > > > >Debug level is set to Minor(1) > > > > > > default for new sessions logging level: 3 > > > > > > > > > > > >debug ip packet > > > > > >`end` > > > > > >C1-Default# sh debug logfile mydebugs > > > > > >C1-Default# > > > >___ > >cisco-nsp mailing list cisco-nsp@puck.nether.net > ><https://puck.nether.net/mailman/listinfo/cisco-nsp>https://puck.ne > ther.net/mailman/listinfo/cisco-nsp > >archive at > <http://puck.nether.net/pipermail/cisco-nsp/>http://puck.nether.net/pi > permail/cisco-nsp/ > > > > >Tim Stevenson, tstev...@cisco.com >Routing & Switching CCIE #5561 >Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - ><http://www.cisco.com>http://www.cisco.com IP Phone: 408-526-6759 > >The contents of this message may be *Cisco Confidential* and are >intended for the specified recipients only. > > > > >- >No virus found in this message. >Checked by AVG - www.avg.com >Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: >01/03/12 > >- >No virus found in this message. >Checked by AVG - www.avg.com >Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: >01/03/12 >- >No virus found in this message. >Checked by AVG - www.avg.com >Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: >01/03/12 >- >No virus found in this message. >Checked by AVG - www.avg.com >Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: >01/03/12 Tim Stevenson, tstev...@cisco.com Routing & Switching CCIE #5561 Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - http://www.cisco.com IP Phone: 408-526-6759 The contents of this message may be *Cisco Confidential* and are intended for the specified recipients only. - No virus found in this message.
Re: [c-nsp] Nexus debug output
Hi Bob, Try using the "debug-filter" options - eg, if you're debugging ospf in vrf foo: debug-filter ip ospf vrf foo debug ip ospf adj The debug-filters are really pretty powerful, it helps you narrow down the debugs to just what you're looking for. Filters are available for most L3 protocols & infrastructure. Hope that helps, Tim At 02:37 PM 1/3/2012, Bob Sinclair stated: Thanks Tim! That was it. Huge help! I can also now debug activity in a non-default VDC, but only for activity on default vrf interfaces. That seems like a real limitation, but I cannot find any vrf keywords on debug commands. I also tried changing routing-context to the non-default vrf, but that did not help. Any way to debug activity in the non-default vrfs? For example, debug ip ospf events? Thanks! -Original Message- From: Tim Stevenson [<mailto:tstev...@cisco.com>mailto:tstev...@cisco.com] Sent: Tuesday, January 03, 2012 4:32 PM To: b...@bobsinclair.net; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus debug output Hi Bob, What are you pinging? I assume it's something out the mgmt0 interface. In this case, debug ip packet detail will not generate any output - many debugs are applicable to the inband interface only (as in this case). One alternative if you want to capture mgmt0 traffic is to use the ethanalyzer, eg something like: ethan local int mgmt capture-filter "icmp" limit-captured-frames 20 detail > bootflash:foo etc. Or, if you're just trying to see how the debug logfile works, ping something connected to something other than mgmt0. Hope that helps, Tim At 12:46 PM 1/3/2012, Bob Sinclair stated: >Hi, > > > >I am not able to see any debug output on my Nexus 7K. I am logged into >the default VDC as netadmin. I have set up a debug logfile. But when, >for example, I turn on 'debug ip packet' then try a ping I get nothing >from 'show debug logfile mydebugs' I have searched command references, >config guides and googled, to no avail. > > > >Any help would be most appreciated. > > > >C1-Default# sh debug > > >Output forwarded to file mydebugs (size: 4194304 bytes) > > >Debug level is set to Minor(1) > > > default for new sessions logging level: 3 > > > > > >debug ip packet > > >`end` > > >C1-Default# sh debug logfile mydebugs > > >C1-Default# > >___ >cisco-nsp mailing list cisco-nsp@puck.nether.net ><https://puck.nether.net/mailman/listinfo/cisco-nsp>https://puck.ne ther.net/mailman/listinfo/cisco-nsp >archive at <http://puck.nether.net/pipermail/cisco-nsp/>http://puck.nether.net/pipermail/cisco-nsp/ Tim Stevenson, tstev...@cisco.com Routing & Switching CCIE #5561 Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - <http://www.cisco.com>http://www.cisco.com IP Phone: 408-526-6759 The contents of this message may be *Cisco Confidential* and are intended for the specified recipients only. - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 Tim Stevenson, tstev...@cisco.com Routing & Switching CCIE #5561 Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - http://www.cisco.com IP Phone: 408-526-6759 The contents of this message may be *Cisco Confidential* and are intended for the specified recipients only. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Nexus debug output
Thanks Tim! That was it. Huge help! I can also now debug activity in a non-default VDC, but only for activity on default vrf interfaces. That seems like a real limitation, but I cannot find any vrf keywords on debug commands. I also tried changing routing-context to the non-default vrf, but that did not help. Any way to debug activity in the non-default vrfs? For example, debug ip ospf events? Thanks! -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: Tuesday, January 03, 2012 4:32 PM To: b...@bobsinclair.net; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus debug output Hi Bob, What are you pinging? I assume it's something out the mgmt0 interface. In this case, debug ip packet detail will not generate any output - many debugs are applicable to the inband interface only (as in this case). One alternative if you want to capture mgmt0 traffic is to use the ethanalyzer, eg something like: ethan local int mgmt capture-filter "icmp" limit-captured-frames 20 detail > bootflash:foo etc. Or, if you're just trying to see how the debug logfile works, ping something connected to something other than mgmt0. Hope that helps, Tim At 12:46 PM 1/3/2012, Bob Sinclair stated: >Hi, > > > >I am not able to see any debug output on my Nexus 7K. I am logged into >the default VDC as netadmin. I have set up a debug logfile. But when, >for example, I turn on 'debug ip packet' then try a ping I get nothing >from 'show debug logfile mydebugs' I have searched command references, >config guides and googled, to no avail. > > > >Any help would be most appreciated. > > > >C1-Default# sh debug > > >Output forwarded to file mydebugs (size: 4194304 bytes) > > >Debug level is set to Minor(1) > > > default for new sessions logging level: 3 > > > > > >debug ip packet > > >`end` > > >C1-Default# sh debug logfile mydebugs > > >C1-Default# > >___ >cisco-nsp mailing list cisco-nsp@puck.nether.net >https://puck.nether.net/mailman/listinfo/cisco-nsp >archive at http://puck.nether.net/pipermail/cisco-nsp/ Tim Stevenson, tstev...@cisco.com Routing & Switching CCIE #5561 Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - http://www.cisco.com IP Phone: 408-526-6759 The contents of this message may be *Cisco Confidential* and are intended for the specified recipients only. - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4720 - Release Date: 01/03/12 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Nexus debug output
Hi Bob, What are you pinging? I assume it's something out the mgmt0 interface. In this case, debug ip packet detail will not generate any output - many debugs are applicable to the inband interface only (as in this case). One alternative if you want to capture mgmt0 traffic is to use the ethanalyzer, eg something like: ethan local int mgmt capture-filter "icmp" limit-captured-frames 20 detail > bootflash:foo etc. Or, if you're just trying to see how the debug logfile works, ping something connected to something other than mgmt0. Hope that helps, Tim At 12:46 PM 1/3/2012, Bob Sinclair stated: Hi, I am not able to see any debug output on my Nexus 7K. I am logged into the default VDC as netadmin. I have set up a debug logfile. But when, for example, I turn on 'debug ip packet' then try a ping I get nothing from 'show debug logfile mydebugs' I have searched command references, config guides and googled, to no avail. Any help would be most appreciated. C1-Default# sh debug Output forwarded to file mydebugs (size: 4194304 bytes) Debug level is set to Minor(1) default for new sessions logging level: 3 debug ip packet `end` C1-Default# sh debug logfile mydebugs C1-Default# ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ Tim Stevenson, tstev...@cisco.com Routing & Switching CCIE #5561 Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - http://www.cisco.com IP Phone: 408-526-6759 The contents of this message may be *Cisco Confidential* and are intended for the specified recipients only. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Nexus debug output
Hi, I am not able to see any debug output on my Nexus 7K. I am logged into the default VDC as netadmin. I have set up a debug logfile. But when, for example, I turn on 'debug ip packet' then try a ping I get nothing from 'show debug logfile mydebugs' I have searched command references, config guides and googled, to no avail. Any help would be most appreciated. C1-Default# sh debug Output forwarded to file mydebugs (size: 4194304 bytes) Debug level is set to Minor(1) default for new sessions logging level: 3 debug ip packet `end` C1-Default# sh debug logfile mydebugs C1-Default# ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
