Guest

Cisco Nexus 1000V InterCloud Installation and Upgrade Guide, Release 5.2(1)IC1(1.2)

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Nexus 1000V InterCloud Installation and Upgrade Guide, Release 5.2(1)IC1(1.2)

Chapter Title

Troubleshooting Cisco Nexus 1000V InterCloud

Results

Updated:
November 29, 2013

Chapter: Troubleshooting Cisco Nexus 1000V InterCloud

Troubleshooting Cisco Nexus 1000V InterCloud

This chapter contains the following sections:

Overview of the Troubleshooting Process

To troubleshoot your network, follow these general steps:

  1. Gather information that defines the specific symptoms.
  2. Identify all potential problems that could be causing the symptoms.
  3. Systematically eliminate each potential problem (from most likely to least likely) until the symptoms disappear.

Cisco Support Communities

For additional information, visit one of the following support communities:

Contacting Cisco Customer Support

If you are unable to solve a problem after using the troubleshooting suggestions in this guide, contact a customer service representative for assistance and further instructions. Before you call, have the following information ready to help your service provider assist you as quickly as possible:

  • Version of the Cisco Nexus 1000V InterCloud software that you are running.
  • Contact phone number.
  • Brief description of the problem.
  • Brief explanation of the steps you have already taken to isolate and resolve the problem .

After you have collected this information, see the Obtaining Documentation and Submitting a Service Request.

Problems with Cisco Nexus 1000V InterCloud

This section includes symptoms, possible causes and solutions for the following problems with Cisco Nexus 1000V InterCloud.

Unable to Create an InterCloud Link

Problem- InterCloud Link is not created.

Procedure
    Step 1   On the InterCloud Extender CLI, enter the following commands to verify if the IP address and UUID of the InterCloud Extender and InterCloud Switch is consistent in all the command outputs. 
    switch#	show intercloud ctrl-channel connections
VM Name          Type                 IP                        UUID                    
ICL-2-ics-1      ics                  175.41.178.139        0C54433F-5401-D7A9-2AC9-5DF1C37400B7
switch#

    switch#	show intercloud ctrl-channel config


self vm-info:                   
 type       : InterCloud-Extender     
 name       : Albacore2-icx-1         
 full-name  : hcloud-root/vpc-Albacore405/icl-Albacore2/icx-icx/Albacore2-icx-1
 uuid       : 3B5DF303-A41E-1312-802F-523359D420A6
 ip         : 10.2.70.82              
 HA state   : ACTIVE                  

peer vm-info:                   
 type       : InterCloud-Switch       
 name       : Albacore2-ics-1              
 full-name  : hcloud-root/vpc-Albacore405/icl-Albacore2/ics-ics/Albacore2-ics-1           
 uuid       : 465FEA15-20A2-854A-11EF-7A281C0A4BAA
 ip         : 50.18.137.85            

mgmt tunnel-info:               
 type       : site2site               
 id         : 1                       
 key        : configured              
 key-len    : 16                      
 reason     : valid key received      
switch#

    switch#	show intercloud tunnel statistics

Total tunnels            1                       
Tunnel ID                1                       
Tunnel Type              Site-To-Site            
Remote UUID             465FEA15-20A2-854A-11EF-7A281C0A4BAA
Remote VM Name               Albacore2-ics-1                           
Create Time              Wed May  8 09:23:14 2013
Tunnel Status            UP                      
RX Packets               2160                    
TX Packets               291592                  
RX Drops                 0                       
TX Drops                 0                       
RX Heartbeats            1838                    
TX Heartbeats            1841                    
TX Heartbeat Errors      0                       
Rx Control Packets       0                       
Netlink Drops            0                       
Epoch Failures           0                       
Encryption Errors        0                       
Bad Sequence Drops       0                       
Invalid MAC Drops        0                       
switch#

    switch#		show intercloud tunnel config

Albacore2-ics-1-Profile:            
uuid                    465FEA15-20A2-854A-11EF-7A281C0A4BAA
public-ip                50.18.137.85            
tunnel-port              6644                    

CGu-uuid                3B5DF303-A41E-1312-802F-523359D420A6

Site-to-Site-tunnel-profile:
Heartbeat-interval       1                       
Heartbeat-retries        300                     

Site-to-site-key-profile [Configured]            
Encryption Algorithm     AES-128-CBC             
Encryption-Key           30363046-33443334-46423942-44423233
Hash Algorithm           SHA1                    
Hash-Key                 45363441-39344337-45314239-33333843-38424430-32303932-44443044-36373632
ReKey-State              Not-In-Progress         
Epoch                    0                       

Access-tunnel-profile    [Not Configured]        

Access-key-profile       [Not Configured]
switch#
    Step 2   On the InterCloud Switch CLI, enter the following commands to verify if the IP address and UUID of the InterCloud Extender and InterCloud Switch is consistent in all the command outputs. 
    switch# show intercloud ctrl-channel connections

vm-name                           type   ip                 uuid
ICL-PREFCS-3-icx-1               icx    10.106.192.200     9D595BD4-44C2-5C69-8564-72A91B06A4B9
OVA-CENT-VM2                     ica    10.142.41.143      5D54A673-24CF-9FFE-C0DA-BCA672BA2EB7
MIG-RHEL-6332-Vm2                ica    10.131.46.254      885F3836-F712-3C19-6053-7188386FA2BF
ICL-PREFCS-3-ics-2               ics    175.41.162.75      FE59AE78-4265-8A0F-B839-C73A8C9EF3BC

switch#

    switch#	show intercloud ctrl-channel config

self vm-info:                   
 type       : InterCloud-Switch       
 name       : Albacore2-ics-1         
 full-name  : hcloud-root/vpc-Albacore405/icl-Albacore2/ics-ics/Albacore2-ics-1
 uuid       : 465FEA15-20A2-854A-11EF-7A281C0A4BAA
 ip         : 50.18.137.85            
 HA state   : ACTIVE                  


peer vm-info:                   
 type       : InterCloud-Extender     
 name       : Albacore2-icx-1         
 full-name  : hcloud-root/vpc-Albacore405/icl-Albacore2/icx-icx/Albacore2-icx-1                 
 uuid       : 3B5DF303-A41E-1312-802F-523359D420A6
 ip         : 10.2.70.82              

mgmt tunnel-info:               
 type       : site2site               
 id         : 1                       
 key        : configured              
 key-len    : 16                      
 reason     : valid key received      

 type       : access                  
 id         : 2                       
 key        : configured              
 key-len    : 16                      
 reason     : valid key received      
switch# 

    switch# 	show intercloud tunnel statistics

Total tunnels            1                       
Tunnel ID                1                       
Tunnel Type              Site-To-Site            
Remote UUID             3B5DF303-A41E-1312-802F-523359D420A6
Remote VM Name        Albacore2-icx-1                      
Create Time              Wed May  8 23:48:22 2013

Tunnel Status            UP                      
RX Packets               26814150                
TX Packets               202910                  
RX Drops                 0                       
TX Drops                 0                       
RX Heartbeats            178035                  
TX Heartbeats            177761                  
TX Heartbeat Errors      0                       
Rx Control Packets       0                       
Netlink Drops            0                       
Epoch Failures           0                       
Encryption Errors        0                       
Bad Sequence Drops       0                       
Invalid MAC Drops        0 
switch# 

    switch# 	show intercloud tunnel config

Albacore2-ics-1-Profile:            
uuid                    465FEA15-20A2-854A-11EF-7A281C0A4BAA
public-ip                50.18.137.85            
local-ip                 10.170.61.47            
tunnel-port              6644                    

CGu-uuid                3B5DF303-A41E-1312-802F-523359D420A6

Site-to-Site-tunnel-profile:
Heartbeat-interval       1                       
Heartbeat-retries        300                     

Site-to-site-key-profile [Configured]            
Encryption Algorithm     AES-128-CBC             
Encryption-Key           30363046-33443334-46423942-44423233
Hash Algorithm           SHA1                    
Hash-Key                 45363441-39344337-45314239-33333843-38424430-32303932-44443044-36373632
ReKey-State              Not-In-Progress         
Epoch                    0            
switch#
    Step 3   On the InterCloud Switch CLI, enter the following VEM commands. 
    switch# vemcmd show port

  LTL   VSM Port  Admin Link  State  PC-LTL  SGID  Vem Port  Type
   49      Veth3     UP   UP    FWD       0            eth1  
   50      Veth4     UP   UP    F/B*      0         veth1-0  
   

