HPE Software Products: Network Management / (OpenView-NNM) Support and News Forum
Share |

core dump files are getting generated in NPSDATA directoryOpen in a New Window

Hi Team,

        We are facing issues with core dump files are getting generated with huge size more than 2 GB per file which is causing the E directory to be full within no time under below directory.

E:\Program Files (x86)\HP\HP BTO Software\nonOV\cognos\bi\bin64

Kindly let us know - how to fix this issue.

Thanks

Sandeep.

 

      

 

Unknown protocol packets?Open in a New Window

Hi everyone,

What is unknown protocol packets in NNMi? I found this in Dashboard > Interface Performance.

Thank you.

 

NNMi 10.x How to use web APIOpen in a New Window

Hello,

Could anyone explane how to use NNMi API for getting for example list of all nodes?

I saw a developers guide, but i have no understanding via which tool and which format of requests should i use.

Could anyone provide me with explanation and few examples, please

 

Thank you

 

Swith Port AlertsOpen in a New Window

Hi,

  i'm aware that we can schedule outage of a node for a specific time.Is there a way to schedule outage only for a specific port in the switch?Please advise

 

QA probes and Intelligent Response AgentOpen in a New Window

Looking to deploy the QA SPI to determine if Providers are meeting SLAs and also monitor site performance.  IF access to Cisco equipment is limited can we use Intelligent Response Agents deployed to servers at remote locations?  Is there any documnetation that descibes iRA client requirements?  Would Server automation be a tool for deploying and managing iRAs?

 

Humbly

Carl

 

 

How to stop monitoring of managed node daily for specific time period or scheduleOpen in a New Window

Hi,

We have recently deployed HPE NNM version 10.21 at RHEL 7.0. We also added multiple nodes succesfully and able to made some groups.

Now for some nodes we want to stop or hold monitoring for some specific time or schedule on daily. The business case for this is that some of our regional office dont work 24x7 and therefore not maintaining power in the same way. So core devices placed in the region office needs to shutdown after office hours and on holidays.

Kindly advise how can I confgure this in NNM for selected devcies.

Thanks

Rizwan

 

Set Management Address in nodes non-SNMPOpen in a New Window

Hi,

The nodes do not snmp, although they check their state by icmp appear without ip of management. Is it possible to assign the IP?
What we want is that on the down node traps, that send NNM also send the IP in addition to the Name.

 

PM/FM for Orange IPT linkOpen in a New Window

I have ran the nmdemandpoll again but still the interface TenGigE0/2/1/0 is not discovered,

Please guide on the same . i have given some of my results .

 

bash-2.05$ ./ovtopodump -v AMS-AM2-POP-CRS-1|grep TenGigE0/2

        INTERFACE NAME:  TenGigE0/2/2/0

        INTERFACE DESCRIPTION:  TenGigE0/2/2/0

        INTERFACE NAME:  TenGigE0/2/4/0

        INTERFACE DESCRIPTION:  TenGigE0/2/4/0

        INTERFACE LABEL: TenGigE0/2/4/0

        INTERFACE NAME:  TenGigE0/2/0/0

        INTERFACE DESCRIPTION:  TenGigE0/2/0/0

bash-2.05$

bash-2.05$

bash-2.05$ snmpwalk AMS-AM2-POP-CRS-1|grep TenGigE0/2

interfaces.ifTable.ifEntry.ifDescr.92 : DISPLAY STRING- (ascii):  TenGigE0/2/2/0

interfaces.ifTable.ifEntry.ifDescr.93 : DISPLAY STRING- (ascii):  TenGigE0/2/1/0

interfaces.ifTable.ifEntry.ifDescr.94 : DISPLAY STRING- (ascii):  TenGigE0/2/0/0

interfaces.ifTable.ifEntry.ifDescr.95 : DISPLAY STRING- (ascii):  TenGigE0/2/4/0

^C

bash-2.05$

 

NNM creates incorrect connections.Open in a New Window

Hello.

I use NNM 10.20.280. I have many devices with two ethernet ports and one mac for both ports. No cdp or LLDP like functions. Sometimes the NNM creates links with down port (pic1), and never checks or change them. If i delete the device and add it again, the connection will be correct. How NNM choose which interface use to create link?
The next question is about FDB connections. Initially, the devices didn't support dot1dBasePort and the connections were with the clouds. I added support dot1dBasePort and dot1dBasePortIfIndex to them and now:
collect.BaseCollectHandler] (pool-1-thread-18) DDTable= dot1dBasePort dot1dBasePortIfIndex
----------------------------------------
13 13
14 14 TalkStatus=NULL.
After that, some links became correct. But most of the devices remain without any connections. They have status  "Not Polled". Can anyone answer what information is needed for the NNM to make the correct connections?

Sample log, two device

local
id: 2147561461
downlink: 14
mac: 001349A4508F
port id: 2147561498

remote
id: 38655169894
uplink: 13
mac: 0019CB081026
port id: 38655169927

analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of Dot1dportDTO on switch 2147561461: 2
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) adding 2147561461 to switchIDs list.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of FdbDTO on switch 2147561461 port 13: 9
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of FdbDTO on switch 2147561461 port 14: 2
..skipped
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of Dot1dportDTO on switch 38655169894: 2
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) adding 38655169894 to switchIDs list.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of FdbDTO on switch 38655169894 port 13: 8
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of FdbDTO on switch 38655169894 port 14: 1
..skipped
analyzer.l2.SwitchFdbToConns] # of Dot1dportDTO on switch 2147561461: 2
analyzer.l2.SwitchFdbToConns] adding 2147561461 to switchIDs list.
analyzer.l2.SwitchFdbToConns] # of FdbDTO on switch 2147561461 port 13: 9
analyzer.l2.SwitchFdbToConns] # of FdbDTO on switch 2147561461 port 14: 2
..skipped
analyzer.l2.SwitchFdbToConns] Starting on switch 2147561461
bean.NmsConnectionBean] Found connected ifaces 0
analyzer.l2.SwitchFdbToConns] Found 0 currently existing connections on switch 2147561461.
analyzer.l2.SwitchFdbToConns] Starting on port 13
analyzer.l2.SwitchFdbToConns] # of FdbDTO on port 13: 9
analyzer.l2.SwitchFdbToConns] Node/Switch FDB: 0/9
analyzer.l2.SwitchFdbToConns] Fdb record com.hp.ov.nms.disco.bean.FdbDTO@edefff8d points to an unusable MAC address, so we are skipping it.
..skipped
analyzer.l2.SwitchFdbToConns] Fdb record com.hp.ov.nms.disco.bean.FdbDTO@4390c669 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] local 2147561461 remote 2149628482...
analyzer.l2.SwitchFdbToConns] ...found potential interswitch 17179960728, checking for meshes
analyzer.l2.SwitchFdbToConns] ...local switch does not hear interswitch 17179960728
analyzer.l2.SwitchFdbToConns] ...remote switch hears interswitch 17179960728 on same port as local
analyzer.l2.SwitchFdbToConns] ...interswitch 17179960728 is valid
analyzer.l2.SwitchFdbToConns] Starting on port 14
analyzer.l2.SwitchFdbToConns] # of FdbDTO on port 14: 2
analyzer.l2.SwitchFdbToConns] Node/Switch FDB: 0/2
analyzer.l2.SwitchFdbToConns] Fdb record com.hp.ov.nms.disco.bean.FdbDTO@bdf49760 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] Fdb record com.hp.ov.nms.disco.bean.FdbDTO@bb7d409b points to an unusable MAC address, so we are skipping it.
..skipped
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Starting on switch 38655169894
bean.NmsConnectionBean] (pool-1-thread-28) Found connected ifaces 0
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Found 0 currently existing connections on switch 38655169894.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Starting on port 13
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) # of FdbDTO on port 13: 8
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Node/Switch FDB: 0/8
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Fdb record com.hp.ov.nms.disco.bean.FdbDTO@e8ac1891 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Fdb record com.hp.ov.nms.disco.bean.FdbDTO@eeb0cd00 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Fdb record com.hp.ov.nms.disco.bean.FdbDTO@f117d356 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Fdb record com.hp.ov.nms.disco.bean.FdbDTO@4ec28231 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) local 38655169894 remote 2149628482...
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...found potential interswitch 2147561461, checking for meshes
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...local switch does not hear interswitch 2147561461
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...remote switch hears interswitch 2147561461 on same port as local
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...interswitch 2147561461 is valid
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Fdb record com.hp.ov.nms.disco.bean.FdbDTO@4eeb3a26 points to an unusable MAC address, so we are skipping it.
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) local 38655169894 remote 2147573635...
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...found potential interswitch 2147561461, checking for meshes
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...local switch does not hear interswitch 2147561461
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...remote switch does not hear interswitch 2147561461
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) ...interswitch 2147561461 is valid
analyzer.l2.SwitchFdbToConns] (pool-1-thread-28) Fdb record com.hp.ov.nms.disco.bean.FdbDTO@edf4cc2b points to an unusable MAC address, so we are skipping it.

