Friday, 21 January 2011
Brocade FC SAN Switch CLI Commands
IBM_2005_B64:admin> switchshow
switchName: IBM_2005_B64
switchType: 44.2
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:07:a8:b2
zoning: ON (Switch2)
switchBeacon: OFF
Area Port Media Speed State Proto
=====================================
0 0 id N4 No_Light
1 1 id N4 Online F-Port 20:15:00:a0:b8:47:1a:dc
2 2 id N4 Online F-Port 10:00:00:00:c9:6b:11:d2
3 3 id N4 No_Light
4 4 id N4 No_Light
5 5 id N4 No_Light
6 6 id N4 No_Light
7 7 id N4 Online F-Port 10:00:00:00:c9:6e:54:63
8 8 id N4 No_Light
9 9 id N4 No_Light
10 10 id N4 No_Light
11 11 id N4 Online E-Port 10:00:00:05:1e:08:ed:d2 "brocade4Gb" (upstream)
12 12 id N4 Online F-Port 10:00:00:00:c9:6e:81:f6
13 13 id N4 No_Light
14 14 id N4 No_Light
15 15 id N4 Online E-Port 10:00:00:05:1e:08:ed:ea "brocade4Gb" (downstream)
16 16 id N4 Online F-Port 10:00:00:00:c9:70:35:fa
17 17 id N2 No_Light
18 18 id N2 No_Light
19 19 id N4 No_Light
20 20 id N4 No_Light
21 21 id N4 No_Light
22 22 id N4 No_Light
23 23 id N4 No_Light
24 24 id N4 No_Light
25 25 id N4 No_Light
26 26 id N4 No_Light
27 27 id N4 No_Light
28 28 id N4 No_Light
29 29 id N4 No_Light
30 30 id N4 No_Light
31 31 id N4 Online F-Port 10:00:00:00:c9:6e:41:44
32 32 -- N4 No_Module (No POD License) Disabled
33 33 -- N4 No_Module (No POD License) Disabled
34 34 -- N4 No_Module (No POD License) Disabled
35 35 -- N4 No_Module (No POD License) Disabled
36 36 -- N4 No_Module (No POD License) Disabled
37 37 -- N4 No_Module (No POD License) Disabled
38 38 -- N4 No_Module (No POD License) Disabled
39 39 -- N4 No_Module (No POD License) Disabled
40 40 -- N4 No_Module (No POD License) Disabled
41 41 -- N4 No_Module (No POD License) Disabled
42 42 -- N4 No_Module (No POD License) Disabled
43 43 -- N4 No_Module (No POD License) Disabled
44 44 -- N4 No_Module (No POD License) Disabled
45 45 -- N4 No_Module (No POD License) Disabled
46 46 -- N4 No_Module (No POD License) Disabled
47 47 -- N4 No_Module (No POD License) Disabled
48 48 -- N4 No_Module (No POD License) Disabled
49 49 -- N4 No_Module (No POD License) Disabled
50 50 -- N4 No_Module (No POD License) Disabled
51 51 -- N4 No_Module (No POD License) Disabled
52 52 -- N4 No_Module (No POD License) Disabled
53 53 -- N4 No_Module (No POD License) Disabled
54 54 -- N4 No_Module (No POD License) Disabled
55 55 -- N4 No_Module (No POD License) Disabled
56 56 -- N4 No_Module (No POD License) Disabled
57 57 -- N4 No_Module (No POD License) Disabled
58 58 -- N4 No_Module (No POD License) Disabled
59 59 -- N4 No_Module (No POD License) Disabled
60 60 -- N4 No_Module (No POD License) Disabled
61 61 -- N4 No_Module (No POD License) Disabled
62 62 -- N4 No_Module (No POD License) Disabled
63 63 -- N4 No_Module (No POD License) Disabled
IBM_2005_B64:admin>
IBM_2005_B64:admin> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
2: fffc02 10:00:00:05:1e:07:a8:b2 192.168.3.21 0.0.0.0 "IBM_2005_B64"
4: fffc04 10:00:00:05:1e:08:ed:d2 192.168.70.140 0.0.0.0 >"brocade4Gb" (BLADE CENTRE C2 SEC SAN SW)
5: fffc05 10:00:00:05:1e:08:ed:ea 192.168.70.130 0.0.0.0 "brocade4Gb" (BLADE CENTRE C1 SEC SAN SW)
The Fabric has 3 switches
Set Time Zone, Date and Time
IBM_2005_B64:admin> date
Fri Nov 13 20:32:53 Localtime 2009
IBM_2005_B5K:admin> date 1113193409 (MmDayHrMinYy)
Fri Nov 13 19:34:00 Localtime 2009
IBM_2005_B5K:admin> date
Fri Nov 13 19:34:04 Localtime 2009
IBM_2005_B64:admin> tsTimeZone
Time Zone Hour Offset: 0
Time Zone Minute Offset: 0
IBM_2005_B64:admin> tsTimeZone +5, +00
System Time Zone change will take effect at next reboot
IBM_2005_B64:admin> tsTimeZone
Time Zone Hour Offset: 5
Time Zone Minute Offset: 0
_____________________________
IBM_2005_B64:admin> cfgshow
Defined configuration:
cfg: Switch2
C1_B1_B; C1_B2_B; C1_B3_B; C1_B4_B; C1_B5_B; C1_B6_B; C1_B7_B;
C1_B8_B; C2_B1_B; C2_B2_B; C2_B3_B; C2_B4_B; C2_B5_B; C2_B6_B;
C2_B7_B; C2_B8_B; HA_T24_Node1_B; HA_T24_Node2_B; RAC1_B;
RAC2_B; TSM_B; UAT
zone: C1_B1_B 2,1; 5,1
zone: C1_B2_B 2,1; 5,2
zone: C1_B3_B 2,1; 5,3
zone: C1_B4_B 2,1; 5,4
zone: C1_B5_B 2,1; 5,5
zone: C1_B6_B 2,1; 5,6
zone: C1_B7_B 2,1; 5,7
zone: C1_B8_B 2,1; 5,8
zone: C2_B1_B 2,1; 4,1
zone: C2_B2_B 2,1; 4,2
zone: C2_B3_B 2,1; 4,3
zone: C2_B4_B 2,1; 4,4
zone: C2_B5_B 2,1; 4,5
zone: C2_B6_B 2,1; 4,6
zone: C2_B7_B 2,1; 4,7
zone: C2_B8_B 2,1; 4,8
zone: HA_T24_Node1_B
2,1; 2,7
zone: HA_T24_Node2_B
2,1; 2,12
zone: RAC1_B 2,1; 2,2
zone: RAC2_B 2,1; 2,16
zone: TSM_B 2,1; 2,14
zone: UAT 2,1; 2,31
Effective configuration:
cfg: Switch2
zone: C1_B1_B 2,1
5,1
zone: C1_B2_B 2,1
5,2
zone: C1_B3_B 2,1
5,3
zone: C1_B4_B 2,1
5,4
zone: C1_B5_B 2,1
5,5
zone: C1_B6_B 2,1
5,6
zone: C1_B7_B 2,1
5,7
zone: C1_B8_B 2,1
5,8
zone: C2_B1_B 2,1
4,1
zone: C2_B2_B 2,1
4,2
zone: C2_B3_B 2,1
4,3
zone: C2_B4_B 2,1
4,4
zone: C2_B5_B 2,1
4,5
zone: C2_B6_B 2,1
4,6
zone: C2_B7_B 2,1
4,7
zone: C2_B8_B 2,1
4,8
zone: HA_T24_Node1_B
2,1
2,7
zone: HA_T24_Node2_B
2,1
2,12
zone: RAC1_B 2,1
2,2
zone: RAC2_B 2,1
2,16
zone: TSM_B 2,1
2,14
zone: UAT 2,1
2,31
IBM_2005_B64:admin>
SWITCH IP: 192.168.3.20
IBM_2005_B5K:admin> switchshow
switchName: IBM_2005_B5K
switchType: 58.2
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:90:54:fe
zoning: ON (Switch1)
switchBeacon: OFF
Area Port Media Speed State Proto
=====================================
0 0 id N4 Online F-Port 10:00:00:00:c9:6d:ce:b9
1 1 id N4 Online F-Port 20:14:00:a0:b8:47:1a:dc
2 2 id N4 Online F-Port 20:08:00:0e:11:11:75:94
3 3 id N4 Online F-Port 10:00:00:00:c9:6e:81:c7
4 4 id N4 Online F-Port 10:00:00:00:c9:6e:a0:84
5 5 id N4 Online F-Port 20:02:00:0e:11:11:75:94
6 6 id N4 No_Light
7 7 id N4 Online F-Port 10:00:00:00:c9:6e:41:4e
8 8 id N4 Online F-Port 10:00:00:00:c9:70:38:22
9 9 id N4 Online F-Port 10:00:00:00:c9:6c:65:0b
10 10 id N4 Online F-Port 10:00:00:00:c9:6e:82:8e
11 11 id N4 Online F-Port 10:00:00:00:c9:6e:ce:a6
12 12 id N4 Online F-Port 10:00:00:00:c9:6e:75:98
13 13 id N4 Online F-Port 10:00:00:00:c9:67:b3:9c
14 14 id N4 Online F-Port 10:00:00:00:c9:67:b2:57
15 15 id N4 Online F-Port 10:00:00:00:c9:6e:d1:db
16 16 id N4 Online E-Port 10:00:00:05:1e:08:dc:5b "brocade4Gb" (upstream)
17 17 id N4 Online E-Port 10:00:00:05:1e:08:f1:fe "brocade4Gb" (downstream)
18 18 id N4 No_Light
19 19 id N4 No_Light
20 20 id N4 No_Light
21 21 id N4 No_Light
22 22 id N4 No_Light
23 23 id N4 No_Light
24 24 id N4 No_Light
25 25 id N4 No_Light
26 26 id N4 No_Light
27 27 id N4 No_Light
28 28 id N4 No_Light
29 29 id N4 No_Light
30 30 id N4 No_Light
31 31 id N4 Online F-Port 21:00:00:1b:32:83:01:60
IBM_2005_B5K:admin>
IBM_2005_B5K:admin> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
1: fffc01 10:00:00:05:1e:08:dc:5b 192.168.70.129 0.0.0.0 >"brocade4Gb" (BLADE CENTRE C1 PRI SAN SW)
2: fffc02 10:00:00:05:1e:90:54:fe 192.168.3.20 0.0.0.0 "IBM_2005_B5K"
3: fffc03 10:00:00:05:1e:08:f1:fe 192.168.70.139 0.0.0.0 "brocade4Gb" (BLADE CENTRE C2 PRI SAN SW)
The Fabric has 3 switches
IBM_2005_B5K:admin> cfgshow
Defined configuration:
cfg: Switch1
C1_B2_A; C1_B3_A; C1_B4_A; C1_B5_A; C1_B6_A; C1_B7_A; C1_B8_A;
C2_B1_A; C2_B2_A; C2_B3_A; C2_B4_A; C2_B5_A; C2_B6_A; C2_B7_A;
C2_B8_A; EBSD_Tape; HA_T24_Node1_A; HA_T24_Node2_A;
MQ_Prod1_Tape; MQ_Prod2_Tape; Ora_Prod1_Tape; Ora_Prod2_Tape;
RAC1_A; RAC2_A; T24_Prod1_Tape; T24_Prod2_Tape; TSM_A;
TSM_Zone; WAS_Prod1_Tape; WAS_Prod2_Tape
zone: C1_B2_A 1,2; 2,1
zone: C1_B3_A 1,3; 2,1
zone: C1_B4_A 1,4; 2,1
zone: C1_B5_A 1,5; 2,1
zone: C1_B6_A 1,6; 2,1
zone: C1_B7_A 1,7; 2,1
zone: C1_B8_A 1,8; 2,1
zone: C2_B1_A 2,1; 3,1
zone: C2_B2_A 2,1; 3,2
zone: C2_B3_A 2,1; 3,3
zone: C2_B4_A 2,1; 3,4
zone: C2_B5_A 2,1; 3,5
zone: C2_B6_A 2,1; 3,6
zone: C2_B7_A 2,1; 3,7
zone: C2_B8_A 2,1; 3,8
zone: EBSD_Tape
2,2; 2,5; 3,3
zone: HA_T24_Node1_A
2,1; 2,7
zone: HA_T24_Node2_A
2,1; 2,12
zone: MQ_Prod1_Tape
2,2; 2,5; 2,9
zone: MQ_Prod2_Tape
2,2; 2,3; 2,5
zone: Ora_Prod1_Tape
2,2; 2,5; 2,14
zone: Ora_Prod2_Tape
2,2; 2,5; 2,15
zone: RAC1_A 2,1; 2,4
zone: RAC2_A 2,1; 2,10
zone: T24_Prod1_Tape
2,2; 2,5; 2,8
zone: T24_Prod2_Tape
2,2; 2,5; 2,13
zone: TSM_A 2,1; 2,18
zone: TSM_Zone
2,2; 2,5; 2,6
zone: WAS_Prod1_Tape
2,0; 2,2; 2,5
zone: WAS_Prod2_Tape
2,2; 2,5; 2,11
Effective configuration:
cfg: Switch1
zone: C1_B2_A 1,2
2,1
zone: C1_B3_A 1,3
2,1
zone: C1_B4_A 1,4
2,1
zone: C1_B5_A 1,5
2,1
zone: C1_B6_A 1,6
2,1
zone: C1_B7_A 1,7
2,1
zone: C1_B8_A 1,8
2,1
zone: C2_B1_A 2,1
3,1
zone: C2_B2_A 2,1
3,2
zone: C2_B3_A 2,1
3,3
zone: C2_B4_A 2,1
3,4
zone: C2_B5_A 2,1
3,5
zone: C2_B6_A 2,1
3,6
zone: C2_B7_A 2,1
3,7
zone: C2_B8_A 2,1
3,8
zone: EBSD_Tape
2,2
2,5
3,3
zone: HA_T24_Node1_A
2,1
2,7
zone: HA_T24_Node2_A
2,1
2,12
zone: MQ_Prod1_Tape
2,2
2,5
2,9
zone: MQ_Prod2_Tape
2,2
2,3
2,5
zone: Ora_Prod1_Tape
2,2
2,5
2,14
zone: Ora_Prod2_Tape
2,2
2,5
2,15
zone: RAC1_A 2,1
2,4
zone: RAC2_A 2,1
2,10
zone: T24_Prod1_Tape
2,2
2,5
2,8
zone: T24_Prod2_Tape
2,2
2,5
2,13
zone: TSM_A 2,1
2,18
zone: TSM_Zone
2,2
2,5
2,6
zone: WAS_Prod1_Tape
2,0
2,2
2,5
zone: WAS_Prod2_Tape
2,2
2,5
2,11
IBM_2005_B5K:admin>
How to Backup Brocade Switch
TELNET OR SSH the SAN SWITCH IP
IBM_2005_B5K login: admin
Password:
IBM_2005_B5K:admin> configupload
Protocol (scp or ftp) [ftp]: ftp
Server Name or IP Address [host]: 192.168.3.25 (pl ensure ftp server must be running)
User Name [user]: admin
File Name [config.txt]: config(ddmmyy_B5K.txt) e.g. "config240210_B5K.txt"
Password: xxxx
configUpload complete: All config parameters are uploaded
IBM_2005_B5K:admin>exit
logout
Connection to host lost.
How to RESTORE:
To restore a configuration, you can use the "configDownload" command.
How to add SAN Disk on AIX
a) devices.pci.df1000f7 for the FC6227 or
b) devices.pci.df1000f9 for the FC6228
c) devices.pci.common.IBM.fc
d) devices.fcp.disk
Run 'cfgmgr -v' to configure the FC adapter.
2. Ensure the HBA is available by running 'lsdev -C | grep fcs'.
# lsdev -C | grep fcs (Note: It should be in "Available" State NOT in "Defined" State.
fcs0 Available 0L-08 FC Adapter
fcs1 Available 0R-08 FC Adapter
3. How to find the WWN of the HBA with 'lscfg -vl fcs0'.
# lscfg -vl fcs0 (or 1,2,3....)
fcs0 U7879.001.DQDZNMG-P1-C1-T1 FC Adapter
Part Number.....................03N5014
EC Level..............................A
Serial Number..................1B74504EDB
Manufacturer...................001B
Customer Card ID Number.....280D
FRU Number..................... 03N5014
Device Specific.(ZM).......3
Network Address.............10000000C96E827E
ROS Level and ID.............02C82138
Device Specific.(Z0)........1036406D
Device Specific.(Z1)........00000000
Device Specific.(Z2)........00000000
Device Specific.(Z3)........03000909
Device Specific.(Z4)........FFC01159
Device Specific.(Z5)........02C82138
Device Specific.(Z6)........06C32138
Device Specific.(Z7)........07C32138
Device Specific.(Z8)........20000000C96E827E
Device Specific.(Z9)........BS2.10X8
Device Specific.(ZA)........B1D2.10X8
Device Specific.(ZB)........B2D2.10X8
Device Specific.(ZC)........00000000
Hardware Location Code......U7879.001.DQDZNMG-P1-C1-T1
Ensure the child fscsi devices have been created with 'lscfg | grep fscsi'
# lscfg | grep fscsi
* fscsi1 U7879.001.DQD450R-P1-C4-T1 FC SCSI I/O Controller Protocol Device
* fscsi0 U7879.001.DQDZNMG-P1-C1-T1 FC SCSI I/O Controller Protocol Device
4. Install the FC SCSI array drivers:
a) devices.fcp.disk.array.rte
b) devices.fcp.disk.array.diag
c) devices.fcp.disk.rte
d) devices.scsi.scarray.rte
The RDAC patch is also required. This is comprised of the following PTFs: U477090, U477166, U479510, U479487.
Check the AIX systems driver support and state by running the following command:
# manage_disk_drivers
1: DS4100: currently RDAC; supported: RDAC/fcparray, MPIO
2: DS4300: currently RDAC; supported: RDAC/fcparray, MPIO
3: DS4500: currently RDAC; supported: RDAC/fcparray, MPIO
4: DS4700/DS4200: currently RDAC; supported: RDAC/fcparray, MPIO
5: DS4800: currently RDAC; supported: RDAC/fcparray, MPIO
#
5. Reboot (or possibly run 'cfgmgr -v') to detect the disk arrays. If everything works, 'lsdev -Ccdisk' should show the SAN disks such as:
#lsdev -Ccdisk
hdisk0 Available 0J-08-00-5,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 0U-08-00-5,0 16 Bit LVD SCSI Disk Drive
hdisk4 Available 0L-08-02 1815 DS4800 Disk Array Device (Note: This is a SAN disk)
hdisk5 Available 0L-08-02 1815 DS4800 Disk Array Device (Note: This is a SAN disk)
If several "other FC SCSI Disk Drive" lines are seen the, array drivers are not correctly installed. Remove each FC SCSI device (with rmdev -d -l ) and check the driver installation.
# rmdev -dl fcs0 -R
Then Run "cfgmgr" and
6. How to verify DAR information:
# fget_config -Av
---dar0---
User array name = 'MEEZAN_DS4800_DR'
dac2 ACTIVE dac3 ACTIVE
Disk DAC LUN Logical Drive
utm 31
hdisk4 dac2 9 T24_HA
hdisk5 dac2 10 HA_HB
7. How to check FC connectivity stats
# fcstat fcs0 (or 1,2,3.....)
FIBRE CHANNEL STATISTICS REPORT: fcs0
Device Type: FC Adapter (df1000fd)
Serial Number: 1B74504EDB
Option ROM Version: 02C82138
Firmware Version: B1D2.10X8
World Wide Node Name: 0x20000000C96E827E
World Wide Port Name: 0x10000000C96E827E
FC-4 TYPES:
Supported: 0x0000012000000000000000000000000000000000000000000000000000000000
Active: 0x0000010000000000000000000000000000000000000000000000000000000000
Class of Service: 3
Port Speed (supported): 4 GBIT
Port Speed (running): 4 GBIT
Port FC ID: 0x010200
Port Type: Fabric
Seconds Since Last Reset: 3983
Transmit Statistics Receive Statistics
------------------- ------------------
Frames: 272968 19860
Words: 139650816 6934784
LIP Count: 0
NOS Count: 0
Error Frames: 0
Dumped Frames: 0
Link Failure Count: 2
Loss of Sync Count: 8
Loss of Signal: 0
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 4
Invalid CRC Count: 0
IP over FC Adapter Driver Information
No DMA Resource Count: 0
No Adapter Elements Count: 0
FC SCSI Adapter Driver Information
No DMA Resource Count: 0
No Adapter Elements Count: 0
No Command Resource Count: 0
IP over FC Traffic Statistics
Input Requests: 0
Output Requests: 0
Control Requests: 0
Input Bytes: 0
Output Bytes: 0
FC SCSI Traffic Statistics
Input Requests: 511
Output Requests: 2629
Control Requests: 42
Input Bytes: 27115897
Output Bytes: 551900700
#
8. Also check the following for better understand
# lsdev -C |grep dar
dar0 Available 1815 DS4800 Disk Array Router
en0 Defined 0E-08 Standard Ethernet Network Interface
en1 Defined 0E-09 Standard Ethernet Network Interface
en2 Defined 0G-08 Standard Ethernet Network Interface
en3 Defined 0P-08 Standard Ethernet Network Interface
en4 Defined 0P-09 Standard Ethernet Network Interface
en5 Defined 0Q-08 Standard Ethernet Network Interface
en6 Defined 0a-08 Standard Ethernet Network Interface
en7 Defined 0a-09 Standard Ethernet Network Interface
en8 Defined 0b-08 Standard Ethernet Network Interface
en9 Defined 0l-08 Standard Ethernet Network Interface
en10 Defined 0l-09 Standard Ethernet Network Interface
en11 Defined 0o-08 Standard Ethernet Network Interface
en12 Available Standard Ethernet Network Interface
# lsdev -C |grep dac
dac0 Available 0L-08-02 DS3/4K PCM User Interface
dac1 Available 0R-08-02 DS3/4K PCM User Interface
dac2 Available 0L-08-02 1815 DS4800 Disk Array Controller
dac3 Available 0R-08-02 1815 DS4800 Disk Array Controller
#lspath -H -l hdisk
# lspath -l hdisk4
fcs0 path Enable
fcs1 path Enable
9. Type the following command to list the attributes of each dar found on the system:
# lsattr -El darX where X is the number of the dar (e.g: dar 0)
# lsattr -El dar0
act_controller dac2,dac3 Active Controllers False
aen_freq 600 Polled AEN frequency in seconds True
all_controller dac2,dac3 Available Controllers False
autorecovery no Autorecover after failure is corrected True
balance_freq 600 Dynamic Load Balancing frequency in seconds True
cache_size 2048 Cache size for both controllers False
fast_write_ok yes Fast Write available False
held_in_reset none Held-in-reset controller True
hlthchk_freq 600 Health check frequency in seconds True
load_balancing no Dynamic Load Balancing True
switch_retries 5 Number of times to retry failed switches True
The output looks similar to the following example:
# lsattr -El dar0 |grep autorecovery
autorecovery no Autorecover after failure is corrected True
Configuring iSCSI on AIX 5.3L
Right now, I don’t have any branded iSCSI Solution with me, therefore, I considered a software based iSCSI server for evaluation. I am using Open-E software based iSCSI server software on HP DL-380 G5 with 4 GB RAM and 820 GB (RAID5) Storage.
I have successfully configured iSCSI Target on Windows and Linux but configuring iSCSI on AIX needs little more knowledge, please find below the necessary steps for configuring iSCSI on AIX 5.3L.
!!!! YOU MUST SET YOUR ISCSI TARGET TO "ISCSI ENTERPRISE TARGET [IET]" MODE. SCST, STGT, LIO DID'NT WORK FOR ME!!!!
!!!! I AM USING "OPEN-E DSS V6 LITE !!!!
*******This configuration is without CHAP Authentication********
You must know your iSCSI node name before configuring iSCSI on any host.
My iSCSI target node name: iqn.2011-01:dss.target4
1. Verify the Maintenance level server is running:
# oslevel -r
5200-03
2. Verify the correct iSCSI FileSets have been installed and should be COMMITTED in state:
# lslpp -l | grep -i iscsi
devices.common.IBM.iscsi.rte 5.2.0.30 COMMITTED Common iSCSI Files
devices.iscsi.disk.rte 5.2.0.30 COMMITTED iSCSI Disk Software
devices.iscsi.tape.rte 5.2.0.0 COMMITTED iSCSI Tape Software
devices.iscsi_sw.rte 5.2.0.1 COMMITTED iSCSI Software Device Driver
devices.iscsi_sw.rte 5.2.0.1 COMMITTED iSCSI Software Device Driver
3. Verify the iSCSI device is available in the kernel:
# lsdev -C | grep iscsi
iscsi0 Available iSCSI Protocol Device
4. Add the IP Address, default iSCSI port number, and iSCSI NodeName in "/etc/iscsi/targets"
# vi /etc/iscsi/targets
10.1.2.32 3260 iqn.2011-01:dss.target4
To verify issue the mentioned below command:
# tail -2 /etc/iscsi/targets
10.1.2.32 3260 iqn.2011-01:dss.target4
5.Verify the iSCSI Node Name of the AIX server:
# lsattr -El iscsi0
disc_filename /etc/iscsi/targets Configuration file False
disc_policy file Discovery Policy True
initiator_name iqn.1996-04.wasmq.hostid.0a3cac46 iSCSI Initiator Name True
max_targets 16 Maximum Targets Allowed True
num_cmd_elems 200 Maximum number of commands to queue to driver True
6. Modify the iSCSI Node Name of the AIX server:
# lsattr -El iscsi0
iqn.1996-04.wasmq.hostid.0a3cac46
To Modify issue the mentioned below command:
# chdev -l iscsi0 -a initiator_name=iqn.1992-08.com.ibm:wasmq
iscsi0 changed
7. Verify that the block devices have not been created for you on the AIX server:
# lsdev -Cc disk
hdisk0 Available 10-60-00-9,0 16 Bit SCSI Disk Drive
8. Rescan the iSCSI subsystem for new devices:
# cfgmgr -l iscsi0 OR cfgmgr
9. Verify that the block devices have been created for you on the AIX server:
# lsdev -Cc disk
hdisk0 Available 10-60-00-9,0 16 Bit SCSI Disk Drive
hdisk1 Available Other iSCSI Disk Drive (!!!!Congratulation!!!!)
For more info regarding disk issue the following command:
# lsattr -El hdisk1
10. Create a VG by issuing the following command:
# mkvg hdisk1
!!!! You are done !!!!
Saturday, 7 March 2009
How to move CD-Rom b/w LPARs
First check availability of cdrom on Source machine
Source :/>lsdev –Cccdrom
Cdo Available IDE DVD-RAM0
Second check slot in which cdrom attached.
Source :/>lsslot –c slot
# Slot Description Devices
xxx xxxxx Pci4 ento
xxx xxxxx Pci5 ent1
xxx xxxxx Pci2 scsi0
xxx xxxxx Pci3 ide0
Third remove cdrom from slot (pci3 ide0).
Source:/>rmdev –dl pci3 –R
Source:/>lsdev –Cccdrom
Source:/>
(no drive available means cdrom remove)
Fourth Go to HMC right mouse click source partition and select “Dynamics Logical Partitioning” Select Physical Resources” Select “Move” I/O...Move
Select device and move to destination.
***PLEASE DO NOT CONFUSE YOURSELF WITH IMAGE***
Select the “Bus” and dropdown the Slot as mentioned in step Two (Pci3 ide0)
***PLEASE DO NOT CONFUSE YOURSELF WITH IMAGE***
Select the desired bus and verify the desired device in located under the Bus, select Target machine and press move button.
Fifth login destination machine.
Dest:/>lsdev –Cccdrom
Dest:/>cfgmgr –V
Dest:/>lsdev –Cccdrom
Cdo Available IDE DVD-RAM0
How to move CD-Rom b/w LPARs
Now go to the target server and apply the following command to access CD-Rom Content
mount -rv cdrfs /dev/cd0 /cdrom
!!!You are done!!!
How to check AIX Fix pack
instfix -i |grep ML
All filesets for 5.3.0.0_AIX_ML were found.
All filesets for 5300-01_AIX_ML were found.
All filesets for 5300-02_AIX_ML were found.
All filesets for 5300-03_AIX_ML were found.
All filesets for 5300-04_AIX_ML were found.
All filesets for 5300-05_AIX_ML were found.
All filesets for 5300-06_AIX_ML were found.
All filesets for 5300-07_AIX_ML were found.
All filesets for 5300-08_AIX_ML were found.
The above mentioned fixes are installed in your AIX.
How to install patch/driver/installset in AIX
First check the installed fileset using mentioned below command and look for desired software for fileset. Please note some fileset requires prerequisites which needs to be implemented before the patch using same procedure.
E.g: we need to install “bos.cifs_fs”
Source :/>lslpp –l | more
Source :/>lslpp -l |grep cifs [cifs or else looking for]
Verify the file(s) listed or not.
Copy the patch or fileset to a Folder and run the following command from the folder.
Source :/patches>inutoc . (notice the dot)
Source :/patches>ls
Source :/patches> .toc bos.cifs_fs
Source :/patches>smitty installp
Press ENTER
Insert [.] and ENTER
Press ESC+4
Select the desired installset using TAB (> must appear) and press ENTER
By using TAB change the following:
- COMMIT software updates? Yes to NO
- PREVIEW only? (install operation will NOT occur) No
- ACCEPT new license agreements? No to YES
Press ENTER
The Screen must show “Command: Running” and then OK, please look at bottom of the page for successful installation or failure results.
In case of success: It must how “SUCCESS” depending on the installset packages
To verify go to the prompt and issue the following command
Source :/>lslpp -l |grep cifs [cifs or else looking for]
bos.cifs_fs.rte 5.3.8.0 COMMITTED Runtime for SMBFS
bos.cifs_fs.smit 5.3.7.0 COMMITTED SMIT Interface for SMBFS
bos.cifs_fs.rte 5.3.8.0 COMMITTED Runtime for SMBFS
bos.cifs_fs.smit 5.3.7.0 COMMITTED SMIT Interface for SMBFS
!!!!You are done !!!!
As a student of Information technology, I have learned so many things and I want to share my little knowledge with other IT professional across the planet.
Basically, I am Windows guy and nowadays, I am experiencing different flavors of UNIX family i.e. AIX and Linux (Fedora, Red Hat and SUSE).
I am working with Windows since Windows 3.1, N.T 3.5 and I feel Linux can do a much better job in a much cheaper cost. Therefore, I initiated to transform services from Windows platform to Linux and I am gaining confidence day-by-day.
Please keep in mind that I am not against Windows, but I always prefer to do things out-of-the-box.
I shall be posting my documents and guides and other IT stuff time-to-time, so stay in touch.
The Blog primarily focus on AIX.