| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5362.1 | What's adequate? | VCSESU::WADE | Bill Wade, VAXc Systems & Support Eng | Tue Jul 20 1993 12:55 | 8 |
| It depends on what you define as "adequate".
The Polycenter Framework contains the SNMP AM which is required to
communicate with the GIGAswitch. I know that I'd want the Notification
Services (either separately or in the Network Manager 400 package) for
alarming.
|
| 5362.2 | POLYCENTER NM 200/400 are both adequate | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Wed Aug 18 1993 01:16 | 13 |
| Any network manager that speaks SNMP will allow you to manage the
Gigaswitch. The examples in the release notes and "early ship"
documentation are for DECmcc with some MSU.
I have one customer using HP OpenView to manage it quite nicely,
including alarms, etc.
Most of the examples for DECmcc involve loading of firmware.
See note 5304 for some example DECmcc expressions for monitoring
selected MIB objects.
-Dan
|
| 5362.3 | Not simple from DECmcc | OSLACT::BJORN | Bj�rn Olav Haugom | Wed Aug 18 1993 05:34 | 19 |
| The first Gigaswitch in Norway were installed and setup using SunNet Manager.
The MIB Extensions were loaded into the system in seconds!!!! And up on the
screen in another few seconds. SunNet Manager was used further on to load the
firmware update into the Gigaswitch with simple point and click operations. The
user was unexperienced with SunNet Manager.
Before this they installed POLYCENTER Network Manager 200 V1.3 and loaded the
MIB Extensions, waiting for 6 hours to complete!!!! And after it was loaded the
documented MCC-commands to use for loading the firmware update into the
Gigaswitch failed with "Function SET is not support by entity EMA".
The problem we see is that things are not that simple as we want them to be,
using DECmcc. What the reason for the problems are, can be many, at least the
description of the commands to execute must have been wrong.
Any comments!
Bj�rn Olav
|