1846694 Members
3040 Online
110256 Solutions
New Discussion

Re: Zone Problem !!

 
Prashant Bahuguna
Occasional Advisor

Zone Problem !!

Dear all,
I am posting this again since I was not totally convinced.

I have been receiving a service event notification for quite some time now, however I do not understand what action is required since every thing seems to be working perfectly fine. The event log below suggests some zone configuration problem in my SAN switch. But what is exactly, please help. I have also listed the output of fcmsutil command.


>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Fri Jul 6 10:53:52 2007

upclaps sent Event Monitor notification information:

/adapters/events/ql_adapter/0_2_1_0_4_0 is >= 3.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Fri Jul 6 10:53:52 2007
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 62
System..............: upclaps

Summary:
Adapter at hardware path 0/2/1/0/4/0 : Fabric Name Server rejected GPN_FT
query



Description of Error:


lbolt value: 1565

Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request.
Explanation: FC-4 Type not registered.


Probable Cause / Recommended Action:

The HBA port may not be part of a zone.
Please check zone configuration on your switch.


Additional Event Data:
Event Id............: 0x468dd1e800000000
Monitor Version.....: B.02.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.04.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x468dd14f00000000
Additional System Data:
System Model Number.............: 9000/800/rp3440#1
OS Version......................: B.11.23





# fcdlist

/dev/fcd0 0/2/1/0/4/0.1.0.255.0.0.0 fcd_vbus 0x010000
CLAIMED DEVICE HP HSV100 /dev/rscsi/c7t0d0

/dev/fcd0 0/2/1/0/4/0.1.0.0.0 fcd_vbus 0x010000
CLAIMED DEVICE HP HSV100 /dev/rscsi/c6t0d0
CLAIMED DEVICE HP HSV100 /dev/dsk/c6t0d1 /dev/rdsk/c6t0d1
CLAIMED DEVICE HP HSV100 /dev/dsk/c6t0d2 /dev/rdsk/c6t0d2
#
# fcmsutil /dev/fcd0

Vendor ID is = 0x001077
Device ID is = 0x002312
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x0012c7
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.18
ISP Chip version = 3
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x010400
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x50060b00005df20b
N_Port Port World Wide Name = 0x50060b00005df20a
Switch Port World Wide Name = 0x200400051e0214cb
Switch Node World Wide Name = 0x100000051e0214cb
Driver state = ONLINE
Hardware Path is = 0/2/1/0/4/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx Driver B.11.23.04 /ux/core/isu/FCD/kern/src/common/wsio/fcd_init.c:Oct 18 2005,08:19:50

# fcmsutil /dev/fcd0 get fabric
Fabric Port World Wide Name = 0x200400051e0214cb
Fabric Node World Wide Name = 0x100000051e0214cb
#
#
#


This output appears to be perfectly fine to me but the event is troubling me a lot. Please help. Thanks.

Regards,
PB.
1 REPLY 1
Steven E. Protter
Exalted Contributor

Re: Zone Problem !!

Shalom,

If no LUN0 is assigned to an HP-UX system, the system often detects the disk array itself as a disk.

Since its really not a disk, EMS then detects and notifies of a disk failure.

Two fixes:
1) Ignore the message, be fat and happy.
2) Have a LUN assigned to the system as LUN0, the message will go away.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com