- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: Moving EVA phone home from ISEE to RSP
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
Forums
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
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
тАО08-11-2008 12:05 PM
тАО08-11-2008 12:05 PM
I have been able to get the EVA to show up in SIM. I get the fact you need to have serial numbers and product numbers for it to work. I assume you still need to go into WEBES and enter in the command view credentials for the management server? Do I need to add the management server into WEBES on the SIM server for the log reading to work right? How do I test phoning home and how do I see open and past cases in SIM? Where do I check for the entitlement event being verified? Many questions without many answers.
Aside from that do I need to configure the HPCC-ish collection settings for SANs in there?
Any advise anyone has would be greatly appreciated.
Thanx,
Matt Ronsman
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2008 10:57 AM
тАО09-23-2008 10:57 AM
Re: Moving EVA phone home from ISEE to RSP
I am currently working with HP to do the exact same thing. So far the one major task that needs to be done is install Command View 8.0 then upgrade to CV8.0.1 RSP can not pull any info in to SIM without CV8.
So far that is all I have gotten. I will post more when I finalize my configuration.
Todd.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2008 06:43 AM
тАО09-24-2008 06:43 AM
Re: Moving EVA phone home from ISEE to RSP
I just found out one major issue in having your EVA's report to HP.
your command view server MUST be have a valid warranty or contract to send any data to HP. That is what's stoping me.
Here is what is needed on your SMS(Command View)Server
Command View 8.0.1
ELMC(wccproxy)
Valid warranty/contract.
on your SIM/RSP server
all the componets for SIM/RSP
Webes configured to see your command view server and valid email
ELMC(wccproxy)
and current System Management Home page.
I hope this helps you and others.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2008 06:47 AM
тАО09-24-2008 06:47 AM
Re: Moving EVA phone home from ISEE to RSP
Thanks for the input!!
Thanx,
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-11-2008 12:31 PM
тАО11-11-2008 12:31 PM
Re: Moving EVA phone home from ISEE to RSP
To monitor EVAs using HP-SIM/RSP the following items must be present on the CV server:
- CommandView EVA V6.01 or newer
- SMI-S EVA
- SMI-S CIMOM
- ELMC-WCCproxy, which has to be taken from the CMS, downloaded with RSSM.
WEBES and OSEM on the CMS are now being fed by RSP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2008 11:16 PM
тАО12-17-2008 11:16 PM
Re: Moving EVA phone home from ISEE to RSP
Who knows the needed FW-Ports for the Remote Support Pack (RSP)? Which outgoing ports have to be open for the communication with HP?
Thanks for any response
Remo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2009 05:42 AM
тАО01-15-2009 05:42 AM
Re: Moving EVA phone home from ISEE to RSP
RSP/ISEE/OSEM/WEBES is installed to SIM server (not CV)
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2009 03:46 AM
тАО01-16-2009 03:46 AM
Re: Moving EVA phone home from ISEE to RSP
Thanx,
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2009 03:43 AM
тАО01-29-2009 03:43 AM
Re: Moving EVA phone home from ISEE to RSP
I'm in the process of getting this setup, But its a nightmare... Why go from 2 fairly simple programs to install to what we have to do with Insight manager ?? What bright spark came up with that idea ??. I only want to manage the kit we have contracts with with HP, but the damn thing keeps on adding all the rest, which are on a different contract.. I've unchecked the "Enable systems for Remote Support Services upon discovery." So if anybody has any ideas ??
good luck to the rest of you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2009 05:25 PM
тАО01-29-2009 05:25 PM
Re: Moving EVA phone home from ISEE to RSP
It has not been easy. There is a lot of documentation to read, it is not fluidly written, and there are very few screenshots and examples.
If I can be of any help, I'll monitor this thread and chip it if I can.
I made it a matter of principle to do it without HP Services, to be able to troubleshoot and maintain this properly. Experience has shown me that the monitoring tools eventually break if left unattended. With RSP there's a bunch of software here, increasing the likelyhood that it happens. Cases in point: A bunch of E2E errors many of us had to cope with, and the one that really made me independentely-minded was the built-in timebomb that deactivated WEBES after a year (we never got the reminder e-mails).
Good luck