OID reference
1.3.6.1.4.1.629.10.10.1.3.2.1.9
Should we include this interface in LSPs, even if it is not running the IS-IS Protocol? In DC-ISIS, circuits with isisCircExtDomain 'true' will only be included in LSPs if this field is also 'true', and the circuit is active.
Identification
{1 3 6 1 4 1 629 10 10 1 3 2 1 9}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
isisCircPassiveCircuit OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Should we include this interface in LSPs, even if
it is not running the IS-IS Protocol?
In DC-ISIS, circuits with isisCircExtDomain 'true'
will only be included in LSPs if this field is
also 'true', and the circuit is active."
DEFVAL { false }
::= { isisCircEntry 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Should we include this interface in LSPs, even if it is not running the IS-IS Protocol? In DC-ISIS, circuits with isisCircExtDomain 'true' will only be included in LSPs if this field is also 'true', and the circuit is active.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: isisCircPassiveCircuit
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"isisCircPassiveCircuit",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Should we include this interface in LSPs, even if it is not running the IS-IS Protocol? In DC-ISIS, circuits with isisCircExtDomain 'true' will only be included in LSPs if this field is also 'true', and the circuit is active.\"",
"DEFVAL",
"{",
"false",
"}",
"::=",
"{",
"isisCircEntry",
"9",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Should we include this interface in LSPs, even if it is not running the IS-IS Protocol? In DC-ISIS, circuits with isisCircExtDomain 'true' will only be included in LSPs if this field is also 'true', and the circuit is active."
],
null,
null,
null,
[
"DEFVAL",
"false"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: DC-ISIS-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32', 'TimeTicks', 'NOTIFICATION-TYPE', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'DC-MASTER-TC': ['AuthUserDataString', 'EntityIndexOrZero', 'IgpShortcutMetricType', 'IfOperStatus', 'NumericIndex'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength', 'InetAddressIPv4', 'InetAddressIPv6'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration