ent-map

4.326 ent-map

Use this command to create new entries in the MAP table, which allow the assignment of mated applications and Alternate RI Mate searches for use with SCCP network management. A mated application is used if the local application becomes unavailable. An Alternate RI Mate is used if all mated applications within a MAP Set become unavailable or congested.

Note:

A MAP set is a logical grouping of a set of PC/SSNs that already exist in the EAGLE MAP table. The Flexible GTT Load Sharing (FGTTLS) feature allows a PC/SSN combination to be part of more than one load-sharing group, with each PC/SSN combination defined by a different MAP set.

Note:

If the FGTTLS feature is enabled, then all existing entries in the MAP table and all existing GTA translations in the GTT table with ri=ssn are stored in default MAP sets. Additional MAP sets can be provisioned, and GTT entries can be associated to the MAP sets.

Note:

The GTT Load Sharing with Alternate Routing Indicator (GTT LS ARI) feature must be enabled to provision Alternate RI Mates.

Parameters

Note:

See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.

pc (mandatory)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

pca

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc/pca/pci/pcn/pcn24/pcn16 (mandatory): Primary remote point code.

pci (mandatory)

ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pcn (mandatory)

ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc,m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn24 (mandatory)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn16 (mandatory)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000---127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (--).; un---000---127; sna---000---15; mna---000---31

ssn (mandatory)

Subsystem number. The application’s subsystem number. This attribute is composed of the decimal representation of the 1-byte field used in the SS7 protocol.

Range:: 2 - 255

grp (optional)

Concerned point code broadcast list (CSPC) group name. The name of a group of point codes that should be notified of the subsystem status. A different CSPC group can be assigned to each mated PC/SSN. For ANSI, the EAGLE broadcasts SSP or SSA to the mate subsystem only if the mate’s point code is provisioned as part of the CSPC group to receive an SSP or SSA. This parameter must be provisioned for a node if the node is to receive SSP or SSA broadcasts, even if the node is a mated application.

Range:: ayyyyyyy
1 alphabetic character followed by up to 7 alphanumeric characters
Default:: Current value.

Note:
If the grp parameter value is specified, and the specified point code and SSN is assigned to multiple mated applications, the grp value for all mated applications containing the specified point code and SSN will be changed to the values specified in this procedure.

mapset (optional)

MAP Set ID.

Range:

dflt
new

Default:

dflt if the FGTTLS feature is not enabled

materc (optional)

Mate relative cost. The RC assigned to the mate PC/SSN that is being added to the entity set. The EAGLE determines the multiplicity mode based on the relative costs (the rc and materc parameters) of the subsystem.

Range:: 0 - 99
Default:: 50

mpc (optional)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

mpca

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

Default:

000

mpc/mpca/mpci/mpcn/mpcn24/mpcn16 (optional): Mate remote point code.

mpci (optional)

ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

Default:

0-000-0

mpcn (optional)

ITU national point code with subfield ITU number (nnnnn). The prefix subfield indicates a spare point code.

Range:

s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

Default:

00000

mpcn24 (optional)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

Default:

000

mpcn16 (optional)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000---127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (--).; un---000---127; sna---000---15; mna---000---31

Default:: 000

mrc (optional)

Message routing under congestion. This parameter indicates whether Class 0 messages to the specified PC/SSN can be routed to the next preferred node/subsystem when that PC/SSN is congested.

Range:

yes
no

Default:

yes —if ANSI

no —if ITU

mrnpc (optional)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

mrnpca

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

Default:

000

mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24/mrnpcn16 (optional): Alternate RI Mate point code.

mrnpci (optional)

ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

Default:

0-000-0

mrnpcn (optional)

ITU national point code with subfield ITU number (nnnnn). The prefix subfield indicates a spare point code.

Range:

s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

Default:

00000

mrnpcn24 (optional)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

Default:

000

mrnpcn16 (optional)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000--127; Specify a valid value for each subfield of the point, and separate the subfields with a dash (-).; un---000---127; sna---000---15; mna---000--31

