T.R | Title | User | Personal Name | Date | Lines |
---|
2204.1 | please get me the following information | TOOK::CALLANDER | MCC = My Constant Companion | Tue Jan 28 1992 09:39 | 18 |
|
I am having some problems getting ucx running on my node so if you
could help me here...could you please do the following for me:
sho domain <name> member * all char
and then for each of those that says it is an snmp node could you
please do a
sho snmp <ns:.name> all ident
I can't see anything that would cause this problem, but
if you could get me this info that might help a bit. I will
see what I can do about testing it here as well.
jill
|
2204.2 | here it is | NSCRUE::KEANE | U.S. NIS Service Engineering and Delivery | Tue Jan 28 1992 10:18 | 179 |
|
show domain .mcc.domain.ip member * all char
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.sunrise
!AT 28-JAN-1992 08:13:20 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.sunrise
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.msu-east
!AT 28-JAN-1992 08:13:21 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.msu-east
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.east
!AT 28-JAN-1992 08:13:21 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.east
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.north
!AT 28-JAN-1992 08:13:21 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.north
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.south
!AT 28-JAN-1992 08:13:22 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.south
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.lights
!AT 28-JAN-1992 08:13:22 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.lights
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.cross
!AT 28-JAN-1992 08:13:22 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.cross
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.mcc-north
!AT 28-JAN-1992 08:13:22 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.mcc-north
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.decserver-300
!AT 28-JAN-1992 08:13:22 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.decserver-300
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.MCC.IP.mcc-east
!AT 28-JAN-1992 08:13:23 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.MCC.IP.mcc-east
!
!Domain DSP_NS:.mcc.domain.ip Member DSP_NS:.mcc.ip.decstation-slip
!AT 28-JAN-1992 08:13:23 Characteristics
!
!Examination of attributes shows
! Member Type = Static
! Member Entity = SNMP DSP_NS:.mcc.ip.decstation-slip
!
show snmp dsp_ns:.mcc.ip.sunrise all ident
!
!SNMP DSP_NS:.mcc.ip.sunrise
!AT 28-JAN-1992 08:13:48 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.0.1
! Name = SUNRISE
!
show snmp dsp_ns:.mcc.ip.msu-east all ident
!
!SNMP DSP_NS:.mcc.ip.msu-east
!AT 28-JAN-1992 08:13:58 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.0.2
! Name = msu-east
!
show snmp dsp_ns:.mcc.ip.east all ident
!
!SNMP DSP_NS:.mcc.ip.east
!AT 28-JAN-1992 08:14:05 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.0.254
! Name = east.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.north all ident
!
!SNMP DSP_NS:.mcc.ip.north
!AT 28-JAN-1992 08:14:18 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.16.254
! Name = north.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.south all ident
!
!SNMP DSP_NS:.mcc.ip.south
!AT 28-JAN-1992 08:14:24 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.32.254
! Name = south.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.lights all ident
!
!SNMP DSP_NS:.mcc.ip.lights
!AT 28-JAN-1992 08:14:31 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.16.1
! Name = lights.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.cross all ident
!
!SNMP DSP_NS:.mcc.ip.cross
!AT 28-JAN-1992 08:14:36 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.32.1
! Name = cross.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.mcc-north all ident
!
!SNMP DSP_NS:.mcc.ip.mcc-north
!AT 28-JAN-1992 08:14:45 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.16.2
! Name = msu.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.decserver-300 all ident
!
!SNMP DSP_NS:.mcc.ip.decserver-300
!AT 28-JAN-1992 08:14:54 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.0.4
! Name = decserver-300.nis.cxn.dec.com
!
show snmp dsp_ns:.mcc.ip.mcc-east all ident
!
!SNMP DSP_NS:.mcc.ip.mcc-east
!AT 28-JAN-1992 08:15:03 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.0.3
! Name = mcc-east
!
show snmp dsp_ns:.mcc.ip.decstation-slip all ident
!
!SNMP DSP_NS:.mcc.ip.decstation-slip
!AT 28-JAN-1992 08:15:18 Identifiers
!
!Examination of attributes shows:
! Address = 16.66.0.5
! Name = decstation-slip.nis.cxn.dec.com
!
|
2204.3 | my bug! | TOOK::CALLANDER | MCC = My Constant Companion | Wed Jan 29 1992 17:06 | 10 |
| oops, I should have put a note here...I got my snmp stuff working
(switched to an ultrix system) and found the problem. It is
definitely a problem in the notification FM (there are multiple
events that start with the string linkup) and I am not correctly
handling distinguishing between them.
More info when I have a fix.
jill
|
2204.4 | success with decnet | NSCRUE::KEANE | U.S. NIS Service Engineering and Delivery | Wed Jan 29 1992 19:09 | 11 |
|
Jill,
Thanks for the info. I'll keep my eye open for the fix. I've had some success
getting specific decnet notifications set up.
Any chance in this version that we will be able to call a notification command
procedure after and alarm or event has cleared the filtering process?
Thanks,
Scott
|
2204.5 | if severity == cleared? | TOOK::CALLANDER | MCC = My Constant Companion | Tue Feb 04 1992 16:34 | 9 |
|
well.....you might be able to set up your action procedure on the alarm
event to look at the severity of the alarm (it should be in the output
data you are passed), and then make it take a seperate process flow if
the severity is cleared. As to events from AM sources it doesn't look
like that will be possible.
jill
|