Cisco nexus 5500 vm-fex software license

On the Cisco Nexus Series, you install and manage licenses on the physical device in the default virtual device context VDC 1. As with other Cisco NX-OS features, the licensing feature also maintains the following high-availability standards:. Installing a license automatically saves a copy of permanent licenses to the chassis.

If you have enabled the grace period feature, enabling a licensed feature that does not have a license key starts a counter on the grace period. You then have days to install the appropriate license keys, disable the use of that feature, or disable the grace period feature. If at the end of the day grace period the device does not have a valid license key for the feature, the Cisco NX-OS software automatically disables the feature and removes the configuration from the device.

The license software runs on both supervisor modules and provides failover protection. The license key file is mirrored on both supervisor modules. Even if both supervisor modules fail, the license file continues to function from the version that is available on the chassis. You can either obtain a factory-installed license only applies to new device orders or perform a manual license installation of the license applies to existing devices in your network.

If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you have existing devices or if you wish to install the licenses on your own, you must first obtain the license key file and then install that file in the device. Manual installation is not required.

The license key file is sent to you by e-mail and is digitally signed to only authorize use on the requested device. The requested features are also enabled once the Cisco NX-OS software on the specified device accesses the license key file. Do not make any modifications to the license key file. It will alter the digital signature and render the license invalid. A license is permanent. If you do not have a license, the grace period for using a feature starts from the first time you start using a feature offered by a license.

For information on user accounts and roles, see the Security Configuration Guide for your platform. If you have a single supervisor module on your Cisco NX-OS device and you replace the supervisor module, you must reinstall the license key file. If you are currently running with a grace period license to avoid service disruptions when you install your permanent license, do not disable the grace period by using the no license grace-period command.

Instead, just install your new license. The license manager will automatically transition from grace licensing to the installed license. If you provide a target name for the license key file, the file is installed with the specified name. Otherwise, the filename specified in the license key file is used to install the license.

If the license meets all guidelines when the install license command is used, all features and modules continue functioning as configured. You can use the show license brief command to display a list of license files installed on the device. You can use the show license file command to display information about a specific license file installed on the device.

If the configuration or bootflash memory on your device becomes corrupted, you might need to reinstall your license. You can do a reinstallation from a backed up copy of the license key file. If you do not have a license key file, you can create a copy of the license key file from your installed license. You cannot reinstall the license key file from the backed-up copy.

If you erase any existing licenses installed on your device, you can reinstall them only by using the install license command using the license key file. You can back up your license key file to a remote server or to an external device by using the copy command.

This example shows how to save a license key file to an external Flash device:. This example saves all licenses installed on your device to a. You can uncompress the.

You might have to enable a licensed feature to configure it. To enable a licensed feature, use the feature feature-name command in global configuration mode. For example, you can enable the BGP feature as follows:. Use the show license usage [ package-name ] command to identify all of the active features.

You can only uninstall a permanent license that is not in use. If you try to delete a permanent license that is currently being used, the software rejects the request and issues an error message. Product Specifications. Layer 2 Features. Layer 3 Features. High-Availability Features.

Data Center Bridging. Generic MIBs. Layer 3 MIBs. Fibre Channel MIBs. Ethernet MIBs. Configuration MIBs. Monitoring MIBs. Security MIBs. Miscellaneous MIBs.

Industry Standards. Fibre Channel Standards. Physical Specifications. The following SFP transceiver modules are supported by hardware in all ports of the Cisco Nexus platform:. Table 7. Power Supply Properties.

AC Power Supply Properties. Cisco Nexus P and UP. Cisco Nexus UP. Cisco Nexus T. Typical operating power. Maximum power Layer 2. Maximum power Layer 3. Input voltage. RoHS compliance. Hot swappable. Typical heat dissipation. Front-to-back air flow power supply. Back-to-front air flow power supply. Yes only on Cisco Nexus UP; need fan tray as well. DC Power Supply Properties. Table 8. Environment Properties. Cisco Nexus UP and T. Physical height x width x depth. Operating temperature.

Nonoperating storage temperature. Table 9. Cisco Nexus UP or T with two W power supplies, 3 unified port expansion modules, and 4 fan modules. Table 10 summarizes regulatory standards compliance for the Cisco Nexus platform. Table Regulatory compliance. EMC: Emissions. EMC: Immunity.

Table 11 presents ordering information for the Cisco Nexus platform. Ordering Information. Fan Modules.

