So I have the old 7500 post from since 2007 when I created the FCIP 7500 cheat sheet.  I thought it was time for an updated to include the 7800.  Lots/Most of the terminology hasn’t changed since the 7500.  I can tell since I have started using this technology its much more flexable than the 7500.  Kudo’s to Brocade on that one.. Link to Brocade 7800 details..

So lets get into it then, the 7800′s introduced this concept of circuits which I really like since you can aggregate multiple ethernet interfaces into one tunnel. For my example we have 4 circuits per FCIP Router that make up one VE-Port (Virtual E-Port). This enabled me to run my physical ethernet interfaces to different LAN switches extending the redundancy for the router.

They have also an easy to deploy encryption service as well as 4 compression levels (For those who don’t have a silver-peak and/or cisco wan accelerator). The four encryption levels include:

• Software
• Hardware
• Software / Hardware
• Automatic (Based on load) ** I am using automatic, but if you were using WAN acceleration you would want to disable this compression feature in the tunnel/circuit creation.

The one really slick feature I like is the ARL (Adaptive Rate Limit), this function put simply enables the end-user to put a low end and a high end limit on how how bandwidth is able to be consumed per circuit.  This will be different in every situation etc. So here is a list of CLI commands to enable FCIP on a Brocade 7800:

Source Location
ge0 – fcrap14c002
portcfg ipif ge0 create 10.0.0.1 255.255.252.0 1428
portcfg iproute ge0 create 10.12.0.1 255.255.240.0 10.0.1.250 0

portcfg ipif ge1 create 10.0.0.1 255.255.252.0 1428
portcfg iproute ge1 create 10.12.0.2 255.255.240.0 10.0.1.250 0

portcfg ipif ge2 create 10.0.0.3 255.255.252.0 1428
portcfg iproute ge2 create 10.12.0.3 255.255.240.0 10.0.1.250 0

portcfg ipif ge3 create 10.0.0.4 255.255.252.0 1428
portcfg iproute ge3 create 10.12.0.4 255.255.240.0 10.0.1.250 0

Destination Location
ge0 – fcrrp21002
portcfg ipif ge0 create 10.12.0.1 255.255.240.0 1428
portcfg iproute ge0 create 10.0.0.1 255.255.252.0 10.12.0.250 0

portcfg ipif ge1 create 10.12.0.2 255.255.240.0 1428
portcfg iproute ge1 create 10.0.0.2 255.255.252.0 10.12.0.250 0

portcfg ipif ge2 create 10.12.0.3 255.255.240.0 1428
portcfg iproute ge2 create 10.0.0.3 255.255.252.0 10.12.0.250 0

portcfg ipif ge3 create 10.12.0.4 255.255.240.0 1428
portcfg iproute ge3 create 10.0.0.4 255.255.252.0 10.12.0.250 0

To ensure connectivity between the location execute and ping and traceroute on each circuit pair.  It’s also a good idea (standards wize) to pair up the ethernet ports to each other.

ge0 –> ge0 ge1–> ge1 and so on.  It’s also nice to align the ip address if you are able, just makes things easier to troubleshoot later on.

portcmd –ping ge0 -d 10.0.0.1 -s 10.12.0.1
portcmd –traceroute ge0 -s 10.0.0.1 -d 10.0.0.1

780001Src> portshow iproute ge0
780003Dest> portshow iproute ge0

Create your routes

portcfg iproute ge0 create 10.12.0.10 (From FC) 255.255.240.0 (Mask from Dest) 10.0.0.250 (Gateway on Source) 0 (Metric)

portcfg iproute ge0 create 10.0.0.10 (From FC) 255.255.240.0 (Mask from Dest) 10.12.0.250 (Gateway on source) 0 (Metric)

Perform this for each ethernet interface you wish to configure.

Create the ex port trunks for the environment ( Make sure you persistenly enable these ports before beginning, by default ports are persistently disabled – as shown below)

Source >>portcfgpersistentenable 0
Destination >>portcfgpersistentenable 0

Source to connect the edge fabrics (-f Fabric ID -d sub-domain id)
Fabric 0 >> portcfgexport 0 -a 1 -f 72 -d 120
Fabric 3 >> portcfgexport 1 -a 1 -f 72 -d 120
Fabric 5 >> portcfgexport 2 -a 1 -f 50 -d 120

Destination to connect the edge fabrics
Fabric 0 >> portcfgexport 0 -a 1 -f 73 -d 120
Fabric 3 >> portcfgexport 1 -a 1 -f 73 -d 120
Fabric 5 >> portcfgexport 2 -a 1 -f 33 -d 120

Verify that you edge fabric are connected to each backbone router (>fcrfabricshow will tell you that detail, note you will only see the local edge fabric at first since we haven’t created the circuits and tunnels yet)

Circuit and Tunnel Creation:

Create the tunnels
Source and Destination -Tunnel 16 (-b lower limit of ARL, -B upper limit of ARL, -c 4 auto-compression )
Source >> portcfg fciptunnel 16 create 10.12.0.1 10.0.0.1 -b 50000 -B 100000 -c 4
Dest >> portcfg fciptunnel 16 create 10.0.0.1 10.12.0.1 -b 50000 -B 100000 -c 4
Add Cicuits (ARL is the same, the tunnel determines compression and other options, -x 0 is used to determine failover circuits, since a tunnel can be made up of multiple circuits. To keep things simple we have 1 circuit in our tunnel)
Source >> portcfg fcipcircuit 16 create 1 10.12.0.2 10.0.0.2 -b 50000 -B 100000 -x 1
Dest >> portcfg fcipcircuit 16 create 1 10.0.0.2 10.12.0.2 -b 50000 -B 100000 -x 1

