IPFIX-MIB :: ipfixExportMemberType

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › IPFIX-MIB › ipfixExportMemberType

ipfixExportMemberType

Module: IPFIX-MIB

OID (symbolic): IPFIX-MIB::ipfixExportMemberType

OID (numeric): 1.3.6.1.2.1.193.1.1.4.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The type of member Transport Session in a Transport Session group (identified by the value of ipfixExportIndex, ipfixObservationDomainId, and ipfixMeteringProcessCacheId). The following values are valid:

unknown(0) This value MUST be used if the status of the group membership cannot be detected by the equipment. This value should be avoided as far as possible.

primary(1) This value is used for a group member that is used as the primary target of an Exporter. Other group members (with the same ipfixExportIndex and ipfixMeteringProcessCacheId) MUST NOT have the value primary(1) but MUST have the value secondary(2). This value MUST also be specified if the Exporter does not support Transport Session grouping. In this case, the group contains only one Transport Session.

secondary(2) This value is used for a group member that is used as a secondary target of an Exporter. The Exporter will use one of the targets specified as secondary(2) within the same Transport Session group when the primary target is not reachable.

parallel(3) This value is used for a group member that is used for duplicate exporting (i.e., all group members identified by the ipfixExportIndex are exporting the same Records in parallel). This implies that all group members MUST have the same member type (i.e., parallel(3)).

loadBalancing(4) This value is used for a group member that is used as one target for load-balancing. This means that a Record is sent to one of the group members in this group identified by ipfixExportIndex. This implies that all group members MUST have the same member type (i.e., loadBalancing(4)).

What is ipfixExportMemberType?

Reports this Transport Session's role within its export group: primary (the main target), secondary (failover if primary is unreachable), parallel (duplicate export to all members), or loadBalancing (records spread across members) — key to understanding why flow data might be going to more than one collector.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.193.1.1.4.1.2
snmpwalk -v2c -c public <target> IPFIX-MIB::ipfixExportMemberType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.193.1.1.4.1.2.1
snmpget -v2c -c public <target> IPFIX-MIB::ipfixExportMemberType.1

Start monitoring Vendor-neutral IETF standard (IPFIX-capable router, switch, or flow collector) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IPFIX-MIB::ipfixExportMemberType OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (IPFIX-capable router, switch, or flow collector) from a single console.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.193ipfixMIBIPFIX-MIB
1.3.6.1.2.1.193.1ipfixObjectsIPFIX-MIB
1.3.6.1.2.1.193.1.1ipfixMainObjectsIPFIX-MIB
1.3.6.1.2.1.193.1.1.4ipfixExportTableIPFIX-MIB
1.3.6.1.2.1.193.1.1.4.1ipfixExportEntryIPFIX-MIB
1.3.6.1.2.1.193.1.1.4.1.2ipfixExportMemberTypeIPFIX-MIB