Wired Intelligent Edge

last person joined: yesterday 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Back to discussions
Expand all | Collapse all

Policy based routing on Aruba 5406R zl2

This thread has been viewed 39 times

  • 1.  Policy based routing on Aruba 5406R zl2

    Posted Jul 18, 2017 01:06 PM
      |   view attached

    Hi,

    Can anyone please guide me how to configure Policy based routing on Aruba modular switch? I am new to Aruba networking.

     

    I have the attached scenario, where I have 2 routers each configured with subinterfaces and I want to route some VLANs from R1 and the other VLANs from R2. Also note that on R2 I have configured a DHCP server for each VLAN.

    The currently running version is KB.16.01.0006 and as I've read, that this version supports PBR without license.

     

    Please I need support

    Attachment(s)

    pdf
    Network Design.pdf   114 KB 1 version


  • 2.  RE: Policy based routing on Aruba 5406R zl2

    EMPLOYEE
    Posted Jul 18, 2017 04:40 PM

    Hi,

     

    I just created an eample that is based on your drawing from top of my head. Please test this in test infrastructure first since it's really from top of my head 8-). There are so many different options you can use within the classifier's or PBR actions. If you want to read some more information see the Advanced Traffic Management Guide manual and than chapter Classifier based software configuration. I'm assuming you have at least 5400 with V2 modules or higher. Hope this example will help you! Regards, Dobias

     

    class ipv4 R1
    match ip 10.128.0.1 0.0.0.255 any
    match ip :10.144.0.1 0.0.15.255 any

    class ipv4 R2
    match ip 10.20.0.1 0.0.15.255 any
    match ip 10.30.0.1 0.0.0.255 any

    policy pbr R1_R2
    class ipv4 R1
    action ip next-hop <IP of default Gateway>
    class ipv4 R2
    action ip next-hop <IP of default Gateway>


    vlan 15
    service-policy R1_R2 in



  • 3.  RE: Policy based routing on Aruba 5406R zl2

    Posted Jul 18, 2017 05:19 PM
    Hi Dobias,

    Thanks for your support.
    I was reading some articles and found that PBR only works on inbound traffic, but in my scenario all edge switches are connected to the Core switch.
    In the example you gave me, what do you mean by VLAN 15?


  • 4.  RE: Policy based routing on Aruba 5406R zl2

    EMPLOYEE
    Posted Jul 18, 2017 05:26 PM

    VLAN 15 was just the incoming VLAN I connected the PBR policy to.



  • 5.  RE: Policy based routing on Aruba 5406R zl2

    Posted Mar 13, 2023 07:29 AM

    Hello i Configure Static route tracking  using IP SLA

    For example like this  topology in cisco router but right now i want to configure  in our hpe Switch 5406

    i did ip SLA in Cisco Router 

    R1(config)# ip route 0.0.0.0 0.0.0.0 2.2.2.2
    R1(config)# ip route 0.0.0.0 0.0.0.0 3.3.3.3 10

    R1(config)# ip sla 1
    R1(config)# icmp-echo 2.2.2.2 source-interface FastEthernet0/0
    R1(config)# timeout 1000
    R1(config)# threshold 2
    R1(config)# frequency 3
    R1(config)# ip sla schedule 1 life forever start-time now 

    R1(config)# track 1 ip sla 1 reachability

    Can Anyone gudie me how to configure this like Topology in  HPE 5406zl Switch

    Regard 

    MBN


    Original Message


  • 6.  RE: Policy based routing on Aruba 5406R zl2

    Posted Feb 27, 2019 04:34 PM

    I have this PBR configuration of an HP comware switch, how can I translate it to ArubaOS Switch?

     

    policy-based-route correoserver deny node 1
    if-match acl 3100
    apply ip-address next-hop 192.168.20.1
    policy-based-route correoserver permit node 3
    if-match acl 3102
    apply ip-address next-hop 192.168.20.254
    #
    policy-based-route bancocajasocial deny node 1
    if-match acl 3000
    apply ip-address next-hop 172.17.0.1
    policy-based-route bancocajasocial permit node 3
    if-match acl 3002
    apply ip-address next-hop 192.168.20.254
    #
    policy-based-route routingWIFI deny node 1
    if-match acl 3200
    apply ip-address next-hop 172.18.0.2
    policy-based-route routingWIFI permit node 3
    if-match acl 3202
    apply ip-address next-hop 172.18.120.1
    #
    policy-based-route routingISSABEL permit node 1
    if-match acl 3404
    apply ip-address next-hop 10.0.0.199
    policy-based-route routingISSABEL deny node 2
    if-match acl 3400
    apply ip-address next-hop 10.0.0.1
    policy-based-route routingISSABEL permit node 3
    if-match acl 3402
    apply ip-address next-hop 10.0.0.199
    #
    policy-based-route routingACADEM deny node 1
    if-match acl 3500
    apply ip-address next-hop 172.16.0.1
    policy-based-route routingACADEM permit node 3
    if-match acl 3502
    apply ip-address next-hop 172.16.120.1



  • 7.  RE: Policy based routing on Aruba 5406R zl2

    MVP GURU
    Posted Feb 28, 2019 07:17 AM
    juanfarias88@gmail.com wrote:

    I have this PBR configuration of an HP comware switch, how can I translate it to ArubaOS Switch?

     

    policy-based-route correoserver deny node 1
    if-match acl 3100
    apply ip-address next-hop 192.168.20.1
    policy-based-route correoserver permit node 3
    if-match acl 3102
    apply ip-address next-hop 192.168.20.254
    #
    policy-based-route bancocajasocial deny node 1
    if-match acl 3000
    apply ip-address next-hop 172.17.0.1
    policy-based-route bancocajasocial permit node 3
    if-match acl 3002
    apply ip-address next-hop 192.168.20.254
    #
    policy-based-route routingWIFI deny node 1
    if-match acl 3200
    apply ip-address next-hop 172.18.0.2
    policy-based-route routingWIFI permit node 3
    if-match acl 3202
    apply ip-address next-hop 172.18.120.1
    #
    policy-based-route routingISSABEL permit node 1
    if-match acl 3404
    apply ip-address next-hop 10.0.0.199
    policy-based-route routingISSABEL deny node 2
    if-match acl 3400
    apply ip-address next-hop 10.0.0.1
    policy-based-route routingISSABEL permit node 3
    if-match acl 3402
    apply ip-address next-hop 10.0.0.199
    #
    policy-based-route routingACADEM deny node 1
    if-match acl 3500
    apply ip-address next-hop 172.16.0.1
    policy-based-route routingACADEM permit node 3
    if-match acl 3502
    apply ip-address next-hop 172.16.120.1

    it will be better to create a new topic...