ASA Troubleshooting - Application Inspection Trouble

[@keooka]

awesome video my friend, learned two things from you today

[@aquadir2830]

You're a great troubleshooter.. Thanks

[@pepperjackshack2439]

W O W !!! What an amazing video. Helped me debug failed pings like a champ!

[@alejandroreyes2200]

Hi, Thanks for the videos. They are great, keep them coming. Is it possible to do a video on Resets and how to troubleshoot them? I've seen Reset-O and Reset-I in our logs and want to be able to troubleshoot these more effectively. Thanks.

[@Capcut_shorts2016]

AWESOME. NEED MORE VIDEOS

[@TheNihalsalim]

Thank you :)

[@swapnilnagale6577]

Its not clear

[@Phildaexperience]

sweet thanks

[@NA-qo3wp]

So why did changing the LT to EQ fix it is it because so only traffic from port 2000 is sent to Skinny engine thus allowing all other HTTP traffic?

[@namitagrawal738]

Hi Thanks for video, but have one doubt , As earlier Skinny service group is configured less than 200 port (lt 2000) and you corrected to eq 2000... but our Service is only access over Http (80) port.. i believe earlier configuration is matching the access list right ?

[@khurshidkhandy6622]

Hi Sir, unable to find any difference pre and post fix. Can you help me...

[@vikramsharma9312]

Hi Guys , Why this channel stoped . Please let me know if you have otyher channel which is acitve

[@coldbrewmonster7337]

This so wrong, the skinny ACL traffic is lt 2000, therefore HTTP 80 should be allowed and permitted.

[@davidwhite3798]

You misunderstood. The Skinny policy was covering all ports less than 2000. It needed to be modified to only cover port 2000 (hence changing the lt to eq)

[@coldbrewmonster7337]

This is so wrong, changing the lt 2000 to eq 2000 will not fix the problem, because HTTP is port 80 and port 80 is less than 2000 already.

[@davidwhite3798]

HTTP traffic was being treated as Skinny traffic. Please re-watch the videol

[@pepperjackshack2439]

W O W !!! What an amazing video. Helped me debug failed pings like a champ!