[c-nsp] Cisco blade switch config
Matthieu Michaud
matthieu at nxdomain.fr
Tue Feb 19 23:16:00 EST 2013
a common approach is to not use spanning-tree but link state tracking on
blade switches (which are plain 3550 in a blade) + active/passive
redundancy on blade servers (NFT in HP terminology)
On Wed, Feb 20, 2013 at 9:41 AM, Nicolas KARP <liste at karp.fr> wrote:
> For you information, here is what we did :
>
> Gi0/1 up up FRBC1VM01 # VMNIC 0
> Gi0/2 up up FRBC1VM02 # VMNIC 0
> Gi0/3 up up FRBC1VM03 # VMNIC 0
> Gi0/4 up up FRBC1VM04 # VMNIC 0
> Gi0/5 up up FRBC1VM05 # VMNIC 0
> Gi0/6 down down FRBC1VM06 # VMNIC 0
> Gi0/7 down down FRBC1VM07 # VMNIC 0
> Gi0/8 down down FRBC1VM08 # VMNIC 0
> Gi0/9 up up FRBC1VM09 # VMNIC 0
> Gi0/10 up up FRBC1VM10 # VMNIC 0
> Gi0/11 up up FRBC1VM11 # VMNIC 0
> Gi0/12 up up FRBC1VM12 # VMNIC 0
> Gi0/13 up up FRBC1VM13 # VMNIC 0
> Gi0/14 down down FRBC1VM14 # VMNIC 0
> Gi0/15 down down FRBC1VM15 # VMNIC 0
> Gi0/16 down down FRBC1VM16 # VMNIC 0
> Gi0/17 up up 4948-CORE1-FR #
> Gi1/0/9
> Gi0/18 up up 4948-CORE1-FR #
> Gi1/0/10
> Gi0/19 up up 4948-CORE2-FR #
> Gi1/0/9
> Gi0/20 up up 4948-CORE2-FR #
> Gi1/0/10
> Gi0/21 down down
> Gi0/22 down down
> Gi0/23 down down
> Gi0/24 down down
> Po10 up up 4948-CORE1-FR (Local
> : gi0/17-18 # Peer : Gi1/9-10)
> Po11 up up 4948-CORE2-FR (Local
> : gi0/19-20 # Peer : Gi1/9-10)
>
>
>
> Some ports are down because there is currently no Blade connected to slot 6
> / 7 / 8 / 14 / 15 / 16
>
> Port 17 and 18 : Po10 connected to our external switch called Core1
> Port 19 and 20 : Po11 connected to our external switch called Core2
>
> The spanning-tree is handling the failover between the 2 port-channels.
> So far, all vlans trunk on po10 are in the forwarding state whereas on po11
> state is blocking (except 666 due to our design)
>
>
> 3020-1-FR# sh spanning-tree int po10
>
> Vlan Role Sts Cost Prio.Nbr Type
> ------------------- ---- --- --------- --------
> --------------------------------
> VLAN0001 Root FWD 3 128.128 P2p
> VLAN0002 Root FWD 3 128.128 P2p
> VLAN0004 Root FWD 3 128.128 P2p
> VLAN0016 Root FWD 3 128.128 P2p
> VLAN0017 Root FWD 3 128.128 P2p
> VLAN0032 Root FWD 3 128.128 P2p
> VLAN0070 Root FWD 3 128.128 P2p
> VLAN0090 Root FWD 3 128.128 P2p
> VLAN0666 Altn BLK 3 128.128 P2p
>
>
> 3020-1-FR# sh spanning-tree int po11
>
> Vlan Role Sts Cost Prio.Nbr Type
> ------------------- ---- --- --------- --------
> --------------------------------
> VLAN0001 Altn BLK 3 128.136 P2p
> VLAN0002 Altn BLK 3 128.136 P2p
> VLAN0004 Altn BLK 3 128.136 P2p
> VLAN0016 Altn BLK 3 128.136 P2p
> VLAN0017 Altn BLK 3 128.136 P2p
> VLAN0032 Altn BLK 3 128.136 P2p
> VLAN0070 Altn BLK 3 128.136 P2p
> VLAN0090 Altn BLK 3 128.136 P2p
> VLAN0666 Root FWD 3 128.136 P2p
>
>
> Here is an example of g0/1, port connected to a blade-server :
>
> interface GigabitEthernet0/1
> description FRBC1VM01 # VMNIC 0
> switchport trunk encapsulation dot1q
> switchport trunk native vlan 2
> switchport mode trunk
> speed 1000
> spanning-tree portfast trunk
> end
>
>
> And the configuration for the first port-channel :
>
> interface GigabitEthernet0/17
> description 4948-CORE1-FR # Gi1/0/9
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport nonegotiate
> channel-group 10 mode active
> end
>
>
> interface GigabitEthernet0/18
> description 4948-CORE1-FR # Gi1/0/10
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport nonegotiate
> channel-group 10 mode active
> end
>
> interface Port-channel10
> description 4948-CORE1-FR (Local : gi0/17-18 # Peer : Gi1/9-10)
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport nonegotiate
> end
>
>
>
> Hope these examples can help you to find the correct design.
>
> Best Regards,
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
--
Matthieu MICHAUD
More information about the cisco-nsp
mailing list