Search results for query: *

It is the 199.16.16.0 network. Thank you for your help.

I think we have at least some of it figured out. There were some ripping issues, but the bigger problem is the remote router is rebooting. Some diagnostics on the remote rotuer found the router getting BUS Errors and cold starting. I contacted Cisco and I have a replacement coming today.

The 3500's are 3512xls. Older units. Not showing the source of the update was the strange part. The syslog shows "adding 0.0.0.0/0(metric 1) via 0.0.0.0 on FastEthernet0/0 to RIP database. The it follows with redist 0.0.0.0/0 (metric 0) to RIP. I have another wrinkle that maybe the ultimate...

Neither the 6506 nor the firewall have rip enabled. Also, all our routers are cisco

Most of the switches on my network are 2900xl and 3500xl but we do have a few 2950s. Our core switch is 6506. I am using RIPv2 because it is what I have inherited. I am looking at alternatives like OSPF, but have not moved forward with it yet.

The destination is 199.16.16.0 which has 3 routes 199.16.25.14 - T1 199.16.25.30 - T1 199.16.25.102 - ISDN DOD I just had another outage and I was running a Syslog and capturing IP routing events and found there is a RIP update coming in and flushing the routes and installing a new route to...

I almost forgot: yes 172.16.18.254 is our firewall and is the next hop out

Here is the sh ip route while it is working: Codes: C - connected, S - static, I - IGRP, 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...

Here is a pretty sanitized verision: Interfaces that are shutdown are removed: version 12.2 no service single-slot-reload-enable service timestamps debug uptime service timestamps log datetime localtime no service password-encryption no service dhcp ! hostname ROUTER ! ip subnet-zero ip cef ...

Have a Cisco 3640 router that stops routing to one destination. The destination uses 2-T1's and is configured for packet-based loadbalancing. The symptoms during the routing problem are: 1.) From the ethernet side cannot ping the single destination 2.) inside router - Can ping all destinations...