Source >>portcfgpersistentenable 16
Dest >>portcfgpersistentenable 16

Some useful commands

Useful commands
portshow fciptunnel 16 shows single tunnel
portshow fciptunnel all – shows all the configured tunnels
portshow fciptunnel all -c shows all of the tunnels and circuits
portshow fciptunnel 16 -c show circuit and tunnel
portshow fciptunnel 16 -p show tunnel performance
portshow fciptunnel 16 -cp show tunnel and circuit performance
portshow fcipcircuit 16 shows circuit
tperf replacement for ipperf from the 7500

Ensure that wwn’s are being proxyed thru the environment correctly (aka verification of the LSAN zones are correct)

fcrproxydevshow (Shows proxied wwn’s from other edge fabrics, shows FID so you know which edge fabric they are coming from)

fcrphydevshow (Shows the local wwn’s imported into the router, shows FID so you know which edge fabric they are coming from)

Hopefully this post helps you out if you need more assitance see the contact page and email me or find me twitter.

Thanks..

Ran into an issue recently when our Tuning Manager retention slipped us into an full Tuning  Manager database.  We had plenty of file system space so just needed to figure out how to grow it. This is the process I followed:

Shutdown the hcmdservices & Start the database

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbsrv /start

KAPM06438-I The HiRDB service has started.

Check the space and size this will give you the location and size of the database

C:\Program Files (x86)\HiCommand\TuningManager\bin>htm-db-status.bat

KATN01314-I The command htm-db-status will now be executed.

Database Capacity (Used/Total): 1742440 / 2048000 kBytes

Area Path: E:\HiCommand\database\TuningManager\TM00

KATN01309-I The database status has been displayed.

Shutdown the database in order to grow it the default is 2GB and can be grwo in 2GB increments up to 32GB Max

Grow the Tunmgr Database

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbsrv /stop

KAPM06439-I The HiRDB service has stopped.

C:\Program Files (x86)\HiCommand\TuningManager\bin>htm-db-setup /size 4 /areapath E:\HiCommand\database\TuningManager\

KATN01300-I Execution of the command htm-db-setup has started.

KATN01331-I The database file system has been created. (1/2)

KATN01331-I The database file system has been created. (2/2)

KATN01307-I The command htm-db-setup terminated normally.

Check to see and make sure your growth worked.  Reboot your HCS Server and then force a polling interval makes the error should go away

C:\Program Files (x86)\HiCommand\TuningManager\bin>htm-db-status.bat

KATN01314-I The command htm-db-status will now be executed.

Database Capacity (Used/Total): 1742440 / 6144000 kBytes

Area Path:

E:\HiCommand\database\TuningManager\TM00

E:\HiCommand\database\TuningManager\TuningManager\TM01

E:\HiCommand\database\TuningManager\TuningManager\TM02

KATN01309-I The database status has been displayed.

All of this detail can be found in the tuning manager server configuration guide.  Hopefully this helps you out a jam..

• V05 or greater
• Raidcom version 1-29-03 or higher
• For the best performance just like CoW requires and separate parity group(s)
• Usually a 7+1 with with 4 equal ldev sizes is the best practice
• Separate CLPR’s aren’t required yippee!! (No need since it’s asynchronous)

So lets get into the fun part (raidcom to manage thin image) If you are tired of CCI (and all the HORCM fun – pair create, pairdisplay go bye bye) using a ip-command-device along with raidcom makes life a whole lot easier.

• Creating an HTI pool using raid com
  • raidcom add snap_pool -pool_id 101 -pool_name ThinImagePool -ldev_id 0F:00-0F:03 –thinsnap
• Create you Svol and map it to a Host Group
  • raidcom add ldev -pool snap -ldev_id 0xBB02 -capacity 10g
  • See previous Post for HG Mapping
• Create your pair using the PVOL/SVOL and a Snapshot Group name
  • raidcom add snapshot -ldev_id 0xAA02 0xBB02 -pool 100 -snapshotgroup oracle-snap
• Check the Status of your Pair (PAIR, PSUS, etc)
  • raidcom get snapshot -snapshotgroup oracle-snap
• Split your pairs
  • raidcom modify snapshot -snapshotgroup oracle-snap -snapshot_data split
•  Resynch Your Pairs
  • raidcom modify snapshot -snapshotgroup oracle-snap -snapshot_data resync
• Delete your Pairs
  • raidcom delete snapshot -snapshotgroup oracle-snap
• Show the Status of your Thin Image Pool (Shows pool status, snapshot counts, pool usage)
  • raidcom get snap_pool

In summary you can script this process as most of us do..  Hope this little post helps you.. All the best until next time……

Data Center Management (Part-1) Cable Management..

http://www.dcig.com/2012/12/top-5-most-viewed-blog-entries-2012.html

Available commands:
——————-
pureadmin – set password and keys for admin account
purealert – Email address add and removal for alerts
purearray
pureconfig
puredns – set and list dns servers
puredrive – list all the drives in the system
purehelp
purehgroup – list, create, delete, rename HG
purehost – list, create, delete, rename Hosts
purehw – list controller and disk information
purelogger – Working on determining this one..
pureman – Display MAN pages for the other commands
puremonitor – shows volume level performance stats, ops, latency, thruput

Show 5 sec interval 20 times rolling – like tailing a file…

puremonitor –interval 5 –total –nrep 20
purenetwork – list, ping, trace network information
pureport – list, enable and disable FC ports
purevol
exit
logout

Some Examples..

