Table of Contents

Overview of Advanced Features
Serial Line Internet Protocol Support

Selecting the SLIP Address
SLIP Configuration Overview
SLIP Configuration Tutorial

Modem Support

Using Modem Configuration Commands
Using Modem Control Strings
Defining Control Strings
Using the Modem Log
Modem Configuration Tutorial

Setting Security Options

Using Data Capture For Packet Decoding and Analysis
Using the Console Logout Security Feature
Using the Access List Security Feature

Setting Access Levels
Defining Address Groups
Configuring Access List Security
Disabling Access List Security
Access List Examples

Configuring Static Routes
Configuring Private Routes
Using SLIP Routing

Configuring SLIP Routing

Creating IP Filters for Expert Data Reduction

Downloading IP Filter Information Using dvftp
Setting IP-DATAFILTER from Command-Line Mode

Configuring SNMP Trap Ports and Destinations

Specifying Trap Ports

Using Cisco Discovery Protocol
Using the FASTMIB Feature
Assigning a Locally Administered Address (Token Ring Interfaces)
Establishing a Roving Agent for Full RMON Analysis

Making the Roving Connection

Using Advanced Features

Overview of Advanced Features

Table 10-1 describes the advanced features supported in SwitchProbe devices.

Serial Line Internet Protocol Support

All SwitchProbe models support out-of-band communications using Serial Line Internet Protocol (SLIP) through the serial port labeled Remote. You can use the SLIP connection as a secondary connection through which to access all network statistics.

The SLIP function also includes these features:

• SNMP communication over a serial link.
  
  
• Forwarding of trap packets from a LAN to the SLIP port. When you use a modem, you can configure the agent to dial the remote node to forward the trap packet. To configure a modem, see "Modem Configuration Tutorial."
  
  
• Routing of IP packets between the SLIP port and the primary LAN interface.
  
  

The serial connection can be direct through EIA/TIA-232 or over telephone lines using dial-up modems. Communications over a serial line are the same as over a LAN, except that serial line packets are encapsulated using SLIP protocol (as specified in RFC 1055).

Selecting the SLIP Address

The SwitchProbe agent uses a standard IP routing algorithm to route packets to different interfaces. You should configure the agent using an IP address on a different subnet than the LAN IP address. The IP addresses that appear on the SLIP interface should be in a different subnet than the LAN interface; otherwise, the agent cannot route the packets correctly.

SLIP Configuration Overview

To configure the SLIP interface, you must use the console port or the TrafficDirector Remote Login application.

To configure the SLIP interface, follow these steps:

Step 1   Connect to the agent using the console port or the TrafficDirector Remote Login application.

Step 2   Select the SLIP interface.

Step 3   Configure the following elements:

• IP address
  
  
• Subnet mask
  
  
• Gateway address
  
  
• Interface speed
  
  

Step 4   Select the LAN management interface again.

Step 5   Configure the IP stack on the management station to use SLIP.

Step 6   Create a new agent using the Remote Login application with the new IP address and interface used by the SLIP port.

SLIP Configuration Tutorial

To configure the agent to use the SLIP port, follow these steps:

Step 1   Connect to the agent using the console or the TrafficDirector Remote Login application.

After connecting to the agent, the following configuration menu is displayed:

Step 2   Change the selected interface.

You must select the serial interface before you can configure it. The selected interface is shown across from menu item 8. In this example, the selected interface is Ethernet.

To change the selected interface, enter 8 and press Enter.

Step 3   Select the item that corresponds to the serial interface.

In this example, enter 2 and press Enter to select the serial interface. The configuration menu reflects the serial interface settings.

Step 4   To change the IP address of the agent, enter 1 and press Enter.

You are prompted to enter the new IP address.

Step 5   Enter the new IP address and press Enter.

The following example shows how to change the IP address to 192.168.143.1:

---

Note The IP address change does not take effect until you reboot or reset the device. You must do so to continue communication with the agent with its initial address. When a new session is initiated, the device is accessed using the new address.

---

---

Note A subnet mask is automatically inserted by the program, depending on the IP address you entered. You can change the subnet mask in Step 6.

---

Step 6   To change the agent subnet mask, enter 2 and press Enter.

You are prompted for the new subnet mask.

Step 7   Enter the new subnet mask and press Enter.

The following example shows how to change the subnet mask to 255.255.252.0:

