rss.livelink.posts-in-node

Re: How to create custom topology view in NNMi

Abubakar-Acc — Mon, 13 Jan 2020 13:42:40 GMT

You previous post to create topology view with in the same node group helped.

Can you please help to understand as how the topology view can be created to created connection between multiple node groups.

Eg. we have 4 locations . each location devices are in respective node groups. How we can create a connection between these 4 node groups to show in topology view.

Thanks

Enhance custom poller to query multiple tree MIB instances

ramesh9 — Mon, 13 Jan 2020 08:25:56 GMT

Dear

I am trying to use Custom poller to query WIFI Clients performance using below OIDs,

Client name : 1.3.6.1.4.1.14179.2.1.4.1.3
Client SNR ( Signal to noise ratio ) : 1.3.6.1.4.1.14179.2.1.6.1.26
Client RSSI ( Received Signal Strength Indicator ) : 1.3.6.1.4.1.14179.2.1.6.1.1
Client TX Excessive retries : 1.3.6.1.4.1.14179.2.1.21.1.2

I had configured MIB filter as 1.3.6.1.4.1.14179.2.1.4.1.3

However when I see results, I see no value collected for below OID,

Client TX Excessive retries : 1.3.6.1.4.1.14179.2.1.21.1.2

This is because MIB tree for this OID is different from MIB filter.

Please enhance custom poller to collect value from multiple MIB tree branch or remove MIB filter option to collect values from required OIDs.

Re: Creating Different Maps from the existing Default Map

Abubakar-Acc — Sun, 12 Jan 2020 13:53:36 GMT

Dear ,

Can you please share the complete steps you followed to get your requirement fulfill...

I also have similar requirement so wanted it for reference.

Thanks
Abubakar Mohammed

Re: Hostname field with IP address

connection — Sat, 11 Jan 2020 08:32:33 GMT

This issue resolved after running the task discover driver. thanks for your help

error while adding probe in QA

connection — Sat, 11 Jan 2020 08:30:37 GMT

Hi Everyone

Getting an error while adding the probe. it always says source hostname can not be empty, please find the log

2020-01-11 13:54:07,189 SEVERE [com.hp.ov.nms.spi.utils.services.NodeServiceImpl] javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:181)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:161)
at com.sun.proxy.$Proxy519.getNodes(Unknown Source)
at com.hp.ov.nms.spi.utils.services.NodeServiceImpl.listNodesByFilter(NodeServiceImpl.java:627)
at com.hp.ov.nms.spi.utils.services.NodeServiceImpl.findByUuid(NodeServiceImpl.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.interceptors.container.ContainerMethodInvocationWrapper.invokeNext(ContainerMethodInvocationWrapper.java:72)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:76)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:62)
at sun.reflect.GeneratedMethodAccessor259.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:74)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_1703404407.invoke(InvocationContextInterceptor_z_fillMethod_1703404407.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:90)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_1703404407.invoke(InvocationContextInterceptor_z_setup_1703404407.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.async.impl.interceptor.AsynchronousServerInterceptor.invoke(AsynchronousServerInterceptor.java:128)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.core.context.SessionInvocationContextAdapter.proceed(SessionInvocationContextAdapter.java:95)
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:234)
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.notSupported(CMTTxInterceptor.java:329)
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:207)
at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at com.hp.ov.nms.as.server.security.NmsEjbAuthenticationInterceptor.invoke(NmsEjbAuthenticationInterceptor.java:177)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:333)
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:390)
at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.ejb3.proxy.impl.handler.session.SessionLocalProxyInvocationHandler$LocalContainerInvocation.invokeTarget(SessionLocalProxyInvocationHandler.java:184)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor.invoke(AsynchronousClientInterceptor.java:143)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.proxy.impl.handler.session.SessionLocalProxyInvocationHandler$LocalInvokableContextHandler.invoke(SessionLocalProxyInvocationHandler.java:159)
at com.sun.proxy.$Proxy160.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:185)
at com.sun.proxy.$Proxy535.findByUuid(Unknown Source)
at com.hp.ov.nms.spi.qa.war.probeadmin.NnmDetail.getByNodeUuid(NnmDetail.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.directwebremoting.impl.CreatorModule$1.doFilter(CreatorModule.java:172)
at org.directwebremoting.impl.CreatorModule.executeMethod(CreatorModule.java:184)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:353)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:306)
at org.directwebremoting.dwrp.BaseCallHandler.handle(BaseCallHandler.java:110)
at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:211)
at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:185)
at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:144)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:593)
at com.hp.ov.nms.as.server.tomcat.AbstractWebAuthenticator.invoke(AbstractWebAuthenticator.java:163)
at com.hp.ov.nms.as.server.tomcat.NmsWebAuthenticator.invoke(NmsWebAuthenticator.java:26)
at com.hp.ov.nms.as.server.tomcat.NmsCsrfValve.invoke(NmsCsrfValve.java:135)
at com.hp.ov.nms.as.server.tomcat.NmsLocaleValve.invoke(NmsLocaleValve.java:65)
at com.hp.ov.nms.as.owasp.NmsOwaspFilterValve.invoke(NmsOwaspFilterValve.java:997)
at com.hp.ov.nms.as.server.security.NmsAsSecurityValve.invoke(NmsAsSecurityValve.java:20)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:397)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:540)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Could not transmit message
at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:268)
at org.jboss.ws.core.client.transport.NettyClient.invoke(NettyClient.java:125)
at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:157)
at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:69)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:369)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
... 114 more
Caused by: org.jboss.ws.WSException: Invalid HTTP server response [401] - Unauthorized
at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:232)
... 119 more

2020-01-11 13:54:07,192 SEVERE [com.hp.ov.nms.spi.utils.services.NodeServiceImpl] java.rmi.RemoteException: Error occured getting nodes by filter for get nodes
at com.hp.ov.nms.spi.utils.services.NodeServiceImpl.listNodesByFilter(NodeServiceImpl.java:634)
at com.hp.ov.nms.spi.utils.services.NodeServiceImpl.findByUuid(NodeServiceImpl.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.interceptors.container.ContainerMethodInvocationWrapper.invokeNext(ContainerMethodInvocationWrapper.java:72)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:76)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:62)
at sun.reflect.GeneratedMethodAccessor259.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:74)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_1703404407.invoke(InvocationContextInterceptor_z_fillMethod_1703404407.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:90)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_1703404407.invoke(InvocationContextInterceptor_z_setup_1703404407.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.async.impl.interceptor.AsynchronousServerInterceptor.invoke(AsynchronousServerInterceptor.java:128)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.core.context.SessionInvocationContextAdapter.proceed(SessionInvocationContextAdapter.java:95)
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:234)
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.notSupported(CMTTxInterceptor.java:329)
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:207)
at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at com.hp.ov.nms.as.server.security.NmsEjbAuthenticationInterceptor.invoke(NmsEjbAuthenticationInterceptor.java:177)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:333)
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:390)
at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.ejb3.proxy.impl.handler.session.SessionLocalProxyInvocationHandler$LocalContainerInvocation.invokeTarget(SessionLocalProxyInvocationHandler.java:184)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor.invoke(AsynchronousClientInterceptor.java:143)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.proxy.impl.handler.session.SessionLocalProxyInvocationHandler$LocalInvokableContextHandler.invoke(SessionLocalProxyInvocationHandler.java:159)
at com.sun.proxy.$Proxy160.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:185)
at com.sun.proxy.$Proxy535.findByUuid(Unknown Source)
at com.hp.ov.nms.spi.qa.war.probeadmin.NnmDetail.getByNodeUuid(NnmDetail.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.directwebremoting.impl.CreatorModule$1.doFilter(CreatorModule.java:172)
at org.directwebremoting.impl.CreatorModule.executeMethod(CreatorModule.java:184)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:353)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:306)
at org.directwebremoting.dwrp.BaseCallHandler.handle(BaseCallHandler.java:110)
at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:211)
at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:185)
at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:144)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:593)
at com.hp.ov.nms.as.server.tomcat.AbstractWebAuthenticator.invoke(AbstractWebAuthenticator.java:163)
at com.hp.ov.nms.as.server.tomcat.NmsWebAuthenticator.invoke(NmsWebAuthenticator.java:26)
at com.hp.ov.nms.as.server.tomcat.NmsCsrfValve.invoke(NmsCsrfValve.java:135)
at com.hp.ov.nms.as.server.tomcat.NmsLocaleValve.invoke(NmsLocaleValve.java:65)
at com.hp.ov.nms.as.owasp.NmsOwaspFilterValve.invoke(NmsOwaspFilterValve.java:997)
at com.hp.ov.nms.as.server.security.NmsAsSecurityValve.invoke(NmsAsSecurityValve.java:20)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:397)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:540)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

