Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
19 views10 pages

Point-to-Point Single-Area OSPFv2-1

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views10 pages

Point-to-Point Single-Area OSPFv2-1

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

Point-to-Point Single-Area OSPFv2

+6285693811614 [email protected]
Link Addressing

+6285693811614 [email protected]
Trunking VLAN In Switch
Switch 1 (Trunk VLAN)

Switch 2 (Trunk VLAN)

Switch 3 (Trunk VLAN)

The configuration shows port on switch as a trunk using 802.1Q, a protocol for
carrying traffic from multiple VLANs with tagging. The Native VLAN is set to VLAN 99
to handle untagged traffic, typically for compatibility or non-VLAN devices. The VLANs
are active in the management domain and in the forwarding state in spanning tree,
ensuring seamless communication without conflicts.

+6285693811614 [email protected]
Configure DHCP Server
Router 1 (DHCP Server Vlan 10,20)

Router 2 (DHCP Server Vlan 40,50)

Router 3 (DHCP Server Vlan 30,40,50)

The IP DHCP pool configuration above is part of the DHCP Server function on a
router, used to automatically assign IP addresses to client devices in the
network. Each pool (VLAN10, VLAN20, VLAN30, VLAN40, VLAN50) defines the
subnet network, default gateway (default-router), and DNS server (dns-
server) for clients within a specific VLAN. This simplifies network management
by eliminating manual IP configuration, ensuring that each client receives the
correct network settings for both local and internet access.

+6285693811614 [email protected]
Configure OSPFv2
Router 1 (Network-Based Configuration)

Router 2 (Host-Specific Configuration)

Router 3 Trunk (Interface-Based Configuration)

The three configurations demonstrate OSPFv2 methods: 1) The first router uses the
network command with a wildcard mask to define subnets and OSPF areas. 2) The
second router uses a host-specific wildcard mask (0.0.0.0) to advertise specific IPs,
ideal for point-to-point links. 3) The third router enables OSPF directly on interfaces
using ip ospf area, automatically advertising the connected subnets. All methods
achieve OSPF functionality with different approaches.

+6285693811614 [email protected]
Verifying OSPFv2
Router 1

Router 2

Router 3

In the OSPF interface brief output, Cost represents the OSPF metric for the
interface, indicating the "expense" of using that interface in the path selection
process, with lower values indicating more preferred routes (typically based on
bandwidth).

State shows the current status of OSPF adjacencies, such as LOOP for loopback
interfaces, DR (Designated Router) for the router selected as the DR in
broadcast or non-broadcast multi-access networks, and P2P (Point-to-Point) for
direct connections between two routers.

Nbrs F/C stands for Neighbors/Full/Count, where the first number shows the
number of OSPF neighbors, Full indicates how many are in the Full state (fully
established adjacencies), and Count displays the total number of neighbors,
including those not fully established. These fields help monitor and troubleshoot
OSPF interface performance and connectivity.

+6285693811614 [email protected]
Table Routing OSPFv2
Router 1

Router 2

Router 3

The routing tables from Router 1, Router 2, and Router 3 show OSPF-learned
routes (O), indicating interconnectivity between the routers in a multi-area
network. Each router lists networks it has learned, the metric (cost) to reach
them, the next-hop IP, the interface used, and the uptime of each route. For
example, Router 1 reaches 192.168.30.0/24 via 10.1.1.6 (Serial1/1) and 10.1.1.2
(Serial1/0), demonstrating redundancy with equal cost multipath. Similarly, each
router has loopback addresses (10.0.0.x/32) and VLAN subnets reachable via
other routers. These tables reflect a fully converged OSPF network with both
point-to-point and broadcast links.

+6285693811614 [email protected]
What Is Loopback?
Router 1

Router 2

Router 3

Loopback0 is a virtual, logical interface on a router that remains in an "up"


state as long as the router is operational, regardless of physical interface status. It
is commonly used in OSPF as a stable and unique Router ID, ensuring consistent
identification even if physical interfaces go down. Additionally, it provides a
reliable endpoint for management tasks like SSH and is useful for testing and
diagnostics. For example, an IP address like 10.0.0.1/32 assigned to Loopback0
ensures continuous reachability of the router as long as it is running.

+6285693811614 [email protected]
Test Ping & Traceroute
Router To Router
Test Ping
Router 1 to Router 2

Traceroute
Router 1 to Router 2

Test Ping
Router 1 to Router 3

Traceroute
Router 1 to Router 3

The results show successful pings and traceroutes from Router 1 (R1) to various
IP addresses in the network. When pinging 10.1.1.9 and 10.1.1.10, the success
rate is 100% with minimal round-trip times (7-10 ms). The traceroute to 10.1.1.9
shows that the path goes through 10.1.1.2 first (10ms), followed by 10.1.1.6
(9ms), and returns to 10.1.1.2 (8ms), confirming the route is stable. Similarly, the
traceroute to 10.1.1.10 passes through 10.1.1.6 (9ms) and 10.1.1.2 (9ms), with a
return to 10.1.1.6 (8ms), confirming the route is properly established and
responsive. These tests indicate good network connectivity with minimal delays.

+6285693811614 [email protected]
Test Ping VPCS to VPCS
Test Ping
VPCS (VLAN 10) to
VPCS (VLAN 20,30,40,50)

The ping results show that the VPCS device successfully reached all target IP
addresses (192.168.20.3, 192.168.30.2, 192.168.40.2, and 192.168.50.3) with a 100%
success rate and varying response times. The ping to 192.168.20.3 had an average
response time of around 1 ms, indicating low latency. The pings to 192.168.30.2 and
192.168.40.2 had slightly higher response times, ranging from 9 ms to 27 ms, while
the ping to 192.168.50.3 showed latencies between 10 ms and 18 ms. This indicates
that all devices in the network are able to communicate successfully, with some
differences in latency between them.

+6285693811614 [email protected]

You might also like