<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface) in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3908150#M319837</link>
    <description>&lt;P&gt;We have a post that is several months old describing an issue with PBR that received a number of suggestions and has no clear indication of whether the issue was solved or not.&amp;nbsp;I found it odd in the original post that the PBR was specifying the secondary address and no mention of the primary address. And I wonder if the issue was that the device was sending using the primary address and not the secondary address.&amp;nbsp;Now&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/293775"&gt;@Alex Pfeil&lt;/a&gt;&amp;nbsp;says he has the same issue but provides no details. Perhaps if we get the details we might have some suggestions about his issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
    <pubDate>Wed, 14 Aug 2019 14:39:53 GMT</pubDate>
    <dc:creator>Richard Burts</dc:creator>
    <dc:date>2019-08-14T14:39:53Z</dc:date>
    <item>
      <title>PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854400#M314778</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm suffering a problem that about PBR and VLAN Interface on the Catalyst C9300-24UX, Cisco IOS XE Software, Version 16.06.03.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is, I created a route-map and access-list as my PBR configuration, and then applied on VLAN 1, but the PBR seems doesn't work, I even didn't see any hit count when I show route-map and didn't see the relative messages from the 'debug ip policy'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---------------The following is the part of configurations -----------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;description Server network subnet&lt;BR /&gt;ip address 10.99.99.10 255.255.255.240 secondary&lt;BR /&gt;ip address 192.168.34.252 255.255.255.0&lt;BR /&gt;ip policy route-map PBR_testing&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list 110 permit ip 10.99.99.0 0.0.0.255 192.168.56.0 0.0.0.255&lt;BR /&gt;!&lt;BR /&gt;route-map PBR_testing permit 10&lt;BR /&gt;match ip address 110&lt;BR /&gt;set ip next-hop 192.168.34.245&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;---------------The following is my topology -----------------&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PBR.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/36543i26F508142E80E89C/image-size/large?v=v2&amp;amp;px=999" role="button" title="PBR.jpg" alt="PBR.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The purpose that I want to make the client (on the left bottom side) can access the server&amp;nbsp;(on the right bottom side). I'm sure the routing table has the PBR's next-hop existing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help me if you have any idea, please. I spent almost two days trying to solve this issue.&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2019 16:06:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854400#M314778</guid>
      <dc:creator>Ryan YC</dc:creator>
      <dc:date>2019-05-11T16:06:53Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854426#M314788</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;post the full configuration of the switch. Do you have 'ip routing' enabled ?&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2019 18:19:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854426#M314788</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2019-05-11T18:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854438#M314791</link>
      <description>&lt;P&gt;Please let me know if any information is needed for this troubleshooting,&amp;nbsp; thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;------------------------------- The following is the configuration ---------------------------------&lt;BR /&gt;!&lt;BR /&gt;version 16.6&lt;BR /&gt;no service pad&lt;BR /&gt;service timestamps debug datetime localtime show-timezone&lt;BR /&gt;service timestamps log datetime localtime show-timezone&lt;BR /&gt;service password-encryption&lt;BR /&gt;no platform punt-keepalive disable-kernel-core&lt;BR /&gt;!&lt;BR /&gt;hostname xxxxxxx&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;vrf definition Mgmt-vrf&lt;BR /&gt;!&lt;BR /&gt;address-family ipv4&lt;BR /&gt;exit-address-family&lt;BR /&gt;!&lt;BR /&gt;address-family ipv6&lt;BR /&gt;exit-address-family&lt;BR /&gt;!&lt;BR /&gt;enable secret 5 xxxxxxxxxxxxxxxx&lt;BR /&gt;!&lt;BR /&gt;aaa new-model&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;aaa authentication login default local&lt;BR /&gt;aaa authentication enable default enable&lt;BR /&gt;aaa authorization exec default local&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;ip routing&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;cpp system-default&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;diagnostic bootup level minimal&lt;BR /&gt;!&lt;BR /&gt;spanning-tree mode pvst&lt;BR /&gt;spanning-tree extend system-id&lt;BR /&gt;file privilege 5&lt;BR /&gt;!&lt;BR /&gt;username admin secret 5 xxxxxxxxxxxxxxxxxx&lt;BR /&gt;!&lt;BR /&gt;redundancy&lt;BR /&gt;mode sso&lt;BR /&gt;!&lt;BR /&gt;lldp run&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel1&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel2&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel3&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel4&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel5&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel6&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel7&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel8&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel9&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel12&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel16&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel18&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel19&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/0&lt;BR /&gt;vrf forwarding Mgmt-vrf&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;speed 1000&lt;BR /&gt;negotiation auto&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/1&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/2&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/3&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 2 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/4&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 6 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/5&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 3 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/6&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 19 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/7&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 4 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/8&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/9&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/10&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 7 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/11&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 8 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/12&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 9 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/13&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 18 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/14&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 18 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/15&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 12 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/16&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/17&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 16 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/18&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 16 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/19&lt;BR /&gt;switchport mode access&lt;BR /&gt;spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/20&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/21&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/22&lt;BR /&gt;service-policy output IP_Precedence_For_MPLS_QoS&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/23&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/0/24&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/1/1&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/1/2&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/1/3&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/1/4&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/1&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;load-interval 30&lt;BR /&gt;channel-group 5 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/2&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/3&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/4&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/5&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/6&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/7&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet1/1/8&lt;BR /&gt;!&lt;BR /&gt;interface FortyGigabitEthernet1/1/1&lt;BR /&gt;!&lt;BR /&gt;interface FortyGigabitEthernet1/1/2&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/1&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/2&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/3&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 2 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/4&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 6 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/5&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 3 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/6&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 19 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/7&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 4 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/8&lt;BR /&gt;switchport mode access&lt;BR /&gt;spanning-tree portfast&lt;BR /&gt;spanning-tree bpduguard enable&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/9&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/10&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 7 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/11&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 8 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/12&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 9 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/13&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 18 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/14&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 18 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/15&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;channel-group 12 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/16&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/17&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 16 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/18&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;channel-group 16 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/19&lt;BR /&gt;switchport mode access&lt;BR /&gt;spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/20&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/21&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/22&lt;BR /&gt;description DO_NOT_CONFIGURE&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/23&lt;BR /&gt;switchport mode access&lt;BR /&gt;spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/0/24&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet2/1/1&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet2/1/2&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet2/1/3&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet2/1/4&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/1&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;load-interval 30&lt;BR /&gt;channel-group 5 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/2&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/3&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/4&lt;BR /&gt;switchport mode access&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/5&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/6&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/7&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet2/1/8&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface FortyGigabitEthernet2/1/1&lt;BR /&gt;!&lt;BR /&gt;interface FortyGigabitEthernet2/1/2&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;description Server network subnet&lt;BR /&gt;ip address 10.99.99.10 255.255.255.240 secondary&lt;BR /&gt;ip address 192.168.34.252 255.255.255.0&lt;BR /&gt;ip policy route-map PBR_testing&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;!&lt;BR /&gt;ip forward-protocol nd&lt;BR /&gt;ip http server&lt;BR /&gt;ip http authentication local&lt;BR /&gt;ip http secure-server&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 192.168.34.245&lt;BR /&gt;ip route 10.0.0.0 255.255.255.0 192.168.34.245&lt;BR /&gt;ip route 10.40.0.0 255.255.0.0 192.168.34.245&lt;BR /&gt;ip route 10.40.10.0 255.255.254.0 192.168.34.245&lt;BR /&gt;ip route 10.75.254.0 255.255.255.0 192.168.34.245&lt;BR /&gt;ip route 10.75.255.0 255.255.255.0 192.168.34.245&lt;BR /&gt;ip route 192.168.0.0 255.255.224.0 192.168.34.247&lt;BR /&gt;ip route 192.168.52.0 255.255.252.0 192.168.34.247&lt;BR /&gt;ip route 192.168.56.0 255.255.255.0 192.168.34.247&lt;BR /&gt;ip route 192.168.128.0 255.255.128.0 192.168.34.247&lt;BR /&gt;ip route 172.24.16.0 255.255.252.0 192.168.34.245&lt;BR /&gt;ip route 172.24.20.0 255.255.255.0 192.168.34.245&lt;BR /&gt;ip route 172.24.74.11 255.255.255.255 192.168.34.245&lt;BR /&gt;ip route 192.168.2.32 255.255.255.240 192.168.34.247&lt;BR /&gt;!&lt;BR /&gt;ip ssh version 2&lt;BR /&gt;!&lt;BR /&gt;access-list 110 permit ip 10.99.99.0 0.0.0.255 192.168.56.0 0.0.0.255&lt;BR /&gt;!&lt;BR /&gt;route-map PBR_testing permit 10&lt;BR /&gt;match ip address 110&lt;BR /&gt;set ip next-hop 192.168.34.245&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;control-plane&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;line con 0&lt;BR /&gt;exec-timeout 30 0&lt;BR /&gt;logging synchronous&lt;BR /&gt;stopbits 1&lt;BR /&gt;line vty 0 4&lt;BR /&gt;exec-timeout 60 0&lt;BR /&gt;logging synchronous&lt;BR /&gt;transport input all&lt;BR /&gt;line vty 5 15&lt;BR /&gt;exec-timeout 60 0&lt;BR /&gt;logging synchronous&lt;BR /&gt;transport input all&lt;BR /&gt;!&lt;BR /&gt;ntp server 192.168.34.12&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;end&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2019 18:57:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854438#M314791</guid>
      <dc:creator>Ryan YC</dc:creator>
      <dc:date>2019-05-11T18:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854468#M314797</link>
      <description>&lt;OL&gt;
