strange fibre channel behavior

[Michael Murphy_2]

I am getting EMS errors from my fc enclosure - it doesn't seem to affect performance or access. The strange thing is that it occures day to day a few minutes after the day before (see logs below). Can't be a cron since time continually goes up. Maybe netbackup (veritas) related? Any insight would be helpful

Dec 20 15:00:28 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355462 -r /storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0 -n 350355473 -a
Dec 20 15:00:29 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355478 -r /storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0 -n 350355474 -a
Dec 21 15:04:06 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355462 -r /storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0 -n 350355475 -a
Dec 21 15:04:07 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355478 -r /storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0 -n 350355476 -a
Dec 22 15:07:42 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355462 -r /storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0 -n 350355477 -a
Dec 22 15:07:43 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355478 -r /storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0 -n 350355478 -a
Dec 23 15:11:15 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355462 -r /storage/events/enclosures/ses_enclosure/8_8.8.0.255.1.6.0 -n 350355479 -a
Dec 23 15:11:17 oh30 EMS [5346]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 350355478 -r /storage/events/enclosures/ses_enclosure/8_12.8.0.255.1.6.0 -n 350355480 -a

[James A. Donovan]

You need to run any one of the commands listed to get more details....

post the results...

[Steven E. Protter]

Its not strange at all actually, you're just not familiar with this issue.

If you connect a fiber card to a disk array or fiber switch and don't have LUN0 assigned to that card, the fiber switch or disk array appears to your system as LUN0

Your system thinks its a disk and when it doesn't respond like a disk EMS picks up the error.

You can make the EMS messages go away by assigning LUN0 on that card. All it needs is some disk space and EMS thinks its a disk.

You might also be able to fix this by changing zoning on the fiber switch, but I can't help you with that.

SEP