To configure AA filters
Steps
1 |
Log in to a station that has access to the NSP system. |
2 |
Open a console window. |
3 |
As required, issue the following RESTCONF API call to configure an AA filter that specifies a subscriber type: Note: In order to issue a RESTCONF API call, you require a token; see the My First NSP API Client tutorial on the Network Developer Portal for information. PATCH https://address:443/restconf/data/flowconf:config/filters/aa/sub-type where address is the NSP cluster advertised address The message body is the following: { "sub-type" : [ { "sub-type" : "sub", "enabled" : "true", } ] } where sub is the subscriber type Note: The settings in the above example represent the default values. Note: This configuration has a fixed number of entries (8), which are pre-configured with default values. These entries can be updated (PATCH), but cannot be replaced or deleted. |
4 |
As required, issue the following RESTCONF API call to specify an AA application defined on the router: Note: In order to issue a RESTCONF API call, you require a token; see the My First NSP API Client tutorial on the Network Developer Portal for information. POST https://address:443/restconf/data/flowconf:config/filters/aa/uapps/app where address is the NSP cluster advertised address The message body is the following: { "app" : [ { "name" : "name", } ] } where name is the name of the AA application defined on the router |
5 |
As required, issue the following RESTCONF API call to specify an AA protocol defined on the router: Note: In order to issue a RESTCONF API call, you require a token; see the My First NSP API Client tutorial on the Network Developer Portal for information. POST https://address:443/restconf/data/flowconf:config/filters/aa/uapps/protocol where address is the NSP cluster advertised address The message body is the following: { "protocol" : [ { "name" : "name", } ] } where name is the name of the AA protocol defined on the router |
6 |
Close the console window. End of steps |