Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

PPP negotiation Magic Number not random

3640 with 12.2(13b) on a T1 Channelized port

point 1) I see that the MagicNumber on ID 60 CONFREQ in and ID 60 CONFACK out are the same. From what I understand this should not be the same number. The "remote" router would see this as a loopback. I have not confirmed this but I will.

Point 2) ID does not match. I see this over and over again. The ID numbers change but never match.

Jul 3 10:48:20.311 ADT: Se2/1:2 LCP: State is Listen

Jul 3 10:48:21.243 ADT: Se2/1:2 LCP: I CONFREQ [Listen] id 60 len 20

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: MRU 1520 (0x010405F0)

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: ACCM 0x00000000 (0x020600000000)

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: MagicNumber 0xF7FDA290 (0x0506F7FDA290)

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: O CONFREQ [Listen] id 46 len 10

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: MagicNumber 0x5348FB5E (0x05065348FB5E)

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: O CONFACK [Listen] id 60 len 20

Jul 3 10:48:21.247 ADT: Se2/1:2 LCP: MRU 1520 (0x010405F0)

Jul 3 10:48:21.251 ADT: Se2/1:2 LCP: ACCM 0x00000000 (0x020600000000)

Jul 3 10:48:21.251 ADT: Se2/1:2 LCP: MagicNumber 0xF7FDA290 (0x0506F7FDA290)

Jul 3 10:48:21.263 ADT: Se2/1:2 LCP: I CONFACK [ACKsent] id 24 len 10

Jul 3 10:48:21.263 ADT: Se2/1:2 LCP: MagicNumber 0x5348052D (0x05065348052D)

Jul 3 10:48:21.263 ADT: Se2/1:2 LCP: ID 24 didn't match 46, discarding packet

Jul 3 10:48:23.247 ADT: Se2/1:2 LCP: TIMEout: State ACKsent

I have tried

shut

no shut on the se2/1:2

I can get the connection up for a while if I reboot the remote router. At first the ckt was up 2 weeks. Now it will only stay up for an hour or two.

Any suggestions?

PS

sh int 2/1:2 shows many interface resets but no carrier transitions

2 REPLIES
Silver

Re: PPP negotiation Magic Number not random

1)Magic number is the MD5 secret number which is unique for each packet and if the same number is seen, then it means that the packet is looped and has not reached the destination. Whenever the same magic number is seen for ConfReq and Confack( with same ID), it means that pots line is physically looped. You may need to contact your local telephone company.

New Member

Re: PPP negotiation Magic Number not random

Thank you for your reply.

That is what the doc's on the Cisco site say but that is not what I am seeing. In this negotiation that completes successfully the Magic # and the ID are the same on ID 35.

I then captured negotiation that worked. If I am reading this correctly. After ID 35 the LCP state is Open and so on until the route is added.

Jul 7 10:01:32 kputel-gw.kpunet.net 261271: Jul 7 10:01:31.691 ADT: Se2/1:0 LCP: State is Listen

Jul 7 10:01:33 kputel-gw.kpunet.net 261273: Jul 7 10:01:32.619 ADT: Se2/1:0 PPP: Using default call direction

Jul 7 10:01:33 kputel-gw.kpunet.net 261274: Jul 7 10:01:32.619 ADT: Se2/1:0 PPP: Treating connection as a dedicated line

Jul 7 10:01:33 kputel-gw.kpunet.net 261275: Jul 7 10:01:32.619 ADT: Se2/1:0 PPP: Phase is ESTABLISHING, Active Open [0 sess, 1 load]

Jul 7 10:01:33 kputel-gw.kpunet.net 261276: Jul 7 10:01:32.619 ADT: Se2/1:0 LCP: O CONFREQ [Closed] id 30 len 10

Jul 7 10:01:33 kputel-gw.kpunet.net 261277: Jul 7 10:01:32.619 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:35 kputel-gw.kpunet.net 261278: Jul 7 10:01:34.619 ADT: Se2/1:0 LCP: TIMEout: State REQsent

Jul 7 10:01:35 kputel-gw.kpunet.net 261279: Jul 7 10:01:34.619 ADT: Se2/1:0 LCP: O CONFREQ [REQsent] id 31 len 10

Jul 7 10:01:35 kputel-gw.kpunet.net 261280: Jul 7 10:01:34.619 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:37 kputel-gw.kpunet.net 261281: Jul 7 10:01:36.619 ADT: Se2/1:0 LCP: TIMEout: State REQsent

Jul 7 10:01:37 kputel-gw.kpunet.net 261282: Jul 7 10:01:36.619 ADT: Se2/1:0 LCP: O CONFREQ [REQsent] id 32 len 10

Jul 7 10:01:37 kputel-gw.kpunet.net 261283: Jul 7 10:01:36.619 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:39 kputel-gw.kpunet.net 261284: Jul 7 10:01:38.619 ADT: Se2/1:0 LCP: TIMEout: State REQsent

Jul 7 10:01:39 kputel-gw.kpunet.net 261285: Jul 7 10:01:38.619 ADT: Se2/1:0 LCP: O CONFREQ [REQsent] id 33 len 10

