Nortel DMS-100 Logical Terminal Mapping Table (LTMAP) |
Table Name
Logical Terminal Mapping Table
Functional Description of Table LTMAP
This table maps logical terminals to a Line Equipment Number (LEN) or trunk span DS0 location and the terminal equipment interface, depending on the Logical Terminal Access Privilege (LTAP).
The key to this table is LTKEY (LTGRP, LTNUM).
No data store is required for this table. It uses the data store of table LTDEF.
Datafill Sequence
The following tables must be datafilled after table LTMAP:
Datafill
The following table describes datafill for table LTMAP:
----------------------------------------------------------------------------------------------
Table LTMAP Field Descriptions
Field Subfield Entry Explanation and Action
----------------------------------------------------------------------------------------------
LTKEY See subfields Logical Terminal Key
This field consists of subfields LTGRP and
LTNUM.
LTGRP Alphanumeric Logical Terminal Group
(maximum 8 Enter the group of the logical terminal.
characters)
LTNUM 1 to 1,022 Logical Terminal Number
Enter the logical terminal number within the
group.
----------------------------------------------------------------------------------------------
MAPPING See subfield Logical Terminal Mapping
This field consists of subfield MAPTYPE.
MAPTYPE CLLI, LEN, or XSG Logical Terminal Mapping Type
Enter the type of mapping being used.
Enter "CLLI" and datafill refinement CLLI.
Enter "LEN" and datafill refinement LEN.
Enter "XSG" and datafill refinement XSG.
For Primary Rate Access (PRA), the logical
terminal identifier must be mapped to a CLLI.
CLLI Alphanumeric Common Language Location Identifier
(maximum 16 Enter the CLLI of the PRA trunk to which the
characters) logical terminal is assigned.
Note: If the mapped CLLI has the IP option
provisioned in table TRKGRP, then the
variant of the LTID must be NI2.
LEN See subfields Line Equipment Number
This field defines the physical location of the
equipment that is connected to a specific
telephone line.
For Integrated Services Digital Network (ISDN)
lines, field LEN consists of subfield Logical
Terminal Identifier (LTID). For non-ISDN lines,
field LEN consists of subfields SITE, FRAME,
UNIT, DRAWER or LSG, SHELF, SLOT, and CIRCUIT.
XSG 0 to 749 X.25 / X.75 Service Group
This field associates an Echo Station LTID to a
XSG for user loop back testing. Identify the XSG
by a X.25 Link Interface Unit (XLIU) in the range
of 0 through 749.
----------------------------------------------------------------------------------------------
OPTION BCH, DCHCHNL, Option
ILDCHNL, LTBYTE, This field is a vector of maximum two entries.
MEM, PHI, TEI, If less than two entries are required, end the
or XSG list with a "$" (dollar sign).
Enter the option that is based on the terminal
access privilege chosen.
Option B-Channel (BCH) is used for BRI packet
data (that is, for PB [high-speed packet-switched
data] type terminals only). Datafill refinement
BCH.
Note: TEI is disallowed for packet-only and
integrated NITs with dynamic TEI.
If the Member (MEM) option is checked, then the
specified LTID is packet on PRI LTID and a member
number must be provided which corresponds to the
member number in table TRKMEM.
BCH B1 or B2 BRI B-Channel
Enter the B-channel that is selected for packet
data. This is specified for PB-type terminals
only.
Option D-Channel (DCHCHNL) is valid for D
(low-speed packet data), BD Circuit Switched (CS)
voice, or 2BD (two B-channel voice and and
low-speed packet mode data) LTIDs that are
associated with loops on an ISDN LTC or LGC.
This option is also valid for all v5.2 ISDN lines.
DCHCHNL 0 to 31 D-Channel Handler (DCH) Channel
Enter the DCH to which the loop is connected.
NI-2 D-channels can only be datafilled on the
24th channel of a carrier. This option is also
valid for all v5.2 ISDN lines.
DCHCHNL must be specified for 2BD-type terminals.
Option ISDN Line Drawer Channel (ILDCHNL) is
defined for D-packet switching on ISDN line
drawer for remote (ILDR) terminals. Datafill
refinement ILDCHNL.
ILDCHNL BD1 or BD2 ILD Channel
Enter the BD-channel number to identify the
channel for D-packet switching.
Option Logical Terminal Byte (LTBYTE) is used
to examine or set the internal LTID BYTE value.
Datafill refinement LTBYTE.
LTBYTE 0 to 255 Logical Terminal Identifier Type
Enter the value used internally to identify the
terminal on the loop.
This option is required during a Batch Change
Supplement (BCS) Switch of Activity (SWACT) to
ensure the LTID BYTE does not change.
Any entry outside the range indicated for this
field is invalid.
Option Packet Handler Interface (PHI) is used
for D and BD-type terminals. Datafill
refinement PHI.
MEM 0 to 32,767 Member
Enter the member number of the trunk group for
PRI with semipermanent packet.
PHI 0 to 1,023 Packet Handler Interface
Enter the PHI that is selected for D and DB
type terminals.
Option Terminal Endpoint Identifier (TEI) is
used for static TEI terminals to indicate the
value of the static TEI. Datafill refinement
TEI.
TEI 0 to 63 Terminal Endpoint Identifier
Enter the terminal endpoint identifier that is
specified for static TEI terminals.
XSG 0 to 749 X.25 / X.75 Service Group
Enter the number of the X.25 or X.75 XSG to which
the provisioned LTID with D-channel packet
service is being assigned.
----------------------------------------------------------------------------------------------
-End-
Datafill Example
The following example MAP display shows sample datafill for table LTMAP.
Note: In software release NA014 and up, the mapping of a LTID provisioned with an On-Demand B-Channel (ODB) service to a LEN requires the provisioning of the LTID with the XSG option in table LTMAP. See LTKEY entries PKT 100 and PKT 101 in the following example.
LTKEY MAPPING OPTION _______________________________________________________________ ISDN 321 CLLI K2KLTI64LP2 (TEI 0) $ ISDN 320 CLLI K2KLTI64LP1 (TEI 0) $ ISDN 323 CLLI LD64CL (TEI 0) $ ISDN 326 CLLI K2KLTC264CLLP1 (TEI 0) $ ISDN 327 CLLI K2KLTC264CLLP2 (TEI 0) $ ISDN 327 LEN HOST 01 0 01 04 (DCHCHNL 0) $ PKRPRA 40 CLLI PKTPRI (MEM 1) $ PKT 100 LEN ISDN 00 0 00 00 (XSG 100) (DCHCHNL 31) $ PKT 101 LEN ISDN 00 0 00 02 (XSG 110) $ |
Supplementary Information
This section explains the error messages that can occur if you incorrectly datafill table LTMAP.
Error Messages Specific to PRI with Semipermanent Packet
Reason: Primary Rate Interface (PRI) with semipermanent packet LTID supports option MEM only.
Only MEM option should be present for packet on PRI.
Action: Perform the LTMAP datafill with only option MEM present.
Reason: The following error message displays if the MAP type is not CLLI for PRI with semipermanent packet.
The map type should be CLLI for packet on PRI LTIDs.
Action: Use CLLI instead of LEN as the datafill for MAP types.
Reason: The following error message displays if table TRKMEM does not datafill to map the CLLI and MEMBER to DS0 datafill in table SPECCONN.
Table TRKMEM should be datafilled before LTMAP.
Action: Datafill table TRKMEM for a member other than 24.
Reason: The following error message displays if the trunk group type is not PRA.
The trunk group should be PRA for packet on PRI trunk.
Action: Use CLLI. CLLI has a PRA trunk group type.
Reason: The following error message displays if the signaling type of the subgroup is not X.25 for packet on PRI CLLI MEM.
The signaling type of subgroup should be X.25 for packet on PRI CLLI MEM.
Action: Enter "X25". X.25 is the signaling type of subgroup for the packet on PRI CLLI MEM.
Reason: The following error message displays if CLLI and MEMBER already map in table LTMAP.
The CLLI & MEMBER are already in use.
Action: The same CLLI and MEMBER cannot map to another LTID.
Reason: The following error message displays if the terminal class of an LTID is not a Basic Rate Access Functional Set (BRAFS).
The terminal class of the LTID is not BRAFS.
Action: The terminal class of an LTID is BRAFS for PRI with semipermanent packet.
Reason: The following error message displays if the access privilege for the LTID is D.
The access privilege of LTID must be PB.
Action: The access privileges for the LTID is PB for PRI with semipermanent packet.
Reason: The following error message displays if table KSETINV does not datafill for the correct LTID.
The LTID is not datafilled in KSETINV.
Action: The LTID datafills in table KSETINV.
Reason: The following error message displays if table KSETLINE does not datafill.
Table KSETLINE not datafilled.
Action: The LTID datafills in table KSETLINE.
Reason: The following error message displays if the LTID does not datafill in table DNCHNL.
Table DNCHNL not datafilled.
Action: The LTID datafills in table DNCHNL.
Reason: The following error message displays if the LTID does not datafill in table DNCTINFO.
Table DNCTINFO not datafilled.
Action: The LTID datafills in table DNCTINFO.
Reason: The following error message displays if the LTID maps to a LEN and operating company personnel try to map the LTID to CLLI with MEM option using the CHANGE command.
Cannot change map type. Please delete and add the tuple.
Action: Detach the LEN from the LTID and then map this LTID to CLLI.
Reason: The following error message displays if the trunk member to change is not in the Installation Busy (INB) state.
The trunk member must be INB.
Action: Change the trunk member to the INB state.
Reason: The following error message displays if operating company personnel use the table control CHANGE command for a PRI with semipermanent packet LTID and try to assign the LTID to a BRI LEN.
Cannot change packet PRI to packet BRI. Please delete and add the tuple.
Action: Delete and then re-add the tuple.
Error Message Specific to PRI Location Indicators
The following error message appears on the MAP display if the protocol variant in table LTDEF is non-Northern Telecom North America (NTNA) or non-Northern Telecom National ISDN (NTNI), and its corresponding LTID attempts to map to a Common Language Location Identifier (CLLI) whose location datafill in table TRKSGRP is LOC_MAP.
LOCATION LOC_MAP is only supported for NTNA and NTNI protocol variants. Change the protocol variant in table LTDEF.
The following error message appears on the MAP display if operating company personnel attempt to delete a tuple that table AINPRI references.
*** Delete the AINPRI entry before deleting LTMAP ***
The following error message appears if an attempt to MAP a NI-2 LTID to a CLLI datafilled as user side in table TRKSGRP (subfield IFCLASS).
*** User IFCLASS is not supported on NIPRI ***
The following error message appears on the MAP display if a B2-channel is assigned to the last card in an Integrated Services Line Card Carrier (ISLCC) and it is an ISDN line.
Only the B1-channel can be assigned on the last card in the line card carrier.
The following error message appears on the MAP display if a 2B Non-Initializing Terminal (NIT) or Fully Initializing Terminal (FIT) is assigned to an ISDN interface while the NI000050_SOC_state = IDLE.
ERROR: 2B terminals cannot be assigned to an ISDN interface. Option NI000050 must be turned ON.
For North American offices, the following error message appears on the MAP display if a 1B NIT is assigned to an ISDN interface while the NI000050_SOC_state = IDLE.
ERROR: Default terminals cannot be assigned to an ISDN interface. Option NI000050 must be turned ON.
Attention: ILDR is first available for remote switching center SONET (RSC-S) and Remote Switching Center (RSC) configurations in the NA007 release and the XPM08 stream. ILDR is first available for Remote Line Concentrating Module (RLCM), Outside Plant Module (OPM), and Outside Plant Access Cabinet (OPAC) configurations in the NA008 release and the XPM81 stream.
The following error message appears on the MAP display if an attempt is made to define a DCHCHNL option for an ILDR terminal.
ERROR: DCHCHNL option not valid for terminals on an ILD.
The following error message appears on the MAP display if the LTID is a B-type terminal (a B access privilege is defined for this LTID in table LTDEF). The LTID cannot be used for packet switching.
ERROR: ILDCHNL option not allowed for a B-type terminal.
The following error message appears on the MAP display if the LTID is a D-type terminal (a D access privilege is defined for this LTID in table LTDEF). An ILDCHNL option must be defined.
ERROR: Must specify ildchnl option for a D-type terminal.
The following error message appears on the MAP display if the LTID is a PB-type terminal (a PB access privilege is defined for this LTID in table LTDEF). The LTID cannot be used for D-packet switching, only for B-packet switching.
ERROR: ILDCHNL option not allowed for a PB-type terminal.
The following error message appears on the MAP display if the LTID is a BD-type terminal (a BD access privilege is defined for this LTID in table LTDEF). An ILDCHNL option must be defined.
ERROR: Must specify ILDCHNL option for a BD-type terminal.
The following error message appears on the MAP display if the ILDCHNL option has been assigned to a non-ILDR terminal.
ERROR: ILDCHNL option valid only for terminals on an ILD.
The following error message appears on the MAP display if the LTID is a 2B-type terminal (a 2B access privilege is defined for this LTID in table LTDEF). The LTID cannot be attached to the ILD LEN.
ERROR: A 2B-type terminal cannot be attached to the ILD LEN.
Feature ISDN Packet Single DN (AF6782) provides the following warnings when you datafill a LTID that is assigned option 2BD in table LTDEF. The 2BD option is assigned to NI-2 Integrated Terminals (IT). Feature ISDN Packet Single DN is controlled by SOC NI000051.
The following error message appears if option TEI is assigned to a LTID that was datafilled as 2BD in table LTDEF.
ERROR: TEI option not allowed for a 2BD-type terminal.
The following error message appears if option PHI is assigned to a LTID that was datafilled as 2BD in table LTDEF.
ERROR: PHI option not allowed for a 2BD-type terminal.
The following error message appears if option BCH is assigned to an LTID that was datafilled as 2BD in table LTDEF.
ERROR: BCH option not allowed for a 2BD-type terminal.
The following error message appears if option DCHCHNL is not assigned to an LTID that was datafilled as 2BD in table LTDEF.
ERROR: Must specify DCHCHNL for a 2BD-type terminal.
The following error message appears if the NI000051_SOC_state = IDLE and the SERVORD SLT ATT command or the ADD or CHANGE command is used to attach a NI-2 interface to an ISDN terminal.
Terminal cannot be assigned to an ISDN interface. Option NI000051 must be turned ON.
Error Messages Specific to the PRI-PRI Over Multiple XPMs Feature
An error message appears under the following conditions:
If a distributed PRI is mapped in table LTMAP and the protocol variant is other than NTNI the following error message is displayed:
ERROR: <CLLI> is a Distributed PRI Interface. Distributed PRI is supported only for NTNI protocol variant.
Operating company personnel can take one of the following actions:
Error Messages Specific to the Echo Station X.25 Loopback Testing Feature
The following error message appears if you try to assign more than five Echo Station LTIDS to one XSG.
ERROR: Maximum 5 Echo Station LTID can be assigned to a XSG.
The following error message appears if you try to map an Echo Station LTID to a line equipment number.
ERROR: Echo Station LTID cannot be mapped to a LEN.
The following error message appears if you try to map a non-Echo Station LTID to a XSG. Or the user tried to map an LTID that is provisioned only in table LTDEF to a XSG in table LTMAP.
ERROR: Non Echo Station LTID cannot be mapped to XSG.
The following error message appears if you try to map an Echo Station LTID to a Common Language Location Identifier (CLLI) instead of a XSG.
ERROR: Echo Station LTID cannot be mapped to a CLLI.
The following error message appears if you try to datafill options for an Echo Station LTID.
ERROR: No options are allowed to be provisioned to an Echo Station LTID.
The following error message appears if you try to map a XSG defined in table XSGDEF without a XLIU assignment to an Echo Station LTID.
ERROR: XSG is not defined in table XSGDEF.
The following error message appears if you try to change the XSG assigned to an Echo Station LTID to a XSG without a XLIU assignment in table XSGDEF.
ERROR: No XLIU is assigned to the XSG defined in table XSGDEF.
The following error message appears if you try to use the table editor CHA command to change the XSG number assigned to an Echo Station LTID.
ERROR: Change operation is not allowed for Echo Station LTID. Delete the tuple and add new tuple.
The following error message appears if you try to add an Echo Station LTID to table LTMAP when no corresponding DN tuple existed in table DNCTINFO.
ERROR: Table DNCTINFO is not datafilled for this LTID.
The following error message appears if you try to add an Echo Station LTID in table LTMAP when no corresponding DN tuple existed in table DNCHNL. Message occurs even if an entry exists in table DNCTINFO for the Echo Station DN.
ERROR: Table DNCHNL is not datafilled for this LTID.
Error Messages Specific to the On-Demand B-channel X.25 Packet Mode Data Provisioning, Data Distribution Manager, and XLIU Feature
The following error messages display and the DMS-100 operating system rejects the table LTMAP operation: