4.235 dlt-map

Use this command to remove mate application entries, groups, or an Alternate RI Mate associated with a MAP Set. This command removes one or more entries from the Remote Point Code Subsystem Number table.

Caution:

If PC/SSNs within a weighted entity set are deleted such that the entity set's multiplicity mode becomes solitary or dominant, the weight values are reset to indicate a non-weighted entity set.

Note:

See the "Notes" section for this command for additional information on multiplicity modes.

Note:

The GTT LS ARI feature must be enabled before an Alternate RI Mate can be deleted from a MAP Set.

Parameters

Note:

At least one of these parameters must be specified: all, ssn.

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)
Post-GTT-translated 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
all (optional)
This parameter must be specified to remove all subsystem numbers associated with this point code. If this parameter is not specified, only the specified subsystem number is removed.
Range:
yes
Default:
no
mapset (optional)
The MAP set ID.
Range:
1 - 36000, dflt

dflt —Default MAP set

Default:
dflt —If the Flexible GTT Load Sharing (FGTTLS) feature is not enabled,
mrnset (optional)

Alternate RI Mate MRN Set ID.

Range:
1 - 3000, dflt
ssn (optional)
Subsystem Number.
Range:
2 - 255
Default:
The specified subsystem number is removed for the given point code.

Example

This example deletes the single entry PC 1 with an SSN value of 123 from its mated group. If this is the last entry in the group then the PC is also deleted from the MAP tables:

dlt-map:pc=1-1-1: ssn=123

This example deletes each entry of PC 1-1-1 and all SSNs associated with the PC from each of the PC/SSN mated groups. The PC is also deleted from the MAP tables:

dlt-map:pc=1-1-1:all=yes

This example deletes subsystem 10 associated with spare PC 1 from the MAP table.

dlt-map:pci=s-1-1-0:ssn=10

This example deletes subsystem 10 associated with PC 1 in MAP set 362.

dlt-map:pc=1-1-1:ssn=10:mapset=362

This example deletes PC 1 along with all the subsystems associated with this PC in the default MAP set.

dlt-map:pc=1-1-2:all=yes:mapset=dflt

This example deletes the Alternate RI Mate associated with MAP Set 362.

dlt-map:mapset=362:mrnset=1

This example deletes the Alternate RI Mate for the default MAP Set and PC/SSN 1-1-1/10.

dlt-map:mapset=dflt:pc=1-1-1:ssn=10:mrnset=1

This example deletes the entry from MAP set.

dlt-map:mapset=1:pc=1-1-1:ssn=10

This example deletes the 16 bit PC entry from MAP set.

dlt-map:mapset=1:pcn16=1-1-1:ssn=10

Dependencies

The all and ssn parameters cannot be specified together in the command.

If the all=yes parameter is specified, all SSNs for the given PC are removed.

The DPC of the primary subsystem must be a full PC.

The specified remote PC must exist in the MAP table.

The specified SSN must exist in the MAP table entity set associated with the specified remote PC.

An STP true point code that is assigned to an AIQ, ATINPQ, EIR, INP, LNP, or V-Flex subsystem cannot be deleted.

If the pcn parameter is specified, the format of the PC must match the format that was assigned with the chg-stpopts:npcfmti parameter.

The Site Identification table is corrupt or cannot be found.

If the FGTTLS feature is not enabled, the mapset parameter cannot be specified. If the FGTTLS feature is enabled, the mapset parameter must be specified.

The specified MAP set must exist in the database.

The specified PC/SSN/MAP set must already be provisioned in the MAP table.

If the pc and mapset parameters are specified, and the all=yes parameter is specified, then at least one entry for that PC/MAP set must exist in the MAP table.

If the FGTTLS feature is enabled, then a MAP entry cannot be deleted if the entry is referenced in the MRN, GTT, GTA, GTT Action, GSM MAP Opcode, or GSM MAP Screening table using the MAPSET/PC/SSN combination, or if the entry is referenced in the MRN, GTT, GTA, GSM MAP Opcode, GSM MAP Screening, or PPSOPTS table using the MAPSET/PC combination, and the entry is the last entry in that MAP set with the specified point code.

If the FGTTLS feature is not enabled, then a MAP entry cannot be deleted if the entry is referenced in the GTT, GTA, GTT Action, GSM MAP Opcode, or GSM MAP Screening table using the PC/SSN combination or if the entry is referenced in the GTT, GTA, GSM MAP Opcode, GSM MAP Screening, or PPSOPTS table using the point code, and the entry is the last entry in the default MAP set with that point code.

The MAP table is corrupt or cannot be found.

PC “Point code out of range”.

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.

The GTT LS ARI feature must be enabled before the mrnset parameter can be specified.

The value specified for the mrnset parameter must already be associated with a MAP Set.

The MRN table is corrupt or cannot be found.

If the mrnset parameter is specified, then the all parameter cannot be specified.

If a MAP set is referenced in the GTT table without an associated point code and subsystem number, then the MAP set cannot be deleted.

Notes

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/dominant loadsharing mode, an entity set can contain multiple loadsharing groups.

The EAGLE supports the following modes for nodes/subsystems:

  • When a PC/SSN pair is not replicated, the pair is in solitary 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 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. In the event of congestion, messages route to the mate subsystem. When the congestion subsides, messages are again routed to the primary (dominant) subsystem.
  • A group of replicated PC/SSN pairs are in load sharing 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. In the event of congestion or failure, the non-affected subsystem assumes the load of its failed or congested mate.
  • The combined load sharing/dominant mode supports a combination of load sharing and dominant mode. A group of PC/SSN pairs are in combined load sharing/dominant 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. A combination of node accessibility and RC determines the preferred PC/SSN.

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

When the FGTTLS feature is on, MAP load sharing sets are supported. Each MAP set is identified by a new 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.

Output

dlt-map:pc=1-1-0:ssn=10:mapset=362

    tekelecstp 08-12-22 12:20:10 EST  EAGLE 40.1.0
    DLT-MAP: MASP A - COMPLTD 
;
dlt-map:mapset=362:mrnset=1

    tekelecstp 08-12-22 12:20:10 EST  EAGLE 40.1.0
    DLT-MAP: MASP A - COMPLTD 
;

Related Topics