Upgrade

[TroyBolton]

Upgrade

[balaji.bandi]

There is no complicate here.

you need to write order process while migrating.

you required down time here, upgrade in maintenance window.

1. Offline configured NExus 9K like 5K as production.

2. check all the configuraiton is correct on 9K.

3. check the FEX compatability with Nexus 9K

4. turn off the FEX and Migrate to new Nexus 9K, should book as expected.

5. then move other FEX to Nexus 9K and any other connection on Nexus 5K to Nexus 9K

make sense ?

[Sergiu.Daniluk]

Hi @TroyBolton 

The "VLAN/BD is down" means that the vlans are not allowed on any ports OR all ports allowing the vlan are down. By default, the SVI will not come up if you do not have an up/up interface in your vlan. The command which is generating this behavior is "autostate". To have the SVIs up, regardless if you have any interface up in the vlan, you can configure 'no autostate'.

N9K-1# show run int vlan 10
interface Vlan10
  no shutdown

N9K-1# show vlan id 10
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
10   VLAN0010                         active    

N9K-1# show interface vlan 10 brief 
-------------------------------------------------------------------------------
Interface Secondary VLAN(Type)                    Status Reason                 
-------------------------------------------------------------------------------
Vlan10    --                                      down   VLAN/BD is down    

N9K-1(config)# interface vlan 10
N9K-1(config-if)# no autostate 
N9K-1(config-if)# show interface vlan 10 brief 
-------------------------------------------------------------------------------
Interface Secondary VLAN(Type)                    Status Reason                 
-------------------------------------------------------------------------------
Vlan10    --                                      up     --        

So with this in mind, if you do not have any ports in the vlans up, what you see is expected behavior. Also, I would not recommend using "no autostate", since it is better to have the default behavior, especially during troubleshooting.

Regarding the mgmt interface, you can do the changes like this:

N9K-1(config)# interface mgmt0
N9K-1(config-if)# ip address <ip>/<mask>

Regards,

Sergiu

[TroyBolton]

@Sergiu.Daniluk you said you wouldn't recommend using "no autostate", but does this mean i didn't copy the config properly or i'm just missing something, I understand that for an SVI - Its VLAN must exist and be active in the VLAN database, at least one switched port in the VLAN (access or trunk) must be up, that port must be in the STP forwarding state.

If i'm correct i must not be meeting one of the criteria?

@balaji.bandi my change was very organised (I hope), shutdown ports 1-48 on the 5k, and then swapped them all into the 9K. Just once i have plugged it all into the 9K all links light up green after no shut, but nothing seem's to get through, even the eth int on the fex are all administratively down, once i return it all to the 5k and no shut, back to normal.

[Sergiu.Daniluk]

Hello @TroyBolton 

If i'm correct i must not be meeting one of the criteria?

That is correct. For SVI to be up, with the default configuration ("autostate" present), the following criteria needs to be true:

 - vlan must be configured in vlan db

 - vlan must allowed on an interface (access or trunk)

 - interface must be up

"no autostate" is just a configuration which can bring your SVI up, even if one of the previously mentioned criteria is not meet.

Cheers,

Sergiu

[balaji.bandi]

I am more intrested to Look at the config and ports were shutdown mode reason ?

is this vPC ? do you have any network diagram how these connected.

give some example  and logs .