RFC relevance of controller

As per Relevance of the word controller, we have this rfc below:

Network Working Group H.
Request for Comments: 3295
Category: Standards Track J.
Nortel
B.

June 2002

Definitions of Managed Objects
the General Switch Management Protocol (GSMP

Status of this

This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited

Copyright

Copyright (C) The Internet Society (2002). All Rights Reserved

This memo defines a portion of the Management Information Base (MIB
for the use with the network management protocols in the
community. In particular, it describes managed objects for
General Switch Management Protocol (GSMP).

Table of

1. Introduction............................................. 2
2. The SNMP Management Framework............................ 2
3. Structure of the MIB..................................... 3
3.1 Overview............................................. 3
3.2 Scope................................................ 4
3.3 MIB guideline........................................ 4
3.4 MIB groups........................................... 5
3.4.1 GSMP Switch Controller group................... 5
3.4.2 GSMP Switch group.............................. 6
3.4.3 GSMP Encapsulation groups...................... 6
3.4.4 GSMP General group............................. 7
3.4.5 The GSMP Notifications Group................... 7
3.5 Textual Conventions................................. 8
4. GSMP MIB Definitions.................................... 9
5. Acknowledgments......................................... 42

Sjostrand, et. al. Standards Track [Page 1]

RFC 3295 GSMP MIB June 2002

6. References.............................................. 42
7. Intellectual Property Rights............................ 44
8. Security Considerations................................. 45
9. Authors' Addresses...................................... 46
10. Full Copyright Statement................................ 47

1.

This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it describes managed objects for the General
Management Protocol (GSMP).

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119 [RFC2119].

2. The SNMP Management

The SNMP Management Framework presently consists of five
components

* An overall architecture, described in RFC 2571 [RFC2571].

* Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and is described
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212], and
1215 [RFC1215]. The second version, called SMIv2, is described
STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579], and
2580[RFC2580].

* Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
SNMP message protocol, which is not an Internet standards
protocol, is called SNMPv2c and is described in RFC 1901 [RFC1901]
and RFC 1906 [RFC1906]. The third version of the message
is called SNMPv3 and is described in RFC 1906 [RFC1906], RFC 2572
[RFC2572], and RFC 2574 [RFC2574].

* Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [RFC1157]. A second set
operations and associated PDU formats are described in 1905
[RFC1905].

Sjostrand, et. al. Standards Track [Page 2]

RFC 3295 GSMP MIB June 2002

* A set of fundamental applications described in RFC 2573 [RFC2573],
and the view-based access control mechanism is described in
2575 [RFC2575].

A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [RFC2570].

Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI

This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB

3. Structure of the

This memo defines a portion of the Management Information Base (MIB
for the use with network management protocols in the
community. In particular, it describes managed objects for
General Switch Management Protocol (GSMP), as defined in [RFC3292].

3.1

The General Switch Management Protocol (GSMP) is a general
protocol to control a label switch. GSMP allows a controller
establish and release connections across the switch, to manage
ports and to request configuration information or statistics.
also allows the switch to inform the controller of
events such as a link going down

The GSMP protocol is asymmetric, the controller being the master
the switch being the slave. Multiple switches may be controlled by
single controller using multiple instantiations of the protocol
separate control connections. Also a switch may be controlled
more than one controller by using the technique of partitioning

Each instance of a (switch controller, switch partition) adjacency
a session between one switch controller entity and one switch entity
The MIB provides objects to configure/setup these entities to
the GSMP sessions. It also provide objects to monitor these
sessions

Sjostrand, et. al. Standards Track [Page 3]

RFC 3295 GSMP MIB June 2002

3.2

The GSMP mib is a protocol mib. It contains objects to configure
monitor, and maintain the GSMP protocol entity. It does not
any information learned via the protocol, such as "all ports config
information

The relationships between virtual entities, such as Virtual
Entities, and "physical" entities, such as Switch Entities,
outside of the management of GSMP. This also applies for
management of switch partitions. So this is excluded from the
mib

It is possible to configure which, and how many Switch
are controlling one Switch since every potential session with
switch has to be represented with an Switch entity. It is, however
not possible to define that one Switch Controller shouldn't
other Switch controllers to control the same switch or partition
the switch. It is assumed that there are mechanisms that
controllers and the configuration of them. This is outside the
of this mib

3.3 MIB

Two tables are used to configure potential GSMP sessions depending
you are acting as a GSMP switch controller or a GSMP switch.
row in these tables initiates a GSMP session

The entity ID is a 48-bit name that is unique within the
context of the device. A 48-bit IEEE 802 MAC address, if available
MAY be used for the entity ID. If the Ethernet encapsulation
used, the entity ID MUST be the IEEE 802 MAC address of the
on which the GSMP session is to be setup

First, the encapsulation of the potential GSMP session shall
defined. If ATM is used, a row in the gsmpAtmEncapTable has to
created with the index set to the entity ID. The specified
should be allocated to GSMP. If TCP/IP is used, a row in
gsmpTcpIpEncapTable has to be created with the index set to
entity ID. The specified port shall be allocated to GSMP.
special action is needed if ethernet encapsulation is used

Then the entity information shall be defined. To create a
Entity, an entry in the gsmpSwitchTable is created with the index
to the entity ID. To create a Switch Controller Entity, an entry
the gsmpControllerTable is created with the index set to the
ID

Sjostrand, et. al. Standards Track [Page 4]

RFC 3295 GSMP MIB June 2002

When the row status of the GsmpControllerEntry or GsmpSwitchEntry
set to active (e.g., in the case with ATM or TCP/IP there are
rows with a corresponding entity ID), the adjacency protocol of
is started

Another table, the gsmpSessionTable, shows the actual sessions
are established or are in the process of being established. Each
represents a specific session between an Entity and a peer.
table carries information about the peer, the session, and
that were negotiated by the adjacency procedures.
gsmpSessionTable also contains statistical information regarding
session

This creation order SHOULD be used by all GSMP managers. This is
avoid clash situations in multiple SNMP manager scenarios
different managers may create competing entries in the
tables

Entities may very well be configured by other means than SNMP, e.g.,
the cli command. Such configured entities SHOULD be represented
entries in the tables of this mib and SHOULD be possible to query
and MAY be possible to alter with SNMP

3.4 MIB

3.4.1 GSMP Switch Controller

The controller group is used to configure a potential GSMP session
a Switch Controller. A row in the gsmpControllerTable is created
each such session. If ATM or TCP/IP encapsulation is used,
corresponding row has to be created in these tables before
session adjacency protocol is initiated

If ATM or TCP/IP is used, encapsulation data is defined in
corresponding encapsulation tables. If ethernet is used, the
address of the interface defined for the session is set by
Controller ID object

The adjacency parameters are defined; such

- Max supported GSMP version
- Time between the periodic adjacency messages
- Controller local port number and instance number
- Whether partitions are being used and the partition ID for
specific partitions this controller is concerned with
partitions are used
- The resynchronisation strategy for the session is specified

Sjostrand, et. al. Standards Track [Page 5]

RFC 3295 GSMP MIB June 2002

The notification mapping is set to specify for with events
corresponding SNMP notifications are sent

3.4.2 GSMP Switch

The switch group is used to configure a potential GSMP session on
Switch. A row in the gsmpSwitchTable is created for each
session. If ATM or TCP/IP encapsulation is used, a corresponding
has to be created in these tables before the session
protocol is initiated

If ATM or TCP/IP is used, encapsulation data is defined in
corresponding encapsulation tables. If ethernet is used the
address of the interface defined for the session is set by the
ID object

The adjacency parameters are defined; such
- Max supported GSMP
- Time between the periodic adjacency
- Switch Name, local port number, and instance number
- Whether partitions are being used and the partition ID for
specific partition if partitions are used
- The switch type could be set
- The suggested maximum window size for unacknowledged
messages

Also, a notification mapping is set to specify for with events
corresponding SNMP notifications are sent

3.4.3 GSMP Encapsulation

The ATM Encapsulation Table and the TCP/IP Encapsulation
provides a way to configure information that are
specific. The encapsulation data is further specified in [RFC3293].

If ATM encapsulation is used, the interface and the virtual
are specified

If TCP/IP is used, the IP address and the port number are specified

No special config data needed if Ethernet encapsulation is used

This mib MAY be extended with new, standard or proprietary,
encapsulation types. If a new encapsulation type needs to be added
it SHOULD be done in the form of a new table with the entity ID as
index. A row in that encapsulation table SHOULD be created
any row in a GSMP entity table is created that is using this new
encapsulation

Sjostrand, et. al. Standards Track [Page 6]

RFC 3295 GSMP MIB June 2002

3.4.4 GSMP General

The GSMP session table provides a way to monitor and maintain
sessions

The session is defined by a Switch Controller Entity and
Entity pair

3.4.5 The GSMP Notifications

The GSMP Notification Group defines notifications for GSMP entities
These notifications provide a mechanism for a GSMP device to
the management station of status changes. Also a notification
defined for each type of GSMP events

The group of notifications consists of the following notifications

-

This notification is generated when a session is terminating and
reports the final accounting statistics of the session

-

This notification is generated when a new session is established

-

This notification is generated when a message with a
indication was sent. This means that this notification identifies
change to the gsmpSessionStatFailureInds object in a row of
gsmpSessionTable

-

This notification is generated when a message with a
indication received. This means that this notification identifies
change to the gsmpSessionStatReceivedFailures object in a row of
gsmpSessionTable

-

This notification is generated when a Port Up Event is
received or sent

Sjostrand, et. al. Standards Track [Page 7]

RFC 3295 GSMP MIB June 2002

-

This notification is generated when a Port Down Event is
received or sent

-

This notification is generated when an Invalid Label Event is
received or sent

-

This notification is generated when New Port Event either is
or sent

-

This notification is generated when a Dead Port Event is
received or sent

-

This notification is generated when an Adjacency Update Event
either received or sent

To disable or enable the sending of each notification, the bits
the bitmap are set to 0 or 1 in the Notification mapping objects
the Controller Entitiy or Switch Entity tables

The GSMP notification map capability should not be seen as
duplication of the filter mechanism in the snmp
originator application [RFC2573], but as a compliment, to
the relation between GSMP events and the SNMP notifications
in the GSMP agent. SNMP notifications and GSMP events
sometimes on a different timescale, and it may in some
be devastating for a SNMP application to receive events for each
events. E.g. the invalid label event in a ATM switch scenario
cause mass SNMP notification flooding if mapped to a
notification

3.5 Textual

The datatypes GsmpNameType, GsmpLabelType, GsmpVersion
GsmpPartitionType, and GsmpPartitionIdType are used as
conventions in this document. These textual conventions are used
the convenience of humans reading the MIB. Objects defined
these conventions are always encoded by means of the rules
define their primitive type. However, the textual conventions

Sjostrand, et. al. Standards Track [Page 8]

RFC 3295 GSMP MIB June 2002

special semantics associated with them. Hence, no changes to the
or the SNMP are necessary to accommodate these textual
which are adopted merely for the convenience of readers

4. GSMP MIB

GSMP-MIB DEFINITIONS ::=

OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE
Unsigned32, Integer32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
RowStatus, TruthValue, TimeStamp
StorageType, TEXTUAL-
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB -- [RFC2021]

FROM IF-MIB -- [RFC2863]
AtmVcIdentifier,
FROM ATM-TC-MIB -- [RFC2514]
InetAddressType, InetAddress,
FROM INET-ADDRESS-MIB ; -- [RFC3291]

gsmpMIB MODULE-
LAST-UPDATED "200205310000Z" -- May 31, 2002
ORGANIZATION "General Switch Management Protocol (gsmp
Working Group, IETF
CONTACT-
"WG Charter
http://www.ietf.org/html.charters/gsmp-charter.

WG-email: gsmp@ietf.
Subscribe: gsmp-request@ietf.
Email Archive
ftp://ftp.ietf.org/ietf-mail-archive/gsmp

WG Chair: Avri
Email: avri@acm.

WG Chair: Kenneth
Email: ksundell@nortelnetworks.

Editor: Hans
Email: hans@ipunplugged.

Sjostrand, et. al. Standards Track [Page 9]

RFC 3295 GSMP MIB June 2002

Editor: Joachim
Email: joachim.buerkle@nortelnetworks.

Editor: Balaji
Email: balaji@cplane.com

"This MIB contains managed object definitions for
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
--**************************************************************

GsmpNameType ::= TEXTUAL-
STATUS

"The Name is a 48-bit quantity
A 48-bit IEEE 802 MAC address,
available, may be used."
SYNTAX OCTET STRING (SIZE(6))

GsmpPartitionType ::= TEXTUAL-
STATUS

"Defining if partitions are used and how the partition
is negotiated. "
SYNTAX INTEGER {
noPartition(1),
fixedPartitionRequest(2),
fixedPartitionAssigned(3)
}

GsmpPartitionIdType ::= TEXTUAL-
STATUS

"A 8-bit quantity. The format of the Partition ID is
defined in GSMP. If desired, the Partition ID can
divided into multiple sub-identifiers within a

Sjostrand, et. al. Standards Track [Page 10]

RFC 3295 GSMP MIB June 2002

partition. For example: the Partition ID could
subdivided into a 6-bit partition number and a 2-
sub-identifier which would allow a switch to support 64
partitions with 4 available IDs per partition."
SYNTAX OCTET STRING (SIZE(1))

GsmpVersion ::= TEXTUAL-
STATUS

"The version numbers defined for the GSMP protocol
The version numbers used are defined in
specifications of the respective protocol
1 - GSMPv1.1 [RFC1987]
2 - GSMPv2.0 [RFC2397]
3 - GSMPv3 [RFC3292]
Other numbers may be defined for other
of the GSMP protocol."
SYNTAX Unsigned32

GsmpLabelType ::= TEXTUAL-
STATUS

"The label is structured as a TLV, a tuple, consisting
a Type, a Length, and a Value. The structure is
in [RFC 3292]. The label TLV is encoded as a 2 octet
field, followed by a 2 octet Length field, followed by
variable length Value field
Additionally, a label field can be composed of many
labels that together constitute the label."
SYNTAX OCTET

--**************************************************************
-- GSMP Entity
--**************************************************************

--
-- Switch Controller Entity
--

gsmpControllerTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table represents the Switch
Entities. An entry in this table needs to be
(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-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table
the data for a specific Switch
Entity. If partitions are used, one
corresponds to one specific switch partition
Depending of the encapsulation used
a corresponding row in the gsmpAtmEncapTable or
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
}

gsmpControllerEntityId OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The Switch Controller Entity Id is
within the operational context of the device."
::= { gsmpControllerEntry 1 }

gsmpControllerMaxVersion OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The max version number of the GSMP protocol being
in this session. The version is negotiated by
adjacency protocol."
DEFVAL { 3 }

Sjostrand, et. al. Standards Track [Page 12]

RFC 3295 GSMP MIB June 2002

::= { gsmpControllerEntry 2 }

gsmpControllerTimer OBJECT-
SYNTAX Unsigned32(1..255)
UNITS "100ms
MAX-ACCESS read-
STATUS

"The timer specifies the nominal time
periodic adjacency protocol messages. It is a
for the duration of a GSMP session. The timer
specified in units of 100ms."
DEFVAL { 10 }
::= { gsmpControllerEntry 3 }

gsmpControllerPort OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS

"The local port number for the Switch
Entity."

"General Switch Management Protocol V3: Section 3.1.2"
::= { gsmpControllerEntry 4 }

gsmpControllerInstance OBJECT-
SYNTAX Unsigned32(1..16777215)
MAX-ACCESS read-
STATUS

"The instance number for the Switch
Entity. The Instance number is a 24-bit
that should be guaranteed to be unique
the recent past and to change when the
or node comes back up after going down. Zero
not a valid instance number. "
::= { gsmpControllerEntry 5 }

gsmpControllerPartitionType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"A controller can request the specific partition
to the session by setting the Partition Type
fixedPartitionRequest(2). A controller can let the
decide whether it wants to assign a fixed partition ID

Sjostrand, et. al. Standards Track [Page 13]

RFC 3295 GSMP MIB June 2002

not, by setting the Partition Type to noPartition(1)."
::= { gsmpControllerEntry 6 }

gsmpControllerPartitionId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The Id for the specific switch partition that
Switch Controller is concerned with
If partitions are not used or if the controller lets
switch assigns Partition ID, i.e Partition Type =
noPartition(1), then this object is undefined."
::= { gsmpControllerEntry 7 }

gsmpControllerDoResync OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"This object specifies whether the controller
resynchronise or reset in case of loss of synchronisation
If this object is set to true then the Controller
resync with PFLAG=2 (recovered adjacency)."
DEFVAL { true }
::= { gsmpControllerEntry 8 }

gsmpControllerNotificationMap OBJECT-
SYNTAX BITS {
sessionDown(0),
sessionUp(1),
sendFailureIndication(2),
receivedFailureIndication(3),
portUpEvent(4),
portDownEvent(5),
invalidLabelEvent(6),
newPortEvent(7),
deadPortEvent(8),
adjacencyUpdateEvent(9)
}
MAX-ACCESS read-
STATUS

"This bitmap defines whether a corresponding
notification should be sent if a GSMP event is
by the Switch Controller. If the bit is set to 1
notification should be sent. The handling and filtering
the SNMP notifications are then further specified in

Sjostrand, et. al. Standards Track [Page 14]

RFC 3295 GSMP MIB June 2002

SNMP notification originator application. "
DEFVAL {{ sessionDown, sessionUp
sendFailureIndication, receivedFailureIndication }}
::= { gsmpControllerEntry 9 }

gsmpControllerSessionState OBJECT-
SYNTAX INTEGER {
null(1),
synsent(2),
synrcvd(3),
estab(4)
}
MAX-ACCESS read-
STATUS

"The state for the existing or potential session
this entity is concerned with
The NULL state is returned if the proper
data is not yet configured, if the row is not in
status or if the session is in NULL state as defined
the GSMP specification."
::= { gsmpControllerEntry 10}

gsmpControllerStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The storage type for this controller entity
Conceptual rows having the value 'permanent' need not
write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { gsmpControllerEntry 11 }

gsmpControllerRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"An object that allows entries in this table
be created and deleted using
RowStatus convention
While the row is in active state it's
possible to modify the value of any
for that row except the
and the gsmpControllerRowStatus objects."
::= { gsmpControllerEntry 12 }

Sjostrand, et. al. Standards Track [Page 15]

RFC 3295 GSMP MIB June 2002

--
-- Switch Entity
--

gsmpSwitchTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table represents the
Entities. An entry in this table needs to be
(created) before a GSMP session might be started."
::= { gsmpObjects 2 }

gsmpSwitchEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table
the data for a specific
Entity. If partitions are used, one
corresponds to one specific switch partition
Depending of the encapsulation used
a corresponding row in the gsmpAtmEncapTable or
gsmpTcpIpEncapTable may have been created."
INDEX { gsmpSwitchEntityId }
::= { gsmpSwitchTable 1 }

GsmpSwitchEntry ::= SEQUENCE {
gsmpSwitchEntityId GsmpNameType
gsmpSwitchMaxVersion GsmpVersion
gsmpSwitchTimer Unsigned32,
gsmpSwitchName GsmpNameType
gsmpSwitchPort Unsigned32,
gsmpSwitchInstance Unsigned32,
gsmpSwitchPartitionType GsmpPartitionType
gsmpSwitchPartitionId GsmpPartitionIdType
gsmpSwitchNotificationMap BITS
gsmpSwitchSwitchType OCTET STRING
gsmpSwitchWindowSize Unsigned32,
gsmpSwitchSessionState INTEGER
gsmpSwitchStorageType StorageType
gsmpSwitchRowStatus
}

gsmpSwitchEntityId OBJECT-
SYNTAX

Sjostrand, et. al. Standards Track [Page 16]

RFC 3295 GSMP MIB June 2002

MAX-ACCESS not-
STATUS

"The Switch Entity Id is
within the operational context of the device. "
::= { gsmpSwitchEntry 1 }

gsmpSwitchMaxVersion OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The max version number of the GSMP protocol
supported by this Switch. The version is negotiated
the adjacency protocol."
DEFVAL { 3 }
::= { gsmpSwitchEntry 2 }

gsmpSwitchTimer OBJECT-
SYNTAX Unsigned32(1..255)
UNITS "100ms
MAX-ACCESS read-
STATUS

"The timer specifies the nominal time
periodic adjacency protocol messages. It is a
for the duration of a GSMP session. The timer
specified in units of 100ms."
DEFVAL { 10 }
::= { gsmpSwitchEntry 3 }

gsmpSwitchName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The name of the Switch. The first three octets must be
Organisationally Unique Identifier (OUI) that
the manufacturer of the Switch. This is by default set
the same value as the gsmpSwitchId object if
separately specified. "
::= {gsmpSwitchEntry 4 }

gsmpSwitchPort OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS

Sjostrand, et. al. Standards Track [Page 17]

RFC 3295 GSMP MIB June 2002

"The local port number for this Switch Entity."

"General Switch Management Protocol V3: Section 3.1.2"
::= { gsmpSwitchEntry 5 }

gsmpSwitchInstance OBJECT-
SYNTAX Unsigned32(1..16777215)
MAX-ACCESS read-
STATUS

"The instance number for the Switch Entity
The Instance number is a 24-bit
that should be guaranteed to be unique
the recent past and to change when the
or node comes back up after going down. Zero
not a valid instance number."
::= { gsmpSwitchEntry 6 }

gsmpSwitchPartitionType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"A switch can assign the specific partition identifier
the session by setting the Partition Type
fixedPartitionAssigned(3). A switch can
that no partitions are handled in the session by
the Partition Type to noPartition(1)."
::= { gsmpSwitchEntry 7 }

gsmpSwitchPartitionId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The Id for this specific switch partition that the
entity represents. If partitions are not used, i.e
Partition Type = noPartition(1), then this object
undefined."
::= { gsmpSwitchEntry 8 }

gsmpSwitchNotificationMap OBJECT-
SYNTAX BITS {
sessionDown(0),
sessionUp(1),
sendFailureIndication(2),
receivedFailureIndication(3),
portUpEvent(4),

Sjostrand, et. al. Standards Track [Page 18]

RFC 3295 GSMP MIB June 2002

portDownEvent(5),
invalidLabelEvent(6),
newPortEvent(7),
deadPortEvent(8),
adjacencyUpdateEvent(9)
}
MAX-ACCESS read-
STATUS

"This bitmap defines whether a corresponding
notification should be sent if an GSMP event is
by the Switch Entity. If the bit is set to 1
notification should be sent. The handling and filtering
the SNMP notifications are then further specified in
SNMP notification originator application. "
DEFVAL {{ sessionDown, sessionUp
sendFailureIndication, receivedFailureIndication }}
::= { gsmpSwitchEntry 9 }

gsmpSwitchSwitchType OBJECT-
SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS read-
STATUS

"A 16-bit field allocated by the
of the switch. The Switch
identifies the product. When the Switch Type is
with the OUI from the Switch Name the product
uniquely identified. "
::= { gsmpSwitchEntry 10 }

gsmpSwitchWindowSize OBJECT-
SYNTAX Unsigned32(1..65535)
MAX-ACCESS read-
STATUS

"The maximum number of unacknowledged request
that may be transmitted by the controller without
possibility of loss. This field is used to
request messages from being lost in the switch because
overflow in the receive buffer. The field is a hint
the controller."
::= { gsmpSwitchEntry 11 }

gsmpSwitchSessionState OBJECT-
SYNTAX INTEGER {
null(1),
synsent(2),

Sjostrand, et. al. Standards Track [Page 19]

RFC 3295 GSMP MIB June 2002

synrcvd(3),
estab(4)
}
MAX-ACCESS read-
STATUS

"The state for the existing or potential session
this entity is concerned with
The NULL state is returned if the proper
data is not yet configured, if the row is not in
status or if the session is in NULL state as defined
the GSMP specification."
::= { gsmpSwitchEntry 12}

gsmpSwitchStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The storage type for this switch entity
Conceptual rows having the value 'permanent' need not
write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { gsmpSwitchEntry 13 }

gsmpSwitchRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"An object that allows entries in this table
be created and deleted using
RowStatus convention
While the row is in active state it's
possible to modify the value of any
for that row except the
and the gsmpSwitchRowStatus objects."
::= { gsmpSwitchEntry 14 }

--**************************************************************
-- GSMP Encapsulation
--**************************************************************

--
-- GSMP ATM Encapsulation
--

gsmpAtmEncapTable OBJECT-

Sjostrand, et. al. Standards Track [Page 20]

RFC 3295 GSMP MIB June 2002

SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table contains the atm encapsulation
for the Controller or Switch that uses atm aal5
encapsulation. "
::= { gsmpObjects 3 }

gsmpAtmEncapEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table
the encapsulation data for a
Switch Controller entity or Switch entity."
INDEX { gsmpAtmEncapEntityId }
::= { gsmpAtmEncapTable 1 }

GsmpAtmEncapEntry ::= SEQUENCE {
gsmpAtmEncapEntityId GsmpNameType
gsmpAtmEncapIfIndex InterfaceIndex
gsmpAtmEncapVpi AtmVpIdentifier
gsmpAtmEncapVci AtmVcIdentifier
gsmpAtmEncapStorageType StorageType
gsmpAtmEncapRowStatus
}

gsmpAtmEncapEntityId OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The Controller Id or Switch Id that is
within the operational context of the device. "
::= { gsmpAtmEncapEntry 1 }

gsmpAtmEncapIfIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The interface index for the virtual channel over
the GSMP session is established, i.e., the GSMP
channel for LLC/SNAP encapsulated GSMP messages on
ATM data link layer."
::= { gsmpAtmEncapEntry 2 }

Sjostrand, et. al. Standards Track [Page 21]

RFC 3295 GSMP MIB June 2002

gsmpAtmEncapVpi OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

" The VPI value for the virtual channel over which
GSMP session is established, i.e., the GSMP
channel for LLC/SNAP encapsulated GSMP messages on
ATM data link layer."
DEFVAL { 0 }
::= { gsmpAtmEncapEntry 3 }

gsmpAtmEncapVci OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

" The VCI value for the virtual channel over which
GSMP session is established, i.e., the GSMP
channel for LLC/SNAP encapsulated GSMP messages on
ATM data link layer."
DEFVAL { 15 }
::= { gsmpAtmEncapEntry 4 }

gsmpAtmEncapStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The storage type for this entry. It should have the
value as the StorageType in the referring
Controller entity or Switch entity."
DEFVAL { nonVolatile }
::= { gsmpAtmEncapEntry 5 }

gsmpAtmEncapRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"An object that allows entries in this table
be created and deleted using
RowStatus convention
While the row is in active state it's
possible to modify the value of any
for that row except the gsmpAtmEncapRowStatus object."
::= { gsmpAtmEncapEntry 6 }

Sjostrand, et. al. Standards Track [Page 22]

RFC 3295 GSMP MIB June 2002

--
-- GSMP TCP/IP Encapsulation
--

gsmpTcpIpEncapTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table contains the encapsulation
for the Controller or Switch that uses TCP/IP
encapsulation."
::= { gsmpObjects 4 }

gsmpTcpIpEncapEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table
the encapsulation data for a
Switch Controller entity or Switch entity."
INDEX { gsmpTcpIpEncapEntityId }
::= { gsmpTcpIpEncapTable 1 }

GsmpTcpIpEncapEntry ::= SEQUENCE {
gsmpTcpIpEncapEntityId GsmpNameType
gsmpTcpIpEncapAddressType InetAddressType
gsmpTcpIpEncapAddress InetAddress
gsmpTcpIpEncapPortNumber InetPortNumber
gsmpTcpIpEncapStorageType StorageType
gsmpTcpIpEncapRowStatus
}

gsmpTcpIpEncapEntityId OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The Controller or Switch Id is
within the operational context of the device. "
::= { gsmpTcpIpEncapEntry 1 }

gsmpTcpIpEncapAddressType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

Sjostrand, et. al. Standards Track [Page 23]

RFC 3295 GSMP MIB June 2002

"The type of address in gsmpTcpIpEncapAddress."
::= { gsmpTcpIpEncapEntry 2 }

gsmpTcpIpEncapAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The IPv4 or IPv6 address used
the GSMP session peer."
::= { gsmpTcpIpEncapEntry 3 }

gsmpTcpIpEncapPortNumber OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The TCP port number used for the TCP
establishment to the GSMP peer."
DEFVAL { 6068 }
::= { gsmpTcpIpEncapEntry 4 }

gsmpTcpIpEncapStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The storage type for this entry. It should have the
value as the StorageType in the referring
Controller entity or Switch entity."
DEFVAL { nonVolatile }
::= { gsmpTcpIpEncapEntry 5 }

gsmpTcpIpEncapRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"An object that allows entries in this table
be created and deleted using
RowStatus convention
While the row is in active state it's
possible to modify the value of any
for that row except the gsmpTcpIpEncapRowStatus object."
::= { gsmpTcpIpEncapEntry 6 }

--**************************************************************
-- GSMP Session

Sjostrand, et. al. Standards Track [Page 24]

RFC 3295 GSMP MIB June 2002

--**************************************************************

--
-- GSMP Session
--

gsmpSessionTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table represents the sessions
Controller and Switch pairs. "
::= { gsmpObjects 5 }

gsmpSessionEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the table
the session data for a specific Controller
Switch pair. Also, statistics for this
session is shown."
INDEX { gsmpSessionThisSideId, gsmpSessionFarSideId }
::= { gsmpSessionTable 1 }

GsmpSessionEntry ::= SEQUENCE {
gsmpSessionThisSideId GsmpNameType
gsmpSessionFarSideId GsmpNameType
gsmpSessionVersion GsmpVersion
gsmpSessionTimer Integer32,
gsmpSessionPartitionId GsmpPartitionIdType
gsmpSessionAdjacencyCount Unsigned32,
gsmpSessionFarSideName GsmpNameType
gsmpSessionFarSidePort Unsigned32,
gsmpSessionFarSideInstance Unsigned32,
gsmpSessionLastFailureCode Unsigned32,
gsmpSessionDiscontinuityTime TimeStamp
gsmpSessionStartUptime TimeStamp
gsmpSessionStatSentMessages ZeroBasedCounter32,
gsmpSessionStatFailureInds ZeroBasedCounter32,
gsmpSessionStatReceivedMessages ZeroBasedCounter32,
gsmpSessionStatReceivedFailures ZeroBasedCounter32,
gsmpSessionStatPortUpEvents ZeroBasedCounter32,
gsmpSessionStatPortDownEvents ZeroBasedCounter32,
gsmpSessionStatInvLabelEvents ZeroBasedCounter32,
gsmpSessionStatNewPortEvents ZeroBasedCounter32,

Sjostrand, et. al. Standards Track [Page 25]

RFC 3295 GSMP MIB June 2002

gsmpSessionStatDeadPortEvents ZeroBasedCounter32,
gsmpSessionStatAdjUpdateEvents ZeroBasedCounter32
}

gsmpSessionThisSideId OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"This side ID uniquely identifies the entity that
session relates to within the
context of the device. "
::= { gsmpSessionEntry 1 }

gsmpSessionFarSideId OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The Far side ID uniquely identifies the entity that
session is established against. "
::= { gsmpSessionEntry 2 }

gsmpSessionVersion OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The version number of the GSMP protocol being used
this session. The version is the result of
negotiation by the adjacency protocol."
::= { gsmpSessionEntry 3 }

gsmpSessionTimer OBJECT-
SYNTAX Integer32
UNITS "100ms
MAX-ACCESS read-
STATUS

"The timer specifies the time remaining until
adjacency timer expires. The object could take
values since if no valid GSMP messages
received in any period of time in excess of three
the value of the Timer negotiated by the
protocol loss of synchronisation may be declared.
timer is specified in units of 100ms."
::= { gsmpSessionEntry 4 }

Sjostrand, et. al. Standards Track [Page 26]

RFC 3295 GSMP MIB June 2002

gsmpSessionPartitionId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The Partition Id for the specific switch partition
this session is concerned with."
::= { gsmpSessionEntry 5 }

gsmpSessionAdjacencyCount OBJECT-
SYNTAX Unsigned32(1..255)
MAX-ACCESS read-
STATUS

"This object specifies the current number of
that are established with controllers and the
partition that is used for this session. The
includes this session."
::= { gsmpSessionEntry 6 }

gsmpSessionFarSideName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The name of the far side as advertised in the
message."
::= {gsmpSessionEntry 7}

gsmpSessionFarSidePort OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS

"The local port number of the link across which
message is being sent."

"General Switch Management Protocol V3: Section 3.1.2"
::= { gsmpSessionEntry 8 }

gsmpSessionFarSideInstance OBJECT-
SYNTAX Unsigned32(1..16777215)
MAX-ACCESS read-
STATUS

"The instance number used for the link during
session. The Instance number is a 24-bit
that should be guaranteed to be unique

Sjostrand, et. al. Standards Track [Page 27]

RFC 3295 GSMP MIB June 2002

the recent past and to change when the
or node comes back up after going down. Zero is
a valid instance number."
::= { gsmpSessionEntry 9 }

gsmpSessionLastFailureCode OBJECT-
SYNTAX Unsigned32(0..255)
MAX-ACCESS read-
STATUS

"This is the last failure code that was received
this session. If no failure code have been received,
value is zero."
::= { gsmpSessionEntry 10 }

gsmpSessionDiscontinuityTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The value of sysUpTime on the most recent occasion
which one or more of this session's
suffered a discontinuity. If no such discontinuities
occurred since then, this object contains the
timestamp as gsmpSessionStartUptime ."
::= { gsmpSessionEntry 11 }

gsmpSessionStartUptime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

" The value of sysUpTime when the session came
established state."
::= { gsmpSessionEntry 12 }

gsmpSessionStatSentMessages OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of messages that have been sent in
session. All GSMP messages pertaining to this session
the session came to established state
be counted, also including adjacency protocol
and failure response messages
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when

Sjostrand, et. al. Standards Track [Page 28]

RFC 3295 GSMP MIB June 2002

happened."
::= { gsmpSessionEntry 13 }

gsmpSessionStatFailureInds OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of messages that have been sent with
failure indication in this session. Warning
SHALL NOT be counted
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 12.1"
::= { gsmpSessionEntry 14 }

gsmpSessionStatReceivedMessages OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of messages that have been received
this session. All legal GSMP messages pertaining to
session after the session came to established state
be counted, also including adjacency protocol
and failure response messages
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."
::= { gsmpSessionEntry 15 }

gsmpSessionStatReceivedFailures OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of messages that have been received
this session with a failure indication. Warning
SHALL NOT be counted
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 12.1"
::= { gsmpSessionEntry 16 }

Sjostrand, et. al. Standards Track [Page 29]

RFC 3295 GSMP MIB June 2002

gsmpSessionStatPortUpEvents OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of Port Up events that have been sent
received on this session
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 9.1"
::= { gsmpSessionEntry 17 }

gsmpSessionStatPortDownEvents OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of Port Down events that have been sent
received on this session
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 9.2"
::= { gsmpSessionEntry 18 }

gsmpSessionStatInvLabelEvents OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of Invalid label events that have been
or received on this session
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 9.3"
::= { gsmpSessionEntry 19 }

gsmpSessionStatNewPortEvents OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of New Port events that have been sent

Sjostrand, et. al. Standards Track [Page 30]

RFC 3295 GSMP MIB June 2002

received on this session
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 9.4"
::= { gsmpSessionEntry 20 }

gsmpSessionStatDeadPortEvents OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of Dead Port events that have been sent
received on this session
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 9.5"
::= { gsmpSessionEntry 21 }

gsmpSessionStatAdjUpdateEvents OBJECT-
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-
STATUS

"The number of Adjacency Update events that have been
or received on this session
When the counter suffers any discontinuity,
the gsmpSessionDiscontinuityTime object indicates when
happened."

"General Switch Management Protocol V3: Section 9.6"
::= { gsmpSessionEntry 22 }

-- **************************************************************
-- GSMP
-- **************************************************************

--
-- Notification
--

gsmpEventPort OBJECT-
SYNTAX Unsigned32
MAX-ACCESS accessible-for-

Sjostrand, et. al. Standards Track [Page 31]

RFC 3295 GSMP MIB June 2002

STATUS

"This object specifies the Port Number that
carried in this event."
::= { gsmpNotificationsObjects 1 }

gsmpEventPortSessionNumber OBJECT-
SYNTAX Unsigned32
MAX-ACCESS accessible-for-
STATUS

"This object specifies the Port Session Number that
carried in this event."
::= { gsmpNotificationsObjects 2 }

gsmpEventSequenceNumber OBJECT-
SYNTAX Unsigned32
MAX-ACCESS accessible-for-
STATUS

"This object specifies the Event Sequence Number that
carried in this event."
::= { gsmpNotificationsObjects 3 }

gsmpEventLabel OBJECT-
SYNTAX
MAX-ACCESS accessible-for-
STATUS

"This object specifies the Label that
carried in this event."
::= { gsmpNotificationsObjects 4 }

--
--
--

gsmpSessionDown NOTIFICATION-
OBJECTS {
gsmpSessionStartUptime
gsmpSessionStatSentMessages
gsmpSessionStatFailureInds
gsmpSessionStatReceivedMessages
gsmpSessionStatReceivedFailures
gsmpSessionStatPortUpEvents
gsmpSessionStatPortDownEvents
gsmpSessionStatInvLabelEvents

Sjostrand, et. al. Standards Track [Page 32]

RFC 3295 GSMP MIB June 2002

gsmpSessionStatNewPortEvents
gsmpSessionStatDeadPortEvents

}
STATUS

"When it has been enabled, this notification
generated whenever a session is taken down,
of whether the session went down normally or not
Its purpose is to allow a management
(primarily an accounting application) that
monitoring the session statistics to receive the
values of these counters, so that the application
properly account for the amounts the counters
incremented since the last time the application
them. The gsmpSessionStartUptime object provides
total amount of time that the session was active

This notification is not a substitute for polling
session statistic counts. In particular, the
values reported in this notification cannot be
to be the complete totals for the life of the session
since they may have wrapped while
session was up

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifiers of the objects contained in
notification
An instance of this notification will contain
one instance of each of its objects, and these
will all belong to the same conceptual row of
gsmpSessionTable."
::= { gsmpNotifications 1 }

gsmpSessionUp NOTIFICATION-
OBJECTS {

}
STATUS

"When it has been enabled, this notification
generated when new session is established

The new session is identified by the
and gsmpSessionFarSideId which could be inferred from
Object Identifier of the gsmpSessionFarSideInstance

Sjostrand, et. al. Standards Track [Page 33]

RFC 3295 GSMP MIB June 2002

contained in the notification."
::= { gsmpNotifications 2 }

gsmpSentFailureInd NOTIFICATION-
OBJECTS {
gsmpSessionLastFailureCode

}
STATUS

"When it has been enabled, this notification
generated when a message with a failure indication
sent

The notification indicates a change in the value
gsmpSessionStatFailureInds.
gsmpSessionLastFailureCode contains the
reason

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifiers of the objects contained in
notification."
::= { gsmpNotifications 3 }

gsmpReceivedFailureInd NOTIFICATION-
OBJECTS {
gsmpSessionLastFailureCode

}
STATUS

"When it has been enabled, this notification
generate when a message with a failure
is received

The notification indicates a change in the value
gsmpSessionStatReceivedFailures.
gsmpSessionLastFailureCode contains the
reason

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifiers of the objects contained in
notification."
::= { gsmpNotifications 4 }

Sjostrand, et. al. Standards Track [Page 34]

RFC 3295 GSMP MIB June 2002

gsmpPortUpEvent NOTIFICATION-
OBJECTS {
gsmpSessionStatPortUpEvents
gsmpEventPort
gsmpEventPortSessionNumber

}
STATUS

"When it has been enabled, this notification
generated when a Port Up Event occurs

The notification indicates a change in the value
gsmpSessionStatPortUpEvents

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifier of the
object contained in the notification."
::= { gsmpNotifications 5 }

gsmpPortDownEvent NOTIFICATION-
OBJECTS {
gsmpSessionStatPortDownEvents
gsmpEventPort
gsmpEventPortSessionNumber

}
STATUS

"When it has been enabled, this notification
generated when a Port Down Event occurs

The notification indicates a change in the value
gsmpSessionStatPortDownEvents

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifier of the
object contained in the notification."
::= { gsmpNotifications 6 }

gsmpInvalidLabelEvent NOTIFICATION-
OBJECTS {
gsmpSessionStatInvLabelEvents
gsmpEventPort

Sjostrand, et. al. Standards Track [Page 35]

RFC 3295 GSMP MIB June 2002

gsmpEventLabel

}
STATUS

"When it has been enabled, this notification
generated when an Invalid Label Event occurs

The notification indicates a change in the value
gsmpSessionStatInvLabelEvents

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifier of the
object contained in the notification."
::= { gsmpNotifications 7 }

gsmpNewPortEvent NOTIFICATION-
OBJECTS {
gsmpSessionStatNewPortEvents
gsmpEventPort
gsmpEventPortSessionNumber

}
STATUS

"When it has been enabled, this notification
generated when a New Port Event occurs

The notification indicates a change in the value
gsmpSessionStatNewPortEvents

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifier of the
object contained in the notification."
::= { gsmpNotifications 8 }

gsmpDeadPortEvent NOTIFICATION-
OBJECTS {
gsmpSessionStatDeadPortEvents
gsmpEventPort
gsmpEventPortSessionNumber

}
STATUS

Sjostrand, et. al. Standards Track [Page 36]

RFC 3295 GSMP MIB June 2002

"When it has been enabled, this notification
generated when a Dead Port Event occurs

The notification indicates a change in the value
gsmpSessionStatDeadPortEvents

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifier of the
object contained in the notification."
::= { gsmpNotifications 9 }

gsmpAdjacencyUpdateEvent NOTIFICATION-
OBJECTS {
gsmpSessionAdjacencyCount
gsmpSessionStatAdjUpdateEvents

}
STATUS

"When it has been enabled, this notification
generated when an Adjacency Update Event occurs

The gsmpSessionAdjacencyCount contains the new value
the number of
that are established with controllers and the
partition that is used for this session

The notification indicates a change in the value
gsmpSessionStatAdjUpdateEvents

The session to which this
applies is identified by the gsmpSessionThisSideId
gsmpSessionFarSideId which could be inferred from
Object Identifier of the
or the gsmpSessionStatAdjUpdateEvents object
in the notification."
::= { gsmpNotifications 10 }

Sjostrand, et. al. Standards Track [Page 37]

RFC 3295 GSMP MIB June 2002

--**************************************************************
-- GSMP
--**************************************************************

gsmpGroups OBJECT IDENTIFIER ::= { gsmpConformance 1 }
gsmpCompliances OBJECT IDENTIFIER ::= { gsmpConformance 2 }

gsmpModuleCompliance MODULE-
STATUS

"The compliance statement for agents that
the GSMP MIB."
MODULE -- this
MANDATORY-GROUPS {
}
GROUP

"This group is mandatory for all
Controllers

GROUP

"This group is mandatory for all Switches

GROUP

"This group must be supported if ATM is used for
encapsulation. "

GROUP

"This group must be supported if TCP/IP is used for
encapsulation. "

OBJECT
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
ipv4z(3), ipv6z(4) }

"An implementation is only required to
'unknown(0)', and IPv4 addresses. Supporting addresses
zone index or IPv6 addresses are optional.
Internet addresses by using DNS domain names are
allowed."

OBJECT
SYNTAX InetAddress (SIZE(0|4|8|16|20))

"An implementation is only required to

Sjostrand, et. al. Standards Track [Page 38]

RFC 3295 GSMP MIB June 2002

IPv4 addresses. Supporting addresses with zone index or IPv
addresses are optional."

GROUP

"This group must be supported if
are supported. "

GROUP

"This group must be supported if
are supported. "

::= { gsmpCompliances 1 }

-- units of

gsmpGeneralGroup OBJECT-
OBJECTS {
gsmpSessionVersion
gsmpSessionTimer
gsmpSessionPartitionId
gsmpSessionAdjacencyCount
gsmpSessionFarSideName
gsmpSessionFarSidePort
gsmpSessionFarSideInstance
gsmpSessionLastFailureCode
gsmpSessionDiscontinuityTime
gsmpSessionStartUptime
gsmpSessionStatSentMessages
gsmpSessionStatFailureInds
gsmpSessionStatReceivedMessages
gsmpSessionStatReceivedFailures
gsmpSessionStatPortUpEvents
gsmpSessionStatPortDownEvents
gsmpSessionStatInvLabelEvents
gsmpSessionStatNewPortEvents
gsmpSessionStatDeadPortEvents

}
STATUS

