at this point if we are in the context admin, we are unable to ping the svi on vlan 192 (10.65.192.1) but of course we ping local interface sucessfully.
same problem on int 196.
we put access list permit ip any any in on both interface but this not resolve.
when on MSFC, we ping local but we dont ping fwsm int192 on the same vlan. strangely, the sh arp command show the ip of the FWSM in router and same command show svi ip in the FWSM. Also, we are unable to telnet from 10.65.192.x to the FWSM.
Do we need something else to permit these elementary things ? we dont set up any nat command at this point.
We also suspect problem communication between the FWSM module and the switch, but if it would be the case, i dont think we would see other module MAC adresse in the arp table.
Join us live on Tuesday, July 14 (and on demand after) to learn what impacts COVID-19 has had on the information security landscape from one of the people living that fight.
We'll take your questions live during the show and after, so post them belo...
TETRA Error Codes - Windows
Here are some common TETRA Error codes that you may find displayed in the dashboard as well as within the C:\Program Files\Cisco\AMP\<your_version>\sfc.exe.log or corresponding sfc.exe_<date>_<time>.logs. The...
Please note that the minimum cryptography settings in AnyConnect 4.9 have been increased. Please ensure that your head-end is properly configured for the more stringent cryptography settings (if applicable) or users will be unable to connect after updatin...
In this guide will we be taking a look at how to configure the web.config file using the URL Rewrite tool when deploying the TETRA update server. This guide is meant as a companion to the existing guides and to help fill in some in...