Extreme Networks Switch Configuration Notes

VLAN Commands

Creating a new VLAN

create vlan <name>
configure vlan <name> ipaddress <x.x.x.x/y>
configure vlan <name> tag <tag>
<configure vlan <name> add ports <1,2,3> untagged>
<configure vlan <name> add ports <4,5,6> tagged>
enable ipforwarding vlan <name>
enable loopback-mode vlan <name>
configure ospf add vlan <name> area 0.0.0.0

save

BGP Commands

Add Subnet to BGP Announcements

configure bgp add network <subnet>/<cidrmask>

save

Remove Subnet to BGP Announcements

configure bgp delete network <subnet>/<cidrmask>

save

View BGP Announcements

show bgp

Next Hop Routing

Setting next hop can be done with Policy-Based redirect on Extreme switches.

Please refer page 601 and 602 in EXOS Concepts guides 12.2.1.

(Your version is 12.0.3, but the basic idea is same. Plus 12.2.1 Concept guides has an example configuration.)

 

------<snip>------

Use the following procedure:

1 Issue the following command to prevent the redirect IP address from clearing from the IP ARP table

due to a timeout:

enable iparp refresh

2 Configure the ACL, either applying an ACL policy file similar to the example, or a Dynamic ACL.

3 Ping or send traffic so that the redirect IP adjacency is resolved.

You may want to create a static ARP entry for the redirect IP address, so that there will always be a

cache entry.

------<snip>------

 

Below is examples for step 2.

 

If you would like to redirect any traffic coming from 10.0.0.1 to 3.3.3.2 ..

(Or say, to configure the next hop of any packets with 10.0.0.1 as SA to 3.3.3.2)

 

This is an example of the policy file, “redirect_10.cfg”.

 

entry redirect_10 {

if match all {

                source-address 10.0.0.1;

} then {

                redirect 3.3.3.2;

}

}

 

This is an example when you apply “redirect_10.cfg” on the switch globally.

#configure access-list redirect_10 any

(any packets with 10.0.0.1 as SA ingress’ing to the switch will be redirected to 3.3.3.2)