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.

LMS 2.6 - 1) disappeared interfaces in DFM 2) selfclosing window

We have LMS 2.6.

In our net we use CISCO routers 2811 and Interface type Tunnel was configured on it. So IP address of this tunnel-interface is not reachable from CiscoWorks-server. DFM has showed alerts for this trouble and we changed Management State from "true" to "false" for Tunnel-interface on all 2811 routers.

Problem1: after last restart CiscoWorks-server new alerts was appeared in DFM - not reachable IP-addresses on tunnel-interfaces and now we does not see this interfaces in Detailed Device View and can not change their Management State. So we have some wrong alerts now. I tried to delete device by Device Management and add it again but I have no result - tunnel-interface did not appear in list of interfaces in Detailed Device View.

How we can get correct information in Detailed Device View and managament it?

Problem2: For one device we can't open window of Detailed Device View - in DFM Alerts and Acivities I click on device name, window is opened and instantly closed. How we can understand what's wrong with it?

Thanks in advance.

Everyone's tags (2)
2 REPLIES
Cisco Employee

Re: LMS 2.6 - 1) disappeared interfaces in DFM 2) selfclosing wi

Post the NMSROOT/log/dfmLogs/DDV/DDV.log.  What version of DFM is this?

Re: LMS 2.6 - 1) disappeared interfaces in DFM 2) selfclosing wi

If I understand correct DFM = Device Fault Manager.

So DFM version is:

Version & Patch Level:
2.0.13

This spam into DDV.log

02-Mar-2010|11:46:02.927|ERROR|DDV|Ajp13Processor[9009][11]|DDVSaxParser|Parse|.|Exception 4 is:org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1258ad) was found in the element content of the document.
02-Mar-2010|11:46:02.927|ERROR|DDV|Ajp13Processor[9009][11]|DDVAction|main|.|
02-Mar-2010|11:48:04.599|ERROR|DDV|Ajp13Processor[9009][8]|DDVSaxParser|Parse|.|Exception 4 is:org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1258ad) was found in the element content of the document.
02-Mar-2010|11:48:04.599|ERROR|DDV|Ajp13Processor[9009][8]|DDVAction|main|.|
02-Mar-2010|11:48:08.052|ERROR|DDV|Ajp13Processor[9009][0]|DDVSaxParser|Parse|.|Exception 4 is:org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1258ad) was found in the element content of the document.
02-Mar-2010|11:48:08.052|ERROR|DDV|Ajp13Processor[9009][0]|DDVAction|main|.|
02-Mar-2010|11:48:15.631|ERROR|DDV|Ajp13Processor[9009][8]|DDVSaxParser|Parse|.|Exception 4 is:org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1258ad) was found in the element content of the document.
02-Mar-2010|11:48:15.631|ERROR|DDV|Ajp13Processor[9009][8]|DDVAction|main|.|
02-Mar-2010|11:48:37.615|ERROR|DDV|Ajp13Processor[9009][11]|DDVSaxParser|Parse|.|Exception 4 is:org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1258ad) was found in the element content of the document.
02-Mar-2010|11:48:37.615|ERROR|DDV|Ajp13Processor[9009][11]|DDVAction|main|.|
15-Mar-2010|15:39:20.655|ERROR|DDV|Ajp13Processor[9009][2]|DDVSaxParser|Parse|.|Exception 4 is:org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1258ad) was found in the element content of the document.
15-Mar-2010|15:39:20.655|ERROR|DDV|Ajp13Processor[9009][2]|DDVAction|main|.|

321
Views
0
Helpful
2
Replies