Enterasys Networks X-PEDITION E9.1.7.0 - Manual (Page 16)

NEW FEATURES AND ENHANCEMENTS IN E9.1.7.0
10/02/03 P/N: 9038090-53 Subject to Change Without Notice Page: 16 of 31
F0615-J
NEW FEATURES AND ENHANCEMENTS IN E9.1.7.0:
NEW FIRMWARE SUPPORT
The E9.1.7.0 system firmware provides support for the new features and enhancements below. For more
information on any of these enhancements, please see the Enterasys X-Pedition User Reference Manual or
Native CLI Reference Manual.
10-Gig Support of Link Aggregation
SmartTRUNK no protocol link aggregation is now supported on 10-Gig interface modules (ER16-OS26-01 and
ER16-OS16-01). This capability permits users to aggregate two or more 10-Gig interfaces and removes the
restriction previously identified as F3493. No support for DEC Hunt Group or 802.3ad (LACP) is provided at this
time although 10-Gig compatibility with 802.3ad is planned for a subsequent release.
PIM-SM Support of 802.1Q trunks
Compatibility between PIM-SM multicast routing and 802.1Q trunks is now provided allowing users to utilize PIM-
SM multicast capabilities on interfaces with 802.1Q tagged packets.
AppleTalk Features
Two new AppleTalk capabilities are introduced with this release: QoS and CPU utilization.
All ingress and egress AppleTalk traffic is normally passed through the system on the low priority queue. Using a
CLI command, one can now specify which of the four X-Pedition queues (control, high, medium or low) will carry
AppleTalk egress traffic thus providing a measure of outbound QoS control.
Introduced in this release is an informational error message that is generated when the CPU utilization of the
Advanced Routing Engine (ARE), which supports AppleTalk data forwarding, exceeds 95% for one minute.
File Delete Command Enhancement
For ER16 or 8x00 systems configured with two control modules, users may now delete files from the backup
control module using the file delete command.
Display of Host Name in Syslog Messages
Introduced in this release is an improvement to Syslog message output that includes the host name. The
message format is <###> Mmm dd hh:mm:ss HOSTNAME MESSAGE where:
Mmm dd – month and day
hh:mm:ss – hour:minute:second
HOSTNAME – the name of the host machine
MESSAGE – the actual message