DELL PowerConnect 6348 stack : 4.x.x.x to 5.0.0.4 firmware upgrade.

Always check release notes and upgrade procedures provided with the firmware package and make sure you have a backup of current running-config before proceeding.

console#show ip interface out-of-band

IP Address..................................... 172.28.1.3

Subnet Mask.................................... 255.255.255.0

Default Gateway................................ 172.28.1.1

Configured IPv4 Protocol....................... DHCP

Burned In MAC Address.......................... A4BA.DB75.604E

console#configure

console(config)#enable password MyPassw0rd123

console(config)#exit

console#copy running-config startup-config

This operation may take a few minutes.

Management interfaces will not be available during this time.

Are you sure you want to save? (y/n) y

Configuration Saved!

console#copy tftp://10.24.2.2/PCM6348v5.0.0.4a22/PC7000_M6348v5.0.0.4.stk image

Transfer Mode.................................. TFTP

Server IP Address.............................. 10.24.2.2

Source File Path............................... PCM6348v5.0.0.4a22/

Source Filename................................ PC7000_M6348v5.0.0.4.stk

Data Type...................................... Code

Destination Filename........................... image

Management access will be blocked for the duration of the transfer

Are you sure you want to start? (y/n) y

TFTP code transfer starting

13401460 bytes transferred...

File contents are valid. Copying file to flash...

Distributing the code to the members of the stack!

File transfer operation completed successfully.

console#show version

Image Descriptions

 image1 : default image

 image2 :

 Images currently available on Flash

unit  image1       image2       current-active     next-active

----- ------------ ------------ ----------------- -----------------

1     4.2.1.3      5.0.0.4      image1             image1

2     5.0.0.4      4.2.2.3      image2             image2

console#boot system 1 image2

Activating image image2 ..

console#boot system 2 image1

Activating image image1 ..

console#show version

Image Descriptions

 image1 : default image

 image2 :

 Images currently available on Flash

unit  image1       image2       current-active     next-active

----- ------------ ------------ ----------------- -----------------

1     4.2.1.3      5.0.0.4      image1             image2

2     5.0.0.4      4.2.2.3      image2             image1

console#update bootcode

Update bootcode and reset (Y/N)?

Issuing boot code update command...

Validating boot code from image...CRC Valid.

FROM CMC:

$ getioinfo

                                                          

Switch-1  Dell PowerConnect M6220        Gigabit Ethernet   Present      OK           ON          Master

Switch-2  Dell PowerConnect M6220        Gigabit Ethernet   Present      OK           ON          Master

Switch-3  Dell PowerConnect M6348        Gigabit Ethernet   Present      OK           ON          Member

Switch-4  Dell PowerConnect M6348        Gigabit Ethernet   Present      OK           ON          Master

Switch-5  M8428-k 10GbEE-FCoE/8Gb FC SW  10 GbE KR          Present      OK           ON          Master

Switch-6  N/A                            None               Not Present  N/A          N/A         N/A

$ connect switch-4                

connect: acquiring remote port.

Connected to remote port.

Escape character is '^\'.

console>en

Password:********

console#show version

Image Descriptions

 image1 : default image

 image2 :

 Images currently available on Flash

unit  image1       image2       current-active     next-active

----- ------------ ------------ ----------------- -----------------

1     4.2.1.3      5.0.0.4      image2             image2

2     5.0.0.4      4.2.2.3      image1             image1

console#show switch

    Management Standby   Preconfig     Plugged-in    Switch        Code

SW  Status     Status    Model ID      Model ID      Status        Version

--- ---------- --------- ------------- ------------- ------------- -----------

1   Mgmt Sw              PCM6348       PCM6348       OK            5.0.0.4

2   Stack Mbr  Oper Stby PCM6348       PCM6348       OK            5.0.0.4

Reference: support.dell.com

Fedora 17 : KVM - Remote connection

 ~]$ virsh -c 'qemu+ssh://user@192.168.0.100/system' list --all
user@192.168.0.100's password: 
 Id    Name                           State
----------------------------------------------------
 7     F17Server                      running

...to be continued.

Red Hat Enterprise Linux 6.x / Fedora 17 : Sample Network Configuration With Bonding And Persistent Device Names

This is a sample network interface configuration on Red Hat Enterprise Linux or Fedora Linux with persistent device names across reboots. We are not using Network Manager and all configuration is done manually and statically by editing configuration files. Server is connected to a public network via eth0-public interface, to a private LAN via eth1-private interface and to a iSCSI network via bond0-iscsi interface which is using eth2-iscsi and eth3-iscsi physical interfaces.


                      [public-net]
                            |
                         [eth0]-192.168.122.190/24
                            |
                   [RHEL/Fedora Server]
                     |        |    |
192.168.100.130/24-[eth1]  [eth2][eth3] 
                     |        |    |
                     |        [bond0]-172.16.0.130/16
                    |           |
    |           |
              [private-lan]  [iscsi-net]


[root@rhel6srv ~]# service NetworkManager stop
[root@rhel6srv ~]# chkconfig NetworkManager off
[root@rhel6srv ~]# yum remove NetworkManager


[root@rhel6srv ~]# vim /etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:df:6a:25", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0-public"
# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:30:94:49", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1-private"
# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:dd:6b:96", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2-iscsi"
# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:ef:76:d9", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3-iscsi"

[root@rhel6srv ~]# vim /etc/sysconfig/network-scripts/ifcfg-eth0-public
DEVICE="eth0-public"
NAME="eth0-public"
BOOTPROTO="none"
HWADDR="52:54:00:DF:6A:25"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
UUID="fcc027ea-a7a8-4bb4-85b2-2f707a0d706a"
IPADDR="192.168.122.190"
NETMASK="255.255.255.0"


[root@rhel6srv ~]# vim /etc/sysconfig/network-scripts/ifcfg-eth1-private
DEVICE="eth1-private"
NAME="eth1-private"
BOOTPROTO="none"
HWADDR="52:54:00:30:94:49"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
UUID="657cedfe-c86d-4402-9987-942a253ea0a5"
IPADDR="192.168.100.130"
NETMASK="255.255.255.0"


[root@rhel6srv ~]# vim /etc/sysconfig/network-scripts/ifcfg-eth2-iscsi
DEVICE="eth2-iscsi"
NAME="eth2-iscsi"
BOOTPROTO="none"
HWADDR="52:54:00:DD:6B:96"
NM_CONTROLLED="no"
ONBOOT="no"
TYPE="Ethernet"
UUID="039001ef-2fd5-461e-9689-ef9d88c64ddc"
MASTER="bond0-iscsi"
SLAVE="yes"


[root@rhel6srv ~]# vim /etc/sysconfig/network-scripts/ifcfg-eth3-iscsi
DEVICE="eth3-iscsi"
NAME="eth3-iscsi"
BOOTPROTO="none"
HWADDR="52:54:00:EF:76:D9"
NM_CONTROLLED="no"
ONBOOT="no"
TYPE="Ethernet"
UUID="05392749-3641-4e19-8c57-68526f8d985d"
MASTER="bond0-iscsi"
SLAVE="yes"


[root@rhel6srv ~]# vim /etc/sysconfig/network-scripts/ifcfg-bond0-iscsi
DEVICE="bond0-iscsi"
NAME="bond0-iscsi"
MASTER="yes"
BOOTPROTO="none"
IPADDR="172.16.0.130"
NETMASK="255.255.0.0"
ONBOOT="yes"
BONDING_OPTS="mode=0 miimon=100"


[root@rhel6srv ~]# vim /etc/modprobe.d/bond0-iscsi.conf 

alias bond0-iscsi bonding


[root@rhel6srv ~]# ip addr show | grep "state UP" | awk '{print $2}' | cut -d ":" -f1
eth0-public
eth1-private
eth2-iscsi
eth3-iscsi
bond0-iscsi

[root@rhel6srv ~]# cat /proc/net/bonding/bond0-iscsi 
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth1-iscsi
MII Status: up
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 52:54:00:b0:33:e7
Slave queue ID: 0

Slave Interface: eth2-iscsi
MII Status: up
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 52:54:00:70:1f:8f
Slave queue ID: 0

Fedora 17 : GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-17-i386

Today I tried to update my freshly upgraded Fedora 17 but it failed with the error:
GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386


On RPM Fusion I found the page with keys:
http://rpmfusion.org/keys?action=AttachFile&do=view&target=RPM-GPG-KEY-rpmfusion-nonfree-fedora-17


Downloaded the following key:
[get | view] (2011-10-28 21:34:45, 1.7 KB) [[attachment:RPM-GPG-KEY-rpmfusion-nonfree-fedora-17]]
...and moved it to /etc/pki/rpm-gpg/


Then I created a symbolic link to the key:
# ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-17 RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386


Finally I cleaned YUM and run update again:
# yum clean all
# yum check-update
# yum update
...
Is this ok [y/N]: y
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID d2382b83: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386
Importing GPG key 0xD2382B83:
 Userid     : "RPM Fusion nonfree repository for Fedora (17) "
 Fingerprint: 6edf 41e4 8312 dfd4 521b 78fb 0dd6 34bd d238 2b83
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386
Is this ok [y/N]: y
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
   Updating

Dell Force10 S4810 Virtual Link Trunking (VLT) Sample Configuration

Topology

=======================================

_________[MANAGEMENT_NETWORK]_______

|                                   |

|                                   |

172.28.17.252 MgmtPort                               MgmtPort 172.28.17.251

[Force10_VLTPeer1-S4810]Fo1/60---VLTI(ICL)---Fo0/60[Force10_VLTPeer2-S4810]

Te1/24                                Te0/24

|                                    |

|______________        ______________|

|       |

Gi1/45   Gi1/47

[Force10-S60]

Force10_VLTPeer1 Switch Configuration

=======================================

Force10(conf)#hostname Force10_VLTPeer1

1. Configure RSTP

Force10_VLTPeer1#configure

Force10_VLTPeer1(conf)#protocol spanning-tree rstp

Force10_VLTPeer1(conf-rstp)#no disable

Force10_VLTPeer1(conf-rstp)#00:04:08: %STKUNIT1-M:CP %SPANMGR-5-STP_ROOT_CHANGE: RSTP root changed. My Bridge ID: 32768:0001.e88b.1b1d Old Root: 32768:0000.0000.0000 New Root: 32768:0001.e88b.1b1d

Force10_VLTPeer1(conf-rstp)#bridge-priority 0

Force10_VLTPeer1(conf-rstp)#00:04:17: %STKUNIT1-M:CP %SPANMGR-5-STP_ROOT_CHANGE: RSTP root changed. My Bridge ID: 0:0001.e88b.1b1d Old Root: 32768:0001.e88b.1b1d New Root: 0:0001.e88b.1b1d

Force10_VLTPeer1(conf-rstp)#end

2. Check and open ports

Force10_VLTPeer1#show interfaces status | grep 24|60

Te 1/24               Down   Auto      Auto   --

Fo 1/60               Down   40000 Mbit Auto   --

Force10_VLTPeer1#configure

Force10_VLTPeer1(conf)#interface range te 1/24 , fo 1/60

Force10_VLTPeer1(conf-if-range-te-1/24,fo-1/60)#no shutdown

00:05:57: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/24

00:05:57: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Fo 1/60

Force10_VLTPeer1(conf-if-range-te-1/24,fo-1/60)#end

3a. Configure VLTI port-channel

Force10_VLTPeer1(conf)#interface port-channel 100

Force10_VLTPeer1(conf-if-po-100)#no switchport

Force10_VLTPeer1(conf-if-po-100)#no ip address

Force10_VLTPeer1(conf-if-po-100)#channel-member fortyGigE 1/60

Force10_VLTPeer1(conf-if-po-100)#no shutdown

00:07:00: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Po 100

