Showing results for 
Search instead for 
Did you mean: 

Cannot ping its own interface help [Basic]

Protocol [ip]:
Target IP address:
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Ingress ping [n]:
Source address or interface: GigabitEthernet0/0
DSCP Value [0]:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0x0000ABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
Packet sent with a source address of
Success rate is 0 percent (0/5)




But it can show neighbor :


Cisco-3650-109_Sr#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID Local Intrfce Holdtme Capability Platform Port ID
Gig 0/0 96 R MikroTik sfp-sfpplus2
Gig 1/0/23 96 R MikroTik Bridge-iSCSI/ether24-to-201
Gig 0/0 109 R MikroTik Bridge-Port-LAN/Bonding to CO
RT CORE GEMAPRO Gig 0/0 80 R MikroTik Bridge-Port-LAN/ether10

Total cdp entries displayed : 4




sho int GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is RP management port, address is 00b7.7129.0680 (bia 00b7.7129.0680)
Internet address is
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 128/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:16, output 00:00:15, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/3883676/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 45000 bits/sec, 49 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
4341103 packets input, 640195068 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
3883676 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
86879 packets output, 7741766 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
2 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

Giuseppe Larosa
Hall of Fame Master

Hello @KemalRzky_ ,


show run int gi0/0


show ip vrf


a possible explanation is that the interface is member of a VRF and so it cannot pinged normally you should ping vrf <vrf-name>

Some devices have a built in VRF named management and this can be your case as gi0/0 can be the management interface.


usually on switches the first user data port is something like gi0/1


Hope to help



Hi sir,


Thankyou for your answer..


I have checked the system and it shows:


#show run int gi0/0
Building configuration...

Current configuration : 175 bytes
interface GigabitEthernet0/0
vrf forwarding Mgmt-vrf
ip address
no ip redirects
no ip unreachables
no ip proxy-arp
negotiation auto


#sh ip vrf
Name Default RD Interfaces
Mgmt-vrf <not set> Gi0/0




What should i do next, if i still want to use Mgmnt Ethernet?

I'm sorry for this basic question '')

Hello @KemalRzky_ ,

move the configuration to another interface on the switch without the line

vrf forwarding Mgmt-vrf.

and adding the line

no switchport

! to be able to give an IP address to it

Gi0/0 is dedicated to management purposes and have some limitations give it a different IP address in a different IP subnet and do not use it for the moment.


Hope to help