Step 8   To change the default gateway address, enter 3 and press Enter.

You are prompted for the new address.

Step 9   Enter the new gateway address and press Enter.

The following example shows how to change the default gateway address to 192.168.143.94:

Step 10   To set the speed of the serial interface, enter 6 and press Enter.

Step 11   Enter the desired speed (in bps).

The following example shows how to change the interface speed to 19.2 kbps:

Step 12   To select the item that corresponds to the Ethernet interface, enter 1 and press Enter.

The configuration menu is displayed:

Step 13   Reset the SwitchProbe agent. To do so, see "Resetting a SwitchProbe Agent" in "Configuring SwitchProbe Devices."

Modem Support

Before the SwitchProbe agent can use a modem through the remote serial port, you must configure SLIP correctly. The agent supports Hayes-compatible modems connected to the remote serial port for SLIP connections with remote network management stations.

Using Modem Configuration Commands

You configure the modem through the agent console using command-line mode. For more information about command-line mode, see ""Using Command-Line Mode to Customize SwitchProbe Devices."

To access command-line mode, follow these steps:

Step 1   Connect to the agent using the console or the TrafficDirector Remote Login application.

Step 2   To access the command-line mode, enter 11 and press Enter.

The object name for modem options is modem. For help about modem options, enter the command help modem, as shown in the following example:

To display all modem parameters, enter the command get modem, as shown in the following example:

To display the contents of a specific modem control string, enter the command get with the modem object and the name of the control string, as shown in the following example

The following example sets the modem connect time to 20:

Using Modem Control Strings

Modem control strings are ASCII strings used to initialize and communicate with the modem.

You must enclose all strings containing blank spaces inside quotation marks. All modem control strings are limited to 40 characters. If you use more characters than the maximum allowed, the string is not accepted.

You can embed control characters such as carriage-returns in the strings by preceding the control character with a caret (^) character. For example, to embed a carriage-return (Ctrl-M), you enter ^M.

The strings can also contain the following special control characters:

• ^digit 1 through 9—Delays 1 to 9 seconds.
  
  
• ^s—Sends the string.
  
  
• ^w—Waits for the string.
  
  

