Cisco DCNM Installation and Licensing Guide, Release 6.x
Installing Cisco DCNM Management Software
Downloads: This chapterpdf (PDF - 187.0KB) The complete bookPDF (PDF - 2.12MB) | Feedback

Table of Contents

Installing Cisco DCNM Management Software

Information About Installing the Management Software

Minimum Hardware Requirements

Installing Cisco DCNM on Windows and Linux using the GUI

Copying Certificates

Collecting PM Data

Collecting Log Files

Installing Cisco DCNM Using the Silent Installer

Running Cisco DCNM Behind a Firewall

Cisco DCNM Server Proxy Services

Modifying a Windows Workstation

Installing Cisco DCNM Management Software

This chapter describes how to install Cisco DCNM components and includes the following sections:

Information About Installing the Management Software

To install the software for the first time, or if you want to update or reinstall the software, access the supervisor module with a web browser. Click the Install links on the web page that is displayed. The software running on your workstation is verified to make sure that you are running the most current version of the software. If it is not current, the most recent version is downloaded and installed on your workstation.


Note Before upgrading or uninstalling Cisco DCNM or Device Manager, make sure that any instances of these applications have been shut down.


Installation options are as follows:

  • Fresh Installation—The installer installs Cisco DCNM-LAN, Cisco DCNM-SAN and the SMI-S agent on your system.
  • Upgrade—The installer detects your current version of Cisco DCNM and Device Manager, and it provides the option to upgrade. The default is to upgrade to the latest version of Cisco DCNM.

Minimum Hardware Requirements

For a PC running Cisco DCNM Server on large fabrics (1000 or more end devices), we recommend that you use a dual core/dual CPU high-speed system with 6 GB of RAM and 10 GB of free disk space.

Installing Cisco DCNM on Windows and Linux using the GUI

If the PostgreSQL database is not present on your computer, the installer installs PostgreSQL8.3. You can change the default credentials after the installation is complete.


Note When installing or upgrading Cisco DCNM federation or cluster with different subnets, Cisco DCNM-LAN and Cisco DCNM-SAN services do not start at the end of the Cisco DCNM installation. You must start the Cisco DCNM services manually using the shortcuts available under ../dcnm/fm/bin. Cisco DCNM-LAN does not support nodes when they are in different subnets.


Cisco DCNM has two executables, one for 32-bit and one for 64-bit.


Note Before you execute the installer, ensure that you create a database user with a user role and assigned schema. If you are using the Oracle database, a mapped schema is already created. If you are using a PostgreSQL database, ensure that you ctreate a new schema with the exact string as the new username and that the new user is the schema owner.


DETAILED STEPS


Step 1 Go to the directory where you downloaded the Cisco DCNM software and run the dcnm-release.exe file.

After the installer prepares the installation, the Introduction step appears in the Cisco DCNM installer window.

Step 2 Click Next when the Introduction step appears in the Cisco DCNM installer window after the installer prepares the installation.

Step 3 Click Next when the Please Read Before Continuing information appears in the Cisco DCNM installer window.

Step 4 Enter the following when the Choose Install Folder step appears in the Cisco DCNM installer window:

a. (Optional) If you want to add the server to the existing federation, check the Add Server to an existing server federation checkbox.

b. (Optional) If you want to change the default installation folder, enter or choose the desired installation folder.

c. Click Next.

As part of the Cisco DCNM installation, one of the following options are displayed according to your system requirements.

  • New installation—The installer installs Cisco DCNM-LAN, Cisco DCNM-SAN, and SMI-S for the first time.

Note From Release 6.1(2), Cisco DCNM supports nodes (SAN federation and LAN clustering) and the database in different subnets.


  • Upgrade Cisco DCNM-LAN and Cisco DCNM-SAN—The installer discovered a previous version of Cisco DCNM-LAN and DCNM-SAN. The installer upgrades to the latest version of Cisco DCNM-LAN and DCNM-SAN, and installs the SMI-S agent.
  • Upgrade Cisco DCNM-LAN—The installer discovered a previous version of Cisco DCNM-LAN. The installer upgrades to the latest version of Cisco DCNM-LAN and installs the Cisco DCNM-SAN and SMI-S agent.
  • Upgrade Cisco DCNM-SAN—The installer discovered a previous version of Cisco DCNM-SAN. The installer upgrades to the latest version of Cisco DCNM-SAN and SMI-S agent. As part of this upgrade process, Cisco DCNM-LAN is also installed.
  • Skip installation—The latest version of Cisco DCNM-LAN and Cisco DCNM-SAN already exists, so the installer skips the installation.

The Database Options step appears in the Cisco DCNM installer window. You can use an existing PostgreSQL installation or an existing Oracle installation. If PostgreSQL is not installed on the server system, you can use the Cisco DCNM installer to add a PostgreSQL installation.

Step 5 If you want to install PostgreSQL, do the following:


Note When you install PostgreSQL with Cisco DCNM, the database admin username and password is the same as the database username and password appended with 123. For example, if your database username is dcnmuser, the admin username is dcnmuser123. Similarly, if the database password is dcnmtest, the admin password is dcnmtest123.



Note • On Linux—If you want install PostgreSQL, ensure you have a non-root privileged user called postgres in the server. If you have not created a non-root privileged user, the installer will prompt you to create one and if you skip entering the details, the installer will automatically create a user called postgres with non-root privileges.

  • On Linux—To allow remote access to the database, modify the pg_hba.conf file and restart the postgres service using the command <dbroot>/bin/pg_ctl.

a. Next to RDBMS, click Install PostgreSQL .

If your server system runs RHEL, the System User dialog box appears.

b. (RHEL only) In the System User dialog box, enter the username for the user account that should be used to run the PostgreSQL software. This user account should not have administrator or root privileges.

