10-18-2018 08:32 AM - edited 03-05-2019 10:59 AM
Hi all,
I'm currently studying for my CCNA and have set up a home lab up till now been using packet tracer. On the sim I have no problem as all setting up a ROAS. Translate it to real life and I can't get it to work. I have a real basic running-config on both switch and router. Nothing can ping anything.
I've followed CBTnuggets videos and checked my configs against the ones in the lab to no avail. On a debug the only thing I saw out the ordinary was the trunk port going down and then back up every time the PC was trying to ping.
I've attached both running configs, any help would be much appreciated.
PS: I did disable the windows firewall as well, just in case
Solved! Go to Solution.
10-23-2018 03:33 AM - edited 10-23-2018 03:34 AM
Hi Paul,
Thanks for your reply. Apologies I took so long to respond. My configuration was correct, I had another router arrive today and I plugged in the exact same config and worked straight away.
It would appear I just had a faulty router is all.
10-18-2018 11:26 AM - edited 10-18-2018 11:28 AM
Hello
Can you explain what ROAS is?
I am assuming the trunk is connected to the router and fa0/2 is connected to you client?
If so your config of the router and switch is okay, it shouldn't negate access, does the client have the correct ip addressing?
10-19-2018 03:51 AM
10-19-2018 04:35 AM - edited 10-19-2018 04:38 AM
Hello
This then should work as it its, no need to change anything, Have you changed the cabling?
sh ip arp
10-19-2018 05:03 AM - edited 10-19-2018 05:05 AM
Hi Paul
Yeah, tried new cables, I've replaced them all with ones I know to work.
This is the output for sh ip arp on the switch
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.1.50 1 c860.00a2.f262 ARPA Vlan50 <---- initial pc
Internet 10.1.1.100 - 000d.296a.e580 ARPA Vlan50 <---- Vlan ip for telnet
Internet 10.1.1.200 3 c860.00a2.f262 ARPA Vlan50 <---- PC I'm using to telnet with
both PC's can ping the IP address for the VLAN, cant get to the router.
and the router
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.50.1 - 000b.5faa.51c0 ARPA FastEthernet0/0.50
Another odd thing I wasn't expecting, I set up telnet on the switch so I could run both terminal windows. I initially had it in vlan 1 issued the no sh command and it shutdown vlan 50. I have turned it back on now.
king regards,
Ross
10-19-2018 07:36 AM
As originally configured vlan 50 from the switch would be operating with tagged frames and the router should have correctly processed those tagged frames. If you change one device to treat vlan 50 as the native vlan then both devices must be changed that way. And I do not believe that tagging or not tagging is the issue. So I suggest leaving it the way that it was originally configured.
The output of show arp is helpful
Internet 10.1.1.50 1 c860.00a2.f262 ARPA Vlan50 <---- initial pc
Internet 10.1.1.100 - 000d.296a.e580 ARPA Vlan50 <---- Vlan ip for telnet
Internet 10.1.1.200 3 c860.00a2.f262 ARPA Vlan50 <---- PC I'm using to telnet with
Internet 10.1.50.1 - 000b.5faa.51c0 ARPA FastEthernet0/0.50
notice the mismatch between the router address and the switch/PC addresses. If they are both in the same vlan then they should both be in the same subnet.
If you turn on debug arp on the router I suspect that you will see arp requests coming from the PC and an error message on the router about wrong cable. Change the router IP to be in 10.1.1 or change multiple 10.1.1 addresses to be in 10.1.50.
HTH
Rick
10-19-2018 07:42 AM
Ross
In response to your statement " I initially had it in vlan 1 issued the no sh command and it shutdown vlan 50. I have turned it back on now." Many layer 2 switches are restricted to having only a single active vlan interface. If interface vlan 50 was active and you brought up interface vlan 1 then 50 does get shut down. Be aware that we are talking about operation of the layer 3 vlan interface. It did not shut down the layer 2 vlan 50. vlan 50 continued to operate just fine forwarding layer 2 Ethernet frames. What was impacted was how the switch would process IP packets to or from the switch.
HTH
Rick
10-19-2018 08:19 AM - edited 10-19-2018 08:20 AM
Hi Rick,
I can't believe I missed that! I have changed the subint ip address to 10.1.1.1/24 (same subnet across the board) trying to ping 10.1.1.50 from 10.1.1.1 with debug arp gives me;
*Mar 1 00:12:04.995: IP ARP: creating incomplete entry for IP address: 10.1.1.50 interface FastEthernet0/0.50
*Mar 1 00:12:04.995: IP ARP: sent req src 10.1.1.1 000b.5faa.51c0,
dst 10.1.1.50 0000.0000.0000 FastEthernet0/0.50.
*Mar 1 00:12:06.995: IP ARP: sent req src 10.1.1.1 000b.5faa.51c0,
dst 10.1.1.50 0000.0000.0000 FastEthernet0/0.50.
*Mar 1 00:12:08.995: IP ARP: sent req src 10.1.1.1 000b.5faa.51c0,
dst 10.1.1.50 0000.0000.0000 FastEthernet0/0.50.
*Mar 1 00:12:10.995: IP ARP: sent req src 10.1.1.1 000b.5faa.51c0,
dst 10.1.1.50 0000.0000.0000 FastEthernet0/0.50.
*Mar 1 00:12:12.995: IP ARP: sent req src 10.1.1.1 000b.5faa.51c0,
dst 10.1.1.50 0000.0000.0000 FastEthernet0/0.50.
Success rate is 0 percent (0/5)
Followed by a lot of;
*Mar 1 00:13:01.431: IP ARP rep filtered src 10.1.50.1 000b.5faa.51c0, dst 10.1.50.1 ffff.ffff.ffff it's our address
I've not seen these messages in any sims I've run.
Kind regards,
Ross
PS: Many thanks for your second message about the up/down state at L2 and 3. Helps a lot!
10-20-2018 03:18 AM - edited 10-20-2018 09:37 AM
Hello
Just to confirm this is what you have and it still doesn't work?
RTR
interface FastEthernet0/0
no shut
interface FastEthernet0/0.50
encapsulation dot1Q 50
ip address 10.1.1.1 255.255.255.0
ip routing
SW
interface FastEthernet0/1
description link to RTR
switchport mode trunk
interface FastEthernet0/2
description link to end host
switchport access vlan 50
switchport mode access
spanning-tree portfast
no ip routing
end host
ip 10.1.1.50
s/m 255.255.255.0
d/g 10.1.1.1
if this is still isn’t working suggest write erase the switch- delete it’s vlan.date file from flash: - reload and reconfigure then test again
10-23-2018 03:33 AM - edited 10-23-2018 03:34 AM
Hi Paul,
Thanks for your reply. Apologies I took so long to respond. My configuration was correct, I had another router arrive today and I plugged in the exact same config and worked straight away.
It would appear I just had a faulty router is all.
10-24-2018 06:07 AM
Ross
Thanks for the update. Glad to know that you have solved the problem and that it turned out to be faulty equipment. When faced with a problem we frequently tend to start looking for more complex causes, such as configuration mistakes. We do occasionally need to be reminded that sometimes out issues are more simple such as faulty hardware. Thanks for reminding us of this lesson.
HTH
Rick
10-18-2018 01:44 PM
As mentioned by Paul, the router on a stick configuration seems okay.
Maybe, for good measure, you can try hard code the encapsulation to dot1q on the switch Fa0/1 interface. I presume its the default though
interface FastEthernet0/1
switchport mode trunk
switchport trunk encapsulation dot1q
You can also paste the output of the following commands on the switch:
show vlan
show interfaces trunk
10-19-2018 03:53 AM
10-19-2018 04:28 AM
I could be wrong, but I always define the native VLAN on the router's connection to the switch. Not exactly sure if it will do it by default. Two choices to try, make VLAN 50 the native VLAN on both:
!
R1
interface FastEthernet0/0.50
encapsulation dot1Q 50 native
!
!
SW1
!
interface FastEthernet0/1
switchport trunk native vlan 50
!
!
Or add a native VLAN1 interface to R1:
!
interface FastEthernet0/0.1
encapsulation dot1Q 1 native
!
10-19-2018 08:45 AM
Hello,
I have made some changes to your config, implement those and check if it makes a difference. Set your PC to DHCP, it should get an IP address from the router.
You are running a very old software on a very old switch, I am not sure about the defaults, but on the 2950, make sure that ip routing is disabled. Also, you might need to manually create Vlan 50 on SW1:
SW1#conf t
SW1(config)#no ip routing
SW1(config)#exit
SW1#vlan database
SW1(vlan)#vlan 50
SW1(vlan)#exit
Current configuration : 870 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
no network-clock-participate slot 1
no network-clock-participate wic 0
no aaa new-model
ip subnet-zero
ip cef
!
ip dhcp excluded-address 10.1.50.1
!
ip dhcp pool LAN
network 10.1.50.0 255.255.255.0
default-router 10.1.50.1
!
ip audit po max-events 100
!
interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/0.50
encapsulation dot1Q 50
ip address 10.1.50.1 255.255.255.0
no snmp trap link-status
!
interface Serial0/0
no ip address
shutdown
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1
no ip address
shutdown
!
no ip http server
no ip http secure-server
ip classless
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
!
end
Current configuration : 1358 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname SW1
!
ip subnet-zero
!
no ip domain-lookup
--> no ip routing
!
ip ssh time-out 120
ip ssh authentication-retries 3
!
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
!
interface FastEthernet0/1
switchport mode trunk
!
interface FastEthernet0/2
switchport access vlan 50
switchport mode access
spanning-tree portfast
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
--> no interface Vlan1
no ip address
no ip route-cache
!
--> no interface Vlan50
description TEST1
no ip address
no ip route-cache
!
ip http server
!
line con 0
logging synchronous
line vty 0 4
login
line vty 5 15
login
!
end
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide