Managing Host Server Connections [Cisco Nexus 1000V Switch for KVM]

Contents
Managing Host Server Connections
Information about Host Server Connections
Configuring Host Server Connections
Mapping a VEM to a New Host
Removing Host Mapping from a Virtual Ethernet Module
Viewing Host Mapping
Verifying the Configuration
Feature History for Host Server Connections
Managing Host Server Connections

This chapter contains the following sections:

Information about Host Server Connections
Configuring Host Server Connections
Verifying the Configuration
Feature History for Host Server Connections

Information about Host Server Connections

When a VSM detects a new VEM, it automatically assigns a free module number to the VEM and then maintains the mapping between the module number and the universally unique identifier (UUID) of a host server. This mapping is used to assign the same module number to a given host server.

Configuring Host Server Connections
Mapping a VEM to a New Host
Before You Begin
Before beginning this procedure, be sure you have done the following:

Logged in to the CLI in EXEC mode

Removed the host from the Cisco Nexus 1000V DVS on the OpenStack controller

Procedure
Command or Action Purpose
Step 1 switch# configure terminal
Places you in global configuration mode.

Step 2 switch(config)# no vem module number (Optional)
Removes the existing module-to-host mapping

Note
If you are changing the mapping on a module, you must remove the existing host mapping first. If you do not remove the existing host mapping first, the new host is assigned a different module number.

Step 3 switch(config)# vem module number
Places you in configuration mode for the specified module.

Step 4 switch(config-vem-slot)# host id server-bios-uuid
Assigns a different host server UUID to the specified module. The host ID must match the host UUID in the /etc/n1kv/n1kv.conf file. The valid range is from 0 to 64 characters.

Step 5 switch(config-vem-slot)# show module vem mapping (Optional)
Displays the mapping of modules to hosts.

Step 6 switch(config-vem-slot)# copy running-config startup-config
Copies the running configuration to the startup configuration.
switch# configure terminal
switch(config)# no vem 3
switch(config)# vem 3
switch(config-vem-slot)# host id 93312881-309e-11db-afa1-0015170f51a8
switch(config-vem-slot)# show module vem mapping
Mod     Status          UUID                                    License Status
---     -----------     ------------------------------------    --------------
  3      powered-up     93312881-309e-11db-afa1-0015170f51a8    licensed
  4          absent     6dd6c3e3-7379-11db-abcd-000bab086eb6    licensed

switch(config-vem-slot)# copy running-config startup-config
Removing Host Mapping from a Virtual Ethernet Module
You can remove the host mapping from a module.

Before You Begin
Before beginning this procedure, be sure you have done the following:

Logged in to theCisco Nexus 1000V in EXEC mode.

Removed the host from the Cisco Nexus 1000V DVS on the OpenStack controller.

Procedure
Command or Action Purpose
Step 1 switch# configure terminal
Places you in global configuration mode.

Step 2 switch(config)# no vem module-number
Removes the specified module from the software.

Note
If the module is still present in the slot, the command is rejected, as shown in the example.

Step 3 switch(config)# show module vem mapping (Optional)
Displays the mapping of modules to hosts.

Step 4 switch(config)# copy running-config startup-config
Copies the running configuration to the startup configuration.
switch# configure terminal
switch(config)# no vem 4
switch(config)# no vem 3
cannot modify slot 3: host module is inserted
switch(config)# show module vem mapping 
Mod     Status          UUID                                    License Status
---     -----------     ------------------------------------    --------------
  3      powered-up     93312881-309e-11db-afa1-0015170f51a8    licensed
switch(config-vem-slot)# copy running-config startup-config
Viewing Host Mapping
Use this procedure in EXEC mode to view the mapping of modules to host servers.

Procedure
Display the mapping on modules to host servers by entering the following command: show module vem mapping
Mod Status      UUID                                 License Status
--- ----------- ------------------------------------ --------------
3   powered-up  93312881-309e-11db-afa1-0015170f51a8  licensed
n1000v(config)#
Verifying the Configuration
Use one of the following commands to verify the configuration:
show running-config

Displays the current configuration.

If the Cisco Nexus 1000V is not connected to a OpenStack controller or KVM server, the output is limited to connection-related information.
switch(config)# show running-config

!Command: show running-config
!Time: Fri Jul 26 01:59:50 2013

version 5.2(1)SK1(1.1)
switchname n1000v-VSM-Primary

no feature telnet

username adminbackup password 5 !  role network-operator
username admin password 5 $1$uaNy2mFT$Sy6fo2j8Q/uxc0fWMpBLz1  role network-admi
n
username admin keypair rsa

banner motd #Nexus 1000v Switch
#

ip domain-lookup
ip host n1000v-VSM-Primary 10.106.202.182
errdisable recovery cause failed-port-state
vem 3
  host id 10
vem 4
  host id 64
snmp-server user admin network-admin auth md5 0xb64ad6879970f0e57600c443287a79f
0 priv 0xb64ad6879970f0e57600c443287a79f0 localizedkey


vrf context management
  ip route 0.0.0.0/0 10.106.202.161
vlan 1,2166-2170