pureuser@SSD> pureconfig list
purearray rename SSD
purevol create –size 250G VDI1
purevol create –size 250G VDI2
purevol create –size 250G VDI3
purevol create –size 250G VDI4
purevol create –size 1T VMServer1
purevol create –size 1T VMServer2
purevol create –size 1T VMServer3
purevol create –size 1T VMServer4
purehost create –wwnlist 10:00:00:00:C9:BB:8D:00,10:00:00:00:C9:BB:8D:00 server1
purehost create –wwnlist 10:00:00:00:C9:BB:7F:00,10:00:00:00:C9:BB:7F:00 server2
purehgroup create –hostlist server1,server2 VMware-Farm
purehgroup connect –lun 10 –vol VDI1 -Farm
purehgroup connect –lun 11 –vol VDI2 -Farm
purehgroup connect –lun 12 –vol VDI3 -Farm
purehgroup connect –lun 13 –vol VDI4 -Farm
purehgroup connect –lun 14 –vol VMServer1 -Farm
purehgroup connect –lun 15 –vol VMServer2 -Farm
purehgroup connect –lun 16 –vol VMServer3 -Farm
purehgroup connect –lun 17 –vol VMServer4 -Farm
purenetwork setattr –mode static –address 10.1.1.1 –netmask 255.255.252.0 –gateway 10.1.1.250 ct0.eth0
purenetwork enable ct0.eth0
purenetwork setattr –mode static –address “” –netmask “” –gateway “” ct0.eth1
purenetwork enable ct0.eth1
purenetwork setattr –mode static –address 10.1.1.2 –netmask 255.255.252.0 –gateway 10.1.1.250 ct1.eth0
purenetwork enable ct1.eth0
purenetwork setattr –mode static –address “” –netmask “” –gateway “” ct1.eth1
purenetwork enable ct1.eth1
purenetwork setattr –mode static –address 10.1.1.3 –netmask 255.255.252.0 –gateway 10.1.1.250 vir0
purenetwork enable vir0
purenetwork setattr –mode static –address “” –netmask “” –gateway “” vir1
purenetwork enable vir1
puredns setattr –mode static –domain .com –nameservers list of dns servers
purealert enable support@purestorage.com
purealert create someone@somewhere.com
purealert enable someone@somewhere.com
purearray setattr –ntpserver time..com
purearray enable phonehome
purearray setattr –relayhost mail..com
purearray setattr –senderdomain noreply..com

pureuser@SSD> puredrive list
Name Type Status Capacity Degraded Last Failure Last Evac Completed
SH0.DRV0 NVRAM healthy 2.00G 0.00 – -
SH0.DRV0 NVRAM healthy 2.00G 0.00 – -
SH0.DRV1 SSD healthy 238.47G 0.00 – -
SH0.DRV1 SSD healthy 238.47G 0.00 – -
SH0.DRV10 SSD healthy 238.47G 0.00 – -
SH0.DRV10 SSD healthy 238.47G 0.00 – -
SH0.DRV11 SSD healthy 238.47G 0.00 – -
SH0.DRV11 SSD healthy 238.47G 0.00 – -
SH0.DRV12 SSD healthy 238.47G 0.00 – -
SH0.DRV12 SSD healthy 238.47G 0.00 – -
SH0.DRV13 SSD healthy 238.47G 0.00 – -
SH0.DRV13 SSD healthy 238.47G 0.00 – -
SH0.DRV14 SSD healthy 238.47G 0.00 – -
SH0.DRV14 SSD healthy 238.47G 0.00 – -
SH0.DRV15 SSD healthy 238.47G 0.00 – -
SH0.DRV15 SSD healthy 238.47G 0.00 – -
SH0.DRV16 SSD healthy 238.47G 0.00 – -
SH0.DRV16 SSD healthy 238.47G 0.00 – -
SH0.DRV17 SSD healthy 238.47G 0.00 – -
SH0.DRV17 SSD healthy 238.47G 0.00 – -
SH0.DRV18 SSD healthy 238.47G 0.00 – -
SH0.DRV18 SSD healthy 238.47G 0.00 – -
SH0.DRV19 SSD healthy 238.47G 0.00 – -
SH0.DRV19 SSD healthy 238.47G 0.00 – -
SH0.DRV2 SSD healthy 238.47G 0.00 – -
SH0.DRV2 SSD healthy 238.47G 0.00 – -
SH0.DRV20 SSD healthy 238.47G 0.00 – -
SH0.DRV20 SSD healthy 238.47G 0.00 – -
SH0.DRV21 SSD healthy 238.47G 0.00 – -
SH0.DRV21 SSD healthy 238.47G 0.00 – -
SH0.DRV22 SSD healthy 238.47G 0.00 – -
SH0.DRV22 SSD healthy 238.47G 0.00 – -
SH0.DRV23 NVRAM healthy 2.00G 0.00 – -
SH0.DRV23 NVRAM healthy 2.00G 0.00 – -
SH0.DRV3 SSD healthy 238.47G 0.00 – -
SH0.DRV3 SSD healthy 238.47G 0.00 – -
SH0.DRV4 SSD healthy 238.47G 0.00 – -
SH0.DRV4 SSD healthy 238.47G 0.00 – -
SH0.DRV5 SSD healthy 238.47G 0.00 – -
SH0.DRV5 SSD healthy 238.47G 0.00 – -
SH0.DRV6 SSD healthy 238.47G 0.00 – -
SH0.DRV6 SSD healthy 238.47G 0.00 – -
SH0.DRV7 SSD healthy 238.47G 0.00 – -
SH0.DRV7 SSD healthy 238.47G 0.00 – -
SH0.DRV8 SSD healthy 238.47G 0.00 – -
SH0.DRV8 SSD healthy 238.47G 0.00 – -
SH0.DRV9 SSD healthy 238.47G 0.00 – -
SH0.DRV9 SSD healthy 238.47G 0.00 – -