c. In the DCNM DB User field, enter the username that Cisco DCNM-LAN should use to access the database. The default username is dcnmuser. The installer creates the user account that you specify.

d. In the DCNM DB Password field, enter the password for the database user account that you specified.

e. In the Confirm DCNM DB Password field, reenter the password for the database user account that you specified.

f. (Optional) If you want to change the default PostgreSQL database installation folder, in the Install Location field, enter or choose the desired installation folder.

Step 6 If you want to use an existing relational database management system (RDBMS) installation, do the following:

a. Next to RDBMS, click one of the following:

Use existing PostgreSQL 8.1/8.2/8.3

Use existing Oracle 10g/11g

Use Oracle RAC

If the Cisco DCNM installer detected an existing RDBMS installation, the DB URL field shows the hostname.


Note Cisco DCNM installation with existing Postgres requires an existing schema with the same name as the dcnm username, owned by the same username. When there are no schemas existing with the dcnm username or if you do not have the ownership of the schema with the same dcnmuser name, the tables get created in the default schema called public.



Note In Oracle, when a new user is created, a schema name with the same name as the username is created automatically.


b. If the DB URL field does not have the correct URL to the database, enter the correct URL.


Note The database is not automatically created. You must manually create the database. A valid database URL is required to create a database schema and connect to it.


c. In the DCNM DB User field, enter the username that Cisco DCNM should use to access the database.

d. In the DCNM DB Password field, enter the password for the database user account that you specified.

Step 7 Click Next .

The Configuration Options step appears in the Cisco DCNM installer window.

Step 8 If you want to use an existing Oracle 10g/11g RAC, do the following:

a. Next to RDBMS, click the following:

Use the existing Oracle 10g/11g RAC

The Oracle RAC configuration dialog box appears.

b. In the Service Name field, enter the service name of the Oracle RAC server.

c. Enter a maximum of three host IP addresses. Click OK. The DB URL is generated.

Step 9 In the Configuration Options dialog box, do the following:


Note During Cisco DCNM installation, use port numbers that are not commonly used. For example, 87 and 23 are reserved or restricted web ports.


a. From the Server IP Address list, choose the IP address that you want to use for the Cisco DCNM server. The list shows only the IP addresses currently that are assigned to network interfaces on the server system.

b. If you want to change the port that the Cisco DCNM-LAN web server listens to, enter the new port number in the LAN Web Server Port field. By default, the Cisco DCNM-LAN web server listens to TCP port 8080.

c. If you want to change the port that the Cisco DCNM-SAN web server listens to, enter the new port number in the SAN Web Server Port field. By default, the Cisco DCNM-SAN web server listens to TCP port 80.


Note If you change the web server port number, it affects the URL that Cisco DCNM-LAN users use to download the Cisco DCNM-LAN client.


Step 10 If you want to change the port that the Cisco DCNM server accepts Cisco DCNM client connections on, under Advanced Settings, enter the new port number in the Naming Service Port field. By default, the Cisco DCNM server accepts connections from Cisco DCNM clients on TCP port 1099.

Step 11 (Optional) For the remaining service ports listed on the Configuration Options step, if you want to specify a different port number, follow these steps in Advanced Settings :

a. For each service port number that you want to change, enter the new port number in the field.

b. Click Resolve Port Conflicts .

If the Cisco DCNM installer detects that a port that you specified is already in use, it automatically assigns an unused port number to the service.

c. Click OK to save the Advanced Settings.

Step 12 Click Next to save the Configuration Options and the IP Multicast Addresses Configuration step appears in the Cisco DCNM installer window.


Note When you install DCNM in the federation mode, you need to update the multicast IP addresses and the partition name to enable cluster between the nodes. If you do not update the multicast IP addresses and partition name, the cluster formation will fail and the nodes will only be in the federation.


Step 13 (Optional) If you are installing the primary server for a Cisco DCNM server cluster, follow these steps:

a. In the Partition Name field, enter a unique name for a Cisco DCNM server cluster. The default partition name is the DCNM host instance ID. The name can contain alphanumeric characters only.

b. (Optional) As needed, change the multicast IP addresses. You might need to change the multicast IP addresses if the addresses provided by the installer are already in use in the routing environment of the Cisco DCNM server cluster.

c. (Optional) As needed, change the multicast ports. You may need to change the multicast ports if the port numbers provided by the installer are already in use on the server system that you are installing Cisco DCNM on.

Step 14 Click Next .

The Choose Archive Folder step appears in the Cisco DCNM installer window.

Step 15 Do one of the following:

    • If you are deploying a clustered-server Cisco DCNM environment, enter or choose the archive folder that you prepared for use by all the servers in the cluster.
    • If you are deploying a single-server Cisco DCNM environment, you can accept the default archive folder or choose the desired archive folder.

Step 16 Click Next .

The Local User Credentials step appears in the Cisco DCNM installer window.

Step 17 In the Local Admin Username field, enter a name for a Cisco DCNM server user. The installer creates the Cisco DCNM server user and assigns the Administrator role to it.

Step 18 In the Password field, enter a password for the user, and in the Confirm Password field, reenter the password.


Note We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.


Step 19 If you want to create a LAN admin user, do the following:

a. Check the Create LAN Admin User check box.

a. In the Local Admin Username field, enter a name for a Cisco DCNM-LAN server user. The installer creates the Cisco DCNM-LAN server user and assigns the Administrator role to it.

b. In the Password field, enter a password for the user, and in the Confirm Password field, reenter the password.

Step 20 If you want to create a SAN admin user, do the following:

a. Check the Create SAN Admin User check box.

a. In the Local Admin Username field, enter a name for a Cisco DCNM-SAN server user. The installer creates the Cisco DCNM-SAN server user and assigns the Administrator role to it.

