6988e3cf0fa93a92e0eac803f0603c40408c3966
bgp-on-extreme-summit5i.md
| ... | ... | @@ -0,0 +1,47 @@ |
| 1 | +# DN42 peering on Extreme Summit 5i |
|
| 2 | +Here i'll show how to configure DN42 peering via BGP on an old Extreme Networks [Summit 5i](http://docs.google.com/viewer?url=andovercg.com/datasheets/summit-5i-switches.pdf) routing switch. This info should be also applicable to any other 'i'-series switch. Other configuration info may be found [here](https://bitbucket.org/dukzcry/hobbies/src). |
|
| 3 | + |
|
| 4 | +## Caveats |
|
| 5 | +Looks like ExtremeWare doesn't support any tunneling mechanism in contrast to ExtremeWare IPv6 or ExtremeXOS operating systems. So you need either put your switch behind the router which will do tunneling with DN42 participant or directly connect the switch to our network, if that possible. |
|
| 6 | + |
|
| 7 | +## Snipplet |
|
| 8 | +This configuration was tested on latest EW of 7.8.4.1 patch1-r4 version. But it should work on most of older releases as well. |
|
| 9 | + enable ipforwarding |
|
| 10 | + |
|
| 11 | + # Adding an alias |
|
| 12 | + enable multinetting standard |
|
| 13 | + configure vlan ext add secondary-ip 172.23.150.2/24 |
|
| 14 | + |
|
| 15 | + # Adding route to a neighbor |
|
| 16 | + configure iproute add 172.23.11.1/32 172.23.150.1 |
|
| 17 | + |
|
| 18 | + configure bgp soft-reconfiguration |
|
| 19 | + configure bgp AS-number 64528 |
|
| 20 | + configure bgp routerid 172.23.150.2 |
|
| 21 | + enable bgp |
|
| 22 | +Now, if you're trying EBGP with your peer: |
|
| 23 | + # Announce some networks |
|
| 24 | + configure bgp add network 172.23.150.0/25 |
|
| 25 | + configure bgp add network 77.37.212.15/32 |
|
| 26 | + |
|
| 27 | + create bgp neighbor 172.23.11.1 remote-AS-number 64526 |
|
| 28 | + # Point to a proper outgoing interface |
|
| 29 | + configure bgp neighbor 172.23.11.1 source-interface vlan ext |
|
| 30 | + |
|
| 31 | + enable bgp neighbor 172.23.11.1 |
|
| 32 | +Or IBGP (local router does the EBGP in following example): |
|
| 33 | +# Don't wait for an EBGP |
|
| 34 | + disable bgp synchronization |
|
| 35 | + |
|
| 36 | + create bgp neighbor 192.168.1.1 remote-AS-number 64528 |
|
| 37 | + enable bgp neighbor 192.168.1.1 |
|
| 38 | +Now you may diagnose the things doing: |
|
| 39 | + show bgp |
|
| 40 | + show bgp neighbor |
|
| 41 | + show bgp neighbor 172.23.11.1 received-routes all |
|
| 42 | + show bgp neighbor 172.23.11.1 transmitted-routes all |
|
| 43 | +After that ping and traceroute are your mates. It is worth to point switch to the DNS which knows .dn42 zone: |
|
| 44 | +`configure dns-client add name-server 192.168.1.1` |
|
| 45 | +And use names. |
|
| 46 | +## TO-DO |
|
| 47 | +Check 'Switch acts like router in multinetting case' setup. |
|
| ... | ... | \ No newline at end of file |