📄 rfc3295.txt
字号:
RFC 3295 GSMP MIB June 2002
3.4.4 GSMP General group
The GSMP session table provides a way to monitor and maintain GSMP
sessions.
The session is defined by a Switch Controller Entity and Switch
Entity pair.
3.4.5 The GSMP Notifications Group
The GSMP Notification Group defines notifications for GSMP entities.
These notifications provide a mechanism for a GSMP device to inform
the management station of status changes. Also a notification is
defined for each type of GSMP events.
The group of notifications consists of the following notifications:
- gsmpSessionDown
This notification is generated when a session is terminating and also
reports the final accounting statistics of the session.
- gsmpSessionUp
This notification is generated when a new session is established.
- gsmpSendFailureInd
This notification is generated when a message with a failure
indication was sent. This means that this notification identifies a
change to the gsmpSessionStatFailureInds object in a row of the
gsmpSessionTable.
- gsmpReceivedFailureInd
This notification is generated when a message with a failure
indication received. This means that this notification identifies a
change to the gsmpSessionStatReceivedFailures object in a row of the
gsmpSessionTable.
- gsmpPortUpEvent
This notification is generated when a Port Up Event is either
received or sent.
Sjostrand, et. al. Standards Track [Page 7]
RFC 3295 GSMP MIB June 2002
- gsmpPortDownEvent
This notification is generated when a Port Down Event is either
received or sent.
- gsmpInvalidLabelEvent
This notification is generated when an Invalid Label Event is either
received or sent.
- gsmpNewPortEvent
This notification is generated when New Port Event either is received
or sent.
- gsmpDeadPortEvent
This notification is generated when a Dead Port Event is either
received or sent.
- gsmpAdjacencyUpdateEvent
This notification is generated when an Adjacency Update Event is
either received or sent.
To disable or enable the sending of each notification, the bits in
the bitmap are set to 0 or 1 in the Notification mapping objects in
the Controller Entitiy or Switch Entity tables.
The GSMP notification map capability should not be seen as a
duplication of the filter mechanism in the snmp notification
originator application [RFC2573], but as a compliment, to configure
the relation between GSMP events and the SNMP notifications already
in the GSMP agent. SNMP notifications and GSMP events operate
sometimes on a different timescale, and it may in some applications
be devastating for a SNMP application to receive events for each GSMP
events. E.g. the invalid label event in a ATM switch scenario may
cause mass SNMP notification flooding if mapped to a SNMP
notification.
3.5 Textual Conventions
The datatypes GsmpNameType, GsmpLabelType, GsmpVersion,
GsmpPartitionType, and GsmpPartitionIdType are used as textual
conventions in this document. These textual conventions are used for
the convenience of humans reading the MIB. Objects defined using
these conventions are always encoded by means of the rules that
define their primitive type. However, the textual conventions have
Sjostrand, et. al. Standards Track [Page 8]
RFC 3295 GSMP MIB June 2002
special semantics associated with them. Hence, no changes to the SMI
or the SNMP are necessary to accommodate these textual conventions
which are adopted merely for the convenience of readers.
4. GSMP MIB Definitions
GSMP-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
Unsigned32, Integer32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
RowStatus, TruthValue, TimeStamp,
StorageType, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB -- [RFC2021]
InterfaceIndex
FROM IF-MIB -- [RFC2863]
AtmVcIdentifier, AtmVpIdentifier
FROM ATM-TC-MIB -- [RFC2514]
InetAddressType, InetAddress, InetPortNumber
FROM INET-ADDRESS-MIB ; -- [RFC3291]
gsmpMIB MODULE-IDENTITY
LAST-UPDATED "200205310000Z" -- May 31, 2002
ORGANIZATION "General Switch Management Protocol (gsmp)
Working Group, IETF"
CONTACT-INFO
"WG Charter:
http://www.ietf.org/html.charters/gsmp-charter.html
WG-email: gsmp@ietf.org
Subscribe: gsmp-request@ietf.org
Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/gsmp/
WG Chair: Avri Doria
Email: avri@acm.org
WG Chair: Kenneth Sundell
Email: ksundell@nortelnetworks.com
Editor: Hans Sjostrand
Email: hans@ipunplugged.com
Sjostrand, et. al. Standards Track [Page 9]
RFC 3295 GSMP MIB June 2002
Editor: Joachim Buerkle
Email: joachim.buerkle@nortelnetworks.com
Editor: Balaji Srinivasan
Email: balaji@cplane.com"
DESCRIPTION
"This MIB contains managed object definitions for the
General Switch Management Protocol, GSMP, version 3"
REVISION "200205310000Z"
DESCRIPTION "Initial Version, published as RFC 3295"
::= { mib-2 98 }
gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 0 }
gsmpObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 }
gsmpNotificationsObjects OBJECT IDENTIFIER ::= { gsmpMIB 2 }
gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 3 }
--**************************************************************
-- GSMP Textual Conventions
--**************************************************************
GsmpNameType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Name is a 48-bit quantity.
A 48-bit IEEE 802 MAC address, if
available, may be used."
SYNTAX OCTET STRING (SIZE(6))
GsmpPartitionType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Defining if partitions are used and how the partition id
is negotiated. "
SYNTAX INTEGER {
noPartition(1),
fixedPartitionRequest(2),
fixedPartitionAssigned(3)
}
GsmpPartitionIdType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A 8-bit quantity. The format of the Partition ID is not
defined in GSMP. If desired, the Partition ID can be
divided into multiple sub-identifiers within a single
Sjostrand, et. al. Standards Track [Page 10]
RFC 3295 GSMP MIB June 2002
partition. For example: the Partition ID could be
subdivided into a 6-bit partition number and a 2-bit
sub-identifier which would allow a switch to support 64
partitions with 4 available IDs per partition."
SYNTAX OCTET STRING (SIZE(1))
GsmpVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The version numbers defined for the GSMP protocol.
The version numbers used are defined in the
specifications of the respective protocol,
1 - GSMPv1.1 [RFC1987]
2 - GSMPv2.0 [RFC2397]
3 - GSMPv3 [RFC3292]
Other numbers may be defined for other versions
of the GSMP protocol."
SYNTAX Unsigned32
GsmpLabelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The label is structured as a TLV, a tuple, consisting of
a Type, a Length, and a Value. The structure is defined
in [RFC 3292]. The label TLV is encoded as a 2 octet type
field, followed by a 2 octet Length field, followed by a
variable length Value field.
Additionally, a label field can be composed of many stacked
labels that together constitute the label."
SYNTAX OCTET STRING
--**************************************************************
-- GSMP Entity Objects
--**************************************************************
--
-- Switch Controller Entity table
--
gsmpControllerTable OBJECT-TYPE
SYNTAX SEQUENCE OF GsmpControllerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the Switch Controller
Entities. An entry in this table needs to be configured
(created) before a GSMP session might be started."
::= { gsmpObjects 1 }
Sjostrand, et. al. Standards Track [Page 11]
RFC 3295 GSMP MIB June 2002
gsmpControllerEntry OBJECT-TYPE
SYNTAX GsmpControllerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table showing
the data for a specific Switch Controller
Entity. If partitions are used, one entity
corresponds to one specific switch partition.
Depending of the encapsulation used,
a corresponding row in the gsmpAtmEncapTable or the
gsmpTcpIpEncapTable may have been created."
INDEX { gsmpControllerEntityId }
::= { gsmpControllerTable 1 }
GsmpControllerEntry ::= SEQUENCE {
gsmpControllerEntityId GsmpNameType,
gsmpControllerMaxVersion GsmpVersion,
gsmpControllerTimer Unsigned32,
gsmpControllerPort Unsigned32,
gsmpControllerInstance Unsigned32,
gsmpControllerPartitionType GsmpPartitionType,
gsmpControllerPartitionId GsmpPartitionIdType,
gsmpControllerDoResync TruthValue,
gsmpControllerNotificationMap BITS,
gsmpControllerSessionState INTEGER,
gsmpControllerStorageType StorageType,
gsmpControllerRowStatus RowStatus
}
gsmpControllerEntityId OBJECT-TYPE
SYNTAX GsmpNameType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Switch Controller Entity Id is unique
within the operational context of the device."
::= { gsmpControllerEntry 1 }
gsmpControllerMaxVersion OBJECT-TYPE
SYNTAX GsmpVersion
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The max version number of the GSMP protocol being used
in this session. The version is negotiated by the
adjacency protocol."
DEFVAL { 3 }
Sjostrand, et. al. Standards Track [Page 12]
RFC 3295 GSMP MIB June 2002
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -