From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Fri Mar 17 2006 - 17:49:08 GMT-3
You need to get rid of those 0.0.0.0 mappings ;-)
HTH,
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: John Matus [mailto:John.Matus@tokiom.com]
Sent: Friday, March 17, 2006 12:39 PM
To: Brian Dennis
Cc: ccielab@groupstudy.com
Subject: RE: ospf adj problem
r4#sh frame map
Serial0/0 (up): ip 0.0.0.0 dlci 433(0x1B1,0x6C10)
broadcast,
CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 403(0x193,0x6430)
broadcast,
CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 402(0x192,0x6420)
broadcast,
CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 401(0x191,0x6410)
broadcast,
CISCO, status defined, active
Serial0/0 (up): ip 183.1.0.3 dlci 405(0x195,0x6450), static,
CISCO, status defined, active
Serial0/0 (up): ip 183.1.0.5 dlci 405(0x195,0x6450), static,
broadcast,
CISCO, status defined, active
r4#
TermServer#3
[Resuming connection 3 to r3 ... ]
line con 0
r3#sh frame map
Serial0/0 (up): ip 183.1.123.1 dlci 302(0x12E,0x48E0), static,
CISCO, status defined, active
Serial0/0 (up): ip 183.1.123.2 dlci 302(0x12E,0x48E0), static,
CISCO, status defined, active
Serial0/1 (up): ip 183.1.0.4 dlci 335(0x14F,0x50F0), static,
CISCO, status defined, active
Serial0/1 (up): ip 183.1.0.5 dlci 335(0x14F,0x50F0), static,
broadcast,
CISCO, status defined, active
r3#
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
"Brian Dennis"
<bdennis@internet
workexpert.com>
To
"John Matus"
03/17/2006 12:36 <John.Matus@tokiom.com>,
cc
Subject
RE: ospf adj problem
You may have a dynamic mapping to 0.0.0.0 from R4 to R3. Since R3 is in
init state, R3 is seeing hellos from R4 but not seeing R4 acknowledge
R3's hellos hence the init state on R3. Just do a show frame map to see
if this is the case.
HTH,
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
John Matus
Sent: Friday, March 17, 2006 12:28 PM
To: ccielab@groupstudy.com
Subject: ospf adj problem
guys,
having a problem w/ ospf adj's
hub & spoke topology, R5 is hub, R4 and R3 spokes. there is level 3
connectiviety between the spokes w/ map statements. ospf net type is
broadcast
R3 shows and init adj w/ R4, but R4 does not show an adj w/ R3
R3
*Mar 1 02:29:08.803: OSPF: Rcv hello from 150.1.4.4 area 0 from
Serial0/1
183.1.0.4
*Mar 1 02:29:08.803: OSPF: End of hello processing
r3#
*Mar 1 02:29:11.399: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/1
from 183.1.0.3
*Mar 1 02:29:12.303: OSPF: Rcv hello from 150.1.5.5 area 0 from
Serial0/1
183.1.0.5
*Mar 1 02:29:12.303: OSPF: End of hello processing
R4
1 02:28:40.951: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from
183.1.0.4
r4#
*Mar 1 02:28:41.119: %SYS-5-CONFIG_I: Configured from console by
console
r4#
*Mar 1 02:28:44.619: OSPF: Rcv hello from 150.1.5.5 area 0 from
Serial0/0
183.1.0.5
*Mar 1 02:28:44.619: OSPF: End of hello processing
r4#
*Mar 1 02:28:50.951: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0
from 183.1.0.4
r4#
*Mar 1 02:28:54.619: OSPF: Rcv hello from 150.1.5.5 area 0 from
Serial0/0
183.1.0.5
*Mar 1 02:28:54.619: OSPF: End of hello processing
r4#
don't know what coud be causing this
any ideas??
TIA
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
========================================================================
================================
This e-mail is intended solely for the individual to whom it
is
addressed. The information contained in this transmission
contains
confidential and/or proprietary information or is otherwise privileged.
If
the reader of this message is not the intended recipient, please be
advised
that any dissemination, distribution or copying of this transmission
is
strictly prohibited. If you have received this e-mail in error,
please
notify us immediately by returning it to the sender and deleting this
copy
from your system. Thank you for your
cooperation.
========================================================================
================================
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3