pureuser@SSD> purehw list
Name Status Identify Slot Index Speed Temperature
CT0 ok off 0 0 – -
CT0.BAY0 not_installed off 0 0 – -
CT0.BAY1 not_installed off 0 1 – -
CT0.BAY10 not_installed off 0 10 – -
CT0.BAY11 not_installed off 0 11 – -
CT0.BAY2 not_installed off 0 2 – -
CT0.BAY3 ok off 0 3 – -
CT0.BAY4 not_installed off 0 4 – -
CT0.BAY5 not_installed off 0 5 – -
CT0.BAY6 not_installed off 0 6 – -
CT0.BAY7 not_installed off 0 7 – -
CT0.BAY8 not_installed off 0 8 – -
CT0.BAY9 not_installed off 0 9 – -
CT0.ETH0 ok – - 0 1.00Gbps -
CT0.ETH1 ok – - 1 0.00bps -
CT0.FAN0 ok – 0 0 5570rpm -
CT0.FAN1 ok – 0 1 6230rpm -
CT0.FAN2 ok – 0 2 5270rpm -
CT0.FAN3 ok – 0 3 5870rpm -
CT0.FAN4 ok – 0 4 5450rpm -
CT0.FAN5 ok – 0 5 6200rpm -
CT0.FAN6 ok – 0 6 5570rpm -
CT0.FAN7 ok – 0 7 6080rpm -
CT0.FAN8 ok – 0 8 5390rpm -
CT0.FAN9 ok – 0 9 5990rpm -
CT0.FC0 ok – 1 0 8.00Gbps -
CT0.FC1 ok – 1 1 8.00Gbps -
CT0.FC2 ok – 2 2 8.00Gbps -
CT0.FC3 ok – 2 3 8.00Gbps -
CT0.IB0 ok – 6 0 40.00Gbps -
CT0.IB1 ok – 6 1 40.00Gbps -
CT0.PWR0 ok – 0 0 – -
CT0.PWR1 ok – 0 1 – -
CT0.SAS0 ok – 4 0 24.00Gbps -
CT0.SAS1 ok – 4 1 24.00Gbps -
CT0.SAS2 ok – 5 2 24.00Gbps -
CT0.SAS3 ok – 5 3 24.00Gbps -
CT0.TMP0 ok – 0 0 – 24C
CT0.TMP1 ok – 0 1 – 26C
CT0.TMP10 ok – 0 10 – 35C
CT0.TMP11 ok – 0 11 – 33C
CT0.TMP12 ok – 0 12 – 44C
CT0.TMP13 ok – 0 13 – 45C
CT0.TMP14 ok – 0 14 – 46C
CT0.TMP15 ok – 0 15 – 43C
CT0.TMP16 ok – 0 16 – 43C
CT0.TMP17 ok – 0 17 – 41C
CT0.TMP18 ok – 0 18 – 44C
CT0.TMP2 ok – 0 2 – 28C
CT0.TMP3 ok – 0 3 – 22C
CT0.TMP4 ok – 0 4 – 38C
CT0.TMP5 ok – 0 5 – 40C
CT0.TMP6 ok – 0 6 – 36C
CT0.TMP7 ok – 0 7 – 35C
CT0.TMP8 ok – 0 8 – 35C
CT0.TMP9 ok – 0 9 – 34C
CT1 ok off – 1 – -
CT1.BAY0 not_installed – - 0 – -
CT1.BAY1 not_installed – - 1 – -
CT1.BAY10 not_installed – - 10 – -
CT1.BAY11 not_installed – - 11 – -
CT1.BAY2 not_installed – - 2 – -
CT1.BAY3 ok – - 3 – -
CT1.BAY4 not_installed – - 4 – -
CT1.BAY5 not_installed – - 5 – -
CT1.BAY6 not_installed – - 6 – -
CT1.BAY7 not_installed – - 7 – -
CT1.BAY8 not_installed – - 8 – -
CT1.BAY9 not_installed – - 9 – -
CT1.ETH0 ok – - 0 1.00Gbps -
CT1.ETH1 ok – - 1 0.00bps -
CT1.FAN0 ok – - 0 5330rpm -
CT1.FAN1 ok – - 1 5750rpm -
CT1.FAN2 ok – - 2 5150rpm -
CT1.FAN3 ok – - 3 6230rpm -
CT1.FAN4 ok – - 4 5810rpm -
CT1.FAN5 ok – - 5 5990rpm -
CT1.FAN6 ok – - 6 5660rpm -
CT1.FAN7 ok – - 7 6320rpm -
CT1.FAN8 ok – - 8 5390rpm -
CT1.FAN9 ok – - 9 6020rpm -
CT1.FC0 ok – 1 0 8.00Gbps -
CT1.FC1 ok – 1 1 8.00Gbps -
CT1.FC2 ok – 2 2 8.00Gbps -
CT1.FC3 ok – 2 3 8.00Gbps -
CT1.IB0 ok – 6 0 40.00Gbps -
CT1.IB1 ok – 6 1 40.00Gbps -
CT1.PWR0 ok – - 0 – -
CT1.PWR1 ok – - 1 – -
CT1.SAS0 ok – 4 0 24.00Gbps -
CT1.SAS1 ok – 4 1 24.00Gbps -
CT1.SAS2 ok – 5 2 24.00Gbps -
CT1.SAS3 ok – 5 3 24.00Gbps -
CT1.TMP0 ok – - 0 – 24C
CT1.TMP1 ok – - 1 – 25C
CT1.TMP10 ok – - 10 – 33C
CT1.TMP11 ok – - 11 – 32C
CT1.TMP12 ok – - 12 – 43C
CT1.TMP13 ok – - 13 – 45C
CT1.TMP14 ok – - 14 – 45C
CT1.TMP15 ok – - 15 – 44C
CT1.TMP16 ok – - 16 – 43C
CT1.TMP17 ok – - 17 – 41C
CT1.TMP18 ok – - 18 – 42C
CT1.TMP2 ok – - 2 – 27C
CT1.TMP3 ok – - 3 – 22C
CT1.TMP4 ok – - 4 – 38C
CT1.TMP5 ok – - 5 – 37C
CT1.TMP6 ok – - 6 – 35C
CT1.TMP7 ok – - 7 – 33C
CT1.TMP8 ok – - 8 – 34C
CT1.TMP9 ok – - 9 – 33C
SH0 ok off – 0 – -
SH0 ok off – 0 – -
SH0.BAY0 ok off – 0 – -
SH0.BAY0 ok off – 0 – -
SH0.BAY1 ok off – 1 – -
SH0.BAY1 ok off – 1 – -
SH0.BAY10 ok off – 10 – -
SH0.BAY10 ok off – 10 – -
SH0.BAY11 ok off – 11 – -
SH0.BAY11 ok off – 11 – -
SH0.BAY12 ok off – 12 – -
SH0.BAY12 ok off – 12 – -
SH0.BAY13 ok off – 13 – -
SH0.BAY13 ok off – 13 – -
SH0.BAY14 ok off – 14 – -
SH0.BAY14 ok off – 14 – -
SH0.BAY15 ok off – 15 – -
SH0.BAY15 ok off – 15 – -
SH0.BAY16 ok off – 16 – -
SH0.BAY16 ok off – 16 – -
SH0.BAY17 ok off – 17 – -
SH0.BAY17 ok off – 17 – -
SH0.BAY18 ok off – 18 – -
SH0.BAY18 ok off – 18 – -
SH0.BAY19 ok off – 19 – -
SH0.BAY19 ok off – 19 – -
SH0.BAY2 ok off – 2 – -
SH0.BAY2 ok off – 2 – -
SH0.BAY20 ok off – 20 – -
SH0.BAY20 ok off – 20 – -
SH0.BAY21 ok off – 21 – -
SH0.BAY21 ok off – 21 – -
SH0.BAY22 ok off – 22 – -
SH0.BAY22 ok off – 22 – -
SH0.BAY23 ok off – 23 – -
SH0.BAY23 ok off – 23 – -
SH0.BAY3 ok off – 3 – -
SH0.BAY3 ok off – 3 – -
SH0.BAY4 ok off – 4 – -
SH0.BAY4 ok off – 4 – -
SH0.BAY5 ok off – 5 – -
SH0.BAY5 ok off – 5 – -
SH0.BAY6 ok off – 6 – -
SH0.BAY6 ok off – 6 – -
SH0.BAY7 ok off – 7 – -
SH0.BAY7 ok off – 7 – -
SH0.BAY8 ok off – 8 – -
SH0.BAY8 ok off – 8 – -
SH0.BAY9 ok off – 9 – -
SH0.BAY9 ok off – 9 – -
SH0.DRV0 ok – - 0 – -
SH0.DRV0 ok – - 0 – -
SH0.DRV1 ok – - 1 – -
SH0.DRV1 ok – - 1 – -
SH0.DRV10 ok – - 10 – -
SH0.DRV10 ok – - 10 – -
SH0.DRV11 ok – - 11 – -
SH0.DRV11 ok – - 11 – -
SH0.DRV12 ok – - 12 – -
SH0.DRV12 ok – - 12 – -
SH0.DRV13 ok – - 13 – -
SH0.DRV13 ok – - 13 – -
SH0.DRV14 ok – - 14 – -
SH0.DRV14 ok – - 14 – -
SH0.DRV15 ok – - 15 – -
SH0.DRV15 ok – - 15 – -
SH0.DRV16 ok – - 16 – -
SH0.DRV16 ok – - 16 – -
SH0.DRV17 ok – - 17 – -
SH0.DRV17 ok – - 17 – -
SH0.DRV18 ok – - 18 – -
SH0.DRV18 ok – - 18 – -
SH0.DRV19 ok – - 19 – -
SH0.DRV19 ok – - 19 – -
SH0.DRV2 ok – - 2 – -
SH0.DRV2 ok – - 2 – -
SH0.DRV20 ok – - 20 – -
SH0.DRV20 ok – - 20 – -
SH0.DRV21 ok – - 21 – -
SH0.DRV21 ok – - 21 – -
SH0.DRV22 ok – - 22 – -
SH0.DRV22 ok – - 22 – -
SH0.DRV23 ok – - 23 – -
SH0.DRV23 ok – - 23 – -
SH0.DRV3 ok – - 3 – -
SH0.DRV3 ok – - 3 – -
SH0.DRV4 ok – - 4 – -
SH0.DRV4 ok – - 4 – -
SH0.DRV5 ok – - 5 – -
SH0.DRV5 ok – - 5 – -
SH0.DRV6 ok – - 6 – -
SH0.DRV6 ok – - 6 – -
SH0.DRV7 ok – - 7 – -
SH0.DRV7 ok – - 7 – -
SH0.DRV8 ok – - 8 – -
SH0.DRV8 ok – - 8 – -
SH0.DRV9 ok – - 9 – -
SH0.DRV9 ok – - 9 – -
SH0.FAN0 ok – - 0 5020rpm -
SH0.FAN0 ok – - 0 5100rpm -
SH0.FAN1 ok – - 1 4650rpm -
SH0.FAN1 ok – - 1 4800rpm -
SH0.FAN2 ok – - 2 5020rpm -
SH0.FAN2 ok – - 2 5250rpm -
SH0.FAN3 ok – - 3 4650rpm -
SH0.FAN3 ok – - 3 4800rpm -
SH0.IOM0 ok off 0 0 – -
SH0.IOM0 ok off 0 0 – -
SH0.IOM1 ok off 1 1 – -
SH0.IOM1 ok off 1 1 – -
SH0.PWR0 ok – - 0 – -
SH0.PWR0 ok – - 0 – -
SH0.PWR1 ok – - 1 – -
SH0.PWR1 ok – - 1 – -
SH0.SAS0 ok – 0 0 24.00Gbps -
SH0.SAS0 ok – 0 0 24.00Gbps -
SH0.SAS1 ok – 0 1 0.00bps -
SH0.SAS1 ok – 0 1 0.00bps -
SH0.SAS2 ok – 0 2 24.00Gbps -
SH0.SAS2 ok – 0 2 24.00Gbps -
SH0.SAS3 ok – 1 3 24.00Gbps -
SH0.SAS3 ok – 1 3 24.00Gbps -
SH0.SAS4 ok – 1 4 0.00bps -
SH0.SAS4 ok – 1 4 0.00bps -
SH0.SAS5 ok – 1 5 24.00Gbps -
SH0.SAS5 ok – 1 5 24.00Gbps -
SH0.TMP0 ok – - 0 – 26C
SH0.TMP0 ok – - 0 – 26C
SH0.TMP1 ok – - 1 – 26C
SH0.TMP1 ok – - 1 – 26C
SH0.TMP2 ok – - 2 – 28C
SH0.TMP2 ok – - 2 – 29C
SH0.TMP3 ok – - 3 – 36C
SH0.TMP3 ok – - 3 – 37C
SH0.TMP4 ok – - 4 – 27C
SH0.TMP4 ok – - 4 – 27C
SH0.TMP5 ok – - 5 – 35C
SH0.TMP5 ok – - 5 – 35C
SH0.TMP6 ok – - 6 – 35C
SH0.TMP6 ok – - 6 – 38C
SH0.TMP7 ok – - 7 – 33C
SH0.TMP7 ok – - 7 – 34C