2020-01-11 13:54:07,193 WARNING [com.hp.ov.nms.spi.qa.war.probeadmin.NnmDetail] Exception looking up node in NNM 8b3df1db-d706-4071-ab4e-fd13b17592fe. Exception: Error occured getting nodes by filter

please advice

THanks

Re: Ping (from server) does not fetch nodename

FrankMortensen — Fri, 10 Jan 2020 14:04:48 GMT

I totally agree regarding a config export first. I thought, however, that a simple disable/enable operation would not change the owner. Anyway, no big deal.

We will probably schedule installation of Patch 3.

Cheers,
Frank

Re: Ping (from server) does not fetch nodename

Eugene Kopyshev — Fri, 10 Jan 2020 13:54:05 GMT

Frank,

Most simple way that is to restore from recent valid backup! I encourage everyone to keep doing nnmconfigexport before every experiment in configuration. In a worse case, if nothing on the hand, this field is adjustable by a direct DB update.

Finally, have installed patch 3 which is latest one?

Continue on device error

BeniG — Fri, 10 Jan 2020 13:49:34 GMT

Hey

Hopefully one of you has a good idea for my problem.

Is there any option for simple config- / diagnostic-scripts in NA to continue on device errors? For example:

I have to adapt an ACL which exists on some devices but not on others. To keep the configs as homogeneous as possible, my approach was; Rollout a change-plan that deletes and recreates the ACL from scratch but this will fail since the deletion of the ACL ("no ip access-list ACL") will fail with an error on devices that don't have the ACL yet.

Same thing for a diagnostics job - For an upcoming change we wanted to create a Diagnostics to check pre/post change. This diagnostic included some specific commands that will lead to an "unknown command" error on devices that don't have a specific feature active (e.g: PIM or BGP on Nexus).

Is there such an option anywhere in NA? Or is it possible to overwrite the standard_error pattern? I'm aware I could do this with multiple diagnostics / change-plans or with advanced scripts, but from an operational point of view it would be a lot easier to handle with just one task.

Re: Ping (from server) does not fetch nodename

FrankMortensen — Fri, 10 Jan 2020 13:47:11 GMT

Thanks for the suggestion. Please recall that this problem occurred after the upgrade and did not exist before the upgrade. Thus the "Customer owned" menu entry hypothesis does not make sense 🙂

I had a look at the menu entry definition, though, because it made me curious. The entry was owned by Network Node Manager on both NNMi-systems, both the working one and the non-working one. Furthermore, i was not able to see any info. regarding which parameter was sent to the menu entry there? I.e. whether it is $uuid or not.

I tried to disable and enable the entry, just to see if this made a difference. It did not, unfortuantely. And this attempt changed the owner from Network Node Manager to Customer 😞 Is there an easy way to change this back?

Cheers,
Frank

Re: NNMi 2019.05 P2 - Bug in nnmbackup.ovpl

Eugene Kopyshev — Fri, 10 Jan 2020 11:44:26 GMT

Frank,

Yes, I also used NNM201905W_00002.msi in my lab. I have not installed it, I have just used msiexec /a /qp to extract all files. And the nnmbackup.ovpl is Okay there... Let me check with F166

Re: NNMi 2019.05 P2 - Bug in nnmbackup.ovpl

FrankMortensen — Fri, 10 Jan 2020 11:50:44 GMT

Hi Eugene,

Thanks for checking. The bug is definately there. Are you looking at the Patch2 files for Windows? Because that is the platform that we are on. The date of the Patch2 installation file (NNM201905W_00002.msi) that I downloaded is December 2. I assume the bug has not silently been fixed in the Patch2 install image that is available now, no? 🙂

The creation time stamp of the buggy nnmbackup.ovpl file on our NNMi-server is 2019-11-18 03:35 (we are on CET, I assume the time is shown based on our time zone).

Just to make sure, I have today unpacked all files in NNM201905W_00002.msi. In this image the backup-script seems to be called F166_nnmbackup.ovpl. I can see the same bug there. I.e. a mismatch between the number of parameters being sent when the processFile function is called to deal with the database (i.e. the line containing the phrase "database restoration") and the number of parameters handled by the actual processFiles function. The problem only applies to this particular call to the function. The other calls to the same function are ok.

Cheers,
Frank

Re: NNMi 2019.05 P2 - Bug in nnmbackup.ovpl

Eugene Kopyshev — Fri, 10 Jan 2020 08:45:46 GMT

Hi Frank,

I checked my system - I can't find such a line. That might be an upgrade issue - if someone has changed the file, the patch skiped the one on upgradation... I have just extracted patch2 content - there is no bad line inside. Please check the timestamp of the file?

Re: Ping (from server) does not fetch nodename

Eugene Kopyshev — Fri, 10 Jan 2020 08:39:36 GMT

Well, so far you have got system working better, just open UI settings, browse the list of actions on this menu and compare with good system. In case if the Owner of menu item is set to Customer, the upgrade does not touch it, and it stays wrong. The fix operation would be to align with new argument format - it uses $uuid

Re: Ping (from server) does not fetch nodename

FrankMortensen — Fri, 10 Jan 2020 08:39:32 GMT

We face this problem for all nodes, so what you write about $nodename vs. $uuid sounds very interesting! I don't find any info. about it in the RN, though. In fact I don't find much valuable info. in the RN whatsoever (I am reading the RN that I find in the product, from the Help menu).

Do you have any other idea where I can find info. about that defect?

Cheers,
Frank

Re: Detected query which has been running for PTXHXXMXXS COMMIT

Eugene Kopyshev — Fri, 10 Jan 2020 07:29:27 GMT

Hi,

In case of disk failure you will see a message in Postgres logs - see pg_log folder. The Postgres likes if you let it run without clients to allow auto vacuum operation to complete. For this purpose, just stop everything, but run DB:

# ovstop -c

# ovstart nmsdbmgr

That might be also a good idea to force health checking, as far the COMMIT hangs... SQL commands are: # vacuum full; reindex database nnm; - make it running twice. When finished, start NNMi.

BR,

Re: Ping (from server) does not fetch nodename

Eugene Kopyshev — Fri, 10 Jan 2020 07:12:29 GMT

Well, problem shows up only if the nodename contains underscore symbol, regarded as illegal per RFC. With patch 3 this checking removed. I tested this with 2019.11, not sure 100% for the patch 3 for 2019.05 but it should work as the patch fix list includes it. Another possible problem that argument for the menu points to the $nodename not $uuid as it should - in that case you would observe problem for all nodes. The instruction on the fix included I believe in release notes...

Re: Ping (from server) does not fetch nodename

FrankMortensen — Fri, 10 Jan 2020 07:00:39 GMT

Thanks for your reply.

Does it mean that the problem is not consequent? Since we do not experience it in the test environment, which has the exact same NNMi version and patch (Patch 2)?

Cheers,
Frank

Re: Change IP in NNM Management Server 10.50 and NNM Performance QASPI Server

Eugene Kopyshev — Fri, 10 Jan 2020 06:37:43 GMT

Marina,

In case you are using self-signed certificates, the way to regenerate these even if the hostname not changes, that is to provide fake FQDN:

1. nnmsetofficialfqdn.ovpl fakefqdn.company.com

2. nnmsetofficialfqdn.ovpl same_fdqn_as_before

When it ask Do you want to generate SSL, answer Yes. Then, repeat steps you made before in a way to integrate NNMi with all SPIs. Let's say, merge trusted stores. You may need to review /var/opt/OV/shared/nnm/conf manually, as there are rare cases when configuration file may contain just an IP, not FQDN filled in.

BR,

Re: Ping (from server) does not fetch nodename

Eugene Kopyshev — Fri, 10 Jan 2020 06:29:22 GMT

Frank,

It might be a known issue which fixed by patch 3. Also, 2019.11 is free of this problem...

Change IP in NNM Management Server 10.50 and NNM Performance QASPI Server

MarinaAraujo — Thu, 09 Jan 2020 19:04:57 GMT

Hello:

We are changing the IP in the NNM Management Server and NNM iSPI Performance for Quality Assurance Server. Both machines change the IP but do not change the hostname. We need to know the steps to do not loose the communication between servers and nodes.

Thank you

Marina

AD based L2 Operators unable to schedule report jobs in NPS

StephenTP — Thu, 09 Jan 2020 17:16:07 GMT

I've been trying to set up our Level 2 Operators with the ability to schedule their own reports in NPS 2018.05. Only administrators and L2 Operators with local accounts in NNMi can schedule reports at the moment. I've adjusted the capabilities in NPS so that all L2 users should be able to schedule reports but nothing has worked for our active directory based users. I created a local test account in NNMi and made it a L2 Operator and it does have the ability to schedule reports NPS. We've tested this in our dev, cert, and prod environments and they all act the same.

Originally the L2 Operators were also not able to run reports from BI Server > Public/My Folders but that has been fixed by updating the capabilities.

I do have a case open with MF Support but I wanted to see if anyone here has run in to this.

HOW TO remove dependencies of a node ( or interface) group as NNMi does not clean up

Andreas Poehlmann — Thu, 09 Jan 2020 07:14:13 GMT

- create a node group
- make use of the group e.g. in NodeSettings of an EvenConfig

=> delete the node group
==> do you want to delete the group and all its dependencies? => YES

I expected proper cleanup - BUT

within NodeSettings the group is still reverenced, no longer by name but by uuid.

Bug or feature?

Questions:
- how to properly remove a node group and its references?
- how to find where a node group was used?

Requesting more flexibility in the way NNMi Catalogs devices to allow for better device management

johnivon — Wed, 08 Jan 2020 16:06:11 GMT

I would like a way to catalog/create a profile using the OID and other variables or sub variables like sysdescriptions to differentiate between dual use device deployments.

Background behind the request. We have an SDLAN ACI deployment.

The aci-n9000-system is a leaf and spine configuration used in the Datacenter environment.

Our configuration has ACI devices with dual usages.

One as a NX-OS(tm) nxos.7.0.3.I7.6.bin device / and one as an aci-n9000-system

We integrate the NNMi inventory with HPNA to backup all device configs.

The HPNA driver can’t support / handle leaf / spines added into NA any other way other than by NA itself (module diagnostic task runs and results in the leaf

spine getting added).

It's a known limitation, so we would need to make sure leaf or spine devices wouldn't get added in thru the integration Module.

We need to filter out that usage to enable HPNA to discover these devices. We do this thru the OID profiles.

NNMi uses Device Profiles (which equate to sysObjectID) to control certain types of behavior.

The Integration Module uses a device group as its input inventory. We configure the group to add or Filter out devices to/from HPNA via the device types and Profiles.

A solution would be to have more flexibility with the way NNMi Catalogs devices to allow for a more granular approach to device management

Re: NA: For Policy / Rule - Add ability to match multiple text within a block

AkashDeep — Wed, 08 Jan 2020 08:22:58 GMT

, Can you please add an Idea for the exact enhancement you need?

Please note the ask under this idea is already available in the product and the Idea is at terminating state "Already Offered".

Ping (from server) does not fetch nodename

FrankMortensen — Wed, 08 Jan 2020 05:04:44 GMT

Hi,

After upgrading from NNMi 10.10 to 2019.05 on Windows in our production env., it is not possible to ping a monitored node interactively from the console anymore. If we right click on a node and select Node Access -> Ping (from server), we do get a new little window, but no ping attempts are made. Instead the text in the windows states "Ping from <NNMi-servername here> to localhost". It i.e. (claims to) ping itself (although it does not even do that). In the same little window it even states "Specify Node" and "Please enter a node name and press "Ping"".

If I enter a nodename in that field and press the Ping button, it just clears the field again without pinging anything.

If I instead right-click the node and select Configuration Details -> Communication Settings, all the comm. settings for the node in question are shown. So in this case NNMi is indeed able to fetch the actual nodename from the node symbol/icon. If I instead, however, choose Configuration Details -> Monitoring Settings, I get the error message "Error: No object found. One of the following parameters must be specified to identify the object: objid, objuuid, objcustattr, objattrs".

Any ideas? How should I troubleshoot? I don't see anything in the logs...

BR,
Frank Mortensen
Managon AB

Network Automation events at audit_log.txt file

dm1tr1y — Tue, 07 Jan 2020 09:19:15 GMT

Hello! Dear Network Automation professionals, I need your advice..

I need to integrate HPE Network Automation 10.30 with SIEM and I'm choosing a way, how to do it.

I see 2 possible ways and try to choose the best one:

Logging by "Send Syslog Message" rule via Admin -> Event Notification & Response Rules
Getting audit_log.txt directly from OS and next - parsing of it by SIEM connector.

Do both ways have the same log level?

Do they log the same event types?

Which way is most full by events completeness?

Which way is usually mostly preferred?

I did not found these answers at documentation...

Provided information is not clear when adding a seed and found duplicate

Bharath Kumar — Tue, 07 Jan 2020 08:58:30 GMT

Hi,

I had gone through few posts:

https://community.microfocus.com/t5/Network-Management-OpenView-NNM/Duplicate-Seed-issue/m-p/561708#M988

https://community.microfocus.com/t5/Network-Management-OpenView-NNM/Duplicate-seed/m-p/615057#M161021

Changing the log level and finding the seed is fine. But my question is:

