- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Associating Node GUID with the OVC
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2024 06:26 AM - last edited on 02-22-2024 07:46 PM by support_s
02-22-2024 06:26 AM - last edited on 02-22-2024 07:46 PM by support_s
I am having some network issues and one of the troubleshooting steps is to run "egrep -i "faulty|suspected" $SVTLOG" from an OVC. I see some entries where the State = SUSPECTED. It shows the Node GUID but how do I associated it with the OmniStack host?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2024 09:57 AM
02-22-2024 09:57 AM
Re: Associating Node GUID with the OVC
Hi @TDW1
I see that you are unsure how to link the Node GUID to a specific OmniStack host after running "egrep -i "faulty|suspected" $SVTLOG".
Note that the Host ID is a GUID and not an IP address or Hostname of the node. While this may appear confusing to the end user, this is the actual GUID of the HPE SimpliVity node. Mapping the GUID to the hostname or IP address of the node is not possible through the GUI.
You may use the command "dsv-balance-show --shownodeip" to display the IP of the OmniStack host instead of the GUID which makes it easier for users to identify a node.
For more details on this, you may refer to the below links:
https://internal.support.hpe.com/hpesc/videoDisplay?videoId=vtc00030581en_us
https://community.hpe.com/t5/around-the-storage-block/how-vm-data-is-managed-within-an-hpe-simplivity-cluster-part-2/ba-p/7022921
Hope this helps.
Regards,
Sanika.
If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2024 06:01 AM
02-23-2024 06:01 AM
SolutionHello @TDW1
You could probably use the command "svt-federation-show --o xml" to see the node GUID and its correspoding OVC IP.
Hope it helps.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
