SEO

#1 (**permalink**) 01-05-2008, 08:03 AM

Hi there !
this is what i have:

server: p650 6M2
os: aix 5.2 ml1
fc adapter: 2 adapters - IBM 6239 with Firmware version 1.81X1
fc switch: migrating from mcdata-ds24m2 to cisco mds9140. one adapter
connected to the mcdata, and one connected to the new cisco mds9140

my problem: the fc adapter does not connect properly to the cisco
mds9140 switch. there is a link, but the switch gui interface shows
link failure. when i examined the fc-scsi-protocol characteristics i
noticed a difference between the 2 adapters:

the command I issued: "lsattr -EHl fscsi0 (or fscsi1)"
the adapter that is connected to the old mcdata switch, and is working
properly has the property "attach=switch" and the adapter that is
connected to the new cisco switch and has a problem has the property
"attach=al". this property is NOT user-settable, so i don't know what
to do in order to change this value.

i also tried to change the admin mode of the port in the switch - to
fix it as an F port, and fix it to 2gb speed, but that didn't help.

is there anything else you can advise?
thanks,
yaron

#2 (**permalink**) 01-05-2008, 08:03 AM

raziel99 wrote:
> Hi there !
> this is what i have:
>
> server: p650 6M2
> os: aix 5.2 ml1
> fc adapter: 2 adapters - IBM 6239 with Firmware version 1.81X1
> fc switch: migrating from mcdata-ds24m2 to cisco mds9140. one adapter
> connected to the mcdata, and one connected to the new cisco mds9140
>
> my problem: the fc adapter does not connect properly to the cisco
> mds9140 switch. there is a link, but the switch gui interface shows
> link failure. when i examined the fc-scsi-protocol characteristics i
> noticed a difference between the 2 adapters:
>
> the command I issued: "lsattr -EHl fscsi0 (or fscsi1)"
> the adapter that is connected to the old mcdata switch, and is working
> properly has the property "attach=switch" and the adapter that is
> connected to the new cisco switch and has a problem has the property
> "attach=al". this property is NOT user-settable, so i don't know what
> to do in order to change this value.
>
> i also tried to change the admin mode of the port in the switch - to
> fix it as an F port, and fix it to 2gb speed, but that didn't help.
>
> is there anything else you can advise?
> thanks,
> yaron
Check and compare with
$ lsattr -EHl fcs0
$ lsattr -EHl fcs1
the fc-hba settings.

If you get no link on the fc-hba attached to your cisco you might have
to cross the cable on one end. Its pretty easy to build and attach the
cable the "wrong way"
Example:
wrong:
hba switch cisco
TX RX TX TX
RX TX RX RX

correct:
hba switch cisco
TX -> RX TX -> RX
RX -> TX RX -> TX

hth
Hajo

#3 (**permalink**) 01-05-2008, 08:03 AM

On Tuesday 06 December 2005 16:40, raziel99 wrote:

> the command I issued: "lsattr -EHl fscsi0 (or fscsi1)"
> the adapter that is connected to the old mcdata switch, and is
> working properly has the property "attach=switch" and the
> adapter that is connected to the new cisco switch and has a
> problem has the property "attach=al". this property is NOT
> user-settable, so i don't know what to do in order to change
> this value.

Try deleting the adapter and reconfiguring it (assuming it is
fcs1):

rmdev -Rdl fcs1
cfgmgr

The fscsi1 device should come up with 'attach=switch' if the
Cisco switch is in a SAN fabric.

If this adapter was never connected before, there is a good
chance that the initial value of 'attach' will be 'al', since
new adapters usually come with plugs that emulate a loop. As
you said, you cannot change this value on the fly, only by
reconfiguring the device.

Dmitri

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

aix fc switch connection problem