Force10_VLTPeer1(conf-if-po-100)#end

3b. Configure VLT Domain

Force10_VLTPeer2#sh ip interface brief | grep YES

ManagementEthernet 0/0   172.28.17.251   YES Manual up                    up

Force10_VLTPeer1#configure

Force10_VLTPeer1(conf)#vlt domain 999

Force10_VLTPeer1(conf-vlt-domain)#back-up destination 172.28.17.251

Force10_VLTPeer1(conf-vlt-domain)#peer-link port-channel 100

Force10_VLTPeer1(conf-vlt-domain)#end

3c. Verify VLT Domain and VLTI (ICL) are working

(when Peer 2 configuration is completed)

Force10_VLTPeer1#show vlt brief

 VLT Domain Brief

------------------

 Domain ID:                    999

 Role:                         Secondary

 Role Priority:                32768

 ICL Link Status:              Up

 HeartBeat Status:             Up

 VLT Peer Status:              Up

 Local System MAC address:     00:01:e8:8b:1b:1d

 Remote System MAC address:    00:01:e8:8b:19:ac

Force10_VLTPeer1#

4. Configure access port-channel on peer

Force10_VLTPeer1#configure

Force10_VLTPeer1(conf)#interface tengigabitethernet 1/24

Force10_VLTPeer1(conf-if-te-1/24)#port-channel-protocol lacp

Force10_VLTPeer1(conf-if-te-1/24-lacp)#port-channel 110 mode active

00:22:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Po 110

Force10_VLTPeer1(conf-if-te-1/24-lacp)#exit

Force10_VLTPeer1(conf-if-te-1/24)#exit

Force10_VLTPeer1(conf)#interface port-channel 110

Force10_VLTPeer1(conf-if-po-110)#switchport

Force10_VLTPeer1(conf-if-po-110)#vlt-peer-lag port-channel 110

Force10_VLTPeer1(conf-if-po-110)#end

Force10_VLTPeer2 Switch Configuration

=======================================

Force10(conf)#hostname FOrce10_VLTPeer2

1. Configure RSTP

Force10_VLTPeer2#configure

Force10_VLTPeer2(conf)#protocol spanning-tree rstp

Force10_VLTPeer2(conf-rstp)#no disable

Force10_VLTPeer2(conf-rstp)#00:10:52: %STKUNIT0-M:CP %SPANMGR-5-STP_ROOT_CHANGE: RSTP root changed. My Bridge ID: 32768:0001.e88b.19ac Old Root: 32768:0000.0000.0000 New Root: 32768:0001.e88b.19ac

Force10_VLTPeer2(conf-rstp)#bridge-priority 4096

Force10_VLTPeer2(conf-rstp)#00:11:07: %STKUNIT0-M:CP %SPANMGR-5-STP_ROOT_CHANGE: RSTP root changed. My Bridge ID: 4096:0001.e88b.19ac Old Root: 32768:0001.e88b.19ac New Root: 4096:0001.e88b.19ac

Force10_VLTPeer2(conf-rstp)#end

2. Check and open ports

Force10_VLTPeer2#show interfaces status | grep 24|60

Te 0/24               Down   Auto      Auto   --

Fo 0/60               Down   40000 Mbit Auto   --

Force10_VLTPeer2#configure

Force10_VLTPeer2(conf)#int range te 0/24 , fo 0/60

Force10_VLTPeer2(conf-if-range-te-0/24,fo-0/60)#no shutdown

00:12:23: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 0/24

00:12:23: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Fo 0/60

Force10_VLTPeer2(conf-if-range-te-0/24,fo-0/60)#00:12:24: %STKUNIT0-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Fo 0/60

Force10_VLTPeer2(conf-if-range-te-0/24,fo-0/60)#end

3a. Configure VLTI port-channel

Force10_VLTPeer2#configure

Force10_VLTPeer2(conf)#interface port-channel 100

Force10_VLTPeer2(conf-if-po-100)#no switchport

Force10_VLTPeer2(conf-if-po-100)#no ip address

Force10_VLTPeer2(conf-if-po-100)#channel-member fortyGigE 0/60

Force10_VLTPeer2(conf-if-po-100)#00:13:50: %STKUNIT0-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Fo 0/60

Force10_VLTPeer2(conf-if-po-100)#no shutdown

00:13:55: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Po 100

Force10_VLTPeer2(conf-if-po-100)#00:13:56: %STKUNIT0-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Fo 0/60

00:13:56: %STKUNIT0-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Po 100

Force10_VLTPeer2(conf-if-po-100)#end

3b. Configure VLT Domain

Force10_VLTPeer1#show ip interface brief | grep YES

fortyGigE 1/60           unassigned      YES Manual up                    up

ManagementEthernet 1/0   172.28.17.252   YES Manual up                    up

Port-channel 100         unassigned      YES Manual up                    up

Force10_VLTPeer2#configure

Force10_VLTPeer2(conf)#vlt domain 999

Force10_VLTPeer2(conf-vlt-domain)#back-up destination 172.28.17.252

Force10_VLTPeer2(conf-vlt-domain)#00:16:10: %STKUNIT0-M:CP %VLTMGR-6-VLT_HBEAT_UP: Heart beat link is up.

Force10_VLTPeer2(conf-vlt-domain)#peer-link port-channel 100

00:16:26: %STKUNIT0-M:CP %IFMGR-5-ACTIVE: Changed Vlan interface state to active: Vl 1

Force10_VLTPeer2(conf-vlt-domain)#00:16:26: %STKUNIT0-M:CP %VLTMGR-6-VLT_ELECTION_ROLE: Chassis is transitioning to primary role.

00:16:27: %STKUNIT0-M:CP %SPANMGR-5-STP_ROOT_CHANGE: RSTP root changed. My Bridge ID: 4096:0001.e88b.19ac Old Root: 4096:0001.e88b.19ac New Root: 0:0001.e88b.1b1d

00:16:27: %STKUNIT0-M:CP %VLTMGR-6-VLT_ICL_UP: InterChassis Link is up.

00:16:27: %STKUNIT0-M:CP %VLTMGR-6-VLT_PEER_STATUS: Peer chassis is up.

Force10_VLTPeer2(conf-vlt-domain)#end

3c. Verify VLT Domain and VLTI (ICL) are working

(Peer 1 configuration is completed)

Force10_VLTPeer2#show vlt brief

 VLT Domain Brief

------------------

 Domain ID:                    999

 Role:                         Primary

 Role Priority:                32768

 ICL Link Status:              Up

 HeartBeat Status:             Up

 VLT Peer Status:              Up

 Local System MAC address:     00:01:e8:8b:19:ac

 Remote System MAC address:    00:01:e8:8b:1b:1d

4. Configure access port-channel on peer

Force10_VLTPeer2#configure

Force10_VLTPeer2(conf)#interface tengigabitethernet 0/24

Force10_VLTPeer2(conf-if-te-0/24)#port-channel-protocol lacp

Force10_VLTPeer2(conf-if-te-0/24-lacp)#port-channel 110 mode active

00:34:36: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Po 110

Force10_VLTPeer2(conf-if-te-0/24-lacp)#exit

Force10_VLTPeer2(conf-if-te-0/24)#exit

Force10_VLTPeer2(conf)#interface port-channel 110

Force10_VLTPeer2(conf-if-po-110)#switchport

Force10_VLTPeer2(conf-if-po-110)#vlt-peer-lag port-channel 110

Force10_VLTPeer2(conf-if-po-110)#end

Access Switch Configuration

=======================================

Force10#show interfaces status | grep 45|47

Gi 1/45               Down   Auto      Auto   --

Gi 1/47               Down   Auto      Auto   --

Force10#configure

Force10(conf)#interface range gi 1/45 , gi 1/47

Force10(conf-if-range-gi-1/45,gi-1/47)#no shutdown

02:02:46: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Gi 1/45

02:02:46: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Gi 1/47

Force10(conf-if-range-gi-1/45,gi-1/47)#02:02:46: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Gi 1/45

02:02:46: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Gi 1/47

Force10(conf-if-range-gi-1/45,gi-1/47)#port-channel-protocol lacp

Force10(conf-if-range-gi-1/45,gi-1/47-lacp)#port-channel 110 mode active

02:04:19: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Po 110

Force10(conf-if-range-gi-1/45,gi-1/47-lacp)#02:04:21: %STKUNIT1-M:CP %LACP-5-PORT-GROUPED: PortChannel-110-Grouped: Interface Gi 1/45 joined port-channel 110

02:04:21: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Po 110

02:04:22: %STKUNIT1-M:CP %LACP-5-PORT-GROUPED: PortChannel-110-Grouped: Interface Gi 1/47 joined port-channel 110

Verifying Configuration

=======================================

1. Interfaces

Force10_VLTPeer1#show interfaces status | grep 24|60

Te 1/24               Up     1000 Mbit Full   --

Fo 1/60               Up     40000 Mbit Auto   --

Force10_VLTPeer1#show running-config interface te 1/24

!

interface TenGigabitEthernet 1/24

 no ip address

! 

 port-channel-protocol LACP

  port-channel 110 mode active

 no shutdown

Force10_VLTPeer1#show running-config interface fo 1/60

!

interface fortyGigE 1/60

 no ip address

 no shutdown

 Force10_VLTPeer1#show  interfaces port-channel brief

Codes: L - LACP Port-channel

    LAG  Mode  Status       Uptime      Ports         

    100  L2    up           00:40:32    Fo 1/60    (Up)

L   110  L2    up           00:05:13    Te 1/24    (Up)

Force10_VLTPeer1#show running-config interface po 100

!

interface Port-channel 100

 no ip address

 channel-member fortyGigE 1/60

 no shutdown

Force10_VLTPeer1#show running-config interface po 110

!

interface Port-channel 110

 no ip address

 switchport

 vlt-peer-lag port-channel 110

 no shutdown

2. RSTP

Force10_VLTPeer1#show running-config spanning-tree rstp

!

protocol spanning-tree rstp

 no disable

 bridge-priority 0

Force10_VLTPeer1#show spanning-tree rstp

Root Identifier has priority 0, Address 0001.e88b.1b1d

Root Bridge hello time 2, max age 20, forward delay 15, max hops 0

Bridge Identifier has priority 0, Address 0001.e88b.1b1d

Configured hello time 2, max age 20, forward delay 15, max hops 0

We are the root

Current root has priority 0, Address 0001.e88b.1b1d

Number of topology changes 2, last change occured 00:50:11 ago on Po 100

Port 101 (Port-channel 100) is designated Forwarding

Port is a Virtual Link Trunk Interconnect port

Port path cost 1400, Port priority 128, Port Identifier 128.101

Designated root has priority 0, address 0001.e88b.1b1d

Designated bridge has priority 0, address 0001.e88b.1b1d

 Designated port id is 128.101 ,designated path cost 0

Number of transitions to forwarding state 2

BPDU : sent 1550, received 7

The port is not in the Edge port mode

Port 111 (Port-channel 110) is designated Forwarding

Port is a Virtual Link Trunk port

Port path cost 18000, Port priority 128, Port Identifier 128.111

Designated root has priority 0, address 0001.e88b.1b1d

Designated bridge has priority 0, address 0001.e88b.1b1d

 Designated port id is 128.111 ,designated path cost 0

Number of transitions to forwarding state 0

BPDU : sent 458, received 0

The port is not in the Edge port mode

Force10_VLTPeer1#show spanning-tree rstp brief

Executing IEEE compatible Spanning Tree Protocol

Root ID    Priority 0, Address 0001.e88b.1b1d

Root Bridge hello time 2, max age 20, forward delay 15

Bridge ID    Priority 0, Address 0001.e88b.1b1d

We are the root

Configured hello time 2, max age 20, forward delay 15

