Download full document:

snmptrap_binding

Binding object which returns the resources bound to snmptrap.

Properties

(click to see Operations)

NameData TypePermissionsDescription
trapclass<String>Read-writeTrap type specified in the trap listener entry.
Possible values = generic, specific
trapdestination<String>Read-writeIP address specified in the trap listener entry.
Minimum length = 1
version<String>Read-writeThe SNMP version of the trap specified in the trap listener entry.
Possible values = V1, V2, V3
td<Double>Read-writeInteger value that uniquely identifies the traffic domain in which you want to configure the entity. If you do not specify an ID, the entity becomes part of the default traffic domain, which has an ID of 0.
Minimum value = 0
Maximum value = 4094
snmptrap_snmpuser_binding<snmptrap_snmpuser_binding[]>Read-onlysnmpuser that can be bound to snmptrap.

Operations

(click to see Properties)

GET| GET (ALL)

Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER:<username>

    X-NITRO-PASS:<password>

    Note:In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

Note:

Mandatory parameters are marked in redand placeholder content is marked in <green>.

get

URL:http://<netscaler-ip-address>/nitro/v1/config/snmptrap_binding

Query-parameters:

args

http://<netscaler-ip-address>/nitro/v1/config/snmptrap_binding?args=trapdestination:<String_value>,version:<String_value>,td:<Double_value>,trapclass:<String_value>

Use this query-parameter to get snmptrap_binding resources based on additional properties.

HTTP Method:GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Accept:application/json

Response:

HTTP Status Code on Success: 200 OK HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the errorResponse Headers:

Content-Type:application/json

Response Payload:

{ "snmptrap_binding": [ {
"trapdestination":<String_value>,
"version":<String_value>,
"td":<Double_value>,
"trapclass":<String_value>,
"snmptrap_snmpuser_binding":<snmptrap_snmpuser_binding[]_value>
}]}

get (all)

URL:http://<netscaler-ip-address>/nitro/v1/config/snmptrap_binding

Query-parameters:

bulkbindings

http://<netscaler-ip-address>/nitro/v1/config/snmptrap_binding?bulkbindings=yes

NITRO allows you to fetch bindings in bulk.

HTTP Method:GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Accept:application/json

Response:

HTTP Status Code on Success: 200 OK HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the errorResponse Headers:

Content-Type:application/json

Response Payload:

{ "snmptrap_binding": [ {
"trapdestination":<String_value>,
"version":<String_value>,
"td":<Double_value>,
"trapclass":<String_value>,
"snmptrap_snmpuser_binding":<snmptrap_snmpuser_binding[]_value>
}]}