Hi;    Yup, the way to do it would be using syslogs. That is the best way to troubleshoot it.  If you have a syslog server, you can go back and correlate the last time if failed and check the reason for the teardown.    ... View more

What version of ASDM are you running? ... View more

Awesome.  When you upgraded the Firewall version, did you also upgrade the ASDM? What ASDM version are you using?    ... View more

Hi,    Would you be able to describe the steps to reproduce this problem?  Mike.  ... View more

If due to security reasons you cannot share the configuration, I would suggest opening a TAC ticket, because we might need to see the entire configuration to verify where the error is.    Mike.  ... View more

I honestly don't think it is version related.  Is  the x.x.x.x the Public IP address of the firewall? If so, if ASDM is enable, you will get this error message.    Mike.    ... View more

My 2 cents, you need to first identify why the connection is being closed prior extending the timeout of it.  Nothing good comes out of changing the default timeout values. If the connection needs to stay up for periods longer than 1 hour, I recommend using DCD to verify if the peer has the socket open still and leave the conn open.   This should be done for the peers you are having troubles with only, and not a global setting.  Here is the configuration example for it:    https://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/firewall/asa_91_firewall_config/conns_connlimits.html#pgfId-1231374     ... View more

Have you discard any connectivity problems? If the user is authentication is not timing out (show uauth), the only thing that comes to mind is that the connection to the ASDM is lost and then you have to authenticate again.    I would have a syslog server logging everything and then check when it asks you to authenticate again and see if the SSL session got deleted.    ... View more

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv73250/?reffering_site=dumpcr ... View more

Hello:  num-packets   number no num-packets   number Syntax Description number The number of packets sent during an SLA operation. Valid values are from 1 to 100. Note   When all the packets specified as the number argument (in this command) are lost, the tracked route has failed.   https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/I-R/cmdref2/n.html#pgfId-1815481   Mike.  ... View more

Hi;    You can upgrade directly to the desired version. Check "Upgrading the Software"  https://www.cisco.com/c/en/us/td/docs/security/asa/asa91/release/notes/asarn91.html#pgfId-763574   I would strongly recommend to find a supported version since 9.1 is going EOL.    https://www.cisco.com/c/en/us/products/collateral/security/asa-firepower-services/eos-eol-notice-c51-738645.html   If you have any questions, let us know.  Mike.  ... View more

I dont think this is going to work. The only way to pass that broadcast would be creating a BVI interface and bridging the traffic, but it needs to be on the same Broadcast domain. ... View more

OK, what happens if you try to ping devices on both vlans? Do you have ARP entries for both vlans? Show ARP.      ... View more

Do you have an IP address for both Bridge groups? Do you have SVIs on the switch?  Mike.  ... View more