b. In the Password field, enter a password for the user, and in the Confirm Password field, reenter the password.

Step 21 Click Next .

The Authentication Settings step appears in the Cisco DCNM installer window.

Choose the authentication method that the Cisco DCNM server should use to authenticate users who log into the Cisco DCNM client. You can choose one of the following:

    • Local —Cisco DCNM client users are authenticated by the Cisco DCNM server user accounts only.
    • RADIUS —Cisco DCNM client users are authenticated by a RADIUS server.
    • TACACS+ —Cisco DCNM client users are authenticated by a TACACS+ server.

Step 22 If you chose RADIUS or TACACS+, do the following:

a. In the primary server address field, enter the IPv4 address of the server in dotted-decimal format.

b. In the primary server key field, enter the shared secret of the server.

c. (Optional) If you want to ensure that Cisco DCNM can communicate with the server, click Verify .

d. In the secondary server address field, enter the IPv4 address of the server in dotted-decimal format.

e. In the secondary server key field, enter the shared secret of the server.

f. (Optional) If you want to ensure that Cisco DCNM can communicate with the server, click Verify .

g. In the tertiary server address field, enter the address of the server in the dotted-decimal format.

h. In the tertirary servery key field, enter the shared secret of the server.

i. (Optional) If you want to ensure that Cisco DCNM can communicate with the server, click Verify .

Step 23 Click Next .

If you are using Microsoft Windows, the installer asks you to specify a shortcut to the application. If you are using RHEL, the installer asks you to specify a link folder.

Step 24 Choose the shortcut or link options that you want.

Step 25 (Optional) If you want the installer to create the shortcuts for all users who can log into the server system, check the Create Icons for All Users check box.

Step 26 Click Next .

The Pre-Installation Summary step appears in the Cisco DCNM installer window.

Step 27 Carefully review the summary of your choices. If you need to change anything, click Previous until the Cisco DCNM installer window displays the step that you need to change, and then return to the applicable preceding step.

Step 28 Click Next when you are ready to install the Cisco DCNM server software.

The installer installs the Cisco DCNM server software.

The Installing Cisco DCNM installer window appears.

Step 29 Choose whether you want to start the Cisco DCNM server now. If you start the Cisco DCNM server now, a splash screen appears while the server starts.

The Install Complete step appears in the Cisco DCNM installer window. The Cisco DCNM instance ID number is displayed.

Step 30 (Optional) If you plan to order licenses for Cisco DCNM, record the Cisco DCNM instance ID number. The licensing process requires that you enter that number.


Note You can begin using Cisco DCNM without a license but some features are not available unless you purchase and install a license and apply the license to managed devices that you want to use licensed features with.


Step 31 Click Done .

Step 32 (Optional) If you want to install a Cisco DCNM license, see Chapter7, “Installing and Managing Licenses for Cisco Data Center Network Manager”


 

Copying Certificates

When you add a new Cisco DCNM instance to an existing federation or cluster, ensure you copy fmtrust.jks and fmserver.jks certificate files manually from any one of the nodes present in the Cisco DCNM federation or cluster.

You should get the certifcate files under the following folders:

  • On Microsoft Windows—<DCNM install folder>\dcm\jboss-4.2.2.GA\server\fm\conf
  • On Linux—<DCNM install folder>/dcm/jboss-4.2.2.GA/server/fm/conf

In the new node, you should copy the certifcate files under the following folders:

  • On Microsoft Windows—<DCNM install folder>\dcm\jboss-4.2.2.GA\server\fm\conf
  • On Linux—<DCNM install folder>/dcm/jboss-4.2.2.GA/server/fm/conf

Note Ensure you restart the Cisco DCNM servers after copying the certificate files.


Collecting PM Data

To setup a shared rrd path to collect PM data, perform these steps:


Step 1 Locate the server.properties file under C:\Program Files\Cisco Systems\dcm\fm\conf.

Step 2 Add the pm.rrdpath property file information to the server.properties file. For example, add the server location that needs to be accessible from the DCNM server.

Step 3 Save the server.properties file.

Step 4 Restart the Cisco DCNM-SAN server.


 

Once PM server is ready, the new shared location will be used by the PM server to save .rrd files. PM will create a new directory called db under pm. Ensure you do not open or change these .rrd files as PM server is actively writing into the .rrd files.

Collecting Log Files

Log files are needed to troubleshoot the Cisco DCNM installation.

Cisco DCNM-LAN and Cisco DCNM-SAN are installed under <DCNM_HOME>. The following are the default installation directories:

  • Microsoft Windows—C:\Program Files\Cisco Systems
  • Linux— /usr/local/cisco

Note In Microsoft Windows, when a Cisco DCNM 32-bit installer is used for installation in a 64-bit environment, the default installation directory is C:\Program Files <x86>\Cisco Systems.


Once the Cisco DCNM installation is complete, you can find the installer logs under:

  • Microsoft Windows—USER_HOME\dcnm_installer.log
  • Linux— /root/dcnm_installer.log

Note When you have several Cisco DCNM installations on the same machine, the installer preserves the logs with a timestamp. When the installation is done in the debug mode, the dcnm_installer.log file is not available.


The PostgreSQL install logs are available under:

  • Microsoft Windows—USER_TEMP_DIR\install-postgresql.log
  • Linux: /tmp/install-postgresql.log

The Cisco DCNM-LAN server logs are available under:

  • Microsoft Windows— DCNM_HOME\dcm\jboss\server\dcnm\logs
  • Linux—DCNM_HOME/dcm/jboss/server/dcnm/logs

The Cisco DCNM-SAN server logs are available under:

  • Microsoft Windows—DCNM_HOME>\dcm\jboss\server\fm\logs
  • Linux—DCNM_HOME/dcm/jboss/server/fm/logs

Installing Cisco DCNM Using the Silent Installer

Ensure that all the executable files are in one location and under one folder.

DETAILED STEPS


Step 1 To install Cisco DCNM on Microsoft Windows, execute the following:

executable filename -i silent -f installer.properties

Note The installer.properties file contains the attributes and the values required for Cisco DCNM installation on a node.


Step 2 To install Cisco DCNM on Linux, execute the following:

sh executable filename -i silent -f installer.properties

Note When installing Cisco DCNM using the silent installer, the default authentication mechanism is local. You can change the authentication mode in the Cisco DCNM-LAN and Cisco DCNM-SAN client.



 

You can find the Cisco DCNM silent installer properties file under the same folder where the Cisco DNCM executables are downloaded. The name of the properties files is DCNM-Silent-Installer-Properties-6.1.1.x.x.x.x.zip. For example, DCNM-Silent-Installer-Properties-6.1.1.SL1.0.140.S0.zip.

Example 4-1 Sample Silent Installer Response or Property File for Oracle and Linux

#-----------------BASIC Properties---------------------
#BASIC Properties will use the node IP
#address where DCNM will be installed (DCNM_IP_ADDRESS).
#Set the property that if its a fresh
#installation or upgrade (INSTALLATION_TYPE).
#Set the property to add the DCNM SAN node to existing
#SAN federation (SAN_FEDERATION).
#Set the property for DCNM running in HTTPS mode (USE_HTTPS)
#For upgrade case set only these properties
#
#
#Postgre+Oracle
#
#
#--------------------------------------------------------
#-----------------BASIC Properties---------------------
 
DCNM_IP_ADDRESS=10.64.66.194
INSTALLATION_TYPE=NEW_INSTALL
#INSTALLATION_TYPE=UPGRADE
SAN_FEDERATION=FALSE
#SAN_FEDERATION=TRUE
USE_HTTPS=FALSE
#USE_HTTPS=TRUE
 
 
#------------------DATABASE Properties--------------------
#User can configure these properties to use existing database or
# install fresh Postgres as database for the DCNM. Existing database
# can be postgres (remote or local), Oracle (remote or local)
# or it can be Oracle RAC.
#----------------------------------------------------
USE_EXISTING_DB=FALSE
#USE_EXISTING_DB=TRUE
PG_DB_PATH=/opt/oracle/app/product//10.2.0//server
#---------------Use Existing Oracle--------------
DCNM_DB_URL=jdbc/:oracle/:thin/:@<ip_address_of_oracle_machine>/:1521/:XE
DCNM_DB_NAME=XE
SELECTED_DATABASE=oracle
DCNM_DB_USERNAME=oracledbadmin1
DCNM_DB_USER_PASSWORD=oracledbadmin1
 
#------------------DATABASE Properties--------------------
 
 
#---------------------DATA PATH----------------
#Data path is the folder location where DCNM LAN related
#information like Config archives, templates etc. are stored.
# In DCNM LAN Cluster mode this folder has to be a shared folder.
#For linux and windows it will be different as the folder structure vaires
#----------------------------------------------------
 
DATA_PATH=/usr/local/cisco/dcm/dcnm
#---------------------DATA PATH----------------
 
 
#------------Port configuration Properties----------------------
#Configure the ports
#----------------------------------------------------
DCNM_SAN_SERVER_PORT=9099
DCNM_SAN_SYSLOG_PORT=5545
DCNM_SAN_JMS_PORT=5457
DCNM_SAN_WEB_SERVICES_PORT=9093
DCNM_SAN_EJB_SSL_PORT=3943
DCNM_SAN_RMI_OBJECT_PORT=24444
DCNM_SAN_INVOKER_BIND_PORT=5446
DCNM_SAN_WEB_PORT=80
DCNM_SAN_RMI_PORT=1198
DCNM_SAN_SERVER_BIND_PORT=5644
DCNM_SAN_AJP_CONNECTOR_PORT=9009
DCNM_SAN_EJB_PORT=3973
DCNM_INVOKER_BIND_PORT=4446
DCNM_EJB_SSL_PORT=3843
DCNM_SERVER_PORT=1099
DCNM_JMS_PORT=4457
DCNM_AJP_CONNECTOR_PORT=8009
DCNM_SYSLOG_PORT=5445
DCNM_WEB_PORT=8080
DCNM_SERVER_BIND_PORT=4445
DCNM_RMI_PORT=1098
DCNM_WEB_SERVICES_PORT=8083
DCNM_RMI_OBJECT_PORT=14444
DCNM_UIL2_PORT=8093
DCNM_EJB_PORT=3873
RESOLVE_PORT_CONFLICTS=FALSE
#------------Port configuration Properties----------------------
 
 
#------------DCNM LAN Cluster properties---------------------
#DCNM LAN Cluster properties
#----------------------------------------------------
DCNM_CLUSTER=FALSE
DCNM_IP_MULTICAST_ADDR4=239.228.32.24
DCNM_IP_MULTICAST_ADDR3=239.228.32.23
DCNM_IP_MULTICAST_ADDR2=239.228.32.22
DCNM_IP_MULTICAST_ADDR1=239.228.32.21
DCNM_IP_MULTICAST_PORT4=45504
DCNM_IP_MULTICAST_PORT3=45503
DCNM_IP_MULTICAST_PORT2=45502
DCNM_PARTITION_NAME=001EC9B84112
#------------DCNM LAN Cluster properties---------------------
 
#---------------Authentication mode-------------------------
#DCNM Authentication mode Properties
#----------------------------------------------------
AUTH_MODE=local
 
 
#----------------------------------------------------
 
#-----------------User Configuration-----------------
#DCNM User Configuration Properties
#If you want to use special characters in DCNM_ADMIN
#credentials,Please use escape character(\) before
#the symbol [For eg. Password "an$6x12" must be specified as "an\$6x12" ].
#----------------------------------------------------
 
