[c-nsp] c7200, only one IP configured, seeing 2 as connected

[David Barak]

Hi Roger,

PPP by default will inject the /32 address of the "far" end into the connected route table.  You can modify this with either a route-map on your redistribute connected statement, or more simply add "no peer neighbor-route" under your interface configuration which will modify the PPP behavior.

-David Barak

Roger Wiklund wrote: 
> Hi
> I have a strange problem. I have a Serial interface with one /30 IP
> configure as a link network between PE and CE.
> interface Serial1/0
>  description MPLS Circuit
>  bandwidth 34368
>  ip address 206.115.103.122 255.255.255.252
>  ip nbar protocol-discovery
>  encapsulation ppp
>  framing g751
>  dsu bandwidth 34010
>  serial restart-delay 0
>  no cdp enable
>  max-reserved-bandwidth 90
>  service-policy output shape-etm
> router#sh conf | i 206.115.103.121
>  neighbor 206.115.103.121 remote-as X
> But Im seeing 2 IPs, Im actually seeing the PEs IP addressing, as beeing
> directly connected, and as I have redist connect it's beeing advertised to
> the PE.
> router#show ip route connected
> C       206.115.103.120/30 is directly connected, Serial1/0
> C       206.115.103.121/32 is directly connected, Serial1/0
> router#show ip bgp nei 206.115.103.121 advertised-routes
> *> 206.115.103.120/30
>                     0.0.0.0                  0         32768 ?
> *> 206.115.103.121/32
>                     0.0.0.0                  0         32768 ?
> Have you ever seen this before?
> Cisco 7204VXR (NPE400) processor (revision B) with 229376K/32768K bytes of
> memory.
> (C7200-IS-M), Version 12.4(25b)
> Regards
> Roger
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/