Specifications

New and Enhanced Features in ExtremeWare 7.4
ExtremeWare 7.4.3 Installation and Release Notes 11
domains in a spatial reuse configuration. By doing this, the entire bandwidth for the ring can be used,
including the LAN segment connected to the secondary port of the master switch.
Multicast Extensions
• Multicast Copy Count
Multicast copy count extension allows you to enable or disable this feature using the CLI when you
need to configure a copy count of more than 512.
• Multicast Queue Management
Multicast queue management provides a CLI configuration to specify which queues are used for
round-robin based load balancing of multicast traffic. It also helps to reduce buffer overflow
conditions.
Using the existing QoS profile configuration, you can set the priority of the queues selected for load
balancing. For best system performance, it is advisable to use the same priority to set all the queues
being used.
RADIUS Attributes Support for Tunnel Attributes
The following RADIUS attributes are supported in ExtremeWare 7.4. These attributes are included in
RADIUS accounting start and stop packets.
• Tunnel-type—VLAN (13)
• Tunnel-medium-type—802
• Tunnel-Private-Group-ID—VLANID
The RADIUS server sends these attributes to the switch to communicate the destination VLAN of the
user in the RADIUS Accept message.
When a RADIUS Accept packet is received, the attributes of the packet are parsed and Tunnel-Type,
Tunnel-Medium-Type, and Tunnel-Private-Group-ID attributes are stored.
Tunnel-Private-Group-ID carries the VLAN ID in a string format. Using the VLAN ID, the VLAN name
is derived and used to identify the destination VLAN of the user.
The value for Tunnel-Type must be 13. The value for Tunnel-Medium-type must be 6 for 802 type
networks. Tunnel-Private-Group-ID is used for the destination VLAN of a supplicant only when
Tunnel-Type and Tunnel-Medium-Type match the values stated above.
Entity MIB
The entity physical table of the entity MIB represents various physical entities present in a device. Some
entities are classified as Field Replaceable Units (FRUs). Currently, the odometer feature is available for
these FRU entities in the CLI. A private MIB module, EXTREME-ENTITY-MIB, is used to implement the
odometer feature.
NOTE
The power supply units are not part of the entity MIB at this time. When the PSUs are added to the
ENTITY-MIB, the corresponding odometer value (if any) is added to the extremeEntityFRUTable.