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. 正文

MLS

2006年08月30日 3451点热度 0人点赞 0条评论

To determine the best path is the primary function of routing protocols, and this can be a
CPU-intensive process. Thus, there is a significant performance increase with the offload
of a portion of this function to switching hardware. This performance increase is the goal
of the MLS feature.
Two of the three major components of MLS are the MLS route processor (MLS-RP) and
the MLS switching engine (MLS-SE). The MLS-RP is the MLS-enabled router, which
performs the traditional function of routing between subnets/VLANs. The MLS-SE is a
MLS-enabled switch, which normally requires a router to route between subnets/VLANs.
However, with special hardware and software, MLS-SE can handle the rewrite of the
packet. When a packet transverses a routed interface, the change (rewrite) of non-data
portions of the packet occurs as the packet heads to the destination, hop by hop.
Confusion can arise here because a Layer 2 device appears to take on a Layer 3 task.
Actually, the switch only rewrites Layer 3 information and "switches" between
subnets/VLANs. The router is still responsible for standards-based route calculations and
best-path determination. You can avoid much of this confusion if you mentally keep the
routing and switching functions separate, especially when they are within the same
chassis (as with an internal MLS-RP). Think of MLS as a much more advanced form of
route cache, with a separation of the cache from the router on a switch. MLS requires
both the MLS-RP and the MLS-SE, along with respective hardware and software
minimums

本作品采用 知识共享署名 4.0 国际许可协议 进行许可
标签: Multilayer 多层交换
最后更新:2006年08月30日

纳米

http://linjing.io

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

文章评论

取消回复

纳米

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
    很方便的nginx在线配置生成网站 [转]路由器常规安全配置 路由器安全保护基本方法[转] 2012,我的这一年[归档] 让VS直接访问另一个VS [转]CISCO IOS ?下出现的命令帮助 修正了2010年以来文章的附件下载 NAT-WITH ACL OR ROUTE-MAP What Does the EIGRP DUAL-3-SIA Error Message Mean? 博客环境迁移
    链接表
    • 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