09-07-2008 10:08 PM - edited 03-06-2019 01:13 AM
when C6506 rises high in cpu utilization intermittently, we could see EOBC 0/0 interface higher CPU uitilization and data flow on this interface at that time. What kind of traffic would flow in /out EOBC0/0 at that time? Right now it is runing version is 12.2(18)SXF12a on backbone C6506 and core C6506 two routers.
09-08-2008 01:00 AM
Hello Justin,
here it is a link on troubleshooting high cpu usage on C6500
May you post a sh module to see what kind of linecards are installed ?
Hope to help
Giuseppe
09-08-2008 01:17 AM
Hi Giuseppe:
The following is show module message on core-6506.
------------------ show module ------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAD111302J2
5 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL1114KMWT
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 001b.2a4e.88a6 to 001b.2a4e.88bd 2.5 12.2(14r)S5 12.2(18)SXF1 Ok
5 0017.9568.bf14 to 0017.9568.bf17 5.3 8.4(2) 12.2(18)SXF1 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Distributed Forwarding Card WS-F6700-DFC3B SAL1114KLGV 4.6 Ok
5 Policy Feature Card 3 WS-F6K-PFC3B SAL1114KP5J 2.3 Ok
5 MSFC3 Daughterboard WS-SUP720 SAL1114KQV6 2.6 Ok
Mod Online Diag Status
---- -------------------
1 Pass
5 Pass
09-08-2008 01:35 AM
Hello Justin,
EOBC Messages
This section contains Ethernet out-of-band channel (EOBC) messages.
these are messages of management inside chassis.
Do you see any error message related to EOBC ?
like the following
http://www.cisco.com/en/US/docs/ios/12_2sx/system/messages/sm2sx03.html#wp1034007
But you have said that three devices are involved in the problem so an hardware failure is unlikely.
There isn't a second supervisor on chassis.
So the EOBC can be used only to upgrade the CEF table on the DFC of linecard and it is a DFC 3B aligned with sup 720 3B.
Try to verify if any routing protocol is recalculating too frequently so triggering a massive CEF update
Hope to help
Giuseppe
09-08-2008 01:58 AM
Hi Giuseppe:
I already checked log , it's no any error message for EOBC interface and no interface is up/down at that time. It should not recalculate in routing update, then trigger mass CEF update. I am not sure it is "Cat6k boxes should not be reachable via 127.0.0.x addresses" or not. I could not encounter the real situation like web site says 6500 could reach via 127.0.0.0.
09-08-2008 02:39 AM
Hello Justin,
127.0.0.x are the ip addresses used for inter -module communication in the chassis and are actually loopback addresses.
127/8 is reserved for loopback addresses: addresses used inside a node and not to be seen outside the node itself.
Hope to help
Giuseppe
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: