cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1569
Views
11
Helpful
6
Replies

DFM 2.0.4 ICMP ping SNMP poll

miheg
Level 5
Level 5

I have a customer that would like to use only SNMP to monitor his network and not allow any ICMP between the DMZ and the internal network.

I thought the reachablilty setting in DFM was related to the Ping DFM sends and my first idea was that disabling this would stop DFM from pinging but would still allow DFM to SNMP poll the interfaces operational status via the device loopback.

First surprise

After applying the disabled reachability setting and rediscovering the devices I still get " Unresponsive" events. Only after deleting devices and bringing them back in via the device selector, DFM listens to its configuration and stops pinging.

Second surprise

Someone pulls a cable in the lab.....no events......link is red in Campus. DFM fails to poll the interface or finds another excuse for not giving an event.

I reenable the availability settings and apply....almost instantly get

" Unresponsive" and "OperationallyDown" events.

My conclusion: If DFM can't ping it will not SNMP poll and it cannot properly manage the device.

Is this correct? Comments anyone?

Third surprise:

The mail notifier still doesn't work. This is mentioned to be fixed in 2.04. I enabled the syslog notifier but no joy there either. It seems no event reaches the adapters.

Cheers,

Michel

1 Accepted Solution

Accepted Solutions

frankzehrer
Level 4
Level 4

I have forgotten to attach the batch file in my first post.

;-))

Cheers

Frank

View solution in original post

6 Replies 6

frankzehrer
Level 4
Level 4

Hi Michel,

i hope i may give you some hints here. as you did to me with many of your comments here in the forum.

For your ICMP - SNMP problem i rembered a similiar task at a costumer site.

Pleas note the following from the User Guide:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm203/ug/snmpinfo.htm

Coordinating ICMP and SNMP Polling

DFM links its ICMP and SNMP pollers; the SNMP poller will not send requests to any SNMP agent IP address that the

ICMP poller has determined is unreachable. These IP addresses are added to a do not poll list, which the SNMP

poller checks before sending SNMP requests. It does not send requests to addresses on this list.

If the SNMP agent has multiple IP addresses, the SNMP poller checks for each address in the do not poll list:

If an address does not appear on the list, the SNMP poller sends a request to it.

If all addresses for an agent are on the list, the SNMP poller considers the agent unreachable and temporarily

suspends sending SNMP requests to it. As soon as an agent's IP address becomes responsive (per the IMCP poller),

the address is removed from the list, and SNMP polling resumes.

To the NOS (Notifier) I had the same problem with DFM 2.04 on a windows box.

The TAC provided me a script that reinitialized the NOS and since then its working fine:

Just copy the lines into a text file and rename it to somthing like nos_fix.bat.

Take care of different installation paths. I have LMS installed on D:\ drive. Just replace D:\ with whatever

matches to you.

D:\PROGRA~1\CSCOpx\MDC\jre

- - - - - - - - - - - - - - - - - - - - - - - -

@ECHO OFF

SET OCWD=%CD%

cd %CWMIBDIR%\..\..\..

SET NMSROOT=%CD%

cd %OCWD%

CALL %NMSROOT%\bin\pdreg.cmd -u NOSServer

CALL %NMSROOT%\bin\pdreg.cmd -r NOSServer -d "EPMDbEngine,EPMServer,INVDbEngine,PMServer,DFMOGSServer" -e

%NMSROOT%\bin\cwjava.exe -f

"^-server^-cp:p^MDC\tomcat\webapps\triveni\WEB-INF\lib\log4j.jar;MDC\tomcat\webapps\triveni\WEB-INF\lib\nos.jar;M

DC\tomcat\webapps\triveni\WEB-INF\lib\ctm.jar;MDC\tomcat\webapps\triveni\WEB-INF\lib\ogs-client.jar;MDC\tomcat\we

bapps\triveni\WEB-INF\lib\cogs.jar;MDC\tomcat\webapps\triveni\WEB-INF\lib\ogs-kc1.0.jar;MDC\tomcat\webapps\triven