DECRYPT_PASSWORDS=FALSE
DCNM_ADMIN_USER=admin
DCNM_ADMIN_USER_PASSWORD=admin
 
#-----------------User Configuration-----------------
 
#------------------DCNM Start/Stop Server-----------------------
#DCNM Start/Stop Server
#----------------------------------------------------
 
START_DCNM_COMMON=TRUE
#START_DCNM_COMMON=FALSE
#----------------------------------------------------
 
#-----------------BASIC Properperties---------------------
#BASIC Properperties will use the node IP
#address where DCNM will be installed (DCNM_IP_ADDRESS).
#Set the property that if its a fresh
#installation or upgrade (INSTALLATION_TYPE).
#Set the property to add the DCNM SAN node to existing
#SAN federation (SAN_FEDERATION).
#Set the property for DCNM running in HTTPS mode (USE_HTTPS)
#For upgrade case set only these properties
#
#
#Windows+Postgres
#
#
#--------------------------------------------------------

Example 4-2 Sample Silent Installer Response or Property File for Oracle and Windows

#-----------------BASIC Properties---------------------
#BASIC Properties will use the node IP
#address where DCNM will be installed (DCNM_IP_ADDRESS).
#Set the property that if its a fresh
#installation or upgrade (INSTALLATION_TYPE).
#Set the property to add the DCNM SAN node to existing
#SAN federation (SAN_FEDERATION).
#Set the property for DCNM running in HTTPS mode (USE_HTTPS)
#For upgrade case set only these properties
#
#
#Oracle+Windows
#
#
#--------------------------------------------------------
#-----------------BASIC Properties---------------------
 
DCNM_IP_ADDRESS=10.64.66.194
INSTALLATION_TYPE=NEW_INSTALL
#INSTALLATION_TYPE=UPGRADE
SAN_FEDERATION=FALSE
#SAN_FEDERATION=TRUE
USE_HTTPS=FALSE
#USE_HTTPS=TRUE
 
 
#------------------DATABASE Properties--------------------
#User can configure these properties to use existing database or
# install fresh Postgres as database for the DCNM. Existing database
# can be postgres (remote or local), Oracle (remote or local)
# or it can be Oracle RAC.
#----------------------------------------------------
USE_EXISTING_DB=FALSE
#USE_EXISTING_DB=TRUE
 
PG_DB_PATH=C:\\oraclexe\\app\\oracle\\product\\10.2.0\\server
#---------------Use Existing Oracle--------------
DCNM_DB_URL=jdbc\:oracle\:thin\:@<ip_address_of_oracle_machine>\:1521\:XE
DCNM_DB_NAME=XE
SELECTED_DATABASE=oracle
DCNM_DB_USERNAME=oracledbadmin1
DCNM_DB_USER_PASSWORD=oracledbadmin1
 
 
#------------------DATABASE Properties--------------------
 
 
#---------------------DATA PATH----------------
#Data path is the folder location where DCNM LAN related
#information like Config archives, templates etc. are stored.
# In DCNM LAN Cluster mode this folder has to be a shared folder.
#For linux and windows it will be different as the folder structure vaires
#----------------------------------------------------
DATA_PATH=C:\\Program Files\\Cisco Systems\\dcm\\dcnm
 
#---------------------DATA PATH----------------
 
 
#------------Port configuration Properties----------------------
#Configure the ports
#----------------------------------------------------
DCNM_SAN_SERVER_PORT=9099
DCNM_SAN_SYSLOG_PORT=5545
DCNM_SAN_JMS_PORT=5457
DCNM_SAN_WEB_SERVICES_PORT=9093
DCNM_SAN_EJB_SSL_PORT=3943
DCNM_SAN_RMI_OBJECT_PORT=24444
DCNM_SAN_INVOKER_BIND_PORT=5446
DCNM_SAN_WEB_PORT=80
DCNM_SAN_RMI_PORT=1198
DCNM_SAN_SERVER_BIND_PORT=5644
DCNM_SAN_AJP_CONNECTOR_PORT=9009
DCNM_SAN_EJB_PORT=3973
DCNM_INVOKER_BIND_PORT=4446
DCNM_EJB_SSL_PORT=3843
DCNM_SERVER_PORT=1099
DCNM_JMS_PORT=4457
DCNM_AJP_CONNECTOR_PORT=8009
DCNM_SYSLOG_PORT=5445
DCNM_WEB_PORT=8080
DCNM_SERVER_BIND_PORT=4445
DCNM_RMI_PORT=1098
DCNM_WEB_SERVICES_PORT=8083
DCNM_RMI_OBJECT_PORT=14444
DCNM_UIL2_PORT=8093
DCNM_EJB_PORT=3873
RESOLVE_PORT_CONFLICTS=FALSE
#------------Port configuration Properties----------------------
 
 
#------------DCNM LAN Cluster properties---------------------
#DCNM LAN Cluster properties
#----------------------------------------------------
DCNM_CLUSTER=FALSE
DCNM_IP_MULTICAST_ADDR4=239.228.32.24
DCNM_IP_MULTICAST_ADDR3=239.228.32.23
DCNM_IP_MULTICAST_ADDR2=239.228.32.22
DCNM_IP_MULTICAST_ADDR1=239.228.32.21
DCNM_IP_MULTICAST_PORT4=45504
DCNM_IP_MULTICAST_PORT3=45503
DCNM_IP_MULTICAST_PORT2=45502
DCNM_PARTITION_NAME=001EC9B84112
#------------DCNM LAN Cluster properties---------------------
 
#---------------Authentication mode-------------------------
#DCNM Authentication mode Properties
#----------------------------------------------------
AUTH_MODE=local
 
 
#----------------------------------------------------
 
