- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA 3000
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
тАО12-20-2006 08:46 PM
тАО12-20-2006 08:46 PM
EVA 3000
I am getting following error when opened EVA management command view.
Another management agent on appliance SMAM01NFK353T at IP address may be actively managing this storage system. (System name: EVA3K).
Only one agent is allowed to manage a system at a time.
Version 2 management agents must be removed from the configuration for 15 minutes to ensure that management has ended. After removing a Version 2 management agent and waiting 15 minutes, click the OK button to continue.
To disable Version 3 management agents, simply click the OK button and management will be redirected to this agent.
How to solve this problem ?
Please help me.
Thanks,
Sujeet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-20-2006 09:48 PM
тАО12-20-2006 09:48 PM
Re: EVA 3000
You should be able to regain control use of the eva by pressing ok.
What happens when you do ?
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-20-2006 11:56 PM
тАО12-20-2006 11:56 PM
Re: EVA 3000
I'd suggest after the prior post to have a short downtime and reset the EVA. Either some other box is using the IP address or the management agent software has been run twice and a reset of the system will fix it.
A rest of the EVA system includes the DL class system that usually controls the storage.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2011 01:07 AM
тАО04-04-2011 01:07 AM
Re: EVA 3000
i would like to know if this problem was solved, because i have same error and i don't know how to solve. Should i press OK and problem will be solved? Should reset solve the problem?
Regards
Thank you in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2011 03:21 AM
тАО04-05-2011 03:21 AM
Re: EVA 3000
If another Command View is using the same EVA in the future, they will get the same message, and they will need to press OK.
You see the IP in there, that is the other command view that is managing the EVA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2011 11:33 PM
тАО04-05-2011 11:33 PM
Re: EVA 3000
But let's make it clear: this is not a "problem".
This is how the EVA/CV-EVA works to restrict management to one active CV-EVA instance.