Name | Organization | |
---|---|---|
Patrick Liu | Huawei Techonologies | Partick.Liu@huawei.com |
Suresh B R | Huawei Techonologies | Suresh.B.R@huawei.com |
Mahesh Poojary | Huawei Techonologies | mahesh.poojary@huawei.com |
Phaneendra Manda | Huawei Techonologies | phaneendra.manda@huawei.com |
Bharat Saraswal | Huawei Techonologies | bharat.saraswal@huawei.com |
Priyanka B | Huawei Techonologies | priyanka.b@huawei.com |
Rajakumar Gootla | Huawei Techonologies | rajakumarg@huawei.com |
This project adds Path Computation Element Protocol (PCEP) as a southbound plugin in ONOS.
Add PCEP South Bound Interface (SBI) for MPLS TE tunnel management which will implement TunnelProvider API to support initiating, updating and releasing of PCE initiated tunnels using PCE communication protocol. The implementation will also support learning of existing active tunnels which are on the network.
Implement PCEP protocol handler, which acts as a server to listen on PCEP port 4189 to establish and manage session with PCCs. A channel handler will be created for each PCEP session to maintain the state machine and state of each PCC.
Implement PCEP message handler, which will encode and decode PCEP messages between ONOS PCEP SBI and PCC. Currently the messages supported are Open, KeepAlive, PCInitiate, PCUpd, PCRpt, PCLabelUpd, TERpt, PCLRResv, PCErr and Close.
Implementation supports state synchronization with PCC reporting reporting LSPs’ state to PCEP protocol handler running on ONOS immediately after session established. These report messages are notified to PCEP Tunnel Provider via message listener which in turn will inform the ONOS Core about the existing tunnels in the network. The Report message can also be the result of PCE initiated messages for creating, updating or releasing tunnels. In this case PCEP Tunnel Provider will invoke the respective API to notify ONOS Core about the result of create or update or release tunnels. All communication between PCEP provider and ONOS Core uses Provider Service interface.
The below API are implemented for tunnel provider in PCEP SBI
Arguments: Tunnel, Path
Return Value: None
Details: This API is responsible for setting up a tunnel on the device. It gets the tunnel parameters from the input parameters Tunnel and Path. The API implementation builds the PCInitiate protocol message from the input parameters. The ingress and egress are taken from src and dst members of Tunnel class. The ingress is considered as source for the tunnel and PCInitiate message is sent to ingress device for which a session is already established with the PCEP protocol handler. The explicit route object is built from the link parameter in the input Path class. The API implementation will take care of generating unique ID for sending the message to PCC and mapping the response from PCC. Finally the response is given to ONOS core using PCEP tunnel provider service.
Arguments: Tunnel, Path
Return Value: None
Details: This API is responsible for modifying an existing tunnel on the device. It gets the tunnel parameters from the input parameters Tunnel and Path. The API implementation builds the PCUpd protocol message from the input parameters. To send a PCUpd message the ingress device should have a tunnel which is already created and the PCE must be the owner of this tunnel. The ingress and egress for the tunnel are taken from src and dst of Tunnel class. The ingress is considered as source for the tunnel and PCUpd message is sent to ingress device for which a session is already established with the PCEP protocol handler. The explicit route object is built from link parameter in the Path class. The API implementation will take care of generating unique ID for sending the message to PCC and mapping the response from PCC. Finally the response is given to ONOS core using PCEP tunnel provider service.
Arguments: Tunnel
Return Value: None
Details: This API is responsible for deleting an existing tunnel on the device. It gets the tunnel parameters from the input parameter Tunnel. The API implementation builds the PCInitiate protocol message from the input parameters. To send a PCInitiate message with delete flag set, the ingress device should have a tunnel which is already created and the PCE must be the owner of this tunnel. The tunnel id, ingress and egress for the tunnel are taken from tunnel id, src and dst of Tunnel class. The ingress is considered as source for the tunnel and PCInitiate message is sent to ingress device for which a session is already established with the PCEP protocol handler. The API implementation will take care of generating unique ID for sending the message to PCC and mapping the response from PCC. Finally the response is given to ONOS core using PCEP tunnel provider service.
Open message is used to establish a PCEP session between PCEP peers. This carries various session characteristics like keep alive time, dead time and capability.
Gmpls-capability TLV
Stateful-Pce-capability TLV
Pcecc capability TLV
Keep alive message used to keep the session active and also in response to open messages while session establishment to acknowledge Open messages and session characteristics are acceptable.
Not Applicable
Setup Tunnel API will build the PCInitiate message to setup a tunnel at the PCC. The objects supported in PCInitiate message are
The SRP (Stateful PCE request parameters) object set the unique identifier for mapping request/response between PCEP and PCC.
Symbolic path name TLV
The LSP contains a set of fields used to specify the target LSP, the operation to be performed on the LSP and LSP delegation. It also contains a flag indicating to a PCE that the LSP state synchronization in progress.
LSP identifiers TLV (IPV4)
Symbolic path name TLV
LSP Error code TLV
RSVP Error Spec TLV
The END POINTS object used to specify the source and destination IP addresses of the tunnel.
None.
Explicit route objects contain list of variable length SubObjects.
IPv4 Prefix
IPv6 Prefix
Autonomous System number
SR-ERO SubObject
Path Key SubObject
This object used to specify the requested bandwidth for a TE LSP.
Update Tunnel API will build the PCUpd message to update a tunnel at the PCC. The objects supported in PCUpd message are
The SRP (Stateful PCE request parameters) object set the unique identifier for mapping request/response between PCEP and PCC.
Symbolic path name TLV
The LSP contains a set of fields used to specify the target LSP, the operation to be performed on the LSP and LSP delegation. It also contains a flag indicating to a PCE that the LSP state synchronization in progress.
LSP identifiers TLV (IPV4)
Symbolic path name TLV
LSP Error code TLV
RSVP Error Spec TLV
Explicit route objects contain list of variable length SubObjects.
IPv4 Prefix
IPv6 Prefix
Autonomous System number
SR-ERO SubObject
Path Key SubObject
This object used to specify the requested bandwidth for a TE LSP.
Report message is sent by PCC in response to PCInitiate/PCUpd messages. Report message is also sent for synchronizing LSP state DB between PCC and PCE immediately after the session establishment. The objects supported in PCRpt message are
The SRP (Stateful PCE request parameters) object set the unique identifier for mapping request/response between PCEP and PCC. SRP object is optional in report messages sent for LSP state synchronization.
Symbolic path name TLV
The LSP contains a set of fields used to specify the target LSP, the operation to be performed on the LSP and LSP delegation. It contains a S flag when true indicates to a PCE that the LSP state synchronization in progress.
LSP identifiers TLV (IPV4)
Symbolic path name TLV
LSP Error code TLV
RSVP Error Spec TLV
Record route objects contain list of variable length SubObjects.
IPv4SubObject
IPv6SubObject
LabelSubObject
This object used to report the bandwidth for an existing TE LSP.
This message is sent by PCE to PCC to download the label or update the label map. The same message is also used to clean the label entry. The objects supported are
The SRP (Stateful PCE request parameters) object set the unique identifier for mapping request/response between PCEP and PCC. SRP object is optional in report messages sent for LSP state synchronization.
Symbolic path name TLV
The LABEL object used to specify the label information and must be carried within PCLabelUpd message.
NexthopIPv4addressTlv
NexthopUnnumberedIPv4IDTlv
The FEC object is used to specify FEC information. The types of FEC objects supported are
IPv4 Node ID
IPv6 Node ID
IPv4 Adjacency
IPv6 Adjacency
This message is sent by PCC to PCE to report any changes in the TE DB. The objects supported in TE Report are
TE Object contains a set of fields used to specify target TE node or link. It also contains a flag indicating to a PCE that the TED synchronization in progress.
Routing Universe TLV
Local TE Node Descriptors TLV
Remote TE Node Descriptors TLV
TE Node Descriptors TLV
TE Link Descriptors TLV
TE Node Attributes TLV
TE Link Attributes TLV
This message is bidirectional between PCC and PCE. This message is sent by PCC to PCE for the reservation of label range. This message is sent by PCE to PCC to sent reserved label range for the network. The objects supported in this message are
The SRP (Stateful PCE request parameters) object set the unique identifier for mapping request/response between PCEP and PCC. SRP object is optional in report messages sent for LSP state synchronization.
Symbolic path name TLV
This object carries label range information based on the label type.
This message is sent by either PCC or PCE in several situations like, when a protocol error condition is met, when a request is not compliant with PCEP specification, policy violation, unexpected message etc. The objects supported in this message are
This object is carried in PCErr message to notify PCEP error
When the parameters in open message are not accepted, then PCErr message is sent to PCEP peer with Open object.