"when you talked to dell rep, did they re-image the array?"
Yup - we re-imaged both the image types offered (mif and iif). Same problem as before.
Yes, I can connect via serial/hyperterm. It seems to POST without problem, but that doesn't mean I know what it is saying. I'll seutp logging and post a log of the boot.
if there are no errors, the post will present some int 13h load statements at the end and it will stop updating...it then passed the control to embedded windows... rest logs come into windows logs... i am going offline now but you can paste the local event log now and i or someone else should be able to comment on that...otherwise emc is just a call away
The look in the text file near the begining of the file - you should see a listing of the software loaded on the array - look for the packages installed - see example below - what you want to see if a listing for "ManagementUI"- if you don't have this then you can't start the GUI on the array using IE - you'll need to use the "Off-Array Management Server" and the "Off-Array Manager" packages - this installs on your Windows workstation.:
Name of the software package: Navisphere Revision of the software package: 6.5.0.3.7 Commit Required: NO Revert Possible: NO Active State: YES Dependent packages: ManagementServer 6.5.0.3.10, Base 02.05.1.60.5.009 Required packages: Base 120 Is installation completed: YES Is this System Software: NO
Name of the software package: ManagementServer Revision of the software package: 6.5.0.3.10 Commit Required: NO Revert Possible: NO Active State: YES Dependent packages: ManagementUI 6.5.0.3.3 Required packages: Navisphere 120 Is installation completed: YES Is this System Software: NO
Name of the software package: ManagementUI Revision of the software package: 6.5.0.3.3 Commit Required: NO Revert Possible: NO Active State: YES Required packages: ManagementServer <=120, ManagementServer >=116, ManagementServerBase MUST NOT BE INSTALLED Is installation completed: YES Is this System Software:
Device Event (0xEF): 0x00030016 Target 0 is online
Target 1 is online
Target 2 is online
Target 3 is online
Target 4 is online
Relocating Data Directory Boot Service (DDBS)...
Autoflash POST?
POST/DIAG image located at sector LBA 0x00012048
Autoflash BIOS?
BIOS image located at sector LBA 0x00011048
EndTime: 02/19/2007 16:55:08
int13 - RESET (1) DDBS: MDB read from both disks. DDBS: Chassis and disk WWN seeds match. DDBS: First disk is valid for boot. DDBS: Second disk is valid for boot.
NT FLARE image (0x00400007) located at sector LBA 0x0002284B
on the final thoughts, you can log on to each sp and issue hfoff. then reboot and again connect via emc remote and issue hfon and then reboot again. this is a L2 solution but i am not sure if its emc would advise customers to run it.
only piece thats refusing to run or misbehaving is naviagent.exe i believe. thats the reason navicli output is useless.
i dont remember if i ever saw that invalid drive id error before in post... also for the ata errors - even though its a failover from fc series, the boot image used to boot sp (on 1st 5 DAE drives) should appear as the same drive and post should not throw that error.
this seems getting out of me...time to involve emc level 2 as they have more sp os troubleshooting aids...
This is really a T2 solution and I would suggest at this point to open a case with EMC for this problem.
The FLARE code is 6.4, which is release 11, considered unsupported at this time - current release is 19 for the cx400 (also, this is the last release for the cx200/400/600 line).
SeanGalyen
12 Posts
0
February 19th, 2007 09:00
Yup - we re-imaged both the image types offered (mif and iif). Same problem as before.
Yes, I can connect via serial/hyperterm. It seems to POST without problem, but that doesn't mean I know what it is saying. I'll seutp logging and post a log of the boot.
Kiran3
410 Posts
0
February 19th, 2007 09:00
rest logs come into windows logs...
i am going offline now but you can paste the local event log now and i or someone else should be able to comment on that...otherwise emc is just a call away
kelleg
4 Operator
•
4.5K Posts
1
February 19th, 2007 10:00
glenk
SeanGalyen
12 Posts
0
February 19th, 2007 10:00
kelleg
4 Operator
•
4.5K Posts
0
February 19th, 2007 10:00
Can you run the:
navicli -h IP_Address getall > SPA_getall.txt
The look in the text file near the begining of the file - you should see a listing of the software loaded on the array - look for the packages installed - see example below - what you want to see if a listing for "ManagementUI"- if you don't have this then you can't start the GUI on the array using IE - you'll need to use the "Off-Array Management Server" and the "Off-Array Manager" packages - this installs on your Windows workstation.:
Name of the software package: Navisphere
Revision of the software package: 6.5.0.3.7
Commit Required: NO
Revert Possible: NO
Active State: YES
Dependent packages: ManagementServer 6.5.0.3.10, Base 02.05.1.60.5.009
Required packages: Base 120
Is installation completed: YES
Is this System Software: NO
Name of the software package: ManagementServer
Revision of the software package: 6.5.0.3.10
Commit Required: NO
Revert Possible: NO
Active State: YES
Dependent packages: ManagementUI 6.5.0.3.3
Required packages: Navisphere 120
Is installation completed: YES
Is this System Software: NO
Name of the software package: ManagementUI
Revision of the software package: 6.5.0.3.3
Commit Required: NO
Revert Possible: NO
Active State: YES
Required packages: ManagementServer <=120, ManagementServer >=116, ManagementServerBase MUST NOT BE INSTALLED
Is installation completed: YES
Is this System Software:
glenk
SeanGalyen
12 Posts
0
February 19th, 2007 10:00
Disk Array Subsystem Controller
Model: CX400
DiagName: Extended POST
DiagRev: Rev. 01.38
Build Date: Fri Feb 21 15:42:43 2003
StartTime: 02/19/2007 16:54:47
SaSerialNo: APM00032300038
ABabCabcDabcdeEFGabHabcIabcJabcKabLabMabNabOabPabQRST
Initializing back end FIBRE...
PCI Config Reg: 1.4.0 0x0157
FCDMTL 0 [1.4.0] Dual Mode Fibre init - OSW DB PTR 0x04C00000
FCDMTL 0 [1.4.0] Cached memory - 0xF5E67 bytes @ 0x4C006A8
FCDMTL 0 [1.4.0] Noncached memory - 0xBF3BF bytes @ 0x4CF650F (0x4CF650F phys)
FCDMTL 0 [1.4.0] DVM Initialized
FCDMTL 0 [1.4.0] IMQ base ptr = 04D70000; IMQ length = 8000
Dualmode fibre init completed
FCDMTL 0 [1.4.0] TPM Notify: st=0xA000000, flg=0x4, cmd=0x1
FCDMTL 0 [1.4.0] TPM Hndle API Event: cntx=0x4C004C4, evnt=0x4002, info=0x0
FCDMTL 0 [1.4.0] TPM Lnk Up: state=0xA000000, flg=0x84
FCDMTL 0 [1.4.0] DVM Disc Comp- Dev List Size: 3
FCDMTL 0 [1.4.0] TPM Notify: st=0xA000000, flg=0x208, cmd=0x0
Link Event: 0x00030001
Link Event: 0x00030005
FCDMTL 0 [1.4.0] TPM Notify: st=0xA000002, flg=0x200, cmd=0x4
Device Event (0xFFFFFC): 0x00030015
FCDMTL 0 [1.4.0] TPM Notify: st=0xA000000, flg=0x200, cmd=0x2
FCDMTL 0 [1.4.0] TPM Hndle API Event: cntx=0x4C004C4, evnt=0x400A, info=0x0
FCDMTL 0 [1.4.0] TPM Lnk Dwn: st=0xA000001, flg=0x201, evnt=0x400A
FCDMTL 0 [1.4.0] TPM Hndle API Event: cntx=0x4C004C4, evnt=0x4002, info=0x0
FCDMTL 0 [1.4.0] TPM Lnk Up: state=0xA000001, flg=0x8005
FCDMTL 0 [1.4.0] DVM Duplicate address id already in list: E1
FCDMTL 0 [1.4.0] DVM Duplicate address id already in list: E2
FCDMTL 0 [1.4.0] DVM Duplicate address id already in list: EF
FCDMTL 0 [1.4.0] DVM Duplicate address id already in list: E4
FCDMTL 0 [1.4.0] DVM Duplicate address id already in list: E8
Device Event (0xE1): 0x00030012
Device Event (0xE2): 0x00030012
Device Event (0xE4): 0x00030012
Device Event (0xE8): 0x00030012
Device Event (0xEF): 0x00030012
FCDMTL 0 [1.4.0] DVM Disc Comp- Dev List Size: 8
FCDMTL 0 [1.4.0] TPM Notify: st=0xA000001, flg=0x8209, cmd=0x0
Link Event: 0x00030001
FCDMTL 0 [1.4.0] TPM Notify: st=0xA000002, flg=0x200, cmd=0x5
FCDMTL 0 [1.4.0] TPM Resume SCSI Issued: tgdb = 0x4C004C4
Device Event (0xEF): 0x00030016
Target 0 is online
Target 1 is online
Target 2 is online
Target 3 is online
Target 4 is online
Relocating Data Directory Boot Service (DDBS)...
Autoflash POST?
POST/DIAG image located at sector LBA 0x00012048
Autoflash BIOS?
BIOS image located at sector LBA 0x00011048
EndTime: 02/19/2007 16:55:08
int13 - RESET (1)
DDBS: MDB read from both disks.
DDBS: Chassis and disk WWN seeds match.
DDBS: First disk is valid for boot.
DDBS: Second disk is valid for boot.
NT FLARE image (0x00400007) located at sector LBA 0x0002284B
Disk Set: 0 2
Total Sectors: 0x005821A1
Relative Sectors: 0x0000003F
Calculated mirror drive geometry:
Sectors: 63
Heads: 240
Cylinders: 382
Capacity: 5775840 sectors
Total Sectors: 0x005821A1
Relative Sectors: 0x0000003F
Calculated mirror drive geometry:
Sectors: 63
Heads: 240
Cylinders: 382
Capacity: 5775840 sectors
int13 - READ PARAMETERS (19)
int13 - READ PARAMETERS (22)
int13 - DRIVE TYPE (57)
int13 - READ PARAMETERS (58)
int13 - DRIVE TYPE (59)
Error : Invalid Drive ID - 0x81
int13 - CHECK EXTENSIONS PRESENT (61)
int13 - GET DRIVE PARAMETERS (Extended) (62)
int13 - READ PARAMETERS (63)
int13 - READ PARAMETERS (65)
int13 - READ PARAMETERS (1252)
int13 - READ PARAMETERS (1292)
int13 - READ PARAMETERS (1329)
int13 - READ PARAMETERS (1366)
int13 - READ PARAMETERS (1407)
int13 - READ PARAMETERS (1636)
int13 - READ PARAMETERS (1671)
int13 - READ PARAMETERS (1705)
int13 - READ PARAMETERS (1741)
int13 - READ PARAMETERS (1803)
int13 - READ PARAMETERS (1837)
int13 - READ PARAMETERS (1910)
------------
So, the Invalid Drive ID - 0x81 is disconcerting but otherwise it loads into the NT OS as expected, just can't see the array.
kelleg
4 Operator
•
4.5K Posts
0
February 19th, 2007 11:00
SeanGalyen
12 Posts
0
February 19th, 2007 11:00
Agent Rev: 6.4.0 (5.2)
Name: K10
Desc:
Node: A-APM00032300772
...and doesn't return anything else, like it should!
A bunch of other command attempts return this error:
Cannot access device
SeanGalyen
12 Posts
0
February 19th, 2007 13:00
Agent Rev: 6.4.0 (5.2)
Name: K10
Desc:
Node: A-APM00032300772
====
Regrettably, that's it!
Kiran3
410 Posts
0
February 19th, 2007 17:00
this is a L2 solution but i am not sure if its emc would advise customers to run it.
see if that gets it working.
Kiran3
410 Posts
0
February 19th, 2007 17:00
only piece thats refusing to run or misbehaving is naviagent.exe i believe. thats the reason navicli output is useless.
i dont remember if i ever saw that invalid drive id error before in post...
also for the ata errors - even though its a failover from fc series, the boot image used to boot sp (on 1st 5 DAE drives) should appear as the same drive and post should not throw that error.
this seems getting out of me...time to involve emc level 2 as they have more sp os troubleshooting aids...
kelleg
4 Operator
•
4.5K Posts
0
February 20th, 2007 09:00
The FLARE code is 6.4, which is release 11, considered unsupported at this time - current release is 19 for the cx400 (also, this is the last release for the cx200/400/600 line).
glenk