Cloud Native应用交付

  • 首页
  • 关于本站
  • 个人介绍
  • Downloads
  • Repo
    • Github
    • Container
  • F5
    • F5 Python SDK
    • F5-container
    • F5-LBaaS
  • 社交
    • 联系我
    • 微信/微博
    • 公众号
    • 打赏赞助
行至水穷处 坐看云起时
Cloud Native Application Services: cnadn.net
  1. 首页
  2. F5技术
  3. 正文

[3DNS],通过snmp探测到的CPU使用 真的正确吗?

2008年06月28日 9624点热度 0人点赞 0条评论

正如我们之前理解的一样,看F5的CPU是一件麻烦的事情。SNMP获取的CPU值依然只是从UC-Davis 这个标准的类unix snmp agent下获得的。这就和通过top看CPU一样并不准确。在3DNS,可以通过cpu bigip这个命令来查看较为准确的cpu使用

 

To measure CPU utilization on the BIG-IP system, you can use the cpu bigip command. Traditional Unix utilities such as top, vmstat, and SNMP monitoring do not report all of the information necessary to measure CPU utilization on the BIG-IP system. As a result, you should not use the traditional Unix utilities for measuring CPU utilization on the BIG-IP system.

The cpu bigip command reports CPU utilization based on BIG-IP-specific instrumentation in the kernel. The kernel uses the high-resolution timer to measure the number of CPU cycles that are spent in each of the major code sections, and then the kernel averages the information over time.

The major code sections are as follows:

  • Idle (Idle)
  • Unix user space (Unix)
  • BIG-IP processing (BIGIP)
  • Network processing (NET)
  • Network device drivers (DV_NET)
  • Interrupts (INT)

 

cpu bigip

BIG-IP will display information similar to the following example:

             Idle   Unix   BIGIP   NET   DV_NET   INT
Current:      100%     0%     0%     0%     0%     0%
10-Sec Avg:   100%     0%     0%     0%     0%     0%
1-Min Avg:     99%     1%     0%     0%     0%     0%
5-Min Avg:     99%     0%     0%     0%     0%     0%
15-Min Avg:    94%     0%     0%     0%     0%     0%
Max BIGIP:      0%     0%     0%     0%     0%     0%
Max NET:        1%     1%     0%     3%     0%    26%
Max DV_NET:     0%     0%     0%     0%     0%     0%

 

目前,通过SNMP是无法获得cpu bigip输出的值。

如果说非要从snmp探测CPU使用,也只能说使用.1.3.6.1.4.1.2021.11这个OID相对接近些而已。

 

 

------------------
For snmp monitoring for CPU for 3dns, under /usr/local/share/snmp/mibs directory, you can use the UCD-SNMP-MIB.txt
This is a MIB-II (RFC 1213) that contains specific management information for the UC-Davis SNMP agent.

 

which is the closest to having cpu utilization. Using UCD SNMP for monitoring CPU status via SNMP.
This mib you can use is.
.1.3.6.1.4.1.2021.11

 Manual Chapter: 3-DNS Reference Guide v4.5.10: Probing and Metrics Collection
https://support.f5.com/kb/en-us/products/3-dns/manuals/product/3dns4_5_10ref/3dns_probing.html

However,  customers will need to keep in mind of  SOL4278: Measuring CPU utilization on BIG-IP and 3-DNS
https://support.f5.com/kb/en-us/solutions/public/4000/200/sol4278.html

To measure CPU utilization on the BIG-IP system, you can use the cpu bigip command. Traditional Unix utilities such as top, vmstat, and SNMP monitoring do not report all of the information necessary to measure CPU utilization on the BIG-IP system. As a result, you should not use the traditional Unix utilities for measuring CPU utilization on the BIG-IP system.

The cpu bigip command reports CPU utilization based on BIG-IP-specific instrumentation in the kernel. The kernel uses the high-resolution timer to measure the number of CPU cycles that are spent in each of the major code sections, and then the kernel averages the information over time.

As result, the usage of the uc

davis MIB results are not valid

bigip:/usr/local/share/snmp/mibs# snmpwalk -cC -v1 -cpublic localhost .1.3.6.1.4.1.2021.11
enterprises.ucdavis.systemStats.ssIndex.0 = 1
enterprises.ucdavis.systemStats.ssErrorName.0 = systemStats
enterprises.ucdavis.systemStats.ssSwapIn.0 = 0
enterprises.ucdavis.systemStats.ssSwapOut.0 = 0
enterprises.ucdavis.systemStats.ssSysInterrupts.0 = 310
enterprises.ucdavis.systemStats.ssSysContext.0 = 29
enterprises.ucdavis.systemStats.ssCpuUser.0 = 0
enterprises.ucdavis.systemStats.ssCpuSystem.0 = 0
enterprises.ucdavis.systemStats.ssCpuIdle.0 = 99
enterprises.ucdavis.systemStats.ssCpuRawUser.0 = Counter32: 132510
enterprises.ucdavis.systemStats.ssCpuRawNice.0 = Counter32: 0
enterprises.ucdavis.systemStats.ssCpuRawSystem.0 = Counter32: 48638
enterprises.ucdavis.systemStats.ssCpuRawIdle.0 = Counter32: 24977579
enterprises.ucdavis.systemStats.ssCpuRawKernel.0 = Counter32: 41344
enterprises.ucdavis.systemStats.ssCpuRawInterrupt.0 = Counter32: 7294

Is it possible to gather the information provided with cpu bigip trough snmp?
From F5 development, It's not possible to get from SNMP the information that "cpu bigip" reports, even in a raw/unprocessed state. Since RFEs for 4.x are not being accepted, this will not change.

