The infrastructure administrator creates network configuration information (XML definition files) for registering network devices based on the network device information (admin IP address, account information, connection information) obtained from the network device administrator.
About the information to be confirmed beforehand
When specifying the ifName for a network device as the "unit connection port name" of link information
Check the ifname of a network device using the snmpwalk command.
Example
snmpwalk -v 1 -c [SNMP_community_name] [IP_address] ifName
If the information is available from the manual or vendor of the destination device, obtain it from there.
Necessary definitions based on the number of devices to be registered.
When registering each network device individually
The Netdevice element must be the first.
When registering all network devices at once
Starting with the Netconfig element, define the settings for each network device under the Netdevices element. When registering multiple network devices at once, connection information can be also defined under the Links element.
At the status of link information already registered, when you register several network devices at once with link information defined in network configuration information, already registered link information is processed according to the mode of link information registration.
when "add"
The same link information is not overwritten.
when "modify"
All the already registered link information is deleted, and then defined link information is registered.
Already registered connection information can be retrieved using the rcxadm netconfig export command.
When registering network devices as network devices before installing them
When a network device is registered as a network device, the monitoring function starts monitoring that device. To avoid unnecessary monitoring, specify "true" for the Maintenance element when registering devices.
This setting enables the maintenance mode, excluding that device from monitored devices. After installing a network device and making it a monitoring target, release the maintenance mode.
The Maintenance element can be specified on individual network devices (individual Netdevice elements) to be registered.
When checking account information on registration or modification of a network device as a network device
When performing network device automatic configuration, Resource Orchestrator logs in to the network device using the registered account information. For this reason, if incorrect account information is specified, automatic configuration of the network device cannot be performed.
To check in advance whether the specified account information is correct, specify "check=true" for the LoginInfo element. This allows the login process to be performed using the specified account to check that login is possible.
The LoginInfo element can be specified on individual network devices (individual Netdevice tags) to be registered.
Only account information for network devices satisfying the following conditions can be confirmed.
Vendor | Unit Name | Prompt Type | Prompt Character |
|---|---|---|---|
Fujitsu | SR-X | Login prompt | Login: |
Password prompt | Password: | ||
Command prompt (*1) | Arbitrary string# | ||
Arbitrary string> | |||
Cisco | Catalyst | Login prompt | Username: |
Password prompt | Password: | ||
Command prompt (*1) | Arbitrary string# | ||
Arbitrary string> | |||
Nexus | Login prompt | login: | |
Password prompt | Password: | ||
Command prompt (*1) | Arbitrary string# | ||
Arbitrary string> | |||
Brocade | VDX | Login prompt | Login: |
Password prompt | Password: | ||
Command prompt (*1) | Arbitrary string# | ||
Arbitrary string> |
*1: The "#" or ">" following arbitrary string is used as a prompt character for the command prompt.
When registering a network device that provides a Web interface for management
When a problem occurs on the system, sometimes investigation may be performed using the Web interface provided by the network device. In such cases, it was necessary to start the web interface of the network device from another Web browser. However, specifying a URL for opening the web interface of the network device for the MgmtURL element when registering the network device makes it be possible to quickly open the web interface of the network device from the ROR console.
The MgmtURL element can be specified on individual network devices (individual Netdevice tags) to be registered.
When registering redundant network devices as network devices
Network devices that have the same "vendor name" and "device name" can be registered for redundant configurations. When registering a network device that has the same vendor name and device name, specify the same value as the registered network device for "Group_ID" of the Redundancy group_id element to treat that device as being in a redundant configuration.
For the "vendor name" and "device name" of a network device, collect MIB information from the network device when registering it, and confirm that the "vendor name" and "device name" are same as the ones of the registered device.
When registering information about connections with rack mount servers
When using a rack mount server with Resource Orchestrator, it is necessary to align the NIC number of the rack mount server with the subscript of the interface name of the server OS in advance. Also, use NIC1 and NIC2 for the admin LAN.
As NIC numbers used for the public LAN are 3 or a higher number, be careful when specifying connection information.
Example
[Windows]
NIC number = the subscript of the OS interface name
The first NIC: Local Area Connection 1
The second NIC: Local Area Connection 2
[Linux]
NIC number -1 = the subscript of the OS interface name
The first NIC: eth0
The second NIC: eth1
When registering an L2 switch
When registering an L2 switch as a network device, omit the Tenant element.
When registering models other than those with model definitions for network devices
Add the model of the network device to be registered to the model definition for network devices, and register the network device after updating the model definition file.
When regularly monitoring network devices registered as network device resources
When the workload of the network or network devices is temporarily increased, the response to the communication of regular monitoring may be delayed. When this delay exceeds the time-out period, the communication for regular monitoring will be executed again.
Therefore, if the monitoring interval (Interval element) or timeout period (Timeout element) specified during registration is short, the number of communications for regular monitoring may increase. It is recommended to use the default values in order to avoid increasing the load on the network and network devices.
See
For details on network configuration information (XML definitions), refer to "13.6 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
A tool has been provided that helps users easily create network configuration information (XML definitions). This tool can be downloaded from ServerView Resource Orchestrator web site.
For details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".
For details on releasing maintenance mode, refer to "22.1 Switchover of Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on model definitions for network devices, refer to "13.13 Network Device Model Definition" in the "Reference Guide (Command/XML) CE".
