|
|
United States-English | |
|
|
 |
|
VSE Management Software Release Notes Version A.03.00.01 > Chapter 4 Known Problems and Workarounds
nPartition Issues |
|
|
If you are managing multiple nPartition complexes with the same complex name and using HP SIM 5.00.02.00, all of the nPartitions in these servers are shown under one instance of the complex name, and they appear to be part of the same complex. If you are discovering the virtual partitions and they don't appear within their vPar monitor, there are a few things that can be wrong. First, you need to make sure all the latest WBEM Services and WBEM Providers are installed on the virtual partition and nPartition operating systems and WBEM access is configured to the managed systems (use the vseassist command for this). If using HP SIM 5.00.02.00, then the names of the complex, nPartitions and virtual partitions should not contain any spaces and all names must be unique. Spaces in these names can cause some errors in the associations between the systems and the virtual partition monitors. Also, the names of the complex, nPartitions, and virtual partitions all need to be unique across all the complexes you are managing from this CMS and each virtual partition name should match the hostname of the operating system running on it. If using HP SIM 5.01.00.01 or later, the serial number field must be defined uniquely in each complex and within a complex the names of the complex, nPartitions, and virtual partitions should be unique and each virtual partition name should match the hostname of the operating system running on it. See the “DISCOVERY” section of the hpsim-readMe.pdf file for more information about discovery issues on HP-UX. Run vseassist to help verify that the managed systems and CMS are configured properly. Use the Configure Follow the naming restrictions for the complex that are outlined in “Naming Restrictions” and, if using HP SIM 5.1.0.1 or later, read and follow the naming restrictions in the “DISCOVERY” section of the /opt/mx/doc/en/hpsim-readMe.pdf file. When a system subtype changes, it often changes the unique identifier use to identify the system. This causes a new managed system object to be created in the database, and the hostname and IP address of that system have to move to the new database object. However, there are still uncleared events associated with the old database object, so it is renamed to an “Orphan” name so that you are still able to view these events. Once you have viewed and cleared all the events associated with the Orphan system, it can be deleted from the database. If you are using HP SIM 5.0.2.0, upgrading to HP SIM 5.1.0.1 or later helps reduce the number of system subtype changes and, therefore, the number of Orphan systems created. Also, the “Orphan” systems will have their status set to disabled so they are not visible in the Virtualization Manager pages. You can also reduce the number of system subtype changes by doing the following:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
Configure VSE Agents submenus to deploy the latest agent software to the managed systems.