MTP3:Configuration of layer
From TBwiki
(Difference between revisions)
(added category) |
m (needs revising edit) |
||
| Line 1: | Line 1: | ||
| − | General guidelines for configuration of MTP3 | + | General guidelines for configuration of MTP3 include the following: |
#The MTP3 [[MTP3:General Configuration|general allocation]] must precede all other messages (other configuration MTP3 alloc, get, states and stats). The response of this message is a MTP3 handle. | #The MTP3 [[MTP3:General Configuration|general allocation]] must precede all other messages (other configuration MTP3 alloc, get, states and stats). The response of this message is a MTP3 handle. | ||
#The MTP3 [[MTP3:Userpart Configuration|Userpart allocation]] must be made (with the MTP3 handle from step 1) for a particular variant. The response of this message is a MTP3 Userpart handle. | #The MTP3 [[MTP3:Userpart Configuration|Userpart allocation]] must be made (with the MTP3 handle from step 1) for a particular variant. The response of this message is a MTP3 Userpart handle. | ||
#The MTP3 [[Toolpack:Create an MTP3 Linkset|Linkset allocation]] must be made (with the MTP3 handle from step 1 and the Userpart handle from step 2) for a particular [[OPC]] and a particular adjacent [[DPC]]. The response of this message is a MTP3 Linkset handle. | #The MTP3 [[Toolpack:Create an MTP3 Linkset|Linkset allocation]] must be made (with the MTP3 handle from step 1 and the Userpart handle from step 2) for a particular [[OPC]] and a particular adjacent [[DPC]]. The response of this message is a MTP3 Linkset handle. | ||
| − | #The MTP3 | + | #The MTP3 Link allocation must be made (with the MTP3 handle from step 1, Linkset handle from step 3 and the unique identifier of the MTP2 Link) to connect with the MTP2 link layer. The response of this message is a MTP3 Link handle. |
#The MTP3 [[Toolpack:Create an MTP3 Route|Route allocation]] must be made (with the MTP3 handle from step 1 and Linkset(s) handle from step 3) to create a self-route and a route to a specific or to a range of DPC. The response of this message is MTP3 Route handle. | #The MTP3 [[Toolpack:Create an MTP3 Route|Route allocation]] must be made (with the MTP3 handle from step 1 and Linkset(s) handle from step 3) to create a self-route and a route to a specific or to a range of DPC. The response of this message is MTP3 Route handle. | ||
Revision as of 10:32, 28 March 2018
General guidelines for configuration of MTP3 include the following:
- The MTP3 general allocation must precede all other messages (other configuration MTP3 alloc, get, states and stats). The response of this message is a MTP3 handle.
- The MTP3 Userpart allocation must be made (with the MTP3 handle from step 1) for a particular variant. The response of this message is a MTP3 Userpart handle.
- The MTP3 Linkset allocation must be made (with the MTP3 handle from step 1 and the Userpart handle from step 2) for a particular OPC and a particular adjacent DPC. The response of this message is a MTP3 Linkset handle.
- The MTP3 Link allocation must be made (with the MTP3 handle from step 1, Linkset handle from step 3 and the unique identifier of the MTP2 Link) to connect with the MTP2 link layer. The response of this message is a MTP3 Link handle.
- The MTP3 Route allocation must be made (with the MTP3 handle from step 1 and Linkset(s) handle from step 3) to create a self-route and a route to a specific or to a range of DPC. The response of this message is MTP3 Route handle.
Configuration notes
General guidelines for configuration of MTP3 for a proper operation include the following:
- Step 2 can be performed for 1 to the maximum number of configured Userparts
- Step 3 can be performed for 1 to the maximum number of configured of Linksets
- Step 4 can be performed for 1 to the maximum number of configured Links per Linkset
- Step 5 must be performed for 1 time for the “self-route” and 1 to the maximum number of configured Routes
