Setting the DLCI on a 1760

[quickconnect]

I am having some majot problems with one of my international routers (Cisco 1760) Currently what is happening is the routers Serial 0/0 interface which is connected to the internet keeps getting peeking with very high Utilization beyond 160% I beleive the line speed is not set properly. Currently I was told by the ISP that they have this
Data Access Port: 256K
DLCI 835: 192K CIR, 0K EIR
DLCI 141: 32K CIR, 64KEIR

If I do a show interfaces this is what the serial 0/0 is configured for:
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 200.44.127.10/30
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 63/255, rxload 120/255
Encapsulation FRAME-RELAY IETF, loopback not set
Keepalive set (10 sec)
LMI enq sent 364, LMI stat recvd 364, LMI upd recvd 0, DTE LMI up
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
FR SVC disabled, LAPF state down
Broadcast queue 0/64, broadcasts sent/dropped 5/0, interface broadcasts 0
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 01:00:44
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/11/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 48 kilobits/sec
5 minute input rate 89000 bits/sec, 17 packets/sec
5 minute output rate 18000 bits/sec, 15 packets/sec
60359 packets input, 29689100 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
50645 packets output, 8964173 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


What do I have to do to get the correct Data Access Port speeds and DLCI speeds set correctly I believe that is what is killing the interface...

 

[quickconnect]

I just changed the bandwidth speed from 64k to 192K

Here is my show run...Please tell me if it looks correct for the above stated settings

interface Serial0/0
bandwidth 192
ip address 200.x.x.x 255.255.x.x
ip access-group 110 in
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
encapsulation frame-relay IETF
no ip route-cache cef
no ip route-cache
no ip mroute-cache
frame-relay interface-dlci 835
frame-relay lmi-type ansi
crypto map ******

 

[JOAMON]

Are you sure you dont need to use the "clockrate 192000" command to set the speed. I thought the bandwidth command was just for informational purposes.

 

[plshlpme]

the bandwidth command is just for routing metrics...
but the actual speed of the cct will be set by the isp using the cir...
the frame switches will mark the packets discard eligable if there is congestion on the link..

in alot of cases the isp/telco will provide a full t1 to the customer and then apply the cir. so if there is no network congestion you can actually burst to the full T1.

usually they will put some CAR on the routers at both ends though to limit the traffic.

so it is ok to see your traffic burst.. just don't get mad when your bursting and packets start dropping...

 

[plshlpme]

just curious though what is the problem?
is it that your seeing high utilization from some management software? or is the circuit actually taking hits?

 

[quickconnect]

The problem I am having is that we are getting complaints from that location that about 2/3 times a day traffic stops or comes to a stopping streach and the only way they can fix it since they dont have access to the router is to reboot it and everyting starts to work again.

I am currently monitoring that serial interface and see that the percent utilization on the serial interface will spike very high several times a day. I dont see any other problems with the router. Matter of fact this is a new router for them which I replaced a few months back. I was lead to beleave that it was an interface bandwitch issue because like I stated about it was set to bandwidth 65 rather then bandwidth 192....

Now raises the question to is that just a reference statement or the actuall interface speed setting? Do you recommend I look at some thing else?

 

[JOAMON]

Do a show process cpu history and look at the cpu load. Also look inside for a blaster or other virus infected machine. These can mess up your network in a hurry. If you have a managed switch you could do a show interface and look at the stats and spot the machine that way as well.

 

[quickconnect]

CPU load is fine something like 20-30%

 

[JOAMON]

Look for blaster.....search and destroy....

 

[plshlpme]

the bandwidth command has no bearing on the speed of the link.. its only used for routing metrics.

you could attach some rate limits to the interface so that you could get realtime stats on the interface.