Note:

You are discouraged from using this rtminst configuration option. This legacy option has been provided for backward compatibility only. Instead, use the Interface identification and network setup option to perform interface identification. For more information, see Driver, Network, and Interface Configuration.

To perform Ethernet interface identification using the Interface identification (legacy) option, select [1] from the main rtminst menu. The program assists you in selecting and labeling your interfaces. First, select one or more communication ports and then identify other NICs as your sniffing interfaces.

The AMD machine is equipped with at least two network interfaces. You must designate at least one NIC as a communication port that will be used to log in remotely via SSH, send data to the report server, and communicate with the RUM Console software. You must configure another NIC to be ready to collect traffic data (enter promiscuous mode).

Note that traffic should be present on the network cable used for interface identification.

The following example demonstrates interface identification on a system with one sniffing NIC (port A) and two communication ports.

Before the actual interface labeling takes place, the program prompts you for the type of network drivers to use during the interface identification procedure. In general, choose the custom network drivers. If your system is not suited for the use of customized drivers, the system will automatically start using native drivers.

Figure 1. Selecting Interface Identification from the rtminst Menu
 AMD Installation Toolkit ver. ndw.12.4.XXX

Options:
        1 - Interface identification (legacy)
        2 - Interface identification and network setup
        3 - AMD setup
        4 - System setup verification
        X - Exit
Select an option and press `Enter` :1

Do you want to use custom network drivers in interface identification procedure?
It is recommended to use custom drivers. (y or n) y

Network drivers must be reloaded now.
WARNING: This may destroy all existing network configuration.
Do you wish to continue? (y or n) y
Starting rtm.setup. Please wait...

Network port identification tool.
- Make sure that a network cable is in a good working order.
- Connections should be made to a hub or VLAN on a switch with any Ethernet traffic.
- Place stickers on the network ports.
- You may exit at any time by pressing ^C.

Enabling promiscuous mode on network devices.. done.
 
Number of network devices detected: 3

Disconnect all network cables from the NICs and then connect one cable
to the port designated as a communication port and press ENTER

Disconnect all of the network cables as instructed, connect a cable to the designated communication port, press [ENTER], and wait for the port to be recognized as shown in the example.

 Wait until the test is completed.

Communication port test successfully completed.
Communication port assigned to eth0.
 
Do you want assign next communication port ? (y or n)

You can re-run the communication port assignment procedure to match the number of subnets that the AMD needs to communicate with:1

 Wait until the test is completed.
 
Communication port test successfully completed.
Communication port assigned to eth1.
 
Do you want assign next communication port ? (y or n) n

Next, there are no more communication ports to be assigned and a sniffing port must be identified, so press [n] to go to the next step.

 Disconnect all network cables from the NICs and then connect one cable
to the port designated as a sniffing port A and press ENTER (enter 'i' to ignore other ports).

Disconnect all of the network cables as instructed, connect a cable to the designated sniffing port A, press [ENTER], and wait for the sniffing port to be recognized as shown in the example.

 Wait until the test is completed.
 
Sniffing port A test successfully completed.
Sniffing port A assigned to eth2
 
 
Disabling promiscuous mode on network devices.. done.
 
communication port: eth0
communication port: eth1
sniffing port A: eth2
 
Do you want to apply the new settings? (y or n) y

If your AMD hardware configuration consists of Broadcom 10 Gb Network Cards, you may experience an error due to the mismatched link speed. For more information, see AMD fails to activate my Broadcom network card during the interface identification procedure..

In this example, there are no more ports to recognize, so select [y] for “yes” on the final confirmation screen and reconnect all network cables as instructed.

 Successfully written new interface assignments
 
Reconnect all network cables to continue setup.
There are more communication ports than recently.
Shutting down interface eth0:                              [  OK  ]
Shutting down interface eth1:                              [  OK  ]
Shutting down interface eth2:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Setting network parameters:                                [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:                                [  OK  ]
Bringing up interface eth1:                                [  OK  ]
Bringing up interface eth2:                                [  OK  ]
Running rtm.setup... done.

You will be asked again for the type of network drivers to use, this time permanently. In general, choose the custom network drivers. If your system is not suited for the use of customized drivers, the system will automatically start using native drivers.

 It is possible on this AMD to use either customized 
driver supplied by Compuware or native Linux driver.

Please note that:
	- Native drivers are required for ApplicationVantage Agent,
   so ApplicationVantage Agent will be disabled in customized drivers mode.
	- Native drivers may reduce AMD performance.

Do you want to use native driver? (y or n) y
Running rtm.setup again...  done.
RTM Probe is not running
AmdStatsMerger is not running
CBA (Console Basic Analyzer) is not running
CBA-Agent is not running
v2page converter is not running
page2trans converter is not running
RTMGATE is not running
Stopping AV Agent:                                         [  OK  ]
Starting rtm performance daemon:                           [  OK  ]
Starting AmdStatsMerger:                                   [  OK  ]
Starting RTM Probe:
Starting RTM please wait...
Done. RTM is running.                                      
                                                           [  OK  ]
Starting CBA-Agent:                                        [  OK  ]
Starting CBA (Console Basic Analyzer):                     [  OK  ]
Starting v2page converter:                                 [  OK  ]
Starting page2trans converter:                             [  OK  ]
Starting RTMGATE: Starting RTMGATE please wait...
Done. RTMGATE is running.                                  
                                                           [  OK  ]
Starting AV Agent:                                         [  OK  ]
____________________
1

Although it is possible to designate all NICs as communication ports, in practice such a setup would not be functional because no sniffing ports would be available on the device.