blog'o thnet

To content | To menu | To search

Tag - management

Entries feed - Comments feed

Sunday 1 May 2011

Switching From RDAC To MPIO For DSXX00 SAN Array

By Julien Gabel on Sunday 1 May 2011, 16:22 - AIX

Here is a simple procedure switching from a RDAC/fcparray management mode to a MPIO multipath mode for SAN disks presented from an IBM DSXX00 array.

Verification of the current monopath configuration:

# 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

Listing of the disks from the array:

# fget_config -vA
---dar0---

User array name = 'CUSTOMERSOFT'
dac0 ACTIVE dac5 ACTIVE

Disk     DAC   LUN Logical Drive
utm            127
hdisk7   dac5    6 beastie1_oracle
hdisk14  dac5   13 beastie2_datavg
hdisk15  dac0   14 beastie3_datavg
hdisk2   dac0    1 beastie3_rootvg
hdisk3   dac0    2 beastie4_rootvg
hdisk4   dac5    3 beastie5_rootvg
hdisk5   dac5    4 beastie2_rootvg
hdisk6   dac0    5 bakup
hdisk8   dac0    7 customer1
hdisk9   dac0    8 customer3
hdisk10  dac5    9 customer6
hdisk11  dac0   10 customer14
hdisk12  dac5   11 beastie2_db2
hdisk13  dac0   12 beastie3_scheduler
hdisk16  dac0   15 customer9
hdisk17  dac0   16 customer8

Listing of the disks as seen from the operating system:

# lsdev -Cc disk | grep DS
hdisk2  Available 00-08-02 1814     DS4700 Disk Array Device
hdisk3  Available 00-08-02 1814     DS4700 Disk Array Device
hdisk4  Available 02-00-02 1814     DS4700 Disk Array Device
hdisk5  Available 02-00-02 1814     DS4700 Disk Array Device
hdisk6  Available 00-08-02 1814     DS4700 Disk Array Device
hdisk7  Available 02-00-02 1814     DS4700 Disk Array Device
hdisk8  Available 00-08-02 1814     DS4700 Disk Array Device
hdisk9  Available 00-08-02 1814     DS4700 Disk Array Device
hdisk10 Available 02-00-02 1814     DS4700 Disk Array Device
hdisk11 Available 00-08-02 1814     DS4700 Disk Array Device
hdisk12 Available 02-00-02 1814     DS4700 Disk Array Device
hdisk13 Available 00-08-02 1814     DS4700 Disk Array Device
hdisk14 Available 02-00-02 1814     DS4700 Disk Array Device
hdisk15 Available 00-08-02 1814     DS4700 Disk Array Device
hdisk16 Available 00-08-02 1814     DS4700 Disk Array Device
hdisk17 Available 00-08-02 1814     DS4700 Disk Array Device

Switch to a multipath management for the SAN volumes presented from the DS4700/DS4200 arrays:

# manage_disk_drivers -c 4
DS4700/DS4200 currently RDAC/fcparray
Change to alternate driver? [Y/N] Y
DS4700/DS4200 now managed by MPIO

It is necessary to perform a bosboot before rebooting the system in
order to incorporate this change into the boot image.

In order to change to the new driver, either a reboot or a full
unconfigure and reconfigure of all devices of the type changed
must be performed.

Reboot the system:

# bosboot –a
bosboot: Boot image is 39636 512 byte blocks.

# shutdown –Fr
[...]

Verification of the new multipath configuration:

# 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 MPIO; supported: RDAC/fcparray, MPIO
5: DS4800: currently RDAC; supported: RDAC/fcparray, MPIO

Listing of the disks from the array:

# mpio_get_config -vA
Frame id 0:
    Storage Subsystem worldwide name: 60ab80016253400009786efca
    Controller count: 2
    Partition count: 1
    Partition 0:
    Storage Subsystem Name = 'CUSTOMERSOFT'
        hdisk      LUN #   Ownership          User Label
        hdisk0         1   A (preferred)      beastie3_rootvg
        hdisk1         2   A (preferred)      beastie4_rootvg
        hdisk2         3   B (preferred)      beastie5_rootvg
        hdisk3         4   B (preferred)      beastie2_rootvg
        hdisk4         5   A (preferred)      bakup
        hdisk5         6   B (preferred)      beastie1_oracle
        hdisk6        16   A (preferred)      customer8
        hdisk7         7   A (preferred)      customer1
        hdisk8         8   A (preferred)      customer3
        hdisk9         9   B (preferred)      customer6
        hdisk10       10   A (preferred)      customer14
        hdisk11       11   B (preferred)      beastie2_db2
        hdisk12       12   A (preferred)      beastie3_scheduler
        hdisk13       13   B (preferred)      beastie2_datavg
        hdisk14       14   A (preferred)      beastie3_datavg
        hdisk15       15   A (preferred)      customer9

