It all depends on whether you are putting the MLM on the Netview
box, or on another box, and which one is supposed to get the traps.
Either one could be the main trap receptor.
To use MLM for trap filtering, it needs to be the trap receptor. It needs
to
run on the address that the devices send traps to, and listen on port 162.
The usual thing would be to put Netview on a different address, somewhere
nearby. Configure MLM to forward to Netview's 162. These are mostly default
setting when they are on two different boxes. I have actually moved
a Netview to a new address and left an MLM behind to be the trap
receptor to avoid having to change the trap destination on all devices.
This works well for sparing Netview the cpu of excess event processing.
If you install an MLM directly on the Netview box, the install
process assumes that you are using it for other than trap filtering,
like APM use, and automatically disables trap reception on the
MLM. Netview still listens on 162. The devices have their trap
destination set to the address of the Netview & MLM box, and Netview
gets the traps. MLM is not involved at all in trap reception, although
it will send its own traps to Netview port 162. If you are looking at the
V4
redbook or the Sysmon redbook, then the instructions may refer to tasks
that are no longer necessary since later versions simplified the install
process in this respect.
If, however, you want to use the MLM right on the Netview box for
trap filtering purposes, then you have to make the change. You
would enable trap reception in the MLM configuration, and set
forwarding to Netview (same address) on port 165. Configure Netview
(trapd) to listen on port 165. So the traps go first to MLM for filtering
(162),
and those that pass go to Netview. This is unusual, since the MLM
filtering is intended to offload cpu, but it is not incorrect.
I hope I have guessed right about what you are trying to accomplish.
If not, ask again and someone else might be able to answer more clearly.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Boulieris, Arthur" <Arthur.Boulieris@nz.unisys.com>@tkg.com on 08/07/2000
05:29:14 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: [NV-L] MLM port configuration.
Hi all,
I am running netview 5.1.2 for solaris 2.6.
I have a request to add an MLM to our existing setup but it has raised a
couple of questions regarding trap ports.
Firstly can a device (MLM) listen and send on the same port (port 162). I
assume no which is why the redbook talks about reconfiguring the netview
server to listen on port 165 for traps and MLM to forward traps to netview
on 165.
The next question is what do I do about hundreds of devices that forward
traps to netview on port 162 , netview wont be listening on this port? Is
there a work around or will I need to have the trap destination of all
these
devices changed to an MLM?
Thanks Arthur
Arthur Boulieris
Implementation & Support Specialist
Systems Management
<<...>>
Ph: 64-4-462 2787
Mobile: 025 543 529
Arthur.Boulieris@Unisys.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|