Linux: How to check CPU Count & Memory

// memory Utilization
[root@host ~]# free -m
             total       used       free     shared    buffers     cached
Mem:        258294       2802     255492          0        187        735
-/+ buffers/cache:       1879     256414
Swap:        16499          0      16499

// CPU Processor Count
[root@ahost ~]# nproc
32
(if the above didn't work, try the below 2 cmds for CPU Count & no of Cores)
[root@host ~]# grep -c processor /proc/cpuinfo
8
[root@host ~]# grep "cpu cores" /proc/cpuinfo |sort -u |cut -d":" -f2 | awk '{s+=$1} END {print s}'
4
// the below cmd give detail CPU info
>>less /proc/cpuinfo

Sym Authorization Check


1. symcli cmd to check the list of users and their access

D:\Program Files (x86)\EMC\SYMCLI\bin>symauth -sid <SymmID> -users list

   S Y M M E T R I X   A U T H O R I Z A T I O N   U S E R S

Symmetrix ID: 000XXXXXXXXX

                                                                           Flags
Role              User/Group name                Component                   E
---------------   -----------------------------  ------------------------- -----
Admin             User  D:Domain1\User 1           N/A                         .
Admin             User  D:Domain2\User2          N/A                    


2. How to add user in symcli.

   .D:\Program Files (x86)\EMC\SYMCLI\bin>symauth -sid <SymmID> -f c:/access.txt commit -nop

access.txt
assign user D:Domain1\User1 to role admin;
(or for group)
assign group D:Domain1\User1 to role admin;

3. How to remove User Access using symcli

   .D:\Program Files (x86)\EMC\SYMCLI\bin>symauth -sid <SymmID> -f c:/access.txt commit -nop

access.txt
delete User/Group D:Domain1\User1;

D:Domain1\User1 - you actually cross verify the user name as it in box, using CMD symauth -sid <SymmID> -users list

How to run EMC grabs on Linux machine

Step 1: Download the EMCGrab File from the Below FTP Link

ftp://ftp.emc.com/pub/emcgrab/Unix/emcgrab_Linux_v4.7.3.tar
or browse the below for respective OS
ftp://ftp.emc.com/pub/emcgrab/Unix/

Step 2: Upload the fail to the root of the host

Step 3: unzip the file on the host

CLI:
root@hostname ~] # cd /usr
root@hostname usr] # tar xvf /root/emcgrab_Linux_v4.7.3.tar (or else give the file path where you uploaded the .tar file instead of /root/emcgrab_Linux_v4.7.3.tar)
root@hostname usr] # mv /usr/emcgrab /usr/emc
root@hostname usr] # cd /usr/emc
root@hostname emc] # ./emcgrab.sh
DO YOU AGREE TO ACCEPT THE TERMS & CONDITIONS OF THIS LEGAL AGREEMENT (Y/N): Y
 EMC GRAB IDENTIFICATION INFORMATION
 -----------------------------------
 1) Service Request Number:              No Information Supplied

 2) Customer Party Number:

 3) Customer Company Name:
 4) Customer Contact Name:
 5) Customer Phone Number:
 6) Customer Email Address:

 Hostname / OS Info:                  hostname / Linux

Is the EMC Grab Identification Information Correct (Y/N)        :
Y

Do you want to collect SMI-S information (y/n) ? n
Do you want to collect XtremIO Array information (y/n) ? n
Please submit this file to EMC for Analysis.  Thank you
Removing Temporary Files....

Step 4: check the file is generated
root@hostname emc] # cd /usr/emc/outputs
root@hostname outputs] #ls   (Check file is generated)
HostName_2016-04-14-21.53.32_Linux_emcgrab_V4.7.3_full_CC0000000000.tar.gz

Step 5: Open WinSCP Tool and login in the host and download the file from path: /usr/emc/outputs/HostName_TimeStamp_Linux_emcgrab_V4.7.3_full_CC0000000000.tar.gz


Let me know if you face Any Issues

CleanUP:
As the root user on <<emc install node>> do the following.

# cd /root
# rm <<emc storage rpm>>
# rm license.txt
# rm <<emc grab tar file>>


How to Remove EVA Node from Command View


