Configuration data synchronization from master SSF failed.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Affirmed Networks MIB copies (Observium Community)
OID reference
1.3.6.1.4.1.37963.7.3.1.13
Configuration data synchronization from master SSF failed.
Identification
{1 3 6 1 4 1 37963 7 3 1 13}
The displayed source records contain one distinct definition. Compare its source records.
anSsfAlarmConfigSync NOTIFICATION-TYPE
OBJECTS {
affirmedSsfAlarmSeqId,
affirmedSsfAlarmDateTime,
affirmedSsfAlarmResource,
affirmedSsfAlarmSeverity,
affirmedSsfAlarmDetails
}
STATUS current
DESCRIPTION
"Configuration data synchronization from master SSF failed."
-- IMPACT
-- "Config data sync from master SSF failed, please refer to the alarm details
-- string for specific reason. This alarm implies that this SSF may not be in sync
-- with the master SSF as configured at /sync/config-master. This implies that any
-- changes in master configuration (e.g. additional dns static-cache entries, or
-- change in gateway admin-state), will not be synced. If /sync/config-interval
-- is configured to a non-zero value, then this SSF will periodically retry to
-- pull the portable configuration data from the master SSF. Sync may be attempted
-- manually by invoking the command 'sync config-pull'. This alarm has major
-- severity."
--
-- REPAIR-ACTION
-- "Please refer to the details string of the alarm for a specific failure reason.
-- If sync is not desired, then de-configure the master IP address under
-- /sync/config-master. Otherwise, check that the master IP address is reachable,
-- and that the correct readonly user credentials are input at /sync/userid and
-- /sync/password. Also verify that all loopback IP names on this SSF match those
-- used on the SSF master."
::= { affirmedSsfTraps 13}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Configuration data synchronization from master SSF failed.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Affirmed Networks MIB copies (Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: anSsfAlarmConfigSync
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"anSsfAlarmConfigSync",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"affirmedSsfAlarmSeqId",
",",
"affirmedSsfAlarmDateTime",
",",
"affirmedSsfAlarmResource",
",",
"affirmedSsfAlarmSeverity",
",",
"affirmedSsfAlarmDetails",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"Configuration data synchronization from master SSF failed.\"",
"::=",
"{",
"affirmedSsfTraps",
"13",
"}"
],
"syntax_tree": [
[
"Objects",
[
"affirmedSsfAlarmSeqId",
"affirmedSsfAlarmDateTime",
"affirmedSsfAlarmResource",
"affirmedSsfAlarmSeverity",
"affirmedSsfAlarmDetails"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Configuration data synchronization from master SSF failed."
],
null
]
}Vendor MIB copy from the Observium Community archive. Affirmed Networks support.
Module: AFFIRMED-SSF-MIB
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'enterprises', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'ITU-ALARM-TC-MIB': ['ItuPerceivedSeverity']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: AFFIRMED-SSF-MIB
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'enterprises', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'ITU-ALARM-TC-MIB': ['ItuPerceivedSeverity']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.37963.7.3.1.1 | anSsfAlarmDnsServiceReachability | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.2 | anSsfAlarmGtpPathStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.3 | anSsfAlarmLdapPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.4 | anSsfAlarmNetworkKeepaliveStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.5 | anSsfAlarmLdapDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.6 | anSsfAlarmOperState | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.7 | anSsfAlarmRestPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.8 | anSsfAlarmRestDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.9 | anSsfAlarmPgwGxMapping | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.10 | anSsfAlarmDiameterPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.11 | anSsfAlarmDiameterDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.12 | anSsfAlarmDnsNameError | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.14 | anSsfAlarmLoginFailure | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.15 | anSsfAlarmFileSystem | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.16 | anSsfAlarmCpu | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.17 | anSsfAlarmMemory | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.18 | anSsfAlarmNetworkNextHopStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.19 | anSsfAlarmNetworkStaticRouteStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.20 | anSsfAlarmStatusSync | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.21 | anSsfAlarmGatewaySnmpStatus | 0 | 0 |