Citrix ADC SNMP Counters

This article contains information about the newnslog Simple Network Management Protocol (SNMP) counters, and its brief description.

Using the Counters

Log on to the ADC using an SSH client, change to SHELL, navigate to the /var/nslog directory, and then use the ‘nsconmsg’ command to see comprehensive statistics using the different counters available. For the detailed procedure refer to Citrix Blog – NetScaler ‘Counters’ Grab-Bag!.

The newnslog SNMP

The following table lists the newnslog SNMP counters with a simple description of the counter.

Newnslog Counter

Description

snmp_tot_rxpkts

This counter tracks the SNMP packets received.

snmp_tot_txpkts

This counter tracks the SNMP packets transmitted.

snmp_tot_badVersions

This counter tracks the number of SNMP messages received, which were for an unsupported SNMP version.

snmp_tot_badCommName

This counter tracks the SNMP messages received, which used an SNMP community name not known to the NetScaler appliance.

snmp_tot_badCommUse

This counter tracks the total number of SNMP Messages received that represented an SNMP operation which is not allowed by the SNMP community named in the Message.

snmp_tot_parseErrs

This counter tracks the number of ASN.1 or BER errors encountered when decoding received SNMP Messages.

snmp_tot_getBulkReqs

This counter tracks the SNMP Get-Bulk PDUs that are accepted and processed.

snmp_tot_getReqs

This counter tracks the SNMP Get-Request PDUs that are accepted and processed.

snmp_tot_getNextReqs

This counter tracks the SNMP Get-Next PDUs that are accepted and processed.

snmp_tot_responses

This counter tracks the SNMP Get-Response PDUs that the NetScaler appliance generates.

snmp_err_req_dropped

This counter tracks the SNMP requests dropped.

snmp_tot_traps

This counter tracks the SNMP Trap PDUs that the NetScaler appliance generates.

snmp_tot_unsupportedSecurityLevel

This counter tracks the SNMP packets that are dropped because they requested a security level that is

unknown to the NetScaler appliance or otherwise unavailable.

snmp_tot_notInTimeWindow

This counter tracks the SNMP packets that are dropped because they appeared outside the Window of the authoritative SNMP engine.

snmp_tot_unknownUserName

This counter tracks the SNMP packets that are dropped because they referenced a user that is not known to the SNMP engine.

snmp_tot_unknownEngineIds

This counter tracks the SNMP packets that are dropped because they referenced an SNMP engine ID that is not known to the NetScaler appliance.

snmp_tot_wrongDigests

This counter tracks the SNMP packets that are dropped because they do not contain the expected digest value.

snmp_tot_decryptionErrors

This counter tracks the SNMP packets that are dropped because they cannot be decrypted.

Related:

Initialization failed. There is a bad global domain ID in the directory. ASN.1 Server error code error code. Offset value. [valuevaluevaluevalue] (16)

Details
Product: Exchange
Event ID: 3056
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: Initialization failed. There is a bad global domain ID in the directory. ASN.1 Server error code error code. Offset value. [valuevaluevaluevalue] (16)
   
Explanation
ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.

The fully encoded ASN.1 envelope is in the

Microsoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site.

APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.

These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.

   
User Action
The bad data may be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Microsoft Exchange Server installation compact disc. For more information, see Knowledge Base articles Q168906 and Q163032.

Related:

Initialization failed. There is a bad global domain ID in the directory. ASN.1 Server error code {error code}. Offset {value}. [{value}{value}{value}{value}] (16)

Details
Product: Exchange
Event ID: 3056
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA03056
Message: Initialization failed. There is a bad global domain ID in the directory. ASN.1 Server error code {error code}. Offset {value}. [{value}{value}{value}{value}] (16)
   
Explanation
ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.The fully encoded ASN.1 envelope is in theMicrosoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site. APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
The bad data may be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Microsoft Exchange Server installation compact disc. For more information, see Knowledge Base articles Q168906 and Q163032.

Related:

