Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CSM error when adding IDSM-2

Hi,

I get the following error when trying to add an IDSM-2 blades to CSM:

"Invalid device: Could not deduce the SysObjId for the platform type

WS-SVC-IDSM-2"

I have successfully added another IDSM-2 blade running the same vesion.

The version is:

sensor# sh ver

Application Partition:

Cisco Intrusion Prevention System, Version 6.2(1)E3

Host:

Realm Keys key1.0

Signature Definition:

Signature Update S365.0 2008-10-31

Virus Update V1.4 2007-03-02

OS Version: 2.4.30-IDS-smp-bigphys

Platform: WS-SVC-IDSM-2

Serial Number: SAD09200865

No license present

Sensor up-time is 15 min.

Using 1410576384 out of 1983508480 bytes of available memory (71% usage) application-data is using 41.6M out of 166.8M bytes of available disk space (26%

usage)

boot is using 39.7M out of 68.6M bytes of available disk space (61% usage) application-log is using 529.7M out of 2.8G bytes of available disk space (20% u

sage)

MainApp E-2008_OCT_16_16_24 (Release) 2008-10-16T16:40:57-0500 Ru

nning

AnalysisEngine E-2008_OCT_16_16_24 (Release) 2008-10-16T16:40:57-0500 Ru

nning

CLI E-2008_OCT_16_16_24 (Release) 2008-10-16T16:40:57-0500

Upgrade History:

IPS-K9-6.2-1-E3 16:24:00 UTC Thu Oct 16 2008

Maintenance Partition Version 2.1(2)

Recovery Partition Version 1.1 - 6.2(1)E3

Host Certificate Valid from: 12-Nov-2008 to 13-Nov-2010

sensor#

1 REPLY
Bronze

Re: CSM error when adding IDSM-2

think that you might be hitting the bug id CSCsm72131.This error message is given when CSM user attempts to Add an IDS/IPS device or Discover Policies on an IDS/IPS device whose platform string changed in IPS software 6.0(4)E1. Or, CSM user attempts to Add a device or Discover Policies on a device whose platform string is not supported by CSM.

Replace the original VMS-SysObjID.xml file ( by default located in the C:\Program Files\CSCOpx\MDC\athena\config\ directory) with the attached (updated)

VMS-SysObjID.xml file. Afterwards, restart the 'Cisco Security Manager Daemon

Manager' service (CRMDmgtd), and re-try adding or discovering the affected

device(s) again.

258
Views
0
Helpful
1
Replies
CreatePlease login to create content