cdp advertise v1
cdp holdtime 10
cdp timer 5
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile default port-binding static
port-profile type vethernet N1K_Cloud_Default_Trunk
  switchport mode trunk
  no shutdown
  guid 51e1095a-61ea-50b5-9f3c-19842dcff6e7
  max-ports 64
  description Port Profile created for Nexus 1000V internal usage. Do not use.
  state enabled
port-profile type ethernet uplink_sys
  switchport mode trunk
  switchport trunk allowed vlan 2167-2170
  no shutdown
  guid 53502d18-9ffb-411a-b665-d830081136e5
  max-ports 512
  state enabled
port-profile type ethernet uplink_sys_pc
  switchport mode trunk
  switchport trunk allowed vlan 2167
  channel-group auto mode active
  no shutdown
  guid 7aa26801-1e00-2684-97ec-a7cc1a4615af
  max-ports 512
  state enabled
port-profile type vethernet vm_access_sys
  switchport mode access
  guid 78dc356e-1fe5-7c72-8c2c-6286065720a8
port-profile type vethernet DEFAULT_DATA_VNIC1
  switchport mode access
  switchport access vlan 2170
  no shutdown
  guid 5cb014fe-3d4f-014a-b673-869700f70425
  state enabled
port-profile type vethernet DEFAULT_DATA_VNIC2
  switchport mode access
  switchport access vlan 2167
  no shutdown
  guid 42dbc174-30ec-2ab7-8796-c92e15ea4167
  state enabled
port-profile type vethernet DEFAULT_DATA_VNIC3
  switchport mode access
  switchport access vlan 2169
  no shutdown
  guid 090dc703-caca-102c-869a-86e433531d77
  state enabled
port-profile type vethernet mx-nlb
  guid 2505614c-2107-5f97-9f21-45d70b57aa3e
port-profile type vethernet hsrp-1
  switchport mode trunk
  disable-loop-detection hsrp
  no shutdown
  guid 6d2b8903-94c5-2e9a-923d-182408301feb
  state enabled
port-profile type vethernet vrrp-1
  disable-loop-detection vrrp
  switchport mode trunk
  no shutdown
  guid 3262b6ec-1333-2665-bc78-37a31ea6a71e
  state enabled
port-profile type vethernet LynnTest
  guid 5a5e3644-8cf9-1f4a-bf63-97912048f20e
port-profile type vethernet LynnPP
  switchport mode access
  switchport access vlan 10
  no shutdown
  capability l3control
  guid 754ab04a-6979-3f5f-a0ec-aef11dd83ff0
  state enabled


interface port-channel2

interface mgmt0
  ip address 10.106.202.182/27

interface control0
  no snmp trap link-status
line console
line vty
boot kickstart bootflash:/n1000v-dk9-kickstart.5.2.1.SK1.1.0.345.gbin sup-1
boot system bootflash:/n1000v-dk9.5.2.1.SK1.1.0.345.gbin sup-1
boot kickstart bootflash:/n1000v-dk9-kickstart.5.2.1.SK1.1.0.345.gbin sup-2
boot system bootflash:/n1000v-dk9.5.2.1.SK1.1.0.345.gbin sup-2
svs-domain
  domain id 1
  control vlan 1
  packet vlan 1
  svs mode L3 interface mgmt0
  switch-guid 07da7e1a-2bff-6833-b416-f5d83204a55c
svs connection svs_system
  max-ports 8192
vservice global type vsg
  tcp state-checks invalid-ack
  tcp state-checks seq-past-window
  no tcp state-checks window-variation
  no bypass asa-traffic
vnm-policy-agent
  registration-ip 0.0.0.0
  shared-secret **********
  log-level info
show svs connections

Displays the current connections to the Cisco Nexus 1000V.

Note

Network connectivity issues may shut down your connection to theOpenStack controller. When network connectivity is restored, the Cisco Nexus 1000V will not automatically restore the connection. In this case, you must restore the connection manually using the following command sequence:

no connect

connect
switch(config)# show svs connections

connection svs_system:
    hostname: -
    ip address: -
    remote port: 80
    protocol: -
    certificate: default
    datacenter name: - 
    admin:   
    max-ports: 8192
    DVS uuid: -
    config status: Disabled
    operational status: Disconnected
    sync status: -
    version: -
    vc-uuid: -
switch(config)# 
show module

Displays the module information.
swtich# show module
Mod  Ports  Module-Type                       Model               Status
---  -----  --------------------------------  ------------------  ------------
1    0      Virtual Supervisor Module         Nexus1000V          active *
2    0      Virtual Supervisor Module         Nexus1000V          ha-standby

Mod  Sw                  Hw      
---  ------------------  ------------------------------------------------  
1    5.2(1)SK1(1)        0.0                                              
2    5.2(1)SK1(1)        0.0                                              

Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  NA
2    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.105.225.180   NA                                    NA
2    10.105.225.180   NA                                    NA

* this terminal session 
Feature History for Host Server Connections

Feature Name

Releases

Feature Information

Host Mapping

Release 5.2(1)SK1(2.1)

This feature was introduced.