CAIUXSA2-MIB :: uxsA2StatusFileEvalPolicy

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCAIUXSA2-MIBuxsA2StatusFileEvalPolicy

uxsA2StatusFileEvalPolicy

Module: CAIUXSA2-MIB

OID (symbolic): CAIUXSA2-MIB::uxsA2StatusFileEvalPolicy

OID (numeric): 1.3.6.1.4.1.791.2.10.2.74.2.11.2.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: &Current evaluation policy for the file watcher. Defines how metric values will be calculated and 'culprits' be determined if two or more file resources fall into the monitoring scope of a one-to-many watcher. If set to 1 (individual), metric values will be set to the worst values (lowest and/or highest) of all file instances; if the value of a metric violates the threshold condition, the respective 'culprits' list will contain all instances individually violating the most severe threshold. If set to 2 (min), metric values will be set to the lowest (minimum) values of all file instances; if the value of a metric violates the threshold condition, the respective 'culprits' list will contain all instances having the same minimum value. If set to 3 (max), metric values will be set to the highest (maximum) values of all file instances; if the value of a metric violates the threshold condition, the respective 'culprits' list will contain all instances having the same maximum value. If set to 4 (sum), metric values will be set to the cumulative values (sum) of all file instances; if the value of a metric violates the threshold condition, the respective 'culprits' list will contain all instances. If set to 5 (avg), metric values will be set to the average values of all file instances; if the value of a metric violates the threshold condition, the respective 'culprits' list will contain all instances individually violating the most severe threshold.

What is uxsA2StatusFileEvalPolicy?

Read-write setting controlling how the watcher calculates metric values and identifies the worst-performing file when its scope covers multiple files, e.g. an 'individual' policy reports the worst-case values.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.791.2.10.2.74.2.11.2.1.3
snmpwalk -v2c -c public <target> CAIUXSA2-MIB::uxsA2StatusFileEvalPolicy

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.791.2.10.2.74.2.11.2.1.3.1
snmpget -v2c -c public <target> CAIUXSA2-MIB::uxsA2StatusFileEvalPolicy.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.791.2.10.2.74.2.11.2.1.3.1 i <value>

Start monitoring UNIX server managed by CA Unicenter TNG (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CAIUXSA2-MIB::uxsA2StatusFileEvalPolicy OID value, configure state conditions and alerts, and monitor any UNIX server managed by CA Unicenter TNG (legacy) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.791caiCA-NTOS-MIB
1.3.6.1.4.1.791.2caiSysMgrCA-NTOS-MIB
1.3.6.1.4.1.791.2.10tngCA-W2KOS-MIB
1.3.6.1.4.1.791.2.10.2agentsCA-W2KOS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.791.2.10.2.74caiUxsA2CAIUXSA2-MIB
1.3.6.1.4.1.791.2.10.2.74.2uxsA2StatusGroupCAIUXSA2-MIB
1.3.6.1.4.1.791.2.10.2.74.2.11uxsA2StatusFileGroupCAIUXSA2-MIB
1.3.6.1.4.1.791.2.10.2.74.2.11.2uxsA2StatusFileTableCAIUXSA2-MIB
1.3.6.1.4.1.791.2.10.2.74.2.11.2.1uxsA2StatusFileEntryCAIUXSA2-MIB
1.3.6.1.4.1.791.2.10.2.74.2.11.2.1.3uxsA2StatusFileEvalPolicyCAIUXSA2-MIB