cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
865
Views
0
Helpful
7
Replies

Can someone help with this and make configuration.

JonSnow
Level 1
Level 1

I cannot get this to work can someone help.

  1. Create VLANs 10 and 20 on S1 Layer 3 switch.

  2. Configure inter-VLAN routing on S1 for VLANs 10 and 20.

Use the IP addresses VLAN 10 192.168.10.254/24 VLAN20 192.168.20.254/24 .

3.Configure an EtherChannel between S1 and S2 (Layer 2 switch) using

interfaces GigabitEthernet 0/1 and 0/2 on both switches. Use the PAGP protocol for EtherChannel.

4.Configure a trunk link on the Port-Channel interface and allow only VLANs 1, 10, and 20.

5.Test connectivity by sending ICMP packets between PC1 and PC2.

Link of topolgy: 

2 Accepted Solutions

Accepted Solutions

Joseph W. Doherty
Hall of Fame
Hall of Fame

Found your problem.

JosephWDoherty_0-1724519603194.png

Where does your requirements note assigning SVIs on the L2 switch, S2?

If you are going to do that, which I'm not saying you cannot, or is bad, any restrictions on what those IPs may, or may not be?

Also BTW, what's the source of this lab?  #3 says to use PAgP, but you used .1Q.  (Perfectly acceptable, IMO, especially [!!!] if switches being used don't offer PAgP.)

BTW, if you "correct" your config(s), you may find pings don't immediately operate correctly.

See if you too can resolve your problem with the information, above.

If not:

How did you trouble shoot?  Could you ping between hosts on/within same VLAN?  If you have L2 problems, L3 probably isn't going to work.

Spoiler
The fundamental issue is, your SVIs IPs use the same IPs on both S1 and S2.
Using SVIs on S2 isn't needed, but it can be done, they just cannot be duplicate IPs.
If after correcting the underlying issue, you note it immediately doesn't work, it may take some time for ARP and/or switch MAC tables to timeout after a config change, or you need to manually flush those stale entries.

View solution in original post

Only revision was to S2 SVI IPs.

View solution in original post

7 Replies 7

marce1000
Hall of Fame
Hall of Fame

 

                    - FYI : Community group for Packet Tracer project questions

  M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Joseph W. Doherty
Hall of Fame
Hall of Fame

What specifically were you unable to get to work?

Are you using PT?  If so, might you attachment your current PT file?

Can't ping PC1 and PC2

Joseph W. Doherty
Hall of Fame
Hall of Fame

Found your problem.

JosephWDoherty_0-1724519603194.png

Where does your requirements note assigning SVIs on the L2 switch, S2?

If you are going to do that, which I'm not saying you cannot, or is bad, any restrictions on what those IPs may, or may not be?

Also BTW, what's the source of this lab?  #3 says to use PAgP, but you used .1Q.  (Perfectly acceptable, IMO, especially [!!!] if switches being used don't offer PAgP.)

BTW, if you "correct" your config(s), you may find pings don't immediately operate correctly.

See if you too can resolve your problem with the information, above.

If not:

How did you trouble shoot?  Could you ping between hosts on/within same VLAN?  If you have L2 problems, L3 probably isn't going to work.

Spoiler
The fundamental issue is, your SVIs IPs use the same IPs on both S1 and S2.
Using SVIs on S2 isn't needed, but it can be done, they just cannot be duplicate IPs.
If after correcting the underlying issue, you note it immediately doesn't work, it may take some time for ARP and/or switch MAC tables to timeout after a config change, or you need to manually flush those stale entries.

I will try and correct that. At first i didnt put any IPs on S2 SVI but it didnt work either. Then i tried everything just to make it work but it didn so i attached maybe that file. Can you please attach yours where you made it work. Thx 

Only revision was to S2 SVI IPs.

knuwanga91
Level 1
Level 1

Hi Johnsnow, I will guide you through the configuration setps:

1.Create VLANs 10 and 20 on S1 Layer 3 switch.
> Configuration to create a vlan - since creating a vlan is a global configuration you need to go to the global configuration mode to create this
switch>enable
switch# conf t
switch(config)# vlan (vlan-no)
switch(config-vlan)# name (vlan-name)

Example 
switch(config) # vlan 10
switch(config-vlan)# name vlan10


2.Configure inter-VLAN routing on S1 for VLANs 10 and 20
To configure inter-vlan routing in the layer 3 switch you need to first configure IP routing in the switch globally
s1(config)#ip routing

then create the interface vlans according to the number of vlan that you require to be participating in inter vlan routing and then give it the desired IP address 

s1(conf)#interface vlan (vlan-no)

s1(conf-if)# IP address (IP-address) (subnet-mask)


example 

s1(config)# interface vlan 10

si(config-if)#ip address 192.168.10.254 255.255.255.0

3. Configure an EtherChannel between S1 and S2 (Layer 2 switch) using
to configure etherchannel between s1 and s2 to follow the best practice first shut down one side (in the example I have shut down the s1 side)

Switch(config)# interface (interface-id) ==> this can be done in range as well

switch(config-if)#shutdown

switch(config-int)#switchport mode trunk

switch(config-if)#switchport trunk allowed vlan 1,10,20

switch(config-if)#channel-group (channel-group no) mode desirable <== other side should be mode auto

switch(config-if)#no shutdown

Example

Switch(config)# interface range Gi0/1-2

switch(config-if)#shutdown

switch(config-if)#switchport mode trunk

switch(config-if)#switchport trunk allowed vlan 1,10,20

switch(config-if)#channel-group 1 mode desirable ( switch one should have switch(config-int)#channel-group 1 mode auto)
switch(config-if)#no shutdown

 

To confirm the configuration  do a "show Etherchannel summary command" to verify if you have the letters "SU" in front of the EtherChannel and "P" in individual interfaces