This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
> Hi everyone, let me just warn that I am a novice with Netview ...
> I am running NV 6.0.1 for NT and when I force a DEC RouteAbout Router link
> to go up and down I get the following event in the event Browser:
>
> Trap Name: Link Up
> SOURCE: netmon-related
> Enterprise: AEASA
> Trap:
> Link Up
> ...
> Details:
>
> DEFAULT FMT: enterprises.dec.ema.emaSystem.brouters.10.1
> (1.3.6.1.4.1.36.2.15.11.10.1) generic:3 specific:0 args(1):
> [1] mgmt.mib-2.interfaces.ifTable.ifEntry.ifIndex.3 (Integer): 3
>
> What I want is to forward those particular events to TEC (I have already
> read the book on Adapters ..)
> I am not able to find any specific MIB for those devices so I created a
> custom Enterprise with # 1.3.6.1.4.1.36.2.15.11.10.1 (AEASA)
> What I don't seem to understand is that the argument of the event comes
> for a branch other than 1.3.6.1.4.1.36.2.15.11: mgmt.mib-2 ... along the
> MIB tree, so I guess I won't able to add the right entries in the cds
> file.
> Is that right ? Am I missing something here ? Do I need an
> enterprise-specific MIB ? By the way, is there a document on interpreting
> the adapter logfile ?
>
> Any help will be greatly appreciated,
>
> Thanks in advance,
>
>
> Ofer Grauer
>
>
Hi everyone, let me just warn that I am a novice with Netview ...
I am running NV 6.0.1 for NT and when I force a DEC RouteAbout Router link to go up and down I get the following event in the event Browser:
Trap Name: Link Up
SOURCE: netmon-related
Enterprise: AEASA
Trap:
Link Up
...
Details:
DEFAULT FMT: enterprises.dec.ema.emaSystem.brouters.10.1 (1.3.6.1.4.1.36.2.15.11.10.1) generic:3 specific:0 args(1):
[1] mgmt.mib-2.interfaces.ifTable.ifEntry.ifIndex.3 (Integer): 3
What I want is to forward those particular events to TEC (I have already read the book on Adapters ..)
I am not able to find any specific MIB for those devices so I created a custom Enterprise with # 1.3.6.1.4.1.36.2.15.11.10.1 (AEASA)
What I don't seem to understand is that the argument of the event comes for a branch other than 1.3.6.1.4.1.36.2.15.11: mgmt.mib-2 ... along the MIB tree, so I guess I won't able to add the right entries in the cds file.
Is that right ? Am I missing something here ? Do I need an enterprise-specific MIB ? By the way, is there a document on interpreting the adapter logfile ?
Any help will be greatly appreciated,
Thanks in advance,
Ofer Grauer
|