TM
FrameSaver SLV and NetScout Manager Plus
Errata
Document Number 9024-A2-GK40-00
May 1998
This document is an errata to the FrameSaver SLV 9x24 User’s Guide
(Document No. 9024-A2-GB20-00).
The information in this document is not available for general distribution. The
NetScout Manager Plus application is scheduled for availability in July.
This errata includes:
Significant features of NetScout Manager Plus.
Hardware and software needed if you want to get these features.
Installation and setup of NetScout Manager Plus software and graphs.
Configuration of NetScout Manager Plus.
Setup of the reports and graphs.
Screens specific to FrameSaver SLV data collection and display.
The NetScout Advantage
NetScout Manager Plus features:
9024-A2-GK40-00
Large central site location: Layers 2 through 7 monitoring,
Remote Probe location: Layers 1 through 3 monitoring
RMON2 customization
Flexible, customized, drill-down tool set
Historical and real-time analysis and reporting
LAN, WAN, and switched LAN support
Protocol analysis
Threshold alarming
Web access
Familiar interface (almost identical to both Motif and Windows environments)
Integrates with other management systems
May 1998
1
See the sections that follow to make sure you have the necessary hardware and
software to support this application.
Minimum Hardware Required
Minimum hardware requirements for each NetScout NMS application are listed in
the table below.
Management Platform
System Hardware Needed
NetScout Manager Plus
Sun SPARC station or compatible station, with
SunOS 4.1.3:
CD-ROM drive
Minimum RAM: 48 MB
Minimum free space: 80 MB
HP 9000, Series 700,
IBM RS/6000,
NCR Unix SVR4, or
Fujitsu DS/90 Unix SVR4:
CD-ROM drive
Minimum RAM: 48 MB
Minimum free space: 40 MB
NetScout Manager Plus for Windows
IBM PC or compatible PC
CD-ROM drive
Minimum RAM: 32 MB
Minimum free space: 25 MB
Super VGA (800 x 600 resolution) or higher,
with 256 colors
SQL Server, if using Trend Reporter
2
May 1998
9024-A2-GK40-00
Minimum Software Required
See the table below to determine whether you need to order additional software
to support FrameSaver SLV units.
Management Platforms
System Software Needed
NetScout Manager Plus
Sun Systems:
– SunOS 4.1.3 or
Solaris 2.5 or higher, with
OpenWindows 3.3 or higher with Motif, and
SunOS Patch #100444-x without Motif or
Motif Window Manager 1.2.4 and
OpenWindows 3.3 or higher
– NetScout User History Viewer, with
Apache 1.2.5 web server, Perl 5.004_04
with GD and GIF graph packages, and
NetScout Manager User History Viewer
– Netscape Communicator 4.04
HP 9000, Series 700:
– HP-UX 9.0.5 or higher, with
– Motif Window Manager 1.2 and X11R5
libraries (included with HP-UX)
IBM RS/6000:
– AIX 3.2.4 or higher, with
NetView for AIX 4.1 or higher
– Motif 1.2.4 and X11R5 libraries
NCR Unix SVR4 – No additional software
required.
Fujitsu DS/90 Unix SVR4:
– OSF/Motif 1.2 and X11R5 libraries
NetScout Manager Plus for Windows
Windows NT Workstation with
Winsock-compliant TCP/IP stack or
Microsoft Windows 95, with
Microsoft SQL Server, 6.0 or higher, and the
Microsoft SQL Server Installation CD, where
the 32 Bit SQL Client if using SQL Server for
Trend Reporter
9024-A2-GK40-00
May 1998
3
Using an NetScout Manager Plus NMS Application
For additional information about accessing and managing the FrameSaver SLV
unit through NetScout Manager Plus, refer to the:
NetScout Manager/Plus User Guide (Document No. 2930-610, Revision B) to
help you install the application, monitor traffic, and diagnose emerging
problems on network segments.
NetScout Manager/Plus & NetScout Server Administrator Guide (Document
No. 2930-620, Revision B) to help you configure agents, remote servers, and
report templates using the various NetScout products.
NetScout Probe User Guide (Document No. 2930-170, Revision D) to help
you install and configure NetScout Probe on network segments you want to
monitor, as shown in SLV Application in Chapter 3, Typical Applications.
Installation and Setup of NetScout Graphs
NetScout has developed User History Viewer (UHV) software to support
FrameSaver SLV units. UHV software is separate from, but run in conjunction
with, NetScout Manager Plus.
To use these graphs, you need to:
4
Install the NetScout Manager Plus software.
Install the new graphs and NetScout webserver software.
Configure NetScout Manager Plus.
Configure the specially developed graphs.
May 1998
9024-A2-GK40-00
Installing NetScout Manager Plus
Installation instructions are located in Chapter 2 of the NetScout Manager/Plus &
NetScout Server Administrator Guide. Depending upon your platform, see either:
Installing NSS/NSM/NSM+ Unix Version
Installing NSS/NSM/NSM+ Windows Version
Installing the New NetScout Graphs
A Readme file is provided that leads you through:
Installation of User History Viewer (UHV) software, which contains the new
NetScout graphs.
Configuration of the software.
Launch of the software.
Install and set up your environment exactly as instructed in the Readme file.
Configuring NetScout Manager Plus
For the NetScout Manager Plus main window to appear, make sure your
environment is set up exactly as specified in your NetScout Readme file.
9024-A2-GK40-00
Add frame relay agents to the NetScout Manager.
Configure agent properties.
Monitor the agent and DLCIs.
May 1998
5
Adding FrameSaver SLV Units to your Network
Procedure
1. Bring up the NetScout Manager Plus main window.
2. Select the FrameRelay radio button from the agent type selection bar (on the
left side of the screen).
A list of configured frame relay agents appear in the list box below the
Name and IP Address columns. If this is a new installation of NetScout
Manager Plus, the list box below the selection bar is blank since no agents
are configured yet.
3. Select the Admin radio button from the application selection bar (to the far
right of the screen). Applicable configuration and administration icons appear
in the box below the application bar.
4. Click on the Config Manager icon to open the Configuration Manager main
window.
5. Select the Add... button (down the center of the screen).
6. Minimally, enter the following:
— Agent name
— IP address
— Interface to be monitored
FrameSaver 9124: Enter 10.
FrameSaver 9624: Enter 8.
7. Select the OK button at the bottom of the screen to add the agent, discover
its DLCIs, and return to the Configuration Manager main window.
The frame relay agent just entered appears in the agent list box, with its
DLCIs in the DLCI list box at the bottom of the screen.
8. Select the Test button (fourth button down, center of the screen) to make
sure you can communicate with the agent.
Refer to Adding Frame Relay Agents in Chapter 5 of the NetScout Manager/Plus
& NetScout Server Administrator Guide for additional information.
6
May 1998
9024-A2-GK40-00
Monitoring the Agent Using NetScout Manager Plus
Once the FrameSaver SLV agent has been added to NetScout Manager Plus,
select either the Traffic or Protocol radio button to monitor the newly added
agent, or one of its DLCIs.
NOTE:
Only the Traffic and Protocol radio buttons on the application selection bar
are supported for FrameSaver SLV agents.
The procedure below describes traffic monitoring. The procedure is the same for
protocol monitoring, but you may be prompted to select a Domain Group as well
as an agent or DLCI.
Procedure
To monitor an agent’s traffic using NetScout Manager Plus:
1. Select the Traffic radio button to monitor the newly added agent, or one of its
DLCIs.
2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI
list box (under the agent list box).
3. If you want to monitor one of the agent’s DLCIs, highlight the DLCI to be
monitored.
4. Click on an applicable icon. The selected graphical report should open.
Traffic icons that would be of particular interest are Traffic Monitor and
Short-Term History. In the example below, the Short-Term History icon was
selected for an agent.
9024-A2-GK40-00
May 1998
7
Configuring the Graphs
Netscape 4.04 must be installed on your system to configure and view the data
collected for an agent. The uhist.conf data file needs to be edited before you
begin. This file defines how the graphs will appear.
Variables that must be set include:
Variable
Description
NSHOME
Specifies the base directory of NetScout Manager Plus.
NSHOME must be set because user history (uhist) uses
NetScout Manager Plus data files. However, it does not
modify them in any way.
delay
Specifies how long a wait between each agent poll.
logmax
Specifies the maximum size of the uhist-fetch log file.
maxbuckets
Specifies the maximum size of points that will appear on
a graph.
To configure the software, change to the library directory (/opt/uhist/lib). Then,
8
Start the user history (uhist) software.
Verify that data is being collected.
Add agents to the uhist software.
Verify that the polling process is gathering data for each agent.
May 1998
9024-A2-GK40-00
Starting the User History Software
Procedure
To start the software:
1. From root, type the /opt/uhist/bin/start-uhist command. This command
must be run with root privilege.
This starts the web server and the agent poller.
2. Once started, exit back to the user shell and start your Netscape 4.04
browser.
3. Go to the http://myhostname URL. Your host name is the name of the Sun
SPARC or compatible station on which the software is installed.
The main User History Viewer window opens.
9024-A2-GK40-00
May 1998
9
4. Select View Data Collector Log to check the user history log for errors.
Progress and problems are logged as they occur. For each poll, the log lists
the date and time, followed by the tasks completed.
If there are errors, a Failed error message appears. Contact your System
Administrator.
10
May 1998
9024-A2-GK40-00
Adding Agents to the Software
Procedure
To add frame relay agents to the uhist software:
1. Select the Netscape browser’s Back button to return to the main User History
Viewer window.
2. Click on Administer Agent List. The Agent List appears, showing all the
agents that have been added to the uhist software, if any.
3. Select the Add button. The Add Agent window opens.
4. Enter the agent name exactly as entered in NetScout Manager Plus.
This is a case-sensitive field. If the name is not entered exactly as entered
into NetScout Manager Plus, you will not be able to retrieve this agent’s data.
5. Select the Add Agent button.
Repeat Steps 1 through 4 until all agents entered into NetScout Manager
Plus are entered into the uhist software.
9024-A2-GK40-00
May 1998
11
Verifying that Agent Data is Being Gathered
Procedure
To verify that data is being gathered for an agent:
1. Press the Top button to return to the main User History Viewer window.
2. Select View Graphs. Make sure you have allowed time for polling and data
gathering to take place for the agent.
3. Click on the Agent box to display the Agent list, and select an agent so it is
displayed in the Agent box.
The first report on the Report list is Tx Bit Burst Analysis. A graph should
appear a few seconds after an agent is selected.
4. Select other reports as you selected an agent.
12
May 1998
9024-A2-GK40-00
Viewing NetScout Manager Plus Graphs
The following NetScout graphical reports support FrameSaver SLV units,
integrating the new service level verifier capability provided by FrameSaver SLV
units:
The following new reports support FrameSaver SLV units:
Transmit Bit Burst Analysis
Round Trip Network Average Latency
Data Delivery Success Rate
Transmit Frame Size Distribution
LMI Availability
DLCI Availability
Protocol Utilization
Error Report
Usage Report
A graph summary report is also provided.
Refer to Chapter 10, Generating Reports, in the NetScout Manager/Plus &
NetScout Server Administrator Guide for additional information about reports.
9024-A2-GK40-00
May 1998
13
Transmit Bit Burst Analysis
This graph shows network utilization bursting details to aid in determining the
cause of frame relay lost packets and/or excessive network latency. Tx Bit Burst
Analysis is measured in megabits and shows the exact distribution of transmitted
data in relation to the DLCI’s CIR and excess burst size.
The color displayed indicates whether the DLCI is or is coming close to
exceeding its purchased CIR and excess burst size.
Color
% of CIR
Indication
Green
Less than 100 %
Packets are within CIR.
Red
100–200 %
Packets are at or over CIR.
Yellow
200–300 %
Packets are two times greater than the contracted
CIR.
Blue
300–400 %
Packets are three times greater than the contracted
CIR.
Pink
More than 400 %
Packets are four times greater than the contracted
CIR.
When zero CIR has been configured, the percentage breakdowns are based on
link speed instead of DLCI speed.
If utilization is consistently under 50 % of CIR, the CIR contracted for should be
downgraded. If over 100 %, the DLCI may be ready for its CIR to be upgraded.
14
May 1998
9024-A2-GK40-00
When a DLCI is overutilizing the network, select Graph Summary from the main
User History Viewer window. This summary combines this graph with three other
graphs for easy comparison (see page 24). Compare the Tx Bit Burst Analysis
graph against the following other graphs to determine the cause:
Data Delivery Success Rate to see if frames are being dropped.
Round Trip Network Average Latency to see if frame size is impacting
latency.
Round Trip Network Average Latency
This graph shows how fast the network is moving traffic. Latency is the amount
of time it takes a frame relay Ping frame to travel from one CPE end point to
another and back. The times at which an average of the frame relay Pings are
calculated is shown along the bottom, while the delay is shown in milliseconds.
Any excessive spikes or increases in latency should be investigated further. It
could indicate a network problem, or it could indicate that the DLCI is
oversubscribed, exceeding CIR, and is sending frames that are filling up the
network switch’s egress queue, delaying network traffic.
To determine the exact cause of the delay, select Graph Summary from the main
User History Viewer window. This summary combines this graph with three other
graphs for easy comparison (see page 24). Compare the Round Trip Network
Average Latency graph against the following graphs to determine the cause:
9024-A2-GK40-00
Tx Bit Burst Analysis to see distribution of transmitted data in relation to the
DLCI’s CIR.
Tx Frame Size Distribution to see the size of the packets that were dropped.
May 1998
15
Data Delivery Success Rate
This graph shows the exact number of bits that were successfully delivered, as
well as those that did not get delivered to the end point node for a selected DLCI.
Data Delivery Success Rate is measured in kilobits over time. The color
displayed indicates whether packets are being delivered.
Color
Indication
Green
Volume of data in the packets that were delivered successfully.
Red
Volume of data in the packets that were dropped by the network.
When frames are being dropped, select Graph Summary from the main User
History Viewer window. This summary combines this graph with three other
graphs for easy comparison (see page 24). Compare this graph with these other
graphs to determine the cause:
16
Tx Bit Burst Analysis to see distribution of transmitted data in relation to the
DLCI’s CIR.
Round Trip Network Average Latency to see if frame size is impacting
latency.
Tx Frame Size Distribution to see the size of the packets that were dropped.
May 1998
9024-A2-GK40-00
Transmit Frame Size Distribution
One of the reasons frames may be lost is because the transmit frame size is too
large for processing, or there are too many small frames slowing the network with
overhead. This graph shows the size of the packets.
Tx Frame Size Distribution is measured over time in percent of all transmitted
packets within each of the following ranges:
Color
Packet Size in Bytes
Green
0–127
Red
128–255
Yellow
256 –511
Blue
512–1023
Pink
More than 1024
Select Graph Summary from the main User History Viewer window. This
summary combines this graph with three other graphs for easy comparison (see
page 24). Compare this graph with the following graphs to determine the cause:
9024-A2-GK40-00
Data Delivery Success Rate to see if frames are being dropped.
Round Trip Network Average Latency to see if frame size is impacting
latency.
May 1998
17
LMI Availability
This graph is only available on a trunk, sometimes called a pipe. It shows the
time the LMI on the network interface has been up and active. Use LMI
Availability to verify that the network is operational, and if the network is down, to
determine how long it was down.
If any area of the graph is not green, the network is down. Availability is based
upon 100 % of 24 hours. Based upon this percentage, network down time can be
determined, which could affect service level agreements.
See the Frame Relay LMI performance statistics in Chapter 10, Displaying
System Information, of the FrameSaver SLV 9x24 User’s Guide to determine
what caused the network to go down.
18
May 1998
9024-A2-GK40-00
DLCI Availability
This graph shows the time the DLCI has been up and active. Use DLCI
Availability to verify that the DLCI is operational, and if the DLCI is down, to
determine how long it has been down.
If any area of the graph is not green, the DLCI is down. Availability is based upon
100 % of 24 hours. Based upon this percentage, DLCI down time can be
determined.
See the PVC Performance Statistics in Chapter 10, Displaying System
Information, of the FrameSaver SLV 9x24 User’s Guide to determine what
caused the DLCI to go down.
9024-A2-GK40-00
May 1998
19
Protocol Utilization
This graph shows the historical view of protocol types used most often in frames
passing through the DLCI. Over time, network resources can be planned for and
justified. Protocol Utilization is used primarily for capacity planning. This graph is
provided via a browser; the NetScout Manager Plus Protocol History icon does
not currently support FrameSaver SLVs.
To view real-time protocol utilization for a DLCI, select the Protocol Monitor icon
while both the FrameRelay and Protocol radio buttons are selected.
20
May 1998
9024-A2-GK40-00
A total for all protocols going through the DLCI is calculated based upon the
DLCI’s data rate and CIR, then used to calculate a percentage for each protocol
over time. The utilization percentage is scaled to the DLCI’s data rate, which
changes dynamically each time the graph is updated or refreshed.
When zero CIR has been configured, the speed of the trunk’s capacity is used in
the calculations instead of the speed of the DLCI’s allocated capacity.
The color displayed indicates the supported protocols used in the frames.
9024-A2-GK40-00
Historical View
Real-time View
Color
Protocol
Color
Protocol
Description
Red
IP
Blue
IP
Internet Protocol
Yellow
IPX
Hot Pink
IPX
Internet Package Exchange
Green
NETBEUI
Green
NETB
Net BEUI
Pink
ATALK
Gray
ATALK
Appletalk
Blue
VINES
Bright Green VINES
Banyan Vines,
Ethertype 0x0BAD
(encapsulation of Ethernet)
Purple
VINESNEW
—
—
New Banyan Vines,
Ethertype 0x80C4
(encapsulation of
Frame Relay)
Orange
SNA
Blue-Green
SNA
Systems Network
Architecture
Yellow-Grey
NET~
Orange
NET~
Others not mentioned in
this list
May 1998
21
Error Report
Use this graph to determine the degree of traffic congestion on the network, and
the reason some frames may have been discarded.
The number of errors counted over time are shown. The color displayed indicates
the kinds of errors detected.
Color
Error
Indication
Green
BECNs
Backward explicit congestion notification has
been sent by the network, warning that
outbound frames may encounter congestion and
may be dropped.
Red
FECNs
Forward explicit congestion notification has
been sent by the network, warning that inbound
frames may encounter congestion and may be
dropped.
Yellow
RxDE
Received data on a management PVC is
marked discard eligible, so the network can
discard the lower-priority frame when there is
congestion.
Blue
TxDE
Transmit data on a management PVC is marked
discard eligible, so the network can discard the
lower-priority frame when there is congestion.
BECNs and FECNs indicate network congestion issues. RxDE and TxDE
indicate that the DLCI is partly responsible for the network congestion; the DLCI
has exceeded its contracted CIR.
22
May 1998
9024-A2-GK40-00
Usage Report
This graph shows the DLCI’s utilization of its allocated bandwidth. When the
DLCI’s allocated bandwidth is underutilized, as in the example below, it is time to
renegotiate CIR and excess burst size agreements.
Used primarily for capacity planning or in CIR negotiations.
The DLCI’s capacity is calculated based upon its data rate and CIR. When zero
CIR has been configured, the speed of the trunk’s capacity is used in the
calculations instead of the speed of the DLCI’s allocated capacity.
9024-A2-GK40-00
May 1998
23
Graph Summary
For a more complete view of network traffic, this graph summary brings together
the information needed to determine the cause of frame relay lost packets and/or
excessive network latency. A patent is pending on this graph combination.
Network service providers can use this screen to help determine whether their
network or the customer’s data was the cause for a missed service level
agreement (SLA).
Because four graphs are combined onto one window, a slightly longer wait is
needed until these graphs appear. Correlate the time at which a problem
occurred to the following:
24
Tx Bit Burst Analysis shows the exact distribution of transmitted data in
relation to the DLCI’s CIR.
Round Trip Network Average Latency shows any spikes or increases in
latency.
Data Delivery Success Rate shows the exact number of bits that were
delivered to the end point node. The rates shown are in relation to the
sending and receiving node’s line speeds, and the CIR. The graph also
shows dropped packets.
Tx Frame Size Distribution enables you to see the size of the packets that
were dropped.
May 1998
9024-A2-GK40-00
In most cases, transmission characteristics of the customer’s data rather than
the network is the cause of apparent network problems. This summary allows
you to determine the following:
H
Overutilization of the network, trying to deliver amounts of data well over
CIR.
H
Data frames are too large.
H
More packets are being sent than the receiving node can receive due to
physical circuit capacity.
Any of these will cause the network switch’s egress queue (outgoing buffer) to fill,
increasing latency and data loss.
Copyright E 1998 Paradyne Corporation
9024-A2-GK40-00
May 1998
25