Disclaimer: I understand that is an train in a course, and beneath is a dialogue about, and an answer to, the train. Use the answer solely as a final resort after you’ve got tried for at the very least 2 hours to unravel the train by yourself and nonetheless have not figured it out by yourself. Dishonest by merely getting the reply to an train is not going to get you wherever.
I’ve little so as to add to the opposite solutions, however I’ll attempt to make clear the problems with the query, and suggest another answer:
Points with the query
For the needs of this dialogue, I will probably be referring to the networks as follows:
- Community connected to Switch1 and PC: N0
- Community connected to PC1: N1
- Community connected to Switch3 and PC2: N2
- Community connected to PC3: N3
From the supplied diagram, the networks are every connected to a separate interface of Router0:
| Router0 interface | Community |
|---|---|
| Gig0/0/0 | N0 |
| Gig0/0/1 | N1 |
| Gig0/1/0 | N2 |
| Gig0/1/1 | N3 |
N0 and N1 are every connected to router interfaces correct. “Correct” router interfaces are interfaces that may solely be router interfaces and you can not configure them to behave as swap ports (or at the very least it could be very troublesome and is clearly not what you are attempting to do right here). This implies they should have an IP tackle, and also you can create subinterfaces on them.
N2 and N3, then again, are linked to what appears to be a swap module that’s plugged into Router0. Now, it will depend on the swap module, however typically these swap modules are swap ports correct. “Correct swap ports” are ports that you just can not configure routing on, can not give them an IP tackle, and you can not configure subinterfaces on them. For the needs of my reply, although, I’ll entertain the situation which you could configure these ports as both L2 or L3 ports. Extra on that later.
Within the query assertion, you say that every community should have a “distinctive VLAN”. VLANs solely matter within the switched phase of the community. Which means as soon as site visitors hits a router, you’ll be able to have the identical VLAN on the opposite aspect of the router. Since right here you’ve got 4 switched segments separated by a router you don’t strictly require distinctive VLANs. Nonetheless, necessities are necessities, so we’ll present for that.
We are going to, for the sake of argument, assign the next VLANs to every switched phase:
| Community | VLAN ID |
|---|---|
| N0 | 10 |
| N1 | 11 |
| N2 | 12 |
| N3 | 13 |
Now allow us to think about the configuration of Switch3:
interface Fast0/2
description port to PC2
switchport mode entry
switchport entry vlan 12
interface Fast0/1
description port to Router0 Gig0/1/0
switchport mode entry
switchport entry vlan 12
With the above configuration stanza we configured N2 site visitors to go to Router0 untagged. When you insist on Switch3 to tag site visitors that it sends to Router0, you need to configure a trunk to Router0:
!on Switch3:
interface Fast0/1
description trunk port to Router0 Gig0/1/0
switchport encapsulation dot1q
switchport mode trunk
switchport trunk native vlan 1
This manner, the swap will probably be tagging all VLAN 12 site visitors that it sends to Router0. The identical is true for all 4 switches.
Resolution if router’s swap module has L3 interfaces
First, we should confirm if the router’s swap module’s interfaces will be configured as L2 interfaces:
! on Router0:
interface Gig0/1/0
no switchport
finish
present interface Gig0/1/0 | embrace swap
If there aren’t any errors, it’s best to transfer on with this situation. If the router doesn’t allow you to configure the port as a L3 port, then you definately merely can not clear up this train with the present cabling. Transfer to the part the place I focus on the train’s various answer.
! on Router0:
interface Gig0/1/0
no switchport
interface Gig0/1/0.12
encapsulation dot1Q 12
ip tackle
If Switch3 will not be tagging VLAN12 site visitors, you could inform Router0 that it is going to be receiving untagged VLAN12 site visitors:
! on Router0:
interface Gig0/1/0.12
encapsulation dot1Q 12 native
And repeat on Gig0/1/1.
On the router interfaces:
! on Router0:
interface Gig0/0/0
no ip tackle
interface Gig0/1/0.10
encapsulation dot1Q 10 ! add native if Switch1 will not be trunking
ip tackle
And repeat for Gig0/0/1.
Various answer
- Delete all switches besides Switch1.
- Connect PC to Fa0/10 of Switch1 (N0 – VLAN 10)
- Connect PC1 to Fa0/11 of Switch1 (N1 – VLAN 11)
- Connect PC2 to Fa0/12 of Switch1 (N2 – VLAN 12)
- Connect PC3 to Fa0/13 of Switch1 (N3 – VLAN 13)
- Configure Switch1:
!on Switch1:
interface Fast0/10
description Entry port to PC (VLAN 10)
switchport mode entry
switchport entry vlan 10
interface Fast0/11
description Entry port to PC1 (VLAN 11)
switchport mode entry
switchport entry vlan 11
interface Fast0/12
description Entry port to PC2 (VLAN 12)
switchport mode entry
switchport entry vlan 12
interface Fast0/13
description Entry port to PC3 (VLAN 13)
switchport mode entry
switchport entry vlan 13
interface Fast0/3
description Trunk port to Router0 Gig0/0/0
switchport encapsulation dot1q
switchport mode trunk
switchport trunk native vlan 1
- Configure Router0 with the subinterfaces that the query is asking:
! on Router0:
interface Gig0/0/0.10
encapsulation dot1Q 10
ip tackle
interface Gig0/0/0.11
encapsulation dot1Q 11
ip tackle
interface Gig0/0/0.12
encapsulation dot1Q 12
ip tackle
interface Gig0/0/0.13
encapsulation dot1Q 13
ip tackle
The above is (or at the very least was) known as Router-On-a-Stick.
Observe: The instructions are from reminiscence, I don’t have entry to this topology or gear proper now, so forgive any errors within the instructions and modify the instructions on the CLI as wanted.