T.R | Title | User | Personal Name | Date | Lines |
---|
4316.1 | | 2582::YAHEY::BOSE | | Tue Dec 29 1992 15:32 | 52 |
|
Renato,
Notification of enterprise specific events seem to work
correctly on my system (X1.3.5).
MCC> notify domain bose entity = (snmp * chipcom), event = (any event)
%MCC-S-NOTIFSTART, Notify request 2 started
%%%%%%%%%%%%%% Event, 29-DEC-1992 14:38:35 %%%%%%%%%%%%%% [2]
Domain: MOLAR_NS:.bose Severity: Indeterminate
Notification Entity: SNMP MOLAR_NS:.chipcom chipcom
Event Source: SNMP MOLAR_NS:.chipcom chipcom
Event: chipFatal
A chipFatal trap was received:
enterprise = "1.3.6.1.4.1.49"
agent-addr = 16.31.112.23
generic-trap = enterpriseSpecific
specific-trap = 8
time-stamp = 698
>> MCC>getevent snmp * chipcom chipslotUp
>> getevent snmp * chipcom chipslotUp
>> SNMP LOCAL_NS:.snmp.etoile1 chipcom
>> AT 28-DEC-1992 15:16:52 CONFIGURATION EVENTS
>> Received event had more object ids than were defined in the dictionary:
>> Event: chipSlotUp
>> A chipSlotUp trap was received:
>> enterprise = "1.3.6.1.4.1.49"
>> agent-addr = 16.188.48.108
>> generic-trap = enterpriseSpecific
>> specific-trap = 3
>> time-stamp = 1091485
>> onlineModSlotIndex = 4
>>
>> In this last command, expected onlineModType variable is NOT displayed...
This is a bug in the SNMP AM and a QAR (#69 in MCC013_EXT) has been
filed against the SNMP AM.
>> 3) is it possible to ckeck what is really returned with MCC_TCPIP_MQ
>> utility ?
Unfortunately, no.
Rahul.
|
4316.2 | maybe an MS file mismatch | GOSTE::CALLANDER | | Thu Dec 31 1992 15:21 | 3 |
| rahul, could you post a copy of the MS you used to specify the trap
in the dictinoary?
|
4316.3 | OK for QAR... What about MCC 1.3.x last kit ? | ZTOIS1::VISTA | Renato VISTA, SIS Strasbourg, France | Mon Jan 04 1993 03:34 | 14 |
|
Hi Rahul,
Thank you for your reply... and a Happy New Year 1993 !
Is the MCC X1.3.5 an available Field Test version ? Do you think that
the QAR about SNMP will be included in an available Field Test new
version ? I would need to have a MCC X1.3.* version running SNMP
correctly for a planned customer demonstration...
Regards,
Renato
|
4316.4 | X is for development group only | TOOK::MINTZ | Erik Mintz | Mon Jan 04 1993 07:30 | 9 |
| No, X kits are internal development kits only.
The next available kit will be the field test update, T1.3.x
If you have a problem that you feel must be fixed, please enter a QAR
as soon as possible (the deadline is fast approaching), and make
sure the importance of the problem is described in the text.
That will help us prioritize the work in relation to other reported problems.
-- Erik
|
4316.5 | | 2582::YAHEY::BOSE | | Mon Jan 04 1993 12:39 | 39 |
|
Happy New Year, Renato.
QAR #69 in MCC013_INT has been addressed and the fix will be in
the field test update kit.
RE .2
>> rahul, could you post a copy of the MS you used to specify the trap
>> in the dictinoary?
Here's the event definition in the MS file :
EVENT chipFatal = 8 :
DISPLAY = TRUE,
SYMBOL = EN49_Event_8,
TEXT = "A chipFatal trap was received:",
CATEGORIES = (CONFIGURATION),
ARGUMENT enterprise = 01 : Latin1String
DISPLAY = TRUE,
SYMBOL = SNMP_EV_GEN_ENTERPRISE
END ARGUMENT enterprise;
ARGUMENT agent-addr = 02 : IpAddress
DISPLAY = TRUE,
SYMBOL = SNMP_EV_GEN_AGENT_ADDR
END ARGUMENT agent-addr;
ARGUMENT generic-trap = 03 : GenericTrap_enm
DISPLAY = TRUE,
SYMBOL = SNMP_EV_GEN_GENERIC_TRAP
END ARGUMENT generic-trap;
ARGUMENT specific-trap = 04 : Integer32
DISPLAY = TRUE,
SYMBOL = SNMP_EV_GEN_SPECIFIC_TRAP
END ARGUMENT specific-trap;
ARGUMENT time-stamp = 05 : MIBTimeTicks
DISPLAY = TRUE,
SYMBOL = SNMP_EV_GEN_TIME_STAMP
END ARGUMENT time-stamp;
END EVENT chipFatal;
|