A Reference Information
This Appendix contains information that is used by multiple commands.
Summary of Range Values for :link Parameter
Table A-1 lists the valid link parameter range values for signaling links assigned to each type of card for which a location can be specified in the command's loc parameter. The commands that use these values refer to this table in their link parameter description.
Note:
The port parameter is a synonym for the link parameter in signaling link definitions for EAGLE commands. The port parameter will be removed in a future EAGLE release.Table A-1 Summary of Ranges for link Parameter
| Card | Link | Supported Application |
|---|---|---|
|
E5-E1T1-B |
A-A31, B-B31 |
SS7ANSI or CCS7ITU application. |
|
E5-E1T1-B for SE-HSL |
A, B |
SS7ANSI or CCS7ITU application. The card can support a maximum of 2 SE-HSL links. |
|
E5-E1T1-B for ST-HSL-A |
A, B |
SS7ANSI application. The card can support a maximum of 2 ST-HSL-A links. |
|
E5-ATM-B |
A, A1, B |
ATMANSI or ATMITU application. The card can support up to 3 signaling links. |
|
E5-ENET/E5-ENET-B |
A-A7, B-B7 |
IPLIIMI application with sockets, M2PA/SCTP associations, or M3UA/SCTP associations. |
|
E5-ENET/E5-ENET-B |
A-A15, B-B15 |
IPSG application. |
|
SLIC |
A-A63, B-B63 |
IPSG application, SLIC card running IPSG application can support up to 128 links. |
Valid CIC Ranges for SI and MSU Types in Routing Key Static Entries
Table A-2 lists the valid CIC ranges for use with SI and MSU types in Routing Key table static entries.
Table A-2 Valid CIC Ranges for SI and MSU Types
| SI | MSU for ANSI DPC | MSU for ITU DPC | Comments |
|---|---|---|---|
|
4 (TUP) |
N/A |
CIC is 12 bits. Range is 0-4095. |
The TUP protocol is used only in ITU networks. |
|
5 (ISUP) |
CIC is 14 bits. Range is 0-16383. |
CIC is 12 bits. Range is 0-4095. |
|
|
13 (QBICC) |
CIC is 32 bits. Range is 0-4294967295. |
DRANAIV/DRANAI Mapping
Table A-3 shows the mapping between the drainaiv and dranai parameters.
Table A-3 DRANAIV/DRANAI Mapping
| DRAINAIV | DRANAI | Description |
|---|---|---|
|
1 |
sub |
Subscriber Number |
|
2 |
unknown |
Unknown |
|
3 |
natl |
National significant number |
|
4 |
intl |
International number |
|
5 |
ntwk |
Network |
DRANPV/DRANP Mapping
Table A-4 shows the mapping between the dranpv and dranp parameters.
Table A-4 DRANPV/DRANP Mapping
| DRANPV | DRANP | Description |
|---|---|---|
|
1 |
E164 |
ISDN/telephony numbering plan |
|
3 |
X121 |
Data numbering plan |
|
4 |
F69 |
Telex Numbering Plan |
NAIV/NAI Mapping
Table A-5 shows the mapping between the naiv and the nai parameters.
Table A-5 NAIV/NAI Mapping
| NAIV | NAI | Description |
|---|---|---|
|
0 |
– |
Unknown |
|
1 |
Sub |
Subscriber Number |
|
2 |
Rsvd |
Reserved for national use |
|
3 |
Natl |
National significant number |
|
4 |
Intl |
International number |
|
5–127 |
– |
Spare |
NPV/NP Mapping
Table A-6 shows the mapping between the npv and the np parameters.
Table A-6 NPV/NP Mapping
| NPV | NP | Description |
|---|---|---|
|
0 |
– |
Unknown |
|
1 |
E164 |
ISDN/telephony numbering plan |
|
2 |
Generic |
Generic numbering plan |
|
3 |
X121 |
Data numbering plan |
|
4 |
F69 |
Telex numbering plan |
|
5 |
E210 |
Maritime mobile numbering plan |
|
6 |
E212 |
Land mobile numbering plan |
|
7 |
E214 |
ISDN/mobile numbering plan |
|
8 |
Private |
Private network or network-specific numbering plan |
|
9-15 |
- |
Spare |
Cards that use the ent-card Command
Table A-7 contains information about cards that use the
ent-card command for provisioning.
Table A-7 Valid Card Applications and Types
| Card Name (as shown on card label) | Part Number | Card Type (:type) | Application Type (:appl) | Maximum Cards in the Database |
|---|---|---|---|---|
| E5-APP-B |
870-3096-01 |
e5appb |
epap elap |
2
2 |
| E5-APP-B | 870-3096-02 | e5appb | lsms
nas imf |
2
1 255 |
|
E5-ATM-B |
870-2972-01 (R) |
limatm lime1atm |
atmansi atmitu |
180 if only one link is provisioned per card. A maximum of 180 links for either application can exist in the system. |
| E5-E1T1-B†† | 870-2970-01 |
lime1 limt1 |
ss7ansi ccs7itu |
250 for each application |
|
E5-ENET-B |
870-2971-01 (R) |
dcm enet enetb ipsm stc |
ss7ipgw ipgwi iplimi stplan eroute ips ipsg |
125 for IPGWx 125 for IPLIMx 100 for ipsg 32 for stplan 32 for eroute |
|
E5-MCPM-B* |
870-3089-01 (R) |
mcpm |
mcp |
250 |
|
E5-SM4G*** |
870-2860-01 (R) 870-2860-02 (R) |
dsm |
vsccp |
18 for use with ELAP 32 for use with EPAP |
|
E5-SM8G-B*** |
870-2990-01 (R) |
dsm |
vsccp |
18 for use with ELAP 32 for use with EPAP |
|
E5-SM8G-B*** |
870-2990-01 (R) |
dsm |
siphc deirhc enumhc |
16 of the E5-SM8G-B cards connected to ELAP or EPAP for siphc and deirhc 16 of the E5-SM8G-B cards connected to EPAP for enumhc |
|
E5-TSM |
870-2943-03 (R) |
tsm |
gls |
8 |
|
SLIC |
|
slic |
ipsg siphc deirhc enumhc vsccp sfapp |
40 for use as GTT on IPSG 75 for use as GTT-disabled IPSG 40 for use as Service Module cards |
|
TELCO |
870-2904-01 |
telco |
switch |
136 |
|
* Though the system allows 250 MCPM cards, practical usage is 2. *** If any MPS-based features are running in the system, up to 25 Service Modules are allowed in the system. If only GTT is running, up to 32 Service Modules can be used in the system with the 50,000 GTT feature. † † For the E1 or T1 interface, either SS7 application (SS7ANSI or CCS7ITU) can be assigned to these cards. For more information on the E1 or T1 interface go to Appendix A "E1 Interface" or Appendix B "T1 Interface” in the Database Administration - SS7 User's Guide. Part numbers followed by (R) are ROHS numbers. These numbers are equivalent to the non-ROHS numbers that they are paired with. ***Connectivity to a TekServer 3 (T1200) with EPAP 13.0 or higher or connectivity to an E5-APP-B card with EPAP 15.0 or higher is required for more than 25 Service Module cards. |
||||
Summary of Loopback Testing Commands and Functions
Table A-8 and Figure A-1 summarize the loopback testing commands and functions in the system.
The tst-slk command provides several methods for testing signaling links. The loopback parameter provides the ability to select lxvr (local transceiver), oam, line, payload, and sltc loopback tests. The command will be rejected if a loopback test is not compatible with the link type.
- For low-speed links, the lxvr and sltc tests are allowed.
- For high-speed links (ATM, E5-ATM-B), the lxvr, oam, line, payload, and sltc tests are allowed.
- For SS7IPGW and IPGWI DCMs, the
tst-slkcommand is not supported. - For LIME1 or LIMT1 cards, or for the E5-ENET-B cards running the IPSG application, only the loopback=sltc test is allowed.
- The E5-E1T1-B cards can function as either an E1 MIM card or a T1 MIM card, depending on how the card is provisioned. The loopback=sltc test is allowed.
The act-lbp command activates test on one or more loopback points for testing data signaling link elements in one CCS7 transmission path. The maximum number of loopback points is 32.
For a single loopback point test, the parameters can be entered on the command line. If the parameters are not entered at the command line, the LFS database is used. For multiple loopback point tests, the LFS database must be used.
The ent-lbp command is used to create the loopback points in the LFS database. The LBPs may be entered in any order.
See the command descriptions in this manual for details on entering parameters and using the commands.
Table A-8 Loopback Testing Commands and Functions
| Command/Function | Card Supported | Testing limits |
|---|---|---|
|
Link State-Down Equipment tested-All links on the T1 port Purpose-tests connectivity between 2 nodes at the T1 level with some isolation for the LIU and/or framer Description-Tests near-end card for line, lxvr, and network payload loopback and far-end card for line and payload loopback. Typical use-Tests connectivity |
|
1024 concurrent tests per system |
|
No impact on link behavior other than allowing multiple points |
|
32 points per card no limit on # of cards |
|
EAGLE initiated Level 1 DS0 LFS tests Link State-Down Equipment tested-Level 1 element(s) in a signaling path Purpose-Test the error rates of a signaling path Description-Sends loopback code to establish loopback, then performs BERT test for a specified period of timed Typical use-Validates signaling path has acceptable error rate |
|
1024 concurrent tests per system |
|
Remote Loopback FAR END initiated DS0 LFS Test Link State-Up or down Equipment tested-Near end hardware up to level 2 and far end hardware level 1 interface Purpose-Auto-Loopback a BERT test to the far end Description-When receiving a loopback code, deactivate the link and go into loopback Typical use-Remotely tests the far end with standard DS0 BERT tests |
|
no limit on # of cards |
|
Link State-Up Equipment tested-Near and far end up to Level 3 Purpose-Test the entire path to the far end at Level 3 Description-Sends an SLTM out and expects an SLTA back Typical use-Validates connectivity of a signaling path |
|
1024 concurrent link tests per system |
|
Link State-Down Equipment tested-Near and far end level 1 software and hardware including all hardware on the cards Purpose-Test the entire near and far end level 1 hardware by exchanging ATM cells Description-Sends OAM cells out to far end for 60 seconds if no errors, or 2 minutes if errors are received Typical use-Verifies ATM cells can be exchanged between 2 signaling points |
|
1024 concurrent link tests per system |
|
Link State-Down Equipment tested-Near end hardware up to level 2 and far end hardware level 1 interface Purpose-Hardware continuity check between near and far end Description-The following steps occur:
Note: If the DUT boots in the middle of sequence, activate or de-activate the link, and the remote device returns to the original programming.Typical use-Checks continuity from the near end level 2 hardware to the level 1 interface at the far end for a link in line timing |
|
1024 concurrent link tests per system |
|
Link State-Down Equipment tested-Near end hardware up to level 2 and far end hardware level 1 interface Purpose-Hardware continuity check between near and far end Description-The following steps occur:
Note: If the DUT boots in the middle of sequence, activate or de-activate the link, and the remote device returns to the original programming.Typical use-Checks continuity from the near end level 2 hardware to the level 1 interface at the far end for a link in master timing |
|
1024 concurrent link tests per system |
|
Link State-Down Equipment tested-Local card Purpose-Test the near end card only Description-Test the near end card up through level 2. Typical use-Validates the card on the Eagle as good |
|
1024 concurrent link tests per system |
|
Link State-Down Equipment tested-All links on the E1 port Purpose-Tests connectivity between 2 nodes at the E1 level with some isolation for the LIU and/or framer Description-Tests near-end card for line, lxvr, and payload loopback Typical use-Tests connectivity |
|
1024 concurrent tests per system |
|
Link State-Down Equipment tested-All links on the T1 port Purpose-Tests connectivity between 2 nodes at the T1 level with some isolation for the LIU and/or framer Description-Tests near-end card for line, lxvr, and payload loopback and far end card for line and payload loopback Typical use-Tests connectivity |
|
1024 concurrent tests per system |
Figure A-1 ATM Loopback Tests
