nv-l

NetView for AIX Service Point is obsolete in some respects

1999-11-21 15:01:18
Subject: NetView for AIX Service Point is obsolete in some respects
From: James Shanks <James_Shanks AT TIVOLI DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Sun, 21 Nov 1999 15:01:18 -0500
James Shanks
Tivoli (NetView for UNIX) L3 Support

---------------------- Forwarded by James Shanks/Tivoli Systems on 11/21/99
03:00 PM ---------------------------


"Bill Evans" <wvevans AT attglobal DOT net> on 11/21/99 01:18:24 PM

To:   "Gord Michaels" <gord_michaels AT HOTMAIL DOT COM>
cc:   James Shanks/Tivoli [email protected] Systems
Subject:  NetView for AIX Service Point is obsolete in some respects




Gord,

As the original designer for AIX Service Point (about ten years ago in a
previous incarnation as an IBM employee) , I've noticed that NetView for OS/390
added a couple new functions last April which reduce the need for my baby.  The
new function get rid of the need for SNA Services to interconnect 390 and AIX in
order to forward events and topology.

The NV390 Event Adapter Service now contains a Trap-to-Alert conversion which
will listen on the IP internet for traps (default to port 162).  This eliminates
the need for TRALERTD daemon of the service point.

NetView for OS/390 MultiSystem Manager for IP (runs on the AIX system) in
conjunction with NetView for Unix will forward traps and topology to a
designated target, presumably NV390 and MSM, via IP.  Prior to April 1999 it
needed the Service Point for AIX for the connection.  Since MSM IP can't share
Port 162 with the SNMP service you also have a datagram redirecter supplied with
NV390.  (Otherwise, if you don't want topology just forward the traps from NVAIX
via SNMP.)

The MSM solution also allows commands be executed at the NetView for Unix
system.  I'm implementing all this at the moment at a client location so my
knowledge is still academic.  Documentation is in the README directory on the
CDROM shipped with NetView for OS/390 V1R2 LK3T-9614-02.  Executables are
elsewhere on that disk.

Sic transit gloria mundi.  RIP Service Point.

Bill Evans  --  Consultant and Trainer for 2ndWave (www.2nd-wave.com)
"Managing the enterprise and beyond"
reply-to: Bill.Evans AT 2nd-wave DOT com
Phone: 919-696-7513 FAX: 919-847-4753
Send short text messages to 9196967513 AT messaging.sprintpcs DOT com
Gord, 

As the original designer for AIX Service Point (about ten years ago in a previous incarnation as an IBM employee) , I've noticed that NetView for OS/390 added a couple new functions last April which reduce the need for my baby.  The new function get rid of the need for SNA Services to interconnect 390 and AIX in order to forward events and topology.

The NV390 Event Adapter Service now contains a Trap-to-Alert conversion which will listen on the IP internet for traps (default to port 162).  This eliminates the need for TRALERTD daemon of the service point.

NetView for OS/390 MultiSystem Manager for IP (runs on the AIX system) in conjunction with NetView for Unix will forward traps and topology to a designated target, presumably NV390 and MSM, via IP.  Prior to April 1999 it needed the Service Point for AIX for the connection.  Since MSM IP can't share Port 162 with the SNMP service you also have a datagram redirecter supplied with NV390.  (Otherwise, if you don't want topology just forward the traps from NVAIX via SNMP.)

The MSM solution also allows commands be executed at the NetView for Unix system.  I'm implementing all this at the moment at a client location so my
knowledge is still academic.  Documentation is in the README directory on the CDROM shipped with NetView for OS/390 V1R2 LK3T-9614-02.  Executables are elsewhere on that disk.

Sic transit gloria mundi.  RIP Service Point.

Bill Evans  --  Consultant and Trainer for 2ndWave (www.2nd-wave.com)
"Managing the enterprise and beyond"
reply-to: Bill.Evans AT 2nd-wave DOT com
Phone: 919-696-7513 FAX: 919-847-4753
Send short text messages to 9196967513 AT messaging.sprintpcs DOT com
<Prev in Thread] Current Thread [Next in Thread>