| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 977.1 | | QUIVER::WALTER | | Tue Jun 01 1993 19:02 | 29 |
| Not sure if I understand your questions, but I'll take a shot at it.
>> 1. Using SNMP SetRequest, what part of MIB info. is set(changed) ?
You must specify in the SNMP Set what MIB object you want to change,
and it must be a writeable object. Further, not all products support
all MIB objects. In the case of the DECbridge Series bridges, they
support the following MIBs:
Mib-2
Bridge
FDDI
DEC
>> 2. Is there any difference, in MIB, to be set by SNMP SetRequest
>> and RBMS ?
In general, SNMP can manage all the bridge parameters that are known to
RBMS, and some that RBMS doesn't know about. RBMS is no longer
supported, so new features can only be accessed through SNMP (for
example, the IPX switch "esysIPXSwitch"). There are just two
significant exceptions to this rule that I know of: you can set the
bridge IP address with RBMS but not SNMP, and you can read the
diagnostic block only with RBMS.
So, in order to manage all bridge features, you must use SNMP.
Dave
|
| 977.2 | Which MIBs are settable ? | TKOV51::AOKI_H | Hiromitsu AOKI, Network Team/SE, Japan DEC | Tue Jun 01 1993 21:47 | 40 |
| *Thank you very much for quick responce.
> >> 1. Using SNMP SetRequest, what part of MIB info. is set(changed) ?
> You must specify in the SNMP Set what MIB object you want to change,
> and it must be a writeable object. Further, not all products support
> all MIB objects. In the case of the DECbridge Series bridges, they
> support the following MIBs:
> Mib-2
> Bridge
> FDDI
> DEC
> >> 2. Is there any difference, in MIB, to be set by SNMP SetRequest
> >> and RBMS ?
> In general, SNMP can manage all the bridge parameters that are known to
> RBMS, and some that RBMS doesn't know about. RBMS is no longer
> supported, so new features can only be accessed through SNMP (for
*What does it mean that RBMS is no longer supported ? Phased out ?
> example, the IPX switch "esysIPXSwitch"). There are just two
> significant exceptions to this rule that I know of: you can set the
> bridge IP address with RBMS but not SNMP, and you can read the
> diagnostic block only with RBMS.
> So, in order to manage all bridge features, you must use SNMP.
From those info., I could get concepts of difference between SNMP & RBMS.
Finally I'd like to know the answer of original question:
Which MIBs are able to be set(changeable) by SNMP, by RBMS,
respectively ?
Thank you very much in advance.
---Hiromitsu
|
| 977.3 | | QUIVER::WALTER | | Wed Jun 02 1993 08:47 | 48 |
| >> *What does it mean that RBMS is no longer supported ? Phased out ?
RBMS is a protocol originally designed by DEC to manage their network
products. I believe that at the time it was developed, there was no
other widely accepted protocol. Since then, SNMP has become the defacto
standard (in the US, anyway), and we must support SNMP for our products
to be successful in the marketplace. We don't have sufficient resources
to continually update RBMS code, so new features and new products
simply aren't "known" to the old RBMS software. RBMS management
stations can still be used on the older products, but new features in
those products can't be accessed, and the latest network products will
not respond to RBMS requests at all.
>> Which MIBs are able to be set(changeable) by SNMP, by RBMS,
>> respectively ?
Well, I answered this question best I knew how. I think you need to do some
reading on SNMP, to get a better understanding of the concept of a
"MIB". A MIB is a database abstraction used by SNMP to access data and
functions within a managed object, such as a bridge. RBMS uses a
different abstraction to get to the information, but ultimately they
both access the same variables or functions. But you can't say that
RBMS can set a MIB object because RBMS knows nothing about MIBs. The
two protocols have different methods to get at the same information.
The SNMP protocol can access ANY object within a MIB, because that's
what SNMP is designed to do. The more important question is, does the
managed device SUPPORT the MIB object as it is defined in the standard?
That all depends on the device. Concentrators don't support the Bridge
MIB because there are no bridge functions within a Concentrator.
I guess I don't know how else to explain this (anyone care to help?).
If you want to do some reading, try "The Simple Book" by Marshall Rose.
Or, you can refer to the relevant RFCs:
RFC 1155 - Structure and Identification of Management Information
for TCP/IP-based Internets
RFC 1157 - A Simple Network Management Protocol (SNMP)
RFC 1213 - Management Information Base for Network Management of
TCP/IP-based Internets: MIB-II
Hope that helped.
Dave
|