After update of NSMxpress custom service objects have changed source-port range

05.31.12   |  
‎05-31-2012 12:48 AM

Yesterday I installed patch nsm2010.3s5 and applied schema 229. Due to this actions the
source port range of all of our custom services objects changed from 0-65535 into
1-65535. This means I'm unable to roll out any changes because on an update all policies
and objects on a ScreenOS device will get deleted and newly created with the changed
source port range. This would mean losing all affected sessions...


I heard some rumors that this is a common issue on NSM updates and that there would be a script which may fix this by walking through the database.


The appliance is for years out of support, thus JTAC won't help at all Smiley Embarassed  Please advise.