Is there a Unisphere ssh login to access symcli?

support would not give me the root password, so i booted into single user mode (very easy to do for Suse, google it.) and reset the root password myself.  I don't typically run symcli commands on the appliance itself because i have dedicated symcli systems for that but i wanted to be able to import device groups so that it's easier to look at performance.

Thanks, good info. Problem is that the entire VCenter is isolated from any real storage (running on small local disks until VMAX is configured), and I don't have the ability to deploy any VMs. The EMC VSI plugin also requires a private SE (SMI-S) but that's only a subset of symcli. So if I do add a real SE server, then I've got 3 SE servers, when 1 is enough. Ugh. But no space to create them since I have no storage to work with!

This all may seem odd, but the whole point of this project is to migrate 39tb of VCenter 5.0 systems from DMX to VMAX on a new SAN and VCenter 5.5 using Open Replication and Vmotion. SAN/DMX/VMAX first, then VCenter. We're using the VCenter 5.5 for Unisphere only right now, but the app team as a deadline to deploy 2 SAP systems, and the DMX is full. So I'm trying to get them the space they need on the new VCenter from VMAX.

point 2 - Been there tried that....Related Objects is empty. EMC pre-created 100% of the space and did not put anything in a thin pool. When I created the pool it actually failed when trying to create the devices to put in it, but still created an empty pool.

jle wrote: Hmm, no root access is good for security, but not good for getting work done.

reset root password and use the symcli just like you would on any other dedicated system. I am assuming you have gatekeepers presented to this VMs.

Hmm, no root access is good for security, but not good for getting work done.

Unfortunately, when deploying the vApp, there is no root access or ability to do much from the command line.  There is a cseadmin user that can be used when SSH is enabled, but it's rights are also extremely limited.  A couple of suggestions:

1.  Set up the vApp as a server (storsrvd daemon) and point an SE client to this vApp and you can then run symcli commands that way.

2.  Instead of using the 'Extend a Thin Pool' wizard, try going into the details of the thin pool, then clicking on the "Data Volumes" link in the upper right of Related Objects.  There will be an "Add Volumes to Pool" button on the bottom.  You are basically doing the same thing, just in a different way than the wizard. Make sure the TDATs are the same raid protection as what is already in the pool, or it won't see them to add to the pool. 

Good luck.

as soon as you see the boot menu press arrow up/arrow down on your keyboard and it will no proceed further

Booting SUSE in single user mode | Linux Blog