In this section:

The DSC Platform contain the MIB files that define all object variables and SNMP traps for this platform. The DSC Platform MIB files and MIB file locations are as follows:

  • /opt/cpu_ss7gw/current/mibs/UCD-SNMP-MIB.txt

  • /opt/cpu_ss7gw/current/mibs/ptiSegway.mib

As an alternative for loading the ptiSegway.mib file, you can use the separate MIB files that are located at /opt/cpu_ss7gw/current/mibs/splitted_mib

  • PTISEGWAY-MIB.mib contains all object tree definitions in SMIv2 syntax format

  • PTISEGWAYTRAP-MIB.mib contains the Ribbon trap definitions in SMIv1 syntax format

An SNMP Manager is required to interpret MIB files correctly. For information about installing the MIB files onto your SNMP Manager, see the documentation for your specific SNMP Manager.

The MIB file OBJECT IDENTIFIER, OBJECT-TYPE and TRAP-TYPE definitions are easily identified and searchable in the textual MIB files. The following are examples of

For more information about the OBJECT IDENTIFIER, see Object Identifier.

The DSC Platform provides definitions in the MIB files for all objects with the exception of filtered objects. The DSC Platform filtered objects are included in the Global Title Translation (GTT), Gateway Screening and MSU Tracing (GWST), and Point Code Emulation (PCE). For more information about these applications, see the appropriate chapter of the SS7 Application Guide 2.

MIB OBJECT INDENTIFIER Construct

The following are examples of OBJECT INDENTIFIERS

  • ptConnGroup         OBJECT IDENTIFIER ::= { ptiSegway 15 }

  • ptMTPMTP3NAManager         OBJECT IDENTIFIER ::= { ptConnGroup 46}

  • ptMTPMTP3NA         OBJECT IDENTIFIER ::= { ptMTPMTP3NAManager 65 }

  • ptMTPRoutesetList         OBJECT IDENTIFIER ::= { ptMTPMTP3NA 63 }

  • ptMTPLinksets         OBJECT IDENTIFIER ::= { ptMTPMTP3NA 64 }

  • ptMTPLinkset         OBJECT IDENTIFIER ::= { ptMTPLinksets 53 }

  • ptMTPLSLink         OBJECT IDENTIFIER ::= { ptMTPLinkset 55 }

  • ptMTPRouteset          OBJECT IDENTIFIER ::= { ptMTPRoutesets 51 }

  • ptMTPRoute         OBJECT IDENTIFIER ::= { ptMTPRouteset 52 }

Note

The following information are examples of the ptiSegway.mib.


MIB OBJECT - TYPE Construct

The following are examples of OBJECT TYPEs.

ptMTPLinksetAPC OBJECT-TYPE

SYNTAX                  Integer32 (-2147483648..2147483647)
MAX-ACCESS              read-only
STATUS                  current
DESCRIPTION
"Adjacent SS7 point code of this linkset."
::= { ptMTPLinksetEntry 2 }


ptMTPLinksetCLLI OBJECT-TYPE

SYNTAX                       DisplayString ( SIZE(0..255) )
MAX-ACCESS                   read-create
STATUS                       current
DESCRIPTION
"Common Language Location Identifier (CLLI) of this linkset."
::= { ptMTPLinksetEntry 5 }


ptMTPLSLinkSLC OBJECT-TYPE

SYNTAX                       Integer32 (0..15)
MAX-ACCESS                   read-only
STATUS                       current
DESCRIPTION
"Signaling Link Code for this link. Value of 0-15"
::= { ptMTPLSLinkEntry 3 }


ptMTPRoutesetDPC OBJECT-TYPE

SYNTAX                       Integer32 (-2147483648..2147483647)
MAX-ACCESS                   read-only
STATUS                       current
DESCRIPTION
"Destination SS7 point code of this routeset This value should be set a creation time of the routeset and cannot be modified thereafter. The point code of the routeset gives the destination that one is seeking. The routes within the routeset will indicate the adjacent point codes that can be used to the get to the destination."
::= { ptMTPRoutesetEntry 2 }

ptMTPRoutesetDestinationType OBJECT-TYPE

SYNTAX                       INTEGER
{
	default (1),
	network (2),
	cluster (3),
	member (4)
}
MAX-ACCESS                   read-only
STATUS                       current
DESCRIPTION
"Describes the destination type of the routeset (network, cluster, member, or default)."
::= { ptMTPRoutesetEntry 3 }


ptMTPRouteAPC OBJECT-TYPE

SYNTAX                       Integer32 (-2147483648..2147483647)        
MAX-ACCESS                   read-only
STATUS                       current
DESCRIPTION
"Adjacent SS7 point code of this route."
::= { ptMTPRouteEntry 2 }


ptMTPRouteCost OBJECT-TYPE

SYNTAX                       Integer32 (0..100)
MAX-ACCESS                   read-create
STATUS                       current
DESCRIPTION
"Cost of this route"
::= { ptMTPRouteEntry 3 }


ptTrapItemOID OBJECT-TYPE

SYNTAX          DisplayString ( SIZE(0..255) )
MAX-ACCESS      read-only
STATUS          current
DESCRIPTION
"The Item OID. This is used to indicate the trap associated object OID."
::= { ptiSegway 1026 }

 

MIB TRAP-TYPE Construct

The following is an SNMP TRAP-TYPE in the MIB.

Note

The PTISEGWAY-MIB.mib contains non-static varbinds based on the MSA and Process Event definition file for selective traps.

Non-static varbinds are used for objects with multiple instances that have incomplete trap definitions in the def files. The MSA and Process Event library related definition files assign the proper varbinds (Name and Slot attributes) to help identify the originating object. 

A trap with the correct varbinds helps provide a correlation between raise and clear traps and ensure users can properly process and address the reported condition.


ptMTP3NAMtp3NANotConnected TRAP-TYPE

      ENTERPRISE ptiSegway
      VARIABLES
      {
         ptTrapType,
         ptTrapSequenceNumber,
         ptTrapSeverity,
         ptTrapProbableCause,
         ptTrapClearType,
         ptTrapDateAndTime,
         ptTrapItemOID,
         ptSGMTP3NANetworkAppearance
      }
      DESCRIPTION
      "An MTP3 NA not connected notification is sent when the
    connectivity between the Dinamo and MTP3 NA is lost."
      ::= 7230
Note

You can manually extract a list of possible product Traps from the MIB files.