This is my first time posting here and hope this is the right place to start.
We just switched over our frame sites to point to point T1. Had the lowest bidder (We are a government agency) come in to configure our routers, nothing has worked right yet. We have gone through 2 consultant from this company. We have two issues but was wondering If anyone else has any tips for the configuration - if you notice anything missing or just outright wrong:
#1. A site keeps keeps going up and down. It's at random times. I'm having the line check done on it, but I've been advise that a misconfigured clock source can cause this.
#2. DHCP cannot send offer to workstation over the new lines. The workstation makes a request and DHCP see's it, it sends an OFFER but it seems like the router isn't forwarding it on. I have a post about it with more info at novell site (see link at bototm)- not sure if its a CISCO issue or a NOVELL issue...
We have a 7204 VXR with an 8 port CSU/DSU at our HQ
We have 1760 ciscos on the remote end
I only see a clock source on the 7204 VXR in the Config.
Heres the 7204 VXR Config at HQ, I've only included two controller's and two serial in the configure.. they are all the same:
Ensure that one side is configured to provide clock, this would be the internal setting , the other end should be set to clock source network. This means that it is looking for clock from the network. A good indication of a clocking issue is if you see a lot of aborts in your show interface serial x . Another thing you may want to check is call your provider and make sure they are not providing clock. If they are you should set the clock source to network on both ends.
Just some quick thoughts. These are not meant to be solutions but these are the first things that I would look at from the small amount of info you provided.
1. You are running RIP V2 which is classless. However, RIP V2 is normally configured in two places, in router mode (which you have) and interface mode (which you do not). You need to specify an interface as RIP2, both sending and receiving. Ohterwise RIPV1 updates will be sent out of the interfaces. Being that RIP1 is classful your T1's may look as if they are on the same subnet giving you IP routing problems. Looking at your config I would lose the RIP 2 all together (and the EIGRP). The 1760 is isolated and only requires a default route. Just make sure the statics are in the 7204 for the net behind the 1760.
2. Clocking. Check the clocking on the CSU/DSU at the remote site (1760). It should be set for line. If it is not then you have a problem. If the telco is providing a clock signal then you also have a problem on the 7204 providing an internal clock source.
We are running rip2 right now because we have some ISDN and Frame Relay sites still running (converting one site at a time, we have a total of 7 sites converting over point-to-point t1). We need the rip2 on so the new sites can get the only site routes. Once everything is converted over we will loose the rip2. We need to keep, as far as I know, eigrp so the sites will know about eachother. As far as setting up rip2 in interface mode
ip rip send version 2
ip rip receive version 2
What's the rule as far as what interface to configure it to? Serial and Ethernet on both routers? I'll do some reading up - but any advice would be great.
Thanks I will call my provider and see if they provide clock.
Yep - I already have the ip helper-address command in the config. Still not passing the DHCPOFFER to the workstations.
I always prefer not to run routing protocols all the way to the edge(your 1700) if it is unnecessary. In this case, it does not seem necessary. Just use statics at the 7204 and redistrbute them into the routing protocol, rip or eigrp. But, that is just a preference. I feel it makes for easier troubleshooting if you only use routing protocols at the core.
The rip config looks right, you need to apply it to every interface that will advertise and receive routes.
You got me on the DHCP, could be related to the routing.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...