PA-500 Shows No matching records after upgrade to 4.0.5

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PA-500 Shows No matching records after upgrade to 4.0.5

L2 Linker

Hello!

I have two layer 2 subinterfaces with dropped packets and packets routed to different zone. Rules allow everything and shouldn't block any traffic (except IPS actions). Is there a way (CLI command) to see what traffic Palo blocks?

Another mistery to me are packets routed to different zone. Two layer 2 subinterfaces are part of one VLAN, without configured Layer3 VLAN interface. Traffic is brigded between that two interfaces. Each interface has its zone (in and out). How it is possible for Palo to route packets if there is no routing configured?

Thanks and best regards,

Maja


--------------------------------------------------------------------------------
Name: ethernet1/1.99, ID: 257, 802.1q tag: 99
Operation mode: layer2
Interface management profile: N/A
Service configured:
Zone: Serveri-Out, virtual system: vsys1
Adjust TCP MSS: no
--------------------------------------------------------------------------------

Logical interface counters read from CPU:
--------------------------------------------------------------------------------
bytes received                           29699995102
bytes transmitted                        544402685918
packets received                         121359018
packets transmitted                      3156978226
receive errors                           0
packets dropped                          200319
packets dropped by flow state check      0
forwarding errors                        0
no route                                 0
arp not found                            0
neighbor not found                       0
neighbor info pending                    0
mac not found                            0
packets routed to different zone         52
land attacks                             0
ping-of-death attacks                    0
teardrop attacks                         0
ip spoof attacks                         0
mac spoof attacks                        0
ICMP fragment                            0
layer2 encapsulated packets              0
layer2 decapsulated packets              0
--------------------------------------------------------------------------------

admin@PA-5050> show interface ethernet1/2.9

--------------------------------------------------------------------------------
Name: ethernet1/2.9, ID: 260, 802.1q tag: 9
Operation mode: layer2
Interface management profile: N/A
Service configured:
Zone: Serveri-In, virtual system: vsys1
Adjust TCP MSS: no
--------------------------------------------------------------------------------

Logical interface counters read from CPU:
--------------------------------------------------------------------------------
bytes received                           545904774447
bytes transmitted                        28405124818
packets received                         3164934385
packets transmitted                      113445173
receive errors                           0
packets dropped                          2227286
packets dropped by flow state check      2
forwarding errors                        0
no route                                 0
arp not found                            0
neighbor not found                       0
neighbor info pending                    0
mac not found                            0
packets routed to different zone         371
land attacks                             0
ping-of-death attacks                    0
teardrop attacks                         25
ip spoof attacks                         0
mac spoof attacks                        0
ICMP fragment                            0
layer2 encapsulated packets              0
layer2 decapsulated packets              0
--------------------------------------------------------------------------------

1 ACCEPTED SOLUTION

Accepted Solutions

You can try adding an 'any any deny' security rule at the end of your policy to see if it catches the drop packets.  The drops should then show up in the Traffic Log.  Make sure this 'any any deny' rule is the last rule in your policy.

NOTE: The 'any any deny' rule will deny all traffic that is not explicitly permitted.  Therefore, you may need to add intra-zone rules to permit traffic within each of your zones.  

If the 'any any deny' rule does not produce any drop in the Traffic Log, you can do a packet capture and filter on stage=drop.

If you need help on this, please contact Support.

Thanks.

View solution in original post

5 REPLIES 5

L6 Presenter

Hi...If traffic is blocked by policy, you should see the block event in Monitor Tab ==> Traffic Log.  However from your stats, the counter is showing packet drops.

packets dropped                          200319

Packets may be dropped for a number of reasons (i.e.1st packet of a TCP session is not SYN packet).  From the CLI you can issue these commands to see the drops:

admin@ca2demo> show counter global | match drop
admin@ca2demo> show counter global filter delta yes | match drop

You may want to contact Support to get an explanation on the packets routed to different zone.

Thanks.

Thanks for the reply. This commands are helpful, but how I can see the traffic that is being droped or routed to another zone (IP and/or MAC addresses, ports...)? In Traffic Log I see only allowed sessions, there is no droped or denied sessions.

admin@PA-5050> show log traffic action equal drop
Time                App             From            Src Port   Source
Rule                Action          To              Dst Port   Destination
                    Src User        Dst User
===============================================================================
admin@PA-5050>


admin@PA-5050> show log traffic action equal deny
Time                App             From            Src Port   Source
Rule                Action          To              Dst Port   Destination
                    Src User        Dst User
===============================================================================
admin@PA-5050>

Regards,

Maja

P.S. Sorry for the wrong thread name.

You can try adding an 'any any deny' security rule at the end of your policy to see if it catches the drop packets.  The drops should then show up in the Traffic Log.  Make sure this 'any any deny' rule is the last rule in your policy.

NOTE: The 'any any deny' rule will deny all traffic that is not explicitly permitted.  Therefore, you may need to add intra-zone rules to permit traffic within each of your zones.  

If the 'any any deny' rule does not produce any drop in the Traffic Log, you can do a packet capture and filter on stage=drop.

If you need help on this, please contact Support.

Thanks.

Thanks. I tried that. Capture of droped packets shows VTP packets. And now I have traffic that matches deny any rule.

Regards,

Maja

excellent!!

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!