Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1697
  • Last Modified:

Policy Based Routing on HP Procurve 5406

I have a business case to split certain vLANs between 2 different ISPs.  I have attached a very simple diagram of the network layout.  I am attempting to configure PBR on the 5406 to push traffic from vLAN 7 to ISP 2 and traffic from vLAN 1 to ISP 1.  I have attached the running config of the 5406.  Once I apply the policy to vLAN 7, only ping and DHCP traffic appear to flow.  From vLAN 7, I can ping other devices on vLAN 1 and from vLAN 1 I can ping devices on vLAN 7.  The DHCP server sits on vLAN 1 and is still able to hand out addresses to clients on vLAN 7.  I need the vLANs to communicate with eachother as well as separating their Internet traffic.

default gateway on vLAN 1 (10.1.0.0 /16): 10.1.1.252
default gateway on vLAN 7 (10.249.0.0 /16) : 10.249.0.1
default gateway on switch: 10.1.1.252

I am trying to determine what I am missing in the setup of the 5406 to make this scenario work.
Network-Diagram.JPG
5406.txt
0
smithdw1
Asked:
smithdw1
1 Solution
 
jburgaardCommented:
I have never worked with PBR in practice, but based on the fact that both
'next-hop' and
'default-next-hop'
statements exist , I guess there could be a difference.

As far as I can tell you must go via vlan1 to come from an IP in vlan7 to 10.1.0.10, but if 'next hop' is not the directly connected 10.1.8.15, you may miss a step-stone.
So my 2cents:
Either give 10.1.0.10 an IP in 10.249.0.0 and connect to vlan7 (also supply route to vlan1 via 10.249.0.1)
 or try
replace 'action next-hop 10.1.0.10'  with
action default-next-hop 10.1.0.10

HTH
0
 
smithdw1Author Commented:
Hello jburgaard,

Thanks for commenting.  I broke down and opened a case with HP and confirmed that the pbr is set correctly.  We verified that the switch was matching packets as expected.  They feel they have narrowed the issue down to the Cisco ASA that is handling the connection to ISP 2 - indicating that it may be blocking some traffic to vlan1.  I will have to take a closer look at the ASA to see if that is the case.  I do like your suggestion of adding a vlan interface to the ASA for each of the subnets, which would then allow me to do away with pbr on the switches.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now