Can someone explain me about the exact difference between Hitachi SN2 and Hitachi Command Suite ?
MIK MIK, SN/SN2 is used to manage the Enterprise arrays individually. If you don't have Device manager to manage the devices across the data center, this is a great tool to manage them.
Each storage (Modular/Enterprise), will have it's own storage management tool called as the Storage Navigator in case of Enterprise and SNM2 in case of Modular.
You can access SN by keying in the IP address of the respective storage in the address bar, You can use the default accounts for accessing the storage, as well you use external authentication methods. (AD/LDAP)
But CS is a centralized storage management tool. This will allow you to manage the storage's available in the data center from a single console.
Hi MIK MIK
To start of the basic difference between the 2 is:
1. SN2 is used to manage modular storage arrays.
Whereas, the Command Suite comes with Device Manager and Element Manager can be used to manage both modular storage arrays (AMS, HUS etc..) and the Enterprise Arrays (VSPs, HUS-VMs...)
2. You can use SN2 CLI to script for any storage work but only for Modular Arrays. Device Manager CLI can be used to write scripts for all your storage fleet out there. It also provides a central repository if you want it to pull some metrics.
These are the basic difference to start with. Please let me know if you had any particular thing in mind?
Thanks for Reply....
However, as per my knowledge ...SN2(Storage Navigator 2) can be use to manage Enterprise Storage arrays(VSP, USP V/VM, HUS VM...) and SNM2(Storage Navigator Modular 2) can be use to manage Modular Storage arrays ( AMS , HUS 110/130/150....) . Kindly correct me if I am wrong..
Now , my confusion is here...
1) Can we manage both enterprise and modular arrays through single SN2.?
2) We can perform almost every task through SN2 (managing LDEVs, CLPR ,LUSE, External storage.etc..) . So, what are the tasks that we can perform using Command Suite but not with SN2 .
Thanks & Regards
Sorry for the confusion above. I thought you meant SNM2 when you said SN2. I do not have any working knowledge about SN2.
The thing is you can have Command Suite integrated with your LDAP or AD. I think SN2 you have to have local accounts. So if your org has
a) Multiple SN2s spread geographically over a wide area (country vs country) and
b) a 90 day password change policy .. then it is better to use Command Suite as opposed to using SN2 and changing passwords manually.
Hope this helps!
HDS CMD lines are not very well documented or understod, can you explain what can be done with each and how.
Any procedural documents on how to use this feature would be welcomed.
Lots of command lines and you can manage quite a bit w/each one.
The Command Suite command line, does what Command suite does – the best part to me is that its one command line for all HDS arrays, the down side is the execution time is very slow.
There are command lines for AMS, USPV, VSP and HUS, the upside is they are fast and very detailed because they are one platform only. For example: I use raidcom for the VSP which gives me a great deal of power and control and I can create 80 ldevs’ in 5 minutes – the same task in Hicommand cli might take 2 hours – this is run time, not scripting time.
I can also do some things I can’t do in Hicommand – for example create a cow device.
Thanks for your reply i can agree with the benifits associated with this cmd lines but the implementation of each is scatchy, i.e what exactly do i need to do to enable each CLI interface, what are the cmd i can use and if you can provide setup and examples of each of the cmd if you have it documented it would help.
without that i am still struggling how to use raidcom.
Depending on what you have licenses for CS also gives you the interface to Replication Manager, tuning manager, Tiered Storage management. The cli is also very usfull as you can script both configuration and reporting in a generic language that works for all your HDS arrays, VPS, HUS, AMS, USPV
Moved to The specified item was not found. space.
Retrieving data ...