You can use the pound (#) character as a delimiter for strings.

Defining Control Strings

Table 10-2 describes the modem control string.

Using the Modem Log

For help with debugging, you can log all messages to and from the modem to the event log. You enable and disable this feature with the agent_options object.

The following example shows how to turn the modem log on:

The following example shows how to turn the modem log off:

The following example shows how to view the event log:

Modem Configuration Tutorial

This tutorial shows the modem configuration process. Any entries you make for modem configuration take effect immediately without rebooting the agent.

To configure the modem through the agent console using the command-line mode, see "Using Command-Line Mode to Customize SwitchProbe Devices," and follow these steps:

Step 1   To access command-line mode, connect to the agent using the console or the TrafficDirector Remote Login application.

Step 2   To access command-line mode, enter 11 and press Enter:

Step 3   To review the existing configuration, enter the command get modem:

Step 4   Enter the modem initialization string:

---

Note Enter the command exactly as shown. You must use quotation marks if there are spaces between the characters in the string. Note the two ^M characters at the end of the string. This is the carriage-return to the modem that indicates the end of the string. If you do not use this string, the command is not processed. This string is automatically sent to the modem when the agent is booted.

---

The agent interprets this string as:

• Send the string AT S0=1 to the modem to instruct it to answer incoming calls on the first ring.
  
  
• Send a carriage-return (Ctrl-M).
  
  

Step 5   Set the modem hangup string to "^2+++^2ATH0^M":

The agent interprets this string as:

• Delay two seconds.
  
  
• Send the string +++ to switch the modem from data mode to command mode
  
  
• Delay two seconds.
  
  
• Send the string ATH0 so the modem hangs up.
  
  
• Send a carriage-return (Ctrl-M).
  
  

Step 6   Set the modem connect string to match the message your modem sends when it makes a connection.

In this example, assume the message is CONNECT or CONNECT 14000.
See your modem reference manual for the exact string used by your modem:

The pound sign (#) is a string separator. The agent assumes that a connection is made if it receives either of the strings delimited by the # character.

Step 7   Set the modem noconnect string to match the message your modem sends when it fails to make a connection.

In this example, assume the message is BUSY or NO CARRIER, or
NO DIALTONE or NO ANSWER. See your modem reference manual for the exact string used by your modem:

The syntax is the same as the connect string.

---

Note You must enter the string on a single line with no carriage-returns.

---

Step 8   Set the modem primary phone number to dial 1-555-123-4567.

You must precede all modem commands with AT. Use the D command to make the modem dial and use T to indicate touch-tome dialing (instead of pulse).

Step 9   Set the modem connect protocol as follows:

% set modem connect_protocol ^2^s^M^wlogin:^smikec^M^wpassword:^ssecretword^M

---

Note You must enter the string on a single line with no carriage-returns.

---

The agent interprets this string as:

• After the connection is made, wait two seconds (^2)
  
  
• Send carriage return to the remote terminal (^s^M)
  
  
• Wait for the login prompt (^wlogin:)
  
  
• Send the string mikec followed by carriage-return (^smikec^M)
  
  
• Wait for the password prompt (^wpassword:)
  
  
• Send the string secretword followed by carriage-return (^ssecretword^M)
  
  

If modem protocol and security support is not needed, set a null connect_protocol string:

The agent waits for the connection to be established for a maximum of connect_time.

Step 10   Set the connect_time to 30 seconds:

The agent retries a number for a maximum of connect_retry times.

Step 11   Set the connect_retry string to 5 times:

Step 12   Set the modem secondary phone number to dial 1-555-123-1111.

After the agent has failed to make a connection after connect_retry attempts, it tries to use the secondary phone number:

You must precede all modem commands with AT. Use the D command to make the modem dial and use T to indicate touch-tome dialing (instead of pulse).

If data is not send for more than disconnect_time after the agent makes the connection, the agent closes the connection.

Step 13   Set the disconnect_time string to 30 seconds:

Setting Security Options

When you select Security Options from the Agent Configuration Utility main menu, another menu is displayed. Table 10-3 describes the security-related functions you can configure with these options.

Using Data Capture For Packet Decoding and Analysis

The Data Capture feature lets a SwitchProbe device collect selected packets for later decoding and analysis. You can use the TrafficDirector Protocol Decode application to upload the packets to the client software for seven-layer protocol analysis.

By default, packet capture is enabled in a SwitchProbe device. After you disable packet capture functionality in an agent, you can only enable it again from the local console.

To toggle packet capture functionality on or off, follow these steps:

Step 1   Access the Agent Configuration Utility.

Step 2   To go to the next page, enter 31 and press Enter.

Step 3   To access Security Options, enter 19 and press Enter.

Step 4   To toggle data capture on or off, enter 4 and press Enter.

Step 5   To return to the previous screen, enter 5 and press Enter.

Using the Console Logout Security Feature

This feature secures an unattended password-protected SwitchProbe device.

If a user or admin password has been assigned to the SwitchProbe device, the Console Logout function immediately ends your Agent Configuration Utility session and displays a prompt to enter a user or admin password. This function is useful for authorized users (using a password) of a SwitchProbe device to temporarily log out of the device without exposing the device to unauthorized use.

If a user or admin password has not been assigned to the device, the Console Logout function performs no useful task, but displays the current screen again.

Using the Access List Security Feature

All SwitchProbe models use the SNMP community mechanism for security. Any stations trying to access the SwitchProbe device must know the read community name to gain read access, and must know the write community name to gain write access.

All SwitchProbe models also support an access list that controls which IP address groups are allowed access, and what level of access they have. The access list allows four different groups of access; you can assign each group a different access level.

Setting Access Levels

Table 10-4 shows the access levels . When an address matches more than one group in the access list and qualifies for rights at more than one level, the access level with the highest priority number is granted.

Defining Address Groups

You can define a maximum of eight different groups and establish access to each group with a different address group. An address group can be an individual IP address or a group of addresses, defined by the network address and network mask:

• Network address—IP or network or subnet address of all hosts allowed to access the agent.
  
  
• Network mask—Mask for the network address, network, or subnet address. This field is used to distinguish what type of address is specified in the IP network address field. For a single IP address, the mask is 255.255.255.255.
  
  

When an SNMP request is received from a host, its source IP address is logically ANDed with the mask. The result of the logical AND is compared with the network address field.

If the comparison is successful, the access level of that group is granted to that host. However, the host can match multiple entries in the access list. When a host matches multiple access levels, the access level with the highest priority is used.

Use the following guidelines to specify masks:

Configuring Access List Security

To configure access list security, follow these steps:

Step 1   Access command-line mode using the console or the TrafficDirector Remote Login application.

Step 2   Enter 11 and press Enter:

Step 3   For help about displaying and changing the SNMP access list, enter the command help access_list:

Step 4   Enter the command get access_list to view the current access list.

When the SwitchProbe device is manufactured, all entries in the table have no access, and the access list security feature is disabled:

Step 5   Enter the command set access_list to change the access list.

The command must specify the access_list object, the entry number, the network address, the mask, and the access level.

---

Note When setting an entry in the access_list, the first entry should always be with read/write (rw) access. When deleting an entry from the list, you must have at least one entry with rw access.

---

The following example grants read and write access to one specific host with the address 192.168.143.5. All other hosts have no access.

Disabling Access List Security

Your SwitchProbe device is shipped with the access list security feature disabled by default. All entries in the table have no access and the SNMP security feature is disabled.

To clear the access list, enter the following command:

You can also create an entry in the table with an IP network address of 0.0.0.0, a mask of 0.0.0.0, and the level as rw, allowing all nodes to read/write to the agent:

Access List Examples

Tables 10-5 and 10-6 show examples of incorrectly and correctly configured access lists.

Configuring Static Routes

You can add static routes to SwitchProbe devices using the local or remote console. A static route is volatile and is deleted when the device is rebooted.

You configure static routes using command-line mode. For more information about command-line mode, see "Using Command-Line Mode to Customize SwitchProbe Devices."

You can access command-line mode by connecting to the agent through the console or by using the TrafficDirector Remote Login application. To do so, enter 11 and press Enter.

In command-line mode, enter the command help route to display a complete set of the routing commands:

Enter the command get route to display the current routing table for the agent:

The following command sets a static route for all communication with the NET 192.168.0.0 to be directed to the gateway 192.168.143.20:

The following command sets a static route for all communication with the IP address 192.168.143.5 to be directed to the gateway 192.168.193.20:

The following command deletes the previous static route:

Configuring Private Routes

You can configure SwitchProbe devices to have private routes that are stored in NVRAM and configured in the agent route table at boot time. NVRAM can hold four private routes, each containing three fields—IP/Subnet address, mask for the IP/Subnet address, and gateway for the route.

You configure private routes through the console using command-line mode. For more information about command-line mode, see "Using Command-Line Mode to Customize SwitchProbe Devices."

You access command-line mode by connecting to the agent using the console or the TrafficDirector Remote Login application. To do so, enter 11 and press Enter.

Enter the command help proute to display a complete set of the private route commands:

Enter the command get proute to display the current private route table:

Enter the command set proute with the entry number, network address, mask, and gateway to change the private route table. In the following example, all packets destined for IP subnet 192.168.143.0 are sent to 192.168.143.20:

To invalidate a private route entry, enter the following commands. This example invalidates private route entry 1:

To clear all private route entries, enter the command clear proute:

Using SLIP Routing

A SLIP mini-routing feature is supported in all SwitchProbe devices. This feature allows trap messages from the network to be forwarded to remote management locations through the SLIP interface. It also allows access to the network through the SLIP port for telnet and other IP-based activities. This feature is useful when the network segment is otherwise inaccessible.

The primary interface (for example, interface 1) has a secondary IP address used to make the agent act as a pseudo-IP router and for routing. If the mini-routing option is enabled, the agent routes all IP packets from the SLIP port to the LAN, and vice versa.

For packets coming from the SLIP interface that are not destined for this agent, but for another host on the network, the agent replaces the source IP address with the pseudo-IP address and recalculates the checksums before sending the packet across the LAN port.

The same process is followed for packets arriving on the LAN port that are destined for the pseudo-IP address. These packets are trapped and sent to the SLIP port using the SLIP port IP address as the source IP address. The checksum is recalculated before transmitting the packets on the SLIP port. All IP packets are supported for this pseudo-router.

The pseudo-routing function works only on IP packets; all other packets are not affected. When the IP packet reaches the SwitchProbe device, the firmware forwards it to the IP task. The IP task determines where the packet belongs. If it is not intended for itself, and if the SLIP route option has been enabled, the IP packet is transmitted on the LAN interface after the source IP address has been submitted by the secondary IP address.

Configuring SLIP Routing

You enable and disable SLIP routing using the agent console in command-line mode. For more information about command-line mode, see "Using Command-Line Mode to Customize SwitchProbe Devices."

You can access command-line mode by connecting to the agent using the console or the TrafficDirector Remote Login application.

To do so, enter 11 and press Enter:

SLIP routing is controlled by the slip_ip option in the agent_options object. To view the current setting, enter the command get agent options:

To enable SLIP routing, enter the following command:

Creating IP Filters for Expert Data Reduction

You can create and download IP filters to SwitchProbe devices that determine whether to include or exclude packets from particular IP addresses. You can configure your SwitchProbe device to collect only packets from those hosts you want to monitor, eliminating unwanted hosts and conversations.

To do so, you must provide the device with the network address and mask of the hosts you want to include or exclude. You can use these methods to provide the SwitchProbe device with this IP filter information:

• Download the information using the TrafficDirector dvftp utility.
  
  
• Pass the information directly to IP-DATAFILTER using the set command.
  
  

Downloading IP Filter Information Using dvftp

You download the required IP filter information by specifying the information in a text file, then passing that file as a parameter to the dvftp utility. This text file contains lines in the following format:

For example:

In this example, the SwitchProbe device includes (I) for collecting all packets from host 192.168.x.x, and excludes (E) all packets from host 192.168.143.x.

Enter the following command to run the dvftp utility:

dvftp agentname filename IP-DATAFILTER

where:

• agentname is the name defined for the agent when adding it to the client software. The dvftp utility downloads the DLCI information to the interface number you specified when you added the agent to the TrafficDirector application.
  
  
• filename is the text file containing the IP filter information. If you do not specify a path, dvftp searches for the file in the $NSHOME/usr directory.
  
  
• IP-DATAFILTER is the file type.
  
  

If you are using the TrafficDirector application on a UNIX platform, you must run the dvftp utility directly from $NSHOME/bin; if you are running the TrafficDirector application on a Windows NT platform, you must enter the command from the TrafficDirector shell. If you do not include a path as part of filename, it defaults to $NSHOME/usr.

To provide the SwitchProbe device with IP filter information using the dvftp utility, follow these steps:

Step 1   Verify that you have added the agent to the TrafficDirector application and specified the monitor interface.

---

Note When you pass the agent name as a parameter to the dvftp utility, it downloads the information to the interface you specified for that agent in the file $NSHOME/usr/agent.lst.

---

Step 2   Create a text file containing the IP filter information for the hosts you want to include or exclude. (You can save this file under a name you select.)

Step 3   To run the dvftp utility, enter the following command:

Setting IP-DATAFILTER from Command-Line Mode

As an alternative to using the dvftp utility for IP filter configuration, you can set the contents of the IP-DATAFILTER object directly from the command line. To do so, follow these steps:

Step 1   Access the Agent Configuration Utility.

Step 2   To access command-line mode, enter 11 and press Enter.

Step 3   Enter the following command:

For example, the following command configures interface 3 to exclude for collection all packets from host 192.168.143.x. Use the get command to check the IP-DATAFILTER information:

Configuring SNMP Trap Ports and Destinations

SwitchProbe devices generate SNMP traps when alarm thresholds are crossed or when there are changes in PVC status. You configure both the port(s) and destination addresses you need for SNMP traps.

Specify the port to which you want the agent to send using the trap_port command-line object.

Specify the hosts to which you want the agent to send traps by maintaining the trap destination table using the TrafficDirector dvadmin utility.

Specifying Trap Ports

By default, all SNMP traps that the SwitchProbe device generates are sent to the TrafficDirector application at port 395. You can also configure the device to send traps to port 162, or to both ports.

The trap_port object contains the number of the port to which the SwitchProbe device sends SNMP traps. This object can contain the following values:

• 395 (default)
  
  
• 162
  
  
• Both 395 and 162
  
  

To specify the ports to which you want the SwitchProbe device to send all SNMP traps, follow these steps:

Step 1   Access the Agent Configuration Utility.

Step 2   To access command-line mode, enter 11 and press Enter.

Step 3   Do one of the following:

• To direct all traps to port 162, enter the following command:
  
  

  set trap_port 162

• To direct all traps to port 395, enter the following command:
  
  

  set trap_port 395

• To direct all traps to both port 395 and port 162, enter the following command:
  
  

  set trap_port 162 395

Using Cisco Discovery Protocol

The Cisco Discovery Protocol (CDP) function is supported on all SwitchProbe devices running firmware Release 4.7 or greater.

CDP allows Cisco Systems' network management applications to automatically discover and learn certain configuration information about network devices that support the CDP protocol.

To provide this functionality, periodic CDP messages are sent from the SwitchProbe device to allow the network management applications to discover the device. These messages are sent out only on the manage interface, although the CDP messages can be seen by all monitor interfaces. After the device has been discovered, you can poll it to gather specific configuration information for that device.

Using the FASTMIB Feature

All Fast Ethernet and FDDI agents include a FASTMIB feature that lets you configure the device to improve the tracking of RMON1 statistics at the first indication of dropped packets.

• When you enable the FASTMIB feature and the device starts dropping packets, it indicates that greater emphasis is placed on tracking RMON1 statistics than RMON2 statistics. As a result, the device can continue tracking MAC-layer statistics during periods of extremely heavy use.
  
  
• When you disable the FASTMIB feature and the device starts dropping packets, it indicates that less emphasis is placed on tracking RMON1 statistics. The FASTMIB feature is enabled by default.
  
  

To change the FASTMIB feature, follow these steps:

Step 1   Access the Agent Configuration Utility.

Step 2   To access command-line mode, enter 11 and press Enter.

Step 3   Use the command get agent_options fastmib to check the current status of the FASTMIB feature.

Step 4   Enable or disable this feature as follows:

• To enable the FASTMIB feature, enter the command
  set agent_options fastmib on.
  
  
• To disable the FASTMIB feature, enter the command
  set agent_options fastmib off.
  
  

Assigning a Locally Administered Address (Token Ring Interfaces)

To identify the location of a SwitchProbe device, you can assign a locally administered address (LAA) that changes the MAC address of the Token Ring interface. You configure the LAA using command-line mode on the agent console.

To configure the LAA, follow these steps:

Step 1   Access the Agent Configuration Utility main menu.

Step 2   To access command-line mode, enter 11 and press Enter.

Step 3   Enter the following command:

set mac_addr <local area address>

where <local area address> is a new MAC address you want to assign to the Token Ring interface.

For example:

set mac_addr 00-80-8C-01-00-42.

Step 4   To return to the Agent Configuration Utility main menu, enter quit and press Enter.

The Agent Configuration Utility main menu is displayed again. The new values do not take effect until you reset the SwitchProbe agent. To do so, see "Resetting a SwitchProbe Agent" in "Configuring SwitchProbe Devices."

---

Note If you want to use the original MAC address (as assigned by Cisco Systems) after you assign a locally administered MAC address, you must set the local MAC address to 00-00-00-00-00-00.

---

Establishing a Roving Agent for Full RMON Analysis

You can establish the SwitchProbe device as a roving agent to achieve full RMON analysis on a specific switch port or other network device port on demand.

Roving is used in conjunction with mini-RMON. For example, you can set up an external proxy agent to provide continuous mini-RMON support for all ports, then use the same agent as a roving agent to achieve full RMON analysis on a particular port on demand.

Although you can use a single SwitchProbe model as both a proxy RMON agent and a roving agent, they are two separate features—both are dependent on the device being monitored. For example, a network device might support proxy RMON but not roving.

To monitor a network device (such as a switch) with a roving agent, the device must support roving. A device supports roving when it meets the following two requirements:

• There is an analyzer port, or a port that is not transmitting network traffic that you can designate as an analyzer port.
  
  
• The device supports mirroring, the ability to direct a copy of traffic from a monitor port to an analyzer port where the roving SwitchProbe device can view that traffic.
  
  

Making the Roving Connection

Roving RMON involves a physical connection between the SwitchProbe device and the switch. Typical roving RMON configuration for a switch includes using one or more switch ports as a monitor port and one switch port as an analyzer port. The monitor port is the port on which you want to examine traffic; the analyzer port is the port where an external SwitchProbe device connected to the switch views that traffic.

You can use any dual-port SwitchProbe device as a roving agent. The agent ports must be of the same media type and configured as shown in Table 10-7.

Posted: Wed Oct 2 08:01:10 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.