Ccna 3 Case Study 1

Author:Navneet Gaur
Date:April 2015
Description:Explanation regarding Eigrp opting for a different route than the feasible successor route
Note 1Index of all my documents
Note 2To view the included images clearly, click on them
Note 3Irrespective of the dates of edit, Cisco Learning Network maintains the history and keeps each edited version in its database for later reference
Note 4

How to stop notifications, that are generated when I edit any one of the pre-existing documents https://learningnetwork.cisco.com/message/406093

 

 

This document analyzes the scenario that has been stipulated under the following discussion by Peter Palúch
https://supportforums.cisco.com/discussion/11877371/eigrp-successor-and-feasible-successor

 

Additionally, there is a discussion that relates to the relevance and influence of MTU in EIGRP

Re: About the infamous EIGRP metric formula and MTU

 

 

 

Index

  • Part 1 - The logic
  • Part 2 - The metric calculation

 

 

 

Part 1

The given topic under discussion considers the state, where EIGRP

  • once the main route fails
  • does not utilize the feasible successor route
  • instead chooses to opt for another route, that did not meet the feasibility condition

 

I am going to explain the thread under consideration, using simple logic.

 

 

First, the conclusion

  • Under standard conditions, routing protocols,
  • use the best metric to choose a path
  • while deciding among multiple competing paths

 

  • The route with the best metric is placed in the routing table
  • The above mentioned discussion also follows that rule

 

 

 

The Topology

*Click on the image to enlarge

 

 

Section 1

 

The topology with metrics for network 100.0.0.0 at router R-1

*Click on the image to enlarge

 

 

 

 

In the above topology, there are three routes that router R-1 can possible use to reach the network 100.0.0.0

  • The first path has a metric of 801,536
  • The second path has a metric of 413,696
  • The third path has a metric of 594,688

 

 

Putting the above in ascending order

  • The second path has a metric of 413,696
  • The third path has a metric of 594,688
  • The first path has a metric of 801,536

 

 

 

Note
  • The metric values could have been manipulated to be simpler. The use of the above metric values is a personal choice dictated by the fact that I am mathematically challenged.
  • Consequently I try to use every opportunity where calculations are required to practice working on mathematical equations, no matter how simple they are.
  • To the mathematically inclined that may seem to be somewhat pointless but for me it is a necessity.
  • That brings me to clarify another point, simpler metric values will also yield similar results.

 

 

Following the normal rule, that the routing protocol, will install the path with the best metric in the routing table, the second path with the lowest metric meets that criterion and is installed by EIGRP in the routing table.

 

  • Routing table at router R-1 where the best route, i.e. Path-2, has been inserted by Eigrp

 

R1#show ip route | i 100.0.0.0

D    100.0.0.0/8 [90/413696] via 2.1.1.3, 00:00:28, Serial0/1

 

 

 

Section 2

 

Modified Topology

*Click on the image to enlarge


 

  • In this modified topology, the route that was considered to be the best path has been completely removed
  • Now there are two routes that router R-1 can possible use to reach the network 100.0.0.0

 

  • The first path has a metric of 801,536
  • The third path has a metric of 594,688

 

Again, putting the above in ascending order

  • The third path has a metric of 594,688
  • The first path has a metric of 801,536

 

Following the normal rule that the routing protocol will install the path with the best metric in the routing table, the third path with the lowest metric meets that criterion and is installed by EIGRP in the routing table.

 

For obvious reasons, we won’t be proceeding to diagram number 3 where only one path is left.

 

 

Section 3

 

The confusion related to the above mentioned article

EIGRP has been programmed to use the concept of backup routes, which are called “Feasible Successors”

 

 

Concept

The concept of feasible successor can be stated in simple terms as follows:

 

  • I, router R-1, have a route to destination 100.0.0.0 with a metric of 413,696
  • I, router R-1, also happen to know about two more possible paths that can be used to reach 100.0.0.0.

 

  • These paths are through routers R-2 and R-4.

 

  • After I have selected the path with the best metric, my consideration for the remaining paths is as follows,

 

  1. If the other router connecting me to that network, 100.0.0.0, has a better metric than I have, I will use it as a backup path.
  2. If the other router connecting me to that network, 100.0.0.0, has a worse metric than I have, I see no reason to use it as a backup path.

 

  • Apart from the loop prevention logic, it is kind of common sense, that I am not going to consider a path through a router that has a worse metric than my own best metric
  • This is also known as feasibility condition
  • The words have been rephrased, but the overall simplified version was first stated by Brian McGahan:

"The EIGRP algorithm is very simple, but uses complicated terminology. The logic is as follows:

My metric to the destination is X.  If your metric is more than X, I'm closer to the destination than you are. If your metric is less than X, you're closer than I am. I can only use you as a backup route if you're closer than I am."

 

 

 

Let us apply the above condition to the given topology after Path-2 has been selected as the best route.

Path 1

*Click on the image to enlarge

 

 

 

 

  • The metric that R-2 has calculated to reach network 100.0.0.0 is 284,416
  • The best path metric at R-1 for network 100.0.0.0 is 413,696

 

  • Following the logic of feasibility condition, R-1 can see that the metric at next hop router R-2, on Path-1, is less than its own best metric to reach network 100.0.0.0
  • Metric at R-2 284,416 is less than R-1s best metric 413,696

 

  • Therefore EIGRP at R-1 considers this path to be usable in case of failure of main path, Path-2.
  • Accordingly it considers it to be a valid candidate for backup path, i.e. feasible successor route.

 

 

EIGRP topology table at R-1

 

R1#show ip eigrp topology | s 100.0.0.0

P 100.0.0.0/8, 1 successors, FD is 413696

        via 2.1.1.3 (413696/25856), Serial0/1

        via 1.1.1.2 (801536/284416), Serial0/0

 

 

Path 3

*Click on the image to enlarge

 

 

 

  • The metric that R-4 has calculated to reach network 100.0.0.0 is 465,408
  • The best path metric at R-1 for network 100.0.0.0 is 413,696

 

  • Following the logic of feasibility condition, R-1 can see that the metric at next hop router R-4, on Path-3, is more than its own best metric to reach network 100.0.0.0
  • Metric at R-4 465,408 is more than R-1s best metric 413,696

 

  • Therefore EIGRP at R-1 considers this path to be un-usable in case of failure of main path, Path-2.
  • Accordingly it considers it to be an invalid candidate for backup path, i.e. feasible successor route, and does not place it in the topology as a feasible successor.

 

 

However, EIGRP does include this route is its topology table and keeps its record.

 

R1#show ip eigrp topology all-links | s 100.0.0.0

P 100.0.0.0/8, 1 successors, FD is 413696, serno 22

        via 2.1.1.3 (413696/25856), Serial0/1

        via 3.1.1.4 (594688/465408), Serial0/2

        via 1.1.1.2 (801536/284416), Serial0/0

 

 

 

Applicability

The concept of retaining backup routes allows EIGRP to converge faster. Under normal and standard conditions, if the main route becomes unavailable, EIGRP is stated to use the backup route without undergoing any further calculations.

 

And here is a finer point that is not usually considered, because, in all fairness, it doesn't usually come up.

The point that is covered in the above-mentioned article.

 

 

The Point

  • What if,
  • there is another route which has a better metric than the current feasible successor
  • but that route failed to be qualified as a ‘backup route’ because the router through which it passes through did not meet the feasibility condition, i.e. did not have a better metric than my best routes metric at that time ?

 

 

The Explanation

Even though EIGRP has selected the other route, Path-1, as a feasible successor route in its topology table

 

Very important – EIGRP still has metrics to all the possible routes as well, in the topology table

  • Therefore when, the main route, Path-2, fails,
  • before promoting the previously determined Feasible Successor route to the routing table,
  • EIGRP will carry out the ‘sanity check’ that this route has the best metric among the remaining routes.

 

  • If it had the best metric, -{logically no recalculation required in the above mentioned scenario }-, it would have been promoted and placed in the routing table as the best route.

 

Summary of the Company and Network Requirements

The XYZ Research Company is a small company that develops high-speed wireless products. The main office occupies two buildings in Sydney. One building is for the Administration Group. The other building is for the Sales and Marketing Group, and the Research and Development Group. The Research Group and the Sales and Marketing Group will each have employees located on all three floors of the main building. The XYZ Research Company also has a Sales Branch Office located in Melbourne. The company is implementing a wired network that should support 100% growth over the next five to ten years. A logical diagram has been provided.

Our task is to design, implement, and fully document the XYZ Research Company network. In addition to a formal report, we are asked to prepare a prototype of the network built, before it is fully implemented, in order to verify that it will meet the company’s needs.

XYZ Research Company Requirements

  • 18 employees in the Research and Development Group
  • 9 employees in the Sales and Marketing Group
  • 7 employees in the Administration Group
  • 5 employees in the Remote Sales office
  • Lifetime maximum of 5 servers on separate subnet, regardless of company growth.
  • Use subnet 200.200.100.0/30 for connection to Internet router.
  • Use public class C network 223.0.0.0 for internal addressing.
  • Use VLSM for IP addressing.
  • Expect 100% growth of current IP requirements and when determining the size of subnets.
  • All network devices must have IP addresses assigned.

