Start a Conversation

Unsolved

This post is more than 5 years old

A

2042

April 7th, 2016 08:00

VRTX shows up as unclassified

Hello,

One out of five VRTX's shows up as unclassified when discovered using WSMAN. First I thought it was a firewall issue but I get the same result whether I run the diag tool from the OME server or from a server on the same subnet as the CMC.

The diag tool shows the following being discovered by 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

Running diag towards any of the other VRTX I get a lot more discovered:

Connected.
WSMAN profiles found on the remote device are:
1. Chassis Software Inventory
2. Power Supply
3. Sensors
4. Base Metrics
5. Physical Asset
6. SM CLP Admin Domain
7. Base Server
8. Power State Management
9. Power Topology
10. Power Allocation
11. Service Processor
12. SMASH
13. Boot Control
14. Chassis System Info
15. Simple Identity Management
16. Chassis Event Filter
17. Role Based Authorization
18. Chassis RAID
19. Chassis License Management
20. Active Directory Client
21. Modular System
22. CMC Profile
23. Chassis Record Log
24. Chassis Job Control
25. Chassis NIC
26. Chassis PCI Management

I have upgraded the CMC fw to v2.11 to no avail as well as re-add it to OME. WSMAN discovery is setup 120 seconds.

Any ideas?

2 Intern

 • 

1K Posts

April 11th, 2016 01:00

Hi,

Can you confirm which version of OME are you using? Can you try downloading the latest Dell TT from http://en.community.dell.com/techcenter/extras/m/white_papers/20097184 and check if you are seeing SSL certificate expiry problem? If it happens to be that, then you will need to reset the SSL certificate on this VRTX.

1 Rookie

 • 

19 Posts

April 11th, 2016 02:00

Thank you for your assistance.

OME is 2.1.0.2635 and TT v3.4.3.

You were spot on - the CMC cert expired last year so did a SSL reset and the VRTX is now correctly discovered.

Thank you very much.

2 Intern

 • 

1K Posts

April 11th, 2016 05:00

Thanks for letting us know. Happy to help.

No Events found!

Top