...and now it's fixed - thanks very much everyone who helped. I have to say though, that it does seem that what fixed it was adding the subnets command (since I hadn't even got round to restarting the ospf process). I'm not sure why I wasn't seeing the effect of it right away (meaning within half an hour). In any case, thanks again, and apologies for the last few redundant emails. Nick. ________________________________
From: Nick Allen Sent: 10 August 2009 18:20 To: Enterasys Customer Mailing List Subject: RE: [enterasys] OSPF issue... Thanks John - an old friend replied off-list, and he mentioned that "you must also restart the OSPF process on the routers"... which I hadn't realised, so will try that too. N. ________________________________ From: Burke, John [mailto:[email protected]] Sent: 10 August 2009 16:41 To: Enterasys Customer Mailing List Subject: RE: [enterasys] OSPF issue... Two things that stood out for me was the lack of a "redistribute subnet" command and that the 10.130.x.x route does not appear in the route table. Since OSPF allows for more specific routes and the 10.131.x.x, 10.132.x.x and 10.133.x.x all work properly, it's not clear why the 10.130.x.x doesn't also exist. Typically supernetting is referred to as route summarization of natural networks, i.e. 192.168.1.x/24, 192.168.2.x/24 , 192.168.3.x/24 networks as 192.168.x.x/16. I'm not sure how the 10.0.0.0/8 would be an issue. It doesn't appear that the solution is an obvious one. I would suggest contacting Enterasys Support (800) 872-8440. From: Nick Allen [mailto:[email protected]] Sent: Monday, August 10, 2009 8:29 AM To: Enterasys Customer Mailing List Subject: RE: [enterasys] OSPF issue... Thanks Jerry but that doesn't fix it. The route doesn't even appear in the "show ip ospf database" on the router where that static route is defined, so it's not actually the redistribution that's the problem as such. As per below, if I add a different subnet (one that doesn't begin with 10) then it does populate the local ospf database and then of course it distributes that just fine. The problem seems to lie with the fact that we have a supernetted route for 10.0.0.0/8 defined in OSPF and this causes the (external) 10.130.0.0/16 route to be ignored by OSPF. Nick. ________________________________ From: Jerry Woodside [mailto:[email protected]] Sent: 10 August 2009 12:45 To: Nick Allen; [email protected] Subject: RE: [enterasys] OSPF issue... Nick, Looking at your OSPF configuration below, it looks like you are actually missing the "subnets" key word at the end of the redistribute static command. See below: router ospf 1 network 172.16.4.0 0.0.0.7 area 0.0.0.0 network 172.16.2.0 0.0.0.7 area 0.0.0.0 redistribute connected subnets redistribute static passive-interface vlan 5 passive-interface vlan 21 passive-interface vlan 22 In order for your static route to be added into OSPF, you'll need to have "redistribute static subnets" in your OSPF configuration. I believe that should resolve the problem. - Jerry ________________________________ From: Nick Allen [mailto:[email protected]] Sent: Monday, August 10, 2009 7:30 AM To: Enterasys Customer Mailing List Subject: FW: [enterasys] OSPF issue... Hi, Sorry to bother you all again, but I didn't receive any replies to the below, so thought I'd try one last time before renumbering the external network. Cheers, Nick. ________________________________ From: Nick Allen Sent: 27 July 2009 10:22 To: '[email protected]' Subject: RE: [enterasys] OSPF issue... Thanks Stephen, Lou, Dave and Bill. Dave - yes it does have the subnet option, but I think the issue is even before I get to the redistribution - it's not even populating the local OSPF database. Bill - we know there are no clashing subnets so using 10.x.x.x isn't a problem in that respect, but solving this issue (easily) could make it worth getting them to renumber their voice VLAN with a subnet that doesn't start with 10. Stephen & Lou: Thought about Stephen's suggestion, but since 10.130.x.x isn't directly connected, it doesn't exist on a directly connected VLAN interface, it's only accessible VIA a directly connected VLAN interface (VLAN 5), so I'm not sure if what you suggest is possible - unless maybe I add another area? Below is the config, and if you have any pointers, that'd be great, otherwise I might just get them to renumber theor voice VLAN and therefore sidestep the issue. Notes on the config below: 1) The route that's not propogating into OSPF is the line "ip route 10.130.0.0 255.255.0.0 172.16.5.2 1 permanent" - I've tried with and without the 'permanent' parameter. 2) 10.130.0.0 is one hop away and goes via the interface on VLAN 5 - ie. 172.16.5.2 3) would creating an area for this subnet help? 4) I changed 10.130.0.0 to 192.168.80.0/24 to test whether that propogates and of course it does, right away Site2 N7(su)->show conf router ...blurb removed... # Router Configuration begin router router enable config t router id 172.16.2.1 interface vlan 2 ip address 172.16.2.1 255.255.255.248 no shutdown exit interface vlan 4 ip address 172.16.4.2 255.255.255.248 no shutdown exit interface vlan 5 ip address 172.16.5.1 255.255.255.248 no shutdown exit interface vlan 21 ip address 10.112.0.1 255.255.0.0 no shutdown exit interface vlan 22 ip address 10.132.0.1 255.255.254.0 ip helper-address 10.112.0.22 ip helper-address 10.112.0.23 no shutdown exit ip route 198.80.123.0 255.255.255.0 172.16.5.2 1 ip route 207.24.30.0 255.255.255.0 172.16.5.2 1 ip route 10.130.0.0 255.255.0.0 172.16.5.2 1 permanent router ospf 1 network 172.16.4.0 0.0.0.7 area 0.0.0.0 network 172.16.2.0 0.0.0.7 area 0.0.0.0 redistribute connected subnets redistribute static passive-interface vlan 5 passive-interface vlan 21 passive-interface vlan 22 exit write file exit disable exit end router end Site2 N7(su)->show ip route ROUTE TABLE Destination Gateway Mask TOS Flags Refcnt Use Interface ------------------------------------------------------------------------ -------- default 10.112.0.1 00000000 0 UGC 5 0 host.0.1 10.111.1.2 10.112.0.1 00000000 0 UGH12 0 7063 host.0.1 10.111.1.202 10.112.0.1 00000000 0 UGH1 3 28870 host.0.1 10.111.1.232 10.112.0.1 00000000 0 UGH1 2 36345 host.0.1 10.112.0.0 10.112.2.2 ffff0000 0 UC 5 0 host.0.1 10.113.11.2 10.112.0.1 00000000 0 UGH12 0 72 host.0.1 127.0.0.1 127.0.0.1 00000000 0 UH 0 0 lo.0.1 127.128.0.0 127.128.0.1 ff800000 0 UC 1 0 etrs0 127.128.0.4 127.128.0.1 00000000 0 UH1 1 1515 etrs0 ------------------------------------------------------------------------ -------- Site2 N7(rw)->Router>show ip ospf database OSPF Router with ID(172.16.2.1) Displaying Net Link States(Area 0.0.0.0) LinkID ADV Router Age Seq# Checksum 172.16.3.2 172.16.2.2 1020 0x80000697 0x714f 172.16.2.2 172.16.2.2 1127 0x800007cf 0xfb8d 172.16.4.2 172.16.2.1 1126 0x80000004 0x9bbf Displaying Router Link States(Area 0.0.0.0) LinkID ADV Router Age Seq# Checksum LinkCount 172.16.2.1 172.16.2.1 1129 0x80000e5a 0x76cb 2 172.16.3.1 172.16.3.1 1038 0x80000f55 0x8bb7 2 172.16.2.2 172.16.2.2 1017 0x800007d7 0x8446 2 Displaying External Link States LinkID ADV Router Age Seq# Checksum Tag 10.112.0.0 172.16.2.1 1594 0x800007e1 0x6636 0 10.132.0.0 172.16.2.1 1594 0x800007e1 0x7019 0 172.16.2.0 172.16.2.1 1594 0x800007e1 0x68f6 0 172.16.5.0 172.16.2.1 1594 0x80000245 0x8f6e 0 207.24.30.0 172.16.2.1 1594 0x80000245 0x7c36 0 198.80.123.0 172.16.2.1 1594 0x80000245 0x4cd9 0 172.16.4.0 172.16.2.1 1594 0x800000df 0x6bfa 0 10.113.0.0 172.16.3.1 886 0x8000079e 0xd904 0 10.133.0.0 172.16.3.1 886 0x8000079e 0xe3e6 0 10.133.254.0 172.16.3.1 886 0x8000079e 0xeedc 0 0.0.0.0 172.16.2.2 1365 0x800007d2 0x46de 0 10.0.0.0 172.16.2.2 1365 0x800007d2 0xc357 0 10.111.0.0 172.16.2.2 1365 0x800007d2 0x8a21 0 10.131.0.0 172.16.2.2 1365 0x800007d2 0x9404 0 10.131.254.0 172.16.2.2 1365 0x800007d2 0x9ff9 0 128.33.0.0 172.16.2.2 1365 0x800007d2 0x3251 0 172.16.2.0 172.16.2.2 1365 0x800007d2 0x80ec 0 172.16.3.0 172.16.2.2 1365 0x800007d2 0x75f6 0 Site2 N7(rw)->Router> ________________________________ From: Stephen Wilson [mailto:[email protected]] Sent: 24 July 2009 20:36 To: Enterasys Customer Mailing List Subject: RE:[enterasys] OSPF issue... Nick, I may be remembering wrong, and if I am hopefully someone will correct me, but I believe when you redistribute a static route into ospf by default it is a type 2 external route. If your supernetted route is part of the OSPF cloud, it would be considered an internal route and therefore get higher priority and be placed into the routing table. On your N7 connected to the other company's network, you can add that vlan interface into the OSPF area (making it an internal route) and then make it a passive interface to keep from sending or receiving OSPF updates. If I'm understanding your description correctly that should solve your issue. Stephen Wilson Network Manager Western Carolina University 828-227-3215 From: Nick Allen [mailto:[email protected]] Sent: Friday, July 24, 2009 1:56 PM To: Enterasys Customer Mailing List Subject: [enterasys] OSPF issue... Hi, We've got 3 routers (2 x N7's + 1 x C2 with routing license on) on 3 sites (1 on each site) connected in a triangle. They are all part of an OSPF area and this works great. We use 10.111.0.0/16 for our data VLAN at 1 site and 10.131.0.0/16 for our voice VLAN at that same site. We use 10.112.0.0/16 for our data VLAN at the 2nd site and 10.132.0.0/16 for our voice VLAN at that same site. We use 10.113.0.0/16 for our data VLAN at the 3rd site and 10.133.0.0/16 for our voice VLAN at that same site. All those routes propogate round the routers via OSPF just fine. We also have a supernetted catch-all route of 10.0.0.0/8 which goes via a gateway on the 10.111 network which hooks us into our worldwide VPN. Since our other Worldwide sites which are accessibe via the VPN also all use 10.x.x.x/16 subnets, this supernet saves us having to configure all those routes locally individually - we essentially just pass everything that's begins with a 10 that's not local, to the VPN gateway to worry about - that works fine. That 10.0.0.0/8 route also propogates just fine round all 3 routers. However, the problem is, we have a VLAN on the 2nd site which connects the N7 at that site to another company's network. Their network is outside of the OSPF area (in fact we only have one connection to it anyway) and is on Cisco kit. The numbering of their network is 10.130.0.0/16 and I can't get that route to propogate around the OSPF network. Is it possible that the existence of the 10.0.0.0/8 route is what's preventing the 10.130.0.0/16 route being propogated? I've tried removing and re-adding the route and redistributing the routes (redistribute static) but it won't go. It just doesn't show up in the "show ip ospf database" even on the router where the route is defined - which is obvioulsy why it'll never propogate. I tried adding a 192.168.80.0/24 network just to check propogation and that one works just fine, so can't see why this one won't unless the supernet is the cause. I know this has nothing to do with the cisco kit as we also route to other networks on that 3rd party site just fine although these don't begin with a 10. Hope this is clear enough and that someone can explain what's (not) happening and how we can address it! Thanks in advance. Nick. This e-mail is intended only for the named person or entity to which it is addressed and contains valuable business information that is proprietary, privileged, confidential and/or otherwise protected from disclosure. If you received this e-mail in error, any review, use, dissemination, distribution or copying of this e-mail is strictly prohibited. Please notify us immediately of the error via e-mail to [email protected] and please delete the e-mail from your system, retaining no copies in any media. We appreciate your cooperation. Reg. Office: TBWA UK GROUP Ltd, 76-80 Whitfield Street, London, W1T 4EZ Company Reg. #: 4332188 (UK) Company VAT #: GB 656 8994 61 * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
