Unisphere-Data-ACCOUNTING-MIB :: usdAcctngSelectionSubtreeType

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › Unisphere-Data-ACCOUNTING-MIB › usdAcctngSelectionSubtreeType

usdAcctngSelectionSubtreeType

Module: Unisphere-Data-ACCOUNTING-MIB

OID (symbolic): Unisphere-Data-ACCOUNTING-MIB::usdAcctngSelectionSubtreeType

OID (numeric): 1.3.6.1.4.1.4874.2.2.24.1.1.1.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indicates the origin of the collection, given the row's subtree. The architecture implementation for statistics collection imposes that rows with distinct usdAcctngSelectionSubtreeType may not be collected into the same accounting file. Conversely, different files (configured from acctngSelectionFile) entries are necessary in order to collect from subtrees (configured from acctngSelectionSubtree) that imply into different subtree types (usdAcctngSelectionSubtreeType).

What is usdAcctngSelectionSubtreeType?

This deprecated value reported the origin of a collection selection's subtree: unknown(0), lineCard(1), or systemController(2), reflecting that rows with different subtree types cannot be collected into the same accounting file. An admin reading this on older configurations would use it to understand why separate accounting files were required for line-card-sourced versus system-controller-sourced statistics. For example, a value of lineCard(1) meant that particular selection's data had to go into a file separate from any systemController(2) selections.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.24.1.1.1.1.3
snmpwalk -v2c -c public <target> Unisphere-Data-ACCOUNTING-MIB::usdAcctngSelectionSubtreeType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.24.1.1.1.1.3.1
snmpget -v2c -c public <target> Unisphere-Data-ACCOUNTING-MIB::usdAcctngSelectionSubtreeType.1

Start monitoring Juniper/Unisphere ERX edge routing switch (accounting-policy/interface-selection config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-ACCOUNTING-MIB::usdAcctngSelectionSubtreeType OID value, configure state conditions and alerts, and monitor any Juniper/Unisphere ERX edge routing switch (accounting-policy/interface-selection config status) from a single console.

OID Breakdown

Upper-level ancestors (14 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.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.24juniAcctngMIBJuniper-ACCOUNTING-MIB
1.3.6.1.4.1.4874.2.2.24.1juniAcctngMIBObjectsJuniper-ACCOUNTING-MIB
1.3.6.1.4.1.4874.2.2.24.1.1juniAcctngSelectionControlJuniper-ACCOUNTING-MIB
1.3.6.1.4.1.4874.2.2.24.1.1.1juniAcctngSelectionTableJuniper-ACCOUNTING-MIB
1.3.6.1.4.1.4874.2.2.24.1.1.1.1juniAcctngSelectionEntryJuniper-ACCOUNTING-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.24.1.1.1.1.3usdAcctngSelectionSubtreeTypeUnisphere-Data-ACCOUNTING-MIB