Nexus Known Limitations 

To be included in the release notes:

1) VPC Domain ID limitation

2) Maintaining support for the Nexus family switches

Challenges: many different models and different NXOS versions may change the commands potentially breaking our scripts. Potential affected Alerts: 

• High ARP cache usages
• High neighbor discovery (ND) cache usage
• Maximum number of routes nearing (IPv4)
• Maximum number of routes nearing (IPv6)
• System resource usage high

3) Nexus Bugs: 

Conditions:
This was observed on a Nexus 7000 running 6.2(10).
Exact conditions are unknown. It is suspected that the affected code path can be invoked either via 'show' commands or via SNMP polling, but the exact commands or OIDs are currently not known.

This will be updated with additional information as the investigation into this issue progresses.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv29907/?referring_site=bugquickviewredir

4) Nexus Bugs reported by customer:

Info from Cisco:

The process crash was due to a memory leak caused by snmp walks to the switch.  This has been fixed with the following defect. 

CSCuy11918    N5K hap reset seen with fs-daemon due to signal 6

Symptom:

A Nexus5K switch may experience an unexpected reload due to a hap reset with fs-daemon service:

%SYSMGR-2-SERVICE_CRASHED: Service "fs-daemon" (PID 3694) hasn't caught signal 6 (core will be saved).

This has been seen on 7.1(0)N1(1a) and 7.1(2)N1(1) at this time and likely subject to change.

Conditions:

Continuous SNMP walk along with periodic execution of show CLIs is a known trigger for this issue. 

7.1(3)N1(4) and later

7.1(4)N1(1) and later

7.2(1)N1(1) and later

5) N3K experiences high CPU usage with Indeni - IKP-1497

N7K: Stale SSH sessions are seen if client is not sending close ack.

CSCue74597 Description

6) Cisco SSH issues - N9k

A number of known SSH related issues can potentially be show stopper.