no bgp enforce-first-as or similar. The route servers do not add the MICE AS to the AS path.The MICE Equipment (.odg) diagram shows how the various switches are connected.
Here are some pictures of the rack, from 2017-05-10: full cabinet, switch, top of cabinet.
This shows how the MICE side is configured and is for reference only. While some of this may be applicable to the member side, it is not a set of instructions on how to configure your device. For that, see the AMS-IX Config Guide or the "Any other tips on configuring my router?" question in the SeattleIX FAQ.
errdisable recovery cause bpduguard errdisable recovery cause link-flap errdisable recovery cause portsec no lldp run platform fap voq scheduling round-robin platform sand lag hardware-only spanning-tree mode rapid-pvst spanning-tree portfast bpduguard default spanning-tree portfast bpdufilter default interface EthernetX/X mtu 9214 switchport port-security maximum 1 switchport port-security storm-control broadcast level 1 storm-control multicast level 1 spanning-tree portfast
This shows how the MICE side is configured and is for reference only. While some of this may be applicable to the member side, it is not a set of instructions on how to configure your device. For that, see the AMS-IX Config Guide or the "Any other tips on configuring my router?" question in the SeattleIX FAQ.
set interface X/X/X mtu 9216 set protocols rstp interface X/X/X edge set ethernet-switching-options bpdu-block interface X/X/X set ethernet-switching-options secure-access-port interface X/X/X mac-limit 1 set ethernet-switching-options storm-control interface X/X/X bandwidth 100000 set ethernet-switching-options bpdu-block disable-timeout 60 set ethernet-switching-options storm-control interface all
This shows how the MICE side is configured and is for reference only. While some of this may be applicable to the member side, it is not a set of instructions on how to configure your device. For that, see the AMS-IX Config Guide or the "Any other tips on configuring my router?" question in the SeattleIX FAQ.
system mtu jumbo 9198 mac address-table aging-time 14400 errdisable detect cause link-flap errdisable recovery cause link-flap errdisable recovery cause storm-control vtp mode transparent switchport block multicast switchport block unicast switchport port-security maximum 1 switchport port-security switchport port-security violation restrict storm-control broadcast level 20.00 spanning-tree bpdufilter enable no cdp enable
no bgp enforce-first-as or similar. The route servers do not add the MICE AS to the AS path.The route servers are configured for passive BFD, meaning they will use BFD with you, but you need to start it. That is, you must be configured for active BFD. The route servers are configured with a minimum interval of 500 ms and a multiplier of 3.
The default behavior of the MICE route servers is to announce all routes to all peers. The following communities modify the annoucements:
0:peerAS -- Do not announce the route to the specified peer. 0:53679 -- Only announce the route to specified peers (see below). 53679:peerAS -- Announce the route to the specified peer.
For example, setting 0:1234 and 0:5678 causes the route server to announce the route to everyone except AS1234 and AS5678. This is an opt-out model.
To use an opt-in model, set 0:53679 plus the communities for each AS you want to receive the route. For example, setting 0:53679 53679:1234 53679:5678 causes the route servers to announce the route to only AS1234 and AS5678. If you choose an opt-in model, you may want to monitor the mice-discuss mailing list to hear about new members connecting.
If you are interested in operating a MICE remote switch, please contact peering@micemn.net.
The process for connecting a new remote switch is as follows:
Remote switch operators’ obligations include (but are not necessarily limited to):