08-11-2022 03:04 PM - last edited on 08-17-2022 03:34 AM by Translator
Greetings
I have a problem, and i dont know if my problem is due to the IOS.
My problem is that i cannot ping my border router interfaces sourced its own other connected interfaces. Here is all the information:
Border_Router#sh run
Building configuration...
Current configuration : 1893 bytes
!
! Last configuration change at 21:33:30 UTC Thu Aug 11 2022
!
version 15.6
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Border_Router
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
ethernet lmi ce
!
!
!
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
!
!
!
!
!
!
!
!
!
!
!
ip cef
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 1.1.1.1 255.255.255.255
!
interface GigabitEthernet0/0
ip address dhcp
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/1
ip address 192.168.2.1 255.255.255.0
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/2
ip address 10.0.0.1 255.255.255.252
ip ospf 1 area 0
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/3
ip address 10.1.1.1 255.255.255.252
ip ospf 1 area 0
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/4
no ip address
shutdown
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/5
no ip address
shutdown
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/6
no ip address
shutdown
duplex full
speed auto
media-type rj45
!
interface GigabitEthernet0/7
no ip address
shutdown
duplex full
speed auto
media-type rj45
!
router ospf 1
router-id 1.1.1.1
default-information originate
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/1 192.168.2.2 5
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0 dhcp
!
!
!
!
control-plane
!
!
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
transport preferred ssh
line aux 0
line vty 0 4
login
transport input ssh
line vty 5
login
transport input none
!
no scheduler allocate
!
end
Border_Router#
_________________________________________________--
Border_Router#sh 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 192.168.1.1 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 192.168.1.1, GigabitEthernet0/0
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C 10.0.0.0/30 is directly connected, GigabitEthernet0/2
L 10.0.0.1/32 is directly connected, GigabitEthernet0/2
C 10.1.1.0/30 is directly connected, GigabitEthernet0/3
L 10.1.1.1/32 is directly connected, GigabitEthernet0/3
100.0.0.0/32 is subnetted, 1 subnets
O 100.100.100.100 [110/2] via 10.0.0.2, 00:33:10, GigabitEthernet0/2
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, GigabitEthernet0/0
L 192.168.1.165/32 is directly connected, GigabitEthernet0/0
192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.2.0/24 is directly connected, GigabitEthernet0/1
L 192.168.2.1/32 is directly connected, GigabitEthernet0/1
200.200.200.0/32 is subnetted, 1 subnets
O 200.200.200.200 [110/2] via 10.1.1.2, 00:33:00, GigabitEthernet0/3
Border_Router#
______________________________________________
Border_Router#sh cdp neig
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
CORE_1 Gig 0/2 129 R S I Gig 0/0
CORE_2 Gig 0/3 173 R S I Gig 0/0
Total cdp entries displayed : 2
_______________________________________________
Border_Router#ping 192.168.1.1 source 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
Packet sent with a source address of 1.1.1.1
.....
Success rate is 0 percent (0/5)
Border_Router#ping 192.168.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/5/12 ms
Border_Router#
_____________________________________________________
Border_Router#show ip int br
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 192.168.1.165 YES DHCP up up
GigabitEthernet0/1 192.168.2.1 YES NVRAM up up
GigabitEthernet0/2 10.0.0.1 YES NVRAM up up
GigabitEthernet0/3 10.1.1.1 YES NVRAM up up
GigabitEthernet0/4 unassigned YES unset administratively down down
GigabitEthernet0/5 unassigned YES unset administratively down down
GigabitEthernet0/6 unassigned YES unset administratively down down
GigabitEthernet0/7 unassigned YES unset administratively down down
Loopback0 1.1.1.1 YES manual up up
Border_Router#
Solved! Go to Solution.
08-11-2022 07:08 PM
that why we use NAT in such case
we will NAT all traffic to interface connect to Cloud and since the cloud already know this IP (it direct connect) the connection success.
08-11-2022 03:10 PM - last edited on 08-17-2022 03:35 AM by Translator
I see under ospf only
default-information
re you sure that you have OSPF adj between the edge router and both Core SW & Cloud??
08-11-2022 03:47 PM
Hi, I don't need for the moment, connectivity between the core switchs and the border router.
The cloud device Is the cloud to internet and is bridged to the server interface. I have in my border router a static route to the internet.
As you can see in the info, I can ping to the cloud device
08-11-2022 04:01 PM - last edited on 08-17-2022 03:41 AM by Translator
GigabitEthernet0/0 192.168.1.165 YES DHCP up up
the cloud as you attach photo connect to g0/0,
and sure you can ping it because you direct connect to it
but when select source
the cloud need to know the retrun back traffic?
how cloud learn retrun back traffic to 1.1.1.1 ?
08-11-2022 06:52 PM
How can i tell the cloud device the route if i can´t administrate it? is just a bridge to the server interface in EVE
08-11-2022 07:08 PM
that why we use NAT in such case
we will NAT all traffic to interface connect to Cloud and since the cloud already know this IP (it direct connect) the connection success.
08-11-2022 08:02 PM
Excelent i ll try and ill notify you the results!! Thanks
08-11-2022 08:45 PM
The NAT worked!! Thanks
08-11-2022 03:34 PM
Hi @mikemanz83 ,
This simply means that the neighbour device (192.168.1.1) doesn't have a route to 1.1.1.1.
Regards,
08-11-2022 03:50 PM
Hello,
As you can see in the information, I can ping to the cloud device and the internet but when I ping to let's say 8.8.8.8 source 1.1.1.1 I can't ping to any route in the internet.
The cloud device is a bridge to the server interface.
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