annuler
Affichage des résultats de 
Rechercher plutôt 
Vouliez-vous dire : 
cancel
2338
Visites
0
Compliment
3
Réponses

can't ping interface router

soso1061
Level 1
Level 1

Bonjour,

Je ne comprends pas pourquoi je ne peux pas pinguer l'interface du routeur 1 (192.168.0.1) à partir de clt2 (192.168.100.1).

cf photo ci-dessus

Lab Enterprise - GNS3.png

Je peux pinguer de clt2 l'interface du commutateur S1 192.168.0.2 mais je ne peux pas pinguer l'interface du routeur R1 192.168.0.1.

Pouvez-vous m'aider?

 

S1 show run

 


!
! Last configuration change at 14:10:05 UTC Mon May 4 2020
!
version 15.1
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service compress-config
!
hostname S1
!
boot-start-marker
boot-end-marker
!
!
logging discriminator EXCESS severity drops 6 msg-body drops EXCESSCOLL
logging buffered 50000
logging console discriminator EXCESS
!
no aaa new-model
no ipv6 cef
ipv6 multicast rpf use-bgp
no ip icmp rate-limit unreachable
!
no ip domain-lookup
ip cef
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
!
vlan internal allocation policy ascending
!
ip tcp synwait-time 5
!
!
!
!
!
!
!
!
!
interface Ethernet0/0
switchport access vlan 90
switchport trunk encapsulation dot1q
switchport mode access
duplex auto
!
interface Ethernet0/1
switchport trunk encapsulation dot1q
switchport mode trunk
duplex auto
!
interface Ethernet0/2
duplex auto
!
interface Ethernet0/3
duplex auto
!
interface Ethernet1/0
duplex auto
!
interface Ethernet1/1
duplex auto
!
interface Ethernet1/2
duplex auto
!
interface Ethernet1/3
duplex auto
!
interface Ethernet2/0
duplex auto
!
interface Ethernet2/1
duplex auto
!
interface Ethernet2/2
duplex auto
!
interface Ethernet2/3
duplex auto
!
interface Ethernet3/0
duplex auto
!
interface Ethernet3/1
duplex auto
!
interface Ethernet3/2
duplex auto
!
interface Ethernet3/3
duplex auto
!
interface Vlan1
no ip address
shutdown
!
interface Vlan10
ip address 192.168.100.254 255.255.255.0
!
interface Vlan20
ip address 192.168.101.254 255.255.255.0
!
interface Vlan90
ip address 192.168.0.2 255.255.255.252
!
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
!
!
no ip http server
!
!

 

 

R1 show run

 


!
! Last configuration change at 20:57:33 UTC Sun May 3 2020
!
version 15.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
aqm-register-fnf
!
!
no aaa new-model
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
no ip icmp rate-limit unreachable
!
!
!
!
!
!


!
!
!
!
no ip domain lookup
ip cef
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
!
!
redundancy
!
!
ip tcp synwait-time 5
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 1.1.1.1 255.255.255.0
!
interface Ethernet0/0
ip address 192.168.0.13 255.255.255.252
!
interface Ethernet0/1
ip address 192.168.0.1 255.255.255.252
!
interface Ethernet0/2
no ip address
shutdown
!
interface Ethernet0/3
no ip address
shutdown
!
interface Ethernet1/0
no ip address
shutdown
!
interface Ethernet1/1
no ip address
shutdown
!
interface Ethernet1/2
no ip address
shutdown
!
interface Ethernet1/3
no ip address
shutdown
!
interface Serial2/0
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/1
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/3
no ip address
shutdown
serial restart-delay 0
!
interface Serial3/0
no ip address
shutdown
serial restart-delay 0
!
interface Serial3/1
no ip address
shutdown
serial restart-delay 0
!
interface Serial3/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial3/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
line aux 0
exec-timeout 0 0
privilege level 15
logging synchronous
line vty 0 4
login
transport input none
!
!
end


!
!
!
control-plane
!
!
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
line aux 0
exec-timeout 0 0
privilege level 15
logging synchronous
line vty 0 4
login
!
end

 

 

Message d'origine en anglais :

Hello,

I don't understand why i can't ping the router 1  interface (192.168.0.1)  from clt2 (192.168.100.1).
cf picture above

I can ping from clt2 the switch  S1 interface 192.168.0.2 but I can't ping router R1 interface 192.168.0.1.
Please can you help ?

 

1 SOLUTION APPROUVÉE

Solutions approuvées

Hi @soso1061 

 

Je suis content que ça t'ait servi.
N'oubliez pas de marquer les bonnes réponses comme résolues, car cela a aidé d'autres utilisateurs ayant des doutes similaires.

Cordialement

 

I am happy that is was useful for you.
Remember to mark the correct answers as solved, because that helped other users with similar questions.

 

Cheers

Voir la solution dans l'envoi d'origine

3 RÉPONSES 3

luis_cordova
VIP Alumni
VIP Alumni

Salut @soso1061 

 

Vérifiez d'abord si vous avez activé le routage sur le commutateur multicouche(S1).
Si shecho ne l'a pas fait, cela est accompli avec la commande ip routing.

Il y a aussi le détail du lien entre S1 et R1.
Dans S1, vous avez indiqué que l'interface appartient au vlan 90, donc les paquets qui seront acceptés seront ceux qui arrivent au commutateur avec le tag 90.

Pour résoudre ce problème, vous pouvez dire au routeur de baliser les paquets avec la balise 90 à l'aide d'une sous-interface:

R1

interface Ethernet0/1

no ip address

interface Ethernet0/1.90

encapsulation dot1q 90

ip address 192.168.0.1 255.255.255.252

 

 

First check if you have enabled routing on the multilayer switch (S1).
If shecho has not, this is accomplished with the ip routing command.

 

There is also the detail of the link between S1 and R1.
In S1 you indicated that the interface belongs to vlan 90, so the packets that will be accepted will be those that arrive at the switch with the tag 90.

To solve this, you can tell the router to tag packets with tag 90 using a subinterface:

R1

interface Ethernet0/1

no ip address

interface Ethernet0/1.90

encapsulation dot1q 90

ip address 192.168.0.1 255.255.255.252

 

Salutations

 

 

Hello,

 

Thank you for your response. 

Thanks to your reflexion I understood where the mistake came from.

 

I corrected it by activating ip routing command. 

And then I disabled switchport on the eth0/0 interface of S1 and assigned an ip.

 

 

S1#show running-config ethernet interface 0/0
Building configuration...

Current configuration: 84 bytes
!
Ethernet interface0/0
no switchport
ip address 192.168.0.2 255.255.255.252
end

 

 

Now clt 2 can reach router R1 192.168.0.1

 

Thank you again for your response

Hi @soso1061 

 

Je suis content que ça t'ait servi.
N'oubliez pas de marquer les bonnes réponses comme résolues, car cela a aidé d'autres utilisateurs ayant des doutes similaires.

Cordialement

 

I am happy that is was useful for you.
Remember to mark the correct answers as solved, because that helped other users with similar questions.

 

Cheers