Well, I've certainly managed to replicate some bizare behaviour that is definitely not intended. I've gathered video clip highlighting the behaviour I experienced and attached it to the TAC case.
I've left the VSM server and VSVM endpoint in this state, and I'm confident I could reproduce this behaviour again. I'm awaiting addtional instruction from TAC regarding what additional data they actually require.
VSM is at 6.3.2
VSVM client is at 6.3.409.0
VSVM node is Windows XP, SP3
VSOM workstation is Windows 7 x64, IE8.
Bulletproof Solutions Inc.
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...