Resolved issuesfor 6100 Switchesin AOS-CX 10.10.0002

Symptom: Routes missing after moving from AFC to NetEdit as a configuration tool.

Scenario: This issue occurs in a deployment with AFCand Net edit where config might be modifying/updating a NULL default Port VRF UUID to the actual UUID of the Port VRF.

Workaround: Perform a关闭/no shuton the interfaces.

Symptom: From the CLI, one of the following errors will be seen:

• Could not copy image.
• Could not access primary switch image.
• Could not access secondary switch image.

Scenario: After updating the software image via the WebUI, copying or uploading a firmware image off the switch or to USB may fail when using a different user account than used to update via the WebUI.

Workaround:

Option 1) Copy or upload the switch firmware image to a remote source using the same user account as was originally used to update the firmware via the WebUI.

Option 2) Re-download the switch firmware image using TFTP, SFTP, SCP, or USB using any administrator user account.

Symptom: If there are two or more LAGs attached to the same hardware ID, software will be configured with two different LAGs but they both will share the hardware instance. Hence, one of the LAG ports does not pass any traffic because of the missing hardware ID.

Scenario: This issue is observed in the following scenario:

1. Create a dynamic LAG 10int lag 10 lacp mode active no shut

2. Create a dynamic LAG 20 int lag 20 lacp mode active no shut. At this point, lag10 will have hardware ID as1and lag20 has hardware ID as "2".

3. Convert lag10 as a static LAG.int lag 10 no lacp mode active step

4. Create another LAG 30int lag 30 lacp mode active no shutAt this point, lag10 and lag30 will share the same hardware ID "1".

Workaround: Delete one lag10 and create it again.

Symptom:在某些配置,RPVST inconsistencies may be encountered.

Scenario: When a 3rd party devices, such as a WAN Optimizer is in-path between switches in the same RPVST domain, and there is also a failure path, the might be inconsistencies in RPVST domain.

Symptom: The switch does not list the configured DNS servers in the order they were entered.

Scenario: When the switch is configured with multiple DNS server using theip dns-server-address command, the configuration is incorrectly listed in the output of theshow ip dnscommand.

Workaround: This is a display issue. The DNS servers are correctly programmed based in the order of configuration.

Symptom: CPU usage spikes.

Scenario: This issue can occur when continuous IGMP control packets from multicast clients are sent a high rate.

Workaround: Identify the groups causing the spike and apply an ACL using the command:ip igmp snooping apply access-list ip igmp apply access-list .