Preparation required in advance to manage network devices as resources is explained in this section.
Conditions where Preparation is Required | Details of Preparation |
|---|---|
When Creating Network Configuration Information (XML Definition) (Required Preparations) | Creating network configuration information (XML definition) |
Configuring definitions of the network device file management function | |
Registering External FTP Servers | |
Setting the login information of network device | |
When Modifying the Values of Network Device Configuration Files | Modifying the settings used in the definition file of the network device file management function |
Creating the port profile configuration function definition file |
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.
When registering network devices as network devices before installing them
When registering a network device that provides a Web interface for management
When registering redundant network devices as network devices
When registering information about connections with rack mount servers
When registering models other than those with model definitions for network devices
When regularly monitoring network devices registered as network device resources
When registering an Ethernet fabric switch
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.
When connection information is already registered
When link information is already registered, if 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 the link information registration.
When "add" is specified
The same link information is not overwritten.
When "modify" is specified
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 the state of 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.
When "telnet" has been specified in the protocol element, 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> | |||
F5 Networks | BIG-IP (*2) | Login prompt | There are no restrictions. |
*1: The "#" or ">" following arbitrary string is used as a prompt character for the command prompt.
*2: The model name for the BIG-IP LTM series is handled as "BIG-IP".
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 Visualizing Networks
When visualizing networks, it is necessary to register link information.
For details on visualization of networks, refer to "Chapter 11 Network Visualization" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When registering information about connections with rack mount servers
Register all link information of the admin LAN and public LANs connected to the rack mount servers.
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
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.
When registering an Ethernet fabric switch
About "unit connection port name" of the link information
When the Ethernet fabric is comprised of "Fujitsu PRIMERGY Converged Fabric Switch Blade (10 Gps 18/8+2)" and "Fujitsu Converged Fabric Switch", login remotely to the fabric virtual IP address of the corresponding device and confirm the name of the connection port to register device using the following command.
# show running-config
Port name and port type are displayed in the following form.
interface domain_id/switch_id/chassis_id/port type type
Port name is displayed following "interface".
Port type is displayed following "type" after that.
Example
interface 3/1/0/3 type cir
Port name in the following port type can be specified for "unit connection port name" of the link information.
"type cir"
The port that connects to an external network device.
"type endpoint"
The port that connects to a server.
"type linkaggregation group"
The port that is "type cir" or "type endpoint" using link aggregation.
For details on display contents of command, refer to Fujitsu Converged Fabric Switch manuals.
Information
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.
See
For details on network configuration information (XML definitions), refer to "15.6 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
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 "15.13 Network Device Model Definition" in the "Reference Guide (Command/XML) CE".
The preparation necessary to use the network device file management function is explained in this section.
Information
When the Ethernet fabric is comprised of "Fujitsu PRIMERGY Converged Fabric Switch Blade (10 Gps 18/8+2)" and "Fujitsu Converged Fabric Switch ", the network device file management function is not used. Follow the maintenance procedure of the corresponding device.
Configuring Definitions of the Network Device File Management Function
When using the network device file management function, it is necessary to configure the functions to be used and the number of generation files in the definition file in advance.
When details on how to define the network device file management function, refer to "9.4.8.3 When Modifying the Values of Network Device Configuration Files".
Registering External FTP Servers
When managing network device files, for network devices without an FTP server function, an external FTP server is necessary.
Backup the network device file
Transfer the backed up network device file to the admin server the manager is operating on
Transfer the backed up network device file from the admin server the manager is operating on
Restore the network device file transferred from the admin server to the target network device
Execute the rcxadm netconfig import command and register an external ftp server.
For details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".
Point
When using a Nexus 5000 series, it is necessary to set the following settings for external ftp server in advance to enable backup and restoration of network device files.
Set the change root.
Change the root directory("/") of the account to the home directory.
Setting the Login Information of Network Device
When registering or changing network devices, register the login information in the network configuration information (XML definition).
For the "SR-X series"
LoginInfo protocol: ftp
User: Must be specified
Password: Must be specified
Tenant: Do not specify
For the "BIG-IP Local Traffic Manager series"
LoginInfo protocol: ssh
LoginInfo authority: admin
User: Must be specified
Password: Must be specified
Tenant: Do not specify
For the "Nexus 5000 series"
LoginInfo protocol: telnet
LoginInfo authority: admin
User: Must be specified
Password: Must be specified
Tenant: Do not specify
For other supported devices
LoginInfo protocol: telnet
LoginInfo authority: user
User: Must be specified
Password: Must be specified
PrivilegedPassword: Must be specified
Tenant: Do not specify
Note
This section explains points to keep in mind when using this function.
When using a "IPCOM EX series"
This function creates a temporary file in the device.
Do not create the following files in the device.
ror-running-config.cli
ror-startup-config.cli
Also, secure sufficient disk space to save the network device configuration file on the device.
When restoring the network device file without initializing the authentication information
Execute the rcxadm netdevice cfexport command and export the network device environment file in advance, and then configure IPCOM EX manually.
For details on configuration, refer to the IPCOM EX manuals.
When deleting, changing, or deleting the account information registered in this product
Execute the rcxadm netdevice cfbackup command and backup the network device configuration file.
If restoration is performed without backing up, the restoration may fail due to account information inconsistency.
When using the automatic updating function for authentication information
When executing the rcxadm netdevice cfrestore command and restoring the network device environment file, authentication information may be initialized.
Example
Functions that are automatically updated include the following.
When "skey" in account authentication type is specified
When the authentication in SSL-VPN client or L2TP/IPsec client is performed using "local database operation"
When using a "BIG-IP Local Traffic Manager series"
The user specified in login information must operate the network device using tmsh immediately after login.
This function creates a temporary file in the device.
Do not create the following files in the device.
/var/local/ucs/environment.ucs
/var/local/scf/config.scf
Also, secure sufficient disk space to save the network device file on the device.
When using a "Nexus 5000 series"
When restoring a "Nexus 5000 series", perform the following.
When not connecting a "Nexus 2000 series"
(1) Log in to the target Nexus, and confirm the management IP address and SNMP community name.
(2) Clear startup-config using the write erase command.
(3) Restart the target Nexus.
(4) After restarting, log in to the target Nexus again.
(5) Set the management IP address and SNMP community name which were confirmed in (1).
(6) After log out of the target Nexus, and perform to restoration.
When connecting a "Nexus 2000 series"
(1) Log in to the target Nexus, and confirm the management IP address and SNMP community name.
(2) Clear startup-config using the write erase command.
(3) Restart the target Nexus.
(4) After restarting, log in to the target Nexus again.
(5) Set the FEX.
(6) Set the management IP address and SNMP community name which were confirmed in (1).
(7) After log out of the target Nexus, and perform to restoration.
When using a "Cisco ASA 5500 series"
When using redundancy configurations and only one device is faulty, it is not necessary to execute the rcxadm netdevice cfrestore command.
Using the functions of the "Cisco ASA 5500 series", the configuration of the active device can be reflected automatically.
For details, refer to the "Cisco ASA 5500 series" manuals.
When using a "Catalyst series"
This function creates a temporary file in the device.
Do not create the following file in the device.
flash:ror-running-config
Also, secure sufficient disk space to save the network device configuration file on the device.
The definition of the configuration management of the network device can be changed by setting the value to the following definition files beforehand.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
unm_mon.rcxprop
Specify variables in the definition file in the following format.
Parameter =Value |
Specify variables for network device configuration file management.
Parameter | Meaning and Value |
CONFIG_BACKUP | Specify whether to enable the network device file backup function.
If left blank, "true" is set. |
CONFIG_AUTO_MASTER | Specify whether to collect a master configuration file when registering a network device as a resource.
If left blank, "false" is set. |
CONFIG_AUTO_BACKUP | Specify whether to back up configuration files when network device auto-configuration is performed.
If left blank, "false" is set. |
CONFIG_RETRY_COUNT | Specify the retry count using a value between 0 and 10 for the network device connection when configuration backup is performed. If left blank, "3" is set. |
CONFIG_TIMEOUT | Specify the time out value using a value between 10 and 60 for the network device connection when configuration backup is performed. If left blank, "30" is set. |
CONFIG_NOTIFY_COMMAND | Specify whether to output a notification message if a change is detected in the backed up configuration when the rcxadm netdevice cfbackup command is executed (On demand collection).
If left blank, "false" is set. |
CONFIG_NOTIFY_AUTO | Specify whether to output a notification message if a change is detected in the backed up network device configuration file when network device auto-configuration is performed.
If left blank, "false" is set. |
Example
CONFIG_BACKUP=true
CONFIG_AUTO_MASTER=true
CONFIG_AUTO_BACKUP=true
CONFIG_RETRY_COUNT=3
CONFIG_TIMEOUT=30
CONFIG_NOTIFY_COMMAND=true
CONFIG_NOTIFY_AUTO=false
To use a port profile manually configured in an Ethernet fabric device ("Fujitsu PRIMERGY Converged Fabric Switch Blade (10 Gps 18/8+2)" or "Fujitsu Converged Fabric Switch ") using the port profile configuration function provided by Resource Orchestrator, define the following file:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
cfabric_portprofile_networkresource.rcxprop
Specify variables in the definition file in the following format.
"Network Resource Name"=Port Profile ID |
Specify the name of the network resource which uses the port profile in the following format:
/folder_name or tenant_name/pool name/network resource name |
Specify the port profile ID manually specified for the target device.
Example
"/TenantA/FolderA/NetworkPool/network1"=123
