The following table lists the mandatory attributes when creating a new routeset using RowStatus and multiple set commands. You must set the Destination Point Code (DPC) and the network routing configuration attributes before you set the new routeset to active using RowStatus.

Although not a mandatory attribute, you should also set the CLLI description at the time of routeset creation to identify the routeset on the SS7 network. Alternatively, you can set this attribute after the routeset is created using RowStatus.

All other configurable routeset attributes listed in the MIB, such as congestion levels, need not be set at the time of row creation. Default values are inserted for these attributes by the system at the time of row creation. For more information about the mandatory attributes and other configurable routeset attributes, refer to the MIB and the appropriate sections in the SS7 Application Guide 1 and SS7 Application Guide 2.

Caution

The procedure fails if you omit any of the mandatory variables when creating a new instance of the variable using RowStatus. You must delete the row and recreate it, ensuring that you include all mandatory variables.

Mandatory Routeset Variables

Variable OBJECT-TYPE Description
ptMTPRoutesetDPC Enter the point code of the destination node as the DPC value here. You must convert the point code into a 32-bit integer.
ptMTPRoutesetDestinationType Enter the network routing configuration as an integer. Valid values: default=1 network=2 cluster=3 member=4

To create a routeset

snmpwalk -c public <host name> 
.1.3.6.1.4.1.1556.17.15.46.65.63.51.1.1.2

Get the list of all routesets on the system and display their DPC.

DPC object tag is 2 as per ptRoutesetDPC OBJECT-TYPE in the MIB.

Parse the list to get the OID of the required Routeset.

  1. Set the RowStatus to 5 (create and wait).

    A routeset has MIB Object Identifier 51:
    ptRouteset                     OBJECT IDENTIFIER ::= { ptMTPRoutesets 51 }

    snmpset -c private <host name>
.1.3.6.1.4.1.1556.17.15.46.65.63.51.1.1.254.1.1.1.1.0 i 5

                

  2. Set the DPC to ANSI 10.10.10.

    DPC object tag is 2 as per ptMTPRoutesetDPC OBJECT-TYPE in the MIB.

    10.10.10 must be entered as the decimal value or 657930.

    snmpset -c private <host name>
.1.3.6.1.4.1.1556.17.15.46.65.63.51.1.1.2.1.1.1.1.0 i 657930

    Destination Type object tag is 3 as per ptMTPRoutesetDestinationType.

    OBJECT-TYPE in the MIB.

    Set the Destination Type to Action = 4 = Member.

    snmpset -c private <host name>
.1.3.6.1.4.1.1556.17.15.46.65.63.51.1.1.3.1.1.1.1.0 i 4

                

  3. Set the Parent OID.

    snmpset -c private <host name> 
.1.3.6.1.4.1.1556.17.15.46.65.63.51.1.1.253.1.1.1.1.0 s
".1.3.6.1.4.1.1556.17.15.46.65.63.1.1.253.1.1.1.1"

         

  4. Check the RowStatus value.

    snmpget -c private <host name>
.1.3.6.1.4.1.1556.17.15.46.65.63.53.1.1.254.1.1.1.1.0

    If the value is 2, the Link is ready to be created (To create SNMP Attributes)

  5. Create the Routeset by setting the RowStatus to 1 (Active).

    snmpset -c private <host name>
.1.3.6.1.4.1.1556.17.15.46.65.63.51.1.1.254.1.1.1.1.0 i 5

            

  6. Verify if the Routeset was created.

    snmpwalk -c public <host name>
.1.3.6.1.4.1.1556.17.15.46.65.63.53.1.1.2

    Get the list of all routesets on the system and display their DPC.

    DPC object tag is 2 as per ptMTPRoutesetDPC OBJECT-TYPE in the MIB.

  • No labels