A: The length of the access list on an interface is taken into account
when formulating the delay factor. An on-average delay factor is taken into
account, independently of where the rule occurs in the list.
A: Traffic that has a source or destination end system (or both)
that is not in the baseline model is displayed in the Remote Networks Report.
To consider the effects of such traffic on the existing model, edit that traffic
so it references two known end systems which would most closely follow the
path of the original unmapped traffic.
To accomplish this:
Display the Communicating Pairs Report and filter for the Remote Network.
This gives you a list of traffic that originates or ends from an unknown
Sort the resulting report by source address.
Select as many entries as possible that can be mapped into any one
Click on the "Edit" button.
The "Task Manager" window appears with the Edit Traffic task highlighted.
Follow the task steps to change the IP address of the selected report
Repeat steps 3 through 6 for all unmapped traffic that you want considered.
A: The Performance Service Manager computes utilization and delay
at steady state. The resulting packet rate on a Frame Relay circuit will be
some (constant) number, and utilization will be relative to bandwidth. In
this situation, changing CIR is equivalent to changing bandwidth, and utilization
will vary inversely with bandwidth.
Because NSM does not model for transient analysis, you have to model both
the "average" as well as the "worst" case in different scenarios to see
whether CIR is exceeded.
NSM will provide information with regards to an average, whether you are
within your subscription, and how much is available for bursts. It is recommended
that this value be used as a measure of how much freedom you have for bursting
rather than to change the traffic inputs and recompute the "averages."