Hi Jeroen,
Yeah, we have two different provider uplinks and we will be adding at
least one more in the coming future.
When I do a sh int e 1/1 it is showing up/up. I also checked to make
sure the media was compatible. LH on Level3 side and LX on my side. I
have had the Fiber tested between their equipment and mine and it is
good. I would think a hardware issue, but when I make a change, such as
remove and re-add "gig-default neg-off" or remove and re-add the "ip
route 0.0.0.0 0.0.0.0 4.53.232.89 distance 240" the interface starts
pinging for a minute or two and then stops responding. So for some
reason it is not being added to my routing table. I have a J-BxGMR
management card with 512M ram, here is my output of 'sh ver':
SW: Version 07.8.01bT53 Copyright (c) 1996-2004 Foundry Networks, Inc.
Compiled on Jul 21 2005 at 19:38:21 labeled as B2R07801b
(3659886 bytes) from Primary b2r07801b.bin
SL 1: J-BxGMR4 JetCore Management Module, SYSIF 2 (Mini GBIC), M4, ACTIVE
4096 KB BRAM, JetCore ASIC IGC version 49, BIA version 8a
32768 KB PRAM and 2M-Bit*1 CAM for IGC 0, version 0449
32768 KB PRAM and 2M-Bit*1 CAM for IGC 1, version 0449
==========================================================================
SL 3: J-BxG JetCore Gig Fiber Module, SYSIF 2 (Mini GBIC)
4096 KB BRAM, JetCore ASIC IGC version 49, BIA version 8a
32768 KB PRAM and 2M-Bit*1 CAM for IGC 8, version 0449
32768 KB PRAM and 2M-Bit*1 CAM for IGC 9, version 0449
==========================================================================
Active management module:
466 MHz Power PC processor 750 (version 8/8302) 66 MHz bus
512 KB boot flash memory
16384 KB code flash memory
512 KB SRAM
512 MB DRAM
The system uptime is 46 days 23 hours 42 minutes 37 seconds
The system : started=warm start reloaded=by "reload"
When I do a "sh ip route static" only the 70.42.176.196/30 shows up, not
my other route. I removed and re-added the IP information for the
Interface and also removed and re-added the ip route for that interface
several times last night. Including moving the connection to port 1/3
and also 3/1. Both of which responded for a minute or two before
stopping again.
I am very confused as to why it is doing this and am hoping someone
knows of a reason or a guess why when adding a new interface to the
BI8000 it might not be added to the routing table right. I would not
think it would be this hard to add an interface to a router.
Thanks
Joe
Jeroen Oldenhof wrote:
ok.. what is it what you are trying do here?
I see two default routes configured.. do you have 2 different uplinks?
It seems you have the uplinks connected to resp. ethe 1/1
(4.53.232.90/30) and ethe 1/2 (70.42.176.196/30).
Ethe 1/1 is down, Ethe 1/2 is up, that's why ethe 1/1 doesn't appear
in the 'show ip route static' or 'direct' output.
Since the distances are equal on both default routes they should both
appear in 'show ip route static' if both links were up.
Anyway.. it seems there's a physical issue here you should solve first..
could you post the output of 'show media'?
And what's connected on the other end of the circuit? Is everything ok
over there?
Best,
- Jeroen
Joseph Hardeman schreef:
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
[email protected]#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
[email protected]#sh ip ro direct | in ^[ ]*0.0.0.0
[email protected]#sh ip ro static | in ^[ ]*0.0.0.0
0.0.0.0 0.0.0.0 70.42.176.197 1/2 1
[email protected]#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
[email protected]#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
!
[email protected]#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:
s...@frontend_bigironb#sh run | in route 0.0.0.0
ip route 0.0.0.0 0.0.0.0 x.y.z.1
s...@frontend_bigironb#sh ip ro direct | in ^[ ]*0.0.0.0
s...@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
s...@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
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
