Standard view Table view

AFFIRMED-SSF-MIB

        Slice Selection Function MIB
Source file
AFFIRMED-SSF-MIB
Last revised
Identity
affirmedSsf
Base OID
1.3.6.1.4.1.37963.7
Imported Objects
ITU-ALARM-TC-MIB ItuPerceivedSeverity
SNMPv2-SMI enterprises Integer32 MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE
Net-SNMP examples using the microsoft MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'AFFIRMED-SSF-MIB' -M '/opt/observium/mibs/microsoft:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AFFIRMED-SSF-MIB::affirmedSsf'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'AFFIRMED-SSF-MIB' -M '/opt/observium/mibs/microsoft:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AFFIRMED-SSF-MIB::affirmedSsf'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (11)
affirmedSsf
.1.3.6.1.4.1.37963.7
affirmedSsfTc
.1.3.6.1.4.1.37963.7.1
affirmedSsfObjects
.1.3.6.1.4.1.37963.7.2
affirmedSsfAlarmObjects
.1.3.6.1.4.1.37963.7.2.1
affirmedSsfAlarmSeqId
SNMPv2-SMIInteger32
 .1.3.6.1.4.1.37963.7.2.1.1
affirmedSsfAlarmDateTime
OctetString
 .1.3.6.1.4.1.37963.7.2.1.2
affirmedSsfAlarmResource
OctetString
 .1.3.6.1.4.1.37963.7.2.1.3
affirmedSsfAlarmSeverity
ITU-ALARM-TC-MIBItuPerceivedSeverity
 .1.3.6.1.4.1.37963.7.2.1.4
affirmedSsfAlarmDetails
OctetString
 .1.3.6.1.4.1.37963.7.2.1.5
affirmedSsfNotifications
.1.3.6.1.4.1.37963.7.3
affirmedSsfTraps
.1.3.6.1.4.1.37963.7.3.1
Dependencies (3) 2 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. ITU-ALARM-TC-MIBrfc
  4. AFFIRMED-SSF-MIBmicrosoftselected
Notifications / Traps (21)
NameOIDDescription
anSsfAlarmDnsServiceReachability
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.1
One or more DNS servers are not reachable by the SSF. This is an aggregate alarm for all configured servers, up to 8.
anSsfAlarmDiameterPeerStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.10
Connection loss to session database from DIAMETER peer. This alarm is raised when connection to the configured DIAMETER peer is down or if the peer is experiencing failures.
anSsfAlarmDiameterDbStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.11
No connection to any DIAMETER peer for database. This alarm is raised when all configured DIAMETER peers for a database are down.
anSsfAlarmDnsNameError
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.12
DNS query returned a name error. One or more FQDNs cannot be resolved.
anSsfAlarmConfigSync
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.13
Configuration data synchronization from master SSF failed.
anSsfAlarmLoginFailure
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.14
SSF user login failure.
anSsfAlarmFileSystem
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.15
File system utilization threshold alarm
anSsfAlarmCpu
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.16
CPU utilization threshold alarm
anSsfAlarmMemory
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.17
Memory utilization threshold alarm
anSsfAlarmNetworkNextHopStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.18
Network context next hop status alarm
anSsfAlarmNetworkStaticRouteStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.19
Network context static route status alarm
anSsfAlarmGtpPathStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.2
One or more GTP paths have timed out. This is an aggregate alarm, summarizing status for all paths.
anSsfAlarmStatusSync
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.20
Status data synchronization from an SSF failed.
anSsfAlarmGatewaySnmpStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.21
Load data retrieval by SNMP from gateway status.
anSsfAlarmLdapPeerStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.3
No connections to the LDAP peer for database. This alarm is raised when all connections to the configured LDAP peer are down.
anSsfAlarmNetworkKeepaliveStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.4
All network context keepalive sessions report failure.
anSsfAlarmLdapDbStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.5
No connections to any LDAP peer for database. This alarm is raised when all connections to all configured LDAP peers for a database are down.
anSsfAlarmOperState
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.6
Operational state of the SSF is disabled.
anSsfAlarmRestPeerStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.7
Connection loss to session database from REST peer. This alarm is raised when all connections to the configured REST peer are down or if the peer is experiencing failures.
anSsfAlarmRestDbStatus
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.8
No connections to any REST peer for database. This alarm is raised when all connections to all configured REST peers for a database are down.
anSsfAlarmPgwGxMapping
affirmedSsfAlarmSeqId affirmedSsfAlarmDateTime affirmedSsfAlarmResource affirmedSsfAlarmSeverity affirmedSsfAlarmDetails
.1.3.6.1.4.1.37963.7.3.1.9
Missing PGW Gx Name Mapping. One or more PGW Gx names cannot be resolved to an S2 FQDN.