&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Sat, 11 May 2019 21:38:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854468#M314797</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2019-05-11T21:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854470#M314798</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The wildcard used in your access list 110 does not match the subnet mask of the secondary IP address on the Vlan interface. Try and change it to:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;access-list 110 permit ip 10.99.99.0 0.0.0.15 192.168.56.0 0.0.0.255&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2019 21:48:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854470#M314798</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2019-05-11T21:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854585#M314813</link>
      <description>&lt;P&gt;Hi Georg,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I changed the wildcard mask in the access list, but the issue still same &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This's my current only ACL in the route-map on the Interface VLAN 1:&lt;/P&gt;&lt;P&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;&lt;EM&gt;'&lt;FONT size="2"&gt;access-list 110 permit ip 10.99.99.0 0.0.0.15 192.168.56.0 0.0.0.255'&lt;/FONT&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;However after I applied the route-map onto the Interface, I can see a lot of messages from 'debug ip policy' those are reporting:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:48:59 UTC: IP: s=192.168.34.76 (Vlan1), d=192.168.34.255, len 692, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:48:59 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:00 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:01 UTC: IP: s=192.168.34.20 (Vlan1), d=192.168.34.255, len 229, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:01 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:02 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:02 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:03 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:04 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:05 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:06 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:07 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:07 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:08 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:08 UTC: IP: s=192.168.34.35 (Vlan1), d=192.168.34.255, len 229, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:08 UTC: IP: s=192.168.34.51 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:08 UTC: IP: s=192.168.34.51 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:09 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;May 12 10:49:10 UTC: IP: s=192.168.34.15 (Vlan1), d=192.168.34.255, len 78, policy rejected -- normal forwarding&lt;/FONT&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was continuing to ping a server in 192.168.56.0/24 subnet by using 10.99.99.1, but I didn't see any message about 10.99.99.0 subnet on the Core switch.&lt;/P&gt;</description>
      <pubDate>Sun, 12 May 2019 08:57:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854585#M314813</guid>
      <dc:creator>Ryan YC</dc:creator>
      <dc:date>2019-05-12T08:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854588#M314815</link>
      <description />
      <pubDate>Sun, 12 May 2019 09:11:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854588#M314815</guid>
      <dc:creator>Ryan YC</dc:creator>
      <dc:date>2019-05-12T09:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854590#M314816</link>
      <description>&lt;P&gt;Hello Yung,&lt;/P&gt;
