Infra World: February 2016

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

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