Create and Present 2 250GB Luns/Volumes to an existing Farm….

pureuser@SSD> purevol create –size 250G VDI5 VDI6
Name Size Serial
VDI5 250G E9AD1897B95AA49A00010008
VDI6 250G E9AD1897B95AA49A00010009
pureuser@SSD> purevol list
Name Size Serial
VDI1 250G E9AD1897B95AA49A00010004
VDI2 250G E9AD1897B95AA49A00010005
VDI3 250G E9AD1897B95AA49A00010006
VDI4 250G E9AD1897B95AA49A00010007
VDI5 250G E9AD1897B95AA49A00010008
VDI6 250G E9AD1897B95AA49A00010009
VMServer1 1T E9AD1897B95AA49A00010000
VMServer2 1T E9AD1897B95AA49A00010001
VMServer3 1T E9AD1897B95AA49A00010002
VMServer4 1T E9AD1897B95AA49A00010003

pureuser@SSD> purehgroup connect –vol VDI5 -Farm
Name Vol Lun
-Farm VDI5 18
pureuser@SSD>purehgroup connect –vol VDI6 -Farm
Name Vol Lun
-Farm VDI6 19

pureuser@SSD> purehgroup list –connect
Name Lun Vol
-Farm 10 VDI1
-Farm 11 VDI2
-Farm 12 VDI3
-Farm 13 VDI4
-Farm 14 VMServer1
-Farm 15 VMServer2
-Farm 16 VMServer3
-Farm 17 VMServer4
-Farm 18 VDI5
-Farm 19 VDI6

