{"id":8047,"date":"2025-01-15T16:17:31","date_gmt":"2025-01-15T15:17:31","guid":{"rendered":"https:\/\/mix2024.it-mix.net\/peering-port-configuration-how-to\/"},"modified":"2025-02-17T16:31:53","modified_gmt":"2025-02-17T15:31:53","slug":"peering-port-configuration-how-to","status":"publish","type":"page","link":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/","title":{"rendered":"Peering Port Configuration How-to"},"content":{"rendered":"
\n\n
<\/div>\n\n\n\n
Purpose<\/strong><\/h5>\n\n\n\n

This document wants to give some suggestions and hints on how to configure equipment directly connected to MIX L2 switches. We will refer to configuration scenarios described in MIX-302 document. Some configuration examples are available for the most popular vendors grouped by equipment type (Layer 2 Switches, Routers and Layer 3 Switches) and also some guidance on how to configure Link Aggregation on multiple peering ports.<\/p>\n\n\n\n

<\/div>\n\n\n\n
Switch L2 Configuration Examples<\/strong><\/h5>\n\n\n\n

The following examples are referred to the \u2018Member Switch\u2019 Equipment in the picture above.<\/p>\n\n\n\n

<\/div>\n\n\n\n
Switch Cisco Catalyst 29xx e 35xx<\/strong><\/h6>\n\n\n\n

When connecting a Catalyst switch to MIX the following protocols\/services must be disabled:<\/p>\n\n\n\n

    \n
  • VTP (VLAN Trunking Protocol)<\/li>\n\n\n\n
  • DTP (Dynamic Trunking Protocol)<\/li>\n\n\n\n
  • LLDP (Link Layer Discovery Protocol)<\/li>\n\n\n\n
  • UDLD (Unidirectional Link Detection)<\/li>\n<\/ul>\n\n\n\n

    Type in the following commands in global config mode (IOS sw)<\/p>\n\n\n\n

    vtp mode transparent!no spanning-tree vlan 100! global disable of LLDPno lldp run! Global dsable of CDPno cdp run!vlan 100name MIX!interface \/IfIdent\/description MIX Interfaceswitchport access vlan 100switchport mode accessswitchport nonegotiateno keepalivespeed nonegotiateno udld enable! If CDP can\/has not been disabile globallyno cdp enable! If LLDP can\/has not been disabile globallyno lldp receiveno lldp transmit! If Spanning Tree can\u2019t be disabile globallyspanning-tree bpdufilter enableend<\/p>\n\n\n\n

    <\/div>\n\n\n\n
    Cisco Catalyst 6500 Family<\/strong><\/h6>\n\n\n\n

    CatOS software is still very used on such equipment: the folowing commands apply:<\/p>\n\n\n\n

    set vtp mode offset port name \/IfIdent\/ Porta MIXset cdp disable \/IfIdent\/set udld disable \/IfIdent\/set trunk \/IfIdent\/ off dot1qset spantree bpdu-filter \/IfIdent\/ enableset vlan 100 name VLAN su MIXset vlan 100 \/IfIdent<\/p>\n\n\n\n

    If VTP can not be disabile globally the only known workaround is using l2pt thus disabling it on a per port basis:<\/p>\n\n\n\n

    set port l2protocol-tunnel \/IfIdent\/ vtp enable<\/p>\n\n\n\n

    Keep attention: this command could not be available on certain CatOS releases.<\/p>\n\n\n\n

    <\/div>\n\n\n\n
    Extreme Networks L2 Switch<\/strong><\/h6>\n\n\n\n

    The configuration fragment which follows is related to a L2 Switch directly connected to MIX belonging also to a EAPS ring. In the example, port 1 is connected to MIX, and port 2 and 3 belong to the ring. Teh peering router is connected to the ring on the MIX Vlan. All ports are Gigabit Ethernet. <\/p>\n\n\n\n

    create vlan “ring”configure vlan “ring” tag 1700 # VLAN-ID=0x6a4 Global Tag 9configure vlan “ring” qosprofile “QP8”configure vlan “ring” add port 2 taggedconfigure vlan “ring” add port 3 taggedcreate vlan “mix”configure vlan “mix” tag 1200 # VLAN-ID=0x4b0 Global Tag 3configure vlan “mix” add port 1 untaggedconfigure vlan “mix” add port 2 taggedconfigure vlan “mix” add port 3 taggedconfigure port 1 auto off speed 1000 duplex fullconfigure port 2 auto off speed 1000 duplex fullconfigure port 3 auto off speed 1000 duplex fulldisable edp port 1disable igmp snoopingdisable igmp snooping with-proxycreate eaps “ring-eaps”configure eaps “ring-eaps” mode transitconfigure eaps “ring-eaps” primary port 2configure eaps “ring-eaps” secondary port 3configure eaps “ring-eaps” add control vlan “ring”configure eaps “ring-eaps” add protect vlan “mix”enable eaps “ring-eaps”<\/p>\n\n\n\n

    <\/div>\n\n\n\n
    Brocade L2 Switch<\/strong><\/h6>\n\n\n\n

    Here follows a configuration fragment for a Brocade BigIron switch used as access device towards MIX LAN. In this example the Peering Router is connected to another porto f thesame switch.<\/p>\n\n\n\n

    ! Define ua VLAN for MIX port and the peering Routervlan number name “MIX” by portno spanning-treeuntagged ethernet if-verso-switch-MIXuntagged ethernet if-verso-router-peering<\/p>\n\n\n\n

    <\/div>\n\n\n\n
    Switch L3 \/ Peering Router Configuration Hints<\/strong><\/h5>\n\n\n\n

    Here follows some configuration templates for Layer 3 switches or Routers acting as Peering Border Router, according to the scheme visible in the picture above.<\/p>\n\n\n\n

    <\/div>\n\n\n\n
    Cisco<\/strong><\/h6>\n\n\n\n

    The following configuration fragmnts aims at disabling all functionalities which generate un wanted and undesirable traffic over MIX Peering LAN;<\/p>\n\n\n\n

    Autoconfiguration Protocol<\/p>\n\n\n\n

      \n
    • DHCP<\/li>\n\n\n\n
    • BOOTP<\/li>\n\n\n\n
    • TFTP of the configuration through MIX<\/li>\n<\/ul>\n\n\n\n

      Other Protocols and Services which traffic must not be sent through MIX LAN<\/p>\n\n\n\n

        \n
      • CDP<\/li>\n\n\n\n
      • DEC MOP<\/li>\n\n\n\n
      • IP redirects<\/li>\n\n\n\n
      • IP directed broadcasts<\/li>\n\n\n\n
      • proxy ARP<\/li>\n\n\n\n
      • IPv6 RouterAdvertisements<\/li>\n\n\n\n
      • L2keepalive<\/li>\n<\/ul>\n\n\n\n
        <\/div>\n\n\n\n

        Global Configuration<\/strong><\/p>\n\n\n\n

        ! Remove DHCPno service dhcp!Older Release may require instead: ip bootp server! NDo not allow Tftp download of configurationno service config! Global Disable of Cisco Discovery Protocol (CDP)no cdp run<\/p>\n\n\n\n

        <\/div>\n\n\n\n

        Interface Configuration<\/strong><\/p>\n\n\n\n

        ! Disable IP redirectsno ip redirects! Disable proxy ARPno ip proxy-arp! If CDP can not be disabled globally do it on MIX portno cdp enable! Disable directed broadcastsno ip directed-broadcast! If DEC\/MOC can not be disabled globally do it on MIXno mop enable! (Fast)Ethernet Ports: no auto-negotiation.no negotiation auto! fix the duplex modeduplex full! L2 keepalives does not have reason to exist on MIX peering LANno keepalive<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Extreme Networks<\/strong><\/h6>\n\n\n\n

        The folIowing example shows the details of a L3 router\/switch connected through port 1 on vlan \u2018mix\u2019 (untagged).<\/p>\n\n\n\n

        #\nConfig information for VLAN mix.\n#\ncreate vlan “mix”\nconfigure vlan “mix” tag 1200\nconfigure vlan “mix” protocol “IP”\nconfigure vlan “mix” ipaddress 217.29.66.\/Y\/ 255.255.254.0\nconfigure vlan “mix” add port 1 untagged\n#\nconfigure port 1 display-string “MIX”\ndisable edp port 1\n#\nenable ipforwarding vlan “mix”\ndisable ipforwarding broadcast vlan “mix”\ndisable ipforwarding fast-direct-broadcast vlan “mix”\ndisable ipforwarding ignore-broadcast vlan “mix”\ndisable ipforwarding lpm-routing vlan “mix\u201d\ndisable isq vlan “mix”\ndisable irdp vlan “mix”\ndisable icmp unreachable vlan “mix”\ndisable icmp redirects vlan “mix”\ndisable icmp port-unreachables vlan “mix”\ndisable icmp time-exceeded vlan “mix”\ndisable icmp parameter-problem vlan “amsix”\ndisable icmp timestamp vlan “mix”\ndisable icmp address-mask vlan “mix”\ndisable subvlan-proxy-arp “mix”\nconfigure ip-mtu 1500 vlan “mix”\n#\nIP Route Configuration\n#\nconfigure iproute add blackhole default\ndisable icmpforwarding vlan “mix”\ndisable igmp vlan “mix”<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Force 10<\/strong><\/h6>\n\n\n\n

        This example shows a configuration fragment for a router\/switch L3 Force10 connected to MIX through a 10 Gbit port.<\/p>\n\n\n\n

        ! Disable proxy-arp over MIX interfaceForce10(conf)#interface tengigabitethernet 0\/0Force10(conf-if-te-0\/0)#no ip proxy-arp! Disable Ipv6 ND RAForce10(conf-if-te-0\/0)#ipv6 nd suppress-ra! ARP timeout is 4 hrs by default but can be changedForce10(conf)#interface tengigabitethernet 0\/0Force10(conf-if-te-0\/0)#arp timeout \/minutes\/<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Brocade<\/strong><\/h6>\n\n\n\n

        Follows a configuration fragment for a Layer 3 Switch Brocade directly connected to MIX.<\/p>\n\n\n\n

        ! MIX interface configurationinterface ethernet ifport-name “MIX”! Activate the port at Layer 3 onlyroute-onlyno spanning-tree! Disable IPv6 ND-RA (Router Advertisements)ipv6 nd suppress-ra! Disable VLAN auto discovery.no vlan-dynamic-discovery! IP addressip address 216.29.6X.Y 255.255.254.0! No redirectsno ip redirectno ipv6 redirect! MIX recommends at least 2 hrs as ARP timeouts valueip arp-age 120! fast-ethernet ports: fix speed and duplexspeed-duplex 100-full<\/p>\n\n\n\n

        In some Ironware releases default settings for ICMPv6 ND was at 1 second, this value ha sto be changed to a much reasonable value of 1 hr, with the following command:<\/p>\n\n\n\n

        !Se IPv6 nd timeout at 1 hr.ipv6 nd ns-retransmit 3600<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Juniper<\/strong><\/h6>\n\n\n\n

        For Juniper routers be sure that you are announcing only unicast routes overMIX peering LAN by adding the following command to all neighbor, groups and prefix-limits:<\/p>\n\n\n\n

        set family inet unicast<\/p>\n\n\n\n

        Even just one neighbor configured with family inet \u2018any\u2019 will activate multi cast routing and MBGP over the peering LAN<\/p>\n\n\n\n

        <\/div>\n\n\n\n

        IPv4 ARP Cache Timeout<\/strong><\/p>\n\n\n\n

        Juniper ARP cache timeout is 20 minutes: to reduce the amount of ARP broadcast traffic we recommend to raise this value up to 4 hrs. Follow the configuration commands to achieve this.<\/p>\n\n\n\n

        > “configure”Entering configuration mode[edit]you@juniper# edit system arp[edit system arp]you@juniper# set aging-timer 240[edit system arp]you@juniper# show | compare[edit system arp]aging-timer 240;[edit system arp]you@juniper# commit and-quit<\/em>commit completeExiting configuration mode<\/p>\n\n\n\n

        Starting from release JUNOS 9.4 ARP cache timeout is configurable on each single interface:<\/p>\n\n\n\n

        [edit system arp aging-timer interface interface-name] [edit system arp aging-timer interface interface-name] aging-timer-minutes;aging-timer-minutes;<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Link Aggregation on Multiple MIX Ports<\/strong><\/h5>\n\n\n\n

        Link Aggregation (LAG) is available as a solution on MIX Peering LAN, according to the scheme visible in the picture below. To finalize this configuration is always mandatory to contact MIX Technical Department. Somo guideleines on how to configure it on the member side follow. <\/p>\n\n\n\n

        The service is available on Gigabit and 10 Gigabit Ethernet ports, up to a maximum of 8.<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Cisco Catalyst 6500<\/strong><\/h6>\n\n\n\n

        The Port Channel on the Cisco side must be configured in mode on, and not as negotiate or desirable. MIX switches does not enable LACT or PaGP as default: LACP is possible asking this feature to the MIX Technical Department. Some Interface modules may have limitations in the amount of traffic injected on the LAG. <\/p>\n\n\n\n

        Please verify your technical documentation or ask the vendor. MIX static MAC address assignment might be a problem so contact MIX Technical Department. MIX static MAC address assignment might be a problem so contact MIX Technical Department. <\/p>\n\n\n\n

        ! Port Channel MIX: Config Exampleinterface GigabitEthernet1\/1description MIX Link 1no ip addressno ip redirectsno ip proxy-arpno keepaliveno cdp enablechannel-group 1 mode on!interface GigabitEthernet1\/2description MIX Link 2no ip addressno ip redirectsno ip proxy-arpno keepaliveno cdp enablechannel-group 1 mode on!interface Port-channel1description MIX aggregated linkip address 217.29.6x.y 255.255.254.0no ip redirectsno ip proxy-arpno keepalive!<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Cisco GSR<\/strong><\/h6>\n\n\n\n

        MIX static MAC address assignment could be a problem with Cisco GSR: keep in touch with MIX Technical Department in this case<\/p>\n\n\n\n

        ! MIX Port Channel config example:!interface Port-channel1description MIX Port Channelip address 217.29.6x.y 255.255.254.0no ip redirectsno ip directed-broadcastno ip proxy-arpchannel-group minimum active 1no channel-group bandwidth control-propagationhold-queue 150 in!interface GigabitEthernet1\/2\/1no keepaliveno negotiation autochannel-group 1no cdp enable!interface GigabitEthernet1\/2\/2no keepaliveno negotiation autochannel-group 1no cdp enable!<\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Switch L3 Brocade<\/strong><\/h5>\n\n\n\n

        Old platforms like BigIron Jetcore and IronCore have limitations on the LAG port configuration. Please check your technical documentation. On BiGIron 15000 slot n. 8 is not available for LAG together with his neighbouring slots. <\/p>\n\n\n\n

        ! BigIron JetCore LAG configuration exampletrunk server ethernet slot\/port to slot\/port+1<\/p>\n\n\n\n

        BigIron RX e MLX\/XMR does not have any limitation on LAG ports.<\/p>\n\n\n\n

        ! RX\/MLX\/XMR MIX port channel config exampletrunk ethe slot\/port to slot\/port ethe otherslot\/otherport to otherslot\/otherport <\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Juniper M-Series<\/strong><\/h6>\n\n\n\n

        There are no nown problem with LAGs configuration starting from JuonOS release 6.0. A configuration example follows: <\/p>\n\n\n\n

        —[edit]ops@junix# show chassisaggregated-devices {ethernet {device-count 1;}}—[edit]ops@junix# show interfaces ge-2\/1\/0gigether-options {802.3ad ae0;}[edit]ops@junix# show interfaces ge-3\/1\/0gigether-options {802.3ad ae0;}—[edit]ops@junix# show interfaces ae0description “MIX”;unit 0 {family inet {filter {input MIX-in;output MIX-out;}address 217.29.6x.y\/23;}family inet6 {address 2001:7F8:B:100:1D1:A5Dx:xxxx:y\/64;}}<\/p>\n\n\n\n

        Optionally a more fine grained load balancing strategy is available:<\/p>\n\n\n\n

        #routing-options {autonomous-system abcde;forwarding-table {export [ load-balance ];}}policy-options {policy-statement load-balance {then {load-balance per-packet;}}}forwarding-options {hash-key {family inet {layer-3;layer-4;}}}<\/p>\n\n\n\n

        Just in case this should not be sufficient the hashing algorithm can be modified through some undocumented options introduced starting from JunOS 7.0<\/p>\n\n\n\n

        —hash-key {family inet {layer-3 {destination-address;protocol;source-address;}layer-4 {destination-port;source-port;type-of-service;}}}<\/p>\n\n\n\n

        Also the minimum number of active links is configurable: when the minimum number of active links is reached the aggregation will be removed, being the LAG not able anymore to carry all the expected traffic.<\/p>\n\n\n\n

        —aggregated-ether-options {minimum-links 2;link-speed 1g;}— <\/p>\n\n\n\n

        <\/div>\n\n\n\n
        Tagged ports configuration on MIX<\/strong><\/h5>\n\n\n\n

        Mix ports can be also configured to be active on multiple VLANS other than the public Peering broadcast domain, followiing the 802.1Q standard. To accomplish this task and gain access to this functionality that allows the implementation of different type of services over the Mix ports the contact and coordination with the MIX NOC is always a requirement, after the subscription of the additional service(s) with the MIX Sales team. Find enclosed in the following some technical guidelines on how to configure this functionality. There are many scenarios where Q-tagging can be employed, here follows some of the most common uses. Additional information and case-by case detail will be provided by the NOC upon configuration of the service. Again, here are presented the most common scenarios: <\/p>\n\n\n\n

          \n
        1. Tagged peering port over two VLANs, one the main Public Peering VLAN and another VLAN to interconnect privately with another member or a Closed User Group of several members ( each of them must have subscribed the service for the Q-tagging of the ports involved )<\/li>\n\n\n\n
        2. Interconnection ports for direct peering configured exclusively on dedicated VLANs3.<\/li>\n\n\n\n
        3. Access ports to other services provided by other MIX Members in appropriately segregated environments (private VLANs)<\/li>\n<\/ol>\n\n\n\n

          The following are the configuration outlines for the most common Vendors<\/p>\n\n\n\n

          <\/div>\n\n\n\n
          Cisco Configuration Commands<\/strong><\/h6>\n\n\n\n

          int gig 1.100encap dot1q 100description – Mix Milano –ip addr 217.29.6x.y 255.255.254.0int gig 1.501description – MIX OHM –encap dot1q 501ip addr 185.1.186.x 255.255.255.0<\/p>\n\n\n\n

          <\/div>\n\n\n\n
          Juniper Configuration Commands<\/strong><\/h6>\n\n\n\n

          user@host# set interfaces ge-0\/0\/0 vlan-tagginguser@host# set interfaces ge-0\/0\/0 unit 0 alias “MIX-MILANO”user@host# set interfaces ge-0\/0\/0.0 vlan-id 100user@host# set interfaces ge-0\/0\/0.0 family inet address 217.29.6x.y\/23user@host# set interfaces ge-0\/0\/0 unit 1 alias “MIX-OHM”user@host# set interfaces ge-0\/0\/0.1 vlan-id 501user@host# set interfaces ge-0\/0\/0.1 family inet address 185.1.186.x\/24<\/p>\n\n\n\n

          <\/div>\n\n\n\n
          Mikrotik Configuration Commands<\/strong><\/h6>\n\n\n\n

          \/interface vlanadd interface=sfp-sfpplus1 name=MIX-MILANO vlan-id=100\/ip addressadd address=217.29.6x.y\/23 interface=MIX-MILANO network=217.29.66.0\/interface vlanadd interface=sfp-sfpplus1 name=MIX-OHM vlan-id=501\/ip addressadd address=185.1.186.x\/24 interface=MIX-OHM network=185.1.186.0<\/p>\n\n\n\n

          <\/div>\n\n\n\n
          BGP Routing between Tagged ports (VLAN MIX and other MIX managed IXes)<\/strong><\/h6>\n\n\n\n

          In this Chapter the operational scenario of a Peering Port connected at the MIX Open Hub Med POP in Carini (PA) or at Mxi Bologna PoP and active both on the MIX Milan public Peering LAN and the local Public Peering VLAN is assessed. At the moment for this configuration the subscription of MIX additional service is not requested, so this can be done directly by sending a configuration request directly to the MIX NOC.Remote Local Peering VLANs are not extended to any other MIX PoP, being introduced to define a precise geographical location for the peering interconnection dedicated to the traffic being originated and terminated locally. For further information regarding the 802.1Q configuration of such a port please refer to the instruction provided in the previous Chapter. <\/p>\n\n\n\n

          As a general rule, MIX Remote VLANs like MIX-OHM or MIX-BO ones must be used as the primary traffic exchange route between members both connected in OHM. As an example in the following picture a basic scenario is presented: ISP1 has multiple MIX connections, one in Milano and one in Palermo while ISP2 is just connected at MIX OHM premises. In normal condition all the traffic between ISP 1 and ISP must use Yellow WLAN and thus follw the green dashed line. When a fault occurs to ISP1 OHM PoP port, the traffic can be routed over red VLAN (Mix Milano Peering VLAN) over the orange dashed path. Same scenario applies if Mix Bologna is involved instead of MIX Palermo. <\/p>\n\n\n\n

          In this scenario the requested routing behaviour is obtainable by ISP2 raising the LP (Local Preference) attribute over the MIX OHM VLAN received announcements coming from ISP1, and by ISP1 in the same way around, raising ISP2 announcement LP over the MIX OHM VLAN. Upon a ISP1 port fault in OHM, the traffic between ISP1 and ISP2 will traverse the MIX Milano Peering VLAN going back to normal upon ISP1 OHM port restoration. <\/p>\n\n<\/div><\/div><\/section>\n

          <\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":7,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"argomento":[],"class_list":["post-8047","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\nPeering Port Configuration How-to | MIX<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Peering Port Configuration How-to | MIX\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/\" \/>\n<meta property=\"og:site_name\" content=\"MIX\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/MIXMilanIXP\" \/>\n<meta property=\"article:modified_time\" content=\"2025-02-17T15:31:53+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/en\\\/peering-port-configuration-how-to\\\/\",\"url\":\"https:\\\/\\\/www.mix-it.net\\\/en\\\/peering-port-configuration-how-to\\\/\",\"name\":\"Peering Port Configuration How-to | MIX\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/#website\"},\"datePublished\":\"2025-01-15T15:17:31+00:00\",\"dateModified\":\"2025-02-17T15:31:53+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/en\\\/peering-port-configuration-how-to\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.mix-it.net\\\/en\\\/peering-port-configuration-how-to\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/en\\\/peering-port-configuration-how-to\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.mix-it.net\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Peering Port Configuration How-to\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/#website\",\"url\":\"https:\\\/\\\/www.mix-it.net\\\/\",\"name\":\"MIX\",\"description\":\"Italy\u2019s Largest Interconnection Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/#organization\"},\"alternateName\":\"Italy\u2019s Largest Interconnection Platform\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.mix-it.net\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/#organization\",\"name\":\"MIX\",\"alternateName\":\"Italy\u2019s Largest Interconnection Platform\",\"url\":\"https:\\\/\\\/www.mix-it.net\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.mix-it.net\\\/wp-content\\\/uploads\\\/2024\\\/09\\\/cropped-MIX-marchio_red.png\",\"contentUrl\":\"https:\\\/\\\/www.mix-it.net\\\/wp-content\\\/uploads\\\/2024\\\/09\\\/cropped-MIX-marchio_red.png\",\"width\":512,\"height\":512,\"caption\":\"MIX\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mix-it.net\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/MIXMilanIXP\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Peering Port Configuration How-to | MIX","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/","og_locale":"en_US","og_type":"article","og_title":"Peering Port Configuration How-to | MIX","og_url":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/","og_site_name":"MIX","article_publisher":"https:\/\/www.facebook.com\/MIXMilanIXP","article_modified_time":"2025-02-17T15:31:53+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/","url":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/","name":"Peering Port Configuration How-to | MIX","isPartOf":{"@id":"https:\/\/www.mix-it.net\/#website"},"datePublished":"2025-01-15T15:17:31+00:00","dateModified":"2025-02-17T15:31:53+00:00","breadcrumb":{"@id":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.mix-it.net\/en\/peering-port-configuration-how-to\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.mix-it.net\/en\/"},{"@type":"ListItem","position":2,"name":"Peering Port Configuration How-to"}]},{"@type":"WebSite","@id":"https:\/\/www.mix-it.net\/#website","url":"https:\/\/www.mix-it.net\/","name":"MIX","description":"Italy\u2019s Largest Interconnection Platform","publisher":{"@id":"https:\/\/www.mix-it.net\/#organization"},"alternateName":"Italy\u2019s Largest Interconnection Platform","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.mix-it.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.mix-it.net\/#organization","name":"MIX","alternateName":"Italy\u2019s Largest Interconnection Platform","url":"https:\/\/www.mix-it.net\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.mix-it.net\/#\/schema\/logo\/image\/","url":"https:\/\/www.mix-it.net\/wp-content\/uploads\/2024\/09\/cropped-MIX-marchio_red.png","contentUrl":"https:\/\/www.mix-it.net\/wp-content\/uploads\/2024\/09\/cropped-MIX-marchio_red.png","width":512,"height":512,"caption":"MIX"},"image":{"@id":"https:\/\/www.mix-it.net\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/MIXMilanIXP"]}]}},"_links":{"self":[{"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/pages\/8047","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/comments?post=8047"}],"version-history":[{"count":1,"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/pages\/8047\/revisions"}],"predecessor-version":[{"id":8048,"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/pages\/8047\/revisions\/8048"}],"wp:attachment":[{"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/media?parent=8047"}],"wp:term":[{"taxonomy":"argomento","embeddable":true,"href":"https:\/\/www.mix-it.net\/en\/wp-json\/wp\/v2\/argomento?post=8047"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}