cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1036
Views
0
Helpful
6
Replies

Cannot ping SVI after power outage

jbritto76
Level 1
Level 1

After a power outage we are unable to ping our SVI. The vlans are showing up and up but I have no connectivity. The vlans that we cannot connect to are phone and camera vlans. The only solution I have found is going into the core switch for the site and shut/no shut all the problem vlans and the issue is resolved. 

 

Has anyone ever had this issue if so how did you resolve?

1 Accepted Solution

Accepted Solutions

Hello

So the first thing to do is to set the core switch as the stp root for the entire network, I would suggest using a stp priority value instead of the marco root primary command.


spanning-tree vlan 1-4096 priority  0 <--4096 is only needed if you have extended vlans over 1004
(enabled by spanning-tree extended-id)

 

Also I encountered a similar issue on a 4500x vss core regarding the L3 svi not being able to route correctly and the only way I could get this back up and running was indeed to shutdown and re enable the effected L3 interfaces - it turned out in my case to be this bug , So eventually I had to upgrade the ios.



res
Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

6 Replies 6

Hello,

 

could be a bug - which platform and IOS are you running ?

Here is the version:

 

Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500e-ENTSERVICESK9-M), Version 12.2(54)SG1, RELEASE SOFTWARE (fc1)

 

 

Hello,

 

I checked for bugs but couldn't find any. Is the core switch the root for those two Vlans ? Can you post he output of 'show spanning-tree vlan x' where 'x' is the Vlan number ?

HI

 

after the outtage, did you do reload? 

I ve seen very strange things happening at l3 after outtages. 

 

A reload usually fixes these issues. 

Yea I see the Core switch is not the root bridge for these VLAN's

 

 

VLAN0200
Spanning tree enabled protocol ieee
Root ID Priority 32968
Address 30e4.db3f.c700
Cost 2
Port 1 (TenGigabitEthernet1/1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32968 (priority 32768 sys-id-ext 200)
Address c89c.1d71.c900
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec

Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Te1/1 Root FWD 2 128.1 P2p
Te1/3 Desg FWD 2 128.3 P2p
Te1/4 Desg FWD 2 128.4 P2p
Te1/5 Desg FWD 2 128.5 P2p
Te1/6 Desg FWD 2 128.6 P2p
Te1/7 Desg FWD 2 128.7 P2p
Te1/8 Desg FWD 2 128.8 P2p
Te3/1 Desg FWD 2 128.129 P2p
Te3/2 Desg FWD 2 128.130 P2p
Gi3/20 Desg FWD 4 128.148 P2p


sh spanning-tree vlan 230

VLAN0230
Spanning tree enabled protocol ieee
Root ID Priority 32998
Address 30e4.db28.f880
Cost 2
Port 3 (TenGigabitEthernet1/3)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32998 (priority 32768 sys-id-ext 230)
Address c89c.1d71.c900
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec

Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Te1/1 Desg FWD 2 128.1 P2p
Te1/3 Root FWD 2 128.3 P2p
Te1/4 Desg FWD 2 128.4 P2p
Te1/5 Desg FWD 2 128.5 P2p
Te1/6 Desg FWD 2 128.6 P2p
Te1/7 Desg FWD 2 128.7 P2p
Te1/8 Desg FWD 2 128.8 P2p
Te3/1 Desg FWD 2 128.129 P2p
Te3/2 Desg FWD 2 128.130 P2p
Gi3/20 Desg FWD 4 128.148 P2p

Hello

So the first thing to do is to set the core switch as the stp root for the entire network, I would suggest using a stp priority value instead of the marco root primary command.


spanning-tree vlan 1-4096 priority  0 <--4096 is only needed if you have extended vlans over 1004
(enabled by spanning-tree extended-id)

 

Also I encountered a similar issue on a 4500x vss core regarding the L3 svi not being able to route correctly and the only way I could get this back up and running was indeed to shutdown and re enable the effected L3 interfaces - it turned out in my case to be this bug , So eventually I had to upgrade the ios.



res
Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul
Review Cisco Networking products for a $25 gift card