* F/B: Port is BLOCKED on some of the vlans.
       One or more vlans are either not created or
       not in the list of allowed vlans for this port.
 Please run "vemcmd show port vlans" to see the details. 
switch# 

    switch# vemcmd show port vlans
                          Native  VLAN   Allowed
  LTL   VSM Port  Mode    VLAN    State* Vlans
   49      Veth3   A         72   FWD    72
   50      Veth4   T          1   FWD    72,2315-2350

* VLAN State: VLAN State represents the state of allowed vlans. 
switch# 

    switch# vemcmd show dvport
  LTL  VSM Port  DVPortID       DVPortGroup  Vem Port
   49     Veth3         0       mgtm_access  eth1
   50     Veth4         0  N1K_Cloud_Default_Trunk  veth1-0
switch#

    InterCloud Extender Does Not Register With Cisco Nexus 1000V VSM in the InterCloud

    Problem- InterCloud Extender does not register With Cisco Nexus 1000V VSM in the InterCloud.

    Procedure
      Step 1   In the InterCloud Extender CLI, enter the following commands to verify if the management interface is up and the ip address/mask is configured correctly. 
      switch# show run interface mgmt 0

!Command: show running-config interface mgmt0
!Time: Sat May 11 06:17:25 2013

version 5.2(1)IC1(1.1)

interface mgmt0
  ip address 10.2.70.82/16
switch# 

      switch#	show interface brief 

--------------------------------------------------------------------------------
Port     VRF          Status IP Address                            Speed    MTU
--------------------------------------------------------------------------------
mgmt0    --           up     10.2.70.82                            1000     1500
switch#
      Step 2   In the Cisco Prime Network Services Controller, navigate to InterCloud Management > InterCloud Link > VPCs > InterCloud Extender. In the Configure Extender Network Interfaces screen, verify that the management interface IP address, netmask, gateway, and port profile are displayed accurately.
      Step 3   In the InterCloud Extender CLI, enter the following command to ping the Cisco Nexus 1000V VSM in the InterCloud. 
      switch# ping 10.2.70.81

PING 10.2.70.81 (10.2.70.81): 56 data bytes
64 bytes from 10.2.70.81: icmp_seq=0 ttl=254 time=0 ms
64 bytes from 10.2.70.81: icmp_seq=1 ttl=254 time=10 ms
64 bytes from 10.2.70.81: icmp_seq=2 ttl=254 time=0 ms
64 bytes from 10.2.70.81: icmp_seq=3 ttl=254 time=0 ms
64 bytes from 10.2.70.81: icmp_seq=4 ttl=254 time=0 ms

--- 10.2.70.81 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0/2/10 ms
switch#

      InterCloud Switch Does Not Register With Cisco Nexus 1000V VSM in the InterCloud

      Problem- InterCloud Switch does not register With Cisco Nexus 1000V VSM in the InterCloud.

      Procedure
        Step 1   In the Cisco Prime Network Services Controller, navigate to InterCloud Management > InterCloud Link > VPCs > General. In the VPCs screen, the InterCloud link is deployed and operational.
        Step 2   In the InterCloud Switch CLI, enter the following commands to verify if the management interface is up and the IP address and netmask is configured correctly. 
        switch# show run interface mgmt 0

!Command: show running-config interface mgmt0
!Time: Sat May 11 20:45:18 2013

version 5.2(1)IC1(1.1)

interface mgmt0
  ip address 10.2.70.83/16
switch# 

        switch# show interface mgmt 0 br

