Re: Simple Question
kzm@hls.com (Keith McCloghrie) Thu, 18 June 1992 07:22 UTC
Return-Path: <kzm@hls.com>
Received: from mvis1.synoptics.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA21826; Thu, 18 Jun 92 03:22:45 -0400
Received: from lanslide.hls.com by synoptics.com (4.1/SMI-4.1) id AA03590; Thu, 18 Jun 92 00:16:52 PDT
Received: from nms.netman (nms.hls.com) by lanslide.hls.com (4.1/SMI-4.0) id AA02415; Thu, 18 Jun 92 00:16:44 PDT
Received: by nms.netman (4.1/SMI-4.1) id AA24694; Thu, 18 Jun 92 00:08:53 PDT
From: kzm@hls.com
Message-Id: <9206180708.AA24694@nms.netman>
Subject: Re: Simple Question
To: ken@signet.com
Date: Thu, 18 Jun 1992 00:08:52 -0700
Cc: chassismib@cs.utk.edu, hubmib@synoptics.com
In-Reply-To: <9206151933.AA19898@signet.com>; from "Kenneth Virgile" at Jun 15, 92 3:33 pm
Organization: Hughes LAN Systems
X-Mailer: ELM [version 2.2 PL0]
Ken, I think a better analogy would be: a workstation with several interfaces, and you are incoporating into the workstation, a terminal server-type capability for some of the interfaces. To refer to the 2nd SLIP interface on the 2nd terminal server, you would need different MIB views for the different terminal servers. Since you don't want to assign IP addresses to the individual terminal servers, and you presumably want to have a single SNMP agent manage everything, you would need to assign different community names (or party OIDs) to each of them. A standard NMS having the ability to communicate via a proxy agent (e.g., the NMS that I am most familiar with) would then be able to refer to ifOperStatus.2 in the appropriate community (or party). Why do I think this is a better analogy ? Because it is adding additional *devices* (not just *interfaces*), which is what you are doing in your scenario by incorporating multiple repeater devices into an existing bridge device. Thus, to refer to your 2nd port of the 2nd group of the 2nd repeater, the NMS would refer to rptrPortOperStatus.2.2 in the appropriate community (or party). [Also note that that there is no (longer a) separate "View MIB", and implementing the Party MIB is (expected to become) required irrespective of whether or not you add repeater functionality.] Keith. ---------- >From owner-chassismib@CS.UTK.EDU Mon Jun 15 16:00:56 1992 From: ken@signet.com (Kenneth Virgile) Message-Id: <9206151933.AA19898@signet.com> To: chassismib@cs.utk.edu Subject: Simple Question Cc: hubmib@synoptics.com I already have a box with FDDI and Ethernet interfaces. So my box supports the mib-2, fddi, and the dot3 MIBs. Just about any NMS can manage my box, (all the NMS needs is that standard MIB support), and each mib-2 ifEntry corresponds to a real physical interface. Now I try to add a new type of interface, an Ethernet repeater. In order for that interface to be manageable, the NMS must implement a highly complex set of new MIBs!!! It needs the ethernet repeater MIB, but that is just for a single repeater, not for a box that might have several repeaters. The NMS also needs the Chassis MIB, and the Party and View MIBs. And it's still not clear how the NMS can access any of a repeater interface's parameters. I have a simple question for the Chassis and Hub Working Groups. First the scenario: A customer wants a simple plug-and-play bridge, including some ethernet repeater interfaces. The customer knows a little about IP, and wants to assign a single IP address to the bridge (I'm not about to correct the customer - what the customer wants is what the customer gets; otherwise, I can't sell my product). The customer expects to then turn on the bridge, and use a standard NMS (e.g., HP Open View) to manage the bridge. Now the question: What MIB parameter should the NMS access in order to, say, determine if a particular repeater port has been auto-partitioned? [For example purposes, say the repeater port is the 2nd port of the 2nd group of the 2nd repeater interface, which is also the 2nd interface of the bridge.] Please be specific with your response. As an analogy, if the 2nd interface was just dot3 or FDDI, then the NMS would reference ifOperStatus.2 to determine if it was operational. Please post all responses to both Working Groups: chassismib@cs.utk.edu hubmib@synoptics.com Thanks, Ken
- Simple Question Kenneth Virgile
- Re: Simple Question Keith McCloghrie