|
|
This chapter provides detailed hardware installation and configuration instructions for SwitchProbe devices. Included are detailed instructions for any configuration tasks you might need to perform before connecting the SwitchProbe device to the network. From basic site requirements, to working with various types of network interfaces, this chapter includes all the information you need to install your SwitchProbe device on the network segment you want to monitor. First, there is an overview to help you determine which steps are required, and then the specific steps are provided in detail.
![]() | Caution To prevent possible damage to the SwitchProbe device, be sure to read the "Site Requirements" section. |
Although this chapter includes information to familiarize yourself with the SwitchProbe model you have, Table 3-1 lists the basic steps for connecting your SwitchProbe device to the network. Use the following table as a guide to ensure you perform all necessary steps for proper installation of your SwitchProbe device. If you are already familiar with SwitchProbe, you can use this table to turn directly to the steps you want to perform. But if you are new to the SwitchProbe device, read the entire chapter, and use this table as a checklist to ensure that you complete all the steps needed for proper configuration and installation of your SwitchProbe device.
| Be sure to: | As described in: |
|---|---|
| Unpack and inspect the SwitchProbe device | "Unpacking" |
| Select a proper site | "Site Requirements" |
| Determine configuration tasks | "Determining Configuration Tasks" |
| Configure the SwitchProbe device using an ASCII terminal
or Set up a BOOTP server to automatically configure the SwitchProbe device | "ASCII Terminal Procedure"
|
| Make the network connections | "Connecting to the Network" |
| Boot the SwitchProbe device | "Power-Up Sequence" |
Before unpacking the carton, ensure that there is no visible damage. Notify the carrier representative if there is damage, and arrange for a representative to be present while the carton is unpacked.
After opening the shipping carton and removing the unit, inspect it for any obvious damage that might have occurred during shipment. If any damage is present, file a claim with the carrier.
Inspect the carton contents to make sure you have received the following:
Each SwitchProbe unit has specific accessories. These are shown in Table 3-2.
| Model | Accessories |
|---|---|
| CDDI SwitchProbe | CDDI RJ-45 cable |
| FDDI SAS SwitchProbe | SC-to-SC cable |
| FDDI DAS SwitchProbe | 2 SC-to-SC cables |
| Fast Ethernet 100BaseFX Half-Duplex SwitchProbe | 3 cables: SC-to-SC, SC-to-ST, SC-to-MIC |
| Fast Ethernet 100BaseTX Full-Duplex SwitchProbe | Fast Ethernet FDX Tap for TX |
| Fast Ethernet 100BaseFX Full-Duplex SwitchProbe | Fast Ethernet FDX Tap for FX
5 cables: 3 SC-to-SC, 1 SC-to-ST, 3 couplers: 2 ST-to-ST, 1 ST-to-MIC |
| WAN SwitchProbe | WAN T cable |
The SwitchProbe device is intended to operate in a normal office environment and should be table mounted near the network segment it serves. The site must be equipped as follows:
![]() | Warning Do not work on the system or connect or disconnect cables during periods of lightning activity. |
![]() | Warning To prevent the switch from overheating, do not operate it in an area that exceeds the maximum recommended ambient temperature of 104°F (40°C). To prevent airflow restriction, allow at least 3 inches (7.6 cm) of clearance around the ventilation openings. |
![]() | Warning Only trained and qualified personnel should be allowed to install or replace this equipment. |
![]() | Caution Adequate ventilation must be provided with at least 6 inches of clearance at the rear and front so the fan can exhaust air from the unit. |
![]() | Caution Before plugging the power cord into the unit and the power source, verify that the power source to be used is compatible with the power supply requirements. |
![]() | Warning A voltage mismatch can cause equipment damage and may pose a fire hazard. If the voltage indicated on the label is different from the power outlet voltage, do not connect the chassis to that receptacle. |
Depending on your needs and situation, you might not need to perform any configuration tasks for your SwitchProbe device. However, you might have to perform a few steps to correctly configure your SwitchProbe device. To determine configuration tasks, make sure you read this section completely.
All SwitchProbe devices must have the following information to communicate with the TrafficDirector software application or other management software:
To determine if your application requires special configuration, read this section carefully.
If the following criteria are met, configuration of the SwitchProbe device is automatic. After unpacking the unit, you can immediately connect it to the network and turn it on. This situation applies only if:
If all of these criteria are met, refer to the "Unpacking" section in this chapter. Otherwise, you must configure either the management interface or the monitor interface before connecting the SwitchProbe device to the network.
Management Interface-Before connecting the management interface to the network, you must use a null-modem cable and an ASCII terminal attached to the console serial port to make configuration changes to the SwitchProbe device. Depending on your needs, you might make the following configuration changes:
Monitor Interface-Before connecting the monitor interface to the network, make the following configuration change to the SwitchProbe device. To do so, use the Console port.
If the network speed is 4 Mbps (only on Token Ring interfaces), set the interface speed.
An ASCII terminal must be used to configure the agent under any of the following conditions:
If an ASCII terminal is required, you need the following accessories before you begin configuration:
Connecting the data terminal to the console port is described in the following procedure:
Step 1 Make sure the SwitchProbe device is turned off. (The power LED on the front panel should be off.) Do not connect to the network at this time.
![]() | Warning Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord. |
![]() | Warning Before working on a chassis or working near power supplies, unplug the power cord on AC units; disconnect the power at the circuit breaker on DC units. |
To see the warnings in multiple languages, refer to the appendix, "Translated Safety Warnings."
Step 2 Make sure the SwitchProbe device is not connected to the network.
Step 3 Connect the data terminal to the console port of the SwitchProbe device using the null-modem cable. If the connector on the cable is not compatible, an adapter has to be used to match the cable and the debug port connector. Ensure that the screws are tight on both the adapter, the debug port connector, and the cable.
Step 4 Turn on the data terminal.
Step 5 Turn on the SwitchProbe device.
The power switch is on the front panel. After you power up the SwitchProbe device, it undergoes a set of self-tests before it actually boots. During a normal power-up or reset, you should see the following sequence:
<12:19:48> ----------New Boot---------- <12:19:48> Booting from flash <12:19:48> Interface 1: Ethernet <12:19:48> Interface 2: SLIP <12:19:48> Free memory after boot = 7225600 Bytes <12:19:51> Number of consoles initialized = 3 <12:19:51> Start agent interfaces.. <12:19:51> Opening port 2 for SLIP <12:19:51> ifn 1 MAC Addr: 00-80-8c-22-33-01 <12:19:51> Control entry: Count = 256, Size of each 908 <12:19:51> Proxy function enabled <12:19:51> AGENT Version 4.1.0 <12:19:51> NVRAM Version 4.1 <12:19:51> Link time Sep 24 19:09:07 97 <12:19:51> Interface [1] IP Addr: 204.240.143.122 <12:19:52> Net mask: 255.255.255.0 <12:19:52> GW Addr: 204.240.143.87 <12:19:52> Interface [2] IP Addr: Not configured <12:19:52> Net mask: Not configured <12:19:52> GW Addr: Not configured <12:19:53> Agent Ready <12:19:53> Free Memory after init = 6371284 Bytes Hit any key to enter configuration utility.
***** Token Ring SwitchProbe Rev 4.1 ***** Interface number :1 [1] Change IP Address 204.240.143.117 [2] Change Net Mask 255.255.255.0 [3] Change Default Gateway Address 204.240.143.1 [4] Change Read Community sqa [5] Change Write Community sqa [8] Select Interface ETHERNET [9] Change Server Address 204.240.143.7 [10] Upgrade Software [11] Enter Command-line mode [12] Reset Agent [31] Go to Next Page Enter your response or Enter "exit" to logout Selection#:
If the SwitchProbe model has a Token Ring or WAN interface, you must set that interface speed to match the speed of the network before you connect it, or it might interfere with network operation. Follow the steps in this section only for Token Ring or WAN. You must repeat these steps for each Token Ring or WAN.
Step 1 Access the Agent Configuration Utility by using the agent console or Remote Login function in the TrafficDirector application. You should see text similar to the following (the model number, revision, and some menu items might differ):
Step 2 Before you can change the speed of the interface, you must select the correct interface. The selected interface is shown across from menu item 8, Select Interface. If the correct interface is already selected, skip to Step 4. In this example, the selected interface is Ethernet. Prepare to change the selected interface by entering 8 and pressing Enter.
Step 3 Select the item that corresponds to the Token Ring or WAN interface. In this example, enter 3 and press Enter to select the Serial interface. An abbreviated menu is displayed:
3
Step 4 Set the speed of the selected interface by entering 6 and pressing Enter. If you are changing the speed of the Token-Ring interface, enter the desired speed in Mbps. For the WAN interface, enter the desired speed in kbps. The following example illustrates changing the interface speed from 1544 kbps to 56 kbps:
Step 5 Reset the agent by entering 12 and pressing Enter. When prompted, enter y and press Enter. The agent resets.You do not have to reset the agent after each setting change, but the settings do not take effect until the agent is reset.
If the SwitchProbe has a WAN interface, the default encapsulation protocol must match the encapsulation protocol of the network that you connect it to. If it does not, you must change the default encapsulation protocol using the following procedure.
Step 1 Access the Agent Configuration Utility by using the agent console or Remote Login function in TrafficDirector. You should see text similar to the following: (The model number, revision, and some menu items might differ.)
Step 2 Select the correct interface. The selected interface is shown across from menu item 8, Select Interface. If the correct interface is already selected, skip ahead to Step 4. In this example, the selected interface is Ethernet. Prepare to change the selected interface by entering 8, and pressing Enter.
8
Step 3 Select the item that corresponds to the WAN interface. In this example, enter 3, and press Enter to select the WAN interface. An abbreviated menu is displayed.
Step 4 Prepare to set the encapsulation protocol by entering 7, and pressing Enter.
7
Step 5 Set the desired encapsulation protocol by entering the appropriate number and pressing Enter. The SwitchProbe confirms your selection by displaying the main menu with the new encapsulation enter shown.
Step 6 Reset the agent by entering 12 and pressing Enter. When prompted, enter y and press Enter. You do not have to reset the agent after each setting change, but the settings do not take effect until the agent is reset.
SwitchProbe devices support multiple interfaces:
| Manage | Communicates the data gathered, configuration commands, and alarms between the management software and the SwitchProbe agent. |
| Monitor | Enables RMON counters embedded in the interface so that traffic statistics are mapped to standard RMON groups. The TrafficDirector application views any interface set to monitor mode as an RMON agent. |
| Manage + Monitor | Enables the SwitchProbe agent to communicate with the TrafficDirector application on the same network segment it is monitoring. |
Out-of-band management means a LAN interface monitors traffic, and the serial interface is used for management access.
Sideband management means a LAN interface monitors traffic, and a different LAN interface is used for management access.
In-band management means a LAN interface is used for management communication on the same network it is monitoring.
All SwitchProbe devices have a LAN interface as Interface 1 in manage mode for communication to the management software. In some SwitchProbe devices, this interface can be configured to simultaneously monitor the LAN segment it is attached to. All SwitchProbe devices also support out-of-band management through a serial interface in manage mode, running SLIP.
CDDI, FDDI, and half-duplex Fast Ethernet SwitchProbe models support optional in-band management through their respective high-speed interfaces. Refer to the "Installation" chapter for information on activating manage and monitor modes.
Table 3-2 shows the possible configurations for each SwitchProbe model. If manage mode is supported, man is shown. If monitor mode is supported, mon is shown. The default setting is shown in boldface type.
| Model | Interface 1 | Interface 2 | Interface 3 | Interface 21 | Interface 22 |
|---|---|---|---|---|---|
| Single and Dual Ethernet | Ethernet man+mon | Serial man | Ethernet (E2 option) mon, or man+mon | ||
| Single and Dual Token Ring | Token Ring mon or man, or man+mon | Serial man | Token Ring (T2 option) mon or man, or man+mon | ||
| WAN | Ethernet or Token Ring
man or man+mon | Serial
| WAN
| ||
| CDDI | Ethernet or Token Ring
mon, man, or man+mon | Serial man | CDDI mon, man, or man+mon | ||
| FDDI (SAS and DAS) | Ethernet or Token Ring
mon, man, or man+mon | Serial man | FDDI mon, man, or man+mon | ||
| Fast Ethernet Half Duplex | Ethernet
mon, man, or man+mon | Serial
man | Fast Ethernet
mon, man, or man+mon | ||
| Fast Ethernet Full Duplex | Ethernet
mon, man, or man+mon | Serial
man | Fast Ethernet mon | Fast Ethernet mon | |
| Fast Ethernet Dual Interface Half Duplex | Fast Ethernet
mon, man or man+mon | Serial
man | Fast Ethernet
mon, man, or mon+man | Fast Ethernet
mon, man, or mon+man | |
| Multiport Ethernet | Ethernet
man, mon, or man+mon | Serial
man | Ethernet
mon | Ethernet
mon | Ethernet
mon |
| Multiport WAN | Ethernet or Token Ring
man, mon, or man+mon | Serial
man | WAN
mon | WAN (option)
mon | WAN (option)
mon |
When a SwitchProbe device is first installed, the agent starts running with no further action. However, you might want to initialize certain parameters before proceeding further. To do so, use the TrafficDirector Configuration Utility.
The TrafficDirector Configuration Utility is a configuration console that lets you enable and configure options to customize the way a SwitchProbe agent monitors and gathers data. You can use the following two methods to access the configuration console:
Once you access the agent console, the TrafficDirector Configuration Utility menu is displayed. The main menu consists of two displays. Figure 3-1 shows the first page of menu items you see upon initial access, whether local or remote. You select a menu item by entering the corresponding number, and pressing Enter.
*****SwitchProbe Rev 4.1*****
Interface number : 1
[1] Change IP address 204.240.143.122
[2] Change Net Mask 255.255.255.0
[3] Change Default Gateway Address 204.240.143.6
[4] Change Read Community public
[5] Change Write Community public
[8] Select Interface ETHERNET
[9] Change Server Address 204.240.143.9
[10] Upgrade Software
[11] Enter Command-line mode
[12] Reset Agent
[31] Go to Next Page
Enter your response or Enter "exit" to logout
Selection #:
By selecting 31 Go to Next Page, the second page of the main console is displayed (Figure 3-2).
*****SwitchProbe Rev 4.1 ***** Interface number : 1 [13] Install Resource Monitor Installed [14] Install Proxy RMON Collector Not Installed [15] Install NetFlow Monitor Not Installed [16] Select Switch Device Type RMON Device (17) Change Device IP Address 204.240.143.196 [18] Change Device Read Community public [19] Change Device Poll Interval (secs) 5 [20] Change RMON parameters [21] Change RMON2 parameters [22] Configure Agent Options [23] Configure Traffic Generator [24] Configure Interface Options [32] Go to Previous Page Enter your response or Enter "exit to logout Selection #:
Other selections result in menu displays that show additional configuration options, such as 22 Configure Agent Options (Figure 3-3).
Selection #: 22
*****SwitchProbe Rev 4.1 *****
Agent Option Menu:
[1] Toggle router_discovery on
[2] Toggle router_enable off
[3] Toggle modem_log off
[4] Toggle slip_ip off
[5] Toggle packet_capture on
[6] Toggle traffic_generator off
[7] Toggle discover_wanspeed off
[8] Go to Main Menu
Selection #:
Some menu items prompt you for an immediate entry after selecting them, such as item 4 Change Read Community (Figure 3-4).
Selection #: 1
*****SwitchProbe Rev 4.1 *****
Agent Option Menu:
[1] Change IP Address 204.240.143.103
[2] Change Net Mask 255.255.255.0
[3] Change Default Gateway Address 204.240.143.1
[4] Change Read Community public
[5] Change Write Community public
[8] Select Interface ETHERNET
[9] Change Server Address 204.240.143.12
[10] Upgrade Software
[11] Enter Command-line mode
[12] Reset Agent
[31] Go to Next Page
Enter your response or Enter "exit" to logout
Selection #:4
New Read Community (public) :
Throughout many of the procedures in this book, you need to access the Agent Configuration Utility and navigate through various menu displays to configure your SwitchProbe device to best suit your monitoring needs.
You can manage CDDI, FDDI, and half-duplex Fast Ethernet SwitchProbe devices in-band through their respective interfaces. The Ethernet and the Token Ring SwitchProbe defaults to management through the Ethernet interface, but you can change the default to the Token Ring interface. Table 1-1 lists the available management options for each model.
The default setting is monitor-only on the high-speed (CDDI, FDDI, or half-duplex Fast Ethernet) interface. The following example shows how to enable in-band management by setting the high-speed interface to manage+monitor mode and setting the LAN interface (Ethernet or Token Ring) to monitor-only mode.
Manage mode cannot be disabled on the Serial Line Internet Protocol (SLIP) interface.
This procedure involves issuing a number of commands from the command line. For more detailed information on command-line mode, refer to the "Command-Line Mode" chapter.
Step 1 Access the Agent Configuration Utility by using the agent console or Remote Login function in the TrafficDirector application. You should see text similar to the following: (The model name, revision number, and some menu items might differ.)
Step 2 Check the current management and monitor settings. Enter 8 and press Enter.
Step 3 Select the interface for which you wish to view or change the settings. Enter 3 and press Enter to select the FDDI interface.
Step 4 Select 11, Enter Command-Line Mode and press Enter. You see a % prompt.
Step 5 Use the get command to display nonvolatile random-access memory (NVRAM) parameters. The object for manage mode is manage_mode. The setting can be either 0 or 1; 0 means that the manage bit is turned off; 1 means that the manage bit is turned on. The following command reports the state of Interface 3, CDDI, because it was selected in Step 3. The SwitchProbe agent returns a 0 to show that manage mode is turned off.
Step 6 Use the set command to change NVRAM parameters. The following command turns on manage mode.
Step 7 Now that manage mode is enabled on Interface 3, it must be disabled on Interface 1. The manage_mode object affects the currently selected interface. To turn off manage mode on Interface 1, you must first select it using the curr_interface object. Use the set command to select Interface 1.
Step 8 Use the set command and manage_mode object to turn off management mode for Interface 1.
Step 9 Configure the address of the high-speed (in this example, CDDI) connection. Follow the steps in the "Network Address and Mask" section to set the IP address, subnet mask address, and default gateway address for Interface 3. Make sure that Interface 1 and Interface 3 are on different subnets.
Step 10 Enter quit (in lowercase) to quit command-line mode.
Step 11 You do not have to reset the agent after each setting change, but the settings do not take effect until the agent has been reset. Reset the agent by entering 12 and pressing Enter. When prompted, enter y and press Enter. The agent resets.
Once the reboot is complete, the SwitchProbe device is configured for management in-band through the CDDI, FDDI, or half-duplex Fast Ethernet interface.
Once the reboot is complete, the SwitchProbe device is ready for in-band management through the FDDI, CDDI, or half-duplex Fast Ethernet interface.
To start a new Remote Login session for the agent, perform one of the following tasks:
Cisco SwitchProbe automatically install the RMON domain, as well as 26 RMON2 protocol domains upon boot up. Note that you cannot de-install network-layer protocol domains that the probe installs automatically. Instead, when you remove a network-layer protocol domain, host and conversation groups are disabled for the protocol domain, and the domain remains installed on the agent with only the statistics group enabled. Table 3-4 shows the list of protocol domains the probe automatically installs upon reset.
| DECNET | IPV6 | NETB | OSPF | TCP |
| FTP | IPX | NFS | RIP | UDP |
| HTTP | IP | NOVRIP | RLOGIN | VINES |
| ICMP | NET | NOVSAP | SNA | WINDOW |
| IP | NCP | OSI | SNMP | ATALK |
You can configure default RMON/RMON2 parameters contained in the probe when it boots up. The configuration you specify applies to all probe interfaces. For example, if you set max_host to a maximum of 10,000, each interface can track statistics for 10,000 hosts. Table 3-5 shows the RMON parameters you can configure.
| Select this: | To configure this: |
|---|---|
| [1] Change max_host | Maximum number of hosts for which each interface tracks mac-layer statistics. |
| [2] Change max_matrix | Maximum number of conversations for which each interface tracks mac-layer statistics. |
| [3] Change sh_buckets | Maximum number of buckets each interface uses to store short-term history statistics. |
| [4] Change lh_buckets | Maximum number of buckets each interface uses to store long-term history statistics. |
| [5] Change sh_interval | Interval the probe uses to gather and store short-term history statistics for each interface. |
| [6] Change lh_interval | Interval the probe uses to gather and store long-term history statistics for each interface. |
| [7] Change dlci_sh_buckets | Maximum number of buckets the probe uses to store short-term history statistics for each DLCI. |
| [8] Change dlci_lh_buckets | Maximum number of buckets the probe uses to store long-term history statistics for each DLCI. |
| [9] Change dlci_sh_interval | Interval the probe uses to gather and store short-term history statistics for each DLCI. |
| [10] Change dlci_lh_interval | Interval the probe uses to gather and store long-term history statistics for each DLCI. |
| [11] Toggle start_stats | Probe to start tracking RMON1 statistics for each interface and all DLCIs upon bootup. |
| [12] start_history | Probe to start tracking short and long-term history statistics for each interface and all DLCIs upon bootup. |
Table 3-6 shows the RMON2 parameters you can configure.
| Select this: | To configure this: |
| [1] Change nl_hosts | Maximum number of hosts each interface tracks network-layer statistics for. |
| [2] Change al_hosts | Maximum number of hosts each interface tracks application layer statistics for. |
| [3] Change nl_matrix | Maximum number of network-layer conversations each interface tracks statistics for. |
| [4] Change al_matrix | Maximum number of application-layer conversations each interface tracks statistics for. |
| [5] Change dlci_nl hosts | Maximum number of hosts each DLCI tracks network-layer statistics for. |
| [6] Change dlci_al_hosts | Maximum number of hosts each DLCI tracks application-layer statistics for. |
| [7] Change dlci_nl_matrix | Maximum number of network-layer conversations each DLCI stores statistics on. |
| [8] Change dlci_al_matrix | Maximum number of application-layer conversations each DLCI stores statistics on. |
| [9] Change host_aging_frequency | Frequency (in secs) at which each interface ages its host tables. |
| [10] Change matrix_aging_frequency | Frequency (in secs) at which each interface ages its conversation tables. |
| [11] Toggle start_protocol_distribution | Probe to start tracking protocol distribution statistics upon bootup. |
| [12] Toggle start_nl_host | Probe to start tracking network-layer host statistics upon bootup. |
| [13] Toggle start_nl_matrix | Probe to start tracking network-layer conversations upon bootup. |
Use the following procedure to configure RMON/RMON2 parameters for all probe interfaces.
Step 1 Access the Agent Configuration Utility.
Step 2 Select [31] Go to Next Page.
Step 3 Do one of the following:
(a) To configure RMON1 parameters for the selected interface, select [20] Change RMON Parameters.
or
(b) To configure RMON2 parameters for the selected interface, select [21] Change RMON2 Parameters.
Step 4 Do one of the following:
(a) If you selected [20] Change RMON Parameters, select the RMON parameter you want to configure as explained in Table 3-5.
or
(b) If you selected [21] Change RMON2 Parameters, select the RMON2 parameter you want to configure as explained in Table 3-6.
Step 5 From the main menu, select [12] Reset Agent for the new settings to take effect.
Before the agent can communicate with the management software, you must configure the management interface with the following parameters:
If you have a BOOTP server, this can be done automatically. For details, see the "Using BOOTP for Automatic Configuration" section in this chapter. If you do not have a BOOTP server or you want to change these settings manually, follow the procedure in this section.
Step 1 Access the Agent Configuration Utility by using the agent console or Remote Login function in SwitchProbe Manager. You should see text similar to the following (the model name, revision number, and some menu items might differ):
Step 2 Change the IP address of the agent by entering 1 and pressing Enter. The agent prompts you to enter the new address. Enter the address and press Enter. The following example illustrates changing the IP address to 45.20.1.2:
Step 3 Change the subnet mask of the agent by entering 2 and pressing Enter. The agent prompts for the new subnet mask. Enter it and press Enter. The following example illustrates changing the subnet mask to 255.255.252.0:
Step 4 Change the default gateway address of the agent by entering 3 and pressing Enter. The agent prompts for the new address. Enter it, and press Enter. The following example illustrates changing the default gateway address to 45.20.0.94:
Step 5 Make sure that the settings are correct by examining the menu carefully. Repeat any steps necessary before preceding to the next step.
Step 6 You do not have to reset the agent after each setting change, but the settings do not take effect until the agent is reset. Reset the agent by entering 12 and pressing Enter. When prompted, enter y and press Enter. The agent resets.
Before turning the SwitchProbe device on, a BOOTP server should be set up. If a BOOTP server is not set up, then use the ASCII terminal procedure detailed in this chapter for configuration. Connect the agent to the network using the interface in manage mode, and turn on the power. When the agent is powered up and completes its internal checkout, it sends out BOOTP requests every 30 seconds if the IP address was not configured.
If the agent needs to be reconfigured because the network address, subnet mask, or gateway address changed, then invalidate the old IP address to force the agent to begin sending out BOOTP requests again. The following procedure describes how to invalidate the IP address when the agent needs to be reconfigured:
Step 1 Access the Agent Configuration Utility by using the agent console or Remote Login function in the TrafficDirector application.
Step 2 Select option 11, Enter Command-line mode. The command-line prompt is displayed.
Step 3 Enter set ip_valid no. This tells the SwitchProbe agent that the IP address is invalid, and causes it to send out BOOTP requests.
Step 4 Enter quit (in lowercase) to quit command-line mode.
Step 5 Enter exit (in lowercase) to exit the Remote Login utility.
Step 6 You do not have to reset the agent after each setting change, but the settings do not take effect until the agent has been reset. Reset the agent by entering 12 and pressing Enter. When prompted, enter y and press Enter. The agent resets.
SwitchProbe devices are shipped with the latest version of firmware already installed. TrafficDirector client software also includes a copy of the latest version of the agent firmware. Should a new version become available, it might be necessary to upgrade the agent firmware.
The software required for the operation of the SwitchProbe device is included on nonvolatile Flash EPROM memory. If needed upgrade the system by loading a new software image to the Flash EPROM using Trivial File Transfer Protocol (TFTP).
Step 1 Follow the instructions appropriate to your TFTP server to get into the /tftpboot directory.
Step 2 Decompress and install the agent upgrade disk in the /tftpboot directory of any TFTP server by using the following command:
This extracts the nsxxxx.hex file. The exact name of the file varies according to the SwitchProbe model. For example, on the Ethernet SwitchProbe models, the file is ns6010.hex.
Alternatively, you can install the disk in any machine and then copy or use FTP (in binary mode) to transfer the nsxxxx.hex file that is extracted into the /tftpboot directory of the TFTP server.
The TFTP process is invoked from the agent console (local or remote).
Step 3 Access the agent through the agent console or through the TrafficDirector Remote Login application. You then see the agent configuration menu.
Step 4 The server address is the IP address the agent uses as the source for the TFTP transfer. To set the server address, enter 9 and press Enter. When the agent prompts for the TFTP server address, enter it and press Enter.
If TrafficDirector is running on the TFTP server that is referenced by this IP address, this server uses a configuration protocol to reconfigure the SwitchProbe device when it is reset.
Step 5 You must verify that the server address was set correctly before proceeding.
Step 6 From the main menu, select option 10, Upgrade Software, and press Enter to initiate the TFTP process and invoke the TFTP client in the agent. A status report of TFTP upgrade process is shown on the screen. A successful completion message on the console indicates the Flash upgrade is complete.
Step 7 You do not have to reset the agent after each setting change, but the settings do not take effect until the agent is reset. Reset the agent by entering 12 and pressing Enter. When prompted, enter y and press Enter and the agent resets.
|
|