- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: ISEE and vPars
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
тАО10-13-2004 09:20 PM
тАО10-13-2004 09:20 PM
It has been suggested that ISEE needs to be installed onto each vPar, but that doesn't seem to be possible, as the system handle would need to be re-used.
Has anyone done this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2004 06:02 AM
тАО10-15-2004 06:02 AM
Re: ISEE and vPars
installed on each vpar (each vpar has different hostname) all reference the same support contract.
Without it on each vpar you are not monitoring ALL the hardware in the box (that presuming that all HW is allocated and in use).
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2004 02:20 AM
тАО10-19-2004 02:20 AM
Re: ISEE and vPars
HP are telling me that I need to get a 'dummy' system handle created for each vPar, as system handles can't be re-used within ISEE. I'm not sure that this is an official recommendation though, anyone from HP's ISEE team care to comment ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2005 01:42 AM
тАО03-15-2005 01:42 AM
SolutionI don't know if you will ever see this but sorry for the very late reply. Our rp7410 has 2 Npars and a total of 4 Vpars. When the "system" was purchased it was given ONE system handle. I did not purchase any additional "dummy" handles. ISEE is installed on each Vpar and all run under the same handle.
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2005 08:22 PM
тАО03-15-2005 08:22 PM
Re: ISEE and vPars
Further responses from HP suggested that ISEE would 'sense' that it is being installed onto a vPar/same hardware, and so would allow the system handle to be re-used.
I had been holding out to confirm this on our systems before posting back to this thread, but time and project work has conspired against me.
Given your own experience, it would appear that HP's response is correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2005 08:24 PM
тАО03-15-2005 08:24 PM