-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Um:
subnet zero should not have an issue here since you are not using
this block for a local network. ip classless might be an issue, the
router is taking .0 as a classless ip. Make sure you have the
classless statement in your config.
Douglas M. Todd, Jr.
Network Engineering
Partners Health Care
t: 617-726-1403
c: 617.943.2396
pgp finger: 9429 CAE3 B2D1 C2E1 DFBC E7A6 E90A 9BE5 C7B6 47BC
verisign:
- -----Original Message-----
From: Brian [mailto:bri@sonicboom.org]
Sent: Wednesday, August 08, 2001 2:16 PM
To: Charles Sprickman
Cc: cisco-nsp@puck.nether.net
Subject: Re: [nsp] error on adding static
Tried ip route 216.223.201.0 255.255.255.248 Serial5/1/11:0 ??
is ip subnet zero in place??
Brian "Sonic" Whalen
Success = Preparation + Opportunity
On Wed, 8 Aug 2001, Charles Sprickman wrote:
> Hi,
>
> I'm turning up a new t1 customer that is connected via a CT3
> interface. On adding a static route, I get the following message:
>
> core-1(config)#ip route 216.223.201.0 255.255.255.248
> 216.223.200.66 %Invalid next hop address (it's this router)
>
> It seems to be lying.
>
> The interface has the next address down in the .64/30:
>
> Serial5/1/11:0 is up, line protocol is up
> Hardware is PA-MC-2T3+
> Description: -circid-
> Internet address is 216.223.200.65/30
>
> The routing table entry for this looks correct:
>
> core-1#sh ip route 216.223.200.64
> Routing entry for 216.223.200.64/30
> Known via "connected", distance 0, metric 0 (connected, via
> interface)
> Redistributing via ospf 1
> Advertised by ospf 1 subnets
> Routing Descriptor Blocks:
> * directly connected, via Serial5/1/11:0
> Route metric is 0, traffic share count is 1
>
> Looking for something else with the .66 address in the running
> config is futile:
>
> core-1#sh conf | inc 216.223.200.66
> core-1#sh conf | inc 216.223.200.65
> ip address 216.223.200.65 255.255.255.252
>
> This is a 7206 VXR running 12.0(7)XE1 with CEF enabled. Turning
> CEF on/off or on/off/on has no effect.
>
> The T1 also shows up/up (hdlc), and has tested clean to the smart
> jack, but I cannot ping the far end, likely because it seems the
> router thinks it has an interface somewhere with that address. At
> some point in the past I had a PA-T3 in the chassis that had that
> address, but the card has been removed AND the router has been
> reloaded afterwards.
>
> Where else can I go with this?
>
> Thanks,
>
> Charles
>
> | Charles Sprickman | Internet Channel
> | INCH System Administration Team | (212)243-5200
> | spork@inch.com | access@inch.com
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0
iQA/AwUBO3GGeOkKm+XHtke8EQIbSQCeL9zr4ZFfgOdlSP0h132KCNGVNr0An2RE
ipGUTf97ZVkCi7U9goGKdzOR
=P2G4
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:48 EDT