topic Re: MSL6000 discovery problem in StoreEver Tape Storage

MSL6000 discovery problem

amer_3 — Tue, 07 Mar 2006 11:06:20 GMT

hi
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.

Re: MSL6000 discovery problem

David Ruska — Tue, 07 Mar 2006 12:59:13 GMT

The HP-UX hosts will not show up on the NSR's host list until the HBAs log in. On a Windows hosts, plug 'n play will make them appear automatically, but on HP-UX you will need to do an IOscan or reboot.

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).

Re: MSL6000 discovery problem

amer_3 — Wed, 08 Mar 2006 01:36:43 GMT

hi
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

Re: MSL6000 discovery problem

Mohanasundaram_1 — Wed, 08 Mar 2006 02:21:38 GMT

Hi Amer,

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.

Re: MSL6000 discovery problem

Marino Meloni_1 — Wed, 08 Mar 2006 02:22:58 GMT

First log on the switch and check if the router and the servers are logged on the Fabric
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.

Re: MSL6000 discovery problem

amer_3 — Wed, 08 Mar 2006 06:34:19 GMT

hi

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

Re: MSL6000 discovery problem

Marino Meloni_1 — Wed, 08 Mar 2006 06:48:26 GMT

Sure,
can you click on report, and save the report as a html archive (*.mth) so I can see the situation

marino

Re: MSL6000 discovery problem

amer_3 — Wed, 08 Mar 2006 07:51:39 GMT

hi
this is the report

Re: MSL6000 discovery problem

Mohanasundaram_1 — Wed, 08 Mar 2006 08:32:33 GMT

Hi Amer,

The 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.

Re: MSL6000 discovery problem

Marino Meloni_1 — Wed, 08 Mar 2006 08:44:24 GMT

it appear that you have a host with alias hpux1 having the active map (called port 0 Device Map FC Port 0 Map ) assigned.
( 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

Re: MSL6000 discovery problem

amer_3 — Wed, 08 Mar 2006 09:42:39 GMT

hi
i have added the wwn as it's been recomanded by hp.
i have done as u sujested but the same.
i have attahed the report and the out put of the commands in the switch.
im sorry but im new in this thats why i have alot of problems.
thanks alot

Re: MSL6000 discovery problem

amer_3 — Wed, 08 Mar 2006 09:44:33 GMT

currant report

Re: MSL6000 discovery problem

amer_3 — Wed, 08 Mar 2006 10:59:29 GMT

hi

i have done a farmware up date for the router and reseted the confguration but still the same

amer

Re: MSL6000 discovery problem

Marino Meloni_1 — Wed, 08 Mar 2006 12:48:57 GMT

the zone do not appear complete, you have to add in the backup zone, the library and the HBA of the servers you want they communicate with the library, not only the library

marino

Re: MSL6000 discovery problem

Marino Meloni_1 — Wed, 08 Mar 2006 15:36:35 GMT

best will be to create a Tape_Zone for each Host that need to see the library:

Zone: TAPE_LIBRARY_host1
Zone Member: Domain 1, Port 3
Zone Member: host1 (alias, wwn or Dom/Port )

Zone: TAPE_LIBRARY_host2
Zone Member: Domain 1, Port 3
Zone Member: host2 (alias, wwn or Dom/Port )

etc...

this will keep all commands separeted from each server and from Disk devices

after you enable and save your zone, the WWN of the hosts should appear in the NSR after a FC discovery command.

THen apply the procedure I described before, and you should be able to assign the map to each host discovered

marino

Re: MSL6000 discovery problem

amer_3 — Thu, 09 Mar 2006 06:28:36 GMT

hi
i have done the following:
1- i have created seperate zones for each server with the MSL
2-i have tried another SAN switch and done the config.
3-i have dont the port speed for 2g.
4- i have created a map on the NSR for the HP ux servers and removed the NSR, priority target/buss.

im still can not see the servers

amer

Re: MSL6000 discovery problem

Marino Meloni_1 — Thu, 09 Mar 2006 06:34:23 GMT

have you run an ioscan on the server in oder to populate the NSR discovery window?

Re: MSL6000 discovery problem

amer_3 — Thu, 09 Mar 2006 07:01:44 GMT

hi
i have just done this:
1-i have created a zone and added the MSL and a windows server to it, when i checked the NSR it ditecte it at the hostsand i could and it to a map and i have discoverd the MSL at the windows server.
2- but when i do a FC discovery it dose not discover the server.

i dont know but is there any thing i should do in the UNIX servers.

amer

Re: MSL6000 discovery problem

Marino Meloni_1 — Thu, 09 Mar 2006 07:11:23 GMT

Amer,
my knowledge on Unix is limited, but if now you could configure and see the library in the Windows server, this mean all is working.
Be sure you do not have dual path on the servers, and you zoned the path inactive one

marino

Re: MSL6000 discovery problem

Mohanasundaram_1 — Fri, 10 Mar 2006 14:07:50 GMT

as per HP's SAN checklist, seperate maps should be created for windows and unix.

Pls follow that checklist to create maps.