From: Daniel Kutchin (daniel@kutchin.com)
Date: Sat Nov 12 2005 - 00:09:34 GMT-3
Zouta -
that solved it! Thanx
Daniel
PS: The error messages are coming from the Ethernet interface
CDPs where odr doesn't run, so can be ignored.
----- Original Message -----
From: Zouta oxpf
To: Daniel Kutchin
Cc: ccielab@groupstudy.com
Sent: Saturday, November 12, 2005 3:56 AM
Subject: Re: ODR woes - CDP-IP: IP TLV length (4) invalid for IP prefixes.
Hello Daniel:
Remove "router odr" command from r1, and see what happens. I think that
command is needed only on the hub router.
HTH
ZO
On 11/11/05, Daniel Kutchin <daniel@kutchin.com> wrote:
ODR doesn't seem to work for me.
r1 ---- r2 (hub)
r1:
interface e0
ip add 172.16.0.0.1 255.255.0.0
!
int s0.1
ip add 192.168.5.1 255.255.255.252
fram int 102
!
router odr
r2:
interface e0
ip add 192.168.0.2 255.255.255.0
!
int s0.1
ip add 192.168.5.2 255.255.255.252
fram int 201
!
router odr
--- r1#sh cdp n Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - RepeaterDevice ID Local Intrfce Holdtme Capability Platform Port ID sw1 Eth 0 125 S I WS-C2950-1Fas 0/3 r2 Ser 0.1 158 R S 2611 Ser 0/0.1
---
r1#debug cdp ip
02:16:08: CDP-IP: IP TLV length (4) invalid for IP prefixes. Expecting IP prefix from stub router r1# 02:16:42: CDP-IP: Aging routes 02:16:42: CDP-IP: Writing default route 172.16.0.1 for Ethernet0 02:16:42: CDP-IP: Writing default route 192.168.5.1 for Serial0.1 r1# 02:17:08: CDP-IP: IP TLV length (4) invalid for IP prefixes. Expecting IP prefix from stub router
---
- Using c2500-is-l.122-15.T17.bin - Both R1 and R2 give the same error messages - no odr routes found - have tried classful addresses too - Have search the Cisco website - Have searched Groupstudy archive. There was a similar thread in March. Someone referred to a link but it is broken.
Any ideas please?
Daniel
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3