- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Removing EVA access to an unwanted WWN
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-07-2010 02:12 PM
тАО10-07-2010 02:12 PM
I want to remove a WWN from being seen on one of our EVA's. Our fabric spans across two sites, and a wwn was accidentally added to an alias at the wrong site.
This then advertised the wwn to an EVA at the wrong site. Since removing the port/wwn from the alias in the san fabric, if i go to add a new port in the EVA it still appears in the list. Ive checked the zone config and there is no entry for this wwn in zone that can see this EVA.
While not causing any issues, i want to remove it so it doesnt get confused as an incorrect port later down the track.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2010 03:04 PM
тАО10-07-2010 03:04 PM
Re: Removing EVA access to an unwanted WWN
the best way is to reboot EVA, after reboot you will not see the WWN in the list any more.
Or you can try to create a dummy host for that WWN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2010 03:23 PM
тАО10-07-2010 03:23 PM
Re: Removing EVA access to an unwanted WWN
Rebooting the EVA is not an option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2010 06:40 PM
тАО10-07-2010 06:40 PM
Re: Removing EVA access to an unwanted WWN
No function for you (the end user) that I know of anyway. There may be a service command that could be run, but you'd have to have HP do it.
If you are worried about the WWN being applied to something... just create a dummy host for now, assign the wwn and put a comment on it... "DO NOT USE!"
Otherwise... schedule a reboot of the EVA... and remember to delete the dummy host if you have created one.
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2010 07:55 PM
тАО10-07-2010 07:55 PM
SolutionSOLUTION:
There is three possible solutions.
1) Restart the whole EVA.
2) Resync the controllers from the FieldService Page.
3) Do a staggered reboot of the controllers. Reboot Controller 1, once this has comeback and joined the system. Reboot controller 2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2010 04:03 PM
тАО10-10-2010 04:03 PM