I'm not sure where you got the idea that one big area zero is a bad thing?
In this case, I would highly recommend it. This is a pretty small network
and I really don't see the benefit of adding hierarchy to it from a
multi-area perspective. Keep in mind that the more you segment an OSPF area
into sub-areas, the more link state qualities you forego. I'd go with your
boss on this one.
Pete
*********** REPLY SEPARATOR ***********
On 8/17/2001 at 12:17 AM Bob Timmons wrote:
>Greetings all,
>
>We're converting our 3Com router world to Cisco soon and I have a question
>regarding the OSPF design. I'm including a link to a JPG in case anyone
>wants to add their 2 cents. You can see it at:
>
>http://members.tripod.com/~bobtimmons/network-1.jpg
>
>This is a somewhat simplistic view of our network and the IP's aren't real,
>but I'm hoping it makes sense regardless. We currently have a full T1 to a
>frame cloud and our other 2 main buildings are off of that cloud as well,
>one is 1M, the other is the balance of the T. Both of the remote sites are
>pointing to the 1 PVC at our main site. My question is, would this OSPF
>network work? I know the OBAZ, (One Big Area Zero - Wow! My first
>acronym! - Hey Howard, feel free to use that one), is frowned upon, but
>that's how my boss wants it, because that's how it is now. Not good logic,
>but I have to follow orders sometimes.
>
>A note: We have other sites off of the main site (Site 1) in another Frame
>Cloud. It shouldn't affect what we're doing here, though.
>
>Also, I didn't include the IPX networks on the Ethernet ports. That's not
>a
>real issue right now.
>
>Specifically, I'm unsure about using the Loopbacks. We're going to use
>them
>for our DLSW (not pictured) links. What I'm unsure about is, can I use
>these addresses, as given, with their masks, and distribute them via OSPF
>and have it work?
>
>If I'm completely off here, please feel free to let me know.
>
>I'm including the proposed configs (snipped)
>
>Thanks!
>
>
>Site1 -
>
>hostname Site1
>!
>ip subnet-zero
>!
>dlsw local-peer peer-id 10.10.0.1
>dlsw remote-peer 0 frame-relay interface Serial5/0.1 200
>dlsw remote-peer 0 frame-relay interface Serial5/0.2 300
>!
>ipx routing 0002.4a8c.xxx1
>!
>interface Loopback0
> ip address 10.10.0.1 255.255.255.255
> no ip directed-broadcast
>!
>interface FastEthernet1/0
> ip address 10.10.1.1 255.255.255.0
> no ip redirects
> no ip directed-broadcast
> ip ospf network broadcast
> ip ospf dead-interval 60
> full-duplex
> ipx network 1 encapsulation SAP
>!
>interface Serial5/0
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay IETF
> no ip mroute-cache
> no fair-queue
> frame-relay interface-dlci 100
>!
>interface Serial5/0.1 multipoint
> description Frame-Relay to Site2 (DLCI 200) Circuit# 22222
> ip address 10.10.10.2 255.255.255.252
> no ip directed-broadcast
> ipx network B
> no arp frame-relay
> no frame-relay inverse-arp
>!
>interface Serial5/0.2 multipoint
> description Frame-Relay to Site3 (DLCI 300) Circuit# 33333
> ip address 10.10.10.6 255.255.255.252
> no ip directed-broadcast
> ipx network C
> no arp frame-relay
> no frame-relay inverse-arp
>!
>router ospf 1
> network 10.10.0.1 0.0.0.0 area 0.0.0.0
> network 10.10.10.1 0.0.0.0 area 0.0.0.0
> network 10.10.10.5 0.0.0.0 area 0.0.0.0
> network 10.10.1.1 0.0.0.0 area 0.0.0.0
>!
>ip classless
>ip default-network 0.0.0.0
>no ip http server
>
>Site 2 -
>
>hostname Site2
>!
>ip subnet-zero
>!
>dlsw local-peer peer-id 10.10.0.2
>dlsw remote-peer 0 frame-relay interface Serial5/0 100
>!
>ipx routing 0002.4a8c.xxx2
>!
>interface Loopback0
> ip address 10.10.0.2 255.255.255.255
> no ip directed-broadcast
>!
>interface FastEthernet1/0
> ip address 10.10.2.1 255.255.255.0
> no ip redirects
> no ip directed-broadcast
> ip ospf network broadcast
> ip ospf dead-interval 60
> full-duplex
> ipx network 2 encapsulation SAP
>!
>interface Serial5/0
> description Frame-Relay to Site1 (DLCI 100) Circuit# 22222
> ip address 10.10.10.2 255.255.255.252
> no ip directed-broadcast
> encapsulation frame-relay IETF
> no ip mroute-cache
> no fair-queue
> frame-relay interface-dlci 200
> ipx network B
> no arp frame-relay
> no frame-relay inverse-arp
>!
>router ospf 1
> network 10.10.0.2 0.0.0.0 area 0.0.0.0
> network 10.10.10.2 0.0.0.0 area 0.0.0.0
> network 10.10.2.1 0.0.0.0 area 0.0.0.0
>!
>ip classless
>ip default-network 0.0.0.0
>no ip http server
>
>Site 3 -
>
>hostname Site3
>!
>ip subnet-zero
>!
>dlsw local-peer peer-id 10.10.0.3
>dlsw remote-peer 0 frame-relay interface Serial5/0 100
>!
>ipx routing 0002.4a8c.xxx3
>!
>interface Loopback0
> ip address 10.10.0.3 255.255.255.255
> no ip directed-broadcast
>!
>interface FastEthernet1/0
> ip address 10.10.3.1 255.255.255.0
> no ip redirects
> no ip directed-broadcast
> ip ospf network broadcast
> ip ospf dead-interval 60
> full-duplex
> ipx network 3 encapsulation SAP
>!
>interface Serial5/0
> description Frame-Relay to Site 1 (DLCI 100) Circuit# 33333
> ip address 10.10.10.3 255.255.255.252
> no ip directed-broadcast
> encapsulation frame-relay IETF
> no ip mroute-cache
> no fair-queue
> frame-relay interface-dlci 300
> ipx network C
> no arp frame-relay
> no frame-relay inverse-arp
>!
>router ospf 1
> network 10.10.0.3 0.0.0.0 area 0.0.0.0
> network 10.10.10.6 0.0.0.0 area 0.0.0.0
> network 10.10.3.1 0.0.0.0 area 0.0.0.0
>!
>ip classless
>ip default-network 0.0.0.0
>no ip http server
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16365&t=16341
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]