Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco Router / Metro E issues

Status
Not open for further replies.

kerneldead

IS-IT--Management
Jun 19, 2008
16
0
0
US
I have two routers a Cisco 1841 and a Cisco 3620. We have just invested in a Metro e 3.0 meg connection to replace a T1. I have put this connection into production last week only to have to revert back to my T1. The metro e connection started acting sluggish, I could not print across it to my print server, access files etc. here is my configurations:

Cisco 1841:
interface FastEthernet0/1
description Metro E
ip address 172.16.255.14 255.255.255.252
speed auto
full-duplex

Cisco 3620:
interface Ethernet1/0
description Metro E
ip address 172.16.255.13 255.255.255.252
full-duplex

Any ideas on what would cause the connection to degrade/ It almost seems like I have a bottle neck.

Thanks,
 
The first thing I would do is change the ethernet ports to 10/full. What are the ip's on the local and remote sites?

Do you have a default route built?

Can you test from point A to point B via FTP? Perform a up/download to verify speed. (multiple the time by 8 to get the actual speed).



[americanflag] Go Army!
Tek-TIP Member 19,650
 
Post a sh int on both sides.

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!
 
Jeter,

One router has the ip address of 172.16.6.1 and the other is 172.16.2.1. What do you mean change the ethernet ports to 10/full? I can pass traffic from A to B, but I have not tried using ftp in order to gauge my traffic speed.

Thanks,
 
First off, we want to look at all the errors (input, output, buffers, resets, crc) and verify the fa is neg @10/full. Please post a sh int from both sides on the interfaces in question here.

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!
 
If you have a true Metro Ethernet you need to choke down your routers Ethernet to speed 10 duplex full. The reason for this is because your provider should police the actual 3meg.






[americanflag] Go Army!
Tek-TIP Member 19,650
 
Here is the show interface for each:

Cisco 3620:
show interface ethernet1/0
Ethernet1/0 is up, line protocol is up
Hardware is AmdP2, address is 00e0.1e84.7671 (bia 00e0.1e84.7671)
Description: Metro E
Internet address is 172.16.255.13/30
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:46, output 00:00:09, output hang never
Last clearing of "show interface" counters 14:09:57
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
855 packets input, 302050 bytes, 0 no buffer
Received 852 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
5952 packets output, 647820 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

Cisco 1841:
show interface FastEthernet0/1
FastEthernet0/1 is up, line protocol is up
Hardware is Gt96k FE, address is 0022.5554.42d5 (bia 0022.5554.42d5)
Description: Metro E
Internet address is 172.16.255.14/30
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:04, output hang never
Last clearing of "show interface" counters 14:25:36
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 8000 bits/sec, 17 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1090008 packets input, 65815314 bytes
Received 1090005 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
6149 packets output, 625872 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

I hope this helps.

Thanks,
 
looks good other than the 3620 connecting a 10/half and the 1841 is at 100/full.


[americanflag] Go Army!
Tek-TIP Member 19,650
 
Jeter,

Would this cause my sluggishness? Should I set the 1841 to 10 or set the 3620 to 100? I have looked but can not find the command do set this can you point me in the right direction.

Thanks,
 
Jeter,

Can you also show me where in the output from the show interface command it tells you if it is set to 10 or 100?

Thanks,
 
Ethernet1/0 is up, line protocol is up
Hardware is AmdP2, address is 00e0.1e84.7671 (bia 00e0.1e84.7671)
Description: Metro E
Internet address is 172.16.255.13/30
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255

FastEthernet0/1 is up, line protocol is up
Hardware is Gt96k FE, address is 0022.5554.42d5 (bia 0022.5554.42d5)
Description: Metro E
Internet address is 172.16.255.14/30
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
the bolded parts above will show you the speed of the interface

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)
 
How can I set the to the same? I have them both set to full duplex. Is one only able to be set to 10 and the other up to 100? Having one set to 10 and the other to 100 would that gradually cause issues as more traffic past? It sounds to me that it would cause the bottle neck that I am getting.

Thanks,
 
Hello
The command is :

conf t
interface FastEthernet0/1
speed 10

In any case I don't the speed is the problem.The ISP will have some kind of switch in the middle that can support both speeds and neutralize the difference.

I would take a look at the broacast to be on the safe side.

"Received 1090005 broadcasts"

Also give the ISP all call to see what they have to say.

Regards
 
Yes, I agree. I am fairly confident that I have tried almost everything on my end. I will contact the ISP to see what they say. I will post the outcome either way.

Thanks,
 
FYI to those advising to set Ethernet to 10. Ethernet can only be 10.

Kerneldead,

If you had speed and duplex issues you'd see you'd see incrementing errors on your interfaces.
 
I'm saying the ethernet ports needs to be set to 10, the statement above says ports which is plural for more than one.

I know that a Ethernet is 10 and a fast Ethernet is a 100.

I work for a telco and I am here to tell you that this needs to be setup as 10/full, this includes the telco switch used at the d-mark....

Call your telco provider an perform a ftp test to confirm the actual speeds....



[americanflag] Go Army!
Tek-TIP Member 19,650
 
The half duplex will be an issue, even if you don't see late collisions on THAT interface. It is happening somewhere.

The ISP likely has auto, and the ethernet (10MBps) is set to half as a result.

Tell the ISP to change their end to 10/full on BOTH lkinks!

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!
 
It was on the providers side. They worked on the Metro-e for 4 days. Now we are error free. I have noticed that on my fastethernet interface I am getting dropped protocols or unknown protocols. Is there a way to tell the fastethernet interface to allow all protocols?
 
What you've learned is that the old-fashioned habits of not-using Auto/Auto speed/Duplex settings causes problems in this age of Auto/Auto being the standard default setting for everything.

Capture some of the traffic - it's not likely you will actually want any of these "unknown" protocols on your network.
 
I thought I kinda said that, except some auto neg protocols do not jive with Cisco. I am all for setting static deals, especially CatOS switch trunks...;)

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top