Enabling Loopback Detection Using The Technician Interface; Monitoring Loopback Detection Using The Technician Interface; Uni And Nni Traffic Policing Disable; Enabling Traffic Policing Using Technician Interface - Bay Networks Baystream 7 Notice

BayStream 7.3 Documentation Change Notice

Enabling Loopback Detection Using the Technician Interface

For example, you can use the Technician Interface to enable loopback detection
for an interface:
[4:1] $ set wfFrSwDlcmiEntry.wfFrSwDlcmiLoopbackEnable.<circuit number> 1
You can use the Technician Interface to disable loopback detection for an
interface:
[4:1] $ set wfFrSwDlcmiEntry.wfFrSwDlcmiLoopbackEnable.<circuit number> 2

Monitoring Loopback Detection Using the Technician Interface

You can use the Technician Interface to monitor the loopback condition for an
interface:
[4:1] $ get wfFrSwDlcmiEntry.wfFrSwDlcmiLoopbackStatus.<circuit number>

UNI and NNI Traffic Policing Disable

You can enable or disable traffic policing on a user-to-network interface (UNI) or
network-to-network (NNI) interface.
When traffic policing is enabled, any traffic flow over the excess burst rate (the
sum of committed burst and excess burst) is dropped and any traffic flow over the
committed burst rate has the Discard Eligibility (DE) bit set (meaning it is eligible
for discard).
The default value for traffic policing on a UNI or NNI interface is Enable. You
can change this value for an interface using Technician Interface or Site Manager.

Enabling Traffic Policing Using Technician Interface

For example, you can use Technician Interface to enable traffic policing for an
interface:
[4:1] $ set wfFrSwDlcmiEntry.wfFrSwDlcmiBcMeasurementEnable.<circuit number> 1
You can use Technician Interface to disable traffic policing for an interface:
[4:1] $ set wfFrSwDlcmiEntry.wfFrSwDlcmiBcMeasurementEnable.<circuit number> 2
38
BayStream Multiservice Software Version 7.3 115385-D Rev 01