VLL Service Configuration Commands
Page 340 7750 SR OS Services Guide
Context config>service>epipe>spoke-sdp
config>service>fpipe>spoke-sdp
config>service>apipe>spoke-sdp
config>service>ipipe>spoke-sdp
config>service>cpipe>spoke-sdp
Description This command specifies the bandwidth to be used for VLL bandwidth accounting by the VLL CAC
feature.
The service manager keeps track of the available bandwidth for each SDP. The maximum value is the
sum of the bandwidths of all constituent LSPs in the SDP. The SDP available bandwidth is adjusted
by the user configured booking factor.
If an LSP consists of a primary and many secondary standby LSPs, then the bandwidth used in the
maximum SDP available bandwidth is that of the active path. Any change to and LSP active path
bandwidth will update the maximumn SDP available bandwidth. Note however that a change to any
constituent LSP bandwidth due to re-signaling of the primary LSP path or the activation of a
secondary path which causes overbooking of the maximum SDP available bandwidth causes a
warning and a trap to be issued but no further action is taken. The activation of a bypass or detour
LSP in the path of the primary LSP does not change the maximum SDP available bandwidth.
When the user binds a VLL service to this SDP, an amount of bandwidth equal to bandwidth is
subtracted from the SDP available bandwidth adjusted by the booking factor. When the user deletes
this VLL service binding from this SDP, an amount of bandwidth equal to bandwidth is added back
into the SDP available bandwidth.
If the total SDP available bandwidth when adding this VLL service is about to overbook, a warning is
issued and the binding is rejected. This means that the spoke-sdp bandwidth does not update the
maximum SDP available bandwidth. In this case, the spoke-sdp is put in operational down state and a
status message of “pseudowire not forwarding” is sent to the remote SR-Series PE node. A trap is also
generated. The service manager will not put the spoke-sdp into operational UP state until the user
performs a shutdown/no-shutdown of the spoke-sdp and the bandwidth check succeeds. Thus, the
service manager will not automatically audit spoke-sdp’s subsequently to their creation to check if
bandwidth is available.
If the VLL service contains an endpoint with multiple redundant spoke-sdp’s, each spoke-sdp will
have its bandwidth checked against the available bandwidth of the corresponding SDP.
If the VLL service performs a pseudowire switching (VC switching) function, each spoke-sdp is
separately checked for bandwidth against the corresponding SDP.
Note this feature does not alter the way service packets are sprayed over multiple RSVP LSPs, which
are part of the same SDP. In other words, by default load balancing of service packets occurs over the
SDP LSP’s based on service-id, or based on a hash of the packet header if ingress SAP shared
queuing is enabled. In both cases, the VLL bandwidth is not checked against the selected LSP(s)
available bandwidth but on the total SDP available bandwidth. Thus, if there is a single LSP per SDP,
these two match.
If class-forwarding is enabled on the SDP, VLL service packets are forwarded to the SDP LSP which
the packet forwarding class maps to, or if this is down to the default LSP. However, the VLL
bandwidth is not checked against the selected LSP available bandwidth but on the total SDP available
bandwidth. If there is a single LSP per SDP, these two match.
If a non-zero bandwidth is specified for a VLL service and attempts to bind the service to an LDP or a
GRE SDP, a warning is issued that CAC failed but the VLL is established. A trap is also generated.
The no form of the command reverts to the default value.
To Next Page
Loading...