Default:: 000

mrnset (optional)

Alternate RI Mate MRN Set ID. The MRN Set where the Alternate RI Mate search is performed.

Range:

1 - 3000, dflt

dflt —default MRN Set

If the mrnpc parameter is specified, and the mrnset parameter is not specified, then the value for the mrnset parameter is automatically set to dflt.

mssn (optional)

Mate subsystem number. The mate application’s subsystem number. This attribute is the decimal representation of the one-byte field used in the SS7 protocol.

Range:: 2 - 255
Default:: Parameter is not used

mwt (optional)

Mate point code weight. The weight assigned to the mate PC/SSN that is being added to a weighted entity set.

Range:: 1 - 99

rc (optional)

Relative cost. The EAGLE determines the multiplicity mode based on the relative costs (the rc and materc parameters) of the subsystem. (SeeNotes for additional information on multiplicity modes).

Range:: 0 - 99
Default:: 10

srm (optional)

Subsystem routing messages. This parameter specifies whether subsystem routing messages (SBR, SNR) are transmitted between the mated applications.

Note:

This value can be provisioned in any of the multiplicity modes, but its value only affects traffic if the multiplicity mode is DOM or COM. See the Notes section for more information on multiplicity modes.

Range:

yes
no

Default:

yes —if ANSI

no —if ITU

sso (optional)

Subsystem status option. This parameter specifies whether or not the PC/SSN is to initiate a subsystem test when a RESUME is received for the PC.

Range:

on
off

Default:

off

thr (optional)

Threshold. The in-service threshold assigned to each PC/SSN in a weighted entity set or RC group. The Weighted GTT Loadsharing feature must be turned on before this parameter can be specified.

Note:

If this parameter is not specified, a value of 1% is assigned to each weighted PC/SSN.

Range:: 1 - 100

wt (optional)

Weight. The weight assigned to the primary PC/SSN that is being added to the weighted entity set.

Range:: 1 - 99

Example

In this example, the rc parameter is not required for a solitary PC/SSN pair. If the rc parameter is not specified, the relative cost defaults to 10.

ent-map:pc=1-1-1:ssn=10:grp=xyz

This example enters 1 and 1 into the MAP table. The rc and materc parameters are required for this command, which defines a map group.

ent-map:pc=1-1-0:ssn=10:rc=10:mpc=1-1-1:mssn=10:materc=20:grp=xyz:srm=on

These examples enter a solitary point code in the MAP table with the Subsystem Status Option set to ON:

ent-map:pc=1-1-3:ssn=20:grp=abc:sso=on

ent-map:pc=2-2-3:ssn=20:grp=abc

This example sets the Subsystem Status Option to ON for the primary and mate:

ent-map:pc=1-1-4:ssn=10:rc=10:mpc=1-1-1:mssn=10:materc=20:sso=on

This example enters a solitary point code in the MAP table with the Subsystem Status Option set to OFF (the default):

ent-map:pc=1-1-6:ssn=10:rc=10:mpc=1-1-7:mssn=10:materc=20

This example creates a new MAP Set with Alternate RI Mate 1-1-3/1:

ent-map:pc=1-1-1:ssn=15:rc=10:mpc=1-1-2:mssn=25:materc=20:mapset=new:mrnset=1:mrnpc=1-1-3

The following example creates a new MAP set, and enters 1 and 1 into the newly created MAP set:

ent-map:pc=1-1-1:ssn=10:rc=10:mpc=1-1-2:mssn=20:materc=20:mapset=new

The following example enters 1 and 1 into the default MAP set:

ent-map:pc=1-1-1:ssn=15:rc=10:mpc=1-1-2:mssn=25:materc=20:mapset=dflt

The following example creates a new MAP set and enters a solitary PC/SSN value of 1:

ent-map:pc=1-1-1:ssn=10:mapset=new

This example enters a solitary PC/SSN of 1 into the default MAP set:

ent-map:pc=1-1-2:ssn=15:mapset=dflt