Step1: Remove the EVA node name folder from Cache Folder
Path: C:\Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\cache

Step2: restart the Command View service
>> Open run and run 'services.msc'
restart the service >> HP Command View EVA

Step3: Completed
//Open command view and see, if its not removed, run discover

unable to distribute ISO file. RPA already contains another ISO file, please contact customer support

Issue: unable to distribute ISO file. RPA already contains another ISO file, please contact customer support.


Resolution: Clear the image file on each RPA using boxmgmt Account
















































Go back to deployment manager
And click on retry



















Repeat the process for all other RP’s

Script#
NzUyZWZhNDAyNTdiYTJhMmMyODgxYjcxN2UxOTVhNjcKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk
ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjI0NjU4ClJlbW92ZSBJU08gZmlsZXMKQnJpYW4KIyEv
YmluL3NoIAojSVNPIFNjcmlwdAojUmVtb3ZlcyBJU08gZmlsZXMKcm0gL2hvbWUva29zL2lzby8q
Lmlzbwo=
#

Warning: There is a clock difference between RP clusters. It is highly recommended to synchronize clocks either manually or by configuring an NTP server

Warning Message: There is a clock difference between RP clusters. It is highly recommended to synchronize clocks either manually or by configuring an NTP server

Cause: poor communication with NTP Server or NTP Server not reachable

How to Check/ Verify:
>Login into RPA Cluster via SSH (putty)
>run the current time cmd as shown below
RPClusterName> get_current_time
Thu Feb 11 18:53:09 2016 (America/New_York)
>verify the current time in google for the location/ site or current time on your laptop.

Fix:
>Open RecoverPoint Deployment Manger
>select 'modify cluster'
>Provide the cluster ip & boxmgmt & admin credential.
>after cluster information is retrieved, change the NTP Server IP with New NTP Server IP.
(get NTP Server IP from your Network Team)
> Click Next & Finish
> wait 10 mins and see if the error msg is gone or not











Done Done

HPEVA - DESTA - Database files growing out of control

HPEVA - DESTA - Database files growing out of control 

Best way to free up the space is, reset the Desta Database

// use below cmd to reset the desta database

desta exec com.compaq.svctools.desta.services.database.ManagePostgreSQL -initdb 

Service-now difference between Assignment group & Work Group

Service-now difference between Assignment group & Work Group


Assignment Group 
Work Group 
Used to organize tickets to be addressed by support personnel
Used to organize support personnel within the organization
Support personnel can belong to more than one Assignment Group
Support personnel can belong to only one Work Group
Upon resolution the Assignment Group of the resolver/fulfiller gets associated with the ticket
Work Groups are associated to the resolver/fulfiller
The Assignment Group associated with the ticket will remain unchanged even when the resolver/fulfiller is no longer a member
As support personnel move from one Work Group to another, the tickets they resolved/fulfilled follow them

Most Usefull ESXi Cmds


Some Most Useful CMDs in Esxi

// list the UUID & VMFS Cable , Snapshot information
esxcfg-volume -l
// Parsistency Mount devices (open ssh into esxi host & run the below cmd for preexistence Mount)
esxcfg-volume -M vmfs_Label
//snapshot list
esxcli storage vmfs snapshot list
// hostd Service restart
/etc/init.d/hostd stop
/etc/init.d/hostd start
/etc/init.d/hostd status

DCNM (Cisco Data Center Network Manager) Admin Password Reset from CLI


DCNM (Cisco Data Center Network Manager) Password Reset from CLI

Recently when i install the DCNM for the first time.
it asked me for DB Password but not the admin password.
i tried logging into GUI using admin default credential, but it didn't work.
Below is the process to reset admin password from root

Login into server via putty
[root@HostName ~]# cd /usr/local/cisco/dcm/fm/bin
[root@HostName bin]# ./addUser.sh  admin NewPassword DBPassword
Server configuration file loaded: /usr/local/cisco/dcm/fm//conf/server.properties
log4j:WARN No appenders could be found for logger (fms.db).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Log4j loaded: /usr/local/cisco/dcm/fm//conf/log4j_fms.xml
Password validation is finished!
Added user : admin successful!

Default root credential: root/root
Default admin Credential: admin/admin