Nick
Just an aside, but, if you're connecting to an external company's network, and 
you and that external company are both using 10/8 addressing, it would be wise 
(although not necessarily essential) to use NAT to get to them.



Billo
Data Communications Co-Ordinator
Information Technology & Telecommunications
Hunter New England Health Service
ph 0249 213804 fax 0249 213038
[email protected]

>>> "Nick Allen" <[email protected]> Saturday, 25 July 2009 >>>
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]

Reply via email to