Telecom/1996-04-telecom-walnutcreek.iso/reports/enterprise.mgt.summit

Internet Message Format | 1994-10-12 | 14KB

Received: from delta.eecs.nwu.edu by MINTAKA.LCS.MIT.EDU id aa23569;
          13 Oct 94 0:16 EDT
Received: by delta.eecs.nwu.edu (4.1/SMI-4.0-proxy)
    id AA06386; Mon, 3 Oct 94 12:38:58 CDT
Return-Path: <telecom>
Received: by delta.eecs.nwu.edu (4.1/SMI-4.0-proxy)
    id AA06378; Mon, 3 Oct 94 12:38:55 CDT
Date: Mon, 3 Oct 94 12:38:55 CDT
From: [e-mail] (TELECOM Digest (Patrick Townson))
Message-Id: <[e-mail]>
To: telecom
Subject: Enterprise Management Summit '94: Vendors Prove Themselves Worthy


A most unusual presentation will be given in the Santa Clara (CA) Convention
Center the week of November 14-18. Entitled 'Enterprise Management Summit '94,
this will be an opportunity for vendors to either prove that they know what
they are talking about ... or else!

Since the first mention of this in TELECOM Digest awhile back, there
have been numerous inquiries made and this followup article will describe
the presentation in great detail, and how to participate.  I won't begin
to print all the letters of inquiry received, but shall use this single
letter I received yesterday from Melissa Brieker as an example:

 > From: [e-mail] (Melissa Brieker)
 > Subject: Enterprise Summit - info?
 > Date: 2 Oct 1994 02:00:30 GMT

 > Does anyone have info on a show/conference called the Enterprise
 > Summit, Management Summit, not sure the exact name. Heard they're
 > having some kind of vendor shootout or commpetition where network
 > mgmt products are demo'd. They're supposedly building a very complex
 > network -- mainframes, minis, lans, applications, the works. Is this
 > possible? If it is, I've never heard of it before. Any info?