i\WEB-INF\lib\ogs-kilnervirtualasa1.0.jar;MDC\tomcat\webapps\triveni\WEB-INF\lib\activation.jar;MDC\tomcat\webapp

s\triveni\WEB-INF\lib\mail.jar;MDC\tomcat\webapps\triveni\WEB-INF\lib\tis-client.jar;MDC\tomcat\webapps\triveni\W

EB-INF\lib\pm.jar;lib\classpath\jconn2.jar;lib\classpath\epm-v0-5-0.jar;lib\classpath\cesar-v0-5-0b.jar;MDC\tomca

t\shared\lib\NATIVE.jar;MDC\tomcat\shared\lib\MICE.jar;MDC\bin;objects\nos\config;MDC\tomcat\webapps\triveni\WEB-

INF\classes;MDC\tomcat\webapps\triveni\WEB-INF\lib\ogs-util.jar;^-cw:jre^D:\PROGRA~1\CSCOpx\MDC\jre^-cw:xrs^-Djav

a.compiler=NONE com.cisco.nm.trx.nos.server.NOSServer"

I hope that helps.

Best reagrds,

Frank

The reaction of the DFM here is headless chicken

There are some interfaces on a device that cannot be pinged. But the management interface can be pinged and SNMP polled.

Turning off the "reachability" setting seems to place the device and probably all devices in that group on the do not poll list as DFM doesn't notice that an interface went down.

It still seems unbelievable to me that DFM works this way.

Anyway, should this NOS reregistration happen with CW crmdmgtd service stopped?

I have not tried this sort of thing before.

Cheers,

Michel

frankzehrer
Level 4
Level 4

Hi Michel,

Maybe you are running Solaris. Then try this.

- - - - - - - - - - - - - - - - - - - - - - - -

/opt/CSCOpx/bin/pdreg -u NOSServer

/opt/CSCOpx/bin/pdreg -r NOSServer -d "EPMDbEngine,EPMServer,INVDbEngine,PMServer,DFMOGSServer" -e

/opt/CSCOpx/bin/cwjava -f

"^-server^-cp:a^MDC/tomcat/webapps/triveni/WEB-INF/lib/ItemLogService.jar:MDC/tomcat/webapps/triveni/WEB-INF/lib/

log4j.jar:MDC/tomcat/webapps/triveni/WEB-INF/lib/nos.jar:MDC/tomcat/webapps/triveni/WEB-INF/lib/ctm.jar:MDC/tomca

t/webapps/triveni/WEB-INF/lib/ogs-client.jar:MDC/tomcat/webapps/triveni/WEB-INF/lib/cogs.jar:MDC/tomcat/webapps/t

riveni/WEB-INF/lib/activation.jar:MDC/tomcat/webapps/triveni/WEB-INF/lib/mail.jar:MDC/tomcat/webapps/triveni/WEB-

INF/lib/tis-client.jar:MDC/tomcat/webapps/triveni/WEB-INF/lib/pm.jar:lib/classpath/jconn2.jar:lib/classpath/epm-v

0-5-0.jar:lib/classpath/cesar-v0-5-0b.jar:MDC/tomcat/shared/lib/NATIVE.jar:MDC/tomcat/shared/lib/MICE.jar:MDC/bin

:objects/nos/config:MDC/tomcat/webapps/triveni/WEB-INF/classes^-cw:jre^/opt/CSCOpx/MDC/jre^-Djava.compiler=NONE

com.cisco.nm.trx.nos.server.NOSServer

- - - - - - - - - - - - - - - - - - - - - - - -

I have not seen the NOS problem on a Solaris box until now. So i have adapted my working NOS environment with the

information from the Windows case. I have tested this and it worked for me.

I hope i did not made something wrong with the solaris code.

:-)

Best regards,

Frank

frankzehrer
Level 4
Level 4

I have forgotten to attach the batch file in my first post.

;-))

Cheers

Frank

Thanks a million Frank.

I have a TAC case open, but I think you may have solved the issue.

I will try this ASAP.

Cheers,

Michel

DFM sends mail now.

Issue resolved

Thanks again Frank!