Cisco Ex SERIES Manuel d'utilisateur télécharger pdf (Page 17)

Juniper Networks/Cisco Systems Switch Interoperability Cookbook

! ! !

Figure 4 illustrates the configuration used to validate jumbo frame switching. As noted in

the configuration sections below, all interfaces explicitly support switching of jumbo

frames. On the Juniper Virtual Chassis Fabric, two clients (one apiece attached to the

Juniper QFX5100 and EX4300) use an untagged VLAN ID of 2001. The 10-Gbit/s

Ethernet interface xe-1/0/2 is a trunk port, conveying tagged traffic to the Cisco Nexus

7010 switch. On the Cisco side, interface Ethernet3/3 is also a trunk port. A server is

attached to access port Ethernet3/13.

!"#$%&'A)'=$>?2'@%.>&'/B"0C1";#'02-232#4'

Juniper!commands!

Jumbo frame support is enabled by adding the mtu keyword when configuring interfaces.

Note that the mtu keyword applies to the physical interface and not the logical unit

interface where VLAN membership is assigned.

Note that the Junos mtu keyword does not include the Ethernet CRC. Thus, to pass

9,216-byte Ethernet frames (including CRC), untagged (access) ports will take a

command of mtu 9212, while trunk ports will take a command of mtu 9216 (to

accommodate the 4-byte VLAN tag).

In this example, MTU and VLAN settings are configured separately. First, MTU settings

are applied to each interface. Again, note that interface xe-1/0/1 takes a larger MTU value

to accommodate VLAN tagging:

admin@VCF> configure

admin@VCF# set interfaces xe-1/0/40 mtu 9212

admin@VCF# set interfaces xe-1/0/40 description "to client on QFX5100"

admin@VCF# set interfaces ge-2/0/0 mtu 9212

admin@VCF# set interfaces ge-2/0/0 description "to client on EX4300"

admin@VCF# set interfaces xe-1/0/2 mtu 9216

admin@VCF# set interfaces xe-1/0/2 description "VLAN trunk to Nexus 7010

e3/3"

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 82 83

Pas de commentaire

Cisco Ex SERIES Manuel d'utilisateur Page 17