#-----------------User Configuration-----------------
#DCNM User Configuration Properties
#If you want to use special characters in DCNM_ADMIN
#credentials,Please use escape character(\) before
#the symbol [For eg. Password "an$6x12" must be specified as "an\$6x12" ].
#----------------------------------------------------
 
DECRYPT_PASSWORDS=FALSE
DCNM_ADMIN_USER=admin
DCNM_ADMIN_USER_PASSWORD=admin
 
#-----------------User Configuration-----------------
 
#------------------DCNM Start/Stop Server-----------------------
#DCNM Start/Stop Server
#----------------------------------------------------
 
START_DCNM_COMMON=TRUE
#START_DCNM_COMMON=FALSE
#----------------------------------------------------
 

Example 4-3 Sample Silent Installer Response or Property File for Postgres and Linux

#-----------------BASIC Properties---------------------
#BASIC Properties will use the node IP
#address where DCNM will be installed (DCNM_IP_ADDRESS).
#Set the property that if its a fresh
#installation or upgrade (INSTALLATION_TYPE).
#Set the property to add the DCNM SAN node to existing
#SAN federation (SAN_FEDERATION).
#Set the property for DCNM running in HTTPS mode (USE_HTTPS)
#For upgrade case set only these properties
#
#
#Postgres+Linux
#
#
#--------------------------------------------------------
#-----------------BASIC Properties---------------------
 
DCNM_IP_ADDRESS=10.64.66.194
INSTALLATION_TYPE=NEW_INSTALL
#INSTALLATION_TYPE=UPGRADE
SAN_FEDERATION=FALSE
#SAN_FEDERATION=TRUE
USE_HTTPS=FALSE
#USE_HTTPS=TRUE
 
 
#------------------DATABASE Properties--------------------
#User can configure these properties to use existing database or
# install fresh Postgres as database for the DCNM. Existing database
# can be postgres (remote or local), Oracle (remote or local)
# or it can be Oracle RAC.
#----------------------------------------------------
USE_EXISTING_DB=FALSE
#USE_EXISTING_DB=TRUE
 
--------------New Postgress---------------------------
PG_DB_PATH=/usr/local/cisco/dcm/db
 
DCNM_DB_URL=jdbc\:postgresql\://localhost\:5432/dcmdb
DCNM_DB_NAME=dcmdb
SELECTED_DATABASE=postgresql
DCNM_DB_USERNAME=dcnmuser
DCNM_DB_USER_PASSWORD=dcnmuser
#------------Use Existing Postgres--------------
#DCNM_DB_URL=jdbc\:postgresql\://<ip_address_of_postgress_machine>\:5432/dcmdb
#DCNM_DB_NAME=dcmdb
#SELECTED_DATABASE=postgresql
#DCNM_DB_USERNAME=dcnmuser
#DCNM_DB_USER_PASSWORD=dcnmuser
 
 
#---------------------DATA PATH----------------
#Data path is the folder location where DCNM LAN related
#information like Config archives, templates etc. are stored.
# In DCNM LAN Cluster mode this folder has to be a shared folder.
#For linux and windows it will be different as the folder structure vaires
#----------------------------------------------------
DATA_PATH=/usr/local/cisco/dcm/dcnm
#---------------------DATA PATH----------------
 
 
#------------Port configuration Properties-----------------
#Configure the ports
#----------------------------------------------------
DCNM_SAN_SERVER_PORT=9099
DCNM_SAN_SYSLOG_PORT=5545
DCNM_SAN_JMS_PORT=5457
DCNM_SAN_WEB_SERVICES_PORT=9093
DCNM_SAN_EJB_SSL_PORT=3943
DCNM_SAN_RMI_OBJECT_PORT=24444
DCNM_SAN_INVOKER_BIND_PORT=5446
DCNM_SAN_WEB_PORT=80
DCNM_SAN_RMI_PORT=1198
DCNM_SAN_SERVER_BIND_PORT=5644
DCNM_SAN_AJP_CONNECTOR_PORT=9009
DCNM_SAN_EJB_PORT=3973
DCNM_INVOKER_BIND_PORT=4446
DCNM_EJB_SSL_PORT=3843
DCNM_SERVER_PORT=1099
DCNM_JMS_PORT=4457
DCNM_AJP_CONNECTOR_PORT=8009
DCNM_SYSLOG_PORT=5445
DCNM_WEB_PORT=8080
DCNM_SERVER_BIND_PORT=4445
DCNM_RMI_PORT=1098
DCNM_WEB_SERVICES_PORT=8083
DCNM_RMI_OBJECT_PORT=14444
DCNM_UIL2_PORT=8093
DCNM_EJB_PORT=3873
RESOLVE_PORT_CONFLICTS=FALSE
#------------Port configuration Properties-----------------
 
 
#------------DCNM LAN Cluster properties---------------------
#DCNM LAN Cluster properties
#----------------------------------------------------
DCNM_CLUSTER=FALSE
DCNM_IP_MULTICAST_ADDR4=239.228.32.24
DCNM_IP_MULTICAST_ADDR3=239.228.32.23
DCNM_IP_MULTICAST_ADDR2=239.228.32.22
DCNM_IP_MULTICAST_ADDR1=239.228.32.21
DCNM_IP_MULTICAST_PORT4=45504
DCNM_IP_MULTICAST_PORT3=45503
DCNM_IP_MULTICAST_PORT2=45502
DCNM_PARTITION_NAME=001EC9B84112
#------------DCNM LAN Cluster properties---------------------
 
#---------------Authentication mode-------------------------
#DCNM Authentication mode Properties
#----------------------------------------------------
AUTH_MODE=local
 
 
#----------------------------------------------------
 