A {name} ASN.1 encoding error at offset {value} was detected by a {service name} service. [{value}{value}{value}{value}] ()

Details
Product: Exchange
Event ID: 3020
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA03020
Message: A {name} ASN.1 encoding error at offset {value} was detected by a {service name} service. [{value}{value}{value}{value}] ()
   
Explanation
ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.The fully encoded ASN.1 envelope is in theMicrosoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site. APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
The bad data may be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Exchange server installation compact disc. For more information, see Knowledge Base articles Q168906 and Q163032.

Related:

A fatal internal MTA error has occurred. The MTA failed to load the RDI.TPL ASN.1 template file. It may be corrupt. Reload a fresh copy from the installation CD. [ ] (16)

Details
Product: Exchange
Event ID: 2231
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: A fatal internal MTA error has occurred. The MTA failed to load the RDI.TPL ASN.1 template file. It may be corrupt. Reload a fresh copy from the installation CD. [<value> <value> <value> <value>] (16)
   
Explanation

ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.

   
User Action

Copy the Rdi.tpl template file from the installation compact disc to the \Exchsrvr\Mtadata directory.

Related:

A fatal internal MTA error has occurred. The MTA failed to load the RDI.TPL ASN.1 template file. It may be corrupt. Reload a fresh copy from the installation CD. [{value}{value}{value}{value}] (16)

Details
Product: Exchange
Event ID: 2231
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA02231
Message: A fatal internal MTA error has occurred. The MTA failed to load the RDI.TPL ASN.1 template file. It may be corrupt. Reload a fresh copy from the installation CD. [{value}{value}{value}{value}] (16)
   
Explanation
ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.
   
User Action
Copy the Rdi.tpl template file from the installation compact disc to the \Exchsrvr\Mtadata directory.

Related:

ROSE error, no ROSE APDU found in ASN.1. Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1177
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, no ROSE APDU found in ASN.1. Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One. The fully encoded ASN.1 envelope is in the Microsoft Exchange Server Application Protocol Data Unit (APDU) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site.

APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.

   
User Action

To obtain more information, in the Server Properties dialog box, on the Diagnostics Logging tab, select MSExchangeMTA, and then set the logging level of the Interoperability and X.400 categories to Medium or greater. Then, check the APDU log files.

Related:

ROSE error, no ROSE APDU found in ASN.1. Control block index {index name} [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 1177
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA01177
Message: ROSE error, no ROSE APDU found in ASN.1. Control block index {index name} [{value}{value}{value}{value}] (14)
   
Explanation
ROSE refers to the remote operation service element. ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.The fully encoded ASN.1 envelope is in theMicrosoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site. APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
To obtain more information, in the Server Properties dialog box, on the Diagnostics Logging tab, select MSExchangeMTA, and then set the logging level of the Interoperability and X.400 categories to Medium or greater. Then, check the APDU log files.

Related:

ROSE error, ASN.1 decode failed, Syntax server error code {error code} Error detected at offset {value} Node label {name} Control block index {index name} [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 1173
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA01173
Message: ROSE error, ASN.1 decode failed, Syntax server error code {error code} Error detected at offset {value} Node label {name} Control block index {index name} [{value}{value}{value}{value}] (14)
   
Explanation
ROSE refers to the remote operation service element. ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One.The fully encoded ASN.1 envelope is in theMicrosoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site. APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
The bad data may be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Exchange server installation compact disc. For more information, see Knowledge Base articles Q168906 and Q163032.

Related:

ROSE error, ASN.1 decode failed, Syntax server error code Error detected at offset Node label Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1173
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, ASN.1 decode failed, Syntax server error code <error code> Error detected at offset <value> Node label <name> Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One. The fully encoded ASN.1 envelope is in the Microsoft Exchange Server Application Protocol Data Unit (APDU) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site.

APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum. These text logs are stored in the Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.

   
User Action

The bad data can be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Exchange server installation compact disc. For more information, see Microsoft Knowledge Base articles 168906 and 163032.

Related: