Author Archives: admin

After upgrading VNX OE Code SMI-S (ECOM) Provider is reporting wrong code version

I discovered this issue a couple of weeks ago.

I had to upgrade a VNX System from VNX OE code release 05.33.000.5.081 to 05.33.006.5.102.

After the successful upgrade i saw that the SMI-S Provider (ECOM) hadn’t picked up the new code level.

The program to test and validate SMI-S Provider Functionality is called testsmisprovider.exe. In my case
it is located on a Management Server in “D:\Program Files\EMC\ECIM\ECOM\bin\TestSmiProvider.exe”.

To retrieve the information from the VNX you have to run the following commands:

1. Run TestSmiProvider from the Command Line:

D:\Program Files\EMC\ECIM\ECOM\bin>TestSmiProvider.exe
 Connection Type (ssl,no_ssl,native) [no_ssl]:
 Host [localhost]:
 Port [5988]:
 Username [admin]:
 Password [xxxxx]:
 Log output to console [y|n (default y)]:
 Log output to file [y|n (default y)]:
 Logfile path [Testsmiprovider.log]:
 Connecting to localhost:5988
 Using user account 'admin' with password 'xxxxx'

Enter “dv”

(localhost:5988) ? dv
 ++++ Display version information ++++
 CIM ObjectManager Name: EMC:xx.xx.xx.xx
 CIMOM Version: EMC CIM Server Version 2.7.3.3.0.8
 SMI-S qualified version: 1.5.0
 SMI-S Provider version: V4.6.2.3
 SMI-S Provider Location: Proxy
 SMI-S Provider Server:
 Windows_NT MBCI0EMS2001 6.2.9200  x86_64 VM Guest OS (64bit Libraries)
 Solutions Enabler version: V7.6-1808 2.8
 Firmware version information:
 (Remote) CLARiiON Array CKM00xxxxxxx (Rack Mounted VNX5600) : 05.33.000.5.081
 Retrieve and Display data - 1 Iteration(s) In 0.093748 Seconds

The command returns the Firmware version information:

 (Remote) CLARiiON Array CKM00xxxxxxxxx (Rack Mounted VNX5600) : 05.33.000.5.081

Now this was still the old Code Level that was returned by SMI-S.
To refresh the system information i ran “refsys”

(localhost:5988) ? refsys
Refresh Systems {y|n} [n]: y
Refresh all systems {y|n} [n]: y
Sync ALL components {y|n} [n]: y
++++ EMCRefreshSystem ++++
EMCRefreshSystem - iteration 1
OUTPUT : 0
Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed
5=Invalid Parameter
4096=Job Queued, 4097=Size Not Supported
Note: Not all above values apply to all methods - see MOF for the method.
In 11.140637 Seconds
Please press enter key to continue...

But even after that the version number was still wrong.
Now, the “quick and dirty” way to fix is: remove the VNX system from the SMI-S config and add it back in.

Here is how you do it:

Run “ein” Get the Instance Name from the configured VNX system:

(localhost:5988) ? ein
 Class: Clar_StorageSystem
 ++++ Testing EnumerationInstanceNames: Clar_StorageSystem ++++
 Instance 0:
 Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+CKM00xxxxxxxxx"
 Enumerate 1 instance names; repeat count 1;return data in 0 seconds
 Retrieve and Display data - 1 Iteration(s) In 0.015627 Seconds
 Please press enter key to continue...

Copy the String after “Instance 0″ to your clipboard:

Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+CKM00xxxxxxxxx"

Run “remsys” to remove the VNX system from the SMI-S config.
The “System’s ObjectPath[null]” is the Instance name that you got from running the “ein” command:

(localhost:5988) ? remsys
 remove System {y|n} [n]: y
 System's ObjectPath[null]: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+CKM00xxxxxxxxx"
About to delete system Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+CKM00xxxxxxxxx"
Are you sure {y|n} [n]: y
++++ EMCRemoveSystem ++++
 OUTPUT : 0
 Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed
 5=Invalid Parameter
 4096=Job Queued, 4097=Size Not Supported
 Note: Not all above values apply to all methods - see MOF for the method.
 In 5.078127 Seconds
Please press enter key to continue...

Run “dv” to see that the system is removed from the SMI-S config:

(localhost:5988) ? dv
 ++++ Display version information ++++
 CIM ObjectManager Name: EMC:xx.xx.xx.xx
 CIMOM Version: EMC CIM Server Version 2.7.3.3.0.8
 SMI-S qualified version: 1.5.0
 SMI-S Provider version: V4.6.2.3
 SMI-S Provider Location: Proxy
 SMI-S Provider Server:
 Windows_NT MBCI0EMS2001 6.2.9200  x86_64 VM Guest OS (64bit Libraries)
Solutions Enabler version: V7.6-1808 2.8
Retrieve and Display data - 1 Iteration(s) In 0.078114 Seconds
Please press enter key to continue...

Add the system back into the SMI-S config.

You have to specify the ArrayType (1 for Clariion/VNX), SP IPs, username and password:

(localhost:5988) ? addsys
 Add System {y|n} [n]: y
 ArrayType (1=Clar, 2=Symm) [1]: 1
 One or more IP address or Hostname or Array ID
 Elements for Addresses
 IP address or hostname or array id 0 (blank to quit): xx.xx.xx.xx
 IP address or hostname or array id 1 (blank to quit):
 Address types corresponding to addresses specified above.
 (1=URL, 2=IP/Nodename, 3=Array ID)
 Address Type (0) [default=2]: 2
 Find peer IP addresses if only one supplied {y|n} [n]: y
 User [null]: xxxxx
 Password [null]: xxxxx
 ++++ EMCAddSystem ++++
 OUTPUT : 0
 Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed
 5=Invalid Parameter
 4096=Job Queued, 4097=Size Not Supported
 Note: Not all above values apply to all methods - see MOF for the method.
 System : //xx.xx.xx.xx/root/emc:Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+CKM00xxxxxxxxx"
 In 16.937526 Seconds

Run “dv” again:

(localhost:5988) ? dv
 ++++ Display version information ++++
 CIM ObjectManager Name: EMC:xx.xx.xx.xx
 CIMOM Version: EMC CIM Server Version 2.7.3.3.0.8
 SMI-S qualified version: 1.5.0
 SMI-S Provider version: V4.6.2.3
 SMI-S Provider Location: Proxy
 SMI-S Provider Server:
 Windows_NT MBCI0EMS2001 6.2.9200  x86_64 VM Guest OS (64bit Libraries)
 Solutions Enabler version: V7.6-1808 2.8
 Firmware version information:
 (Remote) CLARiiON Array CKM00xxxxxxxxx (Rack Mounted VNX5600) : 05.33.006.5.102
 Retrieve and Display data - 1 Iteration(s) In 0.093748 Seconds
Please press enter key to continue...

You should now see the “updated” Code Level /Firmware.

 

 

TwitterLinkedInXINGStumbleUpon

VNX CLI commands

This is a collection of useful naviseccli commands. It is expanded continuously…

Add Host to Storagegroup:

naviseccli -h <SPA IP> -user <username> -password <password> -scope 0 storagegroup -connecthost -host <host name> -gname <group name>

Add LUN to Storagegroup:

naviseccli -h <SPA IP> -user <username> -password <password> -scope 0 storagegroup -addhlu -gname <group name> -hlu <host lun id> -alu <array lun id>

Register Host initiator:

naviseccli -h <SPA IP> -user <username> -password <password> -scope 0  storagegroup -setpath -gname <group name> -hbauid <hba uid>  -host <host name -sp <a or b> -spport <sp port number> -ip <host ip> -failovermode <4 for clariion/vnx> -o

Change LUN name:

naviseccli -h <SPA IP> -user <username> -password <password> -scope 0 chglun -l <lun id> -name <new lun name>

Deregister hosts

naviseccli -h <SPA IP> -user <username> -password <password> -scope 0 port -o -removehba -hbauid <hba uid>
TwitterLinkedInXINGStumbleUpon

Cisco MDS Zoning Mini Howto

Here is a quick’n dirty Cisco MDS Zoning Howto

– collect WWPNs

show flogi database

add interface to VSAN:

conf t
vsan database
vsan 10
vsan 10 interface fc2/1

check configuration change:

sh vsan 10 membership

create fcalias with VSAN 10:

conf t
fcalias name xxxxx_v0 vsan 10
member pwwn <pwwn>

– create zone (initiator/target) in vsan 10

zone name xxxxx_v0-xxxx vsan 10
 member fcalias
 member fcalias

– add zone to active zoneset in vsan 10

zoneset name VSAN-DIC-A_zs vsan 10
member xxxxx

apply config change and activate:

zone commit vsan 10

save config to startup-config

copy running-config startup-config
TwitterLinkedInXINGStumbleUpon

Powerpath vAPP 1.2 P05 “/etc/hosts” file is reset on every reboot

Today i found a strange behaviour on a freshly deployed Powerpath vAPP.

Because the customer DNS server wasn’t ready at the time of the deployment, i had to use the local “/etc/hosts” file.

I opened the /etc/hosts file with my editor of choice and added the lines for all ESXi servers + the vCenter itself.
The reason for that is that if the Powerpath vAPP can’t resolve the names of the ESXi servers that have to be licensed, the ESXi servers show as unlicensed in the GUI.

vapp:~ # vi /etc/hosts
127.0.0.1     localhost.localdom      localhost      
localhost.localdom      localhost
#ESXi and vCenter
10.77.77.20        vcenter vcenter.localdom.local
10.77.77.25         esx001  esx001.localdom.local
10.77.77.26         esx002  esx002.localdom.local
10.77.77.27         esx003  esx003.localdom.local
10.77.77.28         esx004  esx004.localdom.local
10.77.77.29         esx005  esx005.localdom.local
10.77.77.30         esx006  esx006.localdom.local

 

After rebooting the vAPP appliance, the “/etc/hosts” file is automically reset to default

vapp:~ # vi /etc/hosts
 127.0.0.1     localhost.localdom      localhost
 localhost.localdom      localhost

 

Now this happens because the Powerpath vAPP is deployed as a Virtual Appliance, and this has an in‐guest management component called Virtual Appliance Management Infrastructure (VAMI).

VAMI places a lot of scripts in the vAPP located in the following directory:

#/opt/vmware/etc/isv

The script that is responsible for rewriting the hosts file is called

#subsequentboot

 

To prevent VAMI from resetting the host file:

– Open vi with the file “subsequentboot”

localhost:/ # vi /opt/vmware/etc/isv/subsequentboot

– Comment the following 2 lines in line 23/24:

#echo "127.0.0.1     localhost.localdom      localhost"  >       /etc/hosts
#echo "$HOSTADDR     $FQDNADDR      $SHORTHNAME"         >>      /etc/hosts

 

Edit the “/etc/hosts” file again and reboot…
Voilá…”/etc/hosts” file should still have all the entries that you put in

 

 

TwitterLinkedInXINGStumbleUpon