Resolved issuesfor 8400 Switchesin Version 10.08.1080

Symptom: RADIUS disconnect requests failed with the error CONTEXT_NOT_REMOVABLE.

Scenario: This issue is related to timing, Configure concurrent onboarding enabled and default priority enabled. This issue occurs if a user issues a disconnect request for a client after MACauth is successfull, but dot1x authentication is still in-progress.

Workaround: Avoid issuing a disconnect request until the highest priority authentication method is completed. Check theoutpt of theshow aaa authentication port-access interface all client-statuscommand to verify the both the auth-methods are complete. Disconnect the request once higher priority methods are complete.

Symptom: In some rare cases the switch will reboot or crash when a user issues theclear arp vrf ipcommand.

Scenario: When theclear arp vrf ipcommand is issued memory can be accessed incorrectly.

Symptom: A rare intermittent error occurs in an NAE agent action callback where the container for executing the callback could not be created.

Scenario: This issue can occur intermittently when running NAE agent action callbacks.

Workaround: NAE and the agent will continue to function as expected without any intervention. This single action callback that the error occurred in will be lost, but all of the other ones will persist and be executed as expected.

Symptom: A password is not applied after after a json config import if the user config contains a user password and an authorized key.

Scenario: This issue occurs when a configuration containing a user account with both a password and an authorized key is applied and the running-config contains a different password for the same user.

Symptom: An unexpected loop is detected by the loop protect feature resulting in ports getting improperly blocked. A similar problem has been experienced in a square topology, while VSX members are still coming up and It has also been experienced when the ISL link between VSX members is toggled.

Scenario: In a square topology, reboot the primary/secondary VSX peers. or toggle the ISL link and observe that the loop protect feature has blocked ports even though the network topology itself has not changed.

Workaround: Disable loop-protect temporarily, ensure all VSX peers are in a stableestablishedstate. and then enable loop-protect. Running two protocols (RPVST and loop-protect) for the same purpose (l2 loop detection) is not recomended. Loop detection via RPVST is the recommended choice as it detects and mitigates loops per VLAN. Note, however, if loop-protect detects any loop even for one VLAN it will bring down the full link. This will block traffic for all VLANs.

Symptom: Event logs are flooded withPFC TLV status inactive on interfacemessages.

Scenario: When a peer device continuously sends DCBX packets and LLDP is enabled on the local switch, the messagePFC TLV status inactive on interfaceis flooded in the event logs.

Workaround: Either disable the DCBX on the peer device or enable the DCBX on the local device to match the configuration with the peer device.

Symptom: A mismatch occurs between the uptime shown in the output ofshow ospfcommands and the BGP state reflected the event log.

Scenario: This issue occurs if no OSPF show commands are executed for 49 days or more

Workaround：每48天或更少一次运行任何OSPF Show命令。

Symptom: A mismatch between uptime shown byshow bgpcommands and the BGP state is reflected in the event log.

Scenario: This issue occurs if no BGP show commands were run for 49 days

Workaround: Run any BGP show command once every 48 days or fewer.

Symptom: Logs are flooded with unnecessary errors about empty value DB writes.

Scenario:这个问题发生在AOS-CX写空值s defined in the schema to the DB.

Symptom: An IPTV channel change causes momentary freeze or pixelization.

Scenario: This issue occurs when two IPTVs watch the same channel. If one IPTV changes the channel, other IPTV experience pixelization issue.