Sample Banner Messages Most Used in Corporate Companies

Sample#1
Warning!!!! This is a Critical Production SAN Switch.  Do not log in unless it is in conjunction with an APPROVED CHANGE REQUEST


Sample#2
Warning!!!! This is Critical PROD SAN Switch Do not log into this switch if you are not an authorized administrator.



I Will be Keep Post More here Soon. Any Knowledge Sharing would be more appreciated.

[SOLVED] Change Auditor error connecting to the Coordinator service Issue

Error Message: There was an error connecting to the Coordinator service. Check the App_Data/ChangeAuditorWeb.nptlog for errors.

Issue: Change Auditor Web Client displays "There was an error connecting to the Coordinator service. Check the App_Data/ChangeAuditorWeb.nptlog for errors." after Change Auditor Coordinator is restarted.

Cause: the Change Auditor Coordinator service is restarted or some X reason.

Fix:

Update the correct Change Auditor Client Port in "web.config" file

File Location: <Drive:>\Program Files\Dell\ChangeAuditor\WebClient\Web.config

Entry to update: <add key="Coordinator" value="<Coordinator_server>:port"/>

Where

<Coordinator_server>  - Change Auditor Coordinator Server Name

Port: The Change Auditor Coordinator "Client SCP Port" can be viewed in the Change Auditor Coordinator Status.

Note: Reply to the post, if you need any further assistant.

HP EVA - Error 106: Service obligation expired.

Issue: when you are unable to Open the HP EVA Command View Web Console
Where to check first ?
1. Open the Managemet server CMD Line, run the below cmd to check the director services
C:>desta status
Checking for DESTA director with PID 5016
The Director process is running.
If it is running then fine, or else start the desta service using below CMD
C:>desta start
Still Web Console is not Working...!
Open System Event Analyzer

If it is showing below error message in the System Event Analyzer, that means you need the Change the Service obligation start & End Time

Service Obligation:	Expired
Service Obligation Number:	silent
System Serial Number:	silent
Service Provider Company Name:	Hewlett-Packard Company

 

Obligation Start Date:	Thu May 15 13:54:17 EDT 2014
Obligation Ending Date:	Fri May 15 13:54:17 EDT 2015
Time left on Obligation:	0 years, 0 days, 0 hours, 0 minutes, 0 seconds

History of changes:
Thu May 15 13:54:19 EDT 2014: Installer (unknown) of Hewlett-Packard Company
    Installation settings changed to start Thu May 15 13:54:17 EDT 2014 to Fri May 15 13:54:17 EDT 2015 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)

1. Wed Apr 24 08:24:30 EDT 2013: Installer (unknown) of Hewlett-Packard Company
       Installation settings changed to start Wed Apr 24 08:24:27 EDT 2013 to Thu Apr 24 08:24:27 EDT 2014 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
2. Wed May 23 08:21:01 EDT 2012: Installer (unknown) of Hewlett-Packard Company
       Installation settings changed to start Wed May 23 08:20:59 EDT 2012 to Thu May 23 08:20:59 EDT 2013 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
3. Thu Aug 11 10:22:44 EDT 2011: Installer (unknown) of Hewlett-Packard Company
       Installation settings changed to start Thu Aug 11 10:22:44 EDT 2011 to Fri Aug 10 10:22:44 EDT 2012 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)

You can check the Same from CMD Line

C:>wsea status
  Service Obligation:            Expired
  Service Obligation Number:     silent
  System Serial Number:          silent
  Service Provider Company Name: Hewlett-Packard Company
Obligation Start Date:         Thu May 15 13:54:17 EDT 2014
Obligation Ending Date:        Fri May 15 13:54:17 EDT 2015
Time left on Obligation:       0 years, 0 days, 0 hours, 0 minutes, 0 seconds
History of changes:
Thu May 15 13:54:19 EDT 2014: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Thu May 15 13:54:17 EDT 2014 to Fri May
 15 13:54:17 EDT 2015 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Wed Apr 24 08:24:30 EDT 2013: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Wed Apr 24 08:24:27 EDT 2013 to Thu Apr
 24 08:24:27 EDT 2014 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Wed May 23 08:21:01 EDT 2012: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Wed May 23 08:20:59 EDT 2012 to Thu May
 23 08:20:59 EDT 2013 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Thu Aug 11 10:22:44 EDT 2011: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Thu Aug 11 10:22:44 EDT 2011 to Fri Aug
 10 10:22:44 EDT 2012 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)

Notifications to be sent
Error 106: Service obligation expired.


Fix:
C:>desta servob change
WEBES Obligation Change
-----------------------
Service Obligation change date:        Thu May 15 13:54:19 EDT 2014
Service Obligation current state:      Expired
Service Obligation current start date: Thu May 15 13:54:17 EDT 2014
Service Provider Company Name:  <U'r Company Name>
Service Provider Employee Name: <Name>
Service Provider Employee ID#:  <xxxx>
Please enter new service obligation start date <MMM d, yyyy>[Jun 28, 2016]: Jun
28, 2016
Please enter service obligation term end date <MMM d, yyyy>[Jun 28, 2017]: Jun 2
8, 2017
Service Obligation term: 1 years, 0 days, 0 hours, 0 minutes, 0 seconds
Is this correct [y]: y
Current Obligation Settings:
  Service Obligation:            Valid
  Service Obligation Number:     silent
  System Serial Number:          silent
  Service Provider Company Name: Hewlett-Packard Company
