- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- MSL6000 discovery problem
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
тАО03-07-2006 03:06 AM
тАО03-07-2006 03:06 AM
i have new MSL6000 installed and it will be connected to two HP unix servers for backup, the MSL is connected through SAN.
i have configured the zone in the SAN switch, but the MSL router did not discover my servers, the HPA's on the servers are configured and i can connect to the EVA, also if i added the EVA controles to the zone the router discover them.
can anyone help me configuraning the MSL router and what is wrrong.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 04:59 AM
тАО03-07-2006 04:59 AM
Re: MSL6000 discovery problem
Once the HBA's have logged in, then you should see them in the host list, and be able to assign them to a map (or maps, if you want different presentations to different hosts).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 05:36 PM
тАО03-07-2006 05:36 PM
Re: MSL6000 discovery problem
i have done a reboot for the MSL and the MSL router but the same, i have also done arboot for the servers but also the same.
do u think i should reset the router configuration and start again.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 06:21 PM
тАО03-07-2006 06:21 PM
Re: MSL6000 discovery problem
If I understand your query properly then you are unable to view the list of HP-UX hosts on the NSR. You are viewing this information from NSR serial or HTML access.
But as per your own statement, if you include the EVA zone you are able to discover EVA.
If this is what is your scenario then
1) verify and post the zoning information.
2) If you have a mix of Windows and HP-UX servers, then the HP-UX servers have to be in a seperate zone.
3) The device maps have to be created from the NSR interface and assigned to the servers
wwn
4) Make the port speed of the NSR to 2G fixed on the switch side.
With regards,
Mohan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 06:22 PM
тАО03-07-2006 06:22 PM
Re: MSL6000 discovery problem
then be sure that the zone you just created is added to the active config, and that you saved the config, this is something that some time is forgoten.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 10:34 PM
тАО03-07-2006 10:34 PM
Re: MSL6000 discovery problem
im using the html to configure the router.
1- my zones only have HP ux servers and the MSL
2- i have tryed to do the device maps from the NSR interface but i dont see any of my servers can u help me in configuration from the NSR interface
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 10:48 PM
тАО03-07-2006 10:48 PM
Re: MSL6000 discovery problem
can you click on report, and save the report as a html archive (*.mth) so I can see the situation
marino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2006 11:51 PM
тАО03-07-2006 11:51 PM
Re: MSL6000 discovery problem
this is the report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2006 12:32 AM
тАО03-08-2006 12:32 AM
SolutionThe Mapping has a small hiccup. for HP-UX systems the map should not contain the NSR. Please delete the entry for the NSR in that map and then you should be ok.
It is recommended that you create a seperate map for the HP-UX systems. I see that you are using the default map only.
We are still not sure how your zone is configured If you can get the outputs from your switches it can help
a) cfgshow
b) zoneshow
with regards,
Mohan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2006 12:44 AM
тАО03-08-2006 12:44 AM
Re: MSL6000 discovery problem
( did you saw in the past the server WWN and you added an alias, or did you insert by hand the server WWN? )
another initiator identify with 375DCC (this may be the switch as well) have got the defaul indexed map.
but I do not see any "ACTIVE INITIATOR"
this may indicate that the NSR cannot see the servers.
Also the Firmware of library and NSR are quite old, and should be updated
The procedure to configure the NSR is the following:
issue a FC discovery, servers should populate the NSR list of "Actice Initiators
then go in mappin, insert account and password
you can use the map name you created (port 0 Device Map FC Port 0 Map) or you can create a new name
then after selecting the map name, go in edit/view
select clear map
the select the priority as Target/bus
Then click fill map
you will see the map filling in, then you can close the window
Now you are back in previous window were you should see a list of Host that have logged in the NSR
select one and click Edit/view
in this windows, you can select the Map Name that you want to associate to this server, then click Modify
and close the windows.
Now back again in previous page, you should click on "Acticate Mapping and Save"
then reboot the NSR from teh left hand menu
that should be all you need
Marino