Nike Stuff ===================================================================== richard:/users2/mufasa/stuart/doc/nike_stuff SDA 12/10/98 A. GENERAL 1. Here's how you pick out the Nike disks on the system (webby): ioscan -fkCdisk | grep C2300 disk 0 0/28.3.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 1 0/28.3.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 13 2/28.2.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 14 2/28.2.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 15 2/36.3.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 16 2/36.3.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 17 2/44.2.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 18 2/44.2.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 19 2/52.3.0 disc3 CLAIMED DEVICE DGC C2300WDR0 <=19 disk 20 2/52.3.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 41 4/20.2.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 42 4/20.2.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 21 4/28.2.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 22 4/28.2.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 23 4/44.2.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 24 4/44.2.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 25 4/52.3.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 26 4/52.3.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 27 6/44.2.0 disc3 CLAIMED DEVICE DGC C2300WDR0 <=27 disk 28 6/44.2.1 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 29 6/52.3.0 disc3 CLAIMED DEVICE DGC C2300WDR0 disk 30 6/52.3.1 disc3 CLAIMED DEVICE DGC C2300WDR0 2. DIAGRAM: a. They are usually hooked up like this: -------- --------- -------- | |0 | #604 | 0| | 0/36 ----- | SP A | ----- | Lun 0 | ----- | SP B |----- 0/28 | 0/36.3 | | 20 GB | | 0/28.3 | | | |---------| | | | |1 | Lun 1 | 1| | | | ----- | 16 GB | ----- | | | | | | | | -------- --------- -------- b. And, usually, the primaries and alternates will be "alternated": Primary Alternate 0/36.3.0 0/28.3.0 0/28.3.1 0/36.3.1 MAKE SURE THAT THE PRIMARY AND ALTERNATE LVM PATHS MATCH THE SP-DISK BINDING THAT YOU SET UP WITH GRID MANAGER, OR YOU WILL BE "AUTO-TRESPASSING", WHICH IS BAD FOR PERFORMANCE! c. Addressing on a T500: FW Card____ ________Target | | 0/36.3.0 | |______LUN Bus_____| 3. The installation process should add the following definitions for the mux lines connected directly to the SP units to the following files. But, beware, sometimes the customers move them around!: a. /etc/uucp/Devices: ################ NIKE Grid manager Ports ## # # Entry for Webby Nike #1 ### SP A id = 3 h/w path 2/52.3 tty4p10 #### <=Disk 19 above Direct1a tty4p10 - 9600 direct ### SP B id = 2 h/w path 6/44.2 tty4p11 #### <=Disk 27 above Direct1b tty4p11 - 9600 direct # Entry for Webby Nike #2 ### SP A id = 3 h/w path 0/28.3 tty4p12 #### Direct2a tty4p12 - 9600 direct ### SP B id = 2 h/w path 4/28.2 tty4p13 #### Direct2b tty4p13 - 9600 direct # Entry for Webby Nike #3 ### SP A id = 3 h/w path 2/36.3 tty4p8 #### Direct3a tty4p8 - 9600 direct ### SP B id =2 h/w path 4/44.2 tty4p9 #### Direct3b tty4p9 - 9600 direct # Entry for Webby Nike #4 ### SP A id = 3 h/w path 4/52.3 tty4p14 #### Direct4a tty4p14 - 9600 direct ### SP B id = 2 h/w path 2/28.2 tty4p15 #### Direct4b tty4p15 - 9600 direct # Entry for Webby Nike #5 ### SP A id = 3 h/w path 6/52.3 tty4p4 #### Direct5a tty4p4 - 9600 direct ### SP B id = 2 h/w path 2/44.2 tty4p5 #### Direct5b tty4p5 - 9600 direct b. /etc/uucp/Systems nwuxd Any ACU 1200 chicago2600776 in:--in: nuucp word: panzer nike1a Any Direct1a 9600 nike1b Any Direct1b 9600 nike2a Any Direct2a 9600 nike2b Any Direct2b 9600 nike3a Any Direct3a 9600 nike3b Any Direct3b 9600 nike4a Any Direct4a 9600 nike4b Any Direct4b 9600 nike5a Any Direct5a 9600 nike5b Any Direct5b 9600 c. tty device files: o tty devices have the following format: crw--w---- 2 sybase sybase 17 0x000018 May 27 23:27 ttyq8 crw-rw-rw- 2 root root 17 0x000017 May 27 16:36 ttyq7 crw-rw-rw- 2 root root 17 0x000019 May 27 15:42 ttyq9 crw-rw-rw- 2 root root 17 0x00001a May 23 10:42 ttyqa crw--w--w- 1 bin bin 193 0x040a00 May 7 16:25 tty4p10 crw--w--w- 1 bin bin 193 0x040800 May 7 16:24 tty4p8 crw------- 1 root sys 193 0x040500 May 7 16:23 tty4p5 crw--w--w- 1 bin bin 193 0x040400 May 7 16:23 tty4p4 o The ones we are interested in have major number 193: boot@webby:/dev# lsdev 193 Character Block Driver Class 193 -1 mux2 tty B. GRID MGR Grid Manager configures the Nike, and can be used to check status. There are three ways to use Grid Manager: o From the previously described RS 232 Cable to the Server o From a 700/96 terminal o From your PC 1. You can "call" into the SP on the RS232 "line" from the server: xterm & (switch to xterm window) cu -l tty0p3 connected Ctrl-L 2. You can connect up a 700/96 terminal: a. Disconnect the console cable from port 2 on the 700/96. b. Connect HP cable H24542 from the console port 3 to the Nike SP (A or B). Cable: 9 pin Female to 25 pin Female serial cable. (There also is a long cable, 5061-5003, 25 pin female to 25 pin male, that you can use.) c. Change 700/96 from HP to EM1 mode: Menu Setup Config Terminal Config Tab to Term Mode: HP Next Choice: EM1 Save Config d. (When you are done with Console, don't forget to reconfigure back to HP mode. You can do that by: turning off hold down "D" key turn on release "D" 3. You can use your PC: Bring up HyperTerminal Configure: vt100 9600-N-1 Xon/Xoff Connect H24542 to 9 pin male serial port, Comm 1, and to Nike SP (A/B). 4. Grid Manager and you get: SP B SP SCSI ID 1 GridMgr Main Menu 1. Presentation Utility 2. Bind Physical Units 3. Unbind Physical Units 4. View Unsolicited Event Log 5. Change Parameters 6. View Cache Statistics Enter ? or ? for HELP Enter Choice: ~. <== to exit ^ <== to go up one menu level b. Presentation Manager: SP A Presentation Utility (*) SP SCSI ID 5 07/10/1997 16:00 PROM Revision 1.57 +---+---+---+---+---+ +---+---+---+---+---+ FAN A OK | | | | | | | | | | | | Microcode Revision FAN B OK 0 |ENA|ENA|ENA|ENA|ENA| 2 |ENA|ENA|ENA|ENA|ENA| 08.60 | 0| 0| 0| 0| 0| | 0| 0| 0| 0| 0| VSC A OK | | | | | | | | | | | | Statistics Logging VSC B OK +---+---+---+---+---+ +---+---+---+---+---+ DISABLED VSC C OK A B C D E A B C D E +---+---+---+---+---+ +---+---+---+---+---+ Peer SP BBU OK | | | | | | | | | | | | PRESENT 1 |RDY|RDY|RDY|RDY|RDY| 3 |RDY|RDY|RDY|RDY|RDY| ADP 0% | 1| 1| 1| 1| 1| | 1| 1| 1| 1| 1| Requests Completed BDP 0% | | | | | | | | | | | | 835 UDP 0% +---+---+---+---+---+ +---+---+---+---+---+ Cache States Write: ENABLED Enter ? for HELP, ^ to GO TO MAIN MENU Read: ENABLED Enter Choice: blank - The disk module is removed. OFF - Power is off. POW - Powering up. FMT - Formatting. REB - Rebuilding. UNB - Unbound. BIN - Binding ENA - Bound and physical unit owned by this SP. RDY - Bound but physical unit owned by the other SP. The hexadecimal number is the physical unit number that the disk module is bound to. A '**' in this field indicates that the disk module is not currently bound. b. Cursor to a disk unit, and hit to get statistics: Performance Statistics for Disk Module E0 Description: 4.2 GB SCSI Disk State: ENABLED Unit Number (hex): 0 Unit Type: RAID-1/0 Group (Mirrored RAID-0 Group) Stripe Element Size: 128 Sectors Maximum Rebuild Time: 4 Hours This Disk Module is a Primary Mirror Part. Other Image Bind Slot: A2 Statistics logging is disabled. C. BIND A NIKE 1. Presentation Manager Bind Physical Units Select Raid Level tab to select unit return tab to select 2nd unit return Return "Do you want to Bind Y/N?": Y D. Now let's take a look at Nike #1: a. The /etc/uucp/Devices says: # Entry for Webby Nike #1 ### SP A id = 3 h/w path 2/52.3 tty4p10 #### Direct1a tty4p10 - 9600 direct ### SP B id = 2 h/w path 6/44.2 tty4p11 #### Direct1b tty4p11 - 9600 direct b. lssf shows the device file for this path: lssf /dev/dsk/c* | grep "2/52" disc3 card instance 10 SCSI target 3 SCSI LUN 0 section 0 at address 2/52.3.0 /dev/dsk/c10t3d0 disc3 card instance 10 SCSI target 3 SCSI LUN 1 section 0 at address 2/52.3.1 /dev/dsk/c10t3d1 c. And for the other SP: lssf /dev/dsk/c* | grep "6/44" disc3 card instance 19 SCSI target 2 SCSI LUN 0 section 0 at address 6/44.2.0 /dev/dsk/c19t2d0 disc3 card instance 19 SCSI target 2 SCSI LUN 1 section 0 at address 6/44.2.1 /dev/dsk/c19t2d1 d. pvdisplay /dev/dsk/c10t3d0 : --- Physical volumes --- PV Name /dev/dsk/c10t3d0 PV Name /dev/dsk/c19t2d0 Alternate Link VG Name /dev/vg01 PV Status available Allocatable yes VGDA 2 Cur LV 20 PE Size (Mbytes) 4 Total PE 10015 Free PE 15 Allocated PE 10000 Stale PE 0 IO Timeout (Seconds) default E. XSTM a. You can get the following information from xstm at HP-UX 10.20 (10.10 is less useful): xstm highlight disk Tools Information Run Information log b. And this is what you get: -- Information Tool Log for C2300 Array on path 0/28.3 -- Log creation time: Mon May 19 16:50:45 1997 Hardware path: 0/28.3 MAP: ==== This SP: B (7305) Array Date: 05/19/97 Peer SP: A (ID: 3) Array Time: 15:47:06 SysSer#: 95-0241-604 Cabnt Type: Rack Mnt 0 --- ----- ----- ----- ----- 2 --- ----- ----- ----- ----- | | | | | | | | | | | | | Rdy | Rdy | Rdy | Rdy | Rdy | | Ena | Ena | Ena | Ena | Rdy | | R10 | R10 | R10 | R10 | R10 | | R10 | R10 | R10 | R10 | Hot | | A 0 | A 0 | A 0 | A 0 | A 0 | | B 1 | B 1 | B 1 | B 1 | B 2 | | | | | | | | | | | | | ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- A B C D E A B C D E 1 --- ----- ----- ----- ----- 3 --- ----- ----- ----- ----- | | | | | | | | | | | | | Rdy | Rdy | Rdy | Rdy | Rdy | | Ena | Ena | Ena | Ena | Rdy | | R10 | R10 | R10 | R10 | R10 | | R10 | R10 | R10 | R10 | Hot | | A 0 | A 0 | A 0 | A 0 | A 0 | | B 1 | B 1 | B 1 | B 1 | B 3 | | | | | | | | | | | | | ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- Cache: 64mb Systm: 4mb Firmware Rev: HP02 Read: 20mb Enabled Microcode Rev: 8.61.00 Write: 40mb Enabled Prom Rev Levl: 1.63.00 Auto Trespass: On CONFIGURATION: ============== Lun Own Fru/BS Cch ATr Type/Vendor Product ID Cap BSz Rev --- --- ------ --- --- ----------- ---------- ------ --- ---- 0 A/A * -/- On RAID-1/0 C2300WDR10 21.0gb 512 A0 /A0 SEAGATE ST15150N 4.2gb 512 HP03 C0 /C0 SEAGATE ST15150N 4.2gb 512 HP03 E0 /E0 SEAGATE ST15150N 4.2gb 512 HP03 B1 /B1 SEAGATE ST15150N 4.2gb 512 HP03 D1 /D1 SEAGATE ST15150N 4.2gb 512 HP03 B0 /B0 SEAGATE ST15150N 4.2gb 512 HP03 D0 /D0 SEAGATE ST15150N 4.2gb 512 HP03 A1 /A1 SEAGATE ST15150N 4.2gb 512 HP03 C1 /C1 SEAGATE ST15150N 4.2gb 512 HP03 E1 /E1 SEAGATE ST15150N 4.2gb 512 HP03 1 B/B * -/- On RAID-1/0 C2300WDR10 16.8gb 512 A2 /A2 SEAGATE ST15150N 4.2gb 512 HP03 C2 /C2 SEAGATE ST15150N 4.2gb 512 HP03 A3 /A3 SEAGATE ST15150N 4.2gb 512 HP03 C3 /C3 SEAGATE ST15150N 4.2gb 512 HP03 B2 /B2 SEAGATE ST15150N 4.2gb 512 HP03 D2 /D2 SEAGATE ST15150N 4.2gb 512 HP03 B3 /B3 SEAGATE ST15150N 4.2gb 512 HP03 D3 /D3 SEAGATE ST15150N 4.2gb 512 HP03 2 B/- * -/- - Hot Spare C2300WD 4.2gb 512 E2 /E2 SEAGATE ST15150N 4.2gb 512 HP03 3 B/- * -/- - Hot Spare C2300WD 4.2gb 512 E3 /E3 SEAGATE ST15150N 4.2gb 512 HP03 c. And this is how you read it. This is important stuff: - HW Path/SP: o The Hardware Path is listed right at the top of the listing: Hardware Path: 0/28.3 o "This SP: B" tells you that SP "B" is located at this HW path. o So, SP B is located at 0/28.3 - Binding: o Take a look at the grid: 0 --- ----- ----- ----- ----- 2 --- ----- ----- ----- ----- | | | | | | | | | | | | | Rdy | Rdy | Rdy | Rdy | Rdy | | Ena | Ena | Ena | Ena | Rdy | | R10 | R10 | R10 | R10 | R10 | | R10 | R10 | R10 | R10 | Hot | | A 0 | A 0 | A 0 | A 0 | A 0 | | B 1 | B 1 | B 1 | B 1 | B 2 | | | | | | | | | | | | | ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- A B C D E A B C D E 1 --- ----- ----- ----- ----- 3 --- ----- ----- ----- ----- | | | | | | | | | | | | | Rdy | Rdy | Rdy | Rdy | Rdy | | Ena | Ena | Ena | Ena | Rdy | | R10 | R10 | R10 | R10 | R10 | | R10 | R10 | R10 | R10 | Hot | | A 0 | A 0 | A 0 | A 0 | A 0 | | B 1 | B 1 | B 1 | B 1 | B 3 | | | | | | | | | | | | | ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- o Codes: Ena: This mech is primary in LVM to "This" SP (B) on 0/28.3. Rdy: This mech is alternate to SP B on path 0/28.3 R10: This mech is bound Raid 1/0. Hot: This mech is a hot spare A 0: This mech is bound to SP A, and is part of LUN 0. o NOTE: When you configure Nikes, they have a primary and an alternate, and the LVM definitions had better match the SP bindings, or you will "autotrespass", which slows you down. F. INSTALL THE MUX LINES a. Connect up the tty lines from the SPs to the 16 port mux and from the mux to the cpu card. . Do an ioscan and get the device file names for the muxes: ioscan -fnkCtty You should see the console on tty0, and a 16 port mux on tty1. . The 16 port mux cable is a Y cable, with two ends: end port mdp0 0 - 7 mdp1 8 - 15 Plug them into the muxes. . Plug the SP cables: Cable # 17355D - don't use any other cable. Into ports: mdp0 2 - 6 (0, 1 and 7 are reserved for other devices, UPS, etc..) mdp1 8 - 15 For example, use mdp1, port 8 and 9 (tty1p8 and tty1p9). b. Use SAM to set up tty device files (They may already be defined.) SAM Periperals Terminals Add terminal highlight the 16 port mux Port: 8 or 9 (match above) Speed: 9600 OK Device File Name Type Hardware Path Port Number Speed (baud) /dev/console Console 10/4/0 0 0 /dev/tty1p8 Terminal 10/4/8 8 9600 /dev/tty1p9 Terminal 10/4/8 9 9600 creates device file c. Set up /etc/uucp/Devices Add: ## Evinrude Nike serial lines. SDA 10/02/97 # # Mux port 8 connects to SP A # Mux port 9 connects to SP B directA tty1p8 - 9600 direct directB tty1p9 - 9600 direct d. Comment out the /etc/inittab "respawn" messages, which SAM added: vi /etc/inittab vue :4:respawn:/usr/vue/bin/vuerc # VUE invocation #ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600 #ttp2:234:respawn:/usr/sbin/getty -h tty0p2 9600 #ttp3:234:respawn:/usr/sbin/getty -h tty0p3 9600 #ttp4:234:respawn:/usr/sbin/getty -h tty0p4 9600 #ttp5:234:respawn:/usr/sbin/getty -h tty0p5 9600 #ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf ShPr::respawn:/opt/sharedprint/bin/spserver ==> #a0:4:respawn:/usr/sbin/getty -h tty1p0 9600 ==> #a1:4:respawn:/usr/sbin/getty -h tty1p1 9600 G. TURN ON AUTO-TRESPASS: Go to Grid Manager main menu Put keyboard in CAPS-LOCK Type a P Tape the Shift Key - Don't hold it down. Type FE FE will appear in the top right corner of the screen A new menu selection will appear at the bottom of the screen Go to Step 5 - Change Parameters Go to Step 2 - Change Storage System Parameters Go to Step 1 - Change Storage System Cache Parameters Disable caching if enabled Go to Step 5 - Select Storage System Option Pakcage Enter 2 for system type. (Or "A" for autotrespass off.) Array will reboot Reboot computer. New devices will show up in insf stage of reboot