解决的问题for 8320 Switchesin AOS-CX 10.09.1040

Symptom：日志充斥着关于空的DB写入的不必要的错误。

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

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

Scenario：当对等设备在本地交换机上连续发送DCBX数据包和LLDP时，消息时PFC TLV status inactive on interface在事件日志中被淹没。

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: 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：在NAE代理操作回调中发生了罕见的间歇性错误，无法创建用于执行回调的容器。

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: 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 ip发出命令的内存可能会错误地访问。

Symptom: An SNMP trap is sent when a fan fails, but no event log is seen.

Scenario:A single I2C read fails on a fan. The differing logic between the SNMP trap code and the event log code will cause the SNMP trap to be sent, but not the event log.

Workaround：使用SNMP陷阱来确定风扇是否失败。

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无法阻止循环，当访问端口连接到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：在输出中显示的正常运行时间之间发生不匹配show ospf命令和BGP状态反映了事件日志。

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 bgp命令和BGP状态反映在事件日志中。

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：在OOBM端口上报告了IPv4配置的高CPU利用率。

Scenario：如果将无效的默认网关（0.0.0.0）添加到OOBM端口，则会发生此问题，该端口导致OVSDB交易加载CPU。

Workaround：从OOBM端口删除默认网关0.0.0.0配置，并为网络添加正确的网关IPv4地址

Symptom: Port-vlan membership was missing in ASIC for all VLANs, and traffic lose was observed.

Scenario：在Port-VLAN成员配置之后发生了VLAN UP触发器，在这种情况下，一些Port-VLAN会员资格缺失，并且没有在ASIC中编程。

Workaround: Unconfigure VLAN memberships, create VLANs, then configure VLAN membership with a port.

Symptom: Performing any copy operations for configurations/checkpoints including issuing the commandcopy running-config startup-config或者write memory，花费很长时间，然后由于超时而失败。

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重新启动HPE-Config.

Symptom：对于在AOS-CX 10.8（或之前）配置的SNMP V3用户，如果交换机迁移到AOS-CX 10.9（或更高版本），网络管理员将无法将已配置的SNMP V3用于WR操作。

Scenario：此问题发生在开关迁移到AOS-CX 10.9（或更高版本）之后的SNMP V3用户的部署中

Workaround: To resolve this issue:

1. 使用SNMP V2进行10.9（或之后）中所需的任何SNMP WR操作。
2. 添加配置行以启用给定SNMP V3用户的RW。
3. Execute the CMF scriptsnmp_access_level.py将在先前的权限下迁移SNMP V3用户。验证CMF脚本迁移的FT是test_ft_CMF_snmp_access_level.py.