howto/bgp-on-extreme-summit1i.md
... ...
@@ -0,0 +1,67 @@
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).
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
+
10
+ ## DN42 should go both in internal (for clients) and external VLANs
11
+ create vlan svlan
12
+ configure vlan svlan ipaddress 192.168.1.100/24
13
+ # Adding an alias
14
+ enable multinetting standard
15
+ configure vlan svlan add secondary-ip 172.23.150.2/24
16
+ ...
17
+
18
+ enable ipforwarding
19
+
20
+ configure vlan svlan add subvlan ext
21
+ ...
22
+
23
+ # It is worth to filter alien nets
24
+ create access-list deny_int ip destination any source 192.168.1.0/24 deny ports 2-16
25
+ ...
26
+ ##
27
+
28
+ # Adding route to a neighbor
29
+ configure iproute add 172.23.11.1/32 172.23.150.1
30
+
31
+ configure bgp soft-reconfiguration
32
+ configure bgp AS-number 64528
33
+ configure bgp routerid 172.23.150.2
34
+ enable bgp
35
+
36
+Now, if you're trying EBGP with your peer:
37
+
38
+ # Announce some networks
39
+ configure bgp add network 172.23.150.0/25
40
+ configure bgp add network 77.37.212.15/32
41
+
42
+ create bgp neighbor 172.23.11.1 remote-AS-number 64526
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
45
+
46
+ enable bgp neighbor 172.23.11.1
47
+
48
+Or IBGP (local router does the EBGP in following example):
49
+
50
+ # Don't wait for an EBGP
51
+ disable bgp synchronization
52
+
53
+ create bgp neighbor 192.168.1.1 remote-AS-number 64528
54
+ enable bgp neighbor 192.168.1.1
55
+
56
+Next, you may diagnose the things doing:
57
+
58
+ show bgp
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
62
+
63
+After that ping and traceroute are your mates. It is worth to point switch to the DNS which knows .dn42 zone:
64
+
65
+`configure dns-client add name-server 192.168.1.1`
66
+
67
+And use names.
... ...
\ No newline at end of file
howto/bgp-on-extreme-summit5i.md
... ...
@@ -1,67 +0,0 @@
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).
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
-
10
- ## DN42 should go both in internal (for clients) and external VLANs
11
- create vlan svlan
12
- configure vlan svlan ipaddress 192.168.1.100/24
13
- # Adding an alias
14
- enable multinetting standard
15
- configure vlan svlan add secondary-ip 172.23.150.2/24
16
- ...
17
-
18
- enable ipforwarding
19
-
20
- configure vlan svlan add subvlan ext
21
- ...
22
-
23
- # It is worth to filter alien nets
24
- create access-list deny_int ip destination any source 192.168.1.0/24 deny ports 2-16
25
- ...
26
- ##
27
-
28
- # Adding route to a neighbor
29
- configure iproute add 172.23.11.1/32 172.23.150.1
30
-
31
- configure bgp soft-reconfiguration
32
- configure bgp AS-number 64528
33
- configure bgp routerid 172.23.150.2
34
- enable bgp
35
-
36
-Now, if you're trying EBGP with your peer:
37
-
38
- # Announce some networks
39
- configure bgp add network 172.23.150.0/25
40
- configure bgp add network 77.37.212.15/32
41
-
42
- create bgp neighbor 172.23.11.1 remote-AS-number 64526
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
45
-
46
- enable bgp neighbor 172.23.11.1
47
-
48
-Or IBGP (local router does the EBGP in following example):
49
-
50
- # Don't wait for an EBGP
51
- disable bgp synchronization
52
-
53
- create bgp neighbor 192.168.1.1 remote-AS-number 64528
54
- enable bgp neighbor 192.168.1.1
55
-
56
-Next, you may diagnose the things doing:
57
-
58
- show bgp
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
62
-
63
-After that ping and traceroute are your mates. It is worth to point switch to the DNS which knows .dn42 zone:
64
-
65
-`configure dns-client add name-server 192.168.1.1`
66
-
67
-And use names.
... ...
\ No newline at end of file