Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

855

August 19th, 2008 17:00

New Solaris Box Specifications for SYMCLI server

Hi,
We need a new Solaris Box for SYMCLI Server purpose for controlling DMX4 frame. Can anyone let me know the required specifications for Solaris Box..

2.8K Posts

August 19th, 2008 22:00

I don't know what is a "symcli server" ... can you please explain what EMC software will run on the host and what will the "server" do in its daily routine ?? :D

I think you'll be running only solution enabler and you'll use the host to issue commands against the DMX, however I prefer your feedback to my guess ;-)

Message was edited by:
Stefano Del Corno

25 Posts

August 20th, 2008 10:00

Yes, you are correct. we will be installing the solution enabler for controlling the DMX4. We want to use a solaris box for this purpose. Can you please let me know the server specifications.

2.8K Posts

August 20th, 2008 10:00

I think you can easily find S.E. requirements in S.E. installation guide .. However S.E. doesn't require either CPU or RAM .. it requires at least an HBA to "see" gatekeepers from your DMX4. You need 500 Mb (yes, Mb) of disk space for both the runtime and supporting databases.. Wow it looks like a real product if you look at "requirements" ;-)

Solution Enabler is a thin layer of software we suggest to install on EVERY host if possible, not only on a dedicated "solution enabler server" ;-)

1 Rookie

 • 

20.4K Posts

August 20th, 2008 11:00

Solution Enabler is a thin layer of software we
suggest to install on EVERY host if possible, not
only on a dedicated "solution enabler server"


i don't know about that, i would only install it on system that have to have it. Otherwise it's another piece of software to keep updated ..as well as other potential security issue with having SE installed on every box.

2.8K Posts

August 20th, 2008 12:00

I said "suggest" and "if possible" ;-)

2.8K Posts

August 20th, 2008 14:00

again .. "suggest" .. and "if possible" ;-) ..

YMMV :-)

however inq doesn't decode all code pages returned to host from storage when you issue an inquire command ;-) .. And inq is almost useless when you grab an emcgrab :D

2.8K Posts

August 20th, 2008 14:00

And when you have to run emcgrab to dig into issues and to provide EMC customer service better details on your broken host, having S.E. on the host gives a lot more informations that our customer service always appreciate :D

2.8K Posts

August 20th, 2008 14:00

If I give 4 symdevs to a linux (or AIX or windows) host, how can you find better details on the disk when the OS simply gives /dev/sdX names or /dev/rhdiskX or \\.\physicaldriveX to them???

Generally speaking I love to be able to issue even a plain and simple syminq from all the hosts I'm assigning devices to, just to be able to check if everything is fine, if all paths are working fine.. And I love to be able to use always same commands (symcli commands) regardless of underlying OS :D

My 2 cents ]:)

1 Rookie

 • 

20.4K Posts

August 20th, 2008 14:00

why is it suggested ?

1 Rookie

 • 

20.4K Posts

August 20th, 2008 14:00

inq gets the job done. I would like to have full SE installation on every box but then some brave system admin brings a SE license from his former job and decides to "do some storage work" ..i can't allow for that to happen. Until symacl gets more robust ..no full SE installations on my boxes ;)

1 Rookie

 • 

20.4K Posts

August 20th, 2008 15:00

How about installing SE monitoring kit only ..have you played with that much ?

2.8K Posts

August 20th, 2008 16:00

Never played with monitoring kit .. However sounds interesting .. I usually issue symcli commands to cross-check that everything is fine .. however I usually tend to issue symcli commands from a single host where I also keep command files for symconfigure or scripts developed to address specific needs. Monitoring kit on all hosts and full SE only on "symcli servers" sounds good to me .. and to emcgrab, I guess ;-)
No Events found!

Top