Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

access logix & engineering mode in FC4500 1

Status
Not open for further replies.

siemenslimited

Technical User
Mar 26, 2005
1
0
0
EG
Hello all
i have a FC4500 storage with access logix firmware which was running before and we had to do a reinstallation so we had to destroy alla LUNS and reinstalled all the servers attached to it after that we were not able to connect to that storage with the navisphere agent ot manager we have even tried to connect to it throw the seriaql cable with the agent but it gives access denied
emc say that you have to shutdown the access logix from the engineering mode
but the problem that i can not go into engineering mode
and i tried the FLARE but i was not able to access it ether
i tried both the CTL+shift+F12 sequance and the {}{} sequance but both didn't work with the storage and by the way it is writing FC4400 when it is starting not fc4500 as it should be
so i was wondering if anyone can give me support about that problem.
 
FC4400 is ok. That is identifying the storage processor. FC4500 is the complete dpe.
If there are no luns, you'll have to go thru the serial port to set at least one up.
You have to have administrator priveledges on the pc you're using to connect to the serial port to escape the 'access denied' message.
For the Ctrl Shift F12 sequence to work, you must have the storage array highlighted in Navi Manager.
Also, the array serial port may be set to 19200 instead of 9600. You might want to give that a try.
 
A little bit of wrong information given.

Via serial port, if you use a terminal program, you will either land at an FCLI prompt, or a "Starting Serial Mode" with no prompt. If the latter, hit @$@$ to get into debugger prompt "AROM>"

From the debugger, type "menu". From the menu, choose 7 for "nonvol menu", where you can set certain nonvolatile settings.

From there, choose 11, "Serial Mode", and from there, choose "1 - FCLI mode".

Then choose 0 to exit, and then 10 for FLARE menu, and then 5 to start flare.

You should come up to an FLCI prompt.

hit ? for a list of available commands.

From there you can destroy all existing RAID groups and start fresh.

Once you've started fresh, you ~should~ be able to use Navisphere even though there aren't any storage groups yet.
 
