[f-nsp] Route Not Entering Routing Table

[Joseph Hardeman]

Hi Col, Jeroen and Jeroen

I ran all of the commands that you mentioned including a sh run int e 
1/1 which is the interface that I have this circuit configured on.  I 
have tried different M-LX modules, I have tried a different port on this 
card and also a port on a different card.  I also have another switch 
that I was testing on and configured the secondary Level3 circuit on and 
it is up and running now.  With the same config as I applied last night 
to this primary router.  I am able to ping the IP from internal our 
network, plus when I do a sh int e 1/1 it shows up up.  Testing last 
night, when I made a change to this interface the IP would respond from 
external for about 2 minutes then go down again. 

Thanks everyone.

Joe

telnet at br1.atl.colocube.com#sh run | in route 0.0.0.0
ip route 0.0.0.0 0.0.0.0 70.42.176.197 distance 240
ip route 0.0.0.0 0.0.0.0 4.53.232.89 distance 240
telnet at br1.atl.colocube.com#sh ip ro direct | in ^[ ]*0.0.0.0
telnet at br1.atl.colocube.com#sh ip ro static | in ^[ ]*0.0.0.0
        0.0.0.0         0.0.0.0         70.42.176.197   1/2        1

telnet at br1.atl.colocube.com#sh ip ro direct
B:BGP D:Connected  R:RIP  S:Static  O:OSPF *:Candidate default
        Destination     NetMask         Gateway         Port       
Cost   Type
        69.25.80.0      255.255.255.0   0.0.0.0         v1         1
        69.25.88.128    255.255.255.128 0.0.0.0         v1         1
        70.42.176.196   255.255.255.252 0.0.0.0         1/2        1

telnet at br1.atl.colocube.com#sh run int e 1/1
!Building configuration...
!Current configuration : 131 bytes
interface ethernet 1/1
 port-name "Primary_Level3"
 ip address 4.53.232.90 255.255.255.252
 no flow-control
 gig-default neg-off
!

telnet at br1.atl.colocube.com#show ip route 4.53.232.90
Total number of IP routes: 140000
        Destination     NetMask         Gateway         Port       
Cost   Type
        0.0.0.0         0.0.0.0         70.42.176.197   1/2        1      S


Colin House wrote:
> I might be missing something here but it won't show up because it's not
> a directly connected route:
>
> SSH at FrontEnd_BigIronB#sh run | in route 0.0.0.0
> ip route 0.0.0.0 0.0.0.0 x.y.z.1
> SSH at FrontEnd_BigIronB#sh ip ro direct | in ^[ ]*0.0.0.0
> SSH at FrontEnd_BigIronB#sh ip ro static | in ^[ ]*0.0.0.0
>         0.0.0.0         0.0.0.0         x.y.z.1   v133       1
> SSH at FrontEnd_BigIronB#
>
> HTH,
> Col


Jeroen Oldenhof wrote:
> Joe,
>
> a 'sh ip route direct' only shows the directly attached routes, routes 
> which are there because an IP in that subnet is configured on a local 
> (physical or virtual) interface.
> Doesn't your route appear as a static route?
>
> 'show ip route static'
>
> And, as Jeroen Wunnink stated, it appears your EXTERNALIP is not 
> reachable.. what is the output of 'show ip route EXTERNALIP' ?
>
> Best,
>  - Jeroen 


Jeroen Wunnink wrote:
> Make sure EXTERNALIP is an IP which is reachable from the switch and 
> part of a locally configured subnet on the router/switch, also make 
> sure the interface is up
>
> Joseph Hardeman wrote:
>> Greetings,
>>
>> I was wondering if anyone might know why when I add an IP to an 
>> External facing Interface and add "ip route 0.0.0.0 0.0.0.0 
>> EXTERNALIP distance 240" in the config, why when I do a "sh ip route 
>> direct" it would not show up in the output?  I have added "ip policy 
>> prefer-direct-route" to the BI8000 but I do not see that IP in the 
>> routing table, nor is it pingable from outside of our network.  It is 
>> a public facing IP.  I have tried different LX modules and also 
>> different ports on two different cards on that system.
>>
>> Thanks
>>
>> Joe
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>