Path Failed to Storrage box....

[sreekanthtm]

Iam getting following error in log msgs...


qla2xxx 0000:08:00.0: LOOP DOWN detected (4).
rport-3:0-0: blocked FC remote port time out: saving binding
Error:Mpx:Path Bus 3 Tgt 0 Lun 257 to 000190102478 is dead.
Error:Mpx:Killing bus 3 to Symmetrix 000190102478 port 9aA.
Error:Mpx:Path Bus 3 Tgt 0 Lun 275 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 274 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 272 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 263 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 273 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 258 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 259 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 260 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 261 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 264 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 262 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 265 to 000190102478 is dead.
Error:Mpx:Path Bus 3 Tgt 0 Lun 256 to 000190102478 is dead.
Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!
device eth0 entered promiscuous mode
audit(1217254763.351:11): dev=eth0 prom=256 old_prom=0 auid=4294967295
device eth0 left promiscuous mode
audit(1217254763.354:12): dev=eth0 prom=0 old_prom=256 auid=4294967295
device eth0 entered promiscuous mode


How can I confirm weather its a HBA problem or storrage issue??!!

[Ivan Ferreira]

>>> How can I confirm weather its a HBA problem or storrage issue??!!

According to this message:

>>> qla2xxx 0000:08:00.0: LOOP DOWN detected (4).

This should be a problem with our HBA, your cable or your sanswitch port. You are getting LOOP DOWN messages.

In your profile I see "I have assigned points to 42 of 105 responses".

Please keep asigning point to the answers you get.

Have a nice day.

[sreekanthtm]

ok..... But what abt the next line.

'rport-3:0-0: blocked FC remote port time out:'

Rgds
sreekanth

[Matti_Kurkela · Accepted solution]

Cause and effect.

The first message says that one of your FibreChannel connections has failed.

The "blocked FC remote port time out" happens because whatever operation was going on the FibreChannel connection times out because the fiber loop failed.

The messages beginning with "Error:Mpx" are coming your FC multipath software. It is reacting to the FC loop failure and reporting each and every LUN path that has become inaccessible because of the fault.

The "Warning: /proc/ide/hd?/settings..." message is completely unrelated. It is a warning, not an error. Someone was using a program that accessed IDE HD settings using a method that will be removed in some near-future version: the warning is a friendly reminder that this program will need updating at that time.

The "device eth0 entered/left promiscuous mode" and the corresponding audit lines would be caused by someone running tcpdump or any other tool that uses the eth0 NIC to read *all* traffic coming to the NIC.

MK