Cloud Native应用交付
  • 首页
  • 关于本站
  • 个人介绍
  • Downloads
  • Repo
    • Github
    • Container
  • F5
    • F5 Python SDK
    • F5-container
    • F5-LBaaS
  • 社交
    • 联系我
    • 微信/微博
    • 公众号
    • 打赏赞助
行至水穷处 坐看云起时
☁️We are in new App Mesh era: imesh.club ☁️
  1. 首页
  2. 路由器技术
  3. 正文

图解show traffic-shape输出

2006年09月28日 7189点热度 0人点赞 1条评论

这是frame-relay traffic-shapping的show traffic-shape命令输出:

 

Explanation:
To understand the concepts of traffic shaping, it is important to have a firm grasp of the
various traffic parameters in the Frame Relay network. In particular, you should know that
some (such as committed information rate [CIR] and excessive burst [Be]) are commonly
used but misunderstood.
CIR (Committed Information Rate) - The average rate at which you want to transmit. This is
generally not the same as the CIR provided by the telco. This is the rate at which you want to
send in periods of noncongestion.
Bc (Committed Burst) - The amount of data to send in each Tc interval.
Be (Excessive Burst) - The amount of excess data allowed to be sent during the first interval
once credit is built up. Transmission credit is built up during periods of nontransmission. The
credit is the burst size. Full credit is typically CIR / 8.
Tc (Committed Rate Measurement Interval) - The Bc / CIR time interval. The time interval
shouldn’t exceed 125 ms (almost always 125 ms).
MinCIR (Minimum CIR) - The minimum amount of data to send during periods of
congestion. This is usually what you get from the telco.
MinCIR - defaults to one-half of CIR.
PIR (Peak Information Rate) - The highest possible rate of transmission on any given
interface.
MIR (Minimum Information Rate) - The slowest rate of transmission on any given
interface.
Interval - Bc / CIR. The maximum is 125 ms, or 1/8 second.
Byte Increment - Bc / 8. This value must be greater than 125.
Limit - Byte Increment + Be / 8 (in bytes).
本作品采用 知识共享署名 4.0 国际许可协议 进行许可
标签: Frame-relay
最后更新:2006年09月28日

纳米

http://linjing.io

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

文章评论

  • 蓝猫

    路过.....

    2006年09月29日
    回复
  • 取消回复

    纳米

    http://linjing.io

    ☁️迈向Cloud Native ADC ☁️

    认证获得:
    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
  • 点击查看本博技术要素列表
  • 分类目录
    • Avi Networks (3)
    • Cisco ACI (1)
    • CISCO资源 (21)
    • F5 with ELK (8)
    • F5-Tech tips (38)
    • F5技术 (203)
    • Juniper (4)
    • Linux (7)
    • Nginx (18)
    • SDN (4)
    • ServiceMesh (19)
    • WEB编程 (8)
    • WINDOWS相关 (7)
    • 业界文章 (18)
    • 交换机技术 (20)
    • 化云为雨/Openstack (35)
    • 协议原理 (52)
    • 容器/k8s (64)
    • 我的工作 (19)
    • 我的生活 (70)
    • 网站技术 (19)
    • 路由器技术 (80)
    • 项目案例 (28)
    文章归档
    标签聚合
    F5 k8s openstack nginx istio DNS envoy gtm docker network flannel api irule bigip neutron cc kubernetes ELK vxlan BGP dhcp VPN IPSec lbaas ingress ingress controller nginx plus sidecar IPSec VPN NAT sql
    最新 热点 随机
    最新 热点 随机
    Say hello for 2021 二进制flannel部署,非cni网络模式下与k8s CIS结合方案 又是一年国庆 Service Account Token Volume Projection Istio ingressgateway 静态TLS证书加载与SDS发现方式配置区别 Istio里Gateway的port定义与实际ingressgateway的listener端口关系及规则 Helm 3 部署NGINX Ingress Controller 应用交付老兵眼中的Envoy, 云原生时代下的思考 Istio sidecar iptables以及流量控制分析 Istio 熔断策略及envoy配置
    Say hello for 2021
    [flash]我没有车我没有房 Helm 3 部署NGINX Ingress Controller 博客两年咯~~~~~~~~~~~~~~~~ Top 10 Cloud Computing Service Provider 转BGP知识总结 【原创】用CISCO VPN-Client4.01连接扩展验证-VPN-SERVER配置 understand dhcp relay (IOS12.4) F5上取URI各个部分 [原创]BSCI第五章实验,检验OSPF末节区域/绝对末节区域 BGP 属性优先级
    链接表
    • Jimmy Song‘s Blog
    • SDNap
    • SDNlab
    • SDN论坛
    • Service Mesh社区
    • 三斗室
    • 个人profile

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

    THEME KRATOS MADE BY VTROIS

    京ICP备14048088号-1

    京公网安备 11010502041506号

    [ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin