Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Reference Guide (Command/XML)
ServerView

15.13 Network Device Model Definition

Create the model definition file for network devices in the following folders:

[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\network_device_model.xml

[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/network_device_model.xml

The XML definition of model definitions for network devices is shown below.

<?xml version="1.0" encoding="utf-8"?>
<NetworkDeviceCategory>
  <Vendors>
    <Vendor name="Vendor Name" enterprise_num="Vendor Number">
      <Products>
        <Product name="Device Name">
          <Types>
            <Type>Type</Type>
          </Types>
          <Models>
            <Model name="Model Name">
              <Types>
                <Type>Type</Type>
              </Types>
              <SysObjectId>sysObjectID</SysObjectId>
            </Model>
          </Models>
        </Product>
      </Products>
    </Vendor>
  </Vendors>
</NetworkDeviceCategory>
Table 15.22 List of Items Specified in XML Definitions of Model Definitions for Network Devices

Element Name

Description

Remarks (Possible Values, Examples)

Vendor Information

(Vendors)

Collection of vendors

Specify one or more Vendor elements.

Vendor name (*1)

(Vendor name)

Vendor name of the network device

Specify a character string beginning with an alphanumeric character and containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Specify the same arbitrary name as used for the Vendor name of the folder (*2) where the rulesets for L-Platform templates and network resources (network device-specific) are registered.

Vendor number (*3)

(Vendor enterprise_num)

Vendor number of the enterprise OID of the network device

(optional)

Specify the numbers allocated to the vendors continuing on from the enterprise MIB (1.3.6.1.4.1).

Device name information

(Products)

Device name information

Specify one or more Product elements.

Device name

(Product name)

Network device name (product name)

Specify a character string beginning with an alphanumeric character and containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Specify the same arbitrary name as used for the unit_name or model_name of the folder (*2) where the rulesets for L-Platform templates and network resources (network device-specific) are registered.

Type information

(Types)

Type information

(optional)

Specify one or more Type elements.

Type (*4)

(Type)

Type

(This cannot be omitted when specifying type information)

Specify the type of the network device.

  • L2-Switch

  • Firewall

  • SLB

Model name information

(Models)

Model name information

Specify one or more Model elements.

Model Name

(Model name)

Model name of network device

Specify a character string beginning with an alphanumeric character and containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Specify the same arbitrary name as used for the unit_name or model_name of the folder (*2) where the rulesets for L-Platform templates and network resources (network device-specific) are registered.

Type information

(Types)

Type information

(optional)

Specify one or more Type elements.

Type (*4)

(Type)

Type

(This cannot be omitted when specifying type information)

Specify the type of the network device.

  • L2-Switch

  • Firewall

  • SLB

sysObjectID

(SysObjectId)

sysObjectID of network device

Specify the OID character string including numbers and periods (".").
When the standard MIB sysObjectID for a network device is unknown, it can be confirmed using the snmpwalk command.

Example

This example shows checking using the snmpwalk command.

>snmpwalk -v 1 -c [SNMP community name] -On [IP address] sysObjectID

sysObjectID is displayed in the following format:

.1.3.6.1.2.1.1.2.0 = OID: .[sysObjectID]

When specifying the sysObjectID displayed in the command above, exclude the period (".") which is the first character of the command

*1: If two or more Vendor information (Vendor) that have the same Vendor Number are defined, the earliest one will take effect.
If only the vendor name is to be defined, specify the Vendor name and Vendor enterprise_num, and do not specify the apparatus name (Products) or model name (Models).

*2: For details on the folder for registration of the rulesets for L-Platform templates and network resources (network device-specific), refer to "F.3 Creating a Folder for Registering Rulesets" in the "Design Guide CE".

*3: The vendor numbers for major vendors are shown for reference.

Vendor Name

Organization name registered in IANA

Vendor Number

Fujitsu

Fujitsu Limited

211

Brocade

Brocade Communications Systems, Inc.
(previous was 'McData Corporation')

289

Brocade Communications Systems, Inc.

1588

Brocade Communications Systems, Inc.
(previous was 'Foundry Networks, Inc.')

1991

Brocade Communications Systems, Inc.
(previous was 'NuView Inc.')

2427

Brocade Communications Systems, Inc.
(previous was 'McDATA,Inc')

4369

Brocade Communications Systems, Inc.
(previous was 'Rhapsody Networks Inc.')

6905

Brocade Communications Systems, Inc.
(previous was 'McDATA Corp.')

8244

Cisco

ciscoSystems

9

Cisco Systems, Inc.

5771

Cisco Systems

5842

Alaxala_Networks

ALAXALA Networks Corporation

21839

Alcatel-Lucent

Alcatel-Lucent (previously was 'Alcatel Data Network')

637

Alcatel-Lucent (previously was Tropic Networks)

7483

Alcatel-Lucent, 4ESS

35710

Allied_Telesis

Allied Telesis, Inc.

207

Blue_Coat

Blue Coat Systems

14501

Extreme_Networks

Extreme Networks

1916

Fortinet

Fortinet, Inc.

12356

F5_Networks

F5 Labs, Inc.

3375

F5 Networks Inc

12276

Hitachi_Cable

Hitachi Cable, Ltd.

278

HP

Hewlett-Packard

11

H3C

H3C

25506

Juniper_Networks

Juniper Networks, Inc.

2636

Juniper Networks/Unisphere

4874

Juniper Networks/Funk Software

1411

NEC

NEC Corporation

119

Panasonic_Electric_Works

Panasonic Electric Works Co., Ltd.

396

Radware

RND

89

3Com

3Com

43

IANA: Internet Assigned Number Authority

*4: If a type (Type) has been specified under both Product name and Models, the type under Models is given priority.
No network device type is specified if neither is specified.

Example

<?xml version="1.0" encoding="UTF-8"?>
<NetworkDeviceCategory>
  <Vendors>
    <Vendor name="Fujitsu" enterprise_num="211">
      <Products>
        <Product name="SR-X300">
          <Types>
            <Type>L2-Switch</Type>
          </Types>
          <Models>
            <Model name="SR-X316T1">
              <SysObjectId>1.3.6.1.4.1.211.1.127.65.53</SysObjectId>
            </Model>
            <Model name="SR-X324T1">
              <SysObjectId>1.3.6.1.4.1.211.1.127.65.54</SysObjectId>
            </Model>
            <Model name="SR-X340TR1">
              <SysObjectId>1.3.6.1.4.1.211.1.127.65.55</SysObjectId>
            </Model>
          </Models>
        </Product>
        <Product name="SR-X500">
          <Types>
            <Type>L2-Switch</Type>
          </Types>
          <Models>
            <Model name="SR-X526R1">
              <SysObjectId>1.3.6.1.4.1.211.1.127.65.52</SysObjectId>
            </Model>
          </Models>
        </Product>
      </Products>
    </Vendor>
  </Vendors>
</NetworkDeviceCategory>

Information

The values of Vendor elements, ProductName elements, ModelName elements, and Type elements of the network configuration information are used for the vendor name, device name, model name, and type of the network device preferentially.

If the Vendor elements, ProductName elements, ModelName elements, or Type elements are not specified in the XML definition of the network configuration information, identify the vendor name, device name, model name, or type from the model definition file.

In the model definition file, the vendor name, device name, model name, and type of a network device are identified using the OID character string specified in the SysObjectId element in the Model element.

  • The model definition file of the network device is searched from the top.
    The value of the name attribute of the Model element is the model name, the value of the Product element is the device name, the value of the Vendor element is the vendor name, and the value of the Type element is the type of sysObjectID which has been matched first.

  • If no matching OID character string is found in the model definition file of the network device, it is taken as meaning the network device has no vendor name, device name, model name, or type.