Yes Melissa (and others), it is possible and it will happen. It will
be an opportunity to -- if you please -- put up or shut up. Here are
the details available to me as of today.

 From: [e-mail] (Summit '94)
 Subject: Enterprise Management Summit '94 - Theater Scenarios
 Date: 3 Oct 1994 04:55:39 GMT
 Organization: Netcom

Note: Because of the high volume of requests for information about the
theater presentations at Summit '94, we are posting these "scenario"
descriptions. Any suggestions about how to refine them is appreciated.
Information about Summit '94 can be requested at 1-800-340-2111 or
415-512-0801. Fax: [phone]. Email: [e-mail] or
[e-mail].

                   ----------------------

               Enterprise Management Summit '94
               - Enterprise Management Center -

                       Purpose/Function
                     =====================

The Enterprise Management Center will be built in the theater of the
Santa Clara Convention Center during the week of November 14-18, 1994.
(The Theater track will run in addition to the exhibit floor). Vendors
participating in the Theater are Bull, Computer Associates, DEC, HP,
IBM, and NetLabs. Each vendor has 90 minutes to respond to the
scenarios listed below which are constructed around a user's typical
day. It is intended that these scenarios will require each vendor to
present all aspects of their management products (thus minimizing demo
hype) and put the emphasis on solutions.

                      Overview of Theater Scenarios
                     ===============================

Introductions                                      5 minutes
Part I Asset Management                           10 minutes
Part II - Fault Management
     ("A typical Day At the Help Desk")           45 minutes
Part III - Administration                         15 minutes
Summary                                           15 minutes


                       Introductions  (5 minutes)
                     ==============================

To begin the presentation, the vendor will take the stage along with a
narrator (provided by Summit '94). The narrator will announce each
section of the presentation and each scenario by number. The vendor
will introduce speakers and personnel operating the software and will
then highlight architectural aspects of their product(s) including
"partnering" products (e.g.,trouble ticketing).

                Part I - Asset Management (10 minutes)
              ==========================================

Scenario 1:    Auto-Topology

Vendors will be expected to discover only the Theater network.  (The
Theater network will be connected to the network on the exhibit floor
via a router.) This process will be started at the beginning of this
scenario. If it requires more than ten minutes, it will become a
background task and can be revisited at the end of the presentation.

Theater Networks:

     TCP/IP - Theater/Showcase (at least 3 sub-networks with
          approx. 50-100 devices)
     SNA - Theater only
     DECnet Phase IV - Theater only
     Novell - Theater only

Theater Nodes:

     RS6000 with AIX
     HP 9000 700 Series with HP-UX
     Sun with Sun O/S, Solaris
     X-Windows terminal
     PS/2 with OS/2
     486 Processor with DOS/Windows
     Processor with Windows NT and Hermes agent
     Macintosh

Scenario 2:    Inventory

A new piece of equipment is installed and needs to be recorded in
the inventory. Information to be recorded includes:

     Equipment information (Example)
          type (e.g., router)      Router
          manufacturer             Wellfleet
          model                    BCN
          serial number            43086-2
          owner                    PPSD
          administrator            Dave Anderson

     Location
          Physical                 Room 109, 3323 Central Avenue,
                                   San Jose, CA
          Network address          192.225.32.250

The above data for each of the fields are only provided as examples.
Each vendor may choose the exact information which they enter and may
define additional details.

               Part II - Fault Management (45 minutes)
             ===========================================

Scenario 3:    Network Analysis    8:00 A.M.

A user calls to complain that response time is slow.  The cause is
packet congestion. The congestion will be induced with a hardware
device (a probe).

     * Determine that the cause is traffic congestion.
     * Resolve the problem.
     * Notify the user of the resolution.


Scenario 4:    Multiple Alarms     9:00 A.M.

There is a flood of alarms (possibly 20-30) when the connection
to segment A of the showcase network is lost.

     * Isolate the root problem (i.e., the loss of connectivity
          to the segment).
     * Resolve the problem by dispatching service personnel to
          "repair" the cable.
     * Clear any outstanding alarms associated with the problem.

The problem will be generated by activating a software filter in the
router connecting the theater to the Showcase.  In addition, a script
running one of the systems, will send out the series of traps. Note:
Detailed information about the traps to be produced will be supplied
after all of the equipment information is obtained from each of the
participants.

Scenario 5:    Spool Space    10:00 A.M.

The file system on one of the systems in the Theater fills up.
Therefore there is not any spool space available. The vendor will be
allowed to select the environment where the problem occurs. Summit '94
will present the scenario on the "Manufacturing System" in the
Theater.  If a vendor wishes to deal with this scenario on a different
system they will be responsible for providing the system and producing
the scenario on it.

Scenario 6:    Data Base 11:00 A.M.

There is a problem (too much fragmentation) with an Oracle data base.
Each vendor will be assigned a specific data base (file) which they
will be responsible for fixing.  The files will be identical.
However, each vendor will be assigned a unique data base to work with
in order to avoid the need to reload data bases between sessions.  The
scenario will be presented on the "Accounting System."

Scenario 7:    DECnet/SNA     12:00 P.M.

The vendor should choose one of the two following network
problems:

(a)  A problem occurs in a DECnet.

(b)  A problem occurs in an SNA network.  Resolution requires an
     IML command to be issued to a remote controller.

Scenario 8:    Work Group Support  1:00 P.M.

User, on a Novell network, calls to report that their job is not
printing. The cause of the problem will be that the printer is out of
paper. It will be necessary to determine that the lack of paper is the
cause of the problem and arrange for someone to load more paper.

Scenario 9:    Trouble Tracking    3:00 P.M.

An application fails and issues a message (ASCII text) indicating its
status.  Based upon that message (alarm) it will be necessary for the
management system to notify the management personnel of the problem.
The failure of this application is of only limited impact.  Therefore,
it will be classified as a minor alarm.  It is immediately diagnosed
as a problem requiring the dispatch of service personnel on site. The
call is placed to dispatch service personnel.  However, the problem
has occurred just before shift change for the service personnel and is
"lost" at turnover.  They fail to work the ticket.  At 10:00 P.M., the
trouble is still unresolved.  The problem now should be escalated to a
higher level of severity and Help Desk personnel notified that it is
still outstanding --

     * Open a trouble ticket
     * Refer the problem to the service personnel
     * Escalate problem
     * Notify Help Desk of escalation
     * Contact Service Personnel
     * Problem is resolved by service personnel and they clear
          the trouble ticket.

The name of the failing application will be "geninvoices". It will be
running on the "Sales System." It will be caused to fail by finding an
illegal sales account number. When it fails it will issue the
following message "geninv:illegal account name QXZ".  The message will
be written to a log on the "Sales System" with the name of
/VAR/LOG/INV.LOG. In addition, the message will be written to the
console.

               Part III - Administration (15 minutes)
              ========================================

Scenario 10:   Security Administration  4:00 P.M.

It is necessary to authorize a new user to access multiple systems in
the Theater.  This user will be added to as many systems as the vendor
wishes. User name will be the vendor's choice. The security to be used
on UNIX systems is standard UNIX (i.e., no supplementary security
software will be provided, e.g., C2). Vendors wishing to add a user to
a non-UNIX system will be responsible for providing and installing the
necessary security system(s) on those other systems.

User name, systems to which to add the user and the access level to be
granted will be the vendor's choice.  However, in order to avoid
duplication, vendors must provide the names which they will use in
their session to Summit '94 by 10/1.  Names will be reserved on a
first-come, first-served basis.

Scenario 11:   Production     7:00 P.M.

Schedule multiple jobs to run in the Theater.  Jobs should be
scheduled to run on more than one type of system. The schedule should
include dependencies between jobs. The number of systems on which jobs
are scheduled to run will be the vendor's decision.

Some of the jobs scheduled should be performing backups. The backups
should include multiple environments.  Some of the possible options
which vendors may wish to demonstrate in this scenario include
escalating the priority of a job waiting to execute or showing
dependencies between jobs running on different systems. Jobs will be
provided for the UNIX environments only.  Vendors wishing to run jobs
in other environments should be prepared to setup and provide those
jobs.  Vendors may also provide additional jobs for the UNIX systems.

Vendors may select the specific jobs to schedule and the specific
sequence in which they run.  However, they must advise us by October
26 of the jobs they intend to schedule and the sequence in which they
will run them.

Scenario 12:   Configuration  2:00 A.M.

It is necessary to load a new configuration into a router.  This
should be setup to occur automatically. Wellfleet Router, configuration
should be done using an SNMP SET command.  A copy of the new configuration
will be provided to each vendor.

Scenario 13:   Software Distribution    3:00 A.M.

It is necessary to download software to systems in multiple
environments.  Vendors may determine the exact number of environments
and which environments to which they distribute the software. It will
not be necessary to execute, link or compile the software once it is
distributed. Software to be distributed will be provided for each of
the UNIX systems.

               Part IV - Wrap-Up (15 minutes)
              ================================

Scenario 14 :  What Makes Your Software Different?

This is the chance for each vendor to tell the audience what features
differentiate it from the competition.  They can design their own
scenario and solve it during this time.

                       === end ====

                    ---------------------------

[TELECOM Digest Editor's Note: And there you have the details for
Enterprise Management Summit '94.  It ought to be a very interesting
day (and evening, and late night) to say the least. If you are in that
part of California or can spend some time out there, you might want to
reserve that time in the middle of November to check it out for yourself.
It will be at the Santa Clara Convention Center, November 14-18.

Information about Summit '94 can be requested at 1-800-340-2111 or
415-512-0801. Fax: [phone].
Email: [e-mail] or [e-mail].  Please contact them
directly -- *not me* -- for further details.  PAT]