bandwith issue

[roterro]

Hello,

We have two sites which are connected with a optic fiber access. This is supposed to be a 2Gbs link (in order to replicate data) . Our provider has confirmed there is no issue on the access, so we're almost sure that the issue is probably on the last hardware which has been installed (Nexus 6k L3). We made several tries : 

1. At first we got a 1Mbs speed
2. Then, advised by Cisco support, we changed a parameter (below)

class copp-system-class-glean
police cir 20480 kbps bc 6400000 bytes

and now, we got is a 20Mbs speed.

First, to be honest I'm not familiar with this command but I think this is not a durable solution.

Plus, we can't increase this value, so we're stuck to try our replication test with a speed of 2Gbs.

Here's a description of the interface which is is used for transfer :

CRCIS50# sh int e1/1
Ethernet1/1 is up
Dedicated Interface

Hardware: 1000/10000 Ethernet, address: 00de.fba5.c301 (bia 00de.fba5.c2c8)
Description: To Orleans via Providername 2Gb/s replic TSM
Internet Address is 10.35.167.60/30
MTU 1600 bytes, BW 10000000 Kbit,, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
full-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 3week(s) 4day(s)
Last clearing of "show interface" counters 5d02h
0 interface resets
30 seconds input rate 216 bits/sec, 0 packets/sec
30 seconds output rate 136 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 144 bps, 0 pps; output rate 216 bps, 0 pps
RX
1717584 unicast packets 57664 multicast packets 0 broadcast packets
1775248 input packets 2333633862 bytes
0 jumbo packets 0 storm suppression bytes
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 39616 input discard
0 Rx pause
TX
955326 unicast packets 72486 multicast packets 0 broadcast packets
1027812 output packets 89197043 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause

Any suggestions to improve speed ?

Thanks in advance.

Robert

[Georg Pauwen]

Hello,

what happens when you set the police cir to:

class copp-system-class-glean

police cir 2048000 kbps bc 640000000 bytes

[paul driver]

---

@Georg Pauwen wrote:

Hello,

what happens when you set the police cir to:

class copp-system-class-glean

police cir 2048000 kbps bc 640000000 bytes

---

The cir bc rate doesn't look correct, even though the cir rate is kps i think it should be calculated in bps to gain the appropriate bc rate.

So i think with the cir would be 20480000 bps (2048000 kps) with default bc of 640000 bytes at a tc rate 0.25 or a bc of 320000 byes at a tc rate 1.25

[Georg Pauwen]

Actually, reading through your post again, I don't really see how the glean class would influence the transfer rate, as it is related to missing destination MACs...

Either way, what is connected to the other side ? 1 MB is so low, there must be something fundamentally misconfigured, such as MTU size...

[paul driver]

Hello

---

@roterro wrote:

Hello,

We have two sites which are connected with a optic fiber access. This is supposed to be a 2Gbs link (in order to replicate data) . Our provider has confirmed there is no issue on the access, so we're almost sure that the issue is probably on the last hardware which has been installed (Nexus 6k L3). We made several tries : 

1. At first we got a 1Mbs speed
2. Then, advised by Cisco support, we changed a parameter (below)

class copp-system-class-glean
police cir 20480 kbps bc 6400000 bytes

and now, we got is a 20Mbs speed.

First, to be honest I'm not familiar with this command but I think this is not a durable solution.

Plus, we can't increase this value, so we're stuck to try our replication test with a speed of 2Gbs.

---

Not so sure i understand you comment?

[roterro · Accepted solution]

Guys,

Just a quick update. Cisco Support helped me to solve this issue.

There was a missing parameter on the Nexus :

Instead of ip route 192.116.7.18/32 Vlan102

They configured the route as :

ip route 192.116.7.18/32 Vlan102 192.116.7.18

I don't exactly why they added the same ip address at the end, but now the speed is very high (1.4 Gps).

So issue is solved.