HH3C-SRV6POLICY-MIB :: hh3cSrv6PolicyBsidConflictState

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › HH3C-SRV6POLICY-MIB › hh3cSrv6PolicyBsidConflictState

hh3cSrv6PolicyBsidConflictState

Module: HH3C-SRV6POLICY-MIB

OID (symbolic): HH3C-SRV6POLICY-MIB::hh3cSrv6PolicyBsidConflictState

OID (numeric): 1.3.6.1.4.1.25506.2.189.1.2.1.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The conflict state of the binding SID.

What is hh3cSrv6PolicyBsidConflictState?

Indicates whether the policy's Binding SID is currently in conflict with another allocation or whether a prior conflict has been resolved. Admins watch this because a BSID conflict can prevent traffic from being steered onto the policy at all.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.189.1.2.1.8
snmpwalk -v2c -c public <target> HH3C-SRV6POLICY-MIB::hh3cSrv6PolicyBsidConflictState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.189.1.2.1.8.1
snmpget -v2c -c public <target> HH3C-SRV6POLICY-MIB::hh3cSrv6PolicyBsidConflictState.1

Start monitoring H3C router, IPv6/SRv6-capable (SRv6-TE policies) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-SRV6POLICY-MIB::hh3cSrv6PolicyBsidConflictState OID value, configure state conditions and alerts, and monitor any H3C router, IPv6/SRv6-capable (SRv6-TE policies) from a single console.

How to Use in IPNetwork Monitor

Select an H3C router, IPv6/SRv6-capable (SRv6-TE policies) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type hh3cSrv6PolicyBsidConflictState into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The conflict state of the binding SID. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'conflictResolved', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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.25506hh3cHH3C-OID-MIB
1.3.6.1.4.1.25506.2hh3cCommonHH3C-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25506.2.189hh3cSrv6PolicyHH3C-SRV6POLICY-MIB
1.3.6.1.4.1.25506.2.189.1hh3cSrv6PolicyObjectsHH3C-SRV6POLICY-MIB
1.3.6.1.4.1.25506.2.189.1.2hh3cSrv6PolicyTableHH3C-SRV6POLICY-MIB
1.3.6.1.4.1.25506.2.189.1.2.1hh3cSrv6PolicyEntryHH3C-SRV6POLICY-MIB
1.3.6.1.4.1.25506.2.189.1.2.1.8hh3cSrv6PolicyBsidConflictStateHH3C-SRV6POLICY-MIB