ucs manger – AgileOps https://agileops.co.uk Virtualization made simple for Everyone. Sat, 20 Jul 2019 13:03:27 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.8 https://agileops.co.uk/wp-content/uploads/2017/10/favicon-01-50x50.png ucs manger – AgileOps https://agileops.co.uk 32 32 194680508 Reset Admin password for Cisco UCS Director https://agileops.co.uk/reset-admin-password-ucs-director/ https://agileops.co.uk/reset-admin-password-ucs-director/#comments Mon, 10 Jun 2019 00:57:57 +0000 ]]>

Hi All,

In this post i am going to take you through the process of resting the admin password of UCS Director.

As you might be aware that UCS director is a CentOS based appliance and the process to rest the root or the admin password is a bit different then other CentOS based server as this is highly customized appliance by Cisco.

httpss://www.cisco.com/c/pt_br/products/servers-unified-computing/ucs-director/index.html

Step1

To login to the ssh shell we have to use the user ‘shelladmin’ the default password set by Cisco is ‘changeme’ on you first login you will be required to change this.

Reenter the new password

Step2

You will be then presented with a menu. you need to press option 22 to change or reset the root password.

22) Manage Root Access

Type 22 as shown in the screen below

SELECT> 22

You can notice that a simple password was not accepted so i had to give a complex password. create one with letters numbers and special case.

Step3

Then login to the shell as root and run the scrip in the location.
/opt/infra/dbPwdReset.sh

As you can see below the option to specify admin password is not give as the password will be rest to the default password which is ‘changeme’

Then you can login to the UCS Director UI as admin and change the password from ‘changeme’ to your desired password. Make sure you keep this password safe or remember it for the next time you login. 🙂

Once the password is change you will be logout, you will need to reenter the password to login again to mange the UCS Director

More information about Cisco UCS Director can be found on the links below

Getting Started guide

httpss://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/getting-started-guide/6-5/cisco-ucs-director-getting-started-65.html

Overview of Cisco UCS Director
httpss://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/fundamentals-guide/5-4/b_UCS_Director_Fundamentals_Guide_54/Overview.pdf

References:

httpss://www.cisco.com/c/pt_br/products/servers-unified-computing/ucs-director/index.html

]]>

]]> https://agileops.co.uk/reset-admin-password-ucs-director/feed/ 7 1559 UCS Blade unable to ping or connect to vCenter https://agileops.co.uk/ucs-blade-unable-to-ping-or-connect-to-vcenter/ https://agileops.co.uk/ucs-blade-unable-to-ping-or-connect-to-vcenter/#comments Fri, 31 Oct 2014 22:30:11 +0000 https://quraishi.wordpress.com/?p=913 ]]> Hi All, I came across a strange issue where 2 blades was unable to ping I could get 2 ping and then Request time outs Problem : 2 Servers( in the same chassis server 3,4 ) unable to ping their gateway. Ping drops are after 1-2 packets. We cannot ping/ssh to them from outside and they cannot be added to vCenter. Other blades in the same chassis are working ( 1,2) Steps Taken :
  1. Confirmed that we do not have any IP conflicts
  2. Made sure that we do not use the same subnet anywhere else in the network
  3. Also checked and confirmed that the Mgmt(CIMC) subnet is different
ucs1
  1. Started a ping from inside a Host ( Server-3 ) to check if you are able to get to the gateway
  2. Checked vobd logs  to find if you can find any  entrie for duplicate ip/mac
  3. Checked the Mgmt Interface : vmk0
  4. It is connected to Port Group : Management Network  on VLAN ID, Check if we are  using the right vlan
  5. Found that the MAC Address of the vmk0 is same as vnic (vmnic0) : This is a known issue VMware KB article here. This is the vnic mac address of the service profile which is attached to the esx blade.
  6. Deleted and re-created the vmk0 interface
  7. Confirmed that the MAC Address has changed
  8. Started a continuous ping which work fine now
  9. Host can now be added to the vCenter
    So let me go through of the process of how we found the duplicate mac address. The vnic mac address was taken by vmknic  as you might know vmknic mad starts with 00:50:56 but in my case it was same as the mac address of vnic from the service profile. login to the host and give the command #esxcfg-nics -l

this gives the list of vnics assigned to the service profile, note the management nics in my case vnic 0 and 1 then give the below command to get the vmkernal nics #esxcfg-vmknic -l

as you can see above the mac address is not starting from 00:50:56 and it is been duplicated from the vnic template from the service profile vnic0 which is the root cause for the connectivity issue. Now to fix this we have to delete the virtual switch and re-create it. #esxcfg-vswitch -l This lists the virtual switches

#esxcfg-vmknic -d -p ‘Management Network’ you have to specify exact name of the port Now we will need to add the vmknic with the same Management network #esxcfg-vmknic -a -i <IPaddress> -n <Netmask> ‘Management Network’  and also give the command #esxcfg-vswitch -l  to check the Management network created as shown below. note you can not give a gateway at this point you can specify frm DCA

p3

 you should now be able to ping to the host as it has got a new mac address to check it you can give the command #esxcfg-vmknic -l

p34

  for a continus ping you can give #ping <gateway ip> -c 100 this will give 100 continuous pings   Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031111]]>

]]> https://agileops.co.uk/ucs-blade-unable-to-ping-or-connect-to-vcenter/feed/ 1 913