Reaching this stage indicates that the D7 package is
functioning correctly on all machines in the SS7 cluster, and that
this machine has the correct configuration.
This stage checks if all the SS7 links are functional. Perform
the following steps:
- Logon to one of the SS7 Servers as dtuser
- Enter the SS7_MAINT command
- From the top level menu, enter M (D7 Maintenance Programs)
- On the submenu, enter L (Link Status)
The link monitoring program (AccessStatus) is started, and a
screen similar to that below appears:
Figure 1. The link monitoring program screen
There should be one entry displayed for each Link that was configured
in SS7itty. If one is missing, return to SS7itty and review the Link
configuration. There might also be additional information present
in the log file /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/log/mml.log.
Once you have corrected the link information, perform the following
steps:
- Reapply the SS7 configure in SS7_MAINT, by selecting options C,
followed by S alongside the name of the machine on which the Link
is configured to be present. Review the error log, but ignore any
errors that suggest duplication.
- Otherwise perform the reconfiguration as outlined in Migration.
Based on the status of the links in the link monitoring display,
select from the following:
Status |
Action |
If an entry is not showing "is" under the column
L2State |
Go to stage 8a |
If an entry does not show "available" under
L3State, but does show "is" under L2State |
Go to stage 8b |
If all entries show "available" and "is" |
Go to Stage 9: Is the Enablement package working? |
Stage 8a: The
physical connection for this Link is faulty
Try the following procedure:
- Check that the correct port on the adapter has been cabled, and
that the cable is connected to a valid port at the remote end. If
a T1/E1 analyser is present, this will help to prove it.
- Examine the alarm files in /usr/opt/D7/access/RUN/alarmlog. Entries
that are similar to the following would point to a problem with the
physical connection:
Tue May 11 11:11:18 2004
ALARM $870101 HOST: Venus SP: 0 LVL: Minor
MTP-L2: T2 expired [lset=1 link=0]
Tue May 11 11:11:18 2004
ALARM $87010a HOST: Venus SP: 0 LVL: Minor
MTP-L2: Alignment not possible [lset=1 link=0]
- Verify that the correct timeslot has been selected when using
SS7itty.
Stage 8b: Incorrect
Point Code value
This suggests that the cabling is functioning correctly, but what
is connected at the remote end does not match the expected Point Code.
Verify that the DPC value configured in SS7itty under Link Sets matches
the Point Code of the far end.