MXP Optics Technical GuideThe MXP ports on Arista leaf and spine switches can run as standards based 10Gb, 40Gb or 100Gb Ethernet, and simply require the correct fiber cables to enable multi-vendor interoperability. This technical guide is intended to provide accurate information for cabling triple-speed MXP ports with MTP and MPO cables for use with the Arista 7500E and 7280E (10GbE, 40GbE and 100GbE ports) and Arista 7050X (10GbE and 40GbE ports). MTP and MPO cables are widely available and this guide provides the information needed to specify cables to connect to the MXP interface. Arista customers should provide this document to their cabling vendors to get cables for their specific needs.Arista Portfolio With MXP PortsArista offers a portfolio of leaf and spine switches with MXP ports for high-density applications. Arista platforms with MXP ports range from the flagship 7500E spine switch series to ultra deep buffer top of rack 7280E and the high performance 7050X top of rack switches. The MXP ports offer flexibility to customers with investment protection when migrating from 10G to 40G and 100G speeds while maintaining low cost/bit and high reliability.Arista 7500EThe Arista 7500E Series deliver line rate non-blocking switching that enables faster and simpler network designs. The 7500E Series offers two choices for the datacenter a 4-slot 7504 and the 8-slot 7508. The 7500E Series supports a range of interface speeds from 100Mbps up to 100Gbps Ethernet in a single system, ensuring broad choices without limiting system performance when scaling from 10Gb to 100Gb Ethernet.The 7508E is a 11RU chassis with a 30Tbps fabric that supports up to 8 line cards and provides 1,152 – 10Gb ports, 288 – 40Gb ports, or 96 – 100Gb Ethernet ports in a single system - unparalleled density and performance in the industry.The Arista 7504E provides room for 4 line cards in a compact 7RU chassis that delivers 15Tbps of bandwidth allowing up to 576 -10Gb ports, 144 – 40Gb ports, and a massive 48 – 100Gb Ethernet ports.A choice of high-density wire-speed 10GbE, 40GbE and 100GbE line cards is fully supported with the ability to mix and match any combination of modules. The 40GbE and 100GbE modules enable up to 144x10G ports per line card. Each 40G interface can be used as either a single 40G port or quad 10G Ethernet ports. The 100G MXP interfaces can be a single port of 100Gb, three ports of 40Gb or 12 ports of 10Gb Ethernet.Figure 1: 7504E and 7508E with up to 1,152 10G portsArista 7280EThe Arista 7280E Series are purpose-built 10/40/100GbE ultra deep buffer fixed configuration systems built for the highest performance environments, where wire speed L2 and L3 forwarding are combined with advanced features for network virtualization, open monitoring and network analysis, resiliency and architectural flexibility.The 7280E Series are available in three models each with 48 SFP+ ports for 1/10GbE and choice of 40GbE and 100GbE uplinks. The 7280SE-72 has two 100GbE uplinks through the use of Arista MXP interfaces and embedded optics. Each MXP port enables twelve 10GbE, three 40GbE or one 100GbE for a wide choice of cost effective connections. The 7280SE-64 has four QSFP+ uplink portsthat allow a choice of four 40GbE or up to 16 additional 10GbE ports with a range of transceivers or cables. The 7280SE-68 hastwo 100GbE QSFP uplinks that allow the use of both 100GbE and 40GbE optics for the widest range of both short and long reach connection optics.Arista 7050XThe Arista 7050X Series are purpose-built 10/40GbE switches with wire speed layer 2/3/4 performance combined with low latency and advanced features for software defined cloud networking.• The 7050SX-72 and 7050SX-96 provide a 1RU system with 48 10GbE SFP+ ports and 2 or 4 MXP ports that each support 3x40GbE or 12x10GbE.• The 7050TX-72 and 7050TX-96 provide a 1RU system with 48 10GBASE-T ports and 2 or 4 MXP ports that each support 3x40GbE or 12x10GbE.Deploying an Optical Cabling Infrastructure in the Data Center for 40G and 100GRecommended cabling infrastructure deployments in the data center are based upon guidance found in TIA-942, “Telecommunications Infrastructure Standard for Data Centers.” Utilizing a distributed star topology in a structured cabling implementation provides the most flexible and manageable infrastructure. Many data center deployments today utilize the reduced topology described in TIA-942, where the Horizontal Distribution Areas (HDAs) shown are collapsed to the Main Distribution Area (MDA). In this collapsed architecture, the cabling is installed between the MDA and the Equipment Distribution Areas (Figure 2).Figure 2: TIA 942 ArchitectureFor optimized performance in meeting data center requirements, the topology of the cabling infrastructure should not be selected alone; infrastructure topology and product solutions must be considered in unison.Cabling deployed in the data center today to support 10GbE must be selected to support data rate applications of the future, such as 40Gb and 100Gb Ethernet. To do this, OM3 or OM4 multi-mode fiber is a must as the legacy OM1 and OM2 specifications do not support either 40GbE or 100GbE. In addition to being the only multimode fibers included in the 40G and 100G Ethernet standard, OM3 and OM4 fibers provide the highest performance as well as the extended reach often required for structured cabling installations in the data center.In addition to the performance requirements the choice in physical connectivity is also important. Because parallel optics technology requires data transmission across multiple fibers simultaneously, a multi-fiber (or array) connector is required. Utilizing MPO-based connectivity in today’s installations for either 10G or 40G Ethernet provides the means to migrate to this multi-fiber parallel optic interface when needed.Factory-terminated MPO solutions allow connectivity to be achieved through a simple plug-and-play system. To meet the needs of today’s serial Ethernet applications, MPO- terminated backbone/horizontal cabling is simply installed into pre-terminated modules, panels or harnesses (Figure 3).Figure 3: Pre-terminated Solutions (courtesy of Corning Cable Systems)Cabling Arista MXP Ports with MTP CablesTraditional optical-based Ethernet physical media (for speeds below 10Gb) required a duplex fiber scheme and required onlytwo fibers for transmit and receive. The IEEE “SR” specifications for 40Gbps and higher multimode cabling uses parallel optics. By combining multiple channels, each running at 10Gbps or 25Gbps the higher data rates are achieved. This parallel transmission approach requires the use of parallel fiber cables for both structured and non-structured systems. Structured cabling systems use MTP-12 and MTP-24 as standard cabling options. The 40GBASE-SR4 and 100GBASE-SR4 specifications require 4 pairs (8 fibers) in a 12-fiber cable, and the 100GBASE-SR10 standard requires 10 pairs (20 fibers) in a 24-fiber cable.Figure 4: MTP-12 and MTP-24 Connectors (courtesy of Complete Connect)As the 40GbE SR4 specification only uses 8 of the 12 pins in the MTP-12 connector 4 are left unused (or not present). This need for just 8 fibers out of 12 allows an MTP-24 to be used to transport three 40GbE links each utilizing 8 fibers. This is used in structured cabling systems to optimize the trunk utilization between cabling distribution points.Each 40GbE connection is presented to the active equipment as an MTP-12 connector but with only 8f present, which maximizes the channel capacity.The Arista MXP ports provide an MTP-24 port, which can be operated in one of many modes: 1 port of 100GbE, 3 ports of 40GbE or 12 ports of 10GbE and combinations of 10GbE and 40GbE. Each mode uses the same MTP-24 port, and a series of breakout cables is used to adapt this to the correct number of terminations.For example, a 24 fiber MTP to 3x 8-fiber MTP-12 can be used to provide 3 40GbE ports. Figure 5 below shows an example of the cable.MXP in 100GbE Mode - MTP-24 to MTP-24Both the 7500E and 7280E support 100GbE mode with Arista MXP . Operating the MXP port in 100GbE mode requires an MTP-24 to MTP-24 cable (for a point to point or cross-over connection). The cables use 20 of the 24 fibers to carry 100GbE across 10 send and 10 receive channels. When connecting two 100GbE MXP ports, the TX lanes must be crossed with the RX lanes, as shown in the table below.MXP in 40GbE Mode - MTP-24 to 3x MTP-12All Arista MXP ports support a 40GbE mode. Operating the MXP port in 40GbE mode requires an MTP breakout cable that provides a split into three individual MTP-12 ends. The cable is used to adapt the MXP port into three 40GbE interfaces as shown in figure 7. This breaks out the MXP port into three MTP-12 ends each compatible with standards based 40GBASE-SR4 ports over OM3 or OM4 fiber up to 100m or 150m.Table 3 below shows the pin-outs required. Following these pin-outs will guarantee standards based compatibility with existing 40GSR4 optics. In point to point scenarios all plugs should be unpinned for connecting to the active ports.Figure 5: 24-fiber MTP to 3x 8-fiber MTP (image courtesy of Leviton Network Solutions)Figure 6: MTP-24 pin-outMXP in 10GbE Mode - MTP-24 to 12X LCAll the Arista switches with embedded MXP support operation in 10GbE mode. To operate as 12x 10GbE a different breakout cable is used to adapt the MTP-24 port to 12x pairs of LC connectors. An MTP-24 to 12xLC cable is used as shown below in figure 8. This cable presents the Arista MXP port as 12 ports of standard LC connectors for using with 10GBASE-SR or 10GBASE-SRL optics over multimode OM3/OM4 cable. The MTP-24 end should be unpinned to connect to the Arista switch MXP ports.Figure 7: MTP-24 to 3x MTP-12 array cableFigure 8: MTP-24 to 12x LC break out cableSanta Clara—Corporate Headquarters 5453 Great America Parkway, Santa Clara, CA 95054Phone: +1-408-547-5500 Fax: +1-408-538-8920 Email:***************Copyright © 2016 Arista Networks, Inc. All rights reserved. CloudVision, and EOS are registered trademarks and Arista Networks is a trademark of Arista Networks, Inc. All other company names are trademarks of their respective holders. Information in this document is subject to change without notice. Certain features may not yet be available. Arista Networks, Inc. assumes no responsibility for any errors that may appear in this document. MM/YYIreland—International Headquarters 3130 Atlantic AvenueWestpark Business Campus Shannon, Co. Clare IrelandVancouver—R&D Office9200 Glenlyon Pkwy, Unit 300 Burnaby, British Columbia Canada V5J 5J8San Francisco—R&D and Sales Office 1390 Market Street, Suite 800 San Francisco, CA 94102India—R&D OfficeGlobal Tech Park, Tower A & B, 11th Floor Marathahalli Outer Ring RoadDevarabeesanahalli Village, Varthur Hobli Bangalore, India 560103Singapore—APAC Administrative Office 9 Temasek Boulevard #29-01, Suntec Tower Two Singapore 038989Nashua—R&D Office 10 Tara Boulevard Nashua, NH 03062SummaryMXP ports enable high density and flexible connectivity options. Each of the MXP modes requires the use of the correct breakout cable to adapt the MTP-24 interface to either 100GbE, 40GbE or 10GbE presentation. The cable specifications shown in thisdocument provide the information on how to identify the correct cable types. In addition cables that are pre-defined for usage with Arista MXP in each of the modes described are available directly from Arista Networks in both 3m and 5m lengths.。
世界五大唱片公司一、华纳20世纪全球五大唱片集团之一，隶属于拥有好莱坞华纳兄弟(Warner Brother)影片公司，时代杂志，财富杂志、CNN有线电视新闻网等传媒巨子的时代华纳(Time Warner)集团Warner Bros公司1930年因收购了Brunswick唱片公司而顺利进军唱片业.随后又分别于1968年和1970年兼并了Atlantic(大西洋)和Elektra Nonesuch两家唱片公司,并成立了华纳唱片集团(简称WEA)。
近年来，Wea先后将法国Erato公司，德国Teldec公司，芬兰Finlandia公司收归帐下。
2000年随时代华纳被美国在线(AOL)出资1600亿美元合并，并随即又出资200亿美元与英国EMI唱片公司合并，组成了全世界规模最大的唱片集团。
在古典音乐领域，Wea被称为Warner Classics，旗下拥有Erato 、Teldec、Elektra Nonesuch、Finlandia等多家规模不大但实力强劲的唱片公司，是不容忽视的一支力量。
在流行音乐领域Wea 被称为Warner Music，多年来以Warner Brother和Wea作为商标发行唱片，旗下拥有麦当娜、恩雅、All-4-One、Peter Poul & Mary、R.E.M、The Smith、Green Day、Jewel、Cher、Prince 等众多流行巨星。
是世界唱片业重要的组成部分。
我国台湾的UFO(飞碟唱片)，大陆的麦田音乐制作公司和普莱音乐也在Wea旗下。
二环球20世纪全球最大的唱片(音像制品制作，出版，发行)集团，1972年由德国Polydor International (德国DG唱片公司1941年以后的国际业务名称)与荷兰Phonogram(荷兰Philips唱片公司当时的名称)联合组建，从此Polygram便开始了她传奇的发展史.在1961年, Polygram通过Philips将美国Mercury(水星)唱片公司收归帐下。
Enterprise Development专业品质权威Analysis Report企业发展分析报告爱布（上海）人工智能科技有限公司免责声明:本报告通过对该企业公开数据进行分析生成，并不完全代表我方对该企业的意见，如有错误请及时联系;本报告出于对企业发展研究目的产生，仅供参考，在任何情况下，使用本报告所引起的一切后果，我方不承担任何责任:本报告不得用于一切商业用途，如需引用或合作，请与我方联系:爱布（上海）人工智能科技有限公司1企业发展分析结果1.1 企业发展指数得分企业发展指数得分爱布（上海）人工智能科技有限公司综合得分说明：企业发展指数根据企业规模、企业创新、企业风险、企业活力四个维度对企业发展情况进行评价。
该企业的综合评价得分需要您得到该公司授权后，我们将协助您分析给出。
1.2 企业画像类别内容行业科技推广和应用服务业-其他科技推广服务业资质空产品服务术服务、技术开发、技术咨询、技术交流、技1.3 发展历程2工商2.1工商信息2.2工商变更2.3股东结构2.4主要人员2.5分支机构2.6对外投资2.7企业年报2.8股权出质2.9动产抵押2.10司法协助2.11清算2.12注销3投融资3.1融资历史3.2投资事件3.3核心团队3.4企业业务4企业信用4.1企业信用4.2行政许可-工商局4.3行政处罚-信用中国4.5税务评级4.6税务处罚4.7经营异常4.8经营异常-工商局4.9采购不良行为4.10产品抽查4.12欠税公告4.13环保处罚4.14被执行人5司法文书5.1法律诉讼（当事人）5.2法律诉讼（相关人）5.3开庭公告5.4被执行人5.5法院公告5.6破产暂无破产数据6企业资质6.1资质许可6.2人员资质6.3产品许可6.4特殊许可7知识产权7.1商标7.2专利7.3软件著作权7.4作品著作权7.5网站备案7.6应用APP7.7微信公众号8招标中标8.1政府招标8.2政府中标8.3央企招标8.4央企中标9标准9.1国家标准9.2行业标准9.3团体标准9.4地方标准10成果奖励10.1国家奖励10.2省部奖励10.3社会奖励10.4科技成果11 土地11.1大块土地出让11.2出让公告11.3土地抵押11.4地块公示11.5大企业购地11.6土地出租11.7土地结果11.8土地转让12基金12.1国家自然基金12.2国家自然基金成果12.3国家社科基金13招聘13.1招聘信息感谢阅读:感谢您耐心地阅读这份企业调查分析报告。
Deploy Arista CloudEOS with Google Cloud Network Connectivity CenterGoalIn this deployment guide, we will show you how to connect the Arista CloudEOS Router to Google Cloud Network Connectivity Center (NCC), with the following high-level tasks.• Deploy an Arista CloudEOS Router from the Google Cloud marketplace• Create NCC Hub and Spokes using NCC’s UI page• Configure Arista CloudEOS and Google NCC to establish the BGP connection.• Verify the BGP connection and routing information using Arista EOS CLI, CloudVision, and Google NCC’s UI pageFor more information about the Arista CloudEOS Router, see here and Arista CloudVision, see here.For more information about Google Network Connectivity Center, see here.Deployment DiagramIn the following diagram, we will focus on spoke-3’s creation and connecting it to Google NCC. spoke-1 and spoke-2 are optional. They are pre-deployed to show that the CloudEOS router in spoke-3 can learn the other spokes’ prefixes from NCC. CloudVision component is also optional, but it allows you to take advantage of Arista’s real-time state-streaming telemetry capabilities and additional management functionalities.Figure: Connect Arista CloudEOS Router to Google Network Connectivity CenterDeployment Steps1. In the Google Cloud marketplace, search Arista CloudEOS. Choose the licensing model based on your requirement. For thisexample, we used “Arista CloudEOS Router (BYOL)”.2. Click “Launch”3. Fill out the following information, and click “Deploy”• Deployment name: your deployment name• Zone: choose the google region/zone where the router will be deployed• Machine type: choose one of the following, N1-standard-4, N1-standard-8, and N1-standard-16• User name: set the user name for ssh login• Ssh Key: the public key router will use for authentication, in such format: ssh-key XXXX username@host-name • Boot disk-type: Standard Persistent Disk• Boot disk size in GB: 17• Network Interface›Network: the VPC network where cloudeos router will be deployed›Subnetwork: the VPC subnet where cloudeos will be deployed›External IP: Ephemeral (which you can use for SSH and build a tunnel to on-prem cloudeos router for later use)4. The router will take about 5 minutes to be created and boot up. After the router is up and running, log in to the router using theSSK key, and install the license if you choose the BYOL model. You don’t need to install a license if you choose the PAYG model, the license is activated automatically.5. Go back to Google Cloud Console, click “Network Connectivity Center” under Hybrid Connectivity, you will see the summaryinformation about your NCC environment. A hub is already created. You can create a new hub if you don’t see one.6. Click the tab “SPOKES”, you will see all the spokes belonging to the same hub.7. Click “ADD SPOKES” to add a new spoke, with the following information, and click “Create”• Spoke name: cloudeos-r14• Description: cloudeos-r14• Spoke type: Router appliance• Region: choose the region where the cloudeos router is deployed in the previous step• Attach instances to the spoke›Instances: choose the cloudeos instance deployed in the previous step8. Now you can see the new spoke is being created as below9. Click the newly created spoke to configure additional information. Click “CONFIGURE BGP SESSION”10. Configure the Google Cloud Router BGP info• Create New router• Name: ncc-cr-c• Description: ncc-cr-c• Network: xxx-site-107-wan• Region: europe-west2 (the region where cloudeos is deployed in the previous step)• Google ASN: 64597• BGP peer Keepalive interval: 20• Advertised routes: create customer routes, advertise all subnets visible to cloud router (choose this so, on Google Cloud Router page, you can view all subnets that Google Cloud Router advertises to CloudEOS router)11. Configure the first BGP session information, and Click “SAVE AND CONTINUE”• Name: cloudeos-r14-bgp-1• Peer ASN: 65109 (CloudEOS Router’s ASN)• Cloud Router BGP IP: 10.240.209.3 (Google Cloud Router’s IP used for BGP Peering)• BGP Peer IP: 10.240.209.2 (unchangeable, the CloudEOS Router’s IP used for BGP Peering)• BGP Peer: enabled12. Configure the second BGP session information (for redundancy), and Click “SAVE AND CONTINUE”• Name: cloudeos-r14-bgp-2• Peer ASN: 65109 (CloudEOS Router’s ASN)• Cloud Router BGP IP: 10.240.209.4 (Google Cloud Router’s IP used for BGP Peering)• BGP Peer IP: 10.240.209.2 (unchangeable, the CloudEOS Router’s IP used for BGP Peering)• BGP Peer: enabled13. Now you can verify the Cloud Router and two BGP sessions configured as the following, and click “CREATE”14. After the creation, you can see the following BGP information15. Log in to the CloudEOS router using the SSH key and configure the following BGP configurationsrouter bgp 65109neighbor 10.240.209.3 remote-as 64597neighbor 10.240.209.3 maximum-routes 12000neighbor 10.240.209.4 remote-as 64597neighbor 10.240.209.4 maximum-routes 12000!address-family ipv4neighbor 10.240.209.3 activateneighbor 10.240.209.4 activate16. Now you should be able to verify the BGP status on the CloudEOS router using EOS CLI. The following shows that the two BGPsessions are established and 6 prefixes are learned from Google’s Cloud Router.17. You can also check the IP routing table on the CloudEOS router18. (Optional) If you have Arista CloudVision, you can also onboard the CloudEOS Router onto CloudVision, and you can see similarrouting information and more valuable information from a historical perspective for troubleshooting and visibility. If you don’t have Arista CloudVision, you can register it at https://www.arista.io/cv. More information about CloudVision can be found here.19. Go back to Google Cloud Console, under “Hybrid Connectivity” -> “Cloud Router”, you can view the BGP session status on CloudRouter20. Click the Cloud Router “ncc-cr-c” created in the previous step, you can see more details like advertised subnets and BGPconfigurationsSanta Clara—Corporate Headquarters 5453 Great America Parkway,Santa Clara, CA 95054Phone: +1-408-547-5500Fax: +1-408-538-8920Email:***************Ireland—International Headquarters3130 Atlantic AvenueWestpark Business CampusShannon, Co. ClareIrelandVancouver—R&D Office9200 Glenlyon Pkwy, Unit 300Burnaby, British ColumbiaCanada V5J 5J8San Francisco—R&D and Sales Office 1390Market Street, Suite 800San Francisco, CA 94102India—R&D OfficeGlobal Tech Park, Tower A & B, 11th FloorMarathahalli Outer Ring RoadDevarabeesanahalli Village, Varthur HobliBangalore, India 560103Singapore—APAC Administrative Office9 Temasek Boulevard#29-01, Suntec Tower TwoSingapore 038989Nashua—R&D Office10 Tara BoulevardNashua, NH 03062Copyright © 2021 Arista Networks, Inc. All rights reserved. CloudVision, and EOS are registered trademarks and Arista Networks is a trademark of Arista Networks, Inc. All other company names are trademarks of their respective holders. Information in this document is subject to change without notice. Certain features may not yet be available. Arista Networks, Inc. assumes no responsibility for any errors that may appear in this document. October 21, 2021SummaryNow you have completed the steps of creating and connecting the Arista CloudEOS Router to the Google Cloud Network Connectivity Center. You can repeat the steps to create other spokes to connect more Google Cloud regions or configure your on-prem CloudEOS routers to build the overlay tunnel back to your existing network.。
