03-21-2006 09:19 AM - edited 03-03-2019 12:07 PM
Hi Guys,
Forgive me if this is the wrong forum.
I have a 2MB P2P line between two offices, the link is provided by NTL and on each end I has a
Cisco2621XM router with a WIC interface connected to the media convertors.
The problem i have is that most of the infrastructure, primary domain controllers, dns, dhcp, user profiles etc.. are located in the HQ and remote users are logging into client machines at the sub-office. When users login at the sub-office it can sometimes take upto an hour for a users profile to load and these profiles are no more than 500MB.
I've had NTL in to look at the P2P line three times and now im looking at the hardware/config of the routers and wondering if you could help me.
Any suggestions welcome
Cheers
Darren
03-21-2006 09:51 AM
Darren
I see several things to comment about though I am not sure that I see the problem clearly.
On the BAT router the RIP configuration has network statements for 192.168.1.0 and 192.168.2.0. It does not have a network statement for 192.168.3.0 which is the serial interface and I can not find any network 192.168.2.0 on the router.
Simmilarly on the HUD there are RIP network statements for 192.168.4.0 and 192.168.5.0 but not for 192.168.3.0.
Another thing that puzzles me is that the BAT router has an ip helper address pointing to an address on the FastEthernet of HUD and that HUD has an ip helper address pointing to an address on the FastEthernet of BAT. Why are the routers pointing helper addresses at each other? And why are there helper addresses configured on both serial interfaces. I doubt that helper addresses on the serial hurts anything, but it does not good.
I also note on the HUD router that the FastEthernet has its speed and duplex specifically set. This will prevent negotiation with whatever device is connected to that interfade (I am guessing some switch). If the other device is configured to negotiate speed and/or duplex then negotiation will fail, the other device probably assumes half duplex operation. The mismatch of duplex will contribute to poor performance.
Perhaps resolving some of these things may help to solve your performance problem. (I do not see anything configured that should impact the serial interface
HTH
Rick
03-21-2006 12:02 PM
what is the out from the sho serial interface.
Also does one one of the media converters provide clocking, can get errors if both have been setup to provide clocking
03-22-2006 09:46 AM
Here are the outputs from show;
DVWAN-BAT-001#show interfaces serial 0/0
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 192.168.3.1/24
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:07, output 00:00:04, output hang never
Last clearing of "show interface" counters 1w5d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1465247
Queueing strategy: weighted fair
Output queue: 0/1000/64/1465247 (size/max total/threshold/drops)
Conversations 0/23/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 1536 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
98482496 packets input, 3289274195 bytes, 0 no buffer
Received 121343 broadcasts, 0 runts, 6 giants, 0 throttles
3150 input errors, 1539 CRC, 1456 frame, 0 overrun, 0 ignored, 155 abort
140824362 packets output, 1483017618 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
DVWAN-BAT-001#
and..
DVWAN-HUD-001#show interfaces serial 0/0
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 192.168.3.2/24
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 2
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/10/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 1536 kilobits/sec
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
158149575 packets input, 1901709338 bytes, 0 no buffer
Received 141097 broadcasts, 0 runts, 0 giants, 0 throttles
139 input errors, 10 CRC, 121 frame, 0 overrun, 0 ignored, 8 abort
109089828 packets output, 4064794721 bytes, 0 underruns
0 output errors, 0 collisions, 33 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
DVWAN-HUD-001#
Cheers
03-22-2006 11:26 AM
Darren
I do notice one thing in the output that you posted:
on the BAT router is this: Total output drops: 1465247
There is not many output drops on the other router. Is BAT the router where the users are experiencing problems?
Perhaps posting the interface configurations might be helpful.
HTH
Rick
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: