> Удалил стыковочный vlan 9.
> Добавил интерфейс 1/0/24 на 2960 в основной vlan 101
> Дал интерфейсу 0/0 на 2911 адрес из этой сети.
> Пустил маршруты по новым адресам.
> Пока что все работает отлично.
> Наблюдаю.Периодически все же возникают проблемы с откликом.
Для проверки с компьютера запущен пинг до яндекса, и до некоторых узлов.
В конфигурации сети добавился еще один шлюз на микротик, к которому подключен ipsec/gre каналом один из офисов. На микротик выделен отдельный канал в интернет.
Но что же я вижу - как только начинаются проблемы с пингами яндекса, в то же время начинаются проблемы с пингом и в сеть через микротик.
Два разных маршрутизатора, два разных канала доступа, а тупят в одно и то же время.
Для проверки взял еще один компьютер, прописал на нем статические маршруты в интернет, в сеть через микротик, указав в качестве шлюза адреса маршрутизаторов (сейчас у узлов в сети в качестве шлюза стоит адрес центрального коммутатора cisco 2960).
И вот с этого компьютера пинги шикарные. Даже если в это время пинги с первого компа ужасают.
Логично предположить, что проблема в 2960.
Но по загрузке вроде бы должна справляться.
Куда можно посмотреть?
2960#sho ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is 192.168.101.254 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 192.168.101.254 (адрес шлюза на 2911)
10.0.0.0/24 is subnetted, 2 subnets
S 10.0.136.0 [1/0] via 192.168.5.5
S 10.0.146.0 [1/0] via 192.168.5.5
172.19.0.0/24 is subnetted, 3 subnets
S 172.19.2.0 [1/0] via 192.168.5.5
S 172.19.3.0 [1/0] via 192.168.5.5
S 172.19.13.0 [1/0] via 192.168.5.5
C 192.168.2.0/23 is directly connected, Vlan1
192.168.2.0/32 is subnetted, 1 subnets
L 192.168.2.1 is directly connected, Vlan1
192.168.4.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.4.0/24 is directly connected, Vlan4
L 192.168.4.1/32 is directly connected, Vlan4
192.168.5.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.5.0/24 is directly connected, Vlan5
L 192.168.5.1/32 is directly connected, Vlan5
C 192.168.6.0/23 is directly connected, Vlan6
192.168.6.0/32 is subnetted, 1 subnets
L 192.168.6.1 is directly connected, Vlan6
192.168.99.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.99.0/24 is directly connected, Vlan99
L 192.168.99.1/32 is directly connected, Vlan99
192.168.101.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.101.0/24 is directly connected, Vlan101
L 192.168.101.1/32 is directly connected, Vlan101
192.168.102.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.102.0/24 is directly connected, Vlan102
L 192.168.102.1/32 is directly connected, Vlan102
192.168.103.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.103.0/24 is directly connected, Vlan103
L 192.168.103.1/32 is directly connected, Vlan103
192.168.104.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.104.0/24 is directly connected, Vlan104
L 192.168.104.1/32 is directly connected, Vlan104
192.168.105.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.105.0/24 is directly connected, Vlan105
L 192.168.105.1/32 is directly connected, Vlan105
192.168.107.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.107.0/24 is directly connected, Vlan107
L 192.168.107.1/32 is directly connected, Vlan107
192.168.112.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.112.0/24 is directly connected, Vlan112
L 192.168.112.1/32 is directly connected, Vlan112
192.168.115.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.115.0/24 is directly connected, Vlan115
L 192.168.115.1/32 is directly connected, Vlan115
192.168.116.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.116.0/24 is directly connected, Vlan116
L 192.168.116.1/32 is directly connected, Vlan116
192.168.117.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.117.0/24 is directly connected, Vlan117
L 192.168.117.1/32 is directly connected, Vlan117
192.168.160.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.160.0/24 is directly connected, Vlan160
L 192.168.160.1/32 is directly connected, Vlan160
192.168.199.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.199.0/24 is directly connected, Vlan199
L 192.168.199.1/32 is directly connected, Vlan199
S 192.168.205.0/24 [1/0] via 192.168.101.253 (адрес шлюза на микротике)
2911#sho ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override
Gateway of last resort is xxx.xxx.xxx.xxx to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via xxx.xxx.xxx.xxx (адрес шлюза провайдера)
xxx.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C xxx.xxx.xxx.xxx/30 is directly connected, GigabitEthernet0/1
L xxx.xxx.xxx.xxx/32 is directly connected, GigabitEthernet0/1
S 192.168.2.0/23 [1/0] via 192.168.101.1
S 192.168.4.0/24 [1/0] via 192.168.101.1
S 192.168.5.0/24 [1/0] via 192.168.101.1
S 192.168.6.0/23 [1/0] via 192.168.101.1
S 192.168.8.0/24 [1/0] via 192.168.101.1
S 192.168.99.0/24 [1/0] via 192.168.101.1
S 192.168.100.0/24 [1/0] via 192.168.254.14
192.168.101.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.101.0/24 is directly connected, GigabitEthernet0/0
L 192.168.101.254/32 is directly connected, GigabitEthernet0/0
S 192.168.102.0/24 [1/0] via 192.168.101.1
S 192.168.103.0/24 [1/0] via 192.168.101.1
S 192.168.104.0/24 [1/0] via 192.168.101.1
S 192.168.105.0/24 [1/0] via 192.168.101.1
S 192.168.106.0/24 [1/0] via 192.168.254.14
S 192.168.107.0/24 [1/0] via 192.168.101.1
S 192.168.110.0/24 [1/0] via 192.168.101.1
S 192.168.112.0/24 [1/0] via 192.168.101.1
S 192.168.114.0/24 [1/0] via 192.168.101.1
S 192.168.115.0/24 [1/0] via 192.168.101.1
S 192.168.116.0/24 [1/0] via 192.168.101.1
S 192.168.117.0/24 [1/0] via 192.168.101.1
S 192.168.160.0/24 [1/0] via 192.168.101.1
S 192.168.166.0/24 [1/0] via 192.168.254.14
S 192.168.199.0/24 [1/0] via 192.168.101.1
S 192.168.203.0/24 [1/0] via 192.168.254.10
S 192.168.204.0/24 [1/0] via 192.168.254.18
192.168.254.0/24 is variably subnetted, 6 subnets, 2 masks
C 192.168.254.8/30 is directly connected, Tunnel2
L 192.168.254.9/32 is directly connected, Tunnel2
C 192.168.254.12/30 is directly connected, Tunnel3
L 192.168.254.13/32 is directly connected, Tunnel3
C 192.168.254.16/30 is directly connected, Tunnel5
L 192.168.254.17/32 is directly connected, Tunnel5
2960#sho proc cpu sort | e 0.00
CPU utilization for five seconds: 53%/20%; one minute: 55%; five minutes: 53%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
162 829429331 129985057 6380 14.22% 14.85% 14.56% 0 Hulc LED Process
121 30534574 141876017 215 1.08% 0.82% 0.71% 0 HLFM address lea
163 100141220 4915685 20371 1.01% 1.29% 1.30% 0 HL3U bkgrd proce
207 23008952 64982195 354 0.66% 0.62% 0.58% 0 IP Input
220 13709509 56239947 243 0.29% 0.30% 0.29% 0 Spanning Tree
131 14694490 5248878 2799 0.29% 0.28% 0.29% 0 hpm counter proc
94 7554480 238249853 31 0.23% 0.10% 0.09% 0 RedEarth Rx Mana
17 16709684 36240623 461 0.23% 0.34% 0.37% 0 ARP Input
93 5004501 238166893 21 0.11% 0.06% 0.05% 0 RedEarth Tx Mana
173 9411654 1047216 8987 0.05% 0.16% 0.17% 0 HQM Stack Proces
206 5370879 141875048 37 0.05% 0.06% 0.05% 0 IP ARP Retry Age
174 2598331 2094414 1240 0.05% 0.03% 0.05% 0 HRPC qos request
2960#sho proc cpu hist
555555555555555555555555555555555555555555555555555555566666
666665555566666555553333355555666665555555555333334444400000
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)
655555555556555656555656655655555565555555555555555555555555
079799350160998270898081187075669506887398928435835594365541
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 minute (last 60 minutes)
* = maximum CPU% # = average CPU%
696665443334343344444455445543443343344444444544555544343443543434555666
254519739880929914032210664888097909960031229483435594918069209780538003
100 *
90 *
80 *
70 * *
60 *###** * ** * **
50 #####** ******* * * *** ***** * * * ***#
40 #######*******************************************##***************###
30 ######################################################################
20 ######################################################################
10 ######################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
Вроде как загрузка по Hulс LED Cisco не считает проблемой - https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtg86211/?rf...