I wanted to add that once you are communicating through Navisphere to the array, you can use the CTRL-SHIFT-F12 sequence, but that requires a password to be typed after it (you won't get a popup dialogue on v5 and prior, you need to just hit CTRL-SHIFT-F12 and then the password).

I probably shouldn't pass along the password, I'm a former EMC employee.
 
You're concerned about giving out a password but don't mind explaining how to get into fcli? Both are company confidential.
 
You do have a valid point, but let me clarify.

How to get into FCLI mode is referenced on another website, and there are one or more links from this site to that site. All you have to do is use Google and type "CLARiiON FCLI" and you can find all sorts of info about FCLI. If you attempt to find the Navisphere password in a similar fashion, it's much harder to find.

You can find it on this board, however. If someone really wants it, they will find it here.

I also learned the FCLI information on my own, after leaving EMC. I wasn't a CE, I was an SE, and as such I wasn't officially privy to CLARiiON FCLI. Heck, I was selling FC4700, no FCLI there!

On the other hand, I was told about the password for Navisphere when I was employed at EMC. It's confidential information that I learned while employed, which is very different from confidential information leaked to the broad public that I learned well after my departure.

Hope that clears up my stance.

--
Bill Plein
a.k.a. squiddog
Contact me at
 
hello thx for your great help after beeing in the flci mode i can't configure a raid group
for example i get for

bind r0 0_1 0_2 0_3 0_4
05/13/2005 21:19:03
fcli> RB error full 0x50040101
part category 0x5 code 0x5004 error num 0x4 status 0x1 type 0x1
Bind ERROR: Bind Array: Category 0x5 Num 0x4 Type 0x1

Sunburst Code: HOST_BIND_BAD_FRU_CONFIGURATION
Status recv'd opcode 0x81 status 0x50040101
HI_BIND


all drives are unbound and they work i have set them to 0. is there a way to get the system back to factory settings? or what is the problem thx kewitz
 
What FC-series array is that from?

Do all the disks show us as good? What's the output from "lustat", "di -l", and "di 0"?



--
Bill Plein
a.k.a. squiddog
Contact me at
 
hello all lights are green i can use the zero_disk all without problems, all disks are unbound seems to be everything ok. is there a way to get the system back to factory default so that we have a starting point.

fcli> lustat
Logical Unit Summary:

Raid Dflt. Unit
LUN Group Owner Type Capacity Cache State Frus
--- ----- ----- ------ -------- ----- ------- ------------------

05/14/2005 06:11:12
fcli>
fcli> di -l
Fru Vendor Model Rev. Serial no. Capacity
==== ======== ================ ==== ============ =========
0. SEAGATE ST118202 CLAR18 3528 LKC76254 0x2141301
1. SEAGATE ST318203 CLAR18 3844 LRJ83357 0x2141301
2. SEAGATE ST318203 CLAR18 3844 LRJ47560 0x2141301
3. SEAGATE ST318203 CLAR18 3844 LRJ63231 0x2141301
4. SEAGATE ST318203 CLAR18 3844 LRJ66207 0x2141301
5. SEAGATE ST318304 CLAR18 3A90 3EL036S7 0x2141301
6. SEAGATE ST318203 CLAR18 3844 LRJ79445 0x2141301
7. SEAGATE ST318203 CLAR18 3844 LRJ47666 0x2141301
8. SEAGATE ST318203 CLAR18 3844 LRJ73091 0x2141301
9. SEAGATE ST318203 CLAR18 3844 LRJ54718 0x2141301

05/14/2005 06:11:56
fcli>
Performance Statistics for Disk Module 0_0
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST118202 CLAR18
Drive Firmware: 3528
Drive Serial #: LKC76254
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118028197

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2868
Write Requests: 2375
Kbytes Read: 3425
Kbytes Written: 1193
Average Disk Service Time: 3 ms
Average Disk Busy/Idle Time: 192 / 330376 ms

Press any key to continue...(or 'q' to Quit)
ess any key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_1
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ83357
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2868
Write Requests: 2375
Kbytes Read: 3425
Kbytes Written: 1193
Average Disk Service Time: 4 ms
Average Disk Busy/Idle Time: 219 / 330524 ms

Press any key to continue...(or 'q' to Quit)

ress any key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_2
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ47560
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2868
Write Requests: 2375
Kbytes Read: 3425
Kbytes Written: 1193
Average Disk Service Time: 4 ms
Average Disk Busy/Idle Time: 218 / 330725 ms

Press any key to continue...(or 'q' to Quit)
s any key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_3
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ63231
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 6 ms
Average Disk Busy/Idle Time: 0 / 331098 ms

Press any key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_4
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ66207
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 5 ms
Average Disk Busy/Idle Time: 0 / 331201 ms

Press any key to continue...(or 'q' to Quit)
ess any key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_5
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318304 CLAR18
Drive Firmware: 3A90
Drive Serial #: 3EL036S7
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118031737

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 3 ms
Average Disk Busy/Idle Time: 0 / 331379 ms

Press any key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_6
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ79445
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 5 ms
Average Disk Busy/Idle Time: 0 / 331512 ms

Performance Statistics for Disk Module 0_7
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ47666
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 5 ms
Average Disk Busy/Idle Time: 0 / 331629 ms

Press any key to continue...(or 'q' to Quit)
ny key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_8
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ73091
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 1 ms
Average Disk Busy/Idle Time: 0 / 331753 ms

Press any key to continue...(or 'q' to Quit)
key to continue...(or 'q' to Quit)
Performance Statistics for Disk Module 0_9
Description: 18 GB SCSI Disk
Drive Vendor: SEAGATE
Drive Model Info: ST318203 CLAR18
Drive Firmware: 3844
Drive Serial #: LRJ54718
Drive Capacity: 0x2141301 sectors
User Space: 0x20B2301 sectors
Zeroed_Mark: 0x8F000
Additional Info 1: DG118030147

Raid Group (hex): 0x00
Number of units: 0
L2 Cache capacity: 0 bytes
State: UNBOUND
This Disk Module is Not Part of Any Logical Unit
Read Requests: 2
Write Requests: 0
Kbytes Read: 1
Kbytes Written: 0
Average Disk Service Time: 5 ms
Average Disk Busy/Idle Time: 0 / 331856 ms

Press any key to continue...(or 'q' to Quit)
 
Definitely looks OK.

I know of no ~direct~ method for setting everything to a factory default. It's really a matter of inspection and changing settings for people like me who have figured this stuff out bit by bit.

How about the output from "o" "o -h", "h", "ctr", "spstat".

--
Bill Plein
a.k.a. squiddog
Contact me at
 
hello
do you know a source where to get navisphere for a fair price (christiane@kewitz.de)
here are the results
fcli> o
Current system type is 3

05/15/2005 17:18:34
fcli> o -h
setopt/o - set/display the system options package number
Usage: setopt -h
setopt
setopt <#> new system options package number, in hex
supported options:
1: DEFAULT_SYSTEM_TYPE
2: HP_SYSTEM_TYPE
3: FIBRE_OPEN_SYSTEM_TYPE
9: SGI_SYSTEM_TYPE
A: HP2_SYSTEM_TYPE
13: DELL_SYSTEM_TYPE
14: OPEN_SCSI2_SYSTEM_TYPE
16: FUJITSU_SEIMENS_SYSTEM_TYPE
17: SGI_NORESTRICT_SYSTEM_TYPE
1B: HP_SAUNA_AT_SYSTEM_TYPE


05/15/2005 17:18:44
fcli>

fcli> h
Addressing model: LUN
Target initiated negotiation: DISABLED
Substitute busy for qfull: DISABLED
Passive Not Ready Mode: DISABLED
LUN_Z Mode: DISABLED
VPP80 Mode: DISABLED ( ARRAY SN )
Mode page 8: DISABLED
Recovered error log reporting: DISABLED
Allow non-mirrored cache: DISABLED
Auto trespass: DISABLED
Auto format: DISABLED
Raid Optimization: Mixed LUNs
Raid-3 Write Buffering: DISABLED
Loop Failover: DISABLED
Private Loop Enable: DISABLED
Discover Mode: Auto
Discovery Needed: NO
Single-Loop Failed: NO
Fibre-Loop Failed: NO
FED IO Acceptance Algorithm: First-Come/First-Serve
Onboard IO Priority (SFE): DISABLED

Press any key to continue....
The scsi3 option: ENABLED

05/15/2005 17:20:32
fcli>

fcli> ctr
RAID Controller Configuration:
System Type: 3
Restrict drives: ON
RAID 3 Enabled: OFF
Stats Logging: ON
System Config Reg: 0003
Auto format enabled: OFF
Soft Addressing: ON
Display page size: 22

05/15/2005 17:20:59
fcli>

fcli> spstat
SP A LOOP ID 0x0 (0.)
PROM Revision: 2.10 Microcode Revision: 06.32.16
Statistics Logging: ENABLED PEER SP: PRESENT
Disk Write Caching: DISABLED R3 Write Buffering: DISABLED
WRITE CACHE: DISABLED READ CACHE: DISABLED
RAID OPTIMIZED: Mixed LUNs SP TYPE: ALPINE
LUN REMAPPING: ENABLED
A: DP 00% TOTAL 0000 DIRTY 0000
B: TOTAL 0000
U: DP 00% TOTAL 0000
Requests Complete: 0
SPS A: --
SPS B: --

Press any key to continue....

slot : 0 1 2 3 4 5 6 7 8 9 | PSA PSB FAN
DPE-state: UNB UNB UNB UNB UNB UNB UNB UNB UNB UNB | OK OK OK OK
Unit/Group : G00 G00 G00 G00 G00 G00 G00 G00 G00 G00 |

05/15/2005 17:21:46
fcli>

thx a lot for your help
kewitz
 
hello
it must be something with RB, the message is RB error full, when i change to o 1. same error as for the bind
thx
kewitz

o 1
o: About to reboot controller

05/15/2005 17:30:43
fcli> RB error full 0x101C0101
part category 0x1 code 0x101C error num 0x1C status 0x1 type 0x1
Change System Type ERROR: Category 0x1 Num 0x1C Type 0x1

Sunburst Code: HOST_INVALID_SYSTEM_TYPE
Status recv'd opcode 0xA1 status 0x101C0101


05/15/2005 17:30:55
fcli>
 
I don't know where you can buy Navisphere cheap. Once in a while I have seen them on eBay. I'm pretty sure that EMC's licensing seeks to prevent people reselling their versions, but it happens anyhow from time to time.

Try using "cl" to clear the error log, then reboot the array, then use "getlog" and put a complete output of the log in a post here.

My 4500 has different options shown for "o", it probably has something to do with either a slightly different revision of FLARE, or some bits set somewhere (most likely from the debugger) that restrict options for different OEMs.

I have no idea what "RB error full" could be, the only reference to "RB" that I'm even passingly familiar with is "reallocation block", but your drives are zero'd so I don't think it's that. Note that it is NORMAL for your array to show you some number of options, but then you can't set an option, such as with "o 1". Not all of those "o" settings are valid for your array. The "generic" one is "3". One thing that concerns me is that output:
SPS A: --
SPS B: --

Mine show "OK" for both. So whatever is causing that "RB error full" may also be preventing the system from coming up fully.

How about sending the output from "c" as well. Do you have memory allocated to the system?

Here is my output from that screen:

fcli> c
SP B LOOP ID 0x1 (1.)
Write Cache type and state: MIRRORED ENABLED
Local, Peer read cache state: ENABLED ENABLED
Peer read cache state: ENABLED
Cache page size: 8 KB
High, Low watermark levels: 90 % 50 %
SPS testing is: ENABLED for SUNDAY - 10:05

SP-A SP-B
System Memory Size: 24 MB 24 MB
Combined (L1+L2) write cache size: 414 MB 414 MB
Write cache size: 414 MB 414 MB
Read cache size: 74 MB 74 MB
L2 cache map size: 0 MB 0 MB
L2 cache non_map size: 0 MB 0 MB
Requested RAID-3 memory size: 0 MB 0 MB
Allocated RAID-3 memory size: 0 MB 0 MB
Available Memory: 0 MB 0 MB


--
Bill Plein
a.k.a. squiddog
Contact me at
 
hello it looks that not much ram is allocated
here the result
fcli> c
SP A LOOP ID 0x0 (0.)
Write Cache type and state: MIRRORED DISABLED
Local, Peer read cache state: DISABLED DISABLED
Peer read cache state: DISABLED
Cache page size: 8 KB
High, Low watermark levels: 70 % 60 %
SPS testing is: ENABLED for SUNDAY - 01:00

SP-A SP-B
System Memory Size: 24 MB 24 MB
Combined (L1+L2) write cache size: 0 MB 0 MB
Write cache size: 0 MB 0 MB
Read cache size: 0 MB 0 MB
L2 cache map size: 0 MB 0 MB
L2 cache non_map size: 0 MB 0 MB
Requested RAID-3 memory size: 0 MB 0 MB
Allocated RAID-3 memory size: 0 MB 0 MB
Available Memory: 488 MB 488 MB

05/16/2005 10:54:29
fcli> cl

05/16/2005 10:54:55
fcli>


fcli> getlog
Event Date CRU Event (Message) Extended Status
1. 05/16/05 10:59:32 SP A 0x713 SP Ulog has been cleared. 0x00
2. 05/16/05 11:00:06 ???? 0x67E (Unknown) 0x55
3. 05/16/05 11:00:29 SP A 0x730 (Network Initialized) 0x00
4. 05/16/05 11:00:29 SP A 0x731 (Network Configured) 0x00
5. 05/16/05 11:00:29 SP A 0x732 (Network Started) 0x00
6. 05/16/05 11:00:29 0_9 0x608 (CRU Ready) 0x09
7. 05/16/05 11:00:29 0_5 0x608 (CRU Ready) 0x05
8. 05/16/05 11:00:29 0_2 0x608 (CRU Ready) 0x02
9. 05/16/05 11:00:29 0_1 0x608 (CRU Ready) 0x01
10. 05/16/05 11:00:29 0_8 0x608 (CRU Ready) 0x08
11. 05/16/05 11:00:29 0_4 0x608 (CRU Ready) 0x04
12. 05/16/05 11:00:29 0_9 0x608 (CRU Ready) 0x00
13. 05/16/05 11:00:29 0_3 0x608 (CRU Ready) 0x03
14. 05/16/05 11:00:29 0_7 0x608 (CRU Ready) 0x07
15. 05/16/05 11:00:29 0_6 0x608 (CRU Ready) 0x06
16. 05/16/05 11:00:29 0_0 0x608 (CRU Ready) 0x00
17. 05/16/05 11:00:29 0_5 0x608 (CRU Ready) 0x00
18. 05/16/05 11:00:29 0_2 0x608 (CRU Ready) 0x00
19. 05/16/05 11:00:29 0_1 0x608 (CRU Ready) 0x00

Press any key to continue...(or 'q' to Quit)
Event Date CRU Event (Message) Extended Status
20. 05/16/05 11:00:29 0_8 0x608 (CRU Ready) 0x00
21. 05/16/05 11:00:29 0_4 0x608 (CRU Ready) 0x00
22. 05/16/05 11:00:29 0_3 0x608 (CRU Ready) 0x00
23. 05/16/05 11:00:29 0_7 0x608 (CRU Ready) 0x00
24. 05/16/05 11:00:29 0_6 0x608 (CRU Ready) 0x00
25. 05/16/05 11:00:29 0_0 0x608 (CRU Ready) 0x00
26. 05/16/05 11:00:30 SP A 0x6D1 (Local Loop Access for I/O) 0x00
27. 05/16/05 11:00:30 SP A 0x611 (SP Powerup; PROM Rev 0x00020a00) 0x451792C8

28. 05/16/05 11:00:30 SP A 0x601 (SP Powerup; Flare Rev 0x00062010) 0x451792C
8
Last line is on display.

05/16/2005 11:01:26
fcli>




 
I don't think it's required to set your memory settings, but you may as well try.

use the cache FCLI command to set the read cache to 74MB (I do recall that errors would prevent me from setting it too low, so if we're lucky, maybe there is just a minimum read cache to set before it becomes useful). Give the rest of your cache to the write cache. You already have 24MB assigned to System, so don't touch that.

something like:

c -rca 74 -rcb 74 <enter>
c -are 1 -bre 1 <enter>
c -u 414 <enter>
c enable <enter>

If you don't have an SPS (or an SPS emulator), you will never be able to enable write caching and frankly your performance will stink so bad that you won't like using the array.


--
Bill Plein
a.k.a. squiddog
Contact me at
 
I should have added:

If you can't activate write cache due to a missing SPS, then you may as well use 480MB for read cache, but your write performance will still stink.

--
Bill Plein
a.k.a. squiddog
Contact me at
 
hello was on holiday now it is going on but it is still not working here the result
fcli> c
SP A LOOP ID 0x0 (0.)
Write Cache type and state: MIRRORED DISABLED
Local, Peer read cache state: ENABLED ENABLED
Peer read cache state: ENABLED
Cache page size: 8 KB
High, Low watermark levels: 70 % 60 %
SPS testing is: ENABLED for SUNDAY - 01:00

SP-A SP-B
System Memory Size: 24 MB 24 MB
Combined (L1+L2) write cache size: 414 MB 414 MB
Write cache size: 414 MB 414 MB
Read cache size: 74 MB 74 MB
L2 cache map size: 0 MB 0 MB
L2 cache non_map size: 0 MB 0 MB
Requested RAID-3 memory size: 0 MB 0 MB
Allocated RAID-3 memory size: 0 MB 0 MB
Available Memory: 0 MB 0 MB

05/30/2005 17:33:44
fcli>

and
b r0 0_0 0_1 0_2 0_3 0_4

05/30/2005 17:34:30
fcli> RB error full 0x50040101
part category 0x5 code 0x5004 error num 0x4 status 0x1 type 0x1
Bind ERROR: Bind Array: Category 0x5 Num 0x4 Type 0x1

Sunburst Code: HOST_BIND_BAD_FRU_CONFIGURATION
Status recv'd opcode 0x81 status 0x50040101
HI_BIND


05/30/2005 17:34:32
fcli>
 
Cache setups can be handled later. It won't stop you from binding the Raid. In looking at your earlier command line to bind the raid group, I see that there is no lun assigned. Perhaps that is causing the issue. I'll hook up to a 4500 later today and try it out.
your earlier command: bind r0 0_1 0_2 0_3 0_4
(note that r0 indicates a raid 0 unprotected volume)
what might work: bind r0 0 0_1 0_2 0_3 0_4
As I said, I'll test it later today and let you know.
 
OK ... tried both.
the command you used took the lun number I unbound and rebound the units to it. No errors. lustat showed lun binding.
the command I thought might work..won't. You could try using the -u switch to assign a lun number and see if that works for you. That also worked when I changed the unit number to 11.
Also, check the raid groups with the sg command and delete any that you don't need.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top