logo
  • Home
  • About Me
  • EMC
  • Virtualization

Monthly Archives: July 2016

ESXi Hosts showing as unlicensed in Nexus 1000 despite of licenses being available.

Cause

This issue can occur when the Nexus 1000V VSM recognizes a host/VEM module as a new module and not an existing one. The VSM assigns the host a new module ID number.

In this situation, the VEM license is still in use and associated with the old VEM module number in the system. This can sometimes occur after ESXi host or VEM module upgrades, as well as host firmware/BIOS updates.

Resolution

To resolve this issue, transfer the VEM license from the old VEM module number to the new one.

To transfer the VEM license:

  1. Run these commands:

    n1k# show module
    n1k# show license usage NEXUS1000V_LAN_SERVICES_PKG

    Compare the output of the two commands and identify the VEM module that is present in the show license usage output, but not present in the show module output. Make a note of this module number.

  2. The license of the identified module must be transferred to the unlicensed VEM by running these commands:

    n1k# configure terminal
    n1k(config)# svs license transfer src-vem vem_number dst-vem vem_number

    Where vem_number the module numbers identified earlier in this procedure.

  3. Ensure the VEM module is now licensed by running the command:

    n1k# show module

Cisco UCS Major Alert Default Key Ring Certificate Invalid Reason Expired

I faced a major alert is UCSM regarding Default Key Ring Certificate Expired.

Certificates is only valid for 1 year. After that new certificate would needs to be generated.

Check the validity and expiry date as below

login to your primary FI as admin and execute below commnds

FI-A# scope security
FI-A/security# show keyring detail

Generate the new Certificate

FI-A# scope security
FI-A/security# scope keyring default
FI-A/security/ keyring# set regenerate yes
FI-A/security/ keyring*# commit-buffer

UCSM will disconnect and reconnect .

 

Run the above commands again to validate .

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Categories

Follow me on Twitter

My Tweets

Top Posts & Pages

  • Storage vMotion Stuck at 32% when migrating from One Vplex to Other
  • Adding a host to a different vCenter Server after disassociating from existing vCenter Server fails with the error: Failed to configure the VIM account on the host .
  • Resolution :-Host cannot communicate with all other nodes in virtual SAN enabled cluster
  • Changing the IP Address of the Cisco DCNM-SAN & DCNM-SMIS OVA/LINUX Installation

Social

  • View anujajju’s profile on Twitter

Pages

  • About Me

Archives

  • July 2019
  • April 2018
  • January 2018
  • September 2017
  • August 2017
  • August 2016
  • July 2016
  • June 2016
  • May 2016

Categories

  • EMC (3)
    • Unisphere (2)
    • VPLEX (1)
  • UCS (3)
  • Virtualization (19)

WordPress

  • Log in
  • WordPress
follow @anujajju
  • About Me