Se1 IPCP: I CONFREQ [REQsent] id 1 len 10
Se1 IPCP: Address 192.168.180.22 (0x0306CF12B416)
Se1 IPCP: O CONFACK [REQsent] id 1 len 10
Se1 IPCP: Address 192.168.180.22 (0x0306CF12B416)
%LINEPROTO−5−UPDOWN: Line protocol on Interface Serial1,
changed state to up
Se1 IPCP: TIMEout: Time 0x476F808 State ACKsent
Se1 IPCP: O CONFREQ [ACKsent] id 17 len 10
Se1 IPCP: Address 192.168.180.2 (0x0306CF12B402)
Se1 IPCP: I CONFACK [ACKsent] id 17 len 10
Se1 IPCP: Address 192.168.180.2 (0x0306CF12B402)
Se1 IPCP: State is Open
Se1 IPCP: Install route to 192.168.180.22
dialer Protocol up for Se1
Note: For more information on reading debug ppp negotiation output, please refer to the document
Understanding debug ppp negotiation Output.
Troubleshooting Procedure
This section includes some common troubleshooting procedures. If you encounter issues at any step refer to
the ADTRAN technical documentation for more information:
Verify that the display on the front of the ADTRAN reads as follows:
Adtran ISU 128
[Switch−type] Ready
This ensures that the ISDN configuration, such as switchtypes, service profile identifiers (SPIDs) and
local directory number (LDN) have been correctly configured and accepted by the Telco.
1.
Initiate a test connection to the peer using the keypad on the ADTRAN. This can help ensure that the
ISDN circuit, and ISDN related configuration on the TA is correct.
2.
Initiate a ping to the peer. You should see the following on front panel display of the ADTRAN:
"CALLING [PHONENUMBER". This indicates that at least V.25bis is working correctly. If you do
not see the message, try swapping cables and even TAs. This can help isolate bad cables and V.35
interfaces on the TA.
3.
Activate debug dialer. Initiate a ping. Verify that you see the following in the debug output:
Serial1: Dialing cause ip (s=192.168.180.2, d=192.168.180.22)
Serial1: Attempting to dial 5551111&5551112
If you do not see the message, then the issue is DDR−related. Verify that the router configuration is as
shown above. Make sure that the routing and interesting traffic definition is configured as well.
4.
Activate debug serial interface, initiate a ping and verify that the TA raises data set ready (DSR).
Only when the router detects a high DSR, will the router attempt to negotiate PPP. If DSR does not go
up, then we must troubleshoot a lower layer such as ISDN, hardware and cabling.
5.
Related Information
ADTRAN's Web Site
•
Cable Specifications
•
Access Technology Support Pages
•
Technical Support & Documentation − Cisco Systems
•
Contacts & Feedback | Help | Site Map
