topic Re: Changing next-hop for a single IP in ExtremeSwitching (VSP/Fabric Engine)

Changing next-hop for a single IP

JoseG — Mon, 12 Jan 2026 13:21:42 GMT

Hi all.

We have a pair of hosts in the same VLAN whose traffic need to be directed to a next-hop different of that in the default route configured in the VSP. As we searched in the forum and diverse documentation it seems that this is only feasible using filters, is that right? We was thinking in a filter like this:

filter acl 1 type inVlan
filter acl vlan 1 10
filter acl ace 1 1
filter acl ace action 1 1 permit redirect-next-hop <next-hop IP>
filter acl ace action 1 1 permit unreachable permit
filter acl ace action 1 1 permit count
filter acl ace ethernet 1 1 ether-type eq ip
filter acl ace ip 1 1 routed-only
filter acl ace ip 1 1 src-ip eq <host IP>
filter acl ace 1 1 enable

Would this do the work? Thanks!

Re: Changing next-hop for a single IP

RobertD1 — Wed, 14 Jan 2026 08:41:41 GMT

This looks very similar to the article on using PBR (Policy Based Routing) on VOSS. The filter should be able to redirect your traffic to a different destination in theory.

https://extreme-networks.my.site.com/ExtrArticleDetail?an=000082909

Re: Changing next-hop for a single IP

AngeloD — Fri, 16 Jan 2026 10:54:24 GMT

ACL is correct but remove “routed-only” if switch handle traffic only at L2 level (don’t perform routing on 110 VLAN).

The switch will report a warning but I confirm, redirection at L2 still works on release 9.1.0.0 and 9.2.0.0