> To see Pool Capacity
naviseccli -h IP storagepool -list -tiers
> FAST VP AutoTier operation status/details
naviseccli -h ip autotiering -info -opstatus
Wednesday, December 24, 2014
Wednesday, September 10, 2014
Requirements ESRS IP Client:
Requirements ESRS IP Client:
1. Dedicated VM with Windows 2003/08 server
2. A Static IP network with Internet connectivity
3. Network connectivity between the servers and EMC devices to be managed by ESRS IP
4. Internet connectivity to EMC’s ESRS infrastructure by using outbound port 80, 443 and 8443
5. VC++, .Net Framework (min 2.0)
6. Port number 25 needs to be open from ESRS IP Client machine to SMTP Server
1. Dedicated VM with Windows 2003/08 server
2. A Static IP network with Internet connectivity
3. Network connectivity between the servers and EMC devices to be managed by ESRS IP
4. Internet connectivity to EMC’s ESRS infrastructure by using outbound port 80, 443 and 8443
5. VC++, .Net Framework (min 2.0)
6. Port number 25 needs to be open from ESRS IP Client machine to SMTP Server
Thursday, April 17, 2014
EMC Powerpath
• powermt check ( – select option –a ) ( This is needed when you reboot the server Mostly for patching do – Disk Management Rescan and run the command to clear dead paths )
• powermt update lun_names ( This is needed when LUN names is to be updated and you have to update in the system to refresh same)
Friday, March 28, 2014
Reconfiguring Storage Processor (SP) IP address using Navisphere Manager
Reference
Reconfiguring Storage Processor (SP) IP address using Navisphere Manager
CLARiiON
CX Series,CLARiiON iSCSI Array.
Description:
Procedure
to reconfigure SP IP address using Navisphere Manager.
Resolution:
The storage processor (SP) IP address can only be set through the /setup page. Please follow the steps give
below.
If this procedure is done with active hosts attached to the array,
ensure that there are no single HBA-attached hosts and that failover software
is configured on each multi HBA attached host. SPs will reboot each time the IP
address change is submitted. Wait to change the other SP's IP
address until the first SP has rebooted.
1.
If
the storage system to be reconfigured is the domain master, select a new domain
master before proceeding.
2.
Make
sure both SPs for which you want to change IP addresses are connected to the
network
3.
If
the array on which you want to set or cannot set the IP address ("problem
array") is in a domain with other arrays, open Navisphere Manager on one
of the other arrays and remove it from the domain using the Configure Domain
dialog.
4.
Open
the setup page for SP A <SP
A IP address/setup> on the array.
5.
Reset
security and domain information for SP-A by pressing the "Reset
Security" button. Select "Yes" and "Submit" to
confirm.
6.
Re-open
the setup page for SP A on the array and restart the Management Server by
pressing the "Restart Management Server" button. Select
"Yes" and "Submit" to confirm.
7.
Open
the setup page for SP B <SP
B IP address/setup> on the array.
8.
Reset
security and domain information for SP B by pressing the "Reset
Security" button. Select "Yes" and "Submit" to
confirm.
9.
Re-open
the setup page for SP B on the array and restart the Management Server by
pressing the "Restart Management Server" button. Select
"Yes" and "Submit" to confirm.
10. Once the Management Server on
SP A and SP B has been restarted, security and domain information will be in an
uninitialized state. You should now be able to set the IP addresses using
the following steps
11. Open a browser and go to <Current SP A IP address/setup>
12. In the IP address field change
the current SP A IP address to the new SP A IP address and click "Apply
Settings". SP A will reboot which may take up to five minutes to complete
13. Go back to SP A's setup page
using the new SP A IP address <New
SP A IP Address/setup>
14. Open a browser and go to <Current SP B IP address/setup>
15. In the IP address field enter
SP B's new IP address and in the Peer IP Address field enter SP A's new IP
address and click "Apply Settings". SP B will reboot which may take
up to five minutes to complete.
16. Go back to the SP B setup page
<new SP B IP
Address/setup> and click "Restart Management
Server". Select "Yes" and "Submit" on the pop up
screen.
17. Go to SP A setup page <New SP A IP Address/setup>
(You may already be there due to step number 12) and click "Restart
Management Server". Select "Yes" and "Submit" on
the pop up screen. This will update the peer IP address on SP A.
18. If the array will be back in a
domain with other arrays, re-add it to the existing domain.
Security will automatically be initialized by obtaining the necessary
information from the domain master. If it was originally in the domain and it
was the domain master you can now select it as the domain master again.
If the array is not to be in a domain, open Navisphere Manager on SP A of the
array. You should now be prompted to initialize security. Select
"Yes" and add a global username and password.
Friday, March 14, 2014
How to migrate Clariion to VNX using SANCopy (naviseccli)
SANCopy syntax:
naviseccli -h -create -name name <-incremental>
[-srcwwn srcwwn|
-srclun srcspname srcNumOrSnapshotName <-device devicename="">|
-srcportwwn srcportwwn srclunnumber]
[-destwwn destwwns|
-destlunnumber destspname destlunnumber <-device devicename="">|
-destportwwn destportwwn destlunnumber]
<-changesonly> <-verify> <-start> <-throttle 1-10="">
<-linkbw linkbw=""> <-latency latency=""> <-o>
Example:
navicli -h sancopy -create -name -srcwwn xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx destlunnumber -verify
Start SANCopy:
naviseccli -h sancopy -start -name
naviseccli -h
[-srcwwn srcwwn|
-srclun srcspname srcNumOrSnapshotName <-device devicename="">|
-srcportwwn srcportwwn srclunnumber]
[-destwwn destwwns|
-destlunnumber destspname destlunnumber <-device devicename="">|
-destportwwn destportwwn destlunnumber]
<-changesonly> <-verify> <-start> <-throttle 1-10="">
<-linkbw linkbw=""> <-latency latency=""> <-o>
Example:
navicli -h
Start SANCopy:
naviseccli -h
Sunday, March 2, 2014
How to see the EMC ECC Bundle Update version?
Wednesday, September 4, 2013
Memory usage is very high on Redhat Linux
# cat free
total used free
shared buffers cached
Mem:
24674784 24576836 97948 0
351244 21165268
-/+ buffers/cache:
3060324
21614460<<<<-----actual buffers="" cached="" free="" memory="" p="">
= + +
= - - -
= -
Swap:
25165808 1084452 24081356
Total Physical
Memory = 24674784 KB = 24096 MB
Physically Used
Memory = 24576836 KB = 24000 MB
Actual used
memory = 3060324 KB = 2988 MB = ~3 GB
buffers =
351244 KB = 343 MB
cached =
21165268 KB = 20669 MB = ~20 GB
Physically Free
Memory = 97948 KB = 95 MB
Memory free for
Applications = 21614460 KB = 21107 MB = ~20 GB
The items to note here are:
The philosophy in Linux is that an unused resource is a
wasted resource. The kernel therefore will use as much RAM as it can to cache
information from your local and remote filesystems and disks. This builds up
over time as reads and writes are done on the system trying to keep the data
stored in RAM as relevant as possible to the processes that have been running
on your system.
This caching is reported by the system as the sum of two
numbers, buffers and pagecache. The cache is reclaimed, not at the time of
process exit (you might start up another process soon that needs the same
data), but upon demand - i.e. When you start a process that needs a lot of
memory to run, the Linux kernel will reclaim memory that had been storing
cached data and give it to the new process.
Refer below article for detail information on this:
What is cache memory and why is memory utilization high
for cache memory?
Why is so much of my memory used by cache?
Subscribe to:
Posts (Atom)