If the hyper was used in other OS before, the new created LUN may not be used directly by VMWare ESX server (v 3.0). The server will see the LUN and capacity, but will report the error “unable to read partition information for this disk” when try to add it to Vmware system.
By default, Solaris 10 has net-snmp 5.0.9 installed and enabled with it SMA package (System Management Agent). However, the default settings does not allow any snmpwalk to get information.
From techrepublic as suggested by my supervisor
VEA is the GUI tool for veritas volume manager.
We have a new Solaris 10 box up today. The Brocade switch has been setup and LUNs from SAN are visible.
As all the FA on our DMX-3 reaches 255 LUN IDs, I am thinking removing some of non-used devices and noticed each FA has 10 2-way mirror mapped (each has only 6MB). What are these devices?
After we migrate the ECC from old server to new server and rediscover the storage and monitored devices, we realized the storageScope can not display the historical data before the migration date.
After we migrate the EMC SAN storage to a new SAN device, we found the storageScope graph does not work properly. It can either show the historical data till the migration date, or show the graph from migration date to now. This means the graph is cut at the migration date.
We can set the level of access users have by amending there access level in the /usr/openv/java/auth.conf file. However, the access is given either full or none, meaning that we do not have subtle control such like “readonly”.
Our backup solution uses Sun storageEdge L700 with Veritas netbackup. All hosts connect to the L700 with fiber channel. Yesterday we found one LTO3 tape stuck inside the drive and caused the backup partically failed.