The bug-id referenced above is a 4.1 only bug and not related to 5.1. It is possible that you are running into CSCsd33883 which is a loss of config on upgrade to 5.1(1). We've only ever seen it happen on the IDSM2, but it is possible to happen on the appliances (i.e. there is no code specific to the IDSM2). To the best of our knowledge and testing, you should not lose your tunings on service packs in the 5.1(x) train. If you are experiencing this trouble, please open a TAC case and they will get the information to the Dev team.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
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...