| my $0.02 worth...
I have worked with the LANMANAGER agent both on OS2, Alpha NT and Intel
NT.
OS2 works fine, can get most of the defied MIB variables as per
LANMANAGER, only thing is that there is a sort of bit alignment problem
which results in a non printable character as the first character when
you show certain variables.
All standard traps worked fine, we also got the "login Security
Violation" trap to work by defining a valid user name but a garbage
password when doing a remote "use" of a file system from a client to the
server. The following is the rule we used (CERIUS is the domain etc..)
CREATE DOMAIN CERIUS RULE pw_access_violation -
EXPRESSION = (OCCURS( snmp * LANMANAGER accessViolationsAlert)),-
CATEGORY = "Security" ,-
DESCRIPTION = "Network logon access violation" ,-
ALARM FIRED PROCEDURE = MCC$com:cerius_acc_viol_alarm_proc.com ,-
ALARM EXCEPTION PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM ,-
ALARM FIRED PARAMETER = "mercur::mcc" ,-
SEVERITY = Critical
the notifications we used for the domain....
Notify Domain CERIUS Entity List = (snmp *), Events = (any event)
NOW, the story is a little different if you have Alphas. There appears
to be a problem with the variable data sent back from the NT agent some
are ok most you just see garbage back. I reported the problem to Alpha
NT group they said it is a Microsoft NT problem... sorry to say I
basically gave up because of the time it was taking to get to Microsoft
etc..
have fun, Amrit
|