EasyManua.ls Logo

Aruba 2530 - Jumbo Frames; Operating Rules

Aruba 2530
479 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
• Port number on which transceiver is installed.
• Type of transceiver.
• Product number — Includes revision letter, such as A, B, or C. If no revision letter follows a product number,
this means that no revision is available for the transceiver.
• Part number — Allows you to determine the manufacturer for a specified transceiver and revision number.
• For a non-HPE switches installed transceiver (see line 23 of "The show tech transceivers command"
example), no transceiver type, product number, or part information is displayed. In the Serial Number field,
non-operational is displayed instead of a serial number.
• The following error messages may be displayed for a non-operational transceiver:
◦ Unsupported Transceiver. (SelfTest Err#060)
◦ This switch only supports revision B and above transceivers.
◦ Self test failure.
◦ Transceiver type not supported in this port.
◦ Transceiver type not supported in this software version.
◦ Not an HPE Switch Transceiver.
Jumbo frames
The maximum transmission unit(MTU) is the maximum size IP frame the switch can receive for Layer 2 frames
inbound on a port. The switch drops any inbound frames larger than the MTU allowed on the port. Ports operating
at a minimum of 1 Gbps can accept forward frames of up to 9220 bytes (including four bytes for a VLAN tag)
when configured for jumbo traffic. You can enable inbound jumbo frames on a per-VLAN basis. That is, on a
VLAN configured for jumbo traffic, all ports belonging to that VLAN and operating at a minimum of 1 Gbps allow
inbound jumbo frames of up to 9220 bytes.
Operating rules
• Required port speed: This feature allows inbound and outbound jumbo frames on ports operating at a
minimum of 1 Gbps.
• GVRP operation: A VLAN enabled for jumbo traffic cannot be used to create a dynamic VLAN. A port
belonging to a statically configured, jumbo-enabled VLAN cannot join a dynamic VLAN.
• Port adds and moves: If you add a port to a VLAN that is already configured for jumbo traffic, the switch
enables that port to receive jumbo traffic. If you remove a port from a jumbo-enabled VLAN, the switch
disables jumbo traffic capability on the port only if the port is not currently a member of another jumbo-enabled
VLAN. This same operation applies to port trunks.
• Jumbo traffic sources: A port belonging to a jumbo-enabled VLAN can receive inbound jumbo frames
through any VLAN to which it belongs, including non-jumbo VLANs. For example, if VLAN 10 (without jumbos
enabled) and VLAN 20 (with jumbos enabled) are both configured on a switch, and port 1 belongs to both
VLANs, port 1 can receive jumbo traffic from devices on either VLAN. For a method to allow only some ports in
a VLAN to receive jumbo traffic, see Configuring a maximum frame size on page 137.
Chapter 6 Port Traffic Controls 133

Table of Contents