Lets say we have two hostname's (with 2 interfaces) hostA and hostB. When I add hostA it will get added successfully and when tried to add hostB NNM says "Node not created (duplicate seed)".

Would like to check with NNM team that it will be great if we receive a message saying:

"Node not created (duplicate seed) of hostA" which will reduce troubleshooting time.

Also, it will take much time to get MAC addresses from internal customers to find the duplicate device which is already added in NNM.

Kindly suggest !!!

I tried to open Product Enhancement Request but support team requested me to post here.

Regards,

Bharath Kumar.

Improve custom poller to collect based on filter values

ramesh9 — Tue, 07 Jan 2020 07:57:18 GMT

Dear All

I am using Custom poller to collect client details of WIFI access points based on below MIB variables,

1.3.6.1.4.1.14179.2.1.4.1.3
1.3.6.1.4.1.14179.2.1.4.1.9
1.3.6.1.4.1.14179.2.1.6.1.2
1.3.6.1.4.1.14179.2.1.6.1.3
1.3.6.1.4.1.14179.2.1.4.1.25 ( Client protocol - 5 means client is connecting using mobile )

Now when I define the collection NNM collects all client details, even clients who are connecting from laptop.

I only want to collect client details who are connected from mobile.

Is this possible using custom poller or can we enhance custom poller.

Improve custom poller feature with scripting

ramesh9 — Tue, 07 Jan 2020 07:48:03 GMT

Dears

Currently we can use Custom poller to collect MIB values from target devices.

However I see we cannot use scripting on the values collected, for example manipulate values collected and store the manipulated values. If MIB value returned is integer, I know we can use MIB expression, however if collected value is string or other types we cannot use MIB expression.

Please enhance custom poller to have this feature.

Re: add NNMi nodegroup to incident or CMA

asoloperto — Mon, 06 Jan 2020 09:39:58 GMT

Hello ramesh,

I am not sure but as far as I remember the SNMP trap of this integration does not contain the custom atttributes of the node. The integration is not via an incident action script.

BR Allessandro

Not able to launch traffic configuration form

ramesh9 — Mon, 06 Jan 2020 07:36:12 GMT

NNM 10.40 with latest patch installed

Master collector installed on NNM server and started fine, no issues observed in boot.log or jbossserver.log

Leaf collector installed on different server and started fine, no issues observed in boot.log or jbossserver.log

Launching Traffic configuration form from NNM and it presents me blank page.

Checked ports 12080 and 12043 are running fine for master collector.

I see below error in jbossServer.log when launching traffic configuration form,

ERROR [org.apache.catalina.connector.CoyoteAdapter] (tomcat-exec-4) An exception or error occurred in the container during the request processing: java.lang.AbstractMethodError: com.hp.ov.nms.as.ejb.NmsWebRealmSettingsImpl.isBannerEnabled()Z
at com.hp.ov.nms.as.server.tomcat.AbstractWebAuthenticator.shouldCheckBanner(AbstractWebAuthenticator.java:212)

Please advise to solve this problem, as usual Micro Focus NNM support is pathetic.

Re: NA: For Policy / Rule - Add ability to match multiple text within a block

Sanjeev_A — Fri, 03 Jan 2020 10:33:35 GMT

I believe there are use cases when we need to refer names from one part of configuration and refer that in other part of the configuration and if that is made available will help validate these settings. e.g. ACL definition and application or use of that ACL where the ACL number of name is not standard and we need to validate the settings based on what is configured on the devices.

Putting all that information into single rule condition might not be feasible, thus making a case to have it available across multiple rule conditions within a single rule.

Re: Save details / event detail of the report "Check policy compliance" in CSV file

Sanjeev_A — Fri, 03 Jan 2020 10:24:20 GMT

The compliance report available from the Advanced Search option should include all different fields that are selected in the report output format along with the "Detail" column that lists the reason for non-compliance of the rule.

Today, that filed is not available when you download the search results or send those results via email. The "Detail" field is available in view detailed compliance report which doesn't have other fields like rule importance and other selectable fields from the report output option.

So make small tweaks in the report options available from the tool to have that "Detail" field available and same is made available in CLI/API calls too.

Re: NA: tracking of script & policy history

427Cobra — Thu, 02 Jan 2020 14:54:21 GMT

Great idea, it would also be good to rollback the changes using subversion(SVN) running in the background. Also to be able to compare the differences of between saved versions.

Re: Policy management, tracking

427Cobra — Thu, 02 Jan 2020 14:49:34 GMT

Great idea, it would also be good to rollback the changes using subversion(SVN) running in the background. Also to be able to compare the differences of between saved versions.

Re: NA - Check Policy Compliance - Task result should show task status and not compliance status

427Cobra — Thu, 02 Jan 2020 14:39:18 GMT

it would beneficial if from compliance result screen to toggle what as in compliance or matching as well, Possibly handle like configuration change side-by-side comparison.

Re: Hostname field with IP address

Chris_Powers — Thu, 02 Jan 2020 13:13:22 GMT

Couple things that might help.

From what I can see, the devices in your picture are not yet managed in NA (no vendor or model), so currently NA isn't going to have the config to parse the hostname from it. Once it does, then the IP you see in the Host Name column should be the hostname from the config...

Now, you mention the NNMi / NA integration... When NNMi sends over new devices to NA, it sends the IP (not hostname). So, again, same as without the integration, you will rely on the config from the device being retrieved and then parsed to get the hostname.

You "could" change your adjustable_options.rcx file to have NA use the NNM long name, but that's not as simple as you might hope, as you'll need a script to update NA on changes.

Hope this helps,

Chris

Provide an option to create a list of approved values and use them in compliance rules

Sanjeev_A — Thu, 02 Jan 2020 07:10:12 GMT

Can you make an option to define custom lists that can be defined with approved values and have them refer as variable in the compliance rules? That way the list can be managed centrally for any modification and doesn't need to touch any controls in the policy for modification whenever there is a change in the infrastructure.

e.g. If the requirement is to validate specific IP addresses/subnets for AAA, Logging, Monitoring etc.. can be created and referred in different rules for various devices in multiple policies.

XML Parsing support in NA for configuration compliance

Sanjeev_A — Thu, 02 Jan 2020 07:02:33 GMT

The current compliance is based on parsing the text file configuration of devices. However there are few devices like Juniper SSL-VPN devices, that stores the configuration in XML format and there is no option to parse XML files in the NA tool. Can you add additional capability to validate the configuration compliance of these devices by providing the feature to parse XML files? If you are able to add feature to maintain relation of parent-->child relationship to multiple levels and then have the tag-value pairs validated for specific set of configurations then it would be helpful.

On a side note, is there any plan to introduce multiple blocks in the rule, as we have seen in some configurations like Fortinet FortiGate Firewalls (single VDOM and Multi VDOM configurations), there is a need to maintain checks within an outer block and there are multiple blocks within that configuration from which validation is required to be done?

Can we generate Pingable devices report form NPS

fms_bsdc — Wed, 01 Jan 2020 10:15:18 GMT

Hi,

NNMi is 2018.11 on windows 2016 & NPS is same version, both are different box. So we want to generate ICMP reachability reports fom NPS. Please suggest me. How do that.

I have discover Pingable device in NNMi

So what is process, Please suggest

Thanks

Dinesh

Re: kubernetes integration with HP NNMi

AkashDeep — Tue, 31 Dec 2019 04:58:34 GMT

Hi Anish.

