//EtherLike-MIB Align-Err 1.3.6.1.2.1.10.7.2.1.2 FCS-Err 1.3.6.1.2.1.10.7.2.1.3 Single-Col 1.3.6.1.2.1.10.7.2.1.4 Multi-Col 1.3.6.1.2.1.10.7.2.1.5 Late-Col 1.3.6.1.2.1.10.7.2.1.8 Excess-Col 1.3.6.1.2.1.10.7.2.1.9 Carri-Sen 1.3.6.1.2.1.10.7.2.1.11 SQETest-Err 1.3.6.1.2.1.10.7.2.1.6 Deferred-Tx 1.3.6.1.2.1.10.7.2.1.7 IntMacTx-Err 1.3.6.1.2.1.10.7.2.1.10 IntMacRx-Err 1.3.6.1.2.1.10.7.2.1.16 Symbol-Err 1.3.6.1.2.1.10.7.2.1.18 Runts 1.3.6.1.4.1.9.9.276.1.1.1.1.4 //CISCO-IF-EXTENSION-MIB Giants 1.3.6.1.4.1.9.9.276.1.1.1.1.5 //CISCO-IF-EXTENSION-MIB OutDiscards 1.3.6.1.2.1.2.2.1.19 //IF-MIB OutDiscards 1.3.6.1.4.1.9.9.276.1.1.1.1.11 //CISCO-IF-EXTENSION-MIB Xmit-Err 1.3.6.1.2.1.2.2.1.20 //IF-MIB // wanted! Rcv-Err 1.3.6.1.2.1.2.2.1.14 ????? //IF-MIB UnderSize ???
Archive for the ‘cisco’ Category
Snmp monitoring of errors on ethernet interfaces
3750/3560 interface policing/shaping/bandwidth limiting
I assume, that QoS is set up as it is dscribed in my previous .
All traffic is sorted to two different queues: iptv(dscp32) is put into queue1, other traffic is put into queue2. I want to police customers traffic into 20mbps, except iptv packets going towards the customer.
Ingress policing
Create policy map:
policy-map shape-20
class class-default
police 20M 400000 exceed-action dropAssign policy map to interface:
interface FastEthernet1/0/2 service-policy input shape-20
Egress policing
Unfortunately, policy-map containing police action cannot be attached to interface in egress direction. Egress queue2 is shaped to 20mbps:
interface FastEthernet1/0/2 srr-queue bandwidth shape 0 10 0 0
10 is bandwidth weight and is calculated this way: [interface speed]/[bw weight] = [policed speed]. 100mbps/5=20mbps.
There is another possibility to limit egress speed in the interface. It will limit all egress queues to 25% of interface speed:
interface FastEthernet1/0/2 srr-queue bandwidth limit 20 srr-queue bandwidth shape 0 0 0 0
CDP cluster. Управление свитчем по CDP, если через telnet/ssh не попасть
Switch#configure t
Switch(config)#cluster enable test
Switch(config)#do show cluster candidates
MAC Address Name Device Type PortIf FEC Hops SN PortIf FEC
0017.9509.bc80 call_center WS-C2960-48TT-L Gi0/2 1 0 Gi0/2
отсюда смотрим мак адрес
Switch(config)#cluster member 1 mac-address 0017.9509.bc80 password ПАРОЛЬ
Switch(config)#end
Switch#rcommand 1
call_center#
call_center#
call_center#
call_center#exit
И вот мы уже на удаленном свитче.
Выключение кластера:
Switch(config)#no cluster member 1
Switch(config)#no cluster enable
Switch(config)#
Switch#sh cluster
% Not a management cluster member
Switch#
multicast через nat на cisco router
В глобальном конфиге:
ip multicast-routing
ip nat inside source list 100 interface GigabitEthernet0/0 overload
access-list 100 permit ip 192.168.1.0 0.0.0.255 any
access-list 100 deny ip any any
На внешнем интерфейсе:
ip nat outside
ip pim dense-mode
На внутреннем интерфейсе:
ip pim sparse-mode
ip nat inside
ip pim sparse-mode
ip igmp helper-address
Стэк из 3750. Подключение к slave-члену стэка
Некоторые команды можно посмотреть только зайдя непосредственно на slave стэка.
Делается это такой командой:
37-vib#session 2
37-vib-2#
2 – номер устройства в стеке
Просмотр дропов на cisco
Для большинства свитчей: sh int summary
2950
#sh int g0/1 | i drop
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
2960
sh platform port-asic stats drop gigabitEthernet 0/1
3750, 3560
sh platform port-asic stats drop gigabitEthernet 1/0/1
sh int g0/1 | i drop
Статистика раскладывания пакетов по очередям порта
sh platform port-asic stats enqueue gigabitEthernet 1/0/№
ME-3400
sh platform port-asic stats drop gigabitEthernet 0/1
4900M
sh int g3/9 | i drop
3750/3560 qos sample config
Define global qos settings
Enable qos
mls qos
Map cos4, dscp32 packets to egress queue1(priority queue) threshold3(means full queue). cos4,dscp32 – IPTV traffic:
mls qos srr-queue output cos-map queue 1 threshold 3 4 mls qos srr-queue output dscp-map queue 1 threshold 3 32
Map all other traffic to egress queue2:
mls qos srr-queue output cos-map queue 2 threshold 3 0 1 2 3 5 6 7 mls qos srr-queue output dscp-map queue 2 threshold 3 0 1 2 3 4 5 6 7 mls qos srr-queue output dscp-map queue 2 threshold 3 8 9 10 11 12 13 14 15 mls qos srr-queue output dscp-map queue 2 threshold 3 16 17 18 19 20 21 22 23 mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31 mls qos srr-queue output dscp-map queue 2 threshold 3 33 34 35 36 37 38 39 mls qos srr-queue output dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47 mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55 mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
Configure queues
I am going to use queue set 1 for all interfaces. Allocate 20% of reserved buffer pool to queue1 and 80% to queue2, all the rest gets 0%. Reserved buffer pool is buffer memory that is persistently allocated to interface egress buffers. Queue1 does not need big buffer size because it is expedite and is serviced always first.
mls qos queue-set output 1 buffers 20 80 0 0
Now we define the size of reserved buffer pool. Reserved pool takes memory from common pool, remaining space in common pool can be borrowed by different interfaces. Since I am not planning to use queus 3 and 4, I shrink it’s reserved buffer pool to minimum. Thresholds expressed as a percentage of the queue’s allocated memory.
mls qos queue-set output 1 threshold 3 1 1 1 1 mls qos queue-set output 1 threshold 4 1 1 1 1
Actually these settings should not play any role because the buffer sizes for queues 3 and 4 are set to 0.
Define reserved buffer pool for queues 1 and 2. Queue 1 has 20% guarenteed(reserved) from the allocated memory. Queue 1 can borrow from common buffer pool up to 3200% of allocated memory. The same settings for queue 2.
mls qos queue-set output 1 threshold 1 1 1 20 3200 mls qos queue-set output 1 threshold 2 1 1 20 3200
Ingress queues can also be configured, but I am not sure it is needed.
Uplink interfaces configuration
Disable queue shaping(srr-queue bandwidth shape). Guarantee 255/(255+1+1) of bandwidth to queue2 and 1/100 per queues 3 and 4 each. Queue 1 weight is not taken in account because it is expedite queue(priority-queue out). Srr-queue bandwidth share is taken in consideration only when interface is oversubscribed, i.e. experiences a congestion.
interface g0/1 srr-queue bandwidth shape 0 0 0 0 srr-queue bandwidth share 1 255 1 1 priority-queue out mls qos trust queue-set 1 exit
Customer interfaces configuration
The same as uplink configuration, but we do not trust dscp/cos/precendence.
interface g0/2 srr-queue bandwidth shape 0 0 0 0 srr-queue bandwidth share 1 255 1 1 priority-queue out no mls qos trust queue-set 1 exit
Verify interface configurations and check interface counters:
sh mls qos interface g0/1 ?
Sources of inspiration:
http://blog.internetworkexpert.com/2008/06/26/quick-notes-on-the-3560-egress-queuing/
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_55_se/configuration/guide/swqos.html
me3400 настройка qos
Маркировка управляющего траффика с помощью DSCP. Управляющий траффик – пакеты отправляемые CPU свитча:
cpu traffic qos dscp 36
cpu traffic qos precedence 4
Создаем классы траффика. Управляющий траффик, который мы промаркирвоали ниже и iptv, которое приходит уже маркированное:
class-map match-all iptv
match ip dscp cs4
class-map match-all control-traffic
match ip dscp af42
Read More »
View more by category: unix/linux (60), cisco (40), Uncategorized (39), d-link (7), links (7), ZyXel (4), windows (3), mysql (2), Статейки (1), SQL (1). .
