ScreenOS Firewalls (NOT SRX)
Reply
Contributor
Chuck
Posts: 32
Registered: ‎02-03-2009
0

NSM 2007.3r3 and SGS 140 running v6.1r4

Wonder if anyone has seen any issues with their NSM and SGS firewalls at v6.1r4..  we have recently upgrade several devices to this ops and are now seeing  a Slot error in the configuration record of the firewall on the nsm.   all 5 firewalls have the same slot error message

 

we have an open ticket with JTAC,  but it is only at a priority 4

 

we had to postpone numerous other site upgrades until we see a clear resolution

 

chuck  

Recognized Expert Recognized Expert
Recognized Expert
CB
Posts: 159
Registered: ‎05-09-2008
0

Re: NSM 2007.3r3 and SGS 140 running v6.1r4

Hi Chuck,

 

what model of SSG do you have ?

DId you experience this issue on another mainline release of 6.1 or did you upgrade from 6.0 or earlier straight to 6.1r4 ?

Also can you let me know what card type you have installed in the chassis (get chassis will show this)

 

Thanks


Colin

If this worked for you please flag my post as an "Accepted Solution" so others can benefit.
Contributor
hagbard
Posts: 61
Registered: ‎10-29-2008
0

Re: NSM 2007.3r3 and SGS 140 running v6.1r4

During my upgrade process I just had to select maually "not installed" for the slots in the NSM which showed the error (it was just one in my case). However I do not know if you have any installed ...
Trusted Expert Trusted Expert
Trusted Expert
WL
Posts: 790
Registered: ‎07-26-2008
0

Re: NSM 2007.3r3 and SGS 140 running v6.1r4

For your NSM on 2007.3r3 did you have a schema update? Or is it just the plain 2007.3r3? You would need the schema update to fully support devices on 6.1 Screen OS.
****pls click the button " Accept as Solution" if my post helped to solve your problem****
Contributor
Chuck
Posts: 32
Registered: ‎02-03-2009
0

Re: NSM 2007.3r3 and SGS 140 running v6.1r4

we have the schema updated to 2007.3r3

 

the latest from JTAC as they have been able to reproduce in their labs, is for us to update our schema to 2007.3r5 afterwords they will need to do some modifications on our NSM

 

their intiial solution to the problem did not work,

Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.