Power Supplies. Cisco Nexus Blank module cover. Expansion Modules and Daughter Card. Nexus Layer 3 Daughter Card. Nexus Layer 3 Daughter Card, version 2. Procedures to be performed on the switch are described in this document. For procedures to be performed on the server or the VMware vCenter, refer to the server and vCenter documentation.

Switch: Configure two static vEthernet interfaces and bind them to the physical port and channel. See Configuring the Fixed Static Interfaces. Switch: Verify that the two static vEthernet interfaces are active and associated with the vEthernet interfaces of the switch.

See Verifying the Status of the Virtual Interfaces. Enables the virtualization feature set on the switch. This feature set enables the use of static vEthernet interfaces. This feature set enables the use of dynamic vEthernet interfaces. Optional vethernet auto-create. Globally enables the automatic creation of virtual Ethernet interfaces. This feature is not required if the fixed vEthernet interfaces are statically configured. Optional feature fcoe.

Optional end. Optional copy running-config startup-config. Optional reload. You can configure two physical interfaces and binds two virtual interfaces to each physical interface, creating fixed static vEthernet interfaces. With redundant switches, you can perform the following procedure with identical settings on both the primary and secondary switches. Shutting down the interface before enabling VN-Tag mode prevents the dynamic creation of a fixed vEthernet interface. The port channel numbers of the virtual interfaces must match those configured on the vNICs.

Enters configuration mode for the second virtual interface for the first Ethernet port. Enters configuration mode for the first virtual interface for the second Ethernet port.

Enters configuration mode for the second virtual interface for the second Ethernet port. With redundant switches, repeat this procedure with identical settings on the secondary switch. This example shows how to configure two physical interfaces, binds two virtual interfaces to each physical interface, and enables the interfaces:. Verify the status of the connection between the static interfaces and the static vNICs on the host server.

You can configure a port profile for dynamic virtual interfaces. Optional switchport mode access. Optional switchport access vlan vlan-id. Specifies the vCenter DVS to which the port profile is exported as a port-group. With the keyword all , the port profile is exported to all DVSs in the vCenter. Optional port-binding dynamic. Specifies dynamic port binding. The port is connected when the VM is powered on and disconnected when the VM is powered off.

Max-port limits are enforced. The default is static port binding. With redundant switches, perform this procedure on both the primary and the secondary switches. In normal operation, only the primary switch connects to the vCenter, with the secondary switch connecting only upon a failure of the primary.

Specifies the hostname or IP address for the vCenter Server. Optionally, specifies the port number and VRF. The server argument specifies the boot flash memory location to install the certificate. The argument value can be module-1 , sup-1 , sup-active , or sup-local. With redundant switches, perform this step only on the primary switch. The key is automatically synchronized with the secondary switch. This example shows how to configure the SVS connection on the primary switch and the secondary switch:.

With redundant switches, perform this step on both the primary and secondary switches. A virtual interface that migrates with a VM and virtual network link is called a floating vEthernet interface. A fixed vEthernet interface is a virtual interface that does not support migration across physical interfaces.

For fixed vEthernet static or dynamic , an administrator can change configurations at any time. The binding of the vEthernet interface number to a channel number is persistent unless the administrator changes it.

A grace period of days starts when you first configure the licensed feature. The following steps outline the necessary sequence of procedures for configuring VM-FEX between the switch and the server hosting the VMs. Procedures to be performed on the switch are described in this document. For procedures to be performed on the server or the VMware vCenter, refer to the server and vCenter documentation. See Configuring the Fixed Static Interfaces. See Verifying the Status of the Virtual Interfaces.

Optional vethernet auto-create. Optional feature fcoe. Optional end. Optional copy running-config startup-config. Optional reload. Enables the virtualization feature set on the switch. This feature set enables the use of static vEthernet interfaces. This feature set enables the use of dynamic vEthernet interfaces. Globally enables the automatic creation of virtual Ethernet interfaces. This feature is not required if the fixed vEthernet interfaces are statically configured. You can configure two physical interfaces and binds two virtual interfaces to each physical interface, creating fixed static vEthernet interfaces.

With redundant switches, you can perform the following procedure with identical settings on both the primary and secondary switches. With redundant switches, repeat this procedure with identical settings on the secondary switch. Shutting down the interface before enabling VN-Tag mode prevents the dynamic creation of a fixed vEthernet interface.

This example shows how to configure two physical interfaces, binds two virtual interfaces to each physical interface, and enables the interfaces:. Verify the status of the connection between the static interfaces and the static vNICs on the host server. You can configure a port profile for dynamic virtual interfaces. Optional switchport mode access.