×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Catalyst 6513 %SYS-2-MOD_NOINBANDRESPONSE:

Unanswered Question
Oct 9th, 2002
User Badges:

Speaking about a 6513 with 2 supervisor.

We are receiving this system log message every 2 minutes.


InbandPingProcessFailure:Module 2 not responding over inband


ANy ideas?


Thanks


Marco

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Georg Pauwen Wed, 10/09/2002 - 00:56
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 WAN

Hi Marco,


found this on CCO, not sure how your management VLAN is configured:


- One performance-related issue that results from misconfiguration is when the inband channel, which is used for any control traffic terminating on the switch, such as ping, Telnet, VTP, STP, or CDP is not put in a seperate VLAN from user data.


It is always recommended to keep the managment or sc0 interface of the switch in a separate VLAN from user data. Otherwise, any broadcast or multicast storm can flood the inband channel to the Network Management Processor (NMP) which needs to be free to hande the protocols just mentioned.


Regards,


Georg


DALE FRANCIS Wed, 10/09/2002 - 02:36
User Badges:
  • Bronze, 100 points or more

You can test the the com with the mod with the following:


test scp 2 1464 10

Pinging Module 2, Length 1464, Count 10

0: PASSED

1: PASSED

2: PASSED

3: PASSED

4: PASSED

5: PASSED

6: PASSED

7: PASSED

8: PASSED

9: PASSED


The reason why they say make sure your managment VLAN does not carry data is that for inband comms they are tagged with the sc0 vlan. If you do some debugging one can see this, but please do not do this on a live network it can literally kill the switch.. :))

Prashanth Krishnappa Wed, 10/09/2002 - 04:38
User Badges:
  • Cisco Employee,

Did you have any STP loops/High CPU at the time message is printed? The above messages are printed when the Supervisor's CPU gets pegged high. Also does the Supervisor in slot 2 reset? There was a bug file for this kind of crash saying the switch should not crash under these circumstances and is fixed now.

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdx10436

My suggestions to you would be

a)Upgrade to 6.3(9) or 7.3(2) if you are in 7.x

b)reseat the Supervisor in slot 2 and make sure it's seated firmly with screws tightened

Actions

This Discussion