Monitoring Cisco Nexus 1000V

This chapter contains the following sections:

Problems with Monitoring the Cisco Nexus 1000V

This section includes symptoms and solutions for the following problems while you monitor the Cisco Nexus 1000V.

Symptom

Verification and Solution

Dashboard Tab

The Cisco Nexus 1000Vdisplays the wrong system detail values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/summary command.

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/summary HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong network statistic values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/limits command.

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/limits HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays the wrong licenses.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/license command.

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/license HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

Switch Tab

The Cisco Nexus 1000V displays the wrong host/Virtual Ethernet Module (VEM) values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vem?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vem command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/vem HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/vem?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong VM info values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/vnic HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/vnic?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong port profile values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/port-profile?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/port-profile command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/port profile HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/port-profile?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong vNICs.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/vnic HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/vnic?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong uplinks.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/uplink?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/uplink command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/uplink HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/uplink?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

Hosts/VEM Tab

The Cisco Nexus 1000V displays wrong host values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vem command.

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/vem HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong VM info values

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/vnic HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/vnic?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays wrong port group values.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/port-profile?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/port-profile command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/port-profile HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/port-profile?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays the wrong vNICs.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/vnic command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/vnic HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/vnic?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.

The Cisco Nexus 1000V displays the wrong uplinks.

  1. In a Linux VM or a Cisco Virtual Switch Update Manager VM, enter the curl -u admin:Sfish123 <vsm ip>/api/vc/uplink?bulk=1:50 command.

    Note   

    For Release 4.2(1)SV2(1.1a), enter the curl -u admin:Sfish123 <vsm ip>/api/vc/uplink command.

    In the ciscoExt.log, check for the content after the following line: GET /api/vc/uplink HTTP/1.1

  2. In the ciscoExt.log, check for the content after the following line: GET/api/vc/uplink?bulk=1:50 HTTP/1.1

  3. Compare the values.

  4. If there is a difference in values, send the log files to the Cisco Technical Assistance Center.