&lt;P&gt;from the output that you have provided we can say the PBR is configured and actually skipped for all source addresses in the primary IP subnet.&lt;/P&gt;
&lt;P&gt;Could you try to use a test in which you match a specific IP address in the primary subnet&lt;/P&gt;
&lt;P&gt;try to use an ACL like the following&lt;/P&gt;
&lt;P&gt;access-list 111 permit ip 192.168.34.x 0.0.0.0 192.168.56.0 0.0.0.255&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I wonder if the issue is related to secondary addresses.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In old times to make PBR working in some multilayer platforms we needed to change the SDM template. I don't think it is your case as the debug lines show that the PBR is considered before using normal forwarding.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope to help&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 May 2019 09:28:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854590#M314816</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2019-05-12T09:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854605#M314817</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what if you make the secondary the primary and the primary the secondary IP address on your Windows NIC ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 May 2019 11:25:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854605#M314817</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2019-05-12T11:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854715#M314839</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/257823"&gt;@Ryan YC&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Your PBR configuration is correct and should work appropriately. The only think that I can think of is packets not getting to the right router. Can you make sure that you are using 10.99.99.10 as the gateway for the host in 10.99.99.0/28 subnet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also it would be helpful to apply below ACL on the interface and make sure that packets are indeed received on the right interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;access-list 199 permit icmp host 10.99.99.1 192.168.56.0 0.0.0.255 log
access-list 199 permit ip any any &lt;BR /&gt;!&lt;BR /&gt;interface vlan 1 &lt;BR /&gt; ip access-group 199 in&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;If the hit count on the first entry is seen and you've verified in logs that the destination is correct. Then PBR should work fine.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;*** Please mark this post helpful if it contributed to your query ***&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Sebastian&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2019 01:54:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854715#M314839</guid>
      <dc:creator>Sebastian Fernandez</dc:creator>
      <dc:date>2019-05-13T01:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854898#M314869</link>
      <description>&lt;P&gt;&lt;SPAN&gt;for PBR to work, I should expect to have multiple routes, where you want to force/prefer a specific path.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;you are not using a routing protocol, &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;and you are using a single static route to access &lt;/SPAN&gt;&lt;SPAN&gt;192.168.56.0 255.255.255.0 network on the 9300.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;also&lt;SPAN&gt; you need to check both MPLS and VPN routers know the route to the &lt;SPAN&gt;192.168.56.0&lt;/SPAN&gt; subnet?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2019 09:40:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3854898#M314869</guid>
      <dc:creator>pieterh</dc:creator>
      <dc:date>2019-05-13T09:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3907076#M319749</link>
      <description>&lt;P&gt;Were you able to get this issue resolved? I am seeing a similar problem.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2019 20:25:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3907076#M319749</guid>
      <dc:creator>Alex Pfeil</dc:creator>
      <dc:date>2019-08-12T20:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3907122#M319757</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;R&lt;SPAN&gt;egards your ping my understanding the primary interface is always used as source even when you have secondary addressing assign to the same interface.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Just for clarity - you really don’t need these static routes as they are captured by the default static route&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;No ip route 10.0.0.0 255.255.255.0 192.168.34.245&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No ip route 10.40.0.0 255.255.0.0 192.168.34.245&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No ip route 10.40.10.0 255.255.254.0 192.168.34.245&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No ip route 10.75.254.0 255.255.255.0 192.168.34.245&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No ip route 10.75.255.0 255.255.255.0 192.168.34.245&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No ip route 172.24.16.0 255.255.252.0 192.168.34.245&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No ip route 172.24.20.0 255.255.255.0 192.168.34.245&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;Lastly could you try the following:&lt;BR /&gt;&lt;STRONG&gt;no access-list 110 permit ip 10.99.99.0 0.0.0.255 192.168.56.0 0.0.0.255&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;no route-map PBR&lt;BR /&gt;&lt;/STRONG&gt;&lt;STRONG&gt;&lt;BR /&gt;access-list 110 permit ip 192.168.34.0 0.0.0.255 192.168.56.0 0.0.0.255&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;STRONG&gt;route-map PBR_testing deny 10&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;match ip address 110&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;STRONG&gt;route-map PBR_testing permit 99&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;set ip next-hop 192.168.34.245&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2019 22:33:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3907122#M319757</guid>
      <dc:creator>paul driver</dc:creator>
      <dc:date>2019-08-12T22:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: PBR doesn't work on Catalyst 9300 ( VLAN Interface)</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3908150#M319837</link>
      <description>&lt;P&gt;We have a post that is several months old describing an issue with PBR that received a number of suggestions and has no clear indication of whether the issue was solved or not.&amp;nbsp;I found it odd in the original post that the PBR was specifying the secondary address and no mention of the primary address. And I wonder if the issue was that the device was sending using the primary address and not the secondary address.&amp;nbsp;Now&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/293775"&gt;@Alex Pfeil&lt;/a&gt;&amp;nbsp;says he has the same issue but provides no details. Perhaps if we get the details we might have some suggestions about his issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 14:39:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/pbr-doesn-t-work-on-catalyst-9300-vlan-interface/m-p/3908150#M319837</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2019-08-14T14:39:53Z</dc:date>
    </item>
  </channel>
</rss>

