02-04-2013 09:10 AM - edited 03-04-2019 06:56 PM
We have 2 Cisco 1921 routers setup with a fiber PTP between them with all of the internet coming through at 1 location. At the second location I installed a EHWIC model EHWIC-1GE-SFP-CU to connect to a cradlepoint cell modem that we can use as a backup in case the fiber goes down. From the router with the backup connection i turned on the backup interface and it switches fine between the primary and secondary link. From the router when I am connected to the backup it will ping outside with no problem, however if I try to do ping anything from an inside computer. Below is part of the running config plus the ip route - the ip route shows the primary link up. When the secondary comes up, the static route kicks in and shows up in ip route. I didn't want to mess with SLA as i have to purchase another license, and I already bought the EHWIC so i am hopeing I can get this working.
interface GigabitEthernet0/0
description Time Warner P2P
backup interface GigabitEthernet0/0/0
ip address 172.16.0.2 255.255.255.252
duplex auto
speed auto
service-policy output QoS_Policy
!
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/1.1
description LAN 192.168.2.0/24
encapsulation dot1Q 1 native
ip address 192.168.2.241 255.255.255.0 secondary
ip address 192.168.2.254 255.255.255.0
!
interface GigabitEthernet0/1.30
description VoIP 192.168.32.0/24
encapsulation dot1Q 30
ip address 192.168.32.254 255.255.255.0
ip helper-address 192.168.2.4
!
interface GigabitEthernet0/1.100
description Public Wifi 192.168.102.0/24
encapsulation dot1Q 100
ip address 192.168.102.254 255.255.255.0
ip access-group Wireless_Out_ACL in
ip access-group Wireless_In_ACL out
rate-limit input 1496000 512000 1000000 conform-action continue exceed-action drop
rate-limit output 1496000 512000 1000000 conform-action continue exceed-action drop
!
interface GigabitEthernet0/1.110
description Camera 192.168.112.0/24
encapsulation dot1Q 110
ip address 192.168.112.254 255.255.255.0
!
interface GigabitEthernet0/0/0
ip address 10.10.10.1 255.255.255.0
duplex auto
speed auto
!
router ospf 100
network 10.10.10.0 0.0.0.255 area 0
network 172.16.0.0 0.0.0.3 area 0
network 192.168.2.0 0.0.0.255 area 0
network 192.168.32.0 0.0.0.255 area 0
network 192.168.112.0 0.0.0.255 area 0
!
ip forward-protocol nd
!
ip route 0.0.0.0 0.0.0.0 10.10.10.2
!
O*E2 0.0.0.0/0 [110/1] via 172.16.0.1, 1d01h, GigabitEthernet0/0
172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.16.0.0/30 is directly connected, GigabitEthernet0/0
L 172.16.0.2/32 is directly connected, GigabitEthernet0/0
O 192.168.1.0/24 [110/2] via 172.16.0.1, 1d01h, GigabitEthernet0/0
192.168.2.0/24 is variably subnetted, 3 subnets, 2 masks
C 192.168.2.0/24 is directly connected, GigabitEthernet0/1.1
L 192.168.2.241/32 is directly connected, GigabitEthernet0/1.1
L 192.168.2.254/32 is directly connected, GigabitEthernet0/1.1
O 192.168.31.0/24 [110/2] via 172.16.0.1, 1d01h, GigabitEthernet0/0
192.168.32.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.32.0/24 is directly connected, GigabitEthernet0/1.30
L 192.168.32.254/32 is directly connected, GigabitEthernet0/1.30
192.168.102.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.102.0/24 is directly connected, GigabitEthernet0/1.100
L 192.168.102.254/32 is directly connected, GigabitEthernet0/1.100
O 192.168.111.0/24 [110/2] via 172.16.0.1, 1d01h, GigabitEthernet0/0
192.168.112.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.112.0/24 is directly connected, GigabitEthernet0/1.110
L 192.168.112.254/32 is directly connected, GigabitEthernet0/1.110
02-04-2013 09:24 AM
Do you have any nat configuration going on somewhere?
02-04-2013 09:40 AM
No. The firewall is taking care of that.
02-04-2013 09:54 AM
do a traceroute from a computer and see where it stops
02-04-2013 09:57 AM
I have and it stops at the router. I can see the 10.10.10.1 ip on the router. I just can't get to 10.10.10.2.
02-04-2013 10:20 AM
That's where you need to either NAT or configure the cradlepoint to know about the network 192.168.x.x whatever the pcs are, because your router knows where 10.10.10.2 is (cuz it's directly connected) but the cradlepoint doesn't know how to get back to 192.168.x.x.
Hope that explains.
Let me know if you have any further questions
02-04-2013 10:39 AM
Another DUH! moment. (As he slams his head on his desk)
02-04-2013 10:49 AM
HeH
Please mark as helpful.
Thanks
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