
[/B]
I have had problems and recieved this from Email from them explaining their upgrade. Check it out;
Thanks for the information. We have discovered some inefficiencies in the way our headend routers were initially set up and are working to improve things greatly. We have engaged Cisco Professional Services for a number of weeks onsite to help us optimize our network and install & configure some new, very high-end equipment to give us a solid foundation on which to grow in the future. We're spending approximately a half-million dollars on replacements/upgrades. During this time of transition, however, there may be times when things don't work optimally because perhaps only a partial solution is implemented and the remainder will be implemented shortly.
We are upgrading all the interfaces on our routers from 100mb FastE to OC12 optical - 6x faster, as well as implemeting gigabit-level core routers and core switches with 12x greater capacity than we have now. Bear with us during this transitional time as we improve our infrastructure to offer our Pipeline customers even greater
speed and reliability. If you're still seeing these kinds of slowdowns a month or so from now, let us know.
Based on the logs, the only real problem I see is high latency on the 2nd hop. That 2nd hop is not a hop we typically see. We usually see your PC, then the 24.216.191.1 address (edge router), then the 2 10.x addresses (confidential), then we hit Sprintlink. Are you running any kind of personal firewall/router hardware on your end? Is your connection modem, then straight to your PC, or is there something between your PC & the cable modem? The cable modem simply acts as a bridge, so it doesn't show up as a hop at all.
The 172.16.0.1 address is not a part of our network - I'm puzzled about where that's coming from. I just ran a traceroute from the modem network and the 172.16.0.1 hop did not appear. Is it still happening?
I notice the log is from Saturday - we made some changes to the network config last evening, so if this was happening then, what we did should have stopped it from continuing.
Again, thanks for the info. Keep us abreast if you see other anomalies like this. By the way, the slowdowns you may have perceived are probably due to our explosive growth straining the limits of our upstream internet connection. We have more bandwidth on the way which should be turned up before the weekend. See if that doesn't help.
Rob Moody
Charter Pipeline Manager
As you can see some great upgrades are on the way. ONE thing that puzzled me was that my logs showed me going to that 17. address which was not supposed to be happening.