Jul 7 10:01:39 kputel-gw.kpunet.net 261286: Jul 7 10:01:38.619 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:41 kputel-gw.kpunet.net 261287: Jul 7 10:01:40.619 ADT: Se2/1:0 LCP: TIMEout: State REQsent

Jul 7 10:01:41 kputel-gw.kpunet.net 261288: Jul 7 10:01:40.619 ADT: Se2/1:0 LCP: O CONFREQ [REQsent] id 34 len 10

Jul 7 10:01:41 kputel-gw.kpunet.net 261289: Jul 7 10:01:40.619 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:41 kputel-gw.kpunet.net 261290: Jul 7 10:01:41.607 ADT: Se2/1:0 LCP: I CONFREQ [REQsent] id 1 len 10

Jul 7 10:01:41 kputel-gw.kpunet.net 261291: Jul 7 10:01:41.607 ADT: Se2/1:0 LCP: MagicNumber 0x0BFF77B0 (0x05060BFF77B0)

Jul 7 10:01:41 kputel-gw.kpunet.net 261292: Jul 7 10:01:41.607 ADT: Se2/1:0 LCP: O CONFACK [REQsent] id 1 len 10

Jul 7 10:01:41 kputel-gw.kpunet.net 261293: Jul 7 10:01:41.607 ADT: Se2/1:0 LCP: MagicNumber 0x0BFF77B0 (0x05060BFF77B0)

Jul 7 10:01:43 kputel-gw.kpunet.net 261294: Jul 7 10:01:42.619 ADT: Se2/1:0 LCP: TIMEout: State ACKsent

Jul 7 10:01:43 kputel-gw.kpunet.net 261295: Jul 7 10:01:42.619 ADT: Se2/1:0 LCP: O CONFREQ [ACKsent] id 35 len 10

Jul 7 10:01:43 kputel-gw.kpunet.net 261296: Jul 7 10:01:42.619 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:43 kputel-gw.kpunet.net 261297: Jul 7 10:01:43.659 ADT: Se2/1:0 LCP: I CONFACK [ACKsent] id 35 len 10

Jul 7 10:01:43 kputel-gw.kpunet.net 261298: Jul 7 10:01:43.659 ADT: Se2/1:0 LCP: MagicNumber 0x67B959F9 (0x050667B959F9)

Jul 7 10:01:43 kputel-gw.kpunet.net 261299: Jul 7 10:01:43.659 ADT: Se2/1:0 LCP: State is Open

Jul 7 10:01:43 kputel-gw.kpunet.net 261300: Jul 7 10:01:43.659 ADT: Se2/1:0 PPP: Phase is UP [0 sess, 1 load]

Jul 7 10:01:43 kputel-gw.kpunet.net 261301: Jul 7 10:01:43.663 ADT: Se2/1:0 IPCP: O CONFREQ [Closed] id 5 len 10

Jul 7 10:01:43 kputel-gw.kpunet.net 261302: Jul 7 10:01:43.663 ADT: Se2/1:0 IPCP: Address 64.114.232.169 (0x03064072E8A9)

Jul 7 10:01:43 kputel-gw.kpunet.net 261303: Jul 7 10:01:43.663 ADT: Se2/1:0 IPCP: I CONFREQ [REQsent] id 1 len 10

Jul 7 10:01:43 kputel-gw.kpunet.net 261304: Jul 7 10:01:43.663 ADT: Se2/1:0 IPCP: Address 64.114.232.170 (0x03064072E8AA)

Jul 7 10:01:43 kputel-gw.kpunet.net 261305: Jul 7 10:01:43.663 ADT: Se2/1:0 IPCP: O CONFACK [REQsent] id 1 len 10

Jul 7 10:01:44 kputel-gw.kpunet.net 261306: Jul 7 10:01:43.667 ADT: Se2/1:0 IPCP: Address 64.114.232.170 (0x03064072E8AA)

Jul 7 10:01:44 kputel-gw.kpunet.net 261307: Jul 7 10:01:43.667 ADT: Se2/1:0 CDPCP: I CONFREQ [Not negotiated] id 1 len 4

Jul 7 10:01:44 kputel-gw.kpunet.net 261308: Jul 7 10:01:43.667 ADT: Se2/1:0 LCP: O PROTREJ [Open] id 36 len 10 protocol CDPCP (0x820701010004)

Jul 7 10:01:44 kputel-gw.kpunet.net 261309: Jul 7 10:01:43.667 ADT: Se2/1:0 IPCP: I CONFACK [ACKsent] id 5 len 10

Jul 7 10:01:44 kputel-gw.kpunet.net 261310: Jul 7 10:01:43.667 ADT: Se2/1:0 IPCP: Address 64.114.232.169 (0x03064072E8A9)

Jul 7 10:01:44 kputel-gw.kpunet.net 261311: Jul 7 10:01:43.671 ADT: Se2/1:0 IPCP: State is Open

Jul 7 10:01:44 kputel-gw.kpunet.net 261312: Jul 7 10:01:43.675 ADT: Se2/1:0 IPCP: Install route to 64.114.232.170

Is there a trigger number of these matching Magic number and ID packets that it takes to tel the interface that it is looped?

BTW I am the telephone company.

230
Views
0
Helpful
2
Replies