Cisco
Prime DCNM and other applications in the OVA have connectivity issues; a
noticeable drop in ping packets are directed to the virtual appliances.
|
The
datastore used by Cisco Prime DCNM virtual appliance may be almost full or
full. The VM performance is compromised and unpredictable.
|
-
Free
up datastore space and then reboot the Cisco Prime DCNM OVA.
-
Make
sure that the IP address for the Cisco Prime DCNM management access and
Enhanced Fabric Management networks are in different subnets.
-
If
they are not in different subnets, redeploy the OVA.
-
Enter different subnets for the Cisco Prime DCNM management
access and Enhanced Fabric Management networks.
|
The OVA is
successfully deployed, but either the Cisco Prime DCNM management access or
Enhanced Fabric Management interface is down.
|
The IP
addresses for Cisco Prime DCNM and Enhanced Fabric Management networks are in
the same subnet.
|
-
Make
sure that the IP address for the DCNM management access and Enhanced Fabric
Management networks are in different subnets.
-
If
they are not in different subnets, redeploy the OVA.
-
Enter different subnets for the Cisco Prime DCNM management
access and Enhanced Fabric Management networks.
|
Cisco
Prime DCNM is not accessible from the Web UI. The following message is
displayed:
System Message: DCNM(pid
22094) process running, but may not be accessible from Web UI.
|
Cisco
Prime DCNM is starting due to a scheduled restart or due to an appliance
reboot.
|
- After waiting a few minutes,
use the
appmgr status
dcnm command to determine if Cisco DCNM is still not accessible.
-
Use
the
appmgr start
dcnm command to start Cisco Prime DCNM.
- Review the server logs at the
following location:
/usr/local/cisco/dcnm/
/jboss-4.2.2GA/server/fm/log/server.log
|
Users are
unable to log in to the Cisco Prime DCNM Web UI.
|
The
password does not meet security requirements.
|
Make sure
that the administrative password created during the OVA deployments meets
password security criteria. For version 7.0.1, redeploy the OVA with a new
password.
The
password must meet the following requirements:
-
Eight
characters in length
-
A
combination of alpha and numeric characters
-
Limited to include only the following special characters
-
.
(dot)
-
+
(plus)
-
_
(underscore)
-
-
(hyphen)
|
The Cisco
DFA view in the Cisco Prime DCNM Web UI is taking too long to load.
|
A large
number of devices are managed with a local/packaged Postgres database;
significant delays can occur in load times.
|
- Verify the number of devices
managed by Cisco DFA.
- If the number of devices
managed by Cisco DFA exceeds 50 devices, make sure that you are using an
external Oracle Database.
See
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/7_x/dcnm/installation/master_files/OVA_Installation_Guide.html for instructions on configuring the Oracle
database for Cisco Prime DCNM.
|
The
IP address field does not display a fourth octet.
|
Your
monitor resolution is not properly set.
|
Change
your monitor display settings to a higher resolution.
|
DHCPD
crashes if a /8 subnet is entered.
|
An /8
subnet is in use. We recommend that you do not use a /8 subnet; this is a
problem with the DHCPD that is packaged as part of the DCNM bundle.
|
If DHCPD
crashes, you must manually restart it by using an SSH terminal session in DCNM.
|
The
creation of a network fails.
|
DHCPD
may already be employed for that network. DHCPD does not allow overlapping
subnets, even if they are created across different virtual routing and
forwarding (VRF) instances.
|
Ensure
that the new network does not have a subnet that conflicts with an existing
network.
|
Configuration-profile instantiation or application errors
|
Conflicting Profiles Exists
|
Use the following commands to debug the log file:
sh system internal config-profile history
debug logfile fabric-autoconfig
debug fabric forwarding auto-config all
copy log:fabric-autoconfig bootflash:
debug logfile port-profile
debug port-profile all
copy log:port-profile bootflash:
|