Therefore, accurate SNMP monitoring of the 3dns bigip is not viable.

 

[root@test:LICENSE INOPERATIVE] config # snmpwalk -C c -v 1 -c public localhost .1.3.6.1.4.1.2021.11

UCD-SNMP-MIB::ssIndex.0 = INTEGER: 1

UCD-SNMP-MIB::ssErrorName.0 = STRING: systemStats

UCD-SNMP-MIB::ssSwapIn.0 = INTEGER: 0

UCD-SNMP-MIB::ssSwapOut.0 = INTEGER: 0

UCD-SNMP-MIB::ssIOSent.0 = INTEGER: 264

UCD-SNMP-MIB::ssIOReceive.0 = INTEGER: 9

UCD-SNMP-MIB::ssSysInterrupts.0 = INTEGER: 2516

UCD-SNMP-MIB::ssSysContext.0 = INTEGER: 4682

UCD-SNMP-MIB::ssCpuUser.0 = INTEGER: 38

UCD-SNMP-MIB::ssCpuSystem.0 = INTEGER: 38

UCD-SNMP-MIB::ssCpuIdle.0 = INTEGER: 23

UCD-SNMP-MIB::ssCpuRawUser.0 = Counter32: 15403

UCD-SNMP-MIB::ssCpuRawNice.0 = Counter32: 0

UCD-SNMP-MIB::ssCpuRawSystem.0 = Counter32: 15317

UCD-SNMP-MIB::ssCpuRawIdle.0 = Counter32: 9177

UCD-SNMP-MIB::ssRawInterrupts.0 = Counter32: 1003716

UCD-SNMP-MIB::ssRawContexts.0 = Counter32: 1867939

[root@test:LICENSE INOPERATIVE] config # top

 

相关文章

  • 密码保护:F5OS tenant部署后的容器情况、网络接口情况
  • 密码保护:F5OS tenant镜像实例化后信息
  • 密码保护:F5OS docker-compose.yml
  • 密码保护:F5OS 底层容器、网络及k8s状态
  • AI Gateway PII test page - internal only
本作品采用 知识共享署名-非商业性使用 4.0 国际许可协议 进行许可
标签: 3dns bigip cpu snmp
最后更新:2008年06月28日

纳米

linjing.io

打赏 点赞
< 上一篇
下一篇 >

文章评论

razz evil exclaim smile redface biggrin eek confused idea lol mad twisted rolleyes wink cool arrow neutral cry mrgreen drooling persevering
取消回复

这个站点使用 Akismet 来减少垃圾评论。了解你的评论数据如何被处理。

页面AI聊天助手

纳米

linjing.io

☁️迈向Cloud Native ADC ☁️

认证获得:
TOGAF: ID 152743
Kubernetes: CKA #664
Microsoft: MCSE MCDBA
Cisco: CCNP
Juniper: JNCIS
F5:
F5 Certified Solution Expert, Security
F5 Certified Technology Specialist, LTM/GTM/APM/ASM
F5 Certified BIG-IP Administrator
  • 点击查看本博技术要素列表
  • 归档
    分类
    • AI
    • Automation
    • Avi Networks
    • Cisco ACI
    • CISCO资源
    • F5 with ELK
    • F5-Tech tips
    • F5技术
    • Juniper
    • Linux
    • NGINX
    • SDN
    • ServiceMesh
    • WEB编程
    • WINDOWS相关
    • 业界文章
    • 交换机技术
    • 化云为雨/Openstack
    • 协议原理
    • 容器/k8s
    • 我的工作
    • 我的生活
    • 网站技术
    • 路由器技术
    • 项目案例
    标签聚合
    envoy gtm openstack network bigip F5 docker neutron nginx api flannel istio irule k8s DNS
    最近评论
    汤姆 发布于 8 个月前(09月10日) 嗨,楼主,里面的json怎么下载啊,怎么收费啊?
    汤姆 发布于 8 个月前(09月09日) 大佬,kib的页面可以分享下吗?谢谢
    zhangsha 发布于 1 年前(05月12日) 资料发给我下,谢谢纳米同志!!!!lyx895@qq.com
    李成才 发布于 1 年前(01月02日) 麻烦了,谢谢大佬
    纳米 发布于 1 年前(01月02日) 你好。是的,因为以前下载系统插件在一次升级后将所有的下载生成信息全弄丢了。所以不少文件无法下载。DN...
    浏览次数
    • Downloads - 183,773 views
    • 联系我 - 118,966 views
    • 迄今为止最全最深入的BIGIP-DNS/GTM原理及培训资料 - 116,512 views
    • Github - 103,661 views
    • F5常见log日志解释 - 79,774 views
    • 从传统ADC迈向CLOUD NATIVE ADC - 下载 - 74,625 views
    • Sniffer Pro 4 70 530抓包软件 中文版+视频教程 - 74,320 views
    • 迄今为止最全最深入的BIGIP-DNS/GTM原理及培训资料 - 67,770 views
    • 关于本站 - 60,911 views
    • 这篇文档您是否感兴趣 - 55,495 views
    链接表
    • F5SE创新
    • Jimmy Song‘s Blog
    • SDNlab
    • Service Mesh社区
    • 三斗室
    • 个人profile
    • 云原生社区

    COPYRIGHT © 2023 Cloud Native 应用交付. ALL RIGHTS RESERVED.

    Theme Kratos Made By Seaton Jiang

    京ICP备14048088号-1

    京公网安备 11010502041506号