Interface                                                Designated                 

 Name      PortID   Prio Cost    Sts         Cost        Bridge ID        PortID

---------- -------- ---- ------- ----------- ------- -------------------- --------

Po 100     128.101  128  1400    FWD(vltI) 0       0     0001.e88b.1b1d 128.101

Po 110     128.111  128  18000   FWD(vlt)  0       0     0001.e88b.1b1d 128.111

Interface

 Name      Role   PortID   Prio Cost    Sts         Cost    Link-type Edge

---------- ------ -------- ---- ------- ----------- ------- --------- ----

Po 100     Desg   128.101  128  1400    FWD         0       (vltI)P2P No 

Po 110     Desg   128.111  128  18000   FWD       0       (vlt) P2P No 

Force10_VLTPeer1#show spanning-tree rstp interface

Port-channel 100 is designated forwarding

Port is a Virtual Link Trunk Interconnect port

Edge port:no (default) port guard :none (default)

Link type: point-to-point (auto) bpdu filter:disable (default)

Bpdu guard :disable bpduguard shutdown-on-violation : disable RootGuard: disable LoopGuard disable

Bpdus sent 1519, received 7

Interface                                              Designated               

 Name     PortID   Prio Cost    Sts         Cost       Bridge ID         PortID 

--------- -------- ---- ------- ----------- ------- -------------------- --------

Po 100    128.101  128  1400    FWD(vltI) 0       0     0001.e88b.1b1d 128.101

Port-channel 110 is designated Forwarding

Port is a Virtual Link Trunk port

Edge port:no (default) port guard :none (default)

Link type: point-to-point (auto) bpdu filter:disable (default)

Bpdu guard :disable bpduguard shutdown-on-violation : disable RootGuard: disable LoopGuard disable

Bpdus sent 427, received 0

Interface                                              Designated               

 Name     PortID   Prio Cost    Sts         Cost       Bridge ID         PortID 

--------- -------- ---- ------- ----------- ------- -------------------- --------

Po 110    128.111  128  18000   FWD(vlt)  0       0     0001.e88b.1b1d 128.111

3. VLT

Force10_VLTPeer1#show running-config  vlt

!

vlt domain 999

 peer-link port-channel 100

 back-up destination 172.28.17.251

Force10_VLTPeer1#show vlt ?

backup-link             Backup-link information                

brief                   Brief information on the VLT           

detail                  Detail information on the VLT          

role                    Role of VLT peer                        

statistics              Statistics of the VLT     

Force10_VLTPeer1#show vlt backup-link

 VLT Backup Link

-----------------

 Destination:                    172.28.17.251

 Peer HeartBeat status:          Up

 HeartBeat Timer Interval:       1

 HeartBeat Timeout:              3

 UDP Port:                       34998

 HeartBeat Messages Sent:        2547

 HeartBeat Messages Received:    2116

 Force10_VLTPeer1#show vlt brief

 VLT Domain Brief

------------------

 Domain ID:                    999

 Role:                         Secondary

 Role Priority:                32768

 ICL Link Status:              Up

 HeartBeat Status:             Up

 VLT Peer Status:              Up

 Local System MAC address:     00:01:e8:8b:1b:1d

Force10_VLTPeer1#show  vlt detail

Local LAG Id  Peer LAG Id  Local Status  Active VLANs

------------  -----------  ------------  ------------

110           110          Up            1

Force10_VLTPeer1#show vlt role

 VLT Role

----------

 VLT Role:                     Secondary

 System MAC address:           00:01:e8:8b:19:ac

 Primary Role Priority:         32768

 Local System MAC address:     00:01:e8:8b:1b:1d

 Local System Role Priority:   32768

Force10_VLTPeer1#show vlt statistics

 VLT Statistics

----------------

 HeartBeat Messages Sent:       2679

 HeartBeat Messages Received:   2248

 ICL Hello's Sent:              2467

 ICL Hello's Received:          2233

 Domain Mismatch Errors:        0

 Version Mismatch Errors:       0

 Config Mismatch Errors:        0