1.) Looking at the network mask used in the interface it seems that the standby IP address is configured wrong. Also, there is not supposed to be any configurations related to the standby IP address. I mean no NAT configurations or access-list statements as its just there for the Failover to work. (To my understanding)
2.) What you should do is configure another IP from the same network range as the primary IP. When you change the standby IP address you naturally only configure it on the active device as the standby device automatically receives the configuration change from the primary device (provided that the actual failover is working properly)
3.) The IP ending in .120 cannot be used as its not from the same network range as .100 (when you are using a mask of /29) When you have a correct IP address from same network configured on the standby ASA you should be able to ping it and also see it on the "show arp" command on the ASA
Posting this for anyone interested in using a Raspberry PI as a flow collector for Stealthwatch. We created a very lightweight version of our software. It can create flows if the eth port is attached to a SPAN or you can forward NetFlow/IPFIX ...
Dear Team Suppose we have hundreds of rules in access policy on cisco fmc device. Now I want to fetch all access policy rules in which I have mentioned some specific port number X. Can anyone help me with the process to fetch the same?
Greetings everyone, Happy New Year! I would like to thank you all for making our ISE demos in dCloud a great success!
The ISE instant demo has been in the top 5 of Enterprise demos for a long time now and recently just moved into the #1 and 2 slots...
User Experience Enhancements
As part of the Cisco Common User Experience program, we are working towards a more uniform user experience and terminology alignment. This program runs across all Cisco security products.
A More Intuitive Cognitiv...