pureuser@SSD> purearray list –space
Name Capacity RAID-3D Shared Data Volume Data Total
SSD 10.25T 4.01G 3.96G 7.08G 15.05G

pureuser@SSD> purevol list –space
Name Size Data Reduction RAID-3D Volume Data Total
VDI1 250G 100.00% 0.00 0.00 0.00
VDI2 250G 100.00% 0.00 0.00 0.00
VDI3 250G 100.00% 0.00 0.00 0.00
VDI4 250G 100.00% 0.00 0.00 0.00
VDI5 250G 100.00% 0.00 0.00 0.00
VDI6 250G 100.00% 0.00 0.00 0.00
VMServer1 1T 98.38% 457.14M 1.56G 2.01G
VMServer2 1T 98.82% 423.40M 1.45G 1.86G
VMServer3 1T 97.58% 778.84M 2.66G 3.42G
VMServer4 1T 98.87% 412.47M 1.41G 1.81G
pureuser@SSD> purevol list –space VMServer1
Name Size Data Reduction RAID-3D Volume Data Total
VMServer1 1T 98.38% 457.14M 1.56G 2.01G

pureuser@SSD> purevol list –space VDI1
Name Size Data Reduction RAID-3D Volume Data Total
VDI1 250G 100.00% 0.00 0.00 0.00

As I get thru more I will share more..  all the best..

