Screen OS

Dear Team,

I am trying to update ISG-IDP Detector Engine but getting Java error as given below:

Error Code:

Error Text:
java.lang.Exception cannot be cast to com.netscreen.devicecomm.DeviceException

Error Details:
No Details Available.

Screenshot of error attached.

So please help to resolve the issue

Current Detector Enging details are given below

IDP files version:
detector2.so 3.5.140185
engine 3.4.139311
pcid 3.4.139311
scio 3.4.139311

HI Prem,

Please check if the device is shown UP in the NSM.

Also, check CPUs on the SM module, they should be shown as 'Ready'.

Command to check CPU status on device:

->get chassis

Cheers,

Dipanshu

Hello Dipanshu,

Thanks for reply,

Device is showing UP in NSM, find attached screeshot of the same.

aslo find below get chassis command output its showing SM module CPU in ready state.

-> get chassis
Chassis Environment:
Power Supply: Good
Fan Status: Good
CPU Temperature: 114'F ( 46'C)
Slot Information:
Slot Type S/N Assembly-No Version Temperature
0 System Board 0079102011000062 0051-005 F07 86'F (30'C), 96'F (36'C)
4 Management 0252112011000022 0049-004 D19 114'F (46'C)
1 Security 0137012012000076 0067-002 B05 cpu1:Ready, cpu2:Ready
2 Security 0137102011000008 0067-002 B05 cpu1:Ready, cpu2:Ready
3 Security 0137022012000027 0067-002 B05 cpu1:Ready, cpu2:Ready
5 ASIC Board 002321647l110014 0051-005 C03
Marin FPGA version 9, Jupiter ASIC version 1, Fresno FPGA version 110
I/O Board
Slot Type S/N Version FPGA version
1 2 port mini GBIC (0x5) 0141042007000208 C00 8
2 2 port mini GBIC (0x5) 0141032007000203 C00 8
Alarm Control Information:
Power failure audible alarm: disabled
Fan failure audible alarm: disabled
Low battery audible alarm: disabled
Temperature audible alarm: disabled
Normal alarm temperature is 132'F (56'C)
Severe alarm temperature is 150'F (66'C)

Please help to resolve the issue.

regards,

Prem

Hi Prem,

SMs appears to be in good state. Could you please try to update with the following procedure , if possible:

1. Reboot box
2. Import device to NSM again.
3. Update idp policy but not detector to box first.
4. Update detector

Always, make sure you have the latest attack db and detector on NSM as well as on device. Also, try to update the attack db and detector during off business hours/low traffic time.

If still issue persists, then contact Juniper Support for further debugging.

Cheers,

Dipanshu

Hello Dipanshu,

Thanks.

I have reboot Both NSM Server and IDP ISG2000.

And then try to updat e IDP Detector Engine and 

SUCCESS!!!!!!!!!

Regards,

Prem