Information About Licensing a Cisco DCNM-LAN Deployment
This section includes the following topics:
Cisco DCNM-LAN Licensing
When you install the Cisco DCNM-LAN server, you initially install the software without applying a license. Many of the features of Cisco DCNM-LAN do not require a license. If you try to use a feature that does require a license, Cisco DCNM-LAN displays a message that indicates that a license is required by that feature. To use licensed features, you must install the Cisco DCNM LAN Enterprise license.
To use licensed Cisco DCNM-LAN features with Cisco Nexus 7000 Series switches, you must purchase a DCNM LAN Enterprise license. To use licensed Cisco DCNM-LAN features with other supported Cisco Nexus Series switches, you can obtain a DCNM LAN Enterprise license at no cost.
Table 1-2 shows the Cisco DCNM-LAN features and requirements for a DCNM LAN Enterprise license. Table 1-1 shows the legend for the table of features and requirements.
Table 1-1 Table Legend
|
|
X |
No license required. (Works without a license.) |
$0 |
No cost license. (License for DCNM LAN is required, but has no fee.) |
$$ |
Not free license. (License for DCNM LAN Enterprise is required with fee.) |
N/A |
Feature not applicable. |
Table 1-2 Cisco DCNM-LAN Features and DCNM License Requirements
|
|
|
|
|
Port/Port Channel |
X |
X |
X |
X |
Virtual Port Channel |
$$ |
$0 |
N/A |
N/A |
FEX Port Pinning |
N/A |
X |
N/A |
N/A |
LACP |
X |
X |
X |
X |
VLAN 802.1q/PVLAN |
X |
X |
X |
X |
STP (MST, RPVST) |
X |
X |
X |
X |
ACL (MAC, IP, VLAN) |
X |
X |
X |
X |
Traffic Storm Control |
X |
X |
X |
X |
AAA |
X |
X |
X |
X |
Environmental (hardware resource utilization with TCAM statistics) |
X |
X |
X |
X |
Module Temperature |
X |
N/A |
X |
X |
SPAN |
X |
X |
X |
X |
Discovery and Inventory |
X |
X |
X |
X |
L1 and L2 Topology Map |
X |
X |
X |
X |
Fault Management |
X |
X |
X |
X |
Traffic Statistics Reports |
X |
X |
X |
X |
RBAC |
X |
X |
X |
X |
Serial over LAN / Wake on LAN / Trunk Failover / Chassis Internal Network.g |
N/A |
N/A |
X |
X |
Web Services and Java API |
X |
X |
X |
X |
Virtual Device Context |
$$ |
N/A |
N/A |
N/A |
802.1X |
$$ |
$0 |
$0 |
$0 |
GLBP, Object Tracking, Key Chain |
$$ |
$0 |
$0 |
$0 |
HSRP |
$$ |
$0 |
$0 |
$0 |
Cisco Integrated Security Features (DHCP Snooping, Dynamic ARP Inspection, IP Source Guard) |
$$ |
$0 |
$0 |
$0 |
Port Security |
$$ |
$0 |
$0 |
$0 |
Tunnel Interface |
$$ |
$0 |
$0 |
$0 |
Configuration Change Control (arch, roll-back and diff) |
$$ |
$0 |
$0 |
$0 |
OS Image Management |
$$ |
$0 |
$0 |
N/A |
For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the “Installing Licenses on a Primary Cisco DCNM-LAN Server” section.
Primary Server Licensing Installation
You perform a primary server license installation when you are installing Cisco DCNM-LAN licenses for either of the following two purposes:
- You are licensing a single-server Cisco DCNM-LAN environment.
- You are installing licenses on the primary Cisco DCNM-LAN server in a clustered-server environment.
A primary server license installation uses the Cisco DCNM installer wizard. After you have provided the license file location to the installer wizard, it installs the licenses on the primary server.
A primary server license installation also creates the licenses-installer.properties file in the INSTALL_DIR /dcm/dcnm/config directory. This file is for use during the secondary server license installation with all of the secondary servers that are in the server cluster that the primary server belongs to. On a Microsoft Windows server system, the default INSTALL_DIR value is C:\Program Files\Cisco Systems. On a RHEL server system, the default INSTALL_DIR value is /usr/local/cisco.
Secondary Server Licensing Installation
You perform a secondary server license installation when you are installing Cisco DCNM-LAN licenses on all secondary servers in a clustered-server environment.
Note If you license a clustered-server Cisco DCNM-LAN deployment, each server in the cluster must have the same license files installed. For more information, see the “Clustered-Server Configuration Requirements” section.
A secondary server license installation is a silent installation. The installer does not prompt you for information. You provide a path to the directory that contains the license files when you run the installer from a command prompt. You also specify the license-installer.properties file that was created when you installed the primary server in the cluster that the secondary server belongs to.
Installing Licenses on a Primary Cisco DCNM-LAN Server
You can install Cisco DCNM-LAN licenses on a primary Cisco DCNM-LAN server.
After you install licenses, you must specify which managed devices that the licenses apply to before you can use Cisco DCNM-LAN licensed features with those devices. For more information, see the Cisco DCNM Fundamentals Guide, Release 5.x.
Note Each server in a Cisco DCNM-LAN server cluster must have the same license files installed. For more information, see the “Clustered-Server Configuration Requirements” section.
DETAILED STEPS
Step 1 Log into the primary Cisco DCNM-LAN server system.
Step 2 Download the license pack file that you received from TAC into a directory on the server system.
Caution
Make sure that there are no other executable files in the directory where you download the license pack file. Having other files in the directory where you download the license pack file can disrupt the installation of the licenses.
Step 3 Go to the directory where you downloaded the Cisco DCNM-LAN server software and run one of the following files:
- For Microsoft Windows, run the dcnm-k9. release.exe file.
- For RHEL, use the following sh command:
Step 4 Click Next when the Introduction step appears in the Cisco DCNM installer window.
Step 5 Click Next when the Please Read Before Continuing information appears in the Cisco DCNM installer window.
Step 6 When the Choose Install Folder step appears in the Cisco DCNM installer window, do the following:
a. Check the DCNM-LAN checkbox.
b. Click Next.
A warning dialog box indicates that an existing installation of the Cisco DCNM-LAN server was found.
Step 7 Click OK.
The Reinstall step appears in the Cisco DCNM installer window.
Step 8 Choose License Install and click Next.
The Choose Cisco DCNM License Folder step appears in the Cisco DCNM installer window.
Step 9 In the Please Choose a Folder field, enter or choose the folder that contains the license file, and then click Next.
The Pre-Installation Summary step appears in the Cisco DCNM installer window. The License files(s) field shows the licenses that the Cisco DCNM installer found in the folder that you specified.
Step 10 Click Next.
The Install Complete step appears in the Cisco DCNM installer window.
Step 11 Click Done.
You can now specify the managed devices that you want to use licensed Cisco DCNM-LAN features with. For more information, see the Cisco DCNM Fundamentals Guide, Release 5.x.
Installing Licenses on a Secondary Cisco DCNM-LAN Server
Depending on the operating system of the secondary server of a clustered-server environment, you can install licenses using the CLI or the DCNM Install Manager tool. You can use the CLI or the DCNM Install Manager tool for a secondary server running RHEL. For a secondary server running Microsoft Windows, you install licenses with the CLI.
Installing Licenses with the CLI
This section describes how to install licenses on a secondary Cisco DCNM-LAN server system of a clustered-server environment. Secondary server license installations use a silent installation method, which requires the use of a command line interface—for Microsoft Windows, a command prompt window, and for RHEL, a shell window.
The Cisco DCNM installer creates the DCNM_InstallLog.log file in the home directory of the user account that you use to install licenses on the secondary server. You can determine the success of the secondary server license installation by monitoring the DCNM_InstallLog.log file.
Note Each server in a Cisco DCNM-LAN server cluster must have the same license files installed. For more information, see the “Clustered-Server Configuration Requirements” section.
BEFORE YOU BEGIN
You must have installed the licenses on the Cisco DCNM-LAN server software on the primary server system. The license-installer.properties file, required for secondary server license installation, is created during primary server license installation.
Note Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that might interfere with the installation of the Cisco DCNM-LAN server software. After you complete the installation, reenable the software or features.
DETAILED STEPS
Step 1 From the primary Cisco DCNM-LAN server system, get the following:
- A copy of the license-installer.properties file from the following location:
INSTALL_DIR /dcm/dcnm/config
On a Microsoft Windows server system, the default INSTALL_DIR value is C:\Program Files\Cisco Systems. On a RHEL server system, the default INSTALL_DIR value is /usr/local/cisco.
- A copy of the license pack file(s).
Step 2 Log into the secondary server with a user account that has the required privileges, as follows:
- For Microsoft Windows, the user account must be a member of the local administrators group.
- For RHEL, the user account must be root.
If you are installing Cisco DCNM-LAN on Microsoft Windows and using Remote Desktop Connection (RDC) to access the Cisco DCNM-LAN server system, start RDC from a command prompt and use the /console option, as follows:
C:\>mstsc /console /v:server
where server is the DNS name or IP address of the Cisco DCNM-LAN server system.
Step 3 Choose a directory and copy the following files to that directory:
- The license-installer.properties file that you copied from the primary Cisco DCNM-LAN server system.
- The Cisco DCNM-LAN server software that you downloaded.
Step 4 Choose a second directory and copy to that directory the license pack file(s) from the primary server system.
Caution
Make sure that there are no other executable files in the directory that you copy the license pack file(s) to. Having other files in the directory where you download the license pack file can disrupt the installation of the licenses.
Step 5 At a command prompt, change directories as needed to ensure that the working directory is the directory that contains the license-installer.properties file and the Cisco DCNM-LAN server installer software. On Microsoft Windows, use the chdir command without arguments to display the working directory. On RHEL, use the pwd command.
Step 6 Run the applicable command as follows:
- For Microsoft Windows:
dcnm-k9. release .exe -i silent -f license-installer.properties -DLICENSE_FOLDER = license_directory
- For RHEL:
sh dcnm-k9. release .bin -i silent -f license-installer.properties -DLICENSE_FOLDER = license_directory
For example, to install licenses on a secondary Cisco DCNM-LAN Release 5.0(2) server on a Microsoft Windows server system that has license files in the directory C:\DCNMlic, the installation command is as follows:
dcnm-k9.5.0.2.exe -i silent -f license-installer.properties -DLICENSE_FOLDER=C:\DCNMlic
Table 1-3 describes the command syntax.
Table 1-3 Secondary Server License Installation Command Syntax
|
|
-i silent |
Specifies that the installation is silent. |
-f license-installer.properties |
Specifies the license-installer.properties file. |
-DLICENSE_FOLDER = license_directory |
Specifies the full path to the directory that contains the Cisco DCNM-LAN license pack file(s) that you received from Cisco. |
Step 7 Monitor the DCNM_InstallLog.log file to determine the status of the license installation. The Cisco DCNM installer writes the log file to the home directory of the current user account.
Installing Licenses with Install Manager
DCNM Install Manager is a GUI tool for servers running Linux. It is designed to assist in performing silent mode operations on secondary servers (remote nodes).
Note DCNM Install Manager does not support Windows servers.
Note Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that might interfere with the license install of the Cisco DCNM-LAN server software. After you complete the license install, reenable the software or features.
DETAILED STEPS
Step 1 To access Install Manager, navigate to the dcnm-install-manager.sh file that is located in the bin folder where the DCNM-LAN server was installed.
The default bin folder location for servers running Linux is /usr/local/Cisco/dcm/dcnm/bin.
Step 2 Double click the dcnm-install-manager.sh file to launch Install Manager.
Step 3 In the DCNM Installer Folder drop-down list, choose the path that contains the binary executable file for DCNM-LAN server installation.
Step 4 In the DCNM License Folder drop-down list, choose the path that contains the license file for the DCNM-LAN server.
Step 5 In the toolbar, click the New icon in the toolbar near the top of the Install Manager GUI for every secondary server.
A new row in the list of Server Nodes is created every time that the New icon is clicked.
Note Click the Delete icon in the toolbar to delete a selected row in the list of Server Nodes. This action does not delete a secondary server from the clustered-server environment.
Step 6 For each secondary server represented by a row in the list of Server Nodes, enter the following:
- Server name or IP address in the Server Name/IP Address field.
- Protocol used for connectivity in the Protocol field.
The protocol is either Telnet or SSH.
- User credentials (user ID and password) used for connecting to the secondary server in the User Credentials field.
The user credentials are used for SSH connectivity to the server. Telnet connectivity to the server does not require user credentials.
Alternatively, default user credentials can be set by entering the credentials in the Default Credentials section of the GUI. The default credentials are used when the User Credential field is blank.
- (Optional) Comments that might be useful to identify the secondary server in the Comments field.
The Last Action Status column in the list of Server Nodes includes the success or failure status of the last performed action. Clicking the + icon for the Last Action Status expands the display to show the entire log of actions performed on the server.
Step 7 In the list of Server Nodes, choose the secondary servers to perform the license install.
Step 8 In the toolbar, click the Verify icon to verify the connectivity to the selected secondary servers.
Correct any connectivity issues before continuing the license install.
Step 9 (Optional) In the DCNM Install Location field, enter the path on the secondary server for the license install of the DCNM-LAN server.
If the DCNM Install Location field is blank, the Install Manager uses the default path, /usr/local/Cisco/dcm, for the license install of the DCNM-LAN server.
Step 10 In the toolbar, click the License Install icon to begin the installation on the selected secondary servers.
Step 11 Monitor the Last Action Status column to determine the status of the license install.
In addition, you may also review the DCNM_Installer_Manager.log file. This file, located at /root/.dcnm, contains the log for all the operations of the Install Manager.
If the license installation operation fails on a secondary server, the installation log of the secondary server is automatically copied to /usr/local/Cisco/dcm/FailureLog_<SECONDARY_SERVER_IP_ADDRESS>.log on the primary server, where <SECONDARY_SERVER_IP_ADDRESS> is the IP address of the secondary server.
Note The Install Manager is a standalone application. The settings specified are not saved and are not persistent. The settings are lost when the Install Manager GUI is closed.