Installation guide

Acopia Networks, Inc.

Known Anomalies

This release contains the following known anomalies.

Problem Description

Alarming error messages and

logs appear during a firmware

upgrade. (19365, 26774)

The following message appears in the CLI after you invoke and

confirm a firmware upgrade:

ARXa6K# firmware upgrade all

Confirmation of this command commences a firmware upgrade

on the entire chassis. During the upgrade process, the

chassis reboots automatically to complete the upgrade

process.

Proceed? [yes/no] yes

ARXa6K#

REDUNDANCY requires this switch to reboot.

Reason: Paired NSM cores (0x530031, 0x530021) both failed.

Switch reboot is prevented due to a firmware upgrade in

progress. The system will retry every 10 seconds. Service

failover is delayed until firmware upgrade is complete.

Standby.

These messages are expected. The NSM processors (called “cores”)

are rebooting to load the new firmware. Additionally, the ARX sends

SNMP traps (and, possibly E-mail alerts) to alert you to the rebooting

processors.

You can safely ignore all of these alerts until the firmware upgrade is

complete. You can use the show firmware upgrade command to

check the current status of the firmware upgrade.

Incorrect GUI prompt appears

when you remove a Windows

Mgmt. ACL. (26107)

If you go to Authentication -> Windows Mgmt. ACLs in the GUI,

you have the option to remove any of the ACLs. An incorrect prompt

appears in the confirmation pop-up; it warns about deleting an NTLM

Auth. Server instead of the Windows Mgmt. ACL.

The show global-config output

does not contain permit all any

entries for windows-mgmt-auth

groups. (26557)

When the global-config is replayed, members of a Windows-

Management Authorization (WMA) group may lose all access through

MMC. That is, a group that previously had full access would be left

without any permissions to access the ARX volume(s) through MMC.