Comando de verificação no Roteador Cisco 2800

Boa tarde,

Amigos!

Por favor, preciso da ajuda de vocês quais são os camandos de verificação de cagar, de CPU e Link no roteador da Cisco 2800?

Os comandos do roteador 2500 da Cisco são diferentes do 2800.

Consigo verificar com comando se meus links estão no gargalo de trafego?

Aguardo ajuda de vcs.

Obrigado.

João Paulo Machado Vieira

joaopaulo88, boa noite.

Tente os comandos abaixo:

Utilização do link:
1) show interfaces xx/xx

Utilização da CPU:
2) sh processes cpu
3) sh processes cpu history



====================================
Exemplo: Utilização do link
====================================
PE-REDE-CPD-01#sh int gi2/0
GigabitEthernet2/0 is up, line protocol is up
Hardware is 82543, address is ca02.132c.0038 (bia ca02.132c.0038)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is SX
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:06, output hang never
Last clearing of "show interface" counters never
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
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
4 packets output, 1158 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out


====================================
Exemplo - Utilização da CPU
====================================

PE-REDE-CPD-01#sh processes cpu
CPU utilization for five seconds: 5%/90%; one minute: 5%; five minutes: 1%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
1 0 2 0 0.00% 0.00% 0.00% 0 Chunk Manager
2 92 15 6133 0.23% 0.09% 0.03% 0 Load Meter
3 1636 188 8702 0.31% 1.56% 0.44% 0 Exec
4 188 14 13428 0.00% 0.16% 0.04% 0 Check heaps
5 0 1 0 0.00% 0.00% 0.00% 0 Pool Manager
6 0 1 0 0.00% 0.00% 0.00% 0 DiscardQ Backgro
7 4 2 2000 0.00% 0.00% 0.00% 0 Timers
8 4 13 307 0.00% 0.00% 0.00% 0 WATCH_AFS
9 0 1 0 0.00% 0.00% 0.00% 0 ARP Input
10 32 89 359 0.00% 0.01% 0.00% 0 ARP Background
11 0 2 0 0.00% 0.00% 0.00% 0 ATM Idle Timer




====================================
Exemplo 2 - Utilização da CPU
====================================
PE-REDE-CPD-01# sh processes cpu history




966666666666666655555999997777755555444446666666666777776666
100
90
80
70
60
50
40
30
20
10 ************************************ *****************
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per second (last 60 seconds)


Abraços,
Marcelo Guerra

João Paulo,
use o comando :
show interfaces serial x/x e da uma olhada na linha:
reliability 255/255, txload 1/255, rxload 1/255
quanto menor for o txoad e o rxload melhor, ele so vai esta gargalado se estiver txload 255/255 e rxload 255/255

EXEMPLO:
Router#sh interfaces serial 1/0
Serial1/0 is down, line protocol is down (disabled)
Hardware is HD64570
MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 96 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 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
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=down DSR=down DTR=down RTS=down CTS=down

Só complementando o post acima.Quando voce checa a interface 
reliability 255/255, txload 1/255, rxload 1/255
Reliability - 255/255 = Quer dizer que o link é 100% confiavel, 255 de 255 igual a 100%
Tx - 1/255 - porcentagem de transmissão do link, se estiver 255/255 = 100% de utilização da banda na transmissão.
Rx - 1/255 - É a porcentagem de recebimento de pacotes.


0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
Outro campo importante voce prestar atenção quando verificar as interfaces, se não há nenhum erro CRC. Ele indica erros na camada 2/1. Indica quadros corrompidos.

------
Agora na minha opinião o comando mais lindo do mundo


#show ip interface brief. = mostra um sumário das suas interfaces.