cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2496
Views
14
Helpful
8
Replies
Highlighted

Error Logs on 1000v Nexus Switch

Hi Team,

We are below errors from one of our Nexus 1000v switch.

Please advice me why we are getting this kind of errors.

I can see the operational status is disconnected(Show Svs Connection)

Logs:
---------


2012 Dec  2 22:40:15 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec  2 22:43:15 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec  2 22:46:15 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec  2 22:49:14 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.
2012 Dec  2 22:52:14 NODIPXX-N1KVM11 %VMS-3-CONN_CONNECT_ERR: Connection 'vwdixx-vcsem' failed to connect to the vCenter Serve
r.


show svs connections
----------------------

connection vwdixx-vcsem:
    ip address: ---------------------
    remote port: 80
    protocol: vmware-vim https
    certificate: default
    datacenter name: -----------------
    admin:
    max-ports: 8192
    DVS uuid: 53 8a 35 50 99 ba e3 cf-5f 5f fc 1c bd 54 50 f9
    config status: Enabled
   operational status: Disconnected
    sync status: -
    version: -
    vc-uuid: -

Regards,
Sen

8 REPLIES 8
Highlighted
Beginner

Hi Sen,

The VSM is not able to connect to the vCenter through its management interface and hence you're getting these messages.

Some things to check:

- Is the VSM management interface reachable?

- Is the vCenter reachable?

Thanks,

Shankar

Highlighted

Thanks for reply shankar....

you mean the problem is in Nexus 1000v or Server Side?....

if you need any other logs please?...

Regards,

Sen

Highlighted

We can't say where the problem is just by looking at the message. It just means that the VSM is not able to connect to the vCenter through its management interface.

- Is the VSM's management interface (second NIC in the VM) behind the vSwitch or behind the Nexus 1000v?

- Are you able to reach (ping/SSH) the management IP address of the VSM?

     - If not, you need to see why this is not reachable.

- Are you able to connect to the vCenter using its IP address?

Thanks,

Shankar

Highlighted

If vcenter connectivity is fine, can you please post the output for :
n1000v# show vms internal event-history errors
Highlighted

Hi,

As per request please check the logs below..........

Logs:

------

NODEPXX-N1KVM11# sh vm
vms      vmware
NODEPXX-N1KVM11# sh vms internal event-history errors
1) Event:E_DEBUG, length:68, at 126416 usecs after Tue Dec  4 23:40:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1

2) Event:E_DEBUG, length:193, at 126411 usecs after Tue Dec  4 23:40:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()

3) Event:E_DEBUG, length:68, at 160081 usecs after Tue Dec  4 23:37:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1

4) Event:E_DEBUG, length:193, at 160075 usecs after Tue Dec  4 23:37:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()

5) Event:E_DEBUG, length:68, at 194044 usecs after Tue Dec  4 23:34:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1

6) Event:E_DEBUG, length:193, at 194039 usecs after Tue Dec  4 23:34:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()

7) Event:E_DEBUG, length:68, at 227797 usecs after Tue Dec  4 23:31:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1

8) Event:E_DEBUG, length:193, at 227791 usecs after Tue Dec  4 23:31:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()

9) Event:E_DEBUG, length:68, at 262100 usecs after Tue Dec  4 23:28:09 2012
    [102] vms_vim_connect_extension(506): connection failed. returning -1

10) Event:E_DEBUG, length:193, at 262088 usecs after Tue Dec  4 23:28:09 2012
    [102] convert_soap_fault_to_err(1762): SOAP 1.1 fault: SOAP-ENV:Client [VMWARE-VIM] Operation could not be completed due t
o connection failure.Connection refused. connect failed in tcp_connect()

Highlighted

Thanks Senthil. I want to take a look at your setup for both VSm configs and vcenter.

lets debug this offline.

Regards

Sonali

Highlighted

Thanks sonali.......

I need to know how to see this config from Nexus 1000v if you want any logs please let me know.....

Still we are getting same problem.

Thanks....

Regards,

Sen

Highlighted

Did you install VSM using the installer App or manual install?

Is the VSM registered with Vcenter server ? Vcenter Plugin will show if VSM is registered.

Can you please send "show svs connection" output, and logs of continuous ping from vsm to vcenter logs. we want to verify network connectivity is fine between VSM and vcenter.

What version of Nexus1k are you using;

In addition , verifying VSM and Vcenter connectivity section in following troubleshooting guide can help you fix the issue :

http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_2_1_1/troubleshooting/configuration/guide/n1000v_trouble_3install.html#wp1188042


This widget could not be displayed.