Been a bit since we last talked, I could make excuses but I won’t waste your eyes on that non-sense.  Anyways we have been upgrading all our HCS (HiCommand Suite) instances to the latest version 7.3.0, and I like to perform a manual export of the DB versus letting the upgrade tool perform that operation.  As always Murphy’s Law was waiting for me on the very last / hence most important one to crop his head up, attempting to export the DB and it kept bombing out on the replication manager tables.  I fussed with it and finally threw in the towel and buzzed my brother “Anil” our resident HiDRB expert, and we were able to solve the issue.  

We ended up exporting each product one at a time, and  then of course we had some corrupt tables in replication manager. Lucky for us we have a HA HCS system that mirrors this one so we were able to export those tables from that system and import them back to the system having the issue –  - and bazinga all is happy, full exports are now working.

Here is a cut-out of what we did:  Enjoy

Tuning Manager Export :-

=========================================

C:\Program Files (x86)\HiComman m(d\Base\bin>hcmdsdbmove.bat /export /datapath C:\temp /type TuningManager /auto

KAPM06523-I The hcmdsdbmove command has started.

KAPM06524-I Initialization for moving the database is being performed.

KAPM06902-I Processing to stop the service has started.

KAPM06906-I Processing to stop the DBMS has started.

KAPM06907-I The DBMS was stopped successfully.

KAPM06903-I The service was stopped successfully.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06525-I The data for TuningManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/207)

KAPM06537-I The data is being exported. (progress = 002/207)

KAPM06537-I The data is being exported. (progress = 206/207)

KAPM06537-I The data is being exported. (progress = 207/207)

KAPM06900-I Processing to start the service has started.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06901-I The service was started successfully.

KAPM06514-I Processing ended normally.

Device Manager Export :-

=========================================

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbmove.bat /export /datapath C:\temp /type DeviceManager /auto

KAPM06523-I The hcmdsdbmove command has started.

KAPM06524-I Initialization for moving the database is being performed.

KAPM06902-I Processing to stop the service has started.

KAPM06906-I Processing to stop the DBMS has started.

KAPM06907-I The DBMS was stopped successfully.

KAPM06903-I The service was stopped successfully.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06525-I The data for DeviceManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/390)

KAPM06537-I The data is being exported. (progress = 002/390)

KAPM06537-I The data is being exported. (progress = 389/390)

KAPM06537-I The data is being exported. (progress = 390/390)

KAPM06541-I The view is being exported.

KAPM06900-I Processing to start the service has started.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06901-I The service was started successfully.

KAPM06514-I Processing ended normally.

HBase Export :-

=========================================

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbmove.bat /export /datapath C:\temp /type HBase /auto

KAPM06523-I The hcmdsdbmove command has started.

KAPM06524-I Initialization for moving the database is being performed.

KAPM06902-I Processing to stop the service has started.

KAPM06906-I Processing to stop the DBMS has started.

KAPM06907-I The DBMS was stopped successfully.

KAPM06903-I The service was stopped successfully.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06525-I The data for HBase will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/220)

KAPM06537-I The data is being exported. (progress = 002/220)

KAPM06537-I The data is being exported. (progress = 219/220)

KAPM06537-I The data is being exported. (progress = 220/220)

KAPM06900-I Processing to start the service has started.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06901-I The service was started successfully.

KAPM06514-I Processing ended normally.

Replication Manager Export :- From other server with good tables

========================================

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbmove.bat /export /datapath C:\temp /type ReplicationManager /auto

KAPM06523-I The hcmdsdbmove command has started.

KAPM06524-I Initialization for moving the database is being performed.

KAPM06902-I Processing to stop the service has started.

KAPM06906-I Processing to stop the DBMS has started.

KAPM06907-I The DBMS was stopped successfully.

KAPM06903-I The service was stopped successfully.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06525-I The data for ReplicationManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/174)

KAPM06537-I The data is being exported. (progress = 002/174)

KAPM06537-I The data is being exported. (progress = 173/174)

KAPM06537-I The data is being exported. (progress = 174/174)

KAPM06541-I The view is being exported.

KAPM06900-I Processing to start the service has started.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06901-I The service was started successfully.

KAPM06514-I Processing ended normally.

Replication Manager Import some good tables

========================================

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbmove.bat /import /datapath C:\temp /type ReplicationManager /auto

KAPM06523-I The hcmdsdbmove command has started.

KAPM06524-I Initialization for moving the database is being performed.

KAPM06902-I Processing to stop the service has started.

KAPM06906-I Processing to stop the DBMS has started.

KAPM06907-I The DBMS was stopped successfully.

KAPM06903-I The service was stopped successfully.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06525-I The data for ReplicationManager will now be moved.

KAPM06531-I Processing to import data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being imported.

KAPM06537-I The data is being imported. (progress = 001/174)

KAPM06537-I The data is being imported. (progress = 002/174)

KAPM06537-I The data is being imported. (progress = 173/174)

KAPM06537-I The data is being imported. (progress = 174/174)

KAPM06541-I The view is being imported.

KAPM06900-I Processing to start the service has started.

KAPM06904-I Processing to start the DBMS has started.

KAPM06905-I The DBMS was started successfully.

KAPM06901-I The service was started successfully.

KAPM06514-I Processing ended normally.

Complete Export Logs :-

============================================================

C:\Program Files (x86)\HiCommand\Base\bin>hcmdsdbtrans.bat /export /workpath “c:\temp\wktrans” /file “c:\temp1\hcs-full-backup-08082012″

KAPM05900-I The hcmdsdbtrans command has started.

KAPM05930-I The Application data will now be exported.

KAPM06525-I The data for DeviceManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/390)

KAPM06537-I The data is being exported. (progress = 002/390)

KAPM06537-I The data is being exported. (progress = 389/390)

KAPM06537-I The data is being exported. (progress = 390/390)

