Hi, I have been lucky enough to get my hands on 3 of these devices to install. Great machines !!!!
I am having a difference of opionion with the collegue who has designed the solution. He has designed it with 3 Virtual Contexts all using shared interfaces. i.e all 3 VC's share the outside and inside interfaces.
He is of the opinion, that he only needs to put ip addresses on the 'admin' context interfaces, and not the other 2 contexts, his reasoning is that when the packets are classified the ASA will direct the traffic to the correct VC.
Now I have been fiddling on these for some time, and I cannot get it to work without ip addresses on the interfaces of each virtual context. My view is that each and every virtual context interface requires it's own ip address. (On a side note, I can get traffic into a VC without a ip address, but just cannot get it to exit)
Can you please confirm for me if each VC interface requires an ip address when the interfaces are shared i.e. VC 1 outside 10.1.1.1, VC 2 outside 10.1.1.2, VC 3 10.1.1.3 etc, I have read alot of literature, and cannot find it specifically stated, hence why there is disagreement.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...