Specifications

ExtremeXOS 12.4.2 Release Notes

3 Open Issues, Known Behaviors, and Resolved

Issues

This chapter describes items needing further clarification and behaviors that might not be intuitive. It

also includes the items that have been resolved. The numbers shown in column one of the following

tables are for internal reference and can be ignored.

This chapter contains the following section:

● Open Issues on page 61

● Known Behaviors on page 72

● Resolved Issues in ExtremeXOS 12.4.2 on page 77

● Resolved Issues in ExtremeXOS 12.4.1-patch1-5 on page 81

● Resolved Issues in ExtremeXOS 12.4.1-patch1-4 on page 82

● Resolved Issues in ExtremeXOS 12.4.1 on page 84

Open Issues

Following are the open issues for supported features in ExtremeXOS 12.4.2. They are organized into the

following sections:

Table 39: Platform-Specific and Feature PDs

PD Number Description

General

PD3-57182431 For the incoming traffic with alignment errors, the "RX Align" counter in the output of the

show ports <port number> rxerrors command is not incremented. Instead the

"RX CRC" counter is incremented.

PD3-71725881 When configuring an optional name for the time zone/DST, the time zone name truncates

at seven characters. The system default is six characters.

PD4-813961562 When a service VLAN is changed to include a dot1q tag on both sides in CFM VPLS, the

RMEP entry is not learned on one side.

PD4-1194741135 setDynamicAc.pl, which is used to create a dynamic ACL and bind it to a specific port, is

not working.

Workaround: The following SOAP element corrects this issue.

SOAP::Data->name("applicationName" => "Cli"));

PD4-910088928 The following error message is displayed when downgrading a switch from ExtremeXOS

12.3 or later to ExtremeXOS 12.2 or earlier.

Error: child process exited abnormally.

PD4-749060484 Errors are seen when a configuration having identifiers (SNMPv3 user name/EAPS domain

name) with special characters are loaded through a script.

PD4-561358261 If you create a super VLAN and a sub-VLAN in different virtual routers you are able to

bind the VLANs. Super VLANs and sub-VLANs should belong to the same virtual router.