beautypg.com

Correlating, Vcem operations in hp sim and virtual connect logs – HP Virtual Connect Enterprise Manager Software User Manual

Page 55

background image

3.

For each VC Domain released from the VC Domain Group, insert or remove VC modules in the
corresponding enclosure, and perform the necessary domain, network, and storage configuration
changes in the VC Manager user interface.

Before VC module removal, remove the VC module uplink ports from all existing Network or Shared
Uplink settings from VC Domain configuration.

For VC module removal, from the VC Manager user interface, click Hardware
Overview

Enclosure_NameInterconnect Bays, select the VC module at the bay you want to

remove, then click Remove from Domain.

4.

Return to VCEM, click the VC Domain Groups tab, and click New. For more information about creating
a VC Domain Group, see

Creating a VC Domain Group

. At step 1, select the VC Domains to add to

the new VC Domain Group. Wait until the job operation completes. As a result, the new VC Domain
Group created contains an updated configuration reflecting the new VC modules.

NOTE:

Existing profiles cannot see new Fibre Channel SAN connections added using these steps. However,

if the fabrics were created on VC Manager, you can see the Fibre Channel SAN connections. For more
information, see

Editing a profile

.

Moving Ethernet networks (VLANs tagged) from one shared uplink to another

1.

Click the VC Domains tab, and select a VC Domain.

2.

Click VC Domain Maintenance, and enable VC Domain Maintenance by clicking Make changes via
VC Manager

.

3.

In Virtual Connect Manager user interface, delete the desired shared uplink sets or delete desired
Ethernet networks (VLANs tagged) from the shared uplink sets.

4.

Go back to VCEM and complete VC Domain Maintenance by clicking Complete VC Domain
Maintenance

.

5.

Repeat steps 1 and 2.

6.

In Virtual Connect Manager user interface, create Ethernet networks (VLANs tagged) to any shared
uplink set.

7.

Go back to VCEM, and complete VC Domain Maintenance by clicking Complete VC Domain
Maintenance

.

Correlating VCEM operations in HP SIM and Virtual Connect logs

All VCEM operations are logged in HP SIM Audit log and provide a reference to the VC Domain being
managed. The VCEM operations related to a managed VC Domain are also logged by Virtual Connect
Manager in its system log. In an audit process for VCEM operations, you must correlate HP SIM in Virtual
Connect Manager logs. To perform this task:

1.

Look for VCEM entries in HP SIM Audit Log by clicking Tasks & Logs

View HP Systems Insight

Manager Audit log

.

2.

Search for a VCEM operation that is starting: “Virtual Connect Enterprise Manager (VCEM) - Starting
job.”

3.

You can find timestamp, VCEM operation (Job number#, Job details, Job title, VC Domain name), and
username. For most VCEM operations you can find the related name of VC Domain.

4.

Look for VC Domain system log in Virtual Connect Manager by clicking Tools

System Log.

5.

Search for the log entries based on timestamp. Be sure to take the time difference between the CMS
and VC Domain into account.

There is no specific marker for VCEM operations. VCEM operations usually are encompassed by “VCM
user login” and “VCM user logout” entries for the username “A@.” For example,
CMS IP 16.84.195.136 appears in the VC log entry as a reference to
“([email protected])” because VCEM runs on the CMS system.

VC Domain Groups

55