
flowcontrol rx [
off
|
on
] tx [
off
|
on
] [negotiate]
–
rx on
: enter the keywords
rx on
to process the received flow control frames on this port.
–
rx off
: enter the keywords
rx off
to ignore the received flow control frames on this port.
–
tx on
: enter the keywords
tx on
to send control frames from this port to the connected device when a higher rate of
traffic is received.
–
tx off
: enter the keywords
tx off
so that flow control frames are not sent from this port to the connected device when
a higher rate of traffic is received.
–
negotiate
: enable pause-negotiation with the egress port of the peer device. If the
negotiate
command is not used,
pause-negotiation is disabled. 40 gigabit Ethernet interfaces do not support pause-negotiation.
–
threshold
: when you configure
tx on
, you can set the threshold values for:
* Number of flow-control packet pointers: the range is from 1 to 2047 (default =
75
).
* Flow-control buffer threshold in KB: the range is from 1 to 2013 (default =
49KB
).
* Flow-control discard threshold in KB: the range is from 1 to 2013 (default=
75KB
)
Configure the MTU Size on an Interface
If a packet includes a Layer 2 header, the difference in bytes between the link MTU and IP MTU must be enough to include the Layer
2 header.
For example, for VLAN packets, if the IP MTU is 1400, the Link MTU must be no less than 1422:
1400-byte IP MTU + 22-byte VLAN Tag = 1422-byte link MTU
The following table lists the various Layer 2 overheads found in Dell Networking OS and the number of bytes.
The following table lists the various Layer 2 overheads found in the Dell Networking OS and the number of bytes.
Table 42. Layer 2 Overhead
Layer 2 Overhead
Difference Between Link MTU and IP MTU
Ethernet (untagged)
18 bytes
VLAN Tag
22 bytes
Untagged Packet with VLAN-Stack Header
22 bytes
Tagged Packet with VLAN-Stack Header
26 bytes
Link MTU and IP MTU considerations for port channels and VLANs are as follows.
Port Channels
:
•
All members must have the same link MTU value and the same IP MTU value.
•
The port channel link MTU and IP MTU must be less than or equal to the link MTU and IP MTU values configured on the channel
members.
For example, if the members have a link MTU of 2100 and an IP MTU 2000, the port channel’s MTU values cannot be higher than
2100 for link MTU or 2000 bytes for IP MTU.
VLANs
:
•
All members of a VLAN must have the same IP MTU value.
•
Members can have different Link MTU values. Tagged members must have a link MTU 4–bytes higher than untagged members
to account for the packet tag.
•
The VLAN link MTU and IP MTU must be less than or equal to the link MTU and IP MTU values configured on the VLAN
members.
394
Interfaces
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...