Differences between version 19 and revision by previous author of OSPF.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 19 | Last edited on Saturday, September 11, 2004 3:22:14 pm | by CraigBox | Revert |
| Older page: | version 18 | Last edited on Tuesday, August 17, 2004 8:15:35 am | by LindsayDruett | Revert |
@@ -91,13 +91,11 @@
----
!!User Comments on Implementing OSPF
-[Isomer]
says to stick everything in area , <shrug> so do it his way ok..
-
+Perry
says to stick everything in area , <shrug> so do it his way ok..
PerryLorier: Yeah, because dealing with area's is a bitch, and if you are just learning, stick everything in area 0, when your network gets large enough that convergance times are starting to become a worry, think about different areas then, but before that time, stick everything in area 0 and you'll save yourself a lot of hassle. Also, remember that Area 0 is "special" to [OSPF], so if you decide to use area 42 or whatever, it __will__ break.
-
LindsayDruett: Dealing with multiple areas is not really that bad, however, you must remember that all Areas __must__ connect directly to Area 0, that is because Area 0 is the __backbone__ Area.
If you __really__ can't meet the requirements of directly connecting to Area 0 and have to go through another area instead, you can insert a __''Virtual Link''__ - ''However, it is not a recommended strategy, I don't know if this feature is available on routers other than Cisco, but either way it is strongly advised to avoid using virtual links.''
