Svc Operation; Svc Signaling - Bay Networks Baystream 7 Notice

When the active link on the slave node misses the polling by the bi-directional
procedure values that you configured in the Error Threshold and Monitored
Events Site Manager parameters, the following conditions occur:
•
•
•
When a switchover occurs successfully, information about Cross Net inactive
status of PVCs is lost. All PVCs status will come up in the active state on the
newly activated link.
When a switchover occurs successfully, all configured PVCs on the RNNI
interface will become active on the newly activated link regardless of the state of
PVCs before the switchover.
All SVC connections may not be torn down when a switchover between links
occurs. The SVC connections may be left in the "half connected" state. This
condition is similar to the bouncing of UNI SVC interface on a BayStream
software release prior to Revision 7.3.

SVC Operation

The Annex A link management and selection procedures described in the previous
section are used to determine the active link for SVC operation. Either the master
or slave node can initiate LAPF procedures on the active link.

SVC Signaling

SVC signaling is based on FRF.4 signaling. The master node must be configured
as the UNI DTE device. The slave node must be configured as the UNI DCE
device and assigns DLCIs at the interface. This eliminates the possibility of
assigning the same DLCI to different connections (know as a glare condition).
BayStream must be configured as the UNI DCE device for SVC support on the
Resilient NNI interface and SVC calls are rejected based on FRF.4 signaling. The
Resilient NNI SVC interface does not support the ability to overbook CIR
(Committed Information Rate). This means that if an SVC call requests for a CIR
value that is greater than the port available throughput, it will be rejected.
115385-D Rev 01
The state of the active link will be down
All PVC's will be marked as inactive
Asynchronous cross net update (if enabled) packets will be sent to the remote
ends
BayStream Multiservice Software Version 7.3
BayStream 7.3 Documentation Change Notice
21