Specifications

ExtremeXOS 12.4.1 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 59

● Known Behaviors on page 71

● Resolved Issues in ExtremeXOS 12.4.1 on page 74

Open Issues

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

following sections:

Table 39: Platform-Specific and Feature PDs

PD Number Description

General

PD4-1095776451 An Extreme switch is unable to make a connection if the managment IP is in VR Default.

Workaround: XML notifications only work on the Management VR.

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-1185907951,

PD4-1023079871

Disabling learning on a VLAN results in LACP packets being dropped.

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-757870353 Running diagnostics on the master MSM generates errors such as subsection reported as

failed, conduit errors, and HAL.IPv4FIB/HAL.IPv6FIB. These log messages do not appear

to have any impact on the successful completion of diagnostics on the master MSM.

PD4-749280880 Installing firmware fails and displays the following message:

tftp: server says: Wrong TFTP State

PD4-718946965 Directed broadcast traffic is not being forwarded.

PD4-740255437 Policy files are not refreshed when generating 30,000 rules.

PD4-749682632 You cannot run the configure port auto on command on XGM2-2bt ports.