2 SSMC Topology Insights

HPE 3PAR & Primera SSMC Topology Insights

Hello, starting with SSMC 3.6, HPE introduced a new feature called topology Insights.

Let me introduce what topology Insights is and how to enable it.

This guest post is brought to you by Armin Kerl, if you fancy trying you hand at blogging check out our guest posting opportunities.

What is SSMC Topology Insights?

Topology Insights allows a consolidated view of both storage and the VMware layer.  To see it within SSMC go to: VMWARE > Virtual Machines

1 SSMC Menu

Change to: Topology view from the drop down in the right hand window

2 SSMC Topology Insights

You will see all VM’s and the relationship between:

VM <> VMDK <> Datastore <> ESXi Server <> Virtual Volume <> Storage

Also, any performance impacts are displayed on top with a selectable time line, red shows a problem.

How to get Topology Insights?

You need at least:

  • SSMC 3.6
  • 3PAR with OS 3.3.x
  • Service Processor 5.x
  • VMware vCenter (no Hyper-V currently)

In the SSMC go to Settings

3 SSMC Settings

In Section “Application” enable “Topology”

4 Enable Topology Insights

and VMware > Virtual machines

5 SSMC Settings

Now go to “Storage Systems” > “Systems” > “Actions”

6 Set SP credentials

Enter the “Set SP credentials” here.

If it is successful, check under “Systems” > “Settings” if the vCenters entry is here.

7 Add vCentre

If not, go to edit and enter here.

If you don’t see “Set SP credentials”?

Like this:

8 Missing Set SP credentials

Or get this Message?

9 Missing service processor

I have had several customer sites, where the entry did not appear.

Most of the time these are storage systems and SP, which have been upgraded from 3.2.x to 3.3.x.

The following is for information only, it is recommended to contact support before proceeding.

It is a little bit Tricky, but here is a way to fix it:

Login to the 3PAR with SSH (Putty).

Enter: cli% getsys -showsysobjs

Look for {ServiceProcessorCookie {}}

Wrong: … {SessionTimeout 10800} {ServiceProcessorCookie {}} …

Right: … {SessionTimeout 10800} {ServiceProcessorCookie SPxxxyyyyzzzz:IP.of.the.SP}

If the SP Cookie is empty “{}”, we need to fix it.

Login to the SP 5.x Website and go to the Service Processor Overview Homepage.

10 Service processor values

Here we see the SPIP = IP address and SPID = SP ID

Now set the missing Values:

cli% setsys ServiceProcessorCookie SPID:SPIP

Example: setsys ServiceProcessorCookie SPCZ123456789:192.168.10.23

Check again: Enter: cli% getsys -showsysobjs

Now OK?

Go back to the SSMC and the “Set SP credential” should appear.
This fix worked for me every Time.

Thank you, folks for reading.

Armin

Published by

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.