set interfaces xe-1/1/0 unit 0 description routerB1:xe-1/1/0
set interfaces xe-1/1/0 unit 0 family inet mtu 9000
set interfaces xe-1/1/0 unit 0 family inet address 10.0.0.0
set interfaces xe-1/1/0 unit 0 family iso mtu 9000
set interfaces xe-1/1/0 unit 0 family inet6 mtu 9000
set interfaces xe-1/1/0 unit 0 family inet6 address 2001::
[set interfaces xe-1/1/0 unit 0 family mpls mtu 9000]
路由器 A1 (Cisco)
请查看以下示例配置：
interface TenGigE/1/0
description routerB1:xe-1/1/0:TenGigE/1/0
mtu 9000
ip address 10.0.0.0
ipv6 mtu 9000
ipv6 address 2001::
[mpls mtu 9000]
[mpls ip]
set interfaces xe-1/1/0 unit 0 description routerB1:xe-1/1/0
set class-of-service interfaces xe-1/1/0 scheduler-map qos-scheduler
set class-of-service interfaces xe-1/1/0 shaping-rate 9500000000
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-26。"],[],[],null,["# Configure on-premises routers\n\n| **Preview**\n|\n|\n| This product is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to configure on-premises routers for\nCross-Site Interconnect.\n\nAfter you create a cross-site network with one or more wire groups, you need to\nconfigure your on-premises routers at sites A and B to establish connectivity\nwith each other.\n\nThis page provides a sample topology and configuration that you can use as a\nguide when configuring your on-premises routers.\n\nFor definitions of terms used on this page, see\n[Cloud Interconnect key terms](/network-connectivity/docs/interconnect/concepts/terminology) and the\n[Cross-Site Interconnect overview](/network-connectivity/docs/interconnect/concepts/cross-site-overview).\n\nSample topology\n---------------\n\nThis page provides sample configurations for a topology in which:\n\n- Each Cross-Site Interconnect connection terminates on an on-premises router.\n- A cross-site network with a redundant wire group has been created over the connections.\n- Each on-premises router establishes connectivity with the corresponding router at the opposite site over the wire between the connections. The routers exchange routes using IGP.\n\nThe following diagrams show both the physical and logical topology.\n[](/static/network-connectivity/docs/interconnect/images/cross-site-topology-physical.svg) Sample physical topology (click to enlarge).\n\n\u003cbr /\u003e\n\n\n\u003cbr /\u003e\n\n\n[](/static/network-connectivity/docs/interconnect/images/cross-site-topology-logical.svg) Sample logical topology (click to enlarge).\n\n\u003cbr /\u003e\n\nConfigure on-premises routers\n-----------------------------\n\nThis section provides sample on-premises router configurations. Consider the\nfollowing when using the samples on this page:\n\n- The samples assume 10 Gbps Cross-Site Interconnect connections.\n- Some configurations are marked as optional. Use the corresponding samples as needed depending on your use case.\n- The samples apply to router A1 from the sample topology. You must also configure routers A2, B1, and B2.\n\nFor additional information about configuration settings and values, see the\ndocumentation for your device.\n\n### Configure the interface\n\nThis sample configures the interface of the on-premises router as follows:\n\n- Sets the description to the name and interface of the neighbor router with which you are establishing connectivity, in the format \u003cvar translate=\"no\"\u003eROUTER_NAME\u003c/var\u003e:\u003cvar translate=\"no\"\u003eINTERFACE_NAME\u003c/var\u003e. For router A1, the neighbor router is router B1.\n- Sets the IP addresses of the interface for router A1 using the values from the sample topology.\n- Sets MTU to the recommended value of `9000`.\n- Sets MTU values for MPLS in both samples, and enables MPLS in the Cisco sample.\n These settings are optional as indicated by the brackets (`[]`).\n You can omit these settings if you don't plan to configure MPLS RSVP.\n\n### Router A1 (Juniper)\n\nSee the following sample configuration: \n\n```\nset interfaces xe-1/1/0 unit 0 description routerB1:xe-1/1/0\nset interfaces xe-1/1/0 unit 0 family inet mtu 9000\nset interfaces xe-1/1/0 unit 0 family inet address 10.0.0.0\nset interfaces xe-1/1/0 unit 0 family iso mtu 9000\nset interfaces xe-1/1/0 unit 0 family inet6 mtu 9000\nset interfaces xe-1/1/0 unit 0 family inet6 address 2001::\n[set interfaces xe-1/1/0 unit 0 family mpls mtu 9000]\n```\n\n### Router A1 (Cisco)\n\nSee the following sample configuration: \n\n```\ninterface TenGigE/1/0\n description routerB1:xe-1/1/0:TenGigE/1/0\n mtu 9000\n ip address 10.0.0.0\n ipv6 mtu 9000\n ipv6 address 2001::\n [mpls mtu 9000]\n [mpls ip]\n```\n\n### Configure traffic shaper\n\nTo help avoid packet loss, shape traffic below the Cross-Site Interconnect\nconnection capacity to account for additional encapsulation overhead. If you\ndon't configure traffic shaper, you might experience packet loss when traffic is\nat or near the full capacity of the connection, depending on the frame size.\n\nThis sample configures traffic shaper with a value of `9500000000` bits per second\n(bps) for a 10 Gbps Cross-Site Interconnect connection. If you have a\n100 Gbps connection, the recommended value is `96000000000`.\n\nThis sample also sets the description to the name of the neighbor router.\nFor router A1, the neighbor is router B1. \n\n### Router A1 (Juniper)\n\nSee the following sample configuration: \n\n```\nset interfaces xe-1/1/0 unit 0 description routerB1:xe-1/1/0\nset class-of-service interfaces xe-1/1/0 scheduler-map qos-scheduler\nset class-of-service interfaces xe-1/1/0 shaping-rate 9500000000\n```\n\n### Router A1 (Cisco)\n\nSee the following sample configuration: \n\n```\ninterface TenGigE/1/0\n description routerB1\n service-policy output qos-scheduler\n shape average 9500000000\n!\n```\n\n### Enable IGP and BFD\n\nEnable IGP and BFD to exchange routes and detect failures so that you can\nimplement failover.\n\nTo save bandwidth, the following sample disables CSNP by setting\n`csnp-interval` to the maximum value. This setting is optional as indicated by\nthe brackets (`[]`). You can remove or adjust this setting if your\nnetwork requires CSNP.\n**Note:** We recommend that you configure BFD with the following timers and associate it with an IGP as follows. You can alternatively use another method, such as configuring BFD on the interfaces or with static routes. \n\n### Router A1 (Juniper)\n\nSee the following sample configuration: \n\n```\nset protocols isis interface xe-1/1/0.0 level 2 metric 3000\nset protocols isis interface xe-1/1/0.0 level 2 hello-interval 1\nset protocols isis interface xe-1/1/0.0 level 2 hold-time 5\nset protocols isis interface xe-1/1/0.0 level 1 disable\nset protocols isis interface xe-1/1/0.0 hello-padding adaptive\n[set protocols isis interface xe-1/1/0.0 csnp-interval 65535]\nset protocols isis interface xe-1/1/0.0 point-to-point\nset protocols isis interface xe-1/1/0.0 family inet bfd-liveness-detection version 1\nset protocols isis interface xe-1/1/0.0 family inet bfd-liveness-detection minimum-interval 250\nset protocols isis interface xe-1/1/0.0 family inet bfd-liveness-detection multiplier 3\nset protocols isis interface xe-1/1/0.0 family inet bfd-liveness-detection detection-time threshold 900\nset protocols isis interface xe-1/1/0.0 family inet bfd-liveness-detection authentication key-chain IS-IS-BFD-KEY\nset protocols isis interface xe-1/1/0.0 family inet bfd-liveness-detection authentication algorithm keyed-sha-1\n```\n\nReplace \u003cvar translate=\"no\"\u003eIS-IS-BFD-KEY\u003c/var\u003e with the name of your IS-IS BFD\nkeychain.\n\n### Enable LLDP\n\nIf you have port mode wire groups, enable LLDP to help verify connectivity\nbetween your routers. LLDP protocol data units (PDUs) are automatically\nforwarded across the port mode wire between your routers. When your routers\nsuccessfully exchange LLDP information, it confirms that the wire is\nfunctioning correctly.\n\nYou can also enable LLDP before completing the interface configuration to help\nverify newly provisioned Cross-Site Interconnect connections. \n\n### Router A1 (Juniper)\n\nSee the following sample configuration: \n\n```\nset protocols lldp interface xe-1/1/0.0\n```\n\n### Router A1 (Cisco)\n\nSee the following sample configuration: \n\n```\ninterface TenGigE/1/0\n lldp\n receive disable\n transmit disable\n !\n```\n\n### Enable MACsec\n\nEnable MACsec (port mode, optional) if you have port mode wire groups and want\nto use MACsec.\n\nThis sample configuration does the following:\n\n- Enables a must-secure policy\n- Configures a replay window with the maximum value to prevent replay protection from generating false positives when MACsec attempts to order packets\n- Sets the `eapol` destination MAC address to `broadcast-address`\n\n### Router A1 (Cisco)\n\n```\ninterface TenGigE/1/0\n Description facing google PF\n macsec replay-protection window-size 4294967295\n macsec network-link\n no cdp enable\n eapol destination-address broadcast-address\n mka policy MKA_POLICY_NAME\n mka pre-shared-key key-chain MKA_KEY_CHAIN\n service-policy output egress-scheduler\nEnd\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eMKA_POLICY_NAME\u003c/var\u003e: the name of your MKA policy\n- \u003cvar translate=\"no\"\u003eMKA_KEY_CHAIN\u003c/var\u003e: the name of your MKA keychain\n\n### Enable QinQ\n\nQinQ is optional and is used to transport VLANs across a service provider\nnetwork.\n\nAdjust the sample as needed depending on whether you are using STP, LACP, or\nboth protocols between your endpoints. \n\n### Router A1 (Cisco)\n\nSee the following sample configuration: \n\n```\ninterface TenGigE/1/0\n switchport access vlan VLAN_ID\n switchport mode dot1q-tunnel\n l2protocol-tunnel stp\n l2protocol-tunnel point-to-point lacp\n```\n\nReplace \u003cvar translate=\"no\"\u003eVLAN_ID\u003c/var\u003e with your VLAN ID.\n\n### Configure MPLS RSVP\n\nMPLS RSVP is optional and is used to handle failover. \n\n### Router A1 (Juniper)\n\nSee the following sample configuration: \n\n```\nset protocols mpls interface xe-1/1/0.0 admin-group encrypted\nset protocols mpls interface xe-1/1/0.0 admin-group unencrypted\n\nset protocols rsvp interface xe-1/1/0.0 subscription 80\nset protocols rsvp interface xe-1/1/0.0 update-threshold 5\nset protocols rsvp interface xe-1/1/0.0 link-protection optimize-timer 3000\nset protocols rsvp interface xe-1/1/0.0 link-protection exclude-srlg\nset protocols rsvp interface xe-1/1/0.0 link-protection admin-group include-all encrypted\nset protocols rsvp interface xe-1/1/0.0 link-protection admin-group include-all unencrypted\nset protocols rsvp interface xe-1/1/0.0 link-protection admin-group exclude red\n```"]]