This example creates a new MAP set and enters a solitary PC/SSN 1 with the subsystem option ON. It specifies the sso=on parameter for all instances of PC/SSN 1:

ent-map:pc=1-1-1:ssn=10:sso=on:mapset=new

This example enters a solitary PC/SSN of 1 into the default MAP set with the subsystem option ON. The sso=on parameter is specified for all instances of PC/SSN 1:

ent-map:pc=1-1-3:ssn=15:sso=on:mapset=dflt

These examples create a weighted shared PC/SSN pair:

ent-map:pc=1-1-1:ssn=10:rc=20:wt=30:mpc=1-2-1:mssn=10:materc=20:mwt=20

ent-map:pc=1-1-1:ssn=10:rc=20:wt=30:mpc=1-2-1:mssn=10:materc=20:mwt=20:thr=40

This example creates a new MAP Set with a different ITU network type point code for the Alternate RI Mate PC:

ent-map:pci=1-001-1:ssn=15:rc=10:mpci=1-001-2:mssn=25:materc=20:mapset=new:mrnpcn=00126: mrnset=2

Example for 16 bit PC:

ent-map:pcn16=1-2-3:ssn=10:rc=20:wt=30:mpcn16=1-1-1:mssn=10:materc=20:mwt=20:thr=40

Dependencies

The PC/SSN pair cannot already exist in the MAP table.

The specified MPC/MSSN pair cannot already exist in the MAP table.

The apca and pcn24/pcn16 parameters cannot be specified for the same MAP set. The pci and pcn parameters cannot be specified for the same MAP set if the MAP set contains a true point code.

If a subsystem is configured for a subsystem number (SSN) value in the SS-APPL table, then the specified MAP table entry for that subsystem must be a valid point code type for that subsystem. The following point code types are not valid for the indicated subsystems:

For the INP subsystem, the True Point code cannot be an ITU-I point code.
For the AIQ, ATINPQ, VFLEX, and EIR subsystems, the True Point code cannot be an ITU-N24 point code.

The ANSI/ITU SCCP Conversion feature must be enabled before the network type of the CPC broadcast group can be different from the network type of the point code.

If the pci, pcn, or pcn24/pcn16 parameter is specified, then the srm=yes parameter cannot be specified.

The primary remote point code must already exist in the Route table, as a destination in the ordered route entity set, or in a cluster destination for which ordered routes are specified.

If a CSPC broadcast list group name is specified, it must already exist.

A maximum of 1024 unique remote point codes are allowed.

A maximum of 12 SSNs per remote point code can be entered.

The primary subsystem DPCs must be full point codes.

The mate subsystem DPCs must be full point codes.

The LNP, V-Flex, EIR, or INP feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before a value that is a true point code can be specified for the pca/mpca parameter.

The AINPQ, EIR, INP, or V-Flex feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before a value that is a true point code can be specified for the pcn/mpcn parameter.

The EIR or V-Flex feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before a value that is a true point code can be specified for the pci/mpci parameter.

If the mpc/mpca/mpci/mpcn/mpcn24/mpcn16 parameter is specified, then the value must exist in the Routing table.

If the mssn or materc parameter is specified, then the mpc parameter must be specified.

If the pc parameter value is an EAGLE true point code, the subsystem must have a lower relative cost than all other mated subsystems in the group.

The sso parameter cannot be specified with a point code value that is the system true point code.

A true point code cannot be routed to itself.

The mpc and mssn parameters cannot have the same values as the pc and ssn parameters.

The point code must already exist in the Concerned Point Code (CSPC) group.

The number of MPC Subsystem entries must not exceed the table capacity.

The Route table is corrupt or cannot be found.

The Site Identification table is corrupt or cannot be found.

If the Flexible GTT Load Sharing feature is not enabled, then the mapset parameter cannot be specified. If the Flexible GTT Load Sharing feature is enabled, then the mapset parameter must be specified.

The EAGLE True PC can be provisioned only in the default MAP set.

