Deploying FCoE (FIP Snooping) on Dell Force 10 MXL
50
Configuring the Cisco 5000 series switch for vPC and connections from the Dell Force10 MXL
Initial vPC configuration without FCoE links Figure 43.
Peer Keep-Alive
Peer Keep-Alive
CONSOLE
33-3637-40
LNK ACTLNK ACT
Force10 MXL 10/40GbE
41-48
49-56
CONSOLE
33-3637-40
LNK ACTLNK ACT
Force10 MXL 10/40GbE
41-48
49-56
3
CISCO NEXUS N5548UP
STAT
ID
1
2
3
4
5
6
7
8 9 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24 25 26
27
28
29
30
31
32
1/10 GIGABIT ETHERNET 1/2/4/8G FIBRE CHANNEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
N55-M16UP
3
CISCO NEXUS N5548UP
STAT
ID
1
2
3
4
5
6
7
8 9 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24 25 26
27
28
29
30
31
32
1/10 GIGABIT ETHERNET 1/2/4/8G FIBRE CHANNEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
N55-M16UP
Management LAN
LAG/PortChannel
LAG/PortChannel
vPC Peer Link
Nex5K-1
Nex5K-2
MXL-1
MXL-2
In the above figure it can be observed that MXL-1 and MXL-2 each have a 4-port LAG/PortChannel
uplinking into the two Cisco Nexus switches. This number of links is not set in stone and can be
changed to meet the needs of any particular configuration. Also in this example 4 ports were used for
the vPC “Peer Link”, this number also can be changed to adapt to a different configuration. The vPC
Peer Link will be sharing VLAN traffic from the vPC uplinks, so they should be planned in an appropriate
manner to avoid oversubscription. The “Peer Keep-Alive” link is suggested to be configured to utilize
the management port (this is the default) and will send very little layer 3 traffic between the switches.
The two Cisco Nexus 5000 Series switches are considered vPC peer switches.
To Next Page
Loading...
Need help?
General