Fase 1: La topologia

Topologia

Fase 2: Indirizzamento

Riepilogo indirizzamento

Indirizzamento edificio Principale - Sydney

Indirizzamento edificio Secondario - Sydney

Indirizzamento edificio Melbourne

Indirizzamento edificio Admin - Sydney

Indirizzamento Switch Amministrazione - Sydney

Indirizzamento Switch1 edificio Principale - Sydney

Indirizzamento Switch2 edificio Principale - Sydney

Indirizzamento Switch3 edificio Principale - Sydney

Indirizzamento Switch Melbourne

Indirizzamento degli Host e Server - Sydney

Indirizzamento degli Host - Sydney

Fase 3: Routing

Protocolli di routing a confronto

Dettagli routing OSPF

Fase 4: Gestione degli Switch

Detttaglio degli Switch

Fase 5: Previsione dei costi

Materiale per 1° Piano edificio Principale - Sydney

Materiale per 2° Piano edificio Principale - Sydney

Materiale per 3° Piano edificio Principale - Sydney

Materiale per reparto Sales - Sydney

Materiale per reparto Amministrazione - Sydney

Fase 6: Configurazione Router Sydney_Border

enable conf t hostname Sydney_Border banner motd # Sydney_Border - Accesso limitato # line console 0 password cisco login exit line vty 0 4 password cisco login exit enable secret class ip subnet-zero int s0 ip address 223.0.0.1 255.255.255.252 description Interfaccia Serial0/0 DCE - Connessione verso Sydney_Main clock rate 2000000 no shutdown exit int s1 ip address 200.200.200.2 255.255.255.252 description Interfaccia Serial0/1 DTE - Connessione verso ISP no shutdown exit int fa0 ip address 223.0.0.9 255.255.255.252 description Interfaccia FastEthernet0/0 - Connessione verso Sydney_Admin no shutdown exit int lo0 ip address 127.0.0.254 255.255.255.255 description Interfaccia Loopback0/0 - Interfaccia statica per id OSPF no shutdown exit ip route 0.0.0.0 0.0.0.0 200.200.200.1 router ospf 50 network 127.0.0.0 0.0.0.255 area 0 network 223.0.0.0 0.0.0.3 area 0 network 223.0.0.8 0.0.0.3 area 0 default-information originate exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 7: Configurazione Router Sydney_Admin

enable conf t hostname Sydney_Admin banner motd # Sydney_Admin - Accesso limitato # line console 0 password cisco login exit line vty 0 4 password cisco login exit enable secret class ip subnet-zero int fa0 ip address 223.0.0.10 255.255.255.252 description Interfaccia FastEthernet0/0 - Connessione verso Sydney_Border no shutdown exit int fa0/1.1 encapsulation dot1q 1 ip address 223.0.0.17 255.255.255.252 description Interfaccia FastEthernet0/1.1 - Gateway per VLAN1 Admin no shutdown exit int fa0/1.2 encapsulation dot1q 2 ip address 223.0.0.77 255.255.255.240 description Interfaccia FastEthernet0/1.2 - Gateway per Admin no shutdown exit int lo0 ip address 127.0.0.253 255.255.255.255 description Interfaccia Loopback0/0 - Interfaccia statica per id OSPF no shutdown exit router ospf 50 network 127.0.0.0 0.0.0.255 area 0 network 223.0.0.16 0.0.0.3 area 0 network 223.0.0.8 0.0.0.3 area 0 network 223.0.0.76 0.0.0.15 area 0 exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 8: Configurazione Router Sydney_Main