Obligation Start Date:         Tue Jun 28 00:00:00 EDT 2016
Obligation Ending Date:        Wed Jun 28 00:00:00 EDT 2017
Time left on Obligation:       0 years, 364 days, 9 hours, 43 minutes, 4 seconds
History of changes:
Tue Jun 28 14:16:55 EDT 2016: user (12345) of company
  Obligation settings changed to start Tue Jun 28 00:00:00 EDT 2016 to Wed Jun 2
8 00:00:00 EDT 2017 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Thu May 15 13:54:19 EDT 2014: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Thu May 15 13:54:17 EDT 2014 to Fri May
 15 13:54:17 EDT 2015 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Wed Apr 24 08:24:30 EDT 2013: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Wed Apr 24 08:24:27 EDT 2013 to Thu Apr
 24 08:24:27 EDT 2014 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Wed May 23 08:21:01 EDT 2012: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Wed May 23 08:20:59 EDT 2012 to Thu May
 23 08:20:59 EDT 2013 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Thu Aug 11 10:22:44 EDT 2011: Installer (unknown) of Hewlett-Packard Company
  Installation settings changed to start Thu Aug 11 10:22:44 EDT 2011 to Fri Aug
 10 10:22:44 EDT 2012 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds)
Notifications to be sent
0 years, 60 days, 0 hours, 0 minutes, 0 seconds
0 years, 30 days, 0 hours, 0 minutes, 0 seconds
0 years, 15 days, 0 hours, 0 minutes, 0 seconds
0 years, 5 days, 0 hours, 0 minutes, 0 seconds
0 years, 4 days, 0 hours, 0 minutes, 0 seconds
0 years, 3 days, 0 hours, 0 minutes, 0 seconds
0 years, 2 days, 0 hours, 0 minutes, 0 seconds
0 years, 1 days, 0 hours, 0 minutes, 0 seconds


Now Check the Status again
C:>wsea status
System Event Analyzer for Windows V6.2 (Build 157)
Service Tools Home: C:\Program Files\HP\svctools
Service Obligation Start Date: Tue Jun 28 00:00:00 EDT 2016
Service Obligation End Date:   Wed Jun 28 00:00:00 EDT 2017
HPSIM notification: enabled.
ISEE notification: enabled.
SMTP notification: enabled.
DTCS notification: enabled.
MOM notification: enabled.
SNMP notification: enabled.
LOG notification: enabled.
INDICTMENT notification: enabled.
EVT notification: enabled.
VMSMAIL notification: disabled.
Restart the Mgmt Server and Check the web console is working or Not
Let me know if you still face the Issue.

RecoverPoint 4.x Cluster Configuration backup process

How to Backup RecoverPoint 4.x configuration backup


Step1: login to the cluster with cluster ip using putty with adinm credentials
Step2: In Putty make sure, you are logginf putty session output to a text file

Step3: Run the CMD "save_settings" & Quit the session.....Done


ClusterName> save
save_security_settings  save_settings
ClusterName> save_settings
Save in Windows format: (Default: no)
1) yes
2) no
Select, or press 'ENTER' 1

java failed to validate certificate. the application will not be executed

Issue: java failed to validate certificate. the application will not be executed

Resolution:
go to >> Java Control Panel >> Advanced >> 'Perform signed code certification revocation check on'
under that select "Do not check (not recommended)"

Click ok & Refresh the browser. :)

CMD in SRDF to set Link Limbo

Why we need to set Link Limbo value (0-120 Sec)?
link limbo is a feature, that allows you to set a specific length of time for Enginuity to wait, when the data link is down before updating the link status. If the link status is still Not Ready after the link limbo time expires, devices are marked Not Ready to the link.
If it is not set & the data link is flapped for some time, then the SRDF Replication will move the replication from SyncInProg to suspended mode. Then we have to establish the replication manually.

CMD>> symrdf -sid <SymmID> -rdfg <RDFGroupNumber> set link_limbo 120

WARNING: RPA fan failure detected. Contact EMC Customer Service

Issue: WARNING: RPA fan failure detected. Contact EMC Customer Service

Resolution:
1. Set the RPA Cluster to Maintenance Mode

> login to the Cluster using admin credential using tool like putty (default admin/admin)

> enter the cmd for enter into maintenance mode

RPACluster> start_maintenance_mode

Enter the kind of upgrade.

1) major_upgrade

2) minor_upgrade

3) rpa_addition

4) rpa_replacement

5) rpse_conversion

6) system_modification

7) user_initiated

8) connect_cluster

Select: 6

Enter cluster name

RPACluster

Switched to maintenance mode successfully.

2. Reboot the Respective RPA node (in this case i am rebooting RPA Node 5)

> login to the RPA Node using boxmgmt credential (Default Credential: boxmgmt/boxmgmt)

** Main Menu **

[1] Installation

[2] Setup

[3] Diagnostics

[4] Cluster operations

[5] Shutdown / Reboot operations

[Q] Quit

RPACluster RPA 5: 5

** Shutdown / Reboot operations **

[1] Reboot RPA

[2] Shutdown RPA

[M] Main Menu

[B] Back

[Q] Quit

RPACluster RPA 5: 1

Reboot in progress, please wait.

3. After reboot, check the error message is gone.

If note please follow the below steps

1. Shut down the RPA
2. Remove the power cord from the power supply unit of the affected RPA (disconnect the cord from the PSU or unplug it from the wall)
3. Wait for 10 seconds and reinsert the power cord and boot the RPA.
4. Monitor the environment (RPA and site power).

4. finally release the cluster from Maintenance Mode

RPACluster > finish_maintenance_mode

Enter cluster name, or press 'ENTER' for all clusters

RPACluster 

Maintenance mode finished successfully.

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>>