#-----------------User Configuration-----------------
#DCNM User Configuration Properties
#If you want to use special characters in DCNM_ADMIN
#credentials,Please use escape character(\) before
#the symbol [For eg. Password "an$6x12" must be specified as "an\$6x12" ].
#----------------------------------------------------
 
DECRYPT_PASSWORDS=FALSE
DCNM_ADMIN_USER=admin
DCNM_ADMIN_USER_PASSWORD=admin
 
#-----------------User Configuration-----------------
 
#------------------DCNM Start/Stop Server-----------------------
#DCNM Start/Stop Server
#----------------------------------------------------
 
START_DCNM_COMMON=TRUE
#START_DCNM_COMMON=FALSE
#----------------------------------------------------
 

Example 4-4 Sample Silent Installer Response or Property File for Postgres and Windows

#-----------------BASIC Properties---------------------
#BASIC Properties will use the node IP
#address where DCNM will be installed (DCNM_IP_ADDRESS).
#Set the property that if its a fresh
#installation or upgrade (INSTALLATION_TYPE).
#Set the property to add the DCNM SAN node to existing
#SAN federation (SAN_FEDERATION).
#Set the property for DCNM running in HTTPS mode (USE_HTTPS)
#For upgrade case set only these properties
#
#
#Windows+Postgres
#
#
#--------------------------------------------------------
#-----------------BASIC Properties---------------------
 
DCNM_IP_ADDRESS=72.163.209.42
USER_INSTALL_DIR=C:\\Program Files\\Cisco Systems
INSTALLATION_TYPE=NEW_INSTALL
#INSTALLATION_TYPE=UPGRADE
SAN_FEDERATION=FALSE
#SAN_FEDERATION=TRUE
USE_HTTPS=FALSE
#USE_HTTPS=TRUE
 
 
#------------------DATABASE Properties--------------------
#User can configure these properties to use existing database or
# install fresh Postgres as database for the DCNM. Existing database
# can be postgres (remote or local), Oracle (remote or local)
# or it can be Oracle RAC.
#----------------------------------------------------
USE_EXISTING_DB=FALSE
#USE_EXISTING_DB=TRUE
 
PG_DB_PATH=C:\\Program Files\\Cisco Systems\\dcm\\db
 
----------New Postgres---------------------------------
DCNM_DB_URL=jdbc\:postgresql\://localhost\:5432/dcmdb
DCNM_DB_NAME=dcmdb
SELECTED_DATABASE=postgresql
DCNM_DB_USERNAME=dcnmuser
DCNM_DB_USER_PASSWORD=dcnmuser
#------------Use Existing Postgres--------------
#DCNM_DB_URL=jdbc\:postgresql\://localhost\:5432/dcmdb
#DCNM_DB_NAME=dcmdb
#SELECTED_DATABASE=postgresql
#DCNM_DB_USERNAME=dcnmuser
#DCNM_DB_USER_PASSWORD=dcnmuser
 
#------------------DATABASE Properties--------------------
 
 
#---------------------DATA PATH----------------
#Data path is the folder location where DCNM LAN related
#information like Config archives, templates etc. are stored.
# In DCNM LAN Cluster mode this folder has to be a shared folder.
#For linux and windows it will be different as the folder structure vaires
#----------------------------------------------------
DATA_PATH=C:\\Program Files\\Cisco Systems\\dcm\\dcnm
 
#---------------------DATA PATH----------------
 
 
#------------Port configuration Properties----------------------
#Configure the ports
#----------------------------------------------------
DCNM_SAN_SERVER_PORT=9099
DCNM_SAN_SYSLOG_PORT=5545
DCNM_SAN_JMS_PORT=5457
DCNM_SAN_WEB_SERVICES_PORT=9093
DCNM_SAN_EJB_SSL_PORT=3943
DCNM_SAN_RMI_OBJECT_PORT=24444
DCNM_SAN_INVOKER_BIND_PORT=5446
DCNM_SAN_WEB_PORT=80
DCNM_SAN_RMI_PORT=1198
DCNM_SAN_SERVER_BIND_PORT=5644
DCNM_SAN_AJP_CONNECTOR_PORT=9009
DCNM_SAN_EJB_PORT=3973
DCNM_INVOKER_BIND_PORT=4446
DCNM_EJB_SSL_PORT=3843
DCNM_SERVER_PORT=1099
DCNM_JMS_PORT=4457
DCNM_AJP_CONNECTOR_PORT=8009
DCNM_SYSLOG_PORT=5445
DCNM_WEB_PORT=8080
DCNM_SERVER_BIND_PORT=4445
DCNM_RMI_PORT=1098
DCNM_WEB_SERVICES_PORT=8083
DCNM_RMI_OBJECT_PORT=14444
DCNM_UIL2_PORT=8093
DCNM_EJB_PORT=3873
RESOLVE_PORT_CONFLICTS=FALSE
#------------Port configuration Properties----------------------
 
 
#------------DCNM LAN Cluster properties---------------------
#DCNM LAN Cluster properties
#----------------------------------------------------
DCNM_CLUSTER=FALSE
DCNM_IP_MULTICAST_ADDR4=239.228.32.24
DCNM_IP_MULTICAST_ADDR3=239.228.32.23
DCNM_IP_MULTICAST_ADDR2=239.228.32.22
DCNM_IP_MULTICAST_ADDR1=239.228.32.21
DCNM_IP_MULTICAST_PORT4=45504
DCNM_IP_MULTICAST_PORT3=45503
DCNM_IP_MULTICAST_PORT2=45502
DCNM_PARTITION_NAME=001EC9B84112
#------------DCNM LAN Cluster properties---------------------
 
#---------------Authentication mode-------------------------
#DCNM Authentication mode Properties
#-----------------------------------------------------------
AUTH_MODE=local
 
 
#-----------------User Configuration-----------------
#DCNM User Configuration Properties
#If you want to use special characters in DCNM_ADMIN
#credentials,Please use escape character(\) before
#the symbol [For eg. Password "an$6x12" must be specified as "an\$6x12" ].
#----------------------------------------------------
 
