Manual
Table Of Contents
- Contents
- About This Guide
- 1. About the FrameSaver SLV
- 2. User Interface and Basic Operation
- 3. Configuration Procedures
- 4. Configuration Options
- Using the Easy Install Feature
- Using RIP with FrameSaver SLV CSU/DSUs
- Entering System Information and Setting the System Clock
- Setting Up the Modem
- Setting Up Auto-Configuration
- Setting Up Dial Backup
- PVC Backup Over the Network Interface
- Setting Up Back-to-Back Operation
- Configuration Option Tables
- Configuring the Overall System
- Configuring Physical Interfaces
- Assigning Time Slots/Cross Connections
- Configuring Frame Relay for an Interface
- Manually Configuring DLCI Records
- Configuring PVC Connections
- Configuring the IP Path List
- Setting Up Management and Communication Options
- Configuring the Criteria for Automatic Backup
- 5. Configuring the FrameSaver SLV Router
- FrameSaver SLV Router Overview
- IP Routing
- Address Resolution Protocol
- Proxy ARP
- Interface Configuration
- Network Address Translation
- Network Address Port Translation
- Dynamic Host Configuration Protocol Server
- DHCP Relay Agent
- Router Security
- Provisioning the Router Interface
- Configuring the Router Using Terminal Emulation
- 6. Security and Logins
- 7. Operation and Maintenance
- 8. Troubleshooting
- 9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features
- 10. Setting Up NetScout Manager Plus for FrameSaver Devices
- 11. Setting Up Network Health for FrameSaver Devices
- A. Menu Hierarchy
- B. SNMP MIBs and Traps, and RMON Alarm Defaults
- C. Router CLI Commands, Codes, and Designations
- D. Router Command Line Summaries and Shortcuts
- E. Connectors, Cables, and Pin Assignments
- F. Technical Specifications
- G. Equipment List
- Index

10. Setting Up NetScout Manager Plus for FrameSaver Devices
10-8
September 2002 9128-A2-GB20-80
Adding SLV Alarms Using a Template
Once DLCIs have been discovered, SLV alarms should be configured and
assigned to each DLCI. OpenLane provides a template for configuring alarms.
DLCI alarms can be configured manually, but using the Paradyne alarm defaults
template greatly reduces configuration time.
The following alarms are configured for each DLCI included in the Paradyne MIB:
These alarms and current values can be found in $NSHOME/usr/slvtemplate.fct,
which is used as a starting point for loading new alarms. This file can be copied
and edited so the alarm threshold values match service level agreement values.
The copied .fct file can then be used to replicate alarm threshold values for all
DLCIs on the unit using the eztrap utility. All .fct files must be in $NSHOME/usr.
To configure alarms manually, see
Adding SLV Alarms Manually
on page 10-11.
NOTE:
Perl must be installed in your system to use the eztrap utility in the procedure
below. If you have an NT system, please install Perl before proceeding.
Procedure
1. Open a terminal window and go to
$NSHOME/usr
.
2. Type
eztrap -i
filename
.fct -o
agentname
.fct
agentname
and press Enter to
run the eztrap utility to create alarm threshold values across all DLCIs for the
copied .fct file.
The message
eztrap done
appears when the .fct file is transferred.
3. From the NetScout Manager Plus main window, with the FrameRelay and
Admin radio buttons still selected, click on the Config Manager icon to open
the Configuration Manager main window.
4. Edit any alarm values that need to be changed.
5. Select the Install button (down the center of the Configuration Manager main
window) to load alarms for the unit. This may take some time, so please be
patient.
See
Editing Alarms
on page 10-9 if any default settings need to be changed.
— Frames Sent (SLVFramesSnt) — Rx DLCI Utilization (SLVrxDLCIUtil)
— Tx CIR Utilization (SLVTxCIRUtil) — Frames Sent Above CIR
(SLVFramesTxAbvCIR)
— Tx DLCI Utilization (SLVTxDLCIUtil) — Average Latency (AverageLatency)
— Frames Received (SLVFramesRec) — Current Latency (CurrentLatency)