--------------------------------------------------------------------------------
Port     VRF          Status IP Address                            Speed    MTU
--------------------------------------------------------------------------------
mgmt0    --           up     10.2.70.83                            --       1500
switch#
        Step 3   In the Cisco Prime Network Services Controller, navigate to InterCloud Management > InterCloud Link > VPCs > InterCloud Switch. In the Configure Switch Network Interfaces screen, verify that the management interface IP address, netmask, gateway, and port profiles are displayed accurately.
        Step 4   In the InterCloud Switch CLI, enter the following VEM commands. 
        switch# vemcmd show port

  LTL   VSM Port  Admin Link  State  PC-LTL  SGID  Vem Port  Type
   49      Veth3     UP   UP    FWD       0            eth1  
   50      Veth4     UP   UP    F/B*      0         veth1-0  
   

* F/B: Port is BLOCKED on some of the vlans.
       One or more vlans are either not created or
       not in the list of allowed vlans for this port.
 Please run "vemcmd show port vlans" to see the details. 
switch#

        switch# vemcmd show port vlans
                          Native  VLAN   Allowed
  LTL   VSM Port  Mode    VLAN    State* Vlans
   49      Veth3   A         72   FWD    72
   50      Veth4   T          1   FWD    72,2315-2350

* VLAN State: VLAN State represents the state of allowed vlans. 
switch# 

        switch# vemcmd show dvport
  LTL  VSM Port  DVPortID       DVPortGroup  Vem Port
   49     Veth3         0       mgtm_access  eth1
   50     Veth4         0  N1K_Cloud_Default_Trunk  veth1-0
switch#

        Access Tunnel is Not Up

        Problem- Access tunnel is not up and running.

        Procedure
          Step 1   In the Cisco Prime Network Services Controller, navigate to InterCloud Management > Public Cloud > InterCloud Links > VM.Verify that the tunnel status for the VM is displayed as UP.
          Step 2   In the InterCloud Switch CLI, enter the following command to obtain the VM instance information. 
          switch#	show intercloud ctrl-channel connections

VM Name                   		IP                        		UUID                    
vm-CentOS63-64OVA-VM1     10.196.50.213         B859EE40-2857-15D3-8AC5-613B533E11AD

Albacore2-icx-1          	 10.2.70.82        	        3B5DF303-A41E-1312-802F-523359D420A6

switch#
          Step 3   In Amazon EC2, check the VM instance and verify it is running with all status checks passed.
          Step 4   SSH to the public IP of the InterCloud Agent (Cloud VM) and verify if the CSC0 interface ip address is in the same subnet as the default route ip address. 
          sjc-xdm-105:17> ssh -l root 50.18.70.50
root@50.18.70.50's password: 
Last login: Fri May 10 17:31:41 2013 from 128.107.239.233
[root@Centos63-64-VM1 ~]# ifconfig
csc0      Link encap:Ethernet  HWaddr 22:00:0A:C4:32:D5  
          inet addr:10.196.50.213  Bcast:10.196.50.255  Mask:255.255.255.192
          inet6 addr: fe80::2000:aff:fec4:32d5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:322388 errors:0 dropped:0 overruns:0 frame:0
          TX packets:234664 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:43009246 (41.0 MiB)  TX bytes:39264802 (37.4 MiB)
          Interrupt:247 

eth0      Link encap:Ethernet  HWaddr 7A:00:01:00:00:24  
          inet addr:193.100.100.51  Bcast:193.100.100.255  Mask:255.255.255.0
          inet6 addr: fe80::7800:1ff:fe00:24/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1300  Metric:1
          RX packets:88784 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76246 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6992477 (6.6 MiB)  TX bytes:7962844 (7.5 MiB)

eth1      Link encap:Ethernet  HWaddr 7A:00:01:00:00:23  
          inet addr:194.100.100.51  Bcast:194.100.100.255  Mask:255.255.255.0
          inet6 addr: fe80::7800:1ff:fe00:23/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1300  Metric:1
          RX packets:75123 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3501528 (3.3 MiB)  TX bytes:716 (716.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@Centos63-64-VM1 ~]#


[root@Centos63-64-VM1 ~]# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.170.61.47    10.196.50.193   255.255.255.255 UGH       0 0          0 csc0
10.196.50.192   0.0.0.0         255.255.255.192 U         0 0          0 csc0
193.100.100.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0
194.100.100.0   0.0.0.0         255.255.255.0   U         0 0          0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 csc0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth1
0.0.0.0         10.196.50.193   0.0.0.0         UG        0 0          0 csc0
[root@Centos63-64-VM1 ~]#
          Step 5   In the InterCloud Extender CLI, enter the following command to verify there are no cores. 
          switch# show cores 
Module  Instance  Process-name     PID       Date(Year-Month-Day Time)
------  --------  ---------------  --------  ----------------------------------------------

switch#

          There is no Traffic from the VM in the Enterprise to the VM in the Cloud

          Problem- There is no traffic from the VM in the enterprise to the VM in the cloud.

          Procedure
            Step 1   In the Cisco Prime Network Services Controller, navigate to InterCloud Management > Public Cloud > InterCloud Links > VM.Verify that the tunnel status for the VM in the cloud is displayed as UP.
            Step 2   In the Cisco Prime Network Services Controller, navigate to InterCloud Management > Public Cloud > VPC > VMs. Verify that the IP address, and port profile configurations for the VM in the cloud is displayed accurately.
            Step 3   In the InterCloud Switch CLI, enter the following command to verify the information of the VM in the cloud. 
            switch# show intercloud vm-names 

vm-CentOS63-64OVA-VM1     10.196.50.213             B859EE40-2857-15D3-8AC5-613B533E11AD
switch#

            switch# show intercloud port 
self port-info
 uuid           : 465FEA15-20A2-854A-11EF-7A281C0A4BAA 
 type           : InterCloud-Switch
 name           : Albacore2-ics-1 
 state          : 0x7 
 tunnel-id      : --- 
 mgmt-ip        : 10.2.70.83 
 public-ip      : 50.18.137.85 
 private-ip     : 10.170.61.47 
 ctrl channel   : --- 
 num-ports      : 2 

         port           : 1
         name           : veth1-0
         type           : 4
         cm-index       : 0
         instance-id    : 0
         peer-status    : UP
         veth-state     : 0x6
         uvem-port      : 1
         mac-address    : 7A:00:01:00:00:0D
         dv-port-id     : 2
         port-profile   : N1K_Cloud_Default_Trunk
         ip-mode        : ---

         port           : 2
         name           : eth1
         type           : 3
         cm-index       : 1
         instance-id    : 1
         peer-status    : ---
         veth-state     : 0x2
         uvem-port      : 1
         mac-address    : B6:43:69:61:6C:6A
         dv-port-id     : 40961
         port-profile   : mgtm_access
         ip-mode        : static
         ip-address     : 10.2.70.83
         netmask        : 255.255.0.0
         gateway        : 10.2.0.1

peer port-info 
 peer-vm        : 1
 uuid           : 3B5DF303-A41E-1312-802F-523359D420A6 
 type           : InterCloud-Extender
 name           : unknown 
 state          : 0x0 
 tunnel-id      : 1 
 mgmt-ip        : 10.2.70.82 
 public-ip      : --- 
 ctrl channel   : up 

InterCloud-Agent port-info (total: 1)
 InterCloud-Agent               : 1
 uuid           : B859EE40-2857-15D3-8AC5-613B533E11AD 
 type           : InterCloud-Agent
 name           : CentOS63-64OVA-VM1 
 state          : 0x0 
 tunnel-id      : 2 
 mgmt-ip        : --- 
 public-ip      : 213.50.196.10 
 ctrl channel   : up 
 domain name    : cisco.com 
 dns1-ipaddr    : 171.70.168.183
 dns2-ipaddr    : 173.36.131.10
 num-ports      : 2 

         port           : 1
         name           : veth2-0
         type           : 6
         cm-index       : 0
         instance-id    : 0
         peer-status    : UP
         veth-state     : 0x6
         uvem-port      : 1
         mac-address    : 7A:00:01:00:00:24
         dv-port-id     : 49156
         port-profile   : CSW_2315
         ip-mode        : static
         ip-address     : 193.100.100.51
         netmask        : 255.255.255.0
         gateway        : ---

         port           : 2
         name           : veth2-1
         type           : 6
         cm-index       : 1
         instance-id    : 1
         peer-status    : UP
         veth-state     : 0x6
         uvem-port      : 1
         mac-address    : 7A:00:01:00:00:23
         dv-port-id     : 45060
         port-profile   : CSW_2316
         ip-mode        : static
         ip-address     : 194.100.100.51
         netmask        : 255.255.255.0
         gateway        : ---
