2.24.1.1 MMI Managed Objects for M2PA Busy Link
MMI information associated with vSTP generated M2PA Busy Link can be configured from a DSR NOAM or SOAM from
.Once the MMI API Guide gets opened, use the application navigation to locate specific vSTP managed object information.
The following table lists the managed objects and operations supported for M2PA Busy Link functionality:
Managed Object Name | Supported Actions |
---|---|
m3rloptions | GET, PUT, POST, DELETE |
connectionconfigurationsets | GET, PUT, POST, DELETE |
m3rloptions
- On: Specifies that the feature is enabled.
- Off: Specifies that the feature is not enabled.
POST
Create a file with following content to set value for the m2paSctpRxBusyLink parameter. File name could be anything, for example option name can be used as filename:
Execute the following command on Active SOAM to update the data:
/vstp/m3rloptions –v POST –r <filename>.json
{
"cnvAInat": 1,
"cnvCgda": false,
"cnvCgdi": false,
"cnvCgdn": false,
"cnvCgdn24": false,
"cnvClgItu": "Off",
"gtCnvDflt": false,
"islsbrEnabled": false,
"m2paSctpRxbusyLink": "Off",
"performanceMeasurement": "Off",
"randsls": "Off",
"slsRotation": true,
"slscnv": "Off",
"slsocbEnabled": false,
"slsreplace": false,
"sparePCSupportEnabled": true
},
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
GET
Execute the following command to display the content:
/vstp/m3rloptions
Sample Output:
{
"data": {
"cnvAInat": 1,
"cnvCgda": false,
"cnvCgdi": false,
"cnvCgdn": false,
"cnvCgdn24": false,
"cnvClgItu": "Off",
"gtCnvDflt": false,
"islsbrEnabled": false,
"m2paSctpRxbusyLink": "On",
"performanceMeasurement": "Off”,
"randsls": "Off",
"slsRotation": true,
"slscnv": "Off",
"slsocbEnabled": false,
"slsreplace": false,
"sparePCSupportEnabled": true
},
"links": {
"update": {
"action": "PUT",
"description": "Update this item.",
"href": "/mmi/dsr/v4.3/vstp/m3rloptions/",
"type": "status"
}
},
"messages": [],
"status": true
}
connectionconfigurationsets
The sctpBundlingEnabled parameter in connectionconfigurationsets MO enables or disables the SCTP bundling. The parameter supports the following values: Yes/No
POST
{
"name": "ConnCfgSet1",
"sctpBundlingEnabled": "Yes",
"sctpFragmentationEnabled": true,
"sctpHeartbeatInterval": 1000,
"sctpMaximumBurst": 4,
"sctpMaximumSegmentSize": 0,
"sctpNumberInboundStreams": 2,
"sctpNumberOutboundStreams": 2,
"sctpOrderedDelivery": true,
"sctpRetransmissionAssociationFailure": 10,
"sctpRetransmissionInitFailure": 8,
"sctpRetransmissionInitTimeout": 120,
"sctpRetransmissionMaximumTimeout": 800,
"sctpRetransmissionMaximumTimeoutInit": 120,
"sctpRetransmissionMinimumTimeout": 120,
"sctpRetransmissionPathFailure": 5,
"sctpSackDelay": 60,
"sctpSocketReceiveSize": 1000000,
"sctpSocketSendSize": 1000000
}
Execute the following command on Active SOAM to update the data:
/vstp/connectionconfigurationsets/ -v POST -r <filename>.json
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
GET
Execute the following command to display the content:
/vstp/connectionconfigurationsets
Sample Output:
{
"data": [
{
"configurationLevel": "204",
"name": "ConnCfgSet1",
"sctpBundlingEnabled": "Yes",
"sctpFragmentationEnabled": true,
"sctpHeartbeatInterval": 1000,
"sctpMaximumBurst": 4,
"sctpMaximumSegmentSize": 0,
"sctpNumberInboundStreams": 2,
"sctpNumberOutboundStreams": 2,
"sctpOrderedDelivery": true,
"sctpRetransmissionAssociationFailure": 10,
“sctpRetransmissionInitFailure": 8,
"sctpRetransmissionInitTimeout": 120,
"sctpRetransmissionMaximumTimeout": 800,
"sctpRetransmissionMaximumTimeoutInit": 120,
"sctpRetransmissionMinimumTimeout": 120,
"sctpRetransmissionPathFailure": 5,
"sctpSackDelay": 60,
"sctpSocketReceiveSize": 1000000,
"sctpSocketSendSize": 1000000
},
],
"links": {},
"messages": [],
"status": true
}