NNMi is about monitoring and managing network devices. K8S is a computer application, which manages containerized workloads and services. As this is nothing to do with the Computer Network, it is not in the scope of NNMi.

I hope this clarifies.

Operation Bridge from Micro Focus is more tuned to managing applications.

Provide a tool to manage information collected in VLAN tables.

Bfdx — Mon, 30 Dec 2019 12:26:51 GMT

Re: Fix/Update Bundled Documentation in NMC-NNMi-Lin-2019.11.tar.gz

AkashDeep — Mon, 30 Dec 2019 09:30:01 GMT

Hi Brandon.

There are two ways one can raise the documentation issue:

1. There is a Feedback link at the bottom of every page, which generates an email to the documentation team. And they work on addressing the issue.

2. Raise a support case for the same, and the support team would work with R&D to get the reported issue fixed.

Idea Exchange is not the process meant for it. Please forward me the support case ID for the interation you had with support, and I would follow up with the support team.

Re: kubernetes integration with HP NNMi

anishrana2001 — Mon, 30 Dec 2019 09:23:19 GMT

Hello Akash,

Thanks for your response on this topic.

All the alarms generated by Kubernetes should be managed by NNMi. For this, I need a MIBs for Kubernetes devices. As of know, I am also not aware of what type of alarms Kubernetes will send to NNMi. That I need to work with Kubernetes team.

Before starting this project, I need a MIBs that ensure that all the alarms will be well taken at HP NNMi server side.

Let me know if you need further information.

Thanks,

Anish Rana

Re: NNMi 10.x How to use web API

Johan C — Mon, 30 Dec 2019 08:06:32 GMT

Hi there,

If you want to get all nodes, just leave the filter empty like below, it will give you all nodes. If you need more specific filter, let me know.

Regards,

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:node="http://node.sdk.nms.ov.hp.com/">
<soapenv:Header/>
<soapenv:Body>
<node:getNodes>
<arg0>
</arg0>
</node:getNodes>
</soapenv:Body>
</soapenv:Envelope>

Re: how to check node discovery date & time.in NNMi

Johan C — Mon, 30 Dec 2019 07:52:18 GMT

Hi,

There are few ways,

1. Using NNM GUI Console

Inventory -> Nodes (All Attributes) -> Find "Created" Column, Right Click to add filter, Specify the timeline

2. Using NNM Web Service

https://<NNMhost>:<NNMport>/NodeBeanService/NodeBean

Use getNodes method & speficy filter using attribute "created"

Regards,

Re: Hostname field with IP address

Johan C — Mon, 30 Dec 2019 07:02:28 GMT

Hi there,

Do you have those devices information your NA core's host file?

Linux : /etc/hosts

Windows: C:\Windows\System32\drivers\etc\hosts

Run Reesolve FQDN to those devices. Tasks -> New Tasks -> Resolve FQDN

Regards,

Johan

Re: kubernetes integration with HP NNMi - Status changed to: Needs Clarification

AkashDeep — Mon, 30 Dec 2019 04:51:29 GMT

Dear Submitter,

NNMi is available to run in the Kubernetes environment as part of our containerization strategy. However, this is not available for production deployment as of now.

However, this idea seems to be around NNMi integrating with K8S. Can you please clarify, what integration you would like to see between NNMi & K8S?

Re: To be able to use NNM licenses in NOM to use the NOM features - Status changed to: Needs Clarification

AkashDeep — Mon, 30 Dec 2019 04:41:31 GMT

Dear Submitter.

NNMi as a product can be deployed with NNMi or NOM license as of now.

With NOM license, it enables you to have Diagnostics Analytics, BVD export, etc. enabled. Also, with NOM license you can deploy additional components you mentioned above.

The same is true for NA as a product, where it can understand both NOM and NA license.

Given this, can you please clarify as to what exactly is the requirement here?

Re: bug in NNM-2019.05 Logging in with TLS/PKI. Communication Settings shows a new window not the data - Status changed to: Declined

AkashDeep — Mon, 30 Dec 2019 04:26:20 GMT

Dear Submitter,

Please file a support case for any BUG with the tool. If you had already filed one for this, please provide me a case ID.

Re: Replace Flash in NNMi. - Status changed to: Delivered

AkashDeep — Mon, 30 Dec 2019 04:19:50 GMT

Dear submitter and contributors,

We have release NNMi 2019.05 patch 3, which removes the Flash option and all relevant files. Please upgrade to 2019.05 and deploy patch 3 for the same.

Patches and more details can be found at:

Linux: https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/NNM201905L_00003

Windows: https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/NNM201905W_00003

Re: Need to configure SMS alerts and notifications from NNMi

AkashDeep — Mon, 30 Dec 2019 04:08:57 GMT

NNMi allows one to configure an action for any incident. You can use that for integration with email, SMS or any other service.

Cisco Nexus Aggregator interface polling needs to be enhanced

ramesh9 — Sun, 29 Dec 2019 04:32:29 GMT

Cisco Nexus 5000 Switches.

We have Uplink ports created on these switches, however Uplink ports are not been monitored or performance is not getting collected.

Please enhance the solution to get these aggregator interfaces for monitoring and performance data is collected.

Re: add NNMi nodegroup to incident or CMA

ramesh9 — Sun, 29 Dec 2019 04:26:09 GMT

Why cannot you add Custom attribute for each node and when alert comes for the node, map the alarm with custom attribute value.

Re: Configure Email Notifications in NNMi 9.0

Kushal singh — Sat, 28 Dec 2019 20:12:38 GMT

I already have email configured in my NNMi 10.01 version.

I need to change the mail configuration, where can i find the script to modify the existing configuration.

Please provide me the path for that.

Re: Allow additional Wireless Access Point attributes to be replicated to OBM/RTSM/UCMDB

j_h_1 — Sat, 28 Dec 2019 19:48:52 GMT

AkashDeep,

Any updates on this idea?

Hostname field with IP address

connection — Thu, 26 Dec 2019 13:56:10 GMT

Hi Team,

After integrating with NNMI, we see the Device inventory view in NA hostname field with IP address where as in NNMi we see with hostname, please guide what has be changed.

Thanks

Re: HP NNMI -NA integration

connection — Wed, 25 Dec 2019 12:20:12 GMT

In NA device inventory, Hostname field showing it as IP instead of NAME, can you guide please.

how to check node discovery date & time.in NNMi

fms_bsdc — Tue, 24 Dec 2019 12:40:34 GMT

Hi,

I want to know node discovery date & time for in bulk.

for Example:-

Today i added 10 Nodes in NNMi, So need to check how many nodes added in Day with Date & time. Please suggest me.

Re: Enable security access to QA site

ramesh9 — Tue, 24 Dec 2019 04:24:09 GMT

Dear

Thanks for the explanation.

In our environment, devices are owned by network team. QA probes will be created for other teams A and B.

I want Team A to only see the probes assigned to them and similar to Team B.

How this can be achieved by Tenant concept.

As per my understanding, user access to devices is based on Security groups not Tenants.

bug in NNM-2019.05 Logging in with TLS/PKI. Communication Settings shows a new window not the data

Whitlock Support — Mon, 23 Dec 2019 23:03:04 GMT

Both Firefox, Chrome and Edge have this problem. I won't say it is only a problem with Communication Settings (Monitoring settings do not have the problem), but since the problem exists on all my browsers

