HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

1. If you are using redundant networks on the CMS, use the HP Network Configuration Utility
(NCU) to team them now (if you haven't already). If you plan to team your networks, you must
complete that configuration prior to setting the attributes or network order for each network.
NOTE: In a Flex-10 NIC environment, where all potential NICs are enumerated and visible
to the Windows OS, the HP NCU is also useful in mapping the NICs to bays and ports. You
can use this utility to identify which network connections can be disabled in Windows (this
prevents unnecessary reports of a down network connection).
2. Select one network on the CMS to be primary. Usually this is the network that responds with
a matching FQDN used when filling in the primary DNS suffix for the CMS in Configure
Computer name and DNS suffix (page 13). Typically this should be the network used to
communicate with hypervisors and management modules.
3. Configure the properties of each network connection as appropriate for your environment:
a. Set the IP address, subnet mask, and the default gateway (if necessary).
b. Set the DNS server IP address.
c. In Advanced TCP/IP Settings, set the DNS suffix for this connection.
d. On all except the primary network, you may want to clear the Register this connection’s
addresses in DNS and the Use this connection’s DNS suffix in DNS registration checkboxes
to prevent managed nodes from seeing multiple IP addresses and names for the CMS.
4. Prioritize the Network Order to prefer the primary network. If using NIC teaming, then you
would select the connection that represents the team to be primary.
NOTE: If your CMS is running Windows 2012, NIC teaming is included in the OS. Thus,
NCU is not necessary to configure NIC teaming.
a. Open the Network and Sharing Center.
b. Click Change Adapter Setting (for Windows Server 2008 R2 or newer) or click Manage
Network Connections (for Windows Server 2008 SP2.)
c. Select Advanced Settings… from the Advanced menu. (For Windows Server 2008, if the
Advanced menu is not visible, press the Alt key to make the menu appear.)
d. In the Connections box, highlight the primary network and click the up arrow on the right
to move it all the way to the top.
e. Click OK to close Advanced Settings.
NOTE: The selection of the primary network has a significant effect on the behavior of HP
SIM . Whenever possible, you should set the primary network to the network on which the
CMS communicates to the managed nodes. In some network configurations, it is also necessary
to lower the Interface Metric on the network's Advanced TCP/IP Settings properties dialog.
5. After a primary network has been configured for the CMS, confirm that forward and reverse
lookups of the short and fully qualified name for the CMS behave correctly. All DNS lookups
must resolve correctly before proceeding to the next chapter.
Configuring firewalls
The Insight Management software products depend on network connectivity between the
management services and between the management services and the managed nodes. Host-based
firewalls and port filtering solutions on the CMS and other management stations, on the managed
nodes as well as intervening network based firewall products, can result in loss of management
connectivity. Windows Server 2008, by default, enables its host based and blocks ports used by
HP SIM Configure and Repair Agents tasks. Corporate security standards might also block
management protocols, such as those used by Insight Control server deployment. HP recommends
customers and service professionals familiarize themselves with Managing HP servers through
firewalls with Insight Management software, available at www.hp.com/go/foundationmgmt/docs.
22 Preparing the Central Management Server