KAPM06541-I The view is being exported.

KAPM06525-I The data for HBase will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/220)

KAPM06537-I The data is being exported. (progress = 002/220)

KAPM06537-I The data is being exported. (progress = 219/220)

KAPM06537-I The data is being exported. (progress = 220/220)

KAPM06525-I The data for ReplicationManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/174)

KAPM06537-I The data is being exported. (progress = 002/174)

KAPM06537-I The data is being exported. (progress = 173/174)

KAPM06537-I The data is being exported. (progress = 174/174)

KAPM06541-I The view is being exported.

KAPM06525-I The data for TieredStorageManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 01/32)

KAPM06537-I The data is being exported. (progress = 02/32)

KAPM06537-I The data is being exported. (progress = 31/32)

KAPM06537-I The data is being exported. (progress = 32/32)

KAPM06541-I The view is being exported.

KAPM06525-I The data for TuningManager will now be moved.

KAPM06531-I Processing to export data has started.

KAPM06532-I The table definitions of the database are being exported.

KAPM06533-I The data is being exported.

KAPM06537-I The data is being exported. (progress = 001/207)

KAPM06537-I The data is being exported. (progress = 002/207)

KAPM06537-I The data is being exported. (progress = 205/207)

KAPM06537-I The data is being exported. (progress = 206/207)

KAPM06537-I The data is being exported. (progress = 207/207)

KAPM05931-I The Application data has been exported.

KAPM05930-I The Authentication data will now be exported.

KAPM05821-I Processing to export data has started.

KAPM05822-I Processing to export data has ended.

KAPM05931-I The Authentication data has been exported.

KAPM05933-I The archive file will now be created.

KAPM05934-I The archive file has been created.

KAPM05901-I The hcmdsdbtrans command ended normally.

Hope this helps you when your in a pinch like this one.  Again thanks to my Bro Anil for pulling me out of the fire…  Cheers!!

Its been awhile since I posted, but day job has been cranking lately.  I felt this one was worthy of a post, in a previous post I discussed Raidcom commands that could be useful to everyone out there.  Well our friends at HDS have updated the CCI and VSP code to allow end to end provisioning on the VSP – Freakin sweet no more GUI .  My Collegues and I have created a script to perform VSP provisioning but since everyone has there own view on the best scripting languages I will leave the scripts for you to determine what your favorite one is. In place of the script I will give you the appropriate commands to run.

Enjoy and let me know if this has helped you!!!

Create a HORCM file and place it in the proper location c:\windows or whatever os requires

HORCM

#
#/************************* For HORCM_MON *************************************/

HORCM_MON
#ip_address        service         poll(10ms)     timeout(10ms)
10.0.0.1       horcm99         1000              3000

#/************************** For HORCM_CMD ************************************/

HORCM_CMD
#dev_name                dev_name                dev_name
#For IP command device svp is the ip the -31001 is the fixed port for virtual command device
\\.\IPCMD-10.0.0.2-31001
 

#/************************** For HORCM_LDEV ***********************************/

HORCM_LDEV
#dev_group        dev_name        Serial#   CU:LDEV(LDEV#)   MU#
#VG01              oradb3          11112     01:04              0

#/************************* For HORCM_INST ************************************/

HORCM_INST
#dev_group        ip_address      service
#VG01              10.0.0.1    horcm99
C:\>set HORCMINST=99

C:\>horcmstart 99
starting HORCM inst 99
HORCM inst 99 starts successfully.

C:\>raidcom -login maintenance raid-mainte

Host Group Creation / WWN Nickname

• raidcom add host_grp -port CL2-E-1 -host_grp_name test-it
• raidcom add host_grp -port CL1-E-1 -host_grp_name test-it
• raidcom modify host_grp -port CL1-E-1 -host_mode 3 -host_mode_opt 12 40 (HPUX and proper modes)
• raidcom modify host_grp -port CL2-E-1 -host_mode 3 -host_mode_opt 12 40
• raidcom add hba_wwn -port CL1-E-1 -hba_wwn 10000000c9537bb2
• raidcom add hba_wwn -port CL2-E-1 -hba_wwn 10000000c9537d06
• raidcom set hba_wwn -port CL1-E-1 -hba_wwn 10000000c9537bb2 -wwn_nickname testhpux1
• raidcom set hba_wwn -port CL2-E-1 -hba_wwn 10000000c9537d06 -wwn_nickname testhpux1

Create Ldevs and assign to proper CU and Pool

Create an ldev in HDT Pool 0, ldev=00:40:00 , capacity=30GB in blocks

• raidcom add ldev -pool_id 0 -ldev_id 0×4000 -capacity 62914560

Create an ldev in HDT Pool 0, ldev=00:46:47 , capacity=300GB in blocks

• raidcom add ldev -pool_id 0 -ldev_id 0×4647 -capacity 629145600

Add an ldev to a hostgroup

• raidcom add lun -port CL1-E-1 -lun_id 0003 -ldev_id 0×4647
• raidcom add lun -port CL2-E-1 -lun_id 0003 -ldev_id 0×4647

 C:\>raidcom -logout

 C:\>hormcshutdown 99

Enjoy….  http://www.symantec.com/business/theme.jsp?themeid=netbackup-guy

audpoptimize  -unit AMS001 -start -lu 3  -priority host (This will optimize lun # 3 and run it with the priority that runs slower to not impact host i/o)

audpoptimize  -unit AMS001 -start -lu 3-8  -priority host (This will optimize lun # 3-8 and run it with the priority that runs slower to not impact host i/o)

Hope this helps someone especially my lazy colleague….