The Weighted GTT Loadsharing feature must be turned on before the wt, mwt, or thr parameters can be specified.

If the thr parameter is specified, the wt and mwt parameters must be specified.

If the mpc parameter is specified, the rc parameter must be specified.

The wt and mwt parameters must be specified together in the same command.

If the materc parameter value equals the rc parameter value, a Loadshared Group is indicated, and the rc, mpc, materc, and mwt parameters must be specified.

If the chg-sid:pctype=ansi command is entered, a value of ni=000 cannot be specified.

If the chg-sid:pctype=ansi command is entered, and a value of ni=001 – 005 is specified, a value of nc=000 cannot be specified.

If the mpc parameter value is a true point code, the subsystem must have a lower RC than all other mated subsystems in the entity set.

The maximum number of entries in the MAP table cannot be exceeded.

The maximum number of possible entries in the MAP table for the specified True Point Code cannot be exceeded. Maximum entries for the ANSI, ITU-I, and ITU-N point codes are:

ANSI—2 (ANS41 AIQ and LNP), 4 (ANSI41 AIQ, ATINPQ, INP, and V-FLEX)
ITU-I—4 (ANSI41 AIQ, ATINPQ, EIR, V-FLEX)
ITU-N—5 (ANSI41 AIQ, ATINPQ, EIR, INP, and V-FLEX)

Note:

LNP is mutually exclusive with ATINPQ and V-FLEX, unless the Dual ExAP Config feature is enabled.

If the mwt parameter is specified, the mpc parameter must be specified.

If the mpc parameter is specified, the mssn and materc parameters must be specified.

The entity set being created must be either solitary or dominant to use the true point code as a point code.

The MAP table is corrupt or cannot be found.

If the thr parameter is specified, the rc1, rc2, rc3, and rc4 parameters must be of equal value.

If the mpc parameter is specified, then the mssn parameter must be specified.

SRM=YES cannot be entered with ITU point codes.

If the mpc or mssn parameter is specified, then the materc parameter must be specified.

If the pc/ssn parameters and the mpc/mssn parameters are specified, then the rc parameter must be specified.

If the pcn or mpcn parameter is specified, then the format of the parameter must match the format dictated by the chg-stpopts:npcfmti command.

A True PC cannot be routed to itself.

The Spare Point Code Support feature must be enabled to allow provisioning of an ITU-I or ITU-N spare point code.

The True Point Code can be provisioned only in the default MAPSET.

Unable to access database. Severe database failure.

Failed reading SS APPL table.

The values specified for the pc and mpc parameters cannot be associated with proxy point codes.

If the mrnset parameter is specified, then the mrnpc parameter must be specified.

The GTT LS ARI feature must be enabled before the mrnset or mrnpc parameters can be specified.

The value specified for the mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24/mrnpcn16 parameter must be a full point code.

The point codes and alternate RI Mate point codes must have the same network type as shown:

ITUI, ITU-N, ITU-I spare, ITU-N-spare—ITUI, ITU-N, ITU-I spare, ITU-N-spare
ANSI—ANSI
ITUN-24—ITUN-24
ITUN-16 ---ITUN-16

The value specified for the mrnset parameter must already exist in the MRN table.

The MRN table is corrupt or cannot be found.

The value specified for the mrnpc parameter must already exist in the specified MRN Set.

The mrnset parameter cannot be specified if the MAP Set specified by the mapset parameter contains a True Point Code.

The ent-map command will reject provisioning of local subsystem for ITUN16 SID, so that ITUN16 MSUs won't be forwarded to Local Subsystems.

SSN configured for SFAPP cannot be used in any command for any configuration

Notes

Up to 128 PC/SSN pairs can be entered into a mated PC/SSN group.

Multiplicity Modes

For the -map commands, an entity set consists of a group of PC/SSNs that are used for traffic distribution, and an RC group consists of PC/SSNs within an entity set that have the same RC. In loadsharing mode, an entity set contains 1 RC group. In combined loadsharing/dominant mode, an entity set can contain multiple loadsharing groups.

Note:

For dominant and combined loadsharing/dominant modes, the PC/SSN in the MAP table where traffic distribution initializes is determined by the result of GTT translation and is referred to as the preferred PC/SSN. The preferred PC/SSN may not be the lowest cost entry.

The EAGLE supports the following multiplicity modes for nodes/subsystems:

When a PC/SSN pair is not replicated, the pair is in solitary (SOL) mode. The subsystem acts as the only application, with no backup. If this subsystem fails, messages routed to it are discarded and SCCP management returns “Subsystem Unavailable” messages to the originator.
A group of replicated PC/SSN pairs are in dominant (DOM) mode if each PC/SSN pair in the group has a unique RC. The specified subsystem with the lowest RC acts as the primary subsystem, while the mate subsystem acts as a backup.
A group of replicated PC/SSN pairs are in load sharing (SHR) mode if each PC/SSN pair in the group has the same RC. All messages are evenly distributed at the SCCP level to all nodes/subsystems in the group. If failure occurs, the non-affected subsystem assumes the load of its failed mate.
The combined load sharing/dominant (COM) mode supports a combination of load sharing and dominant mode. A group of PC/SSN pairs are in COM mode when at least two of the PC/SSN pairs have the same RC and another node subsystem in the group has a different RC.

If the XMAP feature is enabled, the MAP table can have up to either 2000 or 3000 entries, depending on the controlled feature Part Number that is enabled. If XMAP is not enabled, the MAP table can contain up to 1024 user entries.

The sso parameter changes the initialization of the subsystem status (“prohibited” or “allowed”) for PC/SSN MAP entries. The EAGLE previously marked the subsystem status “allowed” for each PC/SSN entry. The sso parameter marks the subsystem status “prohibited” for each new entry that has sso=on. This causes the EAGLE to generate an SST to the remote point-code when an MTP-RESUME is received. Upon reception of an SSA, the subsystem status is marked “allowed”.

In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).

When the Flexible GTT Load Sharing feature is on, MAP load sharing sets are supported. Each set is identified by the mapset parameter.

When the Weighted GTT Loadsharing feature is turned on, weighted entity sets and RC groups are supported, and threshold values can be assigned to each PC/SSN.

When the GTT Load Sharing with Alternate Routing Indicator feature is enabled, an Alternate RI Mate can be provisioned.

Output


		  ent-map:pc=1-1-1:ssn=10:rc=10:mpc=1-1-2:mssn=20:materc=20:mapset=new


    tekelecstp 11-03-22 11:22:28 EST  EAGLE 44.0.0
    ent-map:pc=1-1-1:ssn=10:rc=10:mpc=1-1-2:mssn=20:materc=20:mapset=new       
    Command entered at terminal #4.
    ENT-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED

    New MAPSET Created : MAPSETID = 362
    ENT-MAP: MASP A – COMPLTD 
;


		  ent-map:pc=1-1-1:ssn=10:rc=10:mapset=dflt:mrnset=1:mrnpc=1-1-2


    tekelecstp 11-03-12 11:22:28 EST  EAGLE 44.0.0
    ent-map:pc=1-1-1:ssn=10:rc=10:mapset=dflt:mrnset=1:mrnpc=1-1-2
    Command entered at terminal #4.
    ENT-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
    ENT-MAP: MASP A - COMPLTD 
;


		  ent-map:pc=1-1-1:ssn=100:rc=10:mrc=no:srm=no


    tekelecstp 11-03-12 11:22:28 EST  EAGLE 44.0.0
    ent-map:pc=1-1-1:ssn=100:rc=10:mrc=no:srm=no
    Command entered at terminal #4.
    ENT-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
    CAUTION: THE VALUE OF SRM IS EFFECTIVE WHEN MULT IS COM OR DOM AND
    THE VALUE OF MRC IS EFFECTIVE WHEN MULT IS DOM.
    ENT-MAP: MASP A - COMPLTD 
;

Related Topics