Start a Conversation

Unsolved

This post is more than 5 years old

1494

November 10th, 2010 06:00

Basic NDMP connectivity question

I'm at the very beginning of lookng at configuring NDMP backups for our new NS480.

Our tape library is fibre channel SAN attached and cannot be dedicated to the NS480. I've therefore assumed that the AUX0 port on the NS480 can be attached to a fabric switch and zoned to have full acces to the TL.

When the facbric port connected to AUX0 is enabled the link does not come up, suggesting that maybe the AUX0 port is not enabled. The documentation suggests that "The hardware autodetects and configures for arbitrated loop or switched fabric connections". Does anyone know is this true, or does the AUX0 port need some configuration.

I'm a little reluctant to start forcing link speeds and rebooting data movers without fist knowing if this action is required.

1 Rookie

 • 

20.4K Posts

November 10th, 2010 06:00

aux0 should automatically login, i've never had to force anything on the datamover side. Safe to assume that port on the switch is not "shut" ?

8.6K Posts

November 10th, 2010 06:00

yes, attaching a FC tape drive through a FC switch to the AUX0 port is the most common config

There aren't many config options there - see the NDMP manual

I think you need to run a server_devconfig to discover the tape drives

November 10th, 2010 10:00

What is your switch vendor and model?  As dynamox says, be sure the port is not shutdown.  You shouldn't have to set anything on the switch port.  Can you see anything in the switch logs, like a portfail or negotiation error?  Twice now, I've used a bad patch cable on the AUX0 and AUX1 ports, then wondered why I had no link.  Otherwise, you can use the server_devconfig commands to try and scan the SCSI bus for devices.

server_devconfig server_# -probe -scsi -nondisks -all should scan all available buses (including the AUX0 and AUX1 ports) without having to reboot the datamovers.  You should see some kind of actvitity on the switch port, perhaps even some errors, to help debug any switch errors.

Let us know how it goes!

Karl

8.6K Posts

November 10th, 2010 11:00

I agree with with Karl - for this kind of problem it's rarely the Celerra - most likely cabling or switch (or plugging the cable into the wrong or standby data mover )

Rainer

19 Posts

November 11th, 2010 00:00

Guys,

Thankyou all for you comments.

It would appear after all that I have a duff AUX0 port on the primary data mover. I get an instant link up and fabric login if I connect either AUX1 on the primary, or AUX0 on the standby.

Regards

Andrew.

8.6K Posts

November 11th, 2010 01:00

try swapping the SFP's - most likely it's just the SFP being dead or not fully plugged in

they are customer replaceable online

19 Posts

November 11th, 2010 02:00

Yeah – I did try that first.

In hindsight I should have tried the other ports before posting the question, but you don’t expect a new onboard port to be dead. I assumed I must have been missing something.

99 Posts

November 11th, 2010 05:00

Good morning


You can try running a .server_config command against the port.  Below are the ones that may help get the port working again:

fcp portreset=n ........ Reset fibre port n
fcp rediscover=n ....... Force fabric discovery process on port n Bounces the link, but does not reset the port
fcp rescan ............. Force a rescan of all LUNS
fcp reset .............. Reset all fibre ports

The command would be similar to the following:
.server_config server_2 -v "fcp portreset=2” [forcing HBA2 to log back into fabric]


Also, please note that support may request a datamover reboot before attempting to have the current one replaced.  If you decide to that, the the above are not required.

Let me know if this helped.

Sebby Robles
eServices Support
EMC Celerra Support

19 Posts

November 12th, 2010 01:00

I’ve ended up running the following command to confirm the port problem;

.server_config server_2 –v 64 “fcp show”

Which has given the following output;

server_2 : commands processed: 1

command(s) succeeded

output is complete

FCP ONLINE HBA 0: ALPA 000001 WWN: 5006016041e11c75 QX4 4G

FCP scsi-0: HBA 0: ALPA 0000ef SP-a00: 500601604460374e Class 3

FCP ONLINE HBA 1: ALPA 000001 WWN: 5006016141e11c75 QX4 4G

FCP scsi-16: HBA 1: ALPA 0000ef SP-b00: 500601684460374e Class 3

FCP OFFLINE HBA 2: ALPA 000001 WWN: 5006016241e11c75 QX4 SFP Bad EEPROM

FCP scsi-32: HBA 2: CHAINS 32 - 47 OFFLINE

FCP ONLINE HBA 3: S_ID 492201 WWN: 5006016341e11c75 QX4 4G

FCP scsi-48: HBA 3: D_ID 49000e N_PORT: 100000e00223a141 Class 3

1289487346: ADMIN: 6: Command succeeded: fcp show

I’ve now logged a support call for the failed port.

No Events found!

Top