Dell Networking S6000 Uživatelský manuál stáhnout pdf (Strana 338)

100

101

occurs. You can optimize the booting time of the ToR nodes that experience a single point of failure

to reduce the outage in traffic-handling operations.

RoCE over a routed system is called RRoCE. RRoCE has IP headers. RRoCE is bursty and uses the entire

10-Gigabit Ethernet interface. Although RRoCE and normal data traffic are propagated in separate

network portions, it may be necessary in certain topologies to combine both the RRoCE and the data

traffic in a single network structure. RRoCE traffic is marked with dot1p priorities 3 and 4 (code points 011

and 100, respectively) and these queues are strict and lossless. DSCP code points are not tagged for

RRoCE. Both ECN and PFC are enabled for RRoCE traffic. For normal IP or data traffic that is not RRoCE-

enabled, the packets comprise TCP and UDP packets and they can be marked with DSCP code points.

Multicast is not supported in that network.

Preserving 802.1Q VLAN Tag Value for Lite Subinterfaces

This functionality is supported on the S6000 platform.

All the frames in a Layer 2 VLAN are identified using a tag defined in the IEEE 802.1Q standard to

determine the VLAN to which the frames or traffic are relevant or associated. Such frames are

encapsulated with the 802.1Q tags. If a single VLAN is configured in a network topology, all the traffic

packets contain the same do1q tag, which is the tag value of the 802.1Q header. If a VLAN is split into

multiple, different sub-VLANs, each VLAN is denoted by a unique 8021.Q tag to enable the nodes that

receive the traffic frames determine the VLAN for which the frames are destined.

Typically, a Layer 3 physical interface processes only untagged or priority-tagged packets. Tagged

packets that are received on Layer 3 physical interfaces are dropped. To enable the routing of tagged

packets, the port that receives such tagged packets needs to be configured as a switchport and must be

bound to a VLAN as a tagged member port.

A lite subinterface is similar to a normal Layer 3 physical interface, except that additional provisioning is

performed to set the VLAN ID for encapsulation.

A physical interface or a Layer 3 Port channel interface can be configured as a lite subinterface. Once a

lite subinterface is configured, only tagged IP packets with encapsulation VLAN ID are processed and

routed. All other data packets are discarded except the Layer 2 and Layer 3 control frames. It is not

required for a VLAN ID to be preserved (in the hardware or the OS application) when a VLAN ID, used for

encapsulation, is associated with a physical/Port-channel interface. Normal VLANs and VLAN

encapsulation can exist simultaneously and any non-unicast traffic received on a normal VLAN is not

flooded using lite subinterfaces whose encapsulation VLAN ID matches with that of the normal VLAN ID.

You can use the encapsulation dot1q vlan-id command in INTERFACE mode to configure lite

subinterfaces.

338

Flex Hash and Optimized Boot-Up

1 2 ... 333 334 335 336 337 338 339 340 341 342 343 ... 985 986

Komentáře k této Příručce

Žádné komentáře

Dell Networking S6000 Uživatelský manuál Strana 338

Komentáře k této Příručce

Související produkty a manuály pro Software Dell Networking S6000