Resolved issuesfor 6100 Switchesin AOS-CX 10.09.1040

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

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

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. Thisissue 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: 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.

Symptom: Spanning-Tree fails to block a loop and the network experiences congestion when access ports are connected to a Cisco switch.

Scenario: When A Cisco switch running PVST+ is mistakenly looped to an Aruba switch running RPVST, the Aruba switch will fail to recognize the proprietary PVST+ BPDUs and will not put the port in a blocked state. This allows the loop to persist which spikes switch CPU and reduces performance of the network. This is due to Aruba switch expecting IEEE standard BPDUs rather than the Cisco proprietary ones.

Workaround: Apply an ACL to block looped traffic.

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: Run any OSPF show command once every 48 days or fewer.

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: Performing any copy operations for configurations/checkpoints including issuing the commandcopy running-config startup-configorwrite memory, takes a long time and then fails due to a timeout.

Scenario: This issue is caused by a race condition, and although it is not trigged by any specific configuration, it has been known to occur on VSX deployments more frequently .

Workaround: Perform a reload of the hpe-config servicesystemctl restart hpe-config.

Symptom: For SNMP v3 users configured in AOS-CX 10.8 (or before) if the switch migrates to AOS-CX 10.9 (or later), network administrators won’t be able to use the configured SNMP v3 for WR operations.

Scenario: This issue occurs in a deployment with SNMP v3 users configured in AOS-CX 10.8 (or before) after the switch migrates to AOS-CX 10.9 (or later)

Workaround: To resolve this issue:

1. Use SNMP v2 for any SNMP WR operations needed in 10.9 (or after).
2. Add a config line to enable RW for the given SNMP v3 user(s).
3. Execute the CMF scriptsnmp_access_level.pywhich will migrate the SNMP V3 user with the prior permission. The FT to validate the CMF script migration istest_ft_CMF_snmp_access_level.py.