"Objects that apply to all GSMP implementations."
::= { gsmpGroups 1 }

gsmpControllerGroup OBJECT-
OBJECTS {
gsmpControllerMaxVersion

Sjostrand, et. al. Standards Track [Page 39]

RFC 3295 GSMP MIB June 2002

gsmpControllerTimer
gsmpControllerPort
gsmpControllerInstance
gsmpControllerPartitionType
gsmpControllerPartitionId
gsmpControllerDoResync
gsmpControllerNotificationMap
gsmpControllerSessionState
gsmpControllerStorageType

}
STATUS

"Objects that apply GSMP implementations
Switch Controllers."
::= { gsmpGroups 2 }

gsmpSwitchGroup OBJECT-
OBJECTS {
gsmpSwitchMaxVersion
gsmpSwitchTimer
gsmpSwitchName
gsmpSwitchPort
gsmpSwitchInstance
gsmpSwitchPartitionType
gsmpSwitchPartitionId
gsmpSwitchNotificationMap
gsmpSwitchSwitchType
gsmpSwitchWindowSize
gsmpSwitchSessionState
gsmpSwitchStorageType

}
STATUS

"Objects that apply GSMP implementations
Switches."
::= { gsmpGroups 3 }

gsmpAtmEncapGroup OBJECT-
OBJECTS {
gsmpAtmEncapIfIndex
gsmpAtmEncapVpi
gsmpAtmEncapVci
gsmpAtmEncapStorageType

}
STATUS

Sjostrand, et. al. Standards Track [Page 40]

RFC 3295 GSMP MIB June 2002

"Objects that apply to GSMP implementations
supports ATM for GSMP encapsulation."
::= { gsmpGroups 4 }

gsmpTcpIpEncapGroup OBJECT-
OBJECTS {
gsmpTcpIpEncapAddressType
gsmpTcpIpEncapAddress
gsmpTcpIpEncapPortNumber
gsmpTcpIpEncapStorageType

}
STATUS

"Objects that apply to GSMP implementations
supports TCP/IP for GSMP encapsulation."
::= { gsmpGroups 5 }

gsmpNotificationObjectsGroup OBJECT-
OBJECTS {
gsmpEventPort
gsmpEventPortSessionNumber
gsmpEventSequenceNumber

}
STATUS