Scribd
Upload
91 views8 pages

Area 0 Is Required For OSPF To Function, and Is Considered The "Backbone"

The document discusses: 1. VLANs create unique broadcast domains and how to configure VLANs on Cisco switches including creating VLANs and assigning interfaces. 2. Details on configuring trunk links between switches including encapsulation types and allowed VLAN lists. 3. Configuring VTP modes including server, client and transparent and how it propagates VLAN information across the network.

Uploaded by

clubman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views8 pages

Area 0 Is Required For OSPF To Function, and Is Considered The "Backbone"

The document discusses: 1. VLANs create unique broadcast domains and how to configure VLANs on Cisco switches including creating VLANs and assigning interfaces. 2. Details on configuring trunk links between switches including encapsulation types and allowed VLAN lists. 3. Configuring VTP modes including server, client and transparent and how it propagates VLAN information across the network.

Uploaded by

clubman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

The OSPF Hierarchy

Area 0 is required for OSPF to function, and is considered the Backbone


area. As a rule, all other areas must have a connection into Area 0. Referred to as
the transit area to connect all other areas.

Cisco applies default costs to specific interface types:

Type Cost

Serial (56K) 1785


Serial (64K) 1562
T1 (1.544Mbps) 64
Token Ring (4Mbps) 25
Ethernet (10 Mbps) 10
Token Ring (16 Mbps) 6
Fast Ethernet 1

On Serial interfaces, OSPF will use the configured bandwidth (measured in


Kbps) to determine the cost:

Router(config)# interface s0
Router(config-if)# bandwidth 64

The default cost of an interface can be superseded:

Router(config)# interface e0
Router(config-if)# ip ospf cost 5

Changing the cost of an interface can alter which path OSPF deems the
shortest, and thus should be used with great care.

To alter how OSPF calculates its default metrics for interfaces:


Router(config)# router ospf 1
Router(config-router)# ospf auto-cost reference-bandwidth 100

The above ospf auto-cost command has a value of 100 configured, which is
actually the default. This indicates that a 100Mbps link will have a cost of 1
(because 100/100 is 1). All other costs are based off of this. For example, the
cost of 4 Mbps Token Ring is 25 because 100/4 = 25.
Configuring Basic OSPF

On Router A, to configure OSPF:

RouterA(config)# router ospf 1


RouterA(config-router)# router-id 1.1.1.1
RouterA(config-router)# network 172.16.0.0 0.0.255.255 area 1
RouterA(config-router)# network 172.17.0.0 0.0.255.255 area 0

The wildcard mask 0.0.255.255 tells us that the last two octets can match any
number.

The first network statement places interface E0 on Router A into Area 1.


Likewise, the second network statement places interface S0 on Router A into
Area 0. The network statement could have been written more specifically:

RouterA(config)# router ospf 1


RouterA(config-router)# network 172.16.1.2 0.0.0.0 area 1
RouterA(config-router)# network 172.17.1.1 0.0.0.0 area 0

In order for Router B to form a neighbor relationship with Router A, its


connecting interface must be put in the same Area as Router A:
RouterB(config)# router ospf 1
RouterA(config-router)# router-id 2.2.2.2
RouterB(config-router)# network 172.17.1.2 0.0.0.0 area 0
RouterB(config-router)# network 172.18.1.1 0.0.0.0 area 2

A passive interface, thus this command prevents


updates from being sent or received out of this interface:

RouterC(config)# router ospf 1


RouterC(config-router)# network 10.4.0.0 0.0.255.255 area 0
RouterC(config-router)# network 10.2.0.0 0.0.255.255 area 0
RouterC(config-router)# passive-interface default
RouterC(config-router)# no passive-interface e0

No routing updates are passed in either direction.


OSPF Virtual Links

Virtual links can be used as a workaround, to


logically connect separated areas to Area 0. In the above example, a virtual
link would essentially create a tunnel from Area 2 to Area 0, using Area 1 a
transit area. One end of the Virtual Link must be connected to Area 0.

Configuration occurs on the Area Border Routers (ABRs) connecting Area


1 to Area 2 (Router B), and Area 1 to Area 0 (Router C). Configuration on
Router B would be as follows:
RouterB(config)# router ospf 1
RouterB(config-router)# router-id 2.2.2.2
RouterB(config-router)# area 1 virtual-link 3.3.3.3

Configuration on Router C would be as follows:


RouterC(config)# router ospf 1
RouterC(config-router)# router-id 3.3.3.3
RouterC(config-router)# area 1 virtual-link 2.2.2.2

Again, configuration occurs on the transit areas ABRs:


RouterB(config)# router ospf 1
RouterB(config-router)# router-id 2.2.2.2
RouterB(config-router)# area 1 virtual-link 3.3.3.3

RouterC(config)# router ospf 1


RouterC(config-router)# router-id 3.3.3.3
RouterC(config-router)# area 1 virtual-link 2.2.2.2

Always remember: the area specified in the virtual-link command is the


transit area. Additionally, the transit area cannot be a stub area.
Troubleshooting OSPF

Router# show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface


7.7.7.7 1 FULL/ - 00:00:36 150.50.17.2 Serial0
6.6.6.6 1 FULL/DR 00:00:11 150.50.18.1 Ethernet0

The Neighbor Table provides the following information about each


neighbor:
The Router ID of the remote neighbor.
The OSPF priority of the remote neighbor (used for DR/BDR
elections).
The current neighbor state.
The dead interval timer.
The connecting IP address of the remote neighbor.
The local interface connecting to the remote neighbor.

To view the OSPF topology table:


Router# show ip ospf database
OSPF Router with ID (9.9.9.9) (Process ID 10)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
7.7.7.7 7.7.7.7 329 0x80000007 0x42A0 2
8.8.8.8 8.8.8.8 291 0x80000007 0x9FFC 1
Summary Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
192.168.12.0 7.7.7.7 103 0x80000005 0x13E4
192.168.34.0 7.7.7.7 105 0x80000003 0x345A

The Topology Table provides the following information:


The actual link (or route).
The advertising Router ID.
The link-state age timer.
The sequence number and checksum for each entry.

To view the specific information about an OSPF process:


Router# show ip ospf 1
The show ip ospf command provides the following information:
The local Router ID.
SPF Scheduling information, and various SPF timers.
The number of interfaces in specific areas, including the type of area.
The link-state age timer.
The sequence number and checksum for each entry.

To view OSPF-specific information on an interface:


Router# show ip ospf interface s0

The show ip ospf interface command provides the following information: The
local Router ID.
The interface network type.
The OSPF cost for the interface.
The interface Hello and Dead timers.
A list of neighbor adjacencies.

To view routing protocol specific information for OSPF:


Router# show ip protocols

The show ip protocols command provides the following information:


Locally originated networks that are being advertised.
Neighboring sources for routing information
The administrative distance of neighboring sources.

To reset an OSPF process, including neighbor adjacencies


Router# clear ip ospf process

To display information about OSPF virtual-links:


Router# show ip ospf virtual-links

To display routes to both ABRs and ASBRs:


Router# show ip ospf border-routers

To debug OSPF in realtime:


Router# debug ip ospf adj
Router# debug ip ospf events
Router# debug ip ospf hello

STUD network ? cari .


Virtual LANs (VLANs)

Each VLAN represents a unique broadcast domain:


Traffic between devices within the same VLAN is switched.
Traffic between devices in different VLANs requires a Layer 3 device to
communicate.

On Cisco switches, all interfaces belong to VLAN 1 by default. VLAN 1 is


also considered the Management VLAN, and should be dedicated for
system traffic such as CDP, STP, VTP, and DTP.

Creating VLANs

By default, all interfaces belong to VLAN 1. To assign an interface to a


different VLAN, that VLAN must first be created:

Switch(config)# vlan 100


Switch(config-vlan)# name SERVERS

To view all created VLANs,

Switch# show vlan

To statically assign an interface into a specific VLAN:

Switch(config)# interface gi1/10


Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 100

VTP server or client mode list of VLANs are


stored in a database file named vlan.dat

VTP transparent mode list of VLANs is stored


in the startup-config file in NVRAM

VLAN Port Types

A VLAN-enabled switch supports two types of ports:


Access ports
Trunk ports
Configuring Trunk Links

To manually configure an interface as a trunk port:

Switch(config)# interface gi2/24


Switch(config-if)# switchport mode trunk

For a switch that supports both ISL and 802.1Q, the tagging or
encapsulation protocol must be configured first:

Switch(config)# interface gi2/24


Switch(config-if)# switchport trunk encapsulation isl
Switch(config-if)# switchport mode trunk

Switch(config)# interface gi2/24


Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk

Important note: Both sides of the trunk must be configured with the same
tagging protocol. Otherwise, a trunk connection will not form.

The switch can negotiate the tagging protocol, using DTP:

Switch(config)# interface gi2/24


Switch(config-if)# switchport trunk encapsulation negotiate
Switch(config-if)# switchport mode trunk

To explicitly allow a subset of VLANs on a trunk port:

Switch(config)# interface gi2/24


Switch(config-if)# switchport trunk allowed vlan 3,9,11-15

To remove a VLAN from the allowed list:


Switch(config)# interface gi2/24
Switch(config-if)# switchport trunk allowed vlan remove 12

To add a specific VLAN back into the allowed list:

Switch(config)# interface gi2/24


Switch(config-if)# switchport trunk allowed vlan add 25

To allow all VLANs except for a specific range:


Switch(config-if)# switchport trunk allowed vlan except 50-99
To allow all VLANs again:

Switch(config-if)# switchport trunk allowed vlan all

To determine whether an interface is an access or trunk port:


Switch# show interface gi2/24 switchport

To view the status of all trunk links:

Switch# show interface trunk

Configuring VTP
To change the VTP domain name:

Switch(config)# vtp domain MYDOMAIN

Note that the domain name is case sensitive. To configure the VTP mode:
Switch(config)# vtp mode server
Switch(config)# vtp mode client
Switch(config)# vtp mode transparent

The VTP domain can be secured using a password:

Switch(config)# vtp password P@SSWORD!

Switch(config)# vtp version 2

To view status information about VTP:

Switch# show vtp status

To view VTP statistical information and error counters:

Switch# show vtp counters

You might also like