Cisco Cisco Nexus 9000v Switch Release Notes

Cisco Nexus 9000 Series NX-OS Release Notes, Release 7.0(3)I2(4)
Caveats
13
Record Number
Description
BGP Inconsistent flags 0x900002 when host routes add it.
The flap of one lane is affecting the other and repeated sh/no shuts is causing all the lanes to go
down. PSM4 tcvrs see flaps in 50g and 25g mode.
down. PSM4 tcvrs see flaps in 50g and 25g mode.
A link goes up when inserting SFP without cables.
Remove snmp-server and rmon configuration by pipe and include option.
PBR Object-tracking with \"set ip default verify-availability\" does not work.
The system encounters multiple aclqos process hap resets/crashes. The system could fail to
communicate/forward traffic as a result of this problem:
communicate/forward traffic as a result of this problem:
%$ VDC-1 %$ %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "aclqos" (PID 2826) hasn't caught signal
11 (core will be saved).
11 (core will be saved).
%$ VDC-1 %$ %VMM-2-VMM_SERVICE_ERR: VDC1: Service SAP Aclmgr SAP for slot 1 returned error
0x41040037 (Linecard aclqos client crash) in if_bind sequence
0x41040037 (Linecard aclqos client crash) in if_bind sequence
%$ VDC-1 %$ %SYSMGR-SLOT2-2-SERVICE_CRASHED: Service "aclqos" (PID 2804) hasn't caught signal
11 (core will be saved).
11 (core will be saved).
%$ VDC-1 %$ %SYSMGR-SLOT2-2-SERVICE_CRASHED: Service "aclqos" (PID 2826) hasn't caught signal
11 (core will be saved).
11 (core will be saved).
%$ VDC-1 %$ %VMM-2-VMM_SERVICE_ERR: VDC1: Service SAP Aclmgr SAP for slot 2 returned error
0x41040037 (Linecard aclqos client crash) in if_bind sequence
0x41040037 (Linecard aclqos client crash) in if_bind sequence
When trying to get output for "show logging last xxx" then "Internal error in displaying logfile -
40540001\n" returned in nxapi.
40540001\n" returned in nxapi.
Some of the commands like switchport, or no switchport, or channel-group X mode active, will take 3-
4 minutes to apply. The bringup of the link takes additional time, and when it comes back up, the mac
addresses are sometimes incorrectly learned on individual interfaces instead of port-channel.
4 minutes to apply. The bringup of the link takes additional time, and when it comes back up, the mac
addresses are sometimes incorrectly learned on individual interfaces instead of port-channel.