This is only a problem with NNM 2019.05 and login with TLS/PKI, though admittedly I haven't tested with user/password login as all my test servers use TLS/PKI. If I select a node and then either from the top level menu or right clicking on the device, when I select Communications Setting, I get a new window. Instead of showing me the data, it asks for a login. If I select Monitoring settings or any other setting I get the normal new window with the data. I tested on Chrome and Edge. I have seen exceptions and it is more consistent when the node is set to critical/red.

Re: NA: For Policy / Rule - Add ability to match multiple text within a block

Brian Kaplan — Mon, 23 Dec 2019 15:42:12 GMT

No, we can't refer to groups from A and use them in B or C.

Re: Enable security access to QA site

Vesselin Kotaro — Mon, 23 Dec 2019 11:28:56 GMT

When creating site you are able to specify Tenant it lives in. Also mentioned in documentation:

https://docs.microfocus.com/itom/Network_Node_Manager_i:2019.11/QaConfigSites#Add_sites

BR,

Vesko.

Re: NA: For Policy / Rule - Add ability to match multiple text within a block

Sanjeev_A — Mon, 23 Dec 2019 09:41:42 GMT

I mean multiple conditions within a rule like Config Block A, Config Text B, Config Text C etc. that we see today while creating a rule and use boolean expression to define the logic. Are we able to refer groups from A and use them in B or C?

Re: How to remove existing incidents from NNMi web console via CMD

Maarten_K — Mon, 23 Dec 2019 07:52:06 GMT

You can use the nnmtrimincidents.ovpl script. For more info:

https://docs.microfocus.com/NNMi/10.30/Content/refdocs/nnmtrimincidents.ovpl.1M.html

To be able to use NNM licenses in NOM to use the NOM features

binuj — Sun, 22 Dec 2019 06:44:26 GMT

Currently there are 2 products which are NNM and NOM. NOM has additional functionality included like NA and also has options like CDF and also integration to BVD. These features are missing for NNM.

There should be an option to use NOM with NNM license whereby only the features of NNM are enabled and if NOM license installed then you should be able to use the full features of NOM.

This will help to have one product and also the customers to be able to use the new enhancements of NOM and also to have it installed on CDF and integrations to BVD etc

Re: Enable security access to QA site

ramesh9 — Sun, 22 Dec 2019 04:21:11 GMT

Not sure how I can assign tenants to QA sites, please can you elaborate more.

How to remove existing incidents from NNMi web console via CMD

fms_bsdc — Sat, 21 Dec 2019 12:06:04 GMT

How to remove existing incidents from NNMi console via CMD. Please suggest me.

Re: HP NNMI -NA integration

connection — Sat, 21 Dec 2019 09:36:23 GMT

Tried with FQDN and found same issue.

There is support case even and i am not getting any help to resolve since from last week.

Kindly help to resolve the same

Re: NNMi - Schedule auto discovery at a given time

Vesselin Kotaro — Sat, 21 Dec 2019 00:30:47 GMT

what I am trying to explain is that discovery is designed in a way that period will shift depending on how network changes/responds/behaves. This is all done to keep up-to-date information about your network.

I am not really getting the reason why you would like to limit discovery to certain timeframe? If discovery runs at 02:00 and interface description changes at 03:00 you will have to live with the old description for 23 hours until next discovery. Haven't seen operations person OK with such delay.

Re: Enable security access to QA site

Vesselin Kotaro — Sat, 21 Dec 2019 00:23:25 GMT

How about using tenants?

Re: HP NNMI -NA integration

qz07sg — Fri, 20 Dec 2019 17:35:31 GMT

Are you using IP address(es) in the integration panel in NNMi -- instead of FQDNs? Assuming that SSL is enabled, IP address(es) may not work because typically SSL certs do not have IP addresses in the subject alternative name section of the certificate.

FQDN should be used there, and the FQDN needs to match the CN value in the cert, or be listed as one of the subject-alternative names.

Re: HP NNMI -NA integration

connection — Fri, 20 Dec 2019 11:36:24 GMT

resolved the certificate issue and still through some different error

Unable to sendViaPost to url[https://ip:443/soap]: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(Unknown Source)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(Unknown Source)
at org.apache.commons.httpclient.HttpConnection.open(Unknown Source)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)

Re: Automatically delete connections for disabled links after a period of time

hansco — Fri, 20 Dec 2019 10:48:58 GMT

In our large environment with changes on a daily basis this would be a great improvement.

Automatically delete connections for disabled links after a period of time

Vicente Navarro — Fri, 20 Dec 2019 10:18:22 GMT

This is a repost of the legacy Enhancement Requests QCCR1B151773 and QCCR1B119433 in Idea Exchange.

When the interfaces that are part of a connection are disabled (ifAdminStatus=Down), the connection becomes grey and NNMi will never remove that connection automatically. That connection may still exist physically or not, and it may make sense that the user wants to keep it or not. But in cases that the connection is undesired (i.e. the link is disabled because it is no longer there), it may create strong confusion in the map. Currently, the workaround to remove that connection if it is undesired is to enable again the interface and: -->rediscover the nodes --> set deletion of inactive connections (which have been down for X number of days) in discovery configuration But that involves re-enabling again the interface, which may be not possible at all! Alternatively, nnmconnedit.ovpl could also be used for this, but it would be highly inconvenient to a large network. Therefore, NNMi should provide a way to remove connections for disabled interfaces. This could be as simple as adding an additional option next to "Period (in Days) to Delete Connections that are Down" for "Period (in Days) to Delete Connections that are Disabled"

Re: HP NNMI -NA integration

asoloperto — Fri, 20 Dec 2019 08:54:01 GMT

Hello,

the storepass password is "sentinel" (your command is missing the "l").

It seems, that you have imported the NA certificate in the NNMi truststore, but that NNMi cannot trust it as the hostname/ip address is not correct in the certificate. Can you ping the NA server with FQDN, hostname and ip address from NNMi?

HTH and best regards

Allessandro

Re: HP NNMI -NA integration

connection — Fri, 20 Dec 2019 08:17:08 GMT

list from NA server

e:\NA\server\ext\jboss\server\default\conf>e:\NA\jre\bin\keytool -v -list -keyst
ore truecontrol.keystore -storepass sentine
keytool error: java.io.IOException: Keystore was tampered with, or password was
incorrect
java.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:785)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:5
6)
at sun.security.provider.KeyStoreDelegator.engineLoad(KeyStoreDelegator.
java:224)
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineLoad(JavaKeySt
ore.java:70)
at java.security.KeyStore.load(KeyStore.java:1445)
at sun.security.tools.keytool.Main.doCommands(Main.java:823)
at sun.security.tools.keytool.Main.run(Main.java:366)
at sun.security.tools.keytool.Main.main(Main.java:359)
Caused by: java.security.UnrecoverableKeyException: Password verification failed

at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:783)
... 7 more

Re: HP NNMI -NA integration

connection — Fri, 20 Dec 2019 07:57:57 GMT

here is the trace log

