OID reference
1.3.6.1.4.1.19746.2.0.5067
Description: Replication context on the destination is missing or mis-matched. Cannot initialize context. Action: - Check both the source and destination configured context URL pair. The context is identified by the destination URL. - Make sure the destination has a matching configuration for this context.
Identification
{1 3 6 1 4 1 19746 2 0 5067}
The displayed source records contain one distinct definition. Compare its source records.
replDestNotConfigured NOTIFICATION-TYPE
OBJECTS { systemSerialNumber, replConfigDest }
STATUS current
DESCRIPTION
"Description:
Replication context on the destination is missing or mis-matched. Cannot initialize context.
Action:
- Check both the source and destination configured context URL pair. The context is identified by the destination URL.
- Make sure the destination has a matching configuration for this context.
"
::= { dataDomainMibTraps 5067 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description: Replication context on the destination is missing or mis-matched. Cannot initialize context. Action: - Check both the source and destination configured context URL pair. The context is identified by the destination URL. - Make sure the destination has a matching configuration for this context.
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: replDestNotConfigured
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"replDestNotConfigured",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"systemSerialNumber",
",",
"replConfigDest",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"Description: Replication context on the destination is missing or mis-matched. Cannot initialize context. Action: - Check both the source and destination configured context URL pair. The context is identified by the destination URL. - Make sure the destination has a matching configuration for this context. \"",
"::=",
"{",
"dataDomainMibTraps",
"5067",
"}"
],
"syntax_tree": [
[
"Objects",
[
"systemSerialNumber",
"replConfigDest"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Description: Replication context on the destination is missing or mis-matched. Cannot initialize context. Action: - Check both the source and destination configured context URL pair. The context is identified by the destination URL. - Make sure the destination has a matching configuration for this context."
],
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: DATA-DOMAIN-MIB
See published definition above
{'IF-MIB': ['ifIndex', 'ifDescr'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Counter32', 'Integer32', 'Counter64'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: DATA-DOMAIN-MIB
{'IF-MIB': ['ifIndex', 'ifDescr'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Counter32', 'Integer32', 'Counter64'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration