All board posts in Network Operations Management

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

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.

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...

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: 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

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: 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: 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.

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: 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

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: 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: 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: 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: 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

TrapReceiver HornetQ Server: Down

fms_bsdc — Wed, 18 Dec 2019 12:27:49 GMT

Please suggest for issue.

thanks

Dinesh

Re: NNM SDK using WebService

asoloperto — Wed, 18 Dec 2019 11:42:44 GMT

Hello KAKA,

what is your NNMi version?

BR Allessandro

Re: HP NNMI -NA integration

asoloperto — Wed, 18 Dec 2019 11:33:12 GMT

Hello,

first step is to check nnm-trace.log for errors, when you submit the configuration.

If the error is not specific enouph I would set the logging for the module in the log file to FINEST (e.g. $NnmInstallDir/support/nnmsetlogginglevel.ovpl com.hp.ov.nnm.na.im FINEST) and repeat the submission.

Perhaps some of the actions in the JMX console can help (http://<nnm-host>/jmx-console/HtmlAdaptor?action=inspectMBean&name=com.hp.ov.nnm.na.im%3Ambean%3DNnmNaModule on localhost).

HTH and best regards

Allessandro

Re: How to find all nodes which are "OutofService" under "Node Management Mode"

asoloperto — Wed, 18 Dec 2019 11:22:03 GMT

Hello,

you can use nnmtopodump:

nnmtopodump.ovpl -type node -filter node.managementMode=OUTOFSERVICE

(other modes are "MANAGED" and "NOTMANAGED")

Use "nnmmanagementmode.ovpl -node.name <nodename> -mode <mode>" to set the management mode (see reference page for the command).

HTH and best regards

Allessandro

Re: NNMi HA cluster %2C SNMP request to devices is going from active server but not common virtual I

asoloperto — Tue, 17 Dec 2019 11:00:57 GMT

Hello Hanumant,

yes, I would give it a try.

BR Allessandro

Re: ERROR: Cluster name not defined properly in NPS prspi.log

Maarten_K — Tue, 17 Dec 2019 10:30:49 GMT

You can try the following:

Stop the NPS with the stopall.ovpl command on the NPS server.
Copy the cluster.keystore file from %NnmDataDir%\shared\nnm\conf\nnmcluster on the active NNMi node to %npsdatadir%\nnmappfailover\keystore on the NPS node.
Copy the nnmgetactive.zip from the %NnmDataDir%\shared\perfSpi\Datafiles on the active NNMi node directory to %NPSDataDir%/nnmappfailover on the NPS server and unzip it in this folder. Overwrite the files.
Start the NPS with the startall.ovpl command.

Re: ERROR: Cluster name not defined properly in NPS prspi.log

Alejandro Bolance — Tue, 17 Dec 2019 07:33:20 GMT

Good day,

exactly the same thing happened to me, did you find a solution?

I add to the thread that the Output that gives the execution of the command is: ClusterNotRunningError

Best regards,

Alejandro Bolancé.

Re: NNMi HA cluster %2C SNMP request to devices is going from active server but not common virtual I

HanumantMadane — Mon, 16 Dec 2019 06:38:26 GMT

Hi Allessandro,

Should we add the P address that we want as a source IP address in this file mentioned and check with what IP address NNMi is going with SNMP request.

Hope we can make NNMi take the common virtual IP that we want.

Regards,

Hanumant

HP NNMI -NA integration

connection — Sat, 14 Dec 2019 07:47:21 GMT

Hi Team,

I need quick help to resolve integration issue.

NNMi Version 2019.11 and NA version is 2019.5

NNM and NA certificate exchanged and restarted the service

Integration form filled all the details required. and getting the error below.

"Error: Unable connect to remote NA host. Please check host, port and credentials and verify that NA certificate has been added as a trusted certificate if using ssl"

Thanks

Re: NNMi HA cluster %2C SNMP request to devices is going from active server but not common virtual I

asoloperto — Fri, 13 Dec 2019 19:19:46 GMT

Hello,

please check the file nms-communication.properties in NnmDataDir\shared\nnm\conf\props for the property com.hp.ov.nms.comm.snmp.sourceAddress.

HTH and best regards

Allessandro

Re: add NNMi nodegroup to incident or CMA

asoloperto — Fri, 13 Dec 2019 18:58:34 GMT

Hello,

the agent and web service integration does not contain information about the Node Group membership of the node so it is not possible out of the box.

I would use an EPI script in OBM to get these information. I see 2 possibilites:

1. NNMi Web Service bean Node Group with getNodeGroupsByNode (my preference)

2. JMX console: nnmtwiddle.ovpl invoke com.hp.ov.nms.monitoring:mbean=NodeGroupAssignmentCacheService dumpCacheForNode abc.com

HTH and best regards

Allessandro

NNM and Firefox 52.9

Mel Farber — Fri, 13 Dec 2019 15:22:27 GMT

My customer has just upgraded to Firefox 52.9. We are running 2018.05 and 2019.05. When I right click on a line to get the NNM menu, I get a Firefox menu, with Save page as, Select ALL, View Page Source. Depending on the length of the NNM menu, I can see some of the lines of the NNM menu, but for the most part I cannot access the NNM menus.

Has anyone seen the problem and have a solution (other than saying use a different browser), I would greatly appreciate it.

Thanks,
Mel

Detected query which has been running for PTXHXXMXXS COMMIT

iamnoone — Thu, 12 Dec 2019 17:40:45 GMT

Greetings and Thank you,

Running 10.00+ on linux and seeing the following message in the nnm-trace.log

Timestamp WARNING [com.hp.ov.nms.topo.ejb.monitor.agents.PostgresHealthAgent] (pool-l-thread-x) Detected query which has been running for PT7H43M19.132S : COMMIT

1. is this serious?

2. How would I determine how to clear it?

add NNMi nodegroup to incident or CMA

RPS_Sholm — Thu, 12 Dec 2019 12:50:55 GMT

Hello.

I would like to extend our forwarded NNMi incidents to HPOM/OBM with the name of the corresponding nodegroup.
A node can belong to several groups, but lets ease up the ambition and pretend there is only one, can this be done?

Br Fredrik

NNMi HA cluster %2C SNMP request to devices is going from active server but not common virtual IP

HanumantMadane — Thu, 12 Dec 2019 11:12:13 GMT

I have already configured NNMi on HA cluster and it is working fine.

We are using below two servers and four IP’s, The application is running on http://pntest34i.abcd.corp/nnm (11.100.**.49 which is virtual IP).

pnnmtest01i.vodacom.corp
11.100.**.129 - Physical IP
11.100.**.45 – Virtual IP

pnnmtest02i.vodacom.corp
11.100.**.130 - Physical IP
11.100.**.46 – Virtual IP

The snmp request is getting sent to end nodes from virtual IP (11.100.**.45/11.100.**.46) instead of 11.100.**.49 as this IP is getting assigned on active node in HA cluster.

So can someone confirm,

1. with Which IP address NNMi should send SNMP request to the devices??

2. or when NNMi is active on one of the server, then request is sent from virtual IP of that server as per product design???

for example: if NNMi is active on 11.100.*.45 server then SNMP request should go from 45 and if active server is 46 then request should go from 46??

3. also, irrespective of any server being active, can we make NNMi to send SNMP request to devices from only one virtual IP i.e. 11.100.**.49

Re: snmp V3 connection failing

Ameren — Wed, 11 Dec 2019 17:43:18 GMT

update - snmpv3 config file was inaccurate

Network Automation postgres DB supports

Dayanand1 — Wed, 11 Dec 2019 05:40:08 GMT

Hi Experts,

Need quick answer whether NA supports embedded postgres if installation done in horizontal scalability with 2 NA cores and also whether it supports in disaster recovery configuration .

Regards,

Dayanand

Network Automation embedded DB data replication

Mohan_M — Wed, 11 Dec 2019 05:32:29 GMT

Hello Experts,

if we have two different NA core servers with embedded postgres DB, then is there any way to do the database replication between both NA servers? or whether it supports the disaster recovery configuration. please guide with the documents if any..

Re: DB Error when installing NA - EXECUTE on CTXSYS.ctx_ddl

Chris_Powers — Tue, 10 Dec 2019 15:53:06 GMT

Hi,

Ugh, this is a difficult situation. No fun and this should be relatively easy...

So, most of the time I've had this problem or something similar, the DBA would either find they made a mistake somewhere or it would by a miracle, work the next day after I was told they didn't make a mistake and requested I try again.

There have been one or two times I needed to bring support in to the mix as I would get an Oracle error and the DBA would say there was no issue on their side and support (CPE) would provide some feedback for the DBA as to what needed to be resolved.

I can't think of a time I've installed a core where I got a DB related issue (Oracle, MySQL, Postgres, SQL Server) that wasn't tied back to some DB issue. Don't think I've had an issue where I saw an option I could skip. Bit different, but we had some similar problems with OBR / NA but again, was DBA related.

Guessing not the issue, but just guessing as to what else it might be... What's the Oracle version? Is this RAC? Have you tried connecting to the DB and looking around? Just trying to think what else it might be...

Is this a HS or MM setup? You gave the DBA the 10.20 sql files and not 2019.05?

Guessing you have, but will ask, have you looked at the install logs in $NA_install_dir/server/log? (install_*) I have seen issues crop up in one log file that didn't really show until later, so that might be useful to look at.

I'd certainly open a case first before just skipping this as if there is a problem, you don't want to find out down the road as then it will be so much harder to address. (and send the install_* logs)

Hope this helps and good luck!

-Chris

nnmi behind proxy

ThibaudA — Tue, 10 Dec 2019 15:45:09 GMT

Hi everyone,

Does anyone configure the NNMi Web interface behind revers proxy ?

I need to configure my NGNIX Revers proxy and I'm facing some issue.

Thanks in advance.

Regards,

Thibaud

Re: DB Error when installing NA - EXECUTE on CTXSYS.ctx_ddl

Ivonne Nirich — Tue, 10 Dec 2019 14:59:57 GMT

Hi Chris,

Thanks a lot for your valuable help!

I am in a tricky situation, the DBA says that the privileges are set, but that the error is on the pre-check of the installer. I think differently, as this is the first time of many I face this issue.

How did you mitigate this? I already send this out to the customer and this is

the response about the checking of the privileges is:

GRANTEE OWNER TABLE_NAME GRANTOR PRIVILEGE GRA HIE COM TYPE INH
--------------- --------------- -------------------- --------------- --------------- --- --- --- ------------------------ ---
NAUSER CTXSYS CTX_DDL CTXSYS EXECUTE NO NO NO PACKAGE NO

But the installer still stop here.

Thanks!

Regards,

Ivonne

Re: Have a few questions related Network Automation product

Chris_Powers — Tue, 10 Dec 2019 13:51:26 GMT

I'd suggest looking here:
https://docs.microfocus.com/itom/Network_Automation:2019.05/Home

The documentation can address many, if not all, of your questions.

Otherwise, you might want to reach out to your Micro Focus person / people.

Many of these questions are based on your company (size, devices, plans, etc). So, if you have a Micro Focus team working with your company, they may be better to answer some of these questions. But in general, the documentation will help!

-Chris

Have a few questions related Network Automation product

Namanh95h — Tue, 10 Dec 2019 01:48:39 GMT

Dear Experts,

I have few questions on the Network Automation products that I cannot find the answers:

Could you please help me to answer as below questions:

1. Is there any use of any content management module (CMS) (If yes then which?)

2. The size of Application (estimated)? (In case of more than 1 application, please provide details for each application)
- No. of dynamic pages
- No. static pages

3. Approximated data entry points (total input fields) in the whole application. (Approximate number?)

4. Type of Authentication used (Form Based/Certificate Based)?

5. No. of web services, if any?

6. No. of methods in all web service?

7. Web/Application Server with version (e.g. llS, Apache, Tomcat etc.)

I am looking forward to your valued answer

Best Regards,

Anh, Nguyen Nam

NNMI details?

Longnguyen612 — Mon, 09 Dec 2019 08:27:51 GMT

Hi all,

I have some questions on the Network Nodem Manager i(NNMI) product.

Could you please help me?

1. Is there any use of any content management module(CMS) (If yes then which?)

2.Estimated size of Application ? (In case of more than 1 application, pls provide details for each application)
- No. of dynamic pages
- No. static pages

4 Approximate data entry points (total input fields) in the whole application. Please provide approx number.

5 Type of Authentication used (Form Based/Certificate Based)?

6 No. of web services, if any?

7 No. of methods in all web services?

8 Web/Application Server with version (e.g. llS, Apache, Tomcat etc.)

Best Regards,

Long

snmp V3 connection failing

Ameren — Thu, 05 Dec 2019 18:40:43 GMT

NNMI version 2018 v11

Having trouble connecting to a snmp v3 device with

HMAC-SHA-1 authentication

DES-CBC Passphase

Setup a snmpwalk.ovpl script returns the following

Exception thrown while writing request PDU: Algorithm not in allowed list: DES/C

I suspect possible java issue, but not sure.

We are running on a RHEL server. Using external JAVA 1.8.0

Device Password Rules using Bastion Host

evapa8f — Thu, 05 Dec 2019 17:08:49 GMT

Trying to setup a device password rule that can be used to login to all of my devices but I am unable to set up the Bastion Host information with the device password rule.

When I add a new device I can enter device specific password information then later in the form there are the fields for the Bastion Host. I would like to set it up so I can use a Device password rule to login to all devices using the Bastion Host

Thanks in advance for your help.

Re: Nodes getting deleted from NNMi

connection — Thu, 05 Dec 2019 08:59:15 GMT

MF support is still looking to the issue.

Re: Customize mail that is send from report

BeniG — Thu, 05 Dec 2019 08:38:03 GMT

Hey Chris

Thanks for the feedback, I already suspected that doing it with linux tools is probably the only solution, just wanted to check with the community. You never know 🙂

Beni

NNMi 2019.05 P2 - Bug in nnmbackup.ovpl

FrankMortensen — Thu, 05 Dec 2019 08:34:41 GMT

Hi,

I hope that someone from MF Support reads this and file it internally as a bug.

I have recently discovered in my customer's recently upgraded NNMi 2019.05 Patch 2 env. on Windows that the nnmbackup.ovpl does not work, at least not with an offline backup (I assume that it works for online backups).

The backup fails at a stage when trying to move the Postgres DB-files to a new directory. From what I have seen the relevant part of the code in nnmbackup.ovpl was rewritten in Patch 2, and this seems to have introduced the bug. The change I am talking about is a subroutine that used be to called 'moveSpecialFiles' that has now been renamed to 'processFiles'. One of the differences is that the latter takes one less parameter than the former. The subroutine is called several times for different types of backup files, and when called to move the Postgres-files it still passes that extra parameter to the subroutine (MF has updated all other calls to the subroutine, it seems, but not the call related to the DB-files). I therefore removed this extra parameter even for the DB-files and now offline backups work as desired.

The line I am talking about originally looks as follows in NNMi 2019.05 P2:

processFiles($SPECIAL_DIR . $DATABASE_DIR, $databaseFile, $srcLength, eval {my $z = nls(432, q"for database restoration"); $z =~ s/(\$[\w_!?]+)/$1/eeg; return $z}, @DATABASE_FILES);

I changed it to:

processFiles($SPECIAL_DIR . $DATABASE_DIR, $srcLength, eval {my $z = nls(432, q"for database restoration"); $z =~ s/(\$[\w_!?]+)/$1/eeg; return $z}, @DATABASE_FILES);

I assume that this info. could be of interest to other people with the same NNMi version who create offline backups.

BR,
Frank Mortensen
Managon AB

Back UP status in Network Automation

Ranjitha_S — Thu, 05 Dec 2019 04:41:19 GMT

Hello Everyone,

Good Day!!!!

Any one please help us to navigate to automatic backup configuration in NA tool.

Thanks in advance.

Re: Deploy NOM 19.11 CDF problem

Patrick_Deloulay — Wed, 04 Dec 2019 18:52:43 GMT

You would need to open a support case – Please visit - https://softwaresupport.softwaregrp.com/

Business view not loading in omi console

Tupere — Wed, 04 Dec 2019 13:38:38 GMT

Hi Team,

We are having OBM in HA enviroment with version 2018.11. We have configured custom business view ,

recently we are facing issue Business view is not reflecting and getting error as ""

NNMI - NA integration

connection — Wed, 04 Dec 2019 10:53:24 GMT

Hi All,

We are using nnmi 2019.05 NA 2019.05.

We are facing issues integrations.

1. Certificates exchanged between NNMI and NA

2. restarted the services.

3. port 443 is opened verified with telnet from NNMi server to NA server.

4. credentials are verified and still we are facing issue.

NA integration configuration update failed.

Error:Unable connect to remote NA host. Please check host, port and credentials and verify that NA certificate has been added as a trusted certificate if using ssl.

Please help me to resolve the issue.

Thanks

Type your subject here...FATAL ERROR during the NA installation

Itayala — Wed, 04 Dec 2019 09:19:46 GMT

Hello, I have some fail during the installation, the version is 2019.05 When I go to the log file I can see the below output: Custom Action: com.rendition.installer.DBVerifyAction Status: FATAL ERROR Additional Notes: FATAL ERROR - class com.rendition.installer.DBVerifyAction FatalInstallException: Internal Error: ERROR: relation "rn_device_software_image" does not exist Position: 32 Thanks for any help.

Generating NPS report on HSRP status

JM_M — Wed, 04 Dec 2019 09:11:49 GMT

Hi,

We need to use iSPI Performance for Metrics to generate a report on the availability of HSRP for some redundant routers, but I'm unable to find how to query info about an HSRP redundancy group from NPS.

This data is available in NNMi under Router Redundancy Groups, but there doesn't seem to be any Redundancy Group object (or HSRP, or similar) in the topology selector, nor anywhere else that I can see.

I could, maybe, group the interfaces hosting the HSRP IPs in an interface group, but that'd get me the individual status for those interfaces, not the availability of the HSRP. And also, since the info regarding the HSRP availability is readily available in NNMi, I'd guess there should be some straight forward method to create a report for that info.

Re: Deploy NOM 19.11 CDF problem

Arun Jayaprakash — Wed, 04 Dec 2019 07:01:10 GMT

NOM 2019.11.0.39 is the right metadata and it only supports NOM Ultimate with BVD as its only capability. You cannot change to Premium after installation.

This is for NOM customers who are using Classic.

Re: Customize mail that is send from report

Chris_Powers — Tue, 03 Dec 2019 17:30:55 GMT

I'd say given what your requirements are and what is doable out of the box today, your best option would be to export it and use cron as you mentioned.

That said, if you had Operations Orchestration, you might be able to create a flow that did everything you wanted, but this might not meet the criteria of using out of the box NA features.

Good luck!

-Chris

Re: Deploy NOM 19.11 CDF problem

Marko Selan — Tue, 03 Dec 2019 15:45:38 GMT

User discussion not the right place ? Can you point me to the right direction then ?

Re: Deploy NOM 19.11 CDF problem

Patrick_Deloulay — Tue, 03 Dec 2019 15:42:26 GMT

Hi Marko. We should not use this portal to relay software related issues. Based on your findings it looks like indeed the suite image bundle definition does not match what is available in our Docker Hub repositories. I will contact NOM Team immediately and they will follow-up with you.

Customize mail that is send from report

BeniG — Tue, 03 Dec 2019 15:23:11 GMT

Hi all

Maybe one of you has already found a good solution for this. For compliance reasons we need to regularly document the compliance state of individual devices.This seems easy - Search for compliance, select the devices and the corresponding policies.

But the problem is the automated storage of this report (I plan to send it to Sharepoint) or to be more precise the customization of the email-report. It would preferably be sent as PDF-Attachment with a defined naming convention, like <Year><Month>_<ReportName>. I would like to use the out-of-the-box feature from NA to send reports by mail but it seems to be lacking this options.

How are you handling reporting tasks like this? Do you export to <NA_Home>/addins and then run a cron to have the flexibility?

Regards

How to find all nodes which are "OutofService" under "Node Management Mode" using command line?

Bharath Kumar — Tue, 03 Dec 2019 14:49:24 GMT

Hi Everyone,

I would like to find all devices which are marked as "OutofService" and marked them as "Managed". Let me know how can I find all devices which are marked as "OutofService" and how can I change them to "Managed" using command line interface. (Don't want to use GUI).

Regards,

Bharath Kumar.