Catalyst 6500 does not display debugging event

Answered Question
Feb 5th, 2010
User Badges:

Dear sir.

I am using Catalyst 6500 in the test.


I wanted to examine details of the event, STP Debug was made Enable.


>logging buffer debug

>logging console debug

>debug spanning-tree event ( or ALL )


However, nothing is displayed.

nothing also even in the buffer.

(There is no problem in 2960/3750.)


Besides, should I set it?


※Referred page

http://www.cisco.com/en/US/customer/tech/tk389/tk621/technologies_tech_note09186a00800951ac.shtml#connectiv

https://supportforums.cisco.com/docs/DOC-5003


※Version and more

12.2.33.SHX4

(Does not use the VLAN Bridge(Cat3750:Fallback bridge))

(all port VLAN 1)

(Enable STP (Priority 4096) of VLAN 1)

Correct Answer by Ganesh Hariharan about 7 years 5 months ago

Hi,


Thanks comment.


Three machines are prepared and it connects it with the triangle.

It is a general composition.

Certainly, the state of STP can be seen from the command and the monitor port.


I want to know whether the Debug command can be used after it is understood.

It is a confirmation for that.
This is not guest's environment.


The availability of CPU goes up when executing it in guest's environment, and the possibility that the system hangs up is understood.


The Debug command was able to be used in old Version.
Moreover, it is possible to use it for HybridOS.


Present NativeOS alone cannot be used.


>debug spanning-tree all


Even if this is input, nothing is displayed as for Catalyst6500 alone.


but,


>debug ip packet


The log comes out from this command.


Will this be a specification?
Or, is the command insufficient?


Hi,


For native ios check out the below link for spanning  tree debug command usage hope that clear you query


http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a00800b1500.shtml


and debug ip packet Don't try it! This command can actually bring an entire production router/switch  down.


However, when used properly, this command can be a very helpful. For example, you can use debug ip packet with an ACL.


If you want to view only traffic from host 1.1.1.1 to host 2.2.2.2 that was using port 80. Being very careful, you could see it using debug ip packet and an ACL.


AS400(config)# access-list 101 deny ip host 1.1.1.1 host 2.2.2.2 eq 80
AS400(config)# exit
AS400# debug ip packet detail 101
IP packet debugging is on (detailed) for access list 101
AS400#


In this example, you have a rudimentary packet sniffer that gives information on TCP port number (src/dest), sequence number, ack, window, and flag information. In addition, this is for the entire device—not just a single interface.


Hope to help


Ganesh.H

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Ganesh Hariharan Sat, 02/06/2010 - 02:38
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Member's Choice, February 2016

Dear sir.

I am using Catalyst 6500 in the test.


I wanted to examine details of the event, STP Debug was made Enable.


>logging buffer debug

>logging console debug

>debug spanning-tree event ( or ALL )


However, nothing is displayed.

nothing also even in the buffer.

(There is no problem in 2960/3750.)


Besides, should I set it?


※Referred page

http://www.cisco.com/en/US/customer/tech/tk389/tk621/technologies_tech_note09186a00800951ac.shtml#connectiv

https://supportforums.cisco.com/docs/DOC-5003


※Version and more

12.2.33.SHX4

(Does not use the VLAN Bridge(Cat3750:Fallback bridge))

(all port VLAN 1)

(Enable STP (Priority 4096) of VLAN 1)

Hi,


Genrally the command mentioned will give you the detail of all stp events happening the switch with respect to vlans,Are you using a single switch are some other switch also connected with cisco 6500 switch.


if another switch is connected just shutdown one port in in another switch which is connected to uplink to core switch then you can see stp events in the primary switch.


and genrall recommendation says you should not enable debugging in switches or routers unless there is some criticallty or need to troubleshoot a problem.


Hope to help


Ganesh.H

ataro Sat, 02/06/2010 - 03:38
User Badges:

Hi,


Thanks comment.


Three machines are prepared and it connects it with the triangle.

It is a general composition.

Certainly, the state of STP can be seen from the command and the monitor port.


I want to know whether the Debug command can be used after it is understood.

It is a confirmation for that.
This is not guest's environment.


The availability of CPU goes up when executing it in guest's environment, and the possibility that the system hangs up is understood.


The Debug command was able to be used in old Version.
Moreover, it is possible to use it for HybridOS.


Present NativeOS alone cannot be used.


>debug spanning-tree all


Even if this is input, nothing is displayed as for Catalyst6500 alone.


but,


>debug ip packet


The log comes out from this command.


Will this be a specification?
Or, is the command insufficient?

Correct Answer
Ganesh Hariharan Sat, 02/06/2010 - 03:58
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Member's Choice, February 2016

Hi,


Thanks comment.


Three machines are prepared and it connects it with the triangle.

It is a general composition.

Certainly, the state of STP can be seen from the command and the monitor port.


I want to know whether the Debug command can be used after it is understood.

It is a confirmation for that.
This is not guest's environment.


The availability of CPU goes up when executing it in guest's environment, and the possibility that the system hangs up is understood.


The Debug command was able to be used in old Version.
Moreover, it is possible to use it for HybridOS.


Present NativeOS alone cannot be used.


>debug spanning-tree all


Even if this is input, nothing is displayed as for Catalyst6500 alone.


but,


>debug ip packet


The log comes out from this command.


Will this be a specification?
Or, is the command insufficient?


Hi,


For native ios check out the below link for spanning  tree debug command usage hope that clear you query


http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a00800b1500.shtml


and debug ip packet Don't try it! This command can actually bring an entire production router/switch  down.


However, when used properly, this command can be a very helpful. For example, you can use debug ip packet with an ACL.


If you want to view only traffic from host 1.1.1.1 to host 2.2.2.2 that was using port 80. Being very careful, you could see it using debug ip packet and an ACL.


AS400(config)# access-list 101 deny ip host 1.1.1.1 host 2.2.2.2 eq 80
AS400(config)# exit
AS400# debug ip packet detail 101
IP packet debugging is on (detailed) for access list 101
AS400#


In this example, you have a rudimentary packet sniffer that gives information on TCP port number (src/dest), sequence number, ack, window, and flag information. In addition, this is for the entire device—not just a single interface.


Hope to help


Ganesh.H

ataro Sat, 02/06/2010 - 04:47
User Badges:

Dear ganishh.iyer


Thank you.

It was necessary to switch to SP.

It tries this time.


IP‐Packet and the point for the system to be downed by the usage are understood.
(It is an example to the end. )

Thank you for pointing it out though it knows the use of written ACL.



Thank you again for your kindness.


Sincerely,

Actions

This Discussion

Related Content