UNSOLVED

mstenbrg

updated

11 years ago

M

mstenbrg

1 Rookie

•

7 Posts

0

45344

September 22nd, 2015 10:00

2.1 with VRTX

After upgrading to Essentials 2.1, my VRTX chassis now shows up as unknown.  It was showing fine before the upgrade.

  • mstenbrg

    1 Rookie

    •

    7 Posts

    1445

    0

    Posted September 22nd, 2015 10:00

    Use the Troubleshooting tool that it.

  • mstenbrg

    1 Rookie

    •

    7 Posts

    1445

    0

    Posted September 22nd, 2015 10:00

    I found the tool.  Looks like it connects fine via WSMAN.

    Time: 22-09-2015 11:23:14 AM Device: stlvrtx01.interfacesys.com


    Protocols Selected are:

    1. WSMAN
    WSMAN
    WSMAN Connected.
    WSMAN profiles found on the remote device are:
    1. Chassis Software Inventory
    2. SM CLP Admin Domain
    3. Power State Management
    4. SMASH
    5. Chassis Event Filter
    6. Chassis RAID
    7. Chassis License Management
    8. CMC Profile
    9. Chassis Record Log
    10. Chassis Job Control
    11. Chassis NIC
    12. Chassis PCI Management

    Top

  • mstenbrg

    1 Rookie

    •

    7 Posts

    1445

    0

    Posted September 22nd, 2015 10:00

    How do I do that.

  • 1445

    0

    Posted September 22nd, 2015 10:00

    Hi,

    Thanks for the post. Can you please check whether are you able to connect using Trouble Shooting tool ?

    If you are able to connect, then please check whether VRTX certificate is valid (not-expired).

    Thanks,

    Arun

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    1445

    0

    Posted September 22nd, 2015 10:00

    You might go to the IP address of the chassis (chassis GUI) and the ip of the servers (idrac GUI) and check to see if the certs are expired.  I think you click on the cert details in the GUI.

    Thanks,

    Rob

  • mstenbrg

    1 Rookie

    •

    7 Posts

    1445

    0

    Posted September 22nd, 2015 10:00

    This is the cert I get when I go to the website of the VRTX chasis management controller.  I will say everything worked fine until I upgraded to 2.1, not sure if 2.01 did not care that the cert was expired?

    Issued to:  cmc-30855

    Issued by:  cmc-30855

    Valid from 8/3/2001 to 8/1/2011

  • DELL-Abhijit P

    Community Manager

    •

    711 Posts

    1445

    0

    Posted September 22nd, 2015 11:00

    OME 2.1 updated the WS-MAN communication component. The newer component enforces better security policies and does not communicate with the devices if the certificates are expired.

    You can update the certificate as follows:

    Open CMC command line console ( SSH or Telnet ) and execute below RACADM command , this will reset the certificate to future date and resolves the issue.

    $ racadm sslresetcfg

    You will see the following output for the command:

    Certificate regenerated successfully and webserver will be restarted

    Regards

    Abhijit

  • mstenbrg

    1 Rookie

    •

    7 Posts

    1445

    0

    Posted September 22nd, 2015 12:00

    That worked.  Thank you.