05-17-2013 03:38 AM - edited 03-07-2019 01:24 PM
Hi
i'm usig GNS3 and i have to deal with this situation:
R5 has NM-1FE-TX modul (connected to R4).
R5 has also NM-16ESW modul (connected to R1,R2 and R3).
here are the config :
R4 :
!
interface FastEthernet0/0
ip address 190.1.1.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet2/0
ip address 190.1.2.1 255.255.255.0
duplex auto
speed auto
!
no ip http server
no ip http secure-server
!
ip classless
ip route 191.1.1.0 255.255.255.0 190.1.1.2
ip route 191.1.1.0 255.255.255.0 190.1.2.2
!
!
R5:
ip dhcp excluded-address 191.1.1.1 191.1.1.10
!
ip dhcp pool URNE
network 191.1.1.0 255.255.255.0
default-router 191.1.1.1
!
!
interface FastEthernet0/0
ip address 190.1.1.2 255.255.255.0
duplex auto
speed auto
!
!
interface FastEthernet2/0
ip address 190.1.2.2 255.255.255.0
duplex auto
speed auto
!
!
interface FastEthernet1/11
switchport access vlan 10
!
interface FastEthernet1/12
switchport access vlan 10
!
interface FastEthernet1/13
switchport access vlan 10
!
!
interface Vlan10
ip address 191.1.1.1 255.255.255.0
!
R1 :
!
interface FastEthernet0/0
ip address dhcp
duplex auto
speed auto
!
R2 :
!
interface FastEthernet0/0
ip address dhcp
duplex auto
speed auto
!
R3 :
!
interface FastEthernet0/0
ip address dhcp
duplex auto
speed auto
!
R1#ping 190.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/30/52 ms
R1#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/42/68 ms
R2#ping 190.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/39/68 ms
R2#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/39/60 ms
R3#ping 190.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/38/72 ms
R3#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/32/72 ms
EVREY THING IS FINE :
now i will shutdown interface f0/0 of R5:
R5(config)#interface f0/0
R5(config-if)#sh
R5(config-if)#end
R5#
*Mar 1 00:24:58.887: %SYS-5-CONFIG_I: Configured from console by console
*Mar 1 00:24:59.799: %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down
R5#
*Mar 1 00:25:00.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
And i ping from routers R1, R2 and R3 190.1.2.1 (other link :(f2/0-----f2/0)).
R1#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/32/64 ms
R2#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R3#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/53/84 ms
why R2 can't ping and others can ?
05-17-2013 04:04 AM
Hi Abdelilah,
please try to check interface status of R5 and R2 with command sh ip interface brief
Also try to configure interface to fixed speed and duplex on both end.
R2 :
!
interface FastEthernet0/0
ip address dhcp
duplex full
speed 100
R5:
interface FastEthernet1/12
switchport access vlan 10
duplex full
speed 100
I had sometimes simmilar problems if duplex and speed is auto.
Regards,
Jan
05-17-2013 04:11 AM
Can you check the trace route result and also the physical port status from R2?.Could be some L1 issue too?
05-17-2013 04:14 AM
R5#sh ip int br
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 190.1.1.2 YES manual administratively down down (entering shutdown on f0/0)
FastEthernet1/0 unassigned YES unset up down
FastEthernet1/1 unassigned YES unset up down
FastEthernet1/2 unassigned YES unset up down
FastEthernet1/3 unassigned YES unset up down
FastEthernet1/4 unassigned YES unset up down
FastEthernet1/5 unassigned YES unset up down
FastEthernet1/6 unassigned YES unset up down
FastEthernet1/7 unassigned YES unset up down
FastEthernet1/8 unassigned YES unset up down
FastEthernet1/9 unassigned YES unset up down
FastEthernet1/10 unassigned YES unset up down
FastEthernet1/11 unassigned YES unset up up
FastEthernet1/12 unassigned YES unset up up
FastEthernet1/13 unassigned YES unset up up
FastEthernet1/14 unassigned YES unset up down
FastEthernet1/15 unassigned YES unset up down
FastEthernet2/0 190.1.2.2 YES manual up up
Vlan1 unassigned YES unset up down
Vlan10 191.1.1.1 YES manual up up
R2#sh ip int br
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 191.1.1.11 YES DHCP up up
i changed the duplex and speed auto by duplex full and speed 100
but the problem persists
05-17-2013 04:17 AM
R2#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R3#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/52/96 ms
R1#ping 190.1.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 190.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/31/60 ms
05-17-2013 04:30 AM
Can you paste traceroute output..?
05-17-2013 04:33 AM
R1#traceroute 190.1.2.1
Type escape sequence to abort.
Tracing the route to 190.1.2.1
1 191.1.1.1 32 msec 40 msec 28 msec
2 190.1.2.1 44 msec * 56 msec
R3#traceroute 190.1.2.1
Type escape sequence to abort.
Tracing the route to 190.1.2.1
1 191.1.1.1 24 msec 48 msec 8 msec
2 190.1.2.1 32 msec * 36 msec
R2#traceroute 190.1.2.1
Type escape sequence to abort.
Tracing the route to 190.1.2.1
1 191.1.1.1 36 msec 52 msec 8 msec
2 * * *
3 * * *
4 * * *
5 * * *
6 etc...
05-17-2013 04:34 AM
191.1.1.1 is the adress of interface VLAN 10 of R5 (dhcp server)
05-17-2013 04:37 AM
R1#sh ip route
Gateway of last resort is 191.1.1.1 to network 0.0.0.0
191.1.0.0/24 is subnetted, 1 subnets
C 191.1.1.0 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 [254/0] via 191.1.1.1
R2#sh ip route
Gateway of last resort is 191.1.1.1 to network 0.0.0.0
191.1.0.0/24 is subnetted, 1 subnets
C 191.1.1.0 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 [254/0] via 191.1.1.1
R3#sh ip route
Gateway of last resort is 191.1.1.1 to network 0.0.0.0
191.1.0.0/24 is subnetted, 1 subnets
C 191.1.1.0 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 [254/0] via 191.1.1.1
05-17-2013 04:46 AM
Hi,
take a look at the duplicate post you made in WAN or LAN section, I answered why it was surely behaving this way.
Regards
Alain
Don't forget to rate helpful posts.
05-17-2013 04:55 AM
It gets dropped at the L3 Vlan interface at R5 itself.Please attach the full configuration of R2 and R4?
05-17-2013 04:57 AM
that is the solution thanks to Alain
i must add this on router R4:
ip sla monitor 1
type echo protocol ipIcmpEcho 190.1.1.2 source-interface FastEthernet0/0
frequency 5
ip sla monitor schedule 1 life forever start-time now
!
!
!
track 1 rtr 1 reachability
!
ip route 191.1.1.0 255.255.255.0 190.1.1.2 track 1
ip route191.1.1.0 255.255.255.0 190.1.2.2 254
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