Line 48442: 2019-12-20 13:09:41.295 INFO [org.apache.commons.httpclient.HttpMethodDirector] (tomcat-exec-1063) I/O exception (javax.net.ssl.SSLException) caught when processing request: hostname in certificate didn't match: <IP address> != </NA server hostname>
Line 48444: 2019-12-20 13:09:41.304 INFO [org.apache.commons.httpclient.HttpMethodDirector] (tomcat-exec-1063) I/O exception (javax.net.ssl.SSLException) caught when processing request: hostname in certificate didn't match: <IP address> != </NA server hostname>
Line 48447: 2019-12-20 13:09:41.318 INFO [org.apache.commons.httpclient.HttpMethodDirector] (tomcat-exec-1063) I/O exception (javax.net.ssl.SSLException) caught when processing request: hostname in certificate didn't match: <IP address> != </NA server hostname>
Line 48449: 2019-12-20 13:09:41.333 INFO [org.apache.axis2.transport.http.HTTPSender] (tomcat-exec-1063) Unable to sendViaPost to url[https://IP address:443/soap]: javax.net.ssl.SSLException: hostname in certificate didn't match: <IP address> != </NA server hostname>
Line 48449: 2019-12-20 13:09:41.333 INFO [org.apache.axis2.transport.http.HTTPSender] (tomcat-exec-1063) Unable to sendViaPost to url[https://IP address:443/soap]: javax.net.ssl.SSLException: hostname in certificate didn't match: <IP address> != </NA server hostname>

Re: NA: For Policy / Rule - Add ability to match multiple text within a block

Brian Kaplan — Thu, 19 Dec 2019 20:31:12 GMT

Hi Sanjeev,

The capture groups work within any of the conditions, but not between them, if that's the question. The context of the capture groups remains within any given condition.

Re: add NNMi nodegroup to incident or CMA

RPS_Sholm — Thu, 19 Dec 2019 13:16:10 GMT

Thank you very much!

It work flawless. Now I just have to figure the out how to provide the script with node ID in one of those tabs with many popups and even more submenus 🙂

Br Fredrik

Re: add NNMi nodegroup to incident or CMA

asoloperto — Thu, 19 Dec 2019 12:28:37 GMT

Hello,

in SoapUI the request against <URL NNMi Server>/NodeGroupBeanService/NodeGroupBean is (arg 0 is the ID of the node):

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nod="http://nodegroup.sdk.nms.ov.hp.com/">
   <soapenv:Header/>
   <soapenv:Body>
      <nod:getNodeGroupsByNode>
         <arg0>23622320293</arg0>
      </nod:getNodeGroupsByNode>
   </soapenv:Body>
</soapenv:Envelope>

The result for this node is:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <nod:getNodeGroupsByNodeResponse xmlns:nod="http://nodegroup.sdk.nms.ov.hp.com/">
         <return>
            <item>
               <id>2147485675</id>
               <name>Island-1</name>
               <status>UNKNOWN</status>
               <uuid>c9866922-76fd-4662-a772-1a1f35e34e1e</uuid>
            </item>
            <item>
               <id>23622321006</id>
               <name>All_Devices</name>
               <status>CRITICAL</status>
               <uuid>b8e66582-3033-4bcc-be03-2dd41b6346f1</uuid>
            </item>
            <item>
               <id>23622320997</id>
               <name>Germany</name>
               <status>CRITICAL</status>
               <uuid>e28f04d0-232a-4c7d-8167-c719cbc28772</uuid>
            </item>
            <item>
               <id>38781</id>
               <name>Networking Infrastructure Devices</name>
               <status>NOSTATUS</status>
               <uuid>d2058de0-6dfe-4d55-bae3-0f9e95b55b1b</uuid>
            </item>
            <item>
               <id>38770</id>
               <name>Switches</name>
               <status>NOSTATUS</status>
               <uuid>5f719483-5569-4d11-a525-e291377b80e6</uuid>
            </item>
            <item>
               <id>38765</id>
               <name>Routers</name>
               <status>NOSTATUS</status>
               <uuid>75f95c1a-0ee0-49ac-a815-c32ab74b1449</uuid>
            </item>
         </return>
      </nod:getNodeGroupsByNodeResponse>
   </env:Body>
</env:Envelope>

HTH and best regards

Allessandro

Re: NNM SDK using WebService

asoloperto — Thu, 19 Dec 2019 10:27:27 GMT

Hello KAKA,

you should use the WEB Service API of NNMi for integration. You can find the documentation online:

https://docs.microfocus.com/itom/Network_Node_Manager_i:10.50/NnmiWsiApi

HTH and kind regards

Allessandro

Re: NA: For Policy / Rule - Add ability to match multiple text within a block

Sanjeev_A — Thu, 19 Dec 2019 06:10:04 GMT

Does it also work for multiple conditions within the rule for checking the configuration at different places?

e.g. ACL definition and use of that ACL in the VTY line configuration.

Re: NNMi - Schedule auto discovery at a given time

pabharat — Thu, 19 Dec 2019 01:01:15 GMT

Event based rediscovery of existing device is fine.

We want to run scheduled discovery of devices in given subnet in given DC on the basis of local off hours. Don't want to run it at same time for all DC spread across many time zones.

for example want to run discovery for DC in CA, USA at 02:00 hrs (PST) and for DC in India at 02:00 hrs (IST).

Re: NA-Run specific policy(s)

pabharat — Thu, 19 Dec 2019 00:50:14 GMT

Exportable report should work.

Compliance status of device will change at next scheduled compliance check, that's ok.

Re: NA: standard FTP-server (for non NA internal tasks)

smith — Wed, 18 Dec 2019 19:17:42 GMT

For this

- credentials - Admin - Administrative Settings - Device Access - FTP and SSH Device Access

I don't see any current information in there. If i add a user and password does it break any existing functionality to anything? Can users who have existing accounts also login via ftp or can ftp only use this account and now must share it? Thanks - just trying to fully understand the ramifications of doing this.

Re: NNM SDK using WebService

KAKA_2 — Wed, 18 Dec 2019 16:26:09 GMT

- I am using 10.50 with patch NNM1050_00001,NNM1050W00001.

-KAKA-

Re: TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 15:24:18 GMT

Hi,
Thanks for support for this issue.

I have been kill the process & restart the nnmtrareceiver
service, as of now nnmtrareceiver working fine with system health.

thanks
Dinesh Choudhary

Re: add NNMi nodegroup to incident or CMA

asoloperto — Wed, 18 Dec 2019 14:41:52 GMT

I use SoapUI to "develop" the request. There is an old blog entry from Micro Focus explaining the usage. Perhaps I can check this tomorrow.

BR Allessandro

Re: TrapReceiver HornetQ Server: Down

asoloperto — Wed, 18 Dec 2019 14:38:10 GMT

Ah, there is an already running nnmtrapreceiver.

Try to stop it with nnmtrareceiver -stop. If it does not work kill it with the task manager.

Issue ovstart -c.

Is it now running?

BR Allessandro

Re: add NNMi nodegroup to incident or CMA

RPS_Sholm — Wed, 18 Dec 2019 14:33:07 GMT

I agree the web service call seems like the best and fastest way.

Im having problems getting the soap together, could you please advice in an example?

Br Fredrik

Re: TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 14:24:36 GMT

Hi,
Yes windows SNMP services are enabled.

Re: TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 14:22:55 GMT

Below Output
C:\>netstat -ano | findstr 23492
TCP 127.0.0.1:5447 0.0.0.0:0 LISTENING 23492
TCP 127.0.0.1:5447 127.0.0.1:51073 ESTABLISHED 23492
TCP 127.0.0.1:5447 127.0.0.1:63704 ESTABLISHED 23492
TCP 127.0.0.1:5447 127.0.0.1:63705 ESTABLISHED 23492
TCP 127.0.0.1:51043 127.0.0.1:51044 ESTABLISHED 23492
TCP 127.0.0.1:51044 127.0.0.1:51043 ESTABLISHED 23492
TCP 127.0.0.1:51050 127.0.0.1:51051 ESTABLISHED 23492
TCP 127.0.0.1:51051 127.0.0.1:51050 ESTABLISHED 23492
TCP 127.0.0.1:51055 127.0.0.1:51056 ESTABLISHED 23492
TCP 127.0.0.1:51056 127.0.0.1:51055 ESTABLISHED 23492
TCP 127.0.0.1:51073 127.0.0.1:5447 ESTABLISHED 23492
TCP 127.0.0.1:51084 127.0.0.1:51086 ESTABLISHED 23492
TCP 127.0.0.1:51086 127.0.0.1:51084 ESTABLISHED 23492
TCP 127.0.0.1:63704 127.0.0.1:5447 ESTABLISHED 23492
TCP 127.0.0.1:63705 127.0.0.1:5447 ESTABLISHED 23492
TCP 127.0.0.1:63710 127.0.0.1:63711 ESTABLISHED 23492
TCP 127.0.0.1:63711 127.0.0.1:63710 ESTABLISHED 23492
TCP 127.0.0.1:63712 127.0.0.1:63713 ESTABLISHED 23492
TCP 127.0.0.1:63713 127.0.0.1:63712 ESTABLISHED 23492
UDP 0.0.0.0:162 *:* 23492
UDP [::]:162 *:* 23492

****************************************
C:\>tasklist | findstr 23492
nnmtrapreceiver.exe 23492 Services 0 16,31,492 K

Re: TrapReceiver HornetQ Server: Down

Gediminas Daniu — Wed, 18 Dec 2019 14:19:46 GMT

Hi,

is Windows SNMP service enabled? You may need to disable it.

my 2 cents,
Gedas

Re: TrapReceiver HornetQ Server: Down

asoloperto — Wed, 18 Dec 2019 14:16:43 GMT

Ok, port udp 162 is already used. Let us check for the process ("UDP 0.0.0.0:162 *:*" and ipv6 line):

netstat -ano | findstr 162

The number at the end is the process id of the owner and we can get it with this command:

tasklist | findstr <process id>

Output?

BR Allessandro

Re: TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 14:09:03 GMT

Below Output

C:\Program Files (x86)\HP\HP BTO Software\bin\nnm\amd64>nnmtrapreceiver.exe -status
Trap Receiver is STOPPED.

C:\Program Files (x86)\HP\HP BTO Software\bin\nnm\amd64>nnmtrapreceiver.exe -start

C:\Program Files (x86)\HP\HP BTO Software\bin\nnm\amd64>nnmtrapreceiver.exe -status
Trap Receiver is STOPPED.

C:\Program Files (x86)\HP\HP BTO Software\bin\nnm\amd64>nnmtrapreceiver.exe -stop

C:\Program Files (x86)\HP\HP BTO Software\bin\nnm\amd64>nnmtrapreceiver.exe -start

C:\Program Files (x86)\HP\HP BTO Software\bin\nnm\amd64>cd \

C:\>netstat -anb | findstr 162
TCP 127.0.0.1:54162 127.0.0.1:54163 ESTABLISHED
TCP 127.0.0.1:54163 127.0.0.1:54162 ESTABLISHED
TCP 172.21.248.186:50694 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:52375 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:52865 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:53696 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:55984 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:56135 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:58675 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:58913 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:59912 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:60904 10.70.251.162:1556 ESTABLISHED
TCP 172.21.248.186:65420 10.70.251.162:1556 ESTABLISHED
UDP 0.0.0.0:162 *:*
UDP 0.0.0.0:5162 *:*
UDP 127.0.0.1:60162 *:*
UDP [::]:162 *:*
UDP [::]:5162 *:*

Re: TrapReceiver HornetQ Server: Down

asoloperto — Wed, 18 Dec 2019 13:56:29 GMT

Ok, thanks for the information.

Restart trapreceiver with "ovstart"
Is it running:
- cd %NnmInstallDir%
- cd bin\nnm\amd64\
- nnmtrapreceiver -status
If it is not running, please check if port already used:
- netstat -an | findstr 162
If port is used let check for exec file
- netstat -anb | findstr 162

What are your findings?

BR Allessandro

Re: TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 13:46:09 GMT

This is windows system, as well as standalone box.

Re: TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 13:43:55 GMT

Below Outputs

C:\Users\emsdradmin>ovstatus -v
object manager name: OVsPMD
state: RUNNING
PID: 16724
last message: -
exit status: -

object manager name: nnmaction
state: RUNNING
PID: 21072
last message: Initialization complete.
exit status: -

object manager name: nnmtrapreceivermd
state: NOT_RUNNING
PID: -
last message: Exited because nnmtrapreceiver service has stopped
exit status: Exit(1)

object manager name: nmsdbmgr
state: RUNNING
PID: 10344
last message: Database available.
exit status: -

object manager name: ovjboss
state: RUNNING
PID: 18908
last message: Initialization complete.
exit status: -
additional info:
SERVICE STATUS
CommunicationModelService Service is started
CommunicationParametersStatsService Service is started
CustomPoller Service is started
IslandSpotterService Service is started
ManagedNodeLicenseManager Service is started
MonitoringSettingsService Service is started
NamedPoll Service is started
NmsApa Service is started
NmsCustomCorrelation Service is started
NmsDisco Service is started
NmsEvents Service is started
NmsEventsConfiguration Service is started
NmsTrapReceiver Service is started
NnmTrapService Service is started
PerformanceSpiConsumptionManager Service is started
PipelineConfiguration Service is started
RbaManager Service is started
SpmdjbossStart Service is started
StagedIcmp Service is started
StagedSnmp Service is started
StatePoller Service is started
TrapConfigurationService Service is started
TrapPropertiesService Service is started
TrustManager Service is started

object manager name: qajboss
state: RUNNING
PID: (never run)
last message: Initialization complete.
exit status: -

object manager name: qajboss
state: RUNNING
PID: (never run)
last message: Initialization complete.
exit status: -

C:\Users\emsdradmin>ovstatus -v ovjboss
object manager name: ovjboss
state: RUNNING
PID: 18908
last message: Initialization complete.
exit status: -
additional info:
SERVICE STATUS
CommunicationModelService Service is started
CommunicationParametersStatsService Service is started
CustomPoller Service is started
IslandSpotterService Service is started
ManagedNodeLicenseManager Service is started
MonitoringSettingsService Service is started
NamedPoll Service is started
NmsApa Service is started
NmsCustomCorrelation Service is started
NmsDisco Service is started
NmsEvents Service is started
NmsEventsConfiguration Service is started
NmsTrapReceiver Service is started
NnmTrapService Service is started
PerformanceSpiConsumptionManager Service is started
PipelineConfiguration Service is started
RbaManager Service is started
SpmdjbossStart Service is started
StagedIcmp Service is started
StagedSnmp Service is started
StatePoller Service is started
TrapConfigurationService Service is started
TrapPropertiesService Service is started
TrustManager Service is started

C:\Users\emsdradmin>nnmtrapreceiver -status
Trap Receiver is STOPPED.

Re: TrapReceiver HornetQ Server: Down

asoloperto — Wed, 18 Dec 2019 13:35:51 GMT

Hello Dinesh,

please post the output of:

ovstatus -c

ovstatus -v ovjboss

nnmtrapreceiver -status

/opt/OV/support/nmshotfix.ovpl -L

BR Allessandro