which MSFC install CEF entries under hybrid 6500(SUP2/MSFC2)

6513 SUP2/PFC2/MSFC2 CatOS8.1+IOS12.1

the two superviors run in highavailability mode, but the two MSFCs doesnt(I am not sure: it is not SRM since 16's status is ok, it is not manual redundancy mode since both MSFC run in IOS stage)

1 1 2 1000BaseX Supervisor WS-X6K-S2U-MSFC2 yes ok 15 1 1 Multilayer Switch Feature WS-F6K-MSFC2 no ok 2 2 2 1000BaseX Supervisor WS-X6K-S2U-MSFC2 yes standby 16 2 1 Multilayer Switch Feature WS-F6K-MSFC2 no ok

In my opinion, 15 is the active module, but I am confused by the CEF table:

layer2>(enable) show mls cef mac Module 15: Physical MAC-Address 00-0c-cf-0f-0f-0c Module 16: Physical MAC-Address 00-0c-cf-0f-0f-0d Module 16 is the designated MSFC for installing CEF entries

I think it is Module 15 installed the CEF entries,because: `show ip route' under session16 display nothing, and `show ip int brief' under session16 says that all interfaces are shutdown. And `show ip cef' under session16 is empty too.

instead, `show ip route', `show ip int brief' and `show ip cef' under session15 have correct entries.

here is CEF table for active supervior in slot 1: the skipped entries are all receive entries for VLAN interfaces. The problem is that I have default route on session15, however it is wildcard in CEF table. I also have many nexthop-ip while `show ip cef' under session15, however no correct nexthop-ip in CEF table. Is it wired, isnt it? :(

layer2> (enable) show mls entry cef Mod FIB-Type Destination-IP Destination-Mask NextHop-IP Weight

--- --------- --------------- ---------------- --------------- ------ 16 receive 0.0.0.0 255.255.255.255 16 receive 255.255.255.255 255.255.255.255 15 receive 127.0.0.0 255.255.255.255 15 receive 127.255.255.255 255.255.255.255 16 resolved 127.0.0.21 255.255.255.255 127.0.0.21 1 16 resolved 127.0.0.11 255.255.255.255 127.0.0.11 1 15 receive 127.0.0.12 255.255.255.255 15 receive 10.50.8.129 255.255.255.255 15 receive 10.50.8.128 255.255.255.255 15 receive 10.50.8.191 255.255.255.255 ..... skipped ..... 15 receive 10.50.14.64 255.255.255.255 15 receive 10.50.14.127 255.255.255.255 15 receive 10.50.14.65 255.255.255.255 16 receive 224.0.0.0 255.255.255.0 16 connected 127.0.0.0 255.0.0.0 16 drop 224.0.0.0 240.0.0.0 16 wildcard 0.0.0.0 0.0.0.0

Mod FIB-Type Dest-IPX-net NextHop-IPX Weight

--- --------- ------------ ------------------------- ------ 16 wildcard 0

So I would like someone point me in the right direction. what should I do, which command to debug it or syslog etc, any idea will be great appreciated, thx

Reply to
Tao Liu
Loading thread data ...

Shouldn't this all depend on which router is the next hop for which networks? Do you have hsrp setup, and if so, which router is active? And truthfully, I'm not even sure HSRP matters in this case. Do you have adjacencies for your routing protocol? This isn't a cef issue, its a layer 2 or 3 issue if you don't have any up/up interfaces in show ip int brief. Something is wrong in configuration, as you should have all vlan interfaces up, you should see adjacencies in your routing protocol, and both routers should have routes to/from the same things presuming you have fully redundant configurations. Once that stuff is resolved, then you can worry about which msfc is primary and will be manipulating CEF. My suspicion is that they both would be, but only the one who is the primary for vlans and routing will actually be doing it while the other one sits in redundant mode ready to takeover in case of a failure.

Reply to
Trendkill

I am sure that it is neither SRM(single router mode) nor Manual-Mode MSFC Redundancy. I guess it is not Dual MSFC Redundancy, no HSRP setup, And I have two questions:

1, is this correct? -- not configre redundancy for two MSFCs in the same chassis. 2, if it is correct, is it possible `show ip int brief' shows all the interfaces are down in session16?

otherwise, I should configure redundancy for both MSFCs, i.e. DRM, SRM etc

no routing protocol is running, only static route and default route.

Reply to
Tao Liu

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.