[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
5796.0. "Targetting requests fail with wildcards" by CSC32::EMAWIZ::T_MILTON () Thu Dec 23 1993 14:31
I am seeing problems with targeting notifications when certain portions of
the targeting request or notify request are wildcarded. It seems that if the
adjacent node in the notify request is wildcarded then the associated target
won't function unless the specific node is stated. The reverse scenario also
functions when the notify request specifies the specific adjacent node and the
targetting request has a wildcard. Any ideas?
Ted.
Example:
Notify requests with wildcard for adjacent node:
Notification 1 - NODE4 VAX865 CIRCUIT * ADJACENT NODE * EVENTS =
ADJACENCY UP, ADJACENCY DOWN
Notification 2 - NODE4 ASTRSK CIRCUIT * ADJACENT NODE VAX865 EVENTS =
ADJACENCY UP, ADJACENCY DOWN
Associated Targets that fail to work:
NODE4 VAX865 CIRCUIT * ADJACENT NODE * EVENT ADJACENCY UP MANAGED OBJECT
NODE4 #1 CIRCUIT #2 ADJACENT NODE #3 TARGET ENTITY NODE4 #3 SEVERITY CLEAR
NODE4 VAX865 CIRCUIT * ADJACENT NODE * EVENT ADJACENCY DOWN MANAGED OBJECT
NODE4 #1 CIRCUIT #2 ADJACENT NODE #3 TARGET ENTITY NODE4 #3 SEVERITY MINOR
Targetting requests that work when you take out the wildcard for adjacent node:
NODE4 ASTRSK CIRCUIT * ADJACENT NODE VAX865 EVENT ADJACENCY UP MANAGED
OBJECT NODE4 #1 CIRCUIT #2 ADJACENT NODE #3 TARGET ENTITY NODE4 #3 SEVERITY
MINOR
NODE4 ASTRSK CIRCUIT * ADJACENT NODE VAX865 EVENT ADJACENCY DOWN MANAGED
OBJECT NODE4 #1 CIRCUIT #2 ADJACENT NODE #3 TARGET ENTITY NODE4 #3 SEVERITY
MINOR
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|