Conference netcad::hub_mgnt

117.0. "Launching HUBwatch from MCC V1.3" by EMDS::SEAVER (LENAC Net Mgnt Mktg 223-4573) Wed Jan 06 1993 00:49

    From:	ZPOVC::RAMARAJ "M Ramaraj, Singapore, 290-7711  05-Jan-1993 2326"  5-JAN-1993 10:23:30.37
To:	EMDS::SEAVER
CC:	QUIVER::PARK,RAMARAJ
Subj:	MCC V1.3 launch file for HW

Hi Bill, Jae,

Just tried this launch definition file for HUBwatch with MCC T1.3.
Works ok.  I'm not sure if anyone else has done this.  See if you would
like to put in the HUB_mgt notes file.

Register a hub or standalone module  using the SNMP proxy agent method.
Choose a hub or standalone module and invoke hubwatch.  I tried this
with a hub and standalone terminal server.

This works only for single entities chosen.  For multiple entities, then
a script file has to be written and a datafile created.  A little troublesome
but can be done.

The read community and write community can be optional.  This example uses
the read community as optional.
 
The launch definition file can be put in /usr/mcc/mcc_system
MCC will pick up launch definition from there.

This same file can be used for the VMS too.  The Binary: need to be changed.
Hopefully the VMS version will have a NMS_DIR equivalent logical to point
to hubwatch directory.
The definition file will be in MCC_SYSTEM:

The earlier launch file used for V1.2 cannot be used for this.  The datafile
created is different for V1.3.

Raj
-------------------------------------------------------
#
#	HUBwatch Launch Application Interface Definition
#                          File
#
#
DEL_KEY:*
Menu:  Applications
  Button:       HUBwatch
    Binary:     $NMS_DIR/bin/DH90_main
    APPLIES_TO: snmp
    ARGUMENT:   -l -x <snmp.!.proxy agent address>
    ARGUMENT:   *-c <SNMPrdCOMMUNITY>*
    Env_type:   WINDOW
    Term_title: HUBWATCH
    Icon_label: HUBWATCH
Endmenu:
-------------------------------------