bean.NmsDiscoFdbBean] Unchanged FDB (pid: 36507265673) for Node (pid): 2147561461
Port: com.hp.ov.nms.disco.model.Dot1dPort{class = class com.hp.ov.nms.disco.model.Dot1dPort, id = 36507265662, ifIndex = 14, ifPid = 2147561498, ifType = 6, mac = 001349A4508F, nodeId = 2147561461, port = 14, tenantUUID = 1b96011e-8829-4e5d-8ab7-f93b7b10ac79, uuid = 29794858-0ad2-4ac3-a04f-9fa7d9f302d4}
VLAN: 900 MAC: 0019CB081026 RESOLVED to Remote Node (pid): 38655169894
Type: Switch Interface (pid): 38655169927 (shared mac)

How can i check why some mac is unusable? 

Thanks!

 

NNMi Instalation on RedHat, DB connection errors to remote OracleOpen in a New Window

Good day everyone,

I'm hoping the wealth of knowledge here can get me out a situation where the NNMi install fails with DB connection errors. Vital statistics are:

NNMI 10.20

Red Hat Enterprise Linux Server release 6.8 (Santiago)

Oracle 12c R1 (12.1.0.x)

The installer CAN connect to the DB in the first instance, as using SQL+ to query the DB shows that the tablespaces have been created. However, it then loses the connection and throws an error saying it cannot connect. Weird and extremely annying as my project is currently blocked.

Can you guys give me a list of "gotchas" that may cause this behaviour as we are out of ideas!

 

How to configure two thresholdsOpen in a New Window

Hi team,

Can some one tell me how to configure two thresholds for CPU and memory utilization for example: 75% for warning

and 85% for major alerts has to get .

 

NNMI filter on L2Connection by interfaceOpen in a New Window

Hi,

I am trying to get all L2Connection to an interface.

I am not sure how to specify the filter!!!

When calling it with below request, I got nothing returned.  

<l2c:getL2Connections>
 <arg0 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns3="http://filter.sdk.nms.ov.hp.com/" xsi:type="ns3:expression">
  <subFilters xsi:type="ns3:constraint">
   <name>maxObjects</name>
   <value>200</value>
  </subFilters>
  <subFilters xsi:type="ns3:condition">
   <name>interfaces</name>
   <operator>EQ</operator>
   <value>4295042852</value>
  </subFilters>
 </arg0>
</l2c:getL2Connections>

When no argument is specified in the request, it will return the L2 connection for that interface id.

<l2c:getL2ConnectionsResponse xmlns:l2c="http://l2connection.sdk.nms.ov.hp.com/">
 <return>
  <item>
   <created>2010-06-08T20:38:33.795-04:00</created>
   <id>4295091276</id>
   <interfaces>4295042852</interfaces>
   <interfaces>47263677743</interfaces>
   <modified>2010-06-08T20:38:33.795-04:00</modified>
   <name>xxxxxxxxxxxxxxxxxxxxx</name>
   <notes/>
   <status>NORMAL</status>
   <uuid>xxxxxxxxxxxxxxxxxxxxxx</uuid>
  </item>

Any help is greatly appreciated.

Terry

 

Jboss version in NNMi 9 and 10?Open in a New Window

Hi everyone,

I was wondering which jboss version are NNMi 9 and 10 using? Where can I find it?

Thank you.

 

ciscoIPSSSM10 Monitoring in NNMi 10 Device does not support way of collecting dataOpen in a New Window

Dear All,

 

We have discovered the ciscoIPSSSM10 device as SNMP node in NMi 10.

However when we say config poll of the device, it says below,

Does that mean , NNMi does not support this device and I will need to upload MIBs in order to poll the required parameters like interface util, etc from the device??

 

As I belive Inferface util comes on IfMIB which should be polled by default.

Please confirm.

 

Configuration Poll of 172.*.*.*
Using timeout of 600 seconds.
Connecting to server for configuration poll.

3/1/17 9:54:01 AM  **** Starting configuration poll of node eLMS-IPS01-A(dec041c5-1ef0-4677-b802-8cb4c2ac9aad) ****

3/1/17 9:54:02 AM  Supports SNMP V2C

3/1/17 9:54:02 AM  Get NodeInfo. Found entries:1

3/1/17 9:54:12 AM  Get NodeCapabilities retrieved no data because this device does not support a way of collecting data.

3/1/17 9:54:12 AM  Get SnmpContext retrieved no data because this device does not support a way of collecting data.

3/1/17 9:54:22 AM  Get MigratableAddresses retrieved no data because this device does not support a way of collecting data.

3/1/17 9:54:22 AM  Get Addresses retrieved no data because this device does not support a way of collecting data.

3/1/17 9:54:22 AM  Get Ipv6Addresses retrieved no data because this device does not support a way of collecting data.

3/1/17 9:54:22 AM  Get AnycastIPAddress retrieved no data because this device does not support a way of collecting data.

 

Does NNMI's soap API have a function for triggering scheduled node outages?Open in a New Window

Hello,

Does NNMI's soap API have a function for triggering scheduled node outages? I would like to integrate this functionality into a management portal but I'm not able to find anything for triggered node outages in the WSDL. I did look at the managementmode function which I'ved used before, but it does not mention anything about scheduled outages.

 
<xs:simpleType name="managementMode">
<xs:restriction base="xs:string">
<xs:enumeration value="INHERITED"/>
<xs:enumeration value="MANAGED"/>
<xs:enumeration value="NOTMANAGED"/>
<xs:enumeration value="OUTOFSERVICE"/>
</xs:restriction>
 
 
scheduled.png

 

FATAL Error on my NFS ServerOpen in a New Window

Hello everyone !

I have a a fatal error on my new NNmi configuration, I don't understand what's wish say logs:

Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 0. /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm:981 [NPS::npslog::FATAL()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 1. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:6104 [main::handle_dbi_err()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 2. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:6077 [main::eval_dbh_do()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 3. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:5328 [main::eval_lock_dbh_do()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 4. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:694 [main::commit_update_topology_records()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 5. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:523 [main::process_topodump_file()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 6. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:435 [main::process_topodumps()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 7. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:382 [main::get_topology()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Stacktrace: 8. /opt/OV/NNMPerformanceSPI/bin/.etl-runtime.Component_Health.ovpl:165 [main::processDataLoop()]
Feb 28, 2017 02:47:00 PM [PID:6105] FATAL /opt/OV/nonOV/perl/a/bin/../lib/site_perl/NPS/npsDB.pm[981] ETL.Component_Health Unable to automatically handle DB error: Non-space text found after ending quote character for an enclosed field.
-- (dblib/db_RecScanner.cxx 2075) (DBD: execute failed)

Thank you everyone for your answer !

Have a good day !

 

Creating Custom NPS report for Business HoursOpen in a New Window

Dear Friends,

We know, NPS provides a functionality to select certain Business hours while launching 'Out of the Box' reports.

How can we achieve the same for any custom NPS report ?

 

Cheers,

 

what is server.CRT and CA.crt while importing certificates into NNMi.Open in a New Window

Hi,

 

i would llike to the difference between the server.crt and ca.crt while importing the organization signed certificates.

i applied for CA certificate to my organization and my CA admin provided only one file, but in the deployment guide it says i must import server.crt and ca.crt to the truststore and keytstore respectively.

PS: i have received CA signed certificate as single file which just has --begin certificate--- and ---end certificate--- 

 

Does NNMI support AP monitoring via managed WLCs for cisco 4402 WLCsOpen in a New Window

Hello,

We recently began using the feature that was included in QCCR1B146008, which allows NNM to monitor APs through their controllers without having to have the APs themselves registered as individual seeds in NNMI. While this has been working pretty well so far, we've noticed that cisco 4402's are not working properly with this feature. Their chassis tabs are completely empty and are not reporting any APs.

Has anyone else encountered this particular problem, or does anyone know if this particular WLC model is not supported for this type of monitoring? 

Thank you

 

'nnmrestore.ovpl' returns error although version/patch level is the sameOpen in a New Window

Hello experts,

We are trying to backup & restore the data of a NNM9.20 IP4 installed in Windows 2008 R2 (single server) in an identical version on RHEL6.5. Although the version and patching level are the same, the restore command returns the version/patch error:

/opt/OV/bin/nnmrestore.ovpl -force -source /backup/nnm-bak-20170227060003
ERROR: Backup can only be restored against the same product version and same patch level.

Backup version:

NNMVersion=9.20,9.23.003,9.23.004
NNMProductLicVersion=8.0, 1.0
ServerType=Primary
InstallType=Full Install
ImageBuiltTime=Sat May 19 07:14:49 MDT 2012
NNMInstallVersion=English Release
package=NNM920_00003,{8C5413F2-247C-439A-82FB-0702F4E2BA7F}
package=NNM920_00004,{08112A7F-EE46-4F83-85A5-0AD792DBDBF9}

Current version:

NNMVersion=9.20,9.23.003,9.23.004
NNMProductLicVersion=8.0, 1.0
ServerType=Primary
InstallType=Full Install
ImageBuiltTime=Sat May 19 06:46:14 MDT 2012
ImageDevelopmentCycle=
NNMInstallVersion=English Release
package=NNM920_00003,NNM920L00003
package=NNM920_00004,NNM920L00004

I don't find any issue apart from the possibility that this feature does not work when transferring data between different platforms (Win / Linux). Am I right? Or is there anything wrong in the process?

Many thanks in advance.

Angel

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.