Listing of the disks as seen from the operating system:

# lsdev -Cc disk | grep DS
hdisk0  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk1  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk2  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk3  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk4  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk5  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk6  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk7  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk8  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk9  Available 06-08-02 MPIO Other DS4K Array Disk
hdisk10 Available 06-08-02 MPIO Other DS4K Array Disk
hdisk11 Available 06-08-02 MPIO Other DS4K Array Disk
hdisk12 Available 06-08-02 MPIO Other DS4K Array Disk
hdisk13 Available 06-08-02 MPIO Other DS4K Array Disk
hdisk14 Available 06-08-02 MPIO Other DS4K Array Disk
hdisk15 Available 06-08-02 MPIO Other DS4K Array Disk
hdisk16 Available 06-08-02 MPIO Other DS4K Array Disk

That's it.

no comment

Wednesday 29 June 2005

Static Route Management for Hosts in the Demilitarized Zone (DMZ)

By Julien Gabel on Wednesday 29 June 2005, 11:39 - Solaris

Based on existing procedures, here is a new tool which aim is to help adding centralized managed static routes for all servers hosted in the demilitarized zone. As for the Password Management for Hosts in the Demilitarized Zone (DMZ), this script is managed using the cvs(1) concurrent management system.

Follow are the three necessary files:

  1. dmz_routes.sh this one is able to get, push and apply new static route(s) remotely
  2. route_admin this script can list and apply new static route(s) locally and is used from rc script at boot time
  3. route_admin.cfg current static routes commented configuration file; used by route_admin

Assuming that the environment variables ${CVSROOT} and ${CVS_RSH} are properly sets, here are little samples of usage:

# cvs checkout -P dmz_route && cd dmz_route
#
# sh ./dmz_route.sh
usage: dmz_route.sh [-hd] [-s servername,...] [-c config_file] [-i init.d_file] {push|add|status}
#
# sh ./dmz_route.sh -s beastie status
* server: beastie
 => state of files:
/data/system/etc/
/data/system/etc/init.d/
/data/system/etc/route_admin.cfg:
     $Id: route_admin.cfg,v 1.10 2005/02/14 14:14:14 root Exp $
/data/system/etc/init.d/route_admin:
     $Id: route_admin,v 1.9 2004/09/14 08:19:29 root Exp $
 => show the routing tables:IRE Table: IPv4
  Destination             Mask           Gateway          Device Mxfrg  Rtt  Ref Flg  Out  In/Fwd
-------------------- --------------- -------------------- ------ ----- ----- --- --- ----- ------
10.126.220.40        255.255.255.255 192.168.138.33               1500*    0   1 UGH    790     0
10.126.220.41        255.255.255.255 192.168.138.33               1500*    0   1 UGH   2862     0
10.126.215.162       255.255.255.255 192.168.138.33               1500*    0   1 UGH     65     0
[...]
#
# sh ./dmz_route.sh -s beastie push
* server: beastie
 => last configuration backuped
 => route_admin.cfg pushed
 => route_admin pushed

Need more help?... See the command line help switch:

# sh ./dmz_route.sh -h

no comment

Saturday 25 June 2005

Password Management for Hosts in the Demilitarized Zone (DMZ)

By Julien Gabel on Saturday 25 June 2005, 11:39 - Solaris

Based on existing procedures, here is a new tool which aim is to help managing centralized passwords for all servers hosted in the demilitarized zone. As for the Static Route Management for Hosts in the Demilitarized Zone (DMZ), this script is managed using the cvs(1) concurrent management system.

Follow is the named script:

  • dmz_passwd.sh this one is able to get and set some password configurations and/or parameters remotely

Assuming that the environment variables ${CVSROOT} and ${CVS_RSH} are properly sets, here are little samples of usage:

# cvs checkout -P dmz_passwd && cd dmz_passwd
#
# sh ./dmz_passwd.sh
usage: dmz_passwd.sh [-hd] [-s servername,...] [-n min_day] [-x max_day] [-w warn_day] -u username,... {status|set|unlock|lock|reset}
#
# sh ./dmz_passwd.sh -s unic -u greg set
* server: unic
 => *set* password attributes and policy for user: greg
#
# sh ./dmz_passwd.sh -s unic,beastie -u greg status
* server: unic
 => *get* password attributes and policy for user: greg
    .password status: locked [LK]
    .last changed: 13 September 2004
    .minimum between password changes: 0 day(s)
    .maximum between password changes: 91 day(s)
    .warning before the password expires: 7 day(s)
    .password will expire at: 13 December 2004

* server: beastie
 => *get* password attributes and policy for user: greg
    .password status: passworded or locked [PS]

Need more help?... See the command line help switch:

# sh ./dmz_passwd.sh -h

no comment