topic Re: Cisco first timer. Can't ping own interface. in Routing and SD-WAN

Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 13:25:05 GMT

I am trying to follow this guide and I am on step 2. Configuring Cisco Router for Internet Access-IP Route Cisco | Configuring Cisco (deltaconfig.com)
I am consoled into my router.
I have a Cisco ASR 1001 and I am setting up the TenGig TE1 as my WAN port. I cannot ping the IP set on my TE1 port from the console.

show ip int bri shows the public IP set on the port but status down but I don't think this should matter?

Everything is being done from the router.

Re: Cisco first timer. Can't ping own interface.

balaji.bandi — Mon, 04 Oct 2021 13:39:54 GMT

show ip int bri shows the public IP set on the port but status down but I don't think this should matter?

If you like to ping the device, that port should be up and protocol UP.

Can you post show ip interface brief ? ( as soon as you enter ip config and no shutdown, the interface should come up ?)

Re: Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 14:41:30 GMT

Maybe something is up with Ping from router?
I can't ping my MGMT IP from the router. I tried it via MGMT port (Via IP) and Console port.
I can ping the MGMT IP from my computer though.
Inbound and outbound common ACL and ACL is not set.

Interface IP-Address OK? Method Status Protocol
Te0/1/0 "x.x.x.x PUBLIC IP" YES manual down down

GigabitEthernet0 192.168.10.1 YES NVRAM up up

Re: Cisco first timer. Can't ping own interface.

balaji.bandi — Mon, 04 Oct 2021 14:55:51 GMT

Most case the Interface in VRF, so you can not ping directly

try below :

Router# ping vrf Mgmt-intf 192.168.10.1

still issue, can you post below output

show run interface gig 0/0

Re: Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 15:27:32 GMT

% VRF Mgmt-intf does not have a usable source address

interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 192.168.10.1 255.255.255.0
negotiation auto
no mop enabled
end

Show interface stats show no packets in or out for the WAN port. This most likely means there's a connection issue between the CISCO router and ISP modem unless I got a bad port config such as a bad public IP?
TenGigabitEthernet0/1/0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 0 0 0 0
Route cache 0 0 0 0
Distributed cache 0 0 0 0
Total 0 0 0 0

Re: Cisco first timer. Can't ping own interface.

balaji.bandi — Mon, 04 Oct 2021 15:33:17 GMT

As per the interface config, the G0 belong to VRF

below command should work :

ping vrf Mgmt-intf 192.168.10.1

what is the outcome simple ping

ping 192.168.10.1

can you post below output

show interface gi0

show ip route

show ip interface brief

Re: Cisco first timer. Can't ping own interface.

Georg Pauwen — Mon, 04 Oct 2021 15:35:04 GMT

Hello,

down/down usually indicates a physical (cabling) problem. What ISP modem/router model do you have ? Then TenGigabitEthernet might be the problem, I have not seen an ISP modem with such an interface yet...

Re: Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 15:45:09 GMT

I am not in charge of the ISP modem. I will need to check to get back to you but it's supposed to be a 10G line.

Re: Cisco first timer. Can't ping own interface.

Georg Pauwen — Mon, 04 Oct 2021 15:59:06 GMT

Hello,

check if the TenG port supports MDIX, the command should be something like 'mdix auto'...

Re: Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 16:05:04 GMT

No issues with ping now. Back to the WAN pinging its own interface issue. Wonder if it's a physical issues instead.
ping vrf Mgmt-intf 192.168.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.10.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

TIF-ASR#ping 192.168.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.10.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

For the WAN port

show interfaces TenGigabitEthernet 0/1/0
TenGigabitEthernet0/1/0 is down, line protocol is down
Hardware is BUILT-IN-8X10G/1G, address is 40b5.c141.5020 (bia 40b5.c141.5020)
Internet address is "PUBLIC IP/SUBNET"
MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full Duplex, 10000Mbps, link type is force-up, media type is 10GBase-SR
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions

#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/1 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/2 192.168.20.1 YES NVRAM down down
GigabitEthernet0/0/3 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/4 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/5 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/6 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/7 unassigned YES NVRAM administratively down down
Te0/1/0 "PUBLIC IP" YES manual down down
Te0/1/1 unassigned YES NVRAM administratively down down
Te0/1/2 unassigned YES NVRAM administratively down down
Te0/1/3 unassigned YES NVRAM administratively down down
Te0/1/4 unassigned YES NVRAM administratively down down
Te0/1/5 unassigned YES NVRAM administratively down down
Te0/1/6 unassigned YES NVRAM administratively down down
Te0/1/7 unassigned YES NVRAM administratively down down
GigabitEthernet0 192.168.10.1 YES NVRAM up up

Re: Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 16:11:30 GMT

That command isn't an option on my router.

Re: Cisco first timer. Can't ping own interface.

balaji.bandi — Mon, 04 Oct 2021 16:24:00 GMT

show interfaces TenGigabitEthernet 0/1/0 
TenGigabitEthernet0/1/0 is down, line protocol is down
Hardware is BUILT-IN-8X10G/1G, address is 40b5.c141.5020 (bia 40b5.c141.5020)
Internet address is "PUBLIC IP/SUBNET"

This show interface Down ? You have SFP 10GBase-SR - I do not see the Port come up, (is the IP address configured Manually ?)

is the ISP offer 10GB connection to you, check the fibre patch between ISP NTU / Router.

Re: Cisco first timer. Can't ping own interface.

tripline — Mon, 04 Oct 2021 16:44:50 GMT

The interface shows down. SFP module is 10G-SR plugged in. I also tried a 10G-LR-S module. The public IP given to me is manually configured. I will check with the cabling team to see if the patching is correct. Thanks for your help.

Re: Cisco first timer. Can't ping own interface.

balaji.bandi — Mon, 04 Oct 2021 16:55:51 GMT

sure feedus back, this is most cause L1 cable issue. this need to be fixed. (once we see port up/up then we can assits better.