Management
Management

NSM 2010.4 - Fail to import SA device

04.26.11   |  
‎04-26-2011 06:13 AM


Hi All,

I have installed NSM 2010.4 on Redhat 5.6 with 158 schema version which fails to import SA-4000 device config

Config status is "import needed".

When I try to import the config through Devices-->Configuration-->Import device config
on "Job Information" box for import config "Job Type", the completion progress stuck at 10% with Pending Description for a long time.
Where the completion runs to a 100% with Failed status, gives the following error
 
"Error Code:

Error Text:
   Import Device Configuration Failure !.
ImportDevice Results
get-config Failed .
null

Error Details:
    No Details Available."

Deleting the SA from the NSM and importing it again won't help even the schema version have been updated to 178.

Is there any of you have an experince with this?

Thanks and Regards,
Isman

5 REPLIES
Management

Re: NSM 2010.4 - Fail to import SA device

[ Edited ]
04.26.11   |  
‎04-26-2011 01:34 PM

Can you check following?

1) related NSM logs ... NSM DevSvr processes names, definitions, and error logs filenames ... http://kb.juniper.net/InfoCenter/index?page=content&id=KB11829

2) How to troubleshoot NSM Delta Config or Device Update Issues ... http://kb.juniper.net/InfoCenter/index?page=content&id=KB9845

Management

Re: NSM 2010.4 - Fail to import SA device

[ Edited ]
02.15.12   |  
‎02-15-2012 10:29 AM

I have this same problem with NSM 2011.1s1.

 

I have a standalone SA4000 and an SA4500 cluster. All fail to import the config.

 

Error Code:

Error Text:
   Import Device Configuration Failure !.
ImportDevice Results
get-config Failed .
null

Error Details:
    No Details Available.

Management

Re: NSM 2010.4 - Fail to import SA device

03.02.12   |  
‎03-02-2012 10:32 AM

Did anyone have a resolution to this issue? I am experiencing the same problem on NSM2011.4 with SA6500 running 7.1r3

Management

Re: NSM 2010.4 - Fail to import SA device

06.25.13   |  
‎06-25-2013 07:58 AM

Same problem. Any solution?

NSMExpress 2012.2

SA 4500 cluster

Management

Re: NSM 2010.4 - Fail to import SA device

06.27.13   |  
‎06-27-2013 12:53 AM

To resolve my problem I delete the SA from the NSM and add it again with another name.

And It works.