Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

2 nodes merged into one

Description

With recent head, I have wo nodes that merged into one. Neither of these nodes
is in capsd config ip range but are defined in poller config. Also the same
nodes as in NMS-1139. Looking at the capsd log shows that they where in fact
scanned before the merge occured. I will attach relevant log files and configs
as well as snmpwalks of the nodes.

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Attachments

3

Lucidchart Diagrams

Activity

Ted Kaczmarek December 4, 2005 at 7:54 AM

Flagged for aggregated capsd issue.

Ted Kaczmarek August 15, 2005 at 8:37 AM

Don't have access to anything to test this on any more.

Ted Kaczmarek February 8, 2005 at 10:56 AM

Last attachment is for different bug id, sorry.

Ted Kaczmarek February 8, 2005 at 10:20 AM

Created an attachment (id=153)
caps log and db entries

Ted Kaczmarek January 26, 2005 at 11:10 AM

I don't think this has anything to do with Postgres 8.0, unless the new jar file
could cause capsd to scan an ip interface that is not in capsd config.

Cannot Reproduce

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created January 26, 2005 at 10:43 AM
Updated January 27, 2017 at 4:30 PM
Resolved September 6, 2010 at 3:34 PM