DECRYPT_PASSWORDS=FALSE
DCNM_ADMIN_USER=admin
DCNM_ADMIN_USER_PASSWORD=admin
 
#-----------------User Configuration-----------------
 
#------------------DCNM Start/Stop Server-----------------------
#DCNM Start/Stop Server
#----------------------------------------------------
 
START_DCNM_COMMON=TRUE
#START_DCNM_COMMON=FALSE
#----------------------------------------------------
 

Running Cisco DCNM Behind a Firewall

For Windows PCs running Cisco DCNM-SAN, Device Manager, behind a firewall, certain ports need to be available.

By default, Cisco DCNM-SAN Client and Device Manager use the first available UDP port for sending and receiving SNMP responses. The UDP SNMP trap local ports are 1162 for Cisco DCNM-SAN, and 1163 or 1164 for Device Manager. Cisco DCNM-SAN Server also opens TCP RMI port 4447.

In DCNM Release 5.0(1) or later releases, you can select the UDP port that Fabric Manager Client or Device Manager uses for SNMP responses by uncommenting the following statement:

  • On a Windows desktop, uncomment the following in the FabricManager.bat or DeviceManager.bat file in the C:\Program Files\Cisco Systems\MDS9000\bin directory:
rem JVMARGS=%JVMARGS% -Dsnmp.localport=9001
 
  • On a UNIX desktop, uncomment the following in the FabricManager.sh or DeviceManager.sh file in the $HOME/.cisco_mds9000/bin directory:
# JVMARGS=$JVMARGS -Dsnmp.localport=9001
 

From Cisco DCNM Release 6.3(1), DCNM San Client initiates communication with DCNM San Server on the following ports:

  • 4447 for Java Remoting,
  • 5457 and 5455 for Java Messaging Service.

DCNM proxy services use a configurable TCP port (9198 by default) for SNMP communications between the DCNM San Client or Device Manager and DCNM Server.

The DCNM San Server component requires two predictable TCP ports to be opened on the firewall for an incoming connection:

  • 4447 for Server
  • 9100 for Server Data

Note The Fabric Manager Client can connect to the server only if these two ports are open. Other TCP ports connected to DCNM San Client are initiated by the server, which is behind the firewall.


The following table lists all ports used by Cisco DCNM-SAN applications:

Communication Type
Port(s) Used
Used by All Applications

SSH

Port 22 (TCP)

Telnet

Port 23 (TCP)

HTTP

Port 80 (TCP)

TFTP

Port 69 (UDP)

SNMP

Port 161 (UDP)

Syslog

Port 514 (UDP)

Used by Cisco DCNM-SAN Server and Performance Manager

SNMP_TRAP

Port 2162 (UDP)

SNMP

Picks a random free local port (UDP) or 9198 (TCP) if SNMP proxy is enabled. Can be changed in server.properties.

Java Remoting

4447

Java Messaging

5457, 5455

Used by Cisco DCNM-SAN Client

SNMP

Picks a random free local port (UDP) if SNMP proxy is enabled. Can be changed with the client -Dsnmp.localport option.

Used by Device Manager

SNMP_TRAP

Picks a free local port between 1163 and 1170 (UDP).

SNMP

Picks a random free local port (UDP) or 9198 (TCP) if SNMP proxy is enabled. Can be changed in server.properties .

The following table lists all the ports and descriptions:

 

Port(s) Used/Type
Service Descriptor
Service Name
Attribute Name
Description

80 or 443

Standalone/configuration/standalone-san.xml

JBoss http (or https) port

http (or https ) service for webclient, SOAP and REST API

http (or https ) service for webclient, SOAP and REST API

4447

Standalone/configuration/standalone-san.xml

jboss:service=Remoting

Remoting Service Port

This port is for JNDI-based naming services. The client look up this port for JNDI-binding objects and resources.

5455

5457

Standalone/configuration/standalone-san.xml

Messaging Service

Unified Invocation Layer for JMS

This port is used for JMS services.

Cisco DCNM Server Proxy Services

The Cisco DCNM-SAN Client and Device Manager use SNMP to communicate with the Cisco DCNM-SAN Server. In typical configurations, the Cisco DCNM-SAN Server may be installed behind a firewall. The SNMP proxy service available in Cisco Fabric Manager Release 2.1(1a) or later releases provides a TCP-based transport proxy for these SNMP requests. The SNMP proxy service allows you to block all UDP traffic at the firewall and configure Cisco DCNM-SAN Client to communicate over a configured TCP port.

Cisco DCNM-SAN uses the CLI for managing some features on the switches. These management tasks are used by DCNM-SAN and do not use the proxy services. Your firewall must remain open for CLI access for the following features:

  • External and internal loopback test
  • Flash files
  • Create CLI user
  • Security—ISCSI users
  • Show image version
  • Show tech
  • Switch resident reports (syslog, accounting)
  • Zone migration
  • Show cores

If you are using the Data Mobility Manager (DMM) Wizard proxy service and another application on your server is using port 9198, you must modify your workstation settings.


Note The Cisco MDS 9000 family switch always checks the local SNMP users before the remote AAA users, unlike the CLI.


Modifying a Windows Workstation

DETAILED STEPS


Step 1 Open Internet Explorer and choose Tools > Internet Options.

You see the Internet Options dialog box.

Step 2 Choose the Connections tab and click LAN Settings.

You see the LAN Settings dialog box.

Step 3 Check the Use a Proxy Server for your LAN check box and click Advanced.

Step 4 Add your server IP address or local host under the Exceptions section.

Step 5 Click OK to save your changes.