Help required for EXOS 15.6 source ip based PBR
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-21-2015 09:36 AM
Running XOS 15.6 on X770 and configured ACL to match on source-address and ACL matches, but the actions i tried e.g. "redirect" and "redirect-name" to change nexthop does not work but instead the switch continues to use the default routing table. Anyone know of any PBR related bug on the version of XOS as we verified the commands exactly same as given in official concept guide and ACL solution guides?
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-25-2015 10:54 PM
Hi Jarek,
Health check using ping was configured and switch still recognises that next hop to be healthy (UP) when problem occured. Ping test to nexthop working but flow-redirect not working still. Snoop at peer showed no packet received from Extreme. So redirect not doing what its supposed to.
Chew
Health check using ping was configured and switch still recognises that next hop to be healthy (UP) when problem occured. Ping test to nexthop working but flow-redirect not working still. Snoop at peer showed no packet received from Extreme. So redirect not doing what its supposed to.
Chew
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-25-2015 12:33 PM
Hi,
the PBR with flow- redirect is working when (concept guide) :redirect IP address’s adjacency
is resolved. When the ARP table does not have the information to reach the redirect IP
address, the packet is routed based on the Layer 3 routing table.
Maybe the next-hop IP is learned from routing protocol like OSPF,BGP etc..
and then it will be up
--
Jarek
the PBR with flow- redirect is working when (concept guide) :redirect IP address’s adjacency
is resolved. When the ARP table does not have the information to reach the redirect IP
address, the packet is routed based on the Layer 3 routing table.
Maybe the next-hop IP is learned from routing protocol like OSPF,BGP etc..
and then it will be up
--
Jarek
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-25-2015 11:07 AM
Now another new issue with PBR feature on same firmware and switch. After running for some time, all of a sudden it no longer redirects any more even though next hop is up (ping health checks) and counter still incrementing (in policy file). Only starts to redirect after a switch reboot done.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-05-2015 06:37 PM
Hi
Could you confirm if you are trying the flow-redirect in the default virtual router or a user-created virtual router?
Flow re-direct is not supported in user created VR.
Thanks.
Prashanth KG
Could you confirm if you are trying the flow-redirect in the default virtual router or a user-created virtual router?
Flow re-direct is not supported in user created VR.
Thanks.
Prashanth KG
