howto/bgp-on-extreme-summit1i.md
... ...
@@ -1,5 +1,5 @@
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 how-to should be also applicable to any other 'i'-series switch. Other configuration info may be found [here](https://bitbucket.org/dukzcry/hobbies/src).
1
+# DN42 peering on Extreme Summit 1i
2
+Here i'll show how to configure DN42 peering via BGP on an old Extreme Networks [Summit 1i](http://docs.google.com/viewer?url=https://www.mtmnet.com/PDF_FILES/summit1i.pdf) routing switch. This how-to should be also applicable to any other 'i'-series switch.
3 3
4 4
## Caveats
5 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.
... ...
@@ -12,7 +12,7 @@ This configuration was tested on latest EW of 7.8.4.1 patch1-r4 version. But it
12 12
configure vlan svlan ipaddress 192.168.1.100/24
13 13
# Adding an alias
14 14
enable multinetting standard
15
- configure vlan svlan add secondary-ip 172.23.150.2/24
15
+ configure vlan svlan add secondary-ip 172.22.251.2/23
16 16
...
17 17
18 18
enable ipforwarding
... ...
@@ -26,39 +26,39 @@ This configuration was tested on latest EW of 7.8.4.1 patch1-r4 version. But it
26 26
##
27 27
28 28
# Adding route to a neighbor
29
- configure iproute add 172.23.11.1/32 172.23.150.1
29
+ configure iproute add 172.22.151.1/23 172.22.251.2
30 30
31 31
configure bgp soft-reconfiguration
32
- configure bgp AS-number 64528
33
- configure bgp routerid 172.23.150.2
32
+ configure bgp AS-number 65534
33
+ configure bgp routerid 172.22.251.2
34 34
enable bgp
35 35
36 36
Now, if you're trying EBGP with your peer:
37 37
38 38
# Announce some networks
39
- configure bgp add network 172.23.150.0/25
40
- configure bgp add network 77.37.212.15/32
39
+ configure bgp add network 172.22.151.0/23
40
+ configure bgp add network aa.bb.cc.dd/32
41 41
42
- create bgp neighbor 172.23.11.1 remote-AS-number 64526
42
+ create bgp neighbor 172.22.151.1 remote-AS-number 65535
43 43
# Point to a proper outgoing interface, useless in case when Super VLAN is used
44
- #configure bgp neighbor 172.23.11.1 source-interface vlan ext
44
+ #configure bgp neighbor 172.22.151.1 source-interface vlan ext
45 45
46
- enable bgp neighbor 172.23.11.1
46
+ enable bgp neighbor 172.22.151.1
47 47
48 48
Or IBGP (local router does the EBGP in following example):
49 49
50 50
# Don't wait for an EBGP
51 51
disable bgp synchronization
52 52
53
- create bgp neighbor 192.168.1.1 remote-AS-number 64528
53
+ create bgp neighbor 192.168.1.1 remote-AS-number 65535
54 54
enable bgp neighbor 192.168.1.1
55 55
56 56
Next, you may diagnose the things doing:
57 57
58 58
show bgp
59 59
show bgp neighbor
60
- show bgp neighbor 172.23.11.1 received-routes all
61
- show bgp neighbor 172.23.11.1 transmitted-routes all
60
+ show bgp neighbor 172.22.151.1 received-routes all
61
+ show bgp neighbor 172.22.151.1 transmitted-routes all
62 62
63 63
After that ping and traceroute are your mates. It is worth to point switch to the DNS which knows .dn42 zone:
64 64