|Installer launch issues.
||Ensure Cisco DCNM installation requirements are met before proceeding with the installation.
|"Choose another location to extract the files to…" error occurs.
||The installer could be corrupted. Try downloading the installer from the Cisco website and then restart the installation.
|Windows 216 error and cannot execute binary file error in Linux occurs.
||You may be installing a 64-bit installer on 32-bit platform.
|DCNM-SAN Server failed to start after installation.
- Browse to <DNCM_HOME>\fm\bin and start #service.bat FMServer server manually.
- Browse to fmserver.conf file:
Change: wrapper.java.additional.12=-XX:MaxPermSize=512m to wrapper.java.additional.12=-XX:MaxPermSize=256m.
- On Microsoft Windows at <DCNM_HOME>\dcm\fm\conf\fmserver.conf
- On Linux at <DCNM_HOME>/dcm/fm/conf/fmserver.conf
- Restart the server.
|Unable to launch the DCNM-SAN Client after installation.
- Possible cause for this issue is that the recommended memory settings are not met for Cisco DCNM installation.
- Try installing the Cisco DCNM in the recommended setup and launch the Cisco DCNM-SAN Client.
|JBOSS Server startup failure. After installing Cisco DCNM, the JBOSS server startup fails with an exception:
creating identity: <HOST_NAME> at org.jboss.remoting.
deployment.DeploymentException: - nested throwable:
- The \etc\hosts file does not contain the correct entries.
- Edit the etc/hosts file to map the loopback address with the hostname.
- The etc/hosts file should contain the hostname (in addition to whatever is already present in the file).
For example, host-ip <space> host-name.
|JBOSS Server startup failure in Secondary Node - After installing Cisco DCNM in the secondary node, DCNM failed to start.
||This issue is seen in Release 5.2(2a) and resolved in Release 5.2(2c). Download the latest installers from the Cisco website and upgrade to the latest release.||
- Add the property as FM_SERVER_INSTALLED=FALSE in the "installer.properties" file that was copied from master node.
- Trigger the silent mode installation using the command in secondary node.
PostgreSQL installation issues— An "init db" error occurs due to file system.
Cisco DCNM Installation failed during PostgreSQL installation and an "init db"error appears, and the installation is aborted.
- Check that the file system is present. It might be FAT/FAT32.
- PostgreSQL installation requires an NTFS file system, and will fail on a FAT/FAT32 file system. The NTFS file system is more reliable than FAT/FAT32 file system. Check your file system before starting the DCNM installation.
PostgreSQL installation issues— An "init db" permission-denied error appears.
Cisco DCNM installation failed during PostgreSQL installation and a permission-denied error appears.
- Check that the local user has administrator privileges. Only administrators can perform this task.
- Try installing PostgreSQL manually.
PostgreSQL installation issues—Cisco DCNM installation failed during the PostgreSQL installation on Linux.
The following error is displayed in the database options screen:
Shared memory settings are low for
- PostgreSQL installation requires a minimum of 256 MB of shared memory. You can view them at /proc/sys/kernel/shmmax.
- The shared memory settings can be increased using the sysctl -w kernel.shmmax=268435456 command.
Oracle or Oracle RAC issues—"No appropriate service handler found" exception occurs.
Cisco DCNM installation failed to add a node in SAN Federation using Oracle as the Database.
This exception occurs in the SAN Server log:
"java.sql.SQLException: Listener refused the
connection with the following error:ORA-12519,
TNS:no appropriate service handler found"
- This exception occurs when the "concurrent db processes" is limited by the database. Ensure that the number of concurrent connections is set according to the requirement.
- Cisco DCNM recommends a minimum of 150 sessions.
- The connections can be increased using the following command in the sqlplus.exe prompt:
alter system set processes=150 scope=spfile
|Oracle or Oracle RAC issues—"Table or view does not exist" exception occurs.
||The database user might not have the privileges to create schema or tables. Ensure that the Oracle or Oracle RAC database user has the required privileges and continue with the installation of Cisco DCNM.
|Oracle or Oracle RAC issues—"Network Adapter could not establish connection" exception occurs.
- This error is displayed when the entries for Oracle RAC setup are not entered in these hosts file.
- Linux– /etc/hosts
- Microsoft Windows – C:\WINDOWS\system32\drivers\etc\hosts
- Ensure that you enter the Oracle RAC VIP (virtual IP address ) and host-ip in the hosts file.
|Unauthorized port scanner–After installing Cisco DCNM in an Linux environment, pnsscan multi-threaded port scanner attempts to scan the entire network.
||The operating system probably had a virus attack.
|Login issue in DCNM-LAN–After installing Cisco DCNM, and when the DCNM-LAN and DCNM-SAN are launched, the following error is displayed:
"Authentication Failure: Invalid username/password"
|Reset the login password using the pwreset tool under <DCNM_HOME>\dcm\dcnm\bin.
||For Linux, configure x-windows to display the pwreset GUI. For more information, see http://www.hungry.com/~jamie/xexport.html.|
|Port conflicts while installing Cisco DCNM.
- Ensure that you stop the firewall, security agent, antivirus, and so on before continuing with the installation. This blocks the port for security constraints.
- To stop the Windows firewall, use the following command:
- OFF: netsh adfirewall set allprofiles state off
- ON: netsh adfirewall set allprofiles state on
- We recommend that you install only Cisco DCNM Server in the server for better performance and to avoid port conflict issues.
- When you change the naming service port during installation, enter the port in DCNM-SAN client as follows:
<HOST_IP_ADDRESS> : < NAMING _SERVICE _ PORT >
- When you change the naming service port during installation, click More (<< More) to enter the port in the DCNM-LAN client.
|Chose Install Directory field and the DB User credentials fields grayed out during recent install with PostgreSQL.
- Previous DCNM and PostgreSQL uninstallation was not complete.
- Delete the postgreSQL service.
Install Cisco DCNM after deleting the following files:
- Windows–C:\Program Files\Zero G Registry\.com.zerog.registry.xml <USER_HOME>\.cisco_mds9000
- Linux–/var/.com.zerog.registry.xml /root/.cisco_mds9000
|Cisco DCNM authentication fails in cluster or federation mode. After Cisco
DCNM is installed in cluster or federation mode, you can log in
to the Cisco DCNM WEB GUI and DCNM SAN Client but cannot log in to DCNM LAN Client. The following error message is displayed:
- The multicast addresses used during the installation of the cluster nodes are not correct.
- Verify that the multicast addresses used are correct by following this procedure:
- Navigate to the following location:
On Windows– <DCNM_HOME>\jboss-4.2.2.GA\server\dcnm\lib
On Linux– <DCNM_HOME>/jboss-4.2.2.GA/server/dcnm/lib
- Execute the following command on all the four DCNM cluster nodes:
java -cp jgroups.jar org.jgroups.tests.McastReceiverTest -mcast_addr multicast_addrress1 -port port1 -bind_addr dcnm-server-ip-address
||Multicast_address1, and port1 are paired values and will be used on all of the machines together.|
||You will not see the output after executing the command if the multicast addresses are wrong.|
- Resolve the multicast addresses by following this procedure:
Go to < DCNM_HOME > \ dcm \ jboss-4.2.2.GA \ server \ dcnm\ deploy \ jboss-web-cluster.sar \META-INF \ jboss-service.xml, and change the multicast IP address:
Go to < DCNM_HOME > \ dcm \ jboss - 4.2.2. GA \ server\ dcnm \ deploy \ cluster-service.xml , and change the multicast IP address:
Go to < DCNM_HOME > \ dcm \ jboss-4.2.2.GA \ server\ dcnm \ deploy \ dcnm-cache-service.xml, and change the multicast addresses:
|Federation nodes are in an inactive state in the Cisco DCNM web GUI under Admin > Federation.
||Ensure that the master and slave nodes are running at the same time and restart the Cisco DCNM Servers.
Launching the web client or other clients (DCNM-LAN
and DCNM-SAN java web start clients fails).
When Cisco DCNM is installed on a new Windows 2008
server. By default, the firewall settings are enabled and you will not be able to launch the web client from any other
server machine (other then the machine where Cisco DCNM servers are
Turn off the
default firewall or create appropriate rules to allow the ports specified
during Cisco DCNM installation.
|Oracle backup script fails in Oracle 11g and the following error message is displayed:
"ORACLE error 12546 encountered. TNS
permission denied. EXP-00000. Export terminated
| When this error message is displayed, the Cisco DCNM Log packager tool stops backing up the Oracle database. Try the following:
- Ensure that you have not logged in to the Linux system as a "root" user.
- Log in as a DB user used during Oracle 11G installation and execute the backup script.
IPv6 on Microsoft Windows 2008
|By default, IPv6 is enabled on Windows 2008 systems. Ensure that you disable IPv6 before you start installing Cisco DCNM. To disable IPv6, see http://support.microsoft.com/kb/929852.