enable conf t hostname Sydney_Main banner motd # Sydney_Main - Accesso limitato # line console 0 password cisco login exit line vty 0 4 password cisco login exit enable secret class ip subnet-zero int s0 ip address 223.0.0.5 255.255.255.252 description Interfaccia Serial0/0 DCE - Connessione verso Melboure_Sales clock rate 2000000 no shutdown exit int s1 ip address 223.0.0.2 255.255.255.252 description Interfaccia Serial0/1 DTE - Connessione verso Sydney_Border no shutdown exit int fa0/0.1 encapsulation dot1q 1 ip address 223.0.0.21 255.255.255.248 description Interfaccia FastEthernet0/0.1 - Gateway per VLAN1 Main no shutdown exit int fa0/0.2 encapsulation dot1q 2 ip address 223.0.0.125 255.255.255.192 description Interfaccia FastEthernet0/0.2 - Gateway per R&D no shutdown exit int fa0/0.3 encapsulation dot1q 3 ip address 223.0.0.93 255.255.255.224 description Interfaccia FastEthernet0/0.3 - Gateway per S&M no shutdown exit int fa0/0.4 encapsulation dot1q 4 ip address 223.0.0.29 255.255.255.224 description Interfaccia FastEthernet0/0.4 - Gateway per Server no shutdown exit int lo0 ip address 127.0.0.252 255.255.255.255 description Interfaccia Loopback0/0 - Interfaccia statica per id OSPF no shutdown exit router ospf 50 network 127.0.0.0 0.0.0.255 area 0 network 223.0.0.4 0.0.0.3 area 0 network 223.0.0.0 0.0.0.3 area 0 network 223.0.0.20 0.0.0.7 area 0 network 223.0.0.124 0.0.0.63 area 0 network 223.0.0.92 0.0.0.31 area 0 network 223.0.0.26 0.0.0.31 area 0 exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 9: Configurazione Router Melbourne_Sales

enable conf t hostname Melbourne_Sales banner motd # Melbourne_Sales - Accesso limitato # line console 0 password cisco login exit line vty 0 4 password cisco login exit enable secret class ip subnet-zero int s0 ip address 223.0.0.6 255.255.255.252 description Interfaccia Serial0/0 DTE - Connessione verso Sydney_Main no shutdown exit int fa0/0.1 encapsulation dot1q 1 ip address 223.0.0.13 255.255.255.252 description Interfaccia FastEthernet0/0.1 - Gateway per VLAN1 Sales no shutdown exit int fa0/0.2 encapsulation dot1q 2 ip address 223.0.0.61 255.255.255.240 description Interfaccia FastEthernet0/1.2 - Gateway per Sales no shutdown exit int lo0 ip address 127.0.0.251 255.255.255.255 description Interfaccia Loopback0/0 - Interfaccia statica per id OSPF no shutdown exit router ospf 50 network 127.0.0.0 0.0.0.255 area 0 network 223.0.0.4 0.0.0.3 area 0 network 223.0.0.12 0.0.0.3 area 0 network 223.0.0.60 0.0.0.15 area 0 exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 10: Configurazione Switch Sw_Admin

enable conf t hostname Sw_Admin line console 0 password cisco login exit line vty 0 23 password cisco login exit ip subnet-zero int fa0/1 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/2 speed 100 duplex full switchport mode access switchport access vlan 2 exit int fa0/3 speed 100 duplex full switchport mode access exit int fa0/4 speed 100 duplex full switchport mode access exit int fa0/5 speed 100 duplex full switchport mode access exit int fa0/6 speed 100 duplex full switchport mode access exit int fa0/7 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdow exit int fa0/8 speed 10 duplex full swit chport mode access switchport access vlan 2 no shutdown exit int fa0/9 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/10 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/11 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/12 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/13 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/14 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/15 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/16 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/17 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/18 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/19 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/20 speed 10 duplex full switchport mode access switchport access vlan 2 exit int fa0/21 speed 10 duplex full switchport mode access exit int fa0/22 speed 10 duplex full switchport mode access exit int fa0/23 speed 10 duplex full switchport mode access exit int fa0/24 speed 10 duplex full switchport mode access exit interface Vlan1 ip address 223.0.0.18 255.255.255.252 exit ip default-gateway 223.0.0.17 exit vlan database vtp v2-mode vtp domain Admin vtp transparent exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 11: Configurazione Switch Sw_Main1

enable conf t hostname Sw_Main1 line console 0 password cisco login exit line vty 0 23 password cisco login exit ip subnet-zero int fa0/1 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/2 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/3 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/4 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/5 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/6 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/7 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/8 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/9 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/10 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/11 speed 100 duplex full switchport mode access switchport access vlan 4 no shutdown exit int fa0/12 speed 100 duplex full switchport mode access switchport access vlan 4 no shutdown exit int fa0/13 speed 100 duplex full switchport mode access switchport access vlan 4 no shutdown exit int fa0/14 speed 100 duplex full switchport mode access switchport access vlan 4 no shutdown exit int fa0/15 speed 100 duplex full switchport mode access switchport access vlan 4 no shutdown exit int fa0/16 speed 100 duplex full switchport mode access exit int fa0/17 speed 100 duplex full switchport mode access exit int fa0/18 speed 100 duplex full switchport mode access exit int fa0/19 speed 100 duplex full switchport mode access exit int fa0/20 speed 100 duplex full switchport mode access exit int fa0/21 speed 100 duplex full switchport mode access exit int fa0/22 speed 100 duplex full switchport mode access exit int fa0/23 speed 100 duplex full switchport mode access exit int fa0/24 speed 100 duplex full switchport mode access exit interface Vlan1 ip address 223.0.0.22 255.255.255.248 exit ip default-gateway 223.0.0.21 exit vlan database vtp v2-mode vtp domain Main vtp server exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 12: Configurazione Switch Sw_Main2