switch#
            Step 4   In the InterCloud Switch CLI, enter the following VEM commands. 
            switch# vemcmd show port
  LTL   VSM Port  Admin Link  State  PC-LTL  SGID  Vem Port  Type
   49      Veth3     UP   UP    FWD       0            eth1  
   50      Veth4     UP   UP    F/B*      0         veth1-0  
   51     Veth24     UP   UP    FWD       0         veth2-0  
   52     Veth25     UP   UP    FWD       0         veth2-1  
	
* F/B: Port is BLOCKED on some of the vlans.
       One or more vlans are either not created or
       not in the list of allowed vlans for this port.
 Please run "vemcmd show port vlans" to see the details. 
switch# 

            switch# vemcmd show port vlans
                          Native  VLAN   Allowed
  LTL   VSM Port  Mode    VLAN    State* Vlans
   49      Veth3   A         72   FWD    72
   50      Veth4   T          1   FWD    72,2315-2350
   51     Veth24   A       2315   FWD    2315
   52     Veth25   A       2316   FWD    2316
* VLAN State: VLAN State represents the state of allowed vlans. 
switch#

            switch# vemcmd show dvport
  LTL  VSM Port  DVPortID       DVPortGroup  Vem Port
   49     Veth3         0       mgtm_access  eth1
   50     Veth4         0  N1K_Cloud_Default_Trunk  veth1-0
   51    Veth24         0          CSW_2315  veth2-0
   52    Veth25         0          CSW_2316  veth2-1
switch#

            InterCloud Switch is not reachable

            Problem- InterCloud Switch is not reachable.

            Procedure
            In the InterCloud Extender CLI, enter the following command to verify if the InterCloud Switch is reachable . Use this command to verify if the state of the ports associated with the control channel and data channel service are open.

            In this command the state of the port indicates the reachability of the port from InterCloud Extender to InterCloud Switch.

            • Open state indicates that the port on InterCloud Switch is open and InterCloud Switch VM is reachable from InterCloud Extender.
            • Closed state indicates that the port on InterCloud Switch is closed and InterCloud Switch VM is reachable from InterCloud Extender.
            • Filtered/ics-unreach state indicates that either the port is filtered by a firewall or InterCloud Switch is not up. 
            switch# intercloud test ics-reachability
         PORT				  STATE				 SERVICE			       REASON
        6644/tcp   open      ctrl-channel     success
        6644/udp   open      data-tunnel      success
        22/tcp     open      ssh              success
        80/tcp     open      http             success
        443/tcp    open      https            success

            Cisco Nexus 1000V InterCloud Troubleshooting Commands

            Use one of the following commands to troubleshoot Cisco Nexus1000V InterCloud:

            Command

            Purpose

            show intercloud ctrl-channel configuration

            Displays information about control channel configuration.

            show intercloud ctrl-channel connections

            Displays information about active VM connections.

            show intercloud ctrl-channel connection status

            Displays information about active VM connection status.

            show intercloud tunnel

            Displays secure tunnel information.

            show intercloud tunnel configuration

            Displays information about secure tunnel configuration.

            show intercloud tunnel statistics

            Displays information about secure tunnel statistics.

            show intercloud tunnel connections

            Displays information about secure tunnel connections.

            show intercloud VM names

            Displays information about VMs names in the cloud.

            show intercloud VM statistics

            Displays information about VMs statistics in the cloud.

            show intercloud port

            Displays InterCloud port information.

            show system internal intercloud

            Displays event log information for all InterCloud modules

            show intercloud clink

            Displays InterCloud clink information.

            show intercloud clink status

            Displays InterCloud clink status information.

            show nsc-pa status

            Verifies the registration status of the Cisco Nexus 1000V InterCloud VSM with the Cisco Prime Network Services Controller.

            Was this Document Helpful?

            FeedbackFeedback

            Contact Cisco

            Related Support Community Discussions