Re: 3750x ping and cpu usage

victor910 · ‎07-30-2020

HI,

I have a couple "problems"

first of all, someone explain to me how I have total 12% cpu usage, just interesting:

switch#show processes cpu sorted
CPU utilization for five seconds: 12%/0%; one minute: 13%; five minutes: 11%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
75 19872 3283 6053 3.67% 3.63% 2.97% 0 RedEarth Tx Mana
74 8910 5058 1761 1.59% 1.62% 1.36% 0 RedEarth I2C dri
165 471 214 2200 1.43% 0.59% 0.13% 1 SSH Process
119 4245 507 8372 0.79% 0.79% 0.66% 0 hpm counter proc
159 309 11981 25 0.15% 0.05% 0.02% 0 Hulc LED Process
170 827 120 6891 0.15% 0.15% 0.15% 0 HQM Stack Proces
1 0 7 0 0.00% 0.00% 0.00% 0 Chunk Manager

for 5 secs must be - 7.78%, ok 8%.

or we have this "smart" mathematic":

3.67 -> 4

1.59 -> 2

1.43 -> 2

0.79 -> 1

0.15 -> 1

but any way:

4+2+2+1+1+1 = 11% not 12%.

second question, why this process ALWAYS uses my CPU:

RedEarth Tx Mana

RedEarth I2C dri

how to fix this" problem"?

probable you say this "not affecting" on traffic, ok then my last and most important question:

I believe problem #3 coming from "problem #1 and #2.

question #3,

why I have undestable ping responce from this switch, device is pinging directly connected to the switch port with 1 gbit/s speed, rg45 cable.

response from switch:

Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time=179ms TTL=255
Reply from 10.10.0.254: bytes=32 time=202ms TTL=255
Reply from 10.10.0.254: bytes=32 time=93ms TTL=255
Reply from 10.10.0.254: bytes=32 time=171ms TTL=255
Reply from 10.10.0.254: bytes=32 time=25ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255
Reply from 10.10.0.254: bytes=32 time<1ms TTL=255

the device is Cisco 3750X

Same behaviour under IOS:

15.2.4E10

15.0.2.SE12

12.2.55.SE13

Config is very close to factory default, nothing special.

Cisco Guru you are welcome.

Leo Laohoo · ‎07-30-2020

RedEarth is associated to STP.
RedEarth is high, for example, if you've got ports that are flapping.

victor910 · ‎07-30-2020

thanks for the response,

any idea how to make less use CPU? maybe someone settings?

I had just this in my config:

spanning-tree mode rapid-pvst
spanning-tree extend system-id

Leo Laohoo · ‎07-30-2020

Well if you have ports that are flapping, that'll kick up STP.

victor910 · ‎07-30-2020

But i do not have any flapping in my “show logging” responce.

Leo Laohoo · ‎07-30-2020

Maybe link logging is disabled?

victor910 · ‎07-30-2020

@Leo Laohoo wrote:
Maybe link logging is disabled?

this enabled by default, I have logs about switch on ports interfaces from "booting period", but nothing after.

Joseph W. Doherty · ‎07-30-2020

The "missing" CPU might be bound up in "interrupt" CPU and/or other incorrectly summed up CPU usage. I.e. a possible bug, that could span various IOS implementations. Possibly even known, internally to Cisco, but also perhaps way, way down on a "to-be-fixed" list.

"probable you say this "not affecting" on traffic, ok then my last and most important question:"

The reason we'll often say that, in a case like yours, your CPU usage isn't a problem, is because, ideally, data plane processing is performed by dedicated ASICs, not the main CPU. I.e., so, in theory, CPU might even be running at 100%, with no impact to data traffic forwarding.

BTW, not withstanding this case, higher than normal/expected CPU, on a switch, though, can represent other issues, and/or be an issue for data traffic forwarding.

"why I have undestable ping responce from this switch, device is pinging directly connected to the switch port with 1 gbit/s speed, rg45 cable."

