Release Notes

15
Cisco Prime DCNM Release Notes, Release 7.0.(2)
OL-31385-01
Caveats
• CSCul07068
Symptom: When a switch is discovered, the mgmt0 interface is not shown in the Interface listing
page for the switch.
Conditions: Always.
Workaround: There is no workaround.
• CSCum62685
Symptom: From POAP definitions, if user edits a definition, goes through all the steps, and finally
publishes it, and then tries to go to DFA topology, the screen becomes blank and unresponsive.
The same issue occurs when POAP definition is saved and published, then the user navigates to the
DFA screen.
Conditions: When the POAP definition is saved or edited and published and the user goes to DFA
topology screen.
Workaround: Doing a browser reload (clicking the reload button on the browser being used) fixes
the issue.
Open Caveats—Prime NSC adapter Release 1.0.1
• CSCum80871
Symptom: Some tenants or networks are missing in NSC after addingVM-mgr for a deployment
where VM-mgr has existing tenants or networks.
Conditions: When a VM-mgr is added to a Prime NSC instance where VM-mgr has tenants or
networks already present. In some cases, all the tenants or networks are not synced to Prime NSC.
Workaround: Remove the NSC instance using nsc-adapter-mgr nsc remove <ip> comman and
then add the NSC instance again using nsc-adapter-mgr nsc add <ip-address> <user-name>
<password> command.
• CSCum55604
Symptom: Upon restarting the NSC adapter, the adapter connections command shows "initializing"
state.
Conditions: This happens when one of the NSC instance specified in config.ini file is unreachable
due to NSC load.
# /opt/nscadapter/bin/nsc-adapter-mgr adapter connections
Workaround: Using the GUI login, verify the NSC instance reachability. Identify the NSC instance
where GUI is not reachable to find out if NSC is unreachable even though pingable. Then follow
these steps:
1. Stop the NSC adapter.
2. Remove the incorrect NSC instances using CLI.
3. Start NSC adapter.
CONNECTION STATUS REASON
dcnm inactive Initializing