Differences between version 18 and previous revision of OSPF.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 18 | Last edited on Tuesday, August 17, 2004 8:15:35 am | by LindsayDruett | Revert |
| Older page: | version 17 | Last edited on Monday, August 16, 2004 10:14:27 pm | by LindsayDruett | Revert |
@@ -28,8 +28,67 @@
# end
ONLY advertise networks that this device is responsible for.
+
+----
+!!Single Area OSPF Configuration on Cisco Routers
+
+Global Router Configurations
+
+ Router(config)#__router ospf__ ''<process-number>''
+ ''- Starts the OSPF process and identifies it with a process ID.''
+ Router(config-router)#__network__ ''<network> <wildcard-mask>'' __area 0__
+ ''- Identifies which networks - and which interfaces - partake in the OSPF process.''
+ Router(config-router)#__router-id__ ''<ip-address>''
+ ''- Used to define the RID of the router.''
+
+Example of configuring the Router ID
+
+ Router(config)#__interface loopback 0__
+ Router(config-if)#__ip address 192.168.254.1 255.255.255.0__
+ Router(config-if)#__!__
+ Router(config)#__router ospf 100__
+ Router(config-router)#__router-id 192.168.254.1__
+
+Interface Level Configurations
+
+ Router(config-if)#__ip ospf cost__ ''<cost>''
+ ''- Sets the cost or metric for the outgoing interface.''
+ Router(config-if)#__auto-cost reference-bandwidth__ ''<reference-bandwidth>''
+ ''- Allows the administrator to change the formula used to calculate the metric.''
+ Router(config-if)#__ip ospf priority__ ''<number>''
+ ''- Helps to determine which router on a multicast network will be elected as the DR/BDR.''
+ Router(config-if)#__ip ospf network__ ''<network-type>''
+ ''- Identifies the type of network to the OSPF process, which will determine how the adjacencies are created.''
+ Router(config-if)#__neighbor__ ''<ip-address>'' (__priority__ ''<number>'') (__poll-interval__ ''<sec>'') (__cost__ ''<number>'')
+ ''- States the neighbor, its address, and its capability to become the DR.''
+ ''- This command also allows the configuration of cost and the timers on the interface.''
+
+Operation Verification Commands
+
+ Router#__show ip ospf__
+ ''- Shows the OSPF process and it's details.''
+ Router#__show ip ospf database__
+ ''- Show the contents of the topological database.''
+ Router#__show ip ospf interface__
+ ''- Gives information about how OSPF has been configured on each interface''
+ Router#__show ip ospf neighbor__
+ ''- Displays all the information about the relationship that the router has with it's neighbors.''
+ Router#__show ip protocols__
+ ''- Enables you to view the IP routing protocol configuration on the router.''
+ Router#__show ip route__
+ ''- Shows detailed information about the networks the router is aware and the preferred paths to those networks.''
+ ''- Also gives the next logical hop as the next step in the path.''
+
+Troubleshooting Commands
+
+''With troubleshooting using debug, if you're connected via the console port, turn on console logging (Router(config)#__logging console__) or if connected by virtual terminal, turn on the logging monitor (Router#__term mon__)''
+
+ Router#__debug ip ospf events__
+ ''- Displays information about OSPF-related events.''
+ Router#__debug ip packet__
+ ''- Ip debugging information includes packets received, generated, and forwarded.''
----
!!User Comments on Implementing OSPF
@@ -38,9 +97,9 @@
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, all Areas __must__ connect directly to Area , that is because Area 0 is the __backbone__ Area.
+LindsayDruett: Dealing with multiple areas is not really that bad, however, you must remember that
all Areas __must__ connect directly to Area , 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.''
It is good practice to configure a Loopback Interface (other than 127.0.0.1) on your OSPF router and use that Loopback interface for the OSPF RouterID. Also it is a good idea to configure it as the OSPF Router ID rather than letting the router discover that address as the OSPF RouterID.