Ping responses, from any host, especially to switches and routers, can be highly variable, as it's a low-priority function on the host. Ping was designed more to determine a host is "alive", not as a true network latency performance metric.

To receive a much more accurate ping network latency measurement, from Cisco switches/routers, you'll want to enable a SLA responder on the device (if supported), and use a SLA ping.

victor910 · ‎07-30-2020

The "missing" CPU might be bound up in "interrupt" CPU and/or other incorrectly summed up CPU usage. I.e. a possible bug, that could span various IOS implementations. Possibly even known, internally to Cisco, but also perhaps way, way down on a "to-be-fixed" list.

my interrupt is zero:
CPU utilization for five seconds: 12%/0%; one minute: 13%; five minutes: 11%
wheres 12%/0% showed this.
------------

"probable you say this "not affecting" on traffic, ok then my last and most important question:"

The reason we'll often say that, in a case like yours, your CPU usage isn't a problem, is because, ideally, data plane processing is performed by dedicated ASICs, not the main CPU. I.e., so, in theory, CPU might even be running at 100%, with no impact to data traffic forwarding.

this just theory.
----------------
BTW, not withstanding this case, higher than normal/expected CPU, on a switch, though, can represent other issues, and/or be an issue for data traffic forwarding.

"why I have undestable ping responce from this switch, device is pinging directly connected to the switch port with 1 gbit/s speed, rg45 cable."

Ping responses, from any host, especially to switches and routers, can be highly variable, as it's a low-priority function on the host. Ping was designed more to determine a host is "alive", not as a true network latency performance metric.

To receive a much more accurate ping network latency measurement, from Cisco switches/routers, you'll want to enable a SLA responder on the device (if supported), and use a SLA ping.

First of all, you still not understand different between ping and latency, like and 99.999999% peoples at this world :).

Any cheap device provide correct ping response but for cisco we need something special, common Friend, this device definitely has a problem, ping response 200ms not under loading - its problem, end of the story, or you not agree and still will statement this is normal? just curious.

victor910 · ‎07-31-2020

dear cisco gurus :)))

so, someone helps me with my little problem ;)

Leo Laohoo · ‎07-31-2020

@victor910 wrote:

why I have undestable ping responce from this switch, device is pinging directly connected to the switch port with 1 gbit/s speed

This is just ONE PC, right? What about others? Are you seeing the same behaviour?

Post the complete output to the following commands:

sh version
sh log
sh proc cpu h

victor910 · ‎07-31-2020

switch#show version
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 12.2(55)SE13, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2018 by Cisco Systems, Inc.
Compiled Thu 06-Sep-18 23:42 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x02800000

ROM: Bootstrap program is C3750E boot loader
BOOTLDR: C3750E Boot Loader (C3750X-HBOOT-M) Version 12.2(58r)SE1, RELEASE SOFTWARE (fc1)

switch uptime is 1 day, 4 hours, 29 minutes
System returned to ROM by power-on
System restarted at 09:55:59 OmniTZ Fri Jul 31 2020
System image file is "flash:c3750e-universalk9-mz.122-55.SE13.bin"

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

License Level: ipservices
License Type: Permanent
Next reload license Level: ipservices

cisco WS-C3750X-24P (PowerPC405) processor (revision A0) with 262144K bytes of memory.
Processor board ID FDO1828Z29F
Last reset from power-on
1 Virtual Ethernet interface
1 FastEthernet interface
28 Gigabit Ethernet interfaces
2 Ten Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.

512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 34:62:88:A3:25:80
Motherboard assembly number : 73-12551-11
Motherboard serial number : FDO18281YSD
Model revision number : A0
Motherboard revision number : A0
Model number : WS-C3750X-24P-E
Daughterboard assembly number : 800-32727-03
Daughterboard serial number : FDO182813WC
System serial number : FDO1828Z29F
Top Assembly Part Number : 800-31325-09
Top Assembly Revision Number : C0
Version ID : V06
CLEI Code Number : CMMPP00DRA
Hardware Board Revision Number : 0x05

Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 30 WS-C3750X-24P 12.2(55)SE13 C3750E-UNIVERSALK9-M

Configuration register is 0xF

switch#

victor910 · ‎07-31-2020

switch#show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: level debugging, 63 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 63 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 65 message lines logged

Log Buffer (4096 bytes):
D: Interface GigabitEthernet1/0/9, changed state to administratively down
*Mar 1 00:00:59.936: %LINK-5-CHANGED: Interface GigabitEthernet1/0/10, changed state to administratively down
*Mar 1 00:00:59.936: %LINK-5-CHANGED: Interface GigabitEthernet1/0/11, changed state to administratively down
*Mar 1 00:00:59.936: %LINK-5-CHANGED: Interface GigabitEthernet1/0/12, changed state to administratively down
*Mar 1 00:00:59.936: %LINK-5-CHANGED: Interface GigabitEthernet1/0/13, changed state to administratively down
*Mar 1 00:00:59.936: %LINK-5-CHANGED: Interface GigabitEthernet1/0/14, changed state to administratively down
*Mar 1 00:00:59.936: %LINK-5-CHANGED: Interface GigabitEthernet1/0/15, changed state to administratively down
*Mar 1 00:00:59.944: %LINK-5-CHANGED: Interface GigabitEthernet1/0/16, changed state to administratively down
*Mar 1 00:00:59.944: %LINK-5-CHANGED: Interface GigabitEthernet1/0/17, changed state to administratively down
*Mar 1 00:00:59.944: %LINK-5-CHANGED: Interface GigabitEthernet1/0/18, changed state to administratively down
*Mar 1 00:00:59.944: %LINK-5-CHANGED: Interface GigabitEthernet1/0/22, changed state to administratively down
*Mar 1 00:00:59.944: %LINK-5-CHANGED: Interface GigabitEthernet1/0/24, changed state to administratively down
*Mar 1 00:00:59.944: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down
*Mar 1 00:01:01.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up
*Mar 1 00:01:02.075: %USB_CONSOLE-6-MEDIA_RJ45: Console media-type is RJ45.
*Mar 1 00:01:02.721: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
*Mar 1 00:01:03.174: %PLATFORM-6-FRULINK_INSERTED: FRULink 1G module inserted in Switch 1.
*Mar 1 00:01:04.096: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
*Mar 1 00:01:04.096: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
*Mar 1 00:01:04.130: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up
*Mar 1 00:01:04.726: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/21, changed state to up
*Mar 1 00:01:04.919: %PLATFORM_ENV-6-FRU_PS_OIR: FRU Power Supply 1 inserted
*Mar 1 00:01:05.153: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
*Mar 1 00:01:05.153: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
*Mar 1 00:01:05.153: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to up
*Mar 1 00:01:05.732: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/21, changed state to up
*Mar 1 00:01:30.469: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Jul 31 06:39:48.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/21, changed state to down
Jul 31 06:39:49.238: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/21, changed state to down
Jul 31 07:29:38.159: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/21, changed state to up
Jul 31 07:29:39.166: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/21, changed state to up
Jul 31 07:43:10.913: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 10.10.0.132.
Jul 31 12:53:48.121: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to down
Jul 31 12:53:49.127: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down
Jul 31 12:53:52.097: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up
Jul 31 12:53:54.454: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down
Jul 31 12:54:04.805: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up
Jul 31 12:54:05.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to up
Jul 31 13:13:57.543: SSH2 0: no matching cipher found: client chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,
Jul 31 13:35:28.456: %SYS-5-CONFIG_I: Configured from console by root on vty0 (10.10.0.2)

victor910 · ‎07-31-2020

switch#show processes cpu history

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

2222222222222222222221222225122221212212112222211222222212
6312072133812213021236133235844007671177981352198613137023
100
90
80
70
60 *
50 *
40 *
30 * * * * * * * * *
20 ***************************#**************************** *
10 ##########################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%

5323543343343368344633333437
5897526515386614717336689868
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%

victor910 · ‎07-31-2020

same ping "problem" when pinging from different ports to another pc