|
|
This chapter describes DLCI monitoring for WAN SwitchProbe devices, and VPI/VCI monitoring for ATM SwitchProbe devices.
WAN SwitchProbe devices provide support for Permanent Virtual Circuit (PVC) monitoring over WAN Frame Relay segments. You can configure these devices to create/discover up to 256 virtual interfaces for each data-link connection identifier (DLCI) on the monitored WAN Frame Relay segment.
After a DLCI virtual interface is created/discovered, it is treated as a physical interface, allowing you to monitor each DLCI as you would an entire SwitchProbe agent. For example, you can use a number of TrafficDirector applications to view detailed statistics of any DLCI on a WAN segment.
Properties (domains, traps, and so on) are assigned to the entire WAN segment and are inherited by all DLCIs on the segment.
For each DLCI the SwitchProbe device sees on the WAN network, the device automatically creates a virtual interface that you can monitor as you would any other agent. This automatic discovery feature is enabled by default. Therefore, in most cases you will connect the SwitchProbe device to the network and specify Frame Relay as the WAN encapsulation protocol. For more information, see "Changing the Encapsulation Protocol (WAN Only)" in "Initialization." The SwitchProbe device automatically learns any DLCI on the monitored network.
If the WAN segment you are monitoring does not use a Frame Relay management protocol such as LMI or Annex D, you must manually specify which DLCIs you want to monitor.
By default, when the pvc_discovery option is enabled in the SwitchProbe device, the device automatically discovers any PVCs on the attached WAN Frame Relay segments that are running a management protocol. The SwitchProbe device reads the management protocol packets to obtain the DLCI and creates a virtual interface for each DLCI found on the attached segment.
If the management protocol is LMI, the SwitchProbe device automatically discovers both the DLCI number and the Committed Information Rate (CIR), and creates a corresponding DLCI virtual interface.
If the management protocol is Annex D, Annex A, and ITU-T, the SwitchProbe device automatically discovers the DLCI number and creates a corresponding DLCI virtual interface. To derive the CIR for the newly created interface, the SwitchProbe device first looks to NVRAM for a matching DLCI entry, and if it finds one, uses the CIR specified in NVRAM. If the SwitchProbe device does not find a matching DLCI entry, it uses the speed of the WAN interface as the CIR.
If an attached WAN Frame Relay segment is not running a management protocol, you can manually specify which DLCIs you want to monitor as an interface.
You can also manually specify the CIR of DLCI interfaces that the SwitchProbe device automatically creates. As explained in the previous section, DLCI interfaces that the SwitchProbe device automatically creates on segments running management protocols such as Annex D, Annex A, and ITU-T determine the speed of the WAN interface based on the management protocol. However, if you know the CIR is different, you can manually specify the DLCI and CIR of the PVC, then reboot the SwitchProbe device.
After automatically rediscovering the PVC, the SwitchProbe device will use the CIR speed that you specified for the DLCI, instead of trying to determine the speed of the WAN interface based on a management protocol.
There are two ways to manually specify the DLCIs you want to monitor as an interface:
To add DLCIs you want to monitor, delete DLCIs you are no longer interested in, or clear all DLCI interfaces, follow these steps:
Step 1 Select the command-line mode option by entering 11 and pressing Enter.
Step 2 To add DLCIs to a particular interface, enter the following command:
set dlci add <phys_interface> "<dlci_number> <dte_cir> <dce_cir>"
<phys_interface> is the number of the specific WAN physical interface on which you want to create DLCI virtual interfaces. (DLCI virtual interfaces will only be created on the physical interface that you specify.)
<dlci_number > is the number that identifies the DLCI you want to monitor. The SwitchProbe device uses this number as both the name and index number of the DLCI interface.
<dte_cir> is the CIR (in bps) of the DTE traffic on the DLCI interface.
<dce_cir> is the CIR (in bps) of the DCE traffic on the DLCI interface.
Step 3 To delete a specific DLCI on a particular interface, enter the following command:
set dlci delete "<phys_interface> <dlci_number>"
<phys_interface> is the number of the specific WAN physical interface on which you want to remove DLCI virtual interfaces. (DLCI virtual interfaces will only be deleted on the physical interface that you specify.)
<dlci_number > is the number that identifies the specific DLCI you want to delete.
Step 4 To delete all DLCIs on a particular interface, enter the following command:
set dlci clear <phys_interface>
<phys_interface> is the number of the specific WAN physical interface on which you want to delete all DLCI virtual interfaces.
Step 5 Exit the command-line mode by entering quit and pressing Enter.
The Agent Configuration Utility Main Menu is displayed.
All manually configured DLCIs take effect when you reset the SwitchProbe's agent, and only if the pvc_discovery option in the SwitchProbe device is set to off. Refer to Toggle pvc_discovery explained in "Special Interface OptionsWAN" in "Configuration."
To reset the SwitchProbe's agent, see "Resetting a SwitchProbe Device Agent" in "Configuration."
WAN SwitchProbe devices automatically send out SNMP traps when there is a change in PVC status, including any of the following:
By default, the SwitchProbe device sends all traps that it generates as a result of a change in PVC status to the server address specified in menu option 9. If desired, you can specify more modes to receive SNMP traps by using the TrafficDirector dvadmin utility to maintain the agent's trap destination table. You can also configure the SwitchProbe device to send SNMP traps to port 162, 395, or both. For more information, refer to "Configuring SNMP Trap Ports and Destinations" in "Advanced Features."
You can specify the amount of resources the SwitchProbe device reserves for tracking RMON1 and RMON2 statistics for each DLCI interface at boot time. You do so by specifying values for selected RMON1 and RMON2 parameters. The values you specify for these parameters apply to each DLCI interface the SwitchProbe device creates.
For example, if you set the maximum number of DLCI network layer hosts to 4000, the SwitchProbe device allocates enough resources (primarily memory) to track network-layer statistics for 4000 hosts on each DLCI interface. This means that if you automatically discover 50 DLCIs, the SwitchProbe device reserves enough agent resources to track statistics for 200,000 hosts. Therefore, you might want to adjust these DLCI maximums based on your monitoring needs and available SwitchProbe device resources.
Table 9-1 describes the DLCI RMON1 parameters you can configure.
| Select This Parameter... | To Configure | Default Value |
|---|---|---|
[5] Change dlci_sh_buckets | Maximum number of buckets the SwitchProbe device uses to store short-term history statistics. | 10 |
[6] Change dlci_lh_buckets | Maximum number of buckets the SwitchProbe device uses to store long-term history statistics. | 10 |
[7] Change dlci_sh_interval | Interval at which the SwitchProbe device gathers and stores short-term history statistics. | 180 |
[8] Change dlci_lh_interval | Interval at which the SwitchProbe device gathers and stores long-term history statistics. | 1800 |
Table 9-1 describes the DLCI RMON2 parameters you can configure.
| Select This Parameter... | To Configure | Default Value |
|---|---|---|
[5] Change dlci_nl hosts | Maximum number of hosts for which the SwitchProbe device tracks network-layer statistics. | 4000 |
[6] Change dlci_al_hosts | Maximum number of hosts for which the SwitchProbe device tracks application-layer statistics. | 8000 |
[7] Change dlci_nl_matrix | Maximum number of conversations for which the SwitchProbe device stores network-layer statistics. | 6000 |
[8] Change dlci_al_matrix | Maximum number of conversations for which the SwitchProbe device stores application-layer statistics. | 12000 |
To set RMON1/RMON2 statistics for DLCIs, follow these steps:
Step 1 Access the Agent Configuration Utility.
Step 2 Enter 8 and press Enter.
Step 3 Select the WAN interface you want to configure.
Step 4 Enter 31 and press Enter.
Step 5 Do one of the following:
To configure RMON1 DLCI parameters, enter 15.
or
To configure RMON2 DLCI parameters, enter 16.
Step 6 Do one of the following:
If you entered 15, select the RMON1 parameters you want to configure as explained in Table 9-1.
or
If you selected 16, select the RMON2 parameters you want to configure as explained in Table 9-2.
Step 7 Enter 12 to reset agent and press Enter.
ATM SwitchProbe devices provide support for PVC monitoring over ATM segments. You can configure these SwitchProbe devices to create up to 256 virtual interfaces for each specified Virtual Path Identifier/Virtual Channel Identifier (VPI/VCI) on the monitored ATM segment.
After you create a VPI/VCI virtual interface in the device, the virtual interface is treated as a physical interface, allowing you to monitor each VPI/VCI as you would an entire SwitchProbe agent.
For example, you can use several TrafficDirector applications to view detailed statistics of any VPI/VCI on an ATM segment.
The ATM SwitchProbe device decodes ATM PVC addresses to a 10-bit resolution. By default, all ten bits are used to specify the VCI portion of the PVC, and no bits are reserved to specify the VPI portion of the PVC. This default bit allocation ratio is adequate in a UNI signaling SVC environment where the VPI is normally 0. However, in other signalling environments, PVCs normally use a non-zero VPI.
If the ATM link you are monitoring with the SwitchProbe device uses non-zero VPIs, use the set atm_maxvpibits command to specify the maximum number of bits that need to be reserved for the VPI. The number of bits that will be used for VCI will then be ten minus the number of maxvpibits.
For example, if you set the number of maxvpibits to 3, three bits are used for VPI and 7 bits for VCI. The total number of bits used for VPI and VCI equals 10.
You must be in ATM interface to specify VPI/VCI size. To specify VPI/VCI size, follow these steps:
Step 1 Select the command-line mode option by entering 11 and pressing Enter.
Step 2 Enter the following command for each PVC (on an attached ATM segment) you want the SwitchProbe device to monitor:
set atm_maxvpibits <maxvpibits #>
<maxvpibits #> is the number of bits reserved for the VPI.
To monitor a PVC as an interface in an ATM SwitchProbe device, you must manually specify it by entering the PVC's VPI/VCI combination using the Agent Configuration Utility's command-line mode.
You must be in ATM interface to configure ATM PVCs. To add ATM PVCs to monitor, delete ATM PVCs you no longer need, or clear all ATM PVCs, follow these steps:
Step 1 Select the command-line mode option by entering 11 and pressing Enter.
Step 2 Enter the following command to add PVCs to the SwitchProbe device's NVRAM:
set atm_pvc add <vpi#> <vci#>
<vpi#> and <vci#> combination defines the PVC to be monitored.
Step 3 After you enter the command, you are prompted to enter a dte_atm_address. The DTE ATM address is optional and you should enter it only if you want the device to display the ATM address associated with the PVC.
If desired, enter the ATM address (a 20-byte NSAPA format) of the DTE device.
Enter the ATM address of the DCE device.
Otherwise, press Enter at the prompt requesting a dte_atm_address.
Step 4 You are prompted to enter a protocol. The protocol information is also optional and you should enter it only if the specified PVC is carrying non-IP, null-encapsulated (per RFC 1483) traffic.
If desired, enter the EtherType (in hex) of the protocol.
For example, if the specified PVC is carrying null-encapsulated Appletalk traffic, enter 0806 (hex value for AppleTalk EtherType) and press Enter.
Otherwise, press Enter at the prompt.
Step 5 To delete a PVC from NVRAM, enter the following command:
set atm_pvc delete <vpi#> <vci#>
<vpi#> and <vci#> combination defines the specific PVC to be removed.
Step 6 To delete all PVCs from the SwitchProbe's NVRAM, enter the following command:
set atm_pvc clear
Step 7 Exit the command-line mode by entering quit and pressing Enter.
The Agent Configuration Utility main menu is displayed again.
All manually configured ATM PVCs will not take effect until you reset the SwitchProbe's agent. To reset the SwitchProbe's agent, see "Resetting a SwitchProbe Device Agent" in "Configuration."
Posted: Wed Oct 2 08:31:34 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.