Remote Support Default Secondary Contact

[Kelly M Knowles]

I have noticed that the default primary contact populates on server hardware enabled for remote support but it is required to go in and set a secondary contact manually.

A feature I would like to request is to be able to set a default secondary contact and have it populate that on newly monitored server hardware in the same way the default primary contact populates already.

Thanks

[ChrisLynch]

That certainly is not expected behavior.  When you add the Remote Support Contact to the Remote Support settings on the appliance and then populate that value in the Data Center(s) you have created.  What appliance version are you using?

[Kelly M Knowles]

This is on version 3.10.07-0310774.

So you are saying if I was to set that seconday contact on the datacenter level it would work for new server hardware?

[ChrisLynch]

Yes.

Sent from my Windows 10 phone

[Kelly M Knowles]

I just assigned the secondary contact to the only customer datacenter defined on the appliance.

I then removed a server hardware from the OneView appliance that had both a primary and secondary contact.

I re-added the same server hardware to the OneView appliance.

The server hardware now only has one Remote Support contact.

[ChrisLynch]

Then please open a support case.

Sent from my Windows 10 phone

[Kelly M Knowles]

I have opened case number 5323295210.  I think this is readily reproducable behavior and should be easy for anyone with OneView to do.  I think if you have a blade enclosure then of it works differently for new hardware than if you have a rack server.  Ideally I would like an appliance wide default secondary contact though.

[Tan_Foo_Siang]

Did you add the server hardware back to the rack which is linked to the datacenter?

If not, you will only have the default remote support contact.

[peyrache]

Unable to replicate using 3.10 and DL380gen8

JY

[Kelly M Knowles]

In the support ticket I opened I demonstrated to the support representative this behavior.  If you have a new server hardware it does not default to be part of a datacenter.  Furthermore it is not part of a rack.  If assigning the hardware to a rack/datacenter is the workaround then I still ask that there be a feature to add a default secondary contact for people who do not use the datacenter or rack part of OneView or people who simply are forced to recreate server hardware or add it and forget to go through these extra steps.

As an alternative I think it would also work fine if the server hardware had a default spot in a datacenter that allow the OneView administrator to say that new devices go to one specific default datacenter and end up in a default rack which is just a placeholder but would allow there to be a default secondary contact.

[ChrisLynch]

If assigning the hardware to a rack/datacenter is the workaround then I still ask that there be a feature to add a default secondary contact for people who do not use the datacenter or rack part of OneView or people who simply are forced to recreate server hardware or add it and forget to go through these extra steps.

That is not how the product was designed.  Creating a Datacenter and putting resources into the data center helps with configuring Remote Support, as they will inherit the DC settings.  Otherwise, you are left with manually managing individual systems REmote Support configuration.

Plus, when you add your resources to racks and within a data center, you get a better visual representation of that data center.  HPE iPDU's and Location Discovery Services aid in that configuration, and can automatically place resources into the right location.  HPE BladeSystem also can place resources within a rack correctly without iPDU's and Location Discovery Services.   

[Kelly M Knowles]

The product has a default datacenter address and default primary contact defined.  This is just a simple feature request to also add a default secondary contact.  I know I can manually add the secondary contact to devices and I know how to add them to racks and datacenters.  I have had specific cases which I am more than happy to discuss offline that have required recreating server hardware usually due to corrupted iLo NAND and the server profile / hardware cannot be salvaged.  Also if a customer simply does want to designate the HPE OneView rack to put the equipment into because documenting the location of installed equipment is too time consuming in the beginning of a project then they have to manually go into each piece of equipment and set the remote support secondary contact becuase it seems you can't just assign equipment to a Datacenter you have to position it into a rack as well.  If this request is so against the way the product is designed to be used then why bother including any default remote support information at all?

[ChrisLynch]

As it stands right now, setting the Secondary Contact is configured at the DataCenter, Enclosure, or Server resource.  I will pass your feedback to the product owner.