enable conf t hostname Sw_Main2 line console 0 password cisco login exit line vty 0 23 password cisco login exit ip subnet-zero int fa0/1 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/2 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/3 speed 100 duplex full exit int fa0/4 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/5 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/6 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/7 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/8 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/9 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/10 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/11 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/12 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/13 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/14 speed 100 duplex full switchport mode access exit int fa0/15 speed 100 duplex full switchport mode access exit int fa0/16 speed 100 duplex full switchport mode access exit int fa0/17 speed 100 duplex full switchport mode access exit int fa0/18 speed 100 duplex full switchport mode access exit int fa0/19 speed 100 duplex full switchport mode access exit int fa0/20 speed 100 duplex full switchport mode access exit int fa0/21 speed 100 duplex full switchport mode access exit int fa0/22 speed 100 duplex full switchport mode access exit int fa0/23 speed 100 duplex full switchport mode access exit int fa0/24 speed 100 duplex full switchport mode access exit interface Vlan1 ip address 223.0.0.23 255.255.255.248 exit ip default-gateway 223.0.0.21 exit vlan database vtp v2-mode vtp domain Main vtp client exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 13: Configurazione Switch Sw_Main3

enable conf t hostname Sw_Main3 line console 0 password cisco login exit line vty 0 23 password cisco login exit ip subnet-zero int fa0/1 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/2 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/3 speed 100 duplex full switchport mode access exit int fa0/4 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/5 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/6 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/7 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/8 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/9 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/10 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/11 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/12 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/13 speed 10 duplex full switchport mode access switchport access vlan 3 no shutdown exit int fa0/14 speed 100 duplex full switchport mode access exit int fa0/15 speed 100 duplex full switchport mode access exit int fa0/16 speed 100 duplex full switchport mode access exit int fa0/17 speed 100 duplex full switchport mode access exit int fa0/18 speed 100 duplex full switchport mode access exit int fa0/19 speed 100 duplex full switchport mode access exit int fa0/20 speed 100 duplex full switchport mode access exit int fa0/21 speed 100 duplex full switchport mode access exit int fa0/22 speed 100 duplex full switchport mode access exit int fa0/23 speed 100 duplex full switchport mode access exit int fa0/24 speed 100 duplex full switchport mode access exit interface Vlan1 ip address 223.0.0.24 255.255.255.248 exit ip default-gateway 223.0.0.21 exit vlan database vtp v2-mode vtp domain Main vtp client exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

Fase 14: Configurazione Switch Sw_Sales

enable conf t hostname Sw_Sales line console 0 password cisco login exit line vty 0 11 password cisco login exit ip subnet-zero int fa0/1 speed 100 duplex full switchport mode trunk no shutdown exit int fa0/2 speed 100 duplex full switchport mode access exit int fa0/3 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/4 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/5 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/6 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/7 speed 10 duplex full switchport mode access switchport access vlan 2 no shutdown exit int fa0/8 speed 100 duplex full switchport mode access no shutdown exit int fa0/9 speed 100 switchport mode access duplex full exit int fa0/10 speed 100 duplex full switchport mode access no shutdown exit int fa0/11 speed 100 duplex full switchport mode access no shutdown exit int fa0/12 speed 100 duplex full switchport mode access exit interface Vlan1 ip address 223.0.0.14 255.255.255.252 exit ip default-gateway 223.0.0.13 exit vlan database vtp v2-mode vtp domain Sales vtp transparent exit ip host Sydney_Border 223.0.0.1 ip host Sydney_Admin 223.0.0.10 ip host Sydney_Main 223.0.0.5 ip host Melbourne_Sales 223.0.0.6 ip host Sw_Admin 223.0.0.18 ip host Sw_Main1 223.0.0.22 ip host Sw_Main2 223.0.0.23 ip host Sw_Main3 223.0.0.24 ip host Sw_Sales 223.0.0.14 ip host www 223.0.0.33

0 thoughts on “Ccna 3 Case Study 1

Leave a Reply

Your email address will not be published. Required fields are marked *