2.35.1.2 MMI Managed Objects CNCF
MMI information associated with CNCF feature is accessed from DSR NOAM or SOAM from Main Menu, and then MMI API Guide.
Once the MMI API Guide is opened, use the application navigation to locate specific vSTP managed object information.
The following table lists the managed objects and operations supported for CNCF feature:
Table 2-57 MMI Managed Objects for CNCF
Managed Object Name | Operations Supported | URI |
---|---|---|
M3RL Options | GET/PUT | /vstp/m3rloptions |
MTP Screening Rules | GET/POST/PUT/DELETE | /vstp/mtpscrrules |
M3rl Options - PUT
The CNCF parameter is used for turning on or off the CNCF feature. CNCF parameter must be On to enable CNCF feature. Create a file with following content. File name could be anything, for example: Test can be used as filename:
$ vim Test.json
{
"CNCF ": "On"
}
Run the following command on Active SOAM to update the data:
/vstp/m3rloptions -v PUT -r /<Absolute Path>/<File Name>.json
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
MTPScreeningRule
The Actname
parameter in MTPScreeningRule MO indicates if CNCF stop
action to be applied
POST
{
" SCCPStopActionScreening": false,
"tifstopAction": “None",
"spare": "no",
"scmgmessagetype": "1",
“affectedPcSsn": "1",
"Actname": "Cncf"
}
Run the following command on Active SOAM to insert the data:
/vstp/mtpscrrules –v POST –r .json
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
GET
/vstp/mtpscrrules
Sample Output:
{
"data": [
{
" SCCPStopActionScreening": false,
"tifstopAction": “None",
"spare": "no",
"scmgmessagetype": "1",
“affectedPcSsn": "1",
"Actname": "Cncf"
}
],
"links": {},
"messages": [],
"status": true
}