Network Working Group C. Chung Request for Comments: 2366 SAIC Category: Standards Track M. Greene Independent Contractor (Editor) July 1998 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1998). All Rights Reserved. Abstract 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 IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks' [1]. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. This memo does not specify a standard for the Internet community. Table of Contents 1 The SNMP Network Management Framework ........................ 2 1.1 Object Definitions ......................................... 2 2 Overview ..................................................... 3 2.1 The MARS Client Group ...................................... 4 2.2 The MARS Server Group ...................................... 4 2.3 The MARS Multicast Server Group ............................ 5 Chung & Greene Standards Track [Page 1] RFC 2366 Multicast MIB July 1998 3 IP over ATM Multicast Address Resolution Server MIB Definitions ............................................... 6 4 Acknowledgments ..............................................73 5 References ...................................................73 6 Security Considerations ......................................74 7 Authors' Addresses ...........................................75 8 Full Copyright Statement .....................................76 1. The SNMP Network Management Framework The SNMP Network Management Framework presently consists of these components. They are: o the SMI, described in RFC 1902 [2] - the mechanisms used for describing and naming objects for the purpose of management. o the Textual Conventions, described in RFC 1903 [3] for SNMPv2. o the Conformance Statements, described in RFC 1904 [4] for SNMPv2. o the Simple Network Management Protocol, described in RFC 1157 [5]. o the Protocol Operations, described in RFC 1905 [6] for SNMPv2. o the MIB-II, STD 17, RFC 1213 [7] - the core set of managed objects for the Internet suite of protocols for SNMPv2. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 1.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to also refer to the object type. Chung & Greene Standards Track [Page 2] RFC 2366 Multicast MIB July 1998 2. Overview This MARS MIB is designed to define managed objects that can be used to manage the MARS clients, servers, and the multicast servers (MCS), as described in the RFC2022[1]. The MIB is supposed to be used on a system where one or more MARS clients are running, or where one or more MARS servers are running, or where one or more MARS multicast servers are running. An understanding of MARS, as defined in [1] is assumed in this MIB module definition. However, the following terms are used frequently and are included here for reference: Multicast Group A group of endpoints that communicate with each other such that packets sent from one endpoint are received by all other members of the multicast group. Multicast Address Resolution Server (MARS) A server that distributes multicast group membership information to endpoints. Client/Endpoint An ATM-attached host or router that registers with a MARS and that is a member of one or more multicast groups. An endpoint may establish ATM Virtual Channels (VCs) to the other group members or may make use of a Multicast Server. Cluster The set of clients managed by a MARS. Multicast Server (MCS) A server that sets up ATM Virtual Channels (VCs) between endpoints in a multicast group and to which the endpoints forward data traffic for transmission on their behalf. The MIB is broken down into three major groups: a MARS client group, MARS (server) group, and MARS Multicast Server (MCS) Group. Chung & Greene Standards Track [Page 3] RFC 2366 Multicast MIB July 1998 2.1. The MARS Client Group This client group defines a collection of objects required to be implemented in a MIB for the management of MARS clients. It contains the following tables: o MARS Client Table Information about a client such as its ATM address, the ATM address of its default MARS, registration status, and timers. o MARS Client Multicast Group Table A list of IP multicast address blocks associated with a MARS client. o MARS Client Backup MARS Group Table A list of backup MARS's associated with a MARS client. o MARS Client VC Table Information about VCs opened by a client. o MARS Client Statistics Table Statistics collected by a MARS client. 2.2. The MARS Server Group This MARS server group defines a collection of objects required to be implemented in a MIB for the management of MARS servers. It contains the following tables: o MARS Table Information about a MARS such as its ATM address, its status and timers. o MARS Multicast Group Table A list of IP multicast address blocks associated with a MARS. o MARS VC Table Information about VCs opened by a MARS. o MARS Registered Client Table Chung & Greene Standards Track [Page 4] RFC 2366 Multicast MIB July 1998 A list of clients registered with a MARS. o MARS Registered Multicast Server Table A list of MCSs registered with a MARS. o MARS Statistics Table Statistics collected by a MARS. o MARS Host Map Table Mappings between multicast groups and clients maintained by a MARS. o MARS Server Map Table Mappings between multicast groups and MCSs maintained by a MARS. 2.3. The MARS Multicast Server Group This MARS multicast server group defines a collection of objects required to be implemented in a MIB for the management of MARS multicast servers. It contains the following tables: This group contains the following tables: o MARS Multicast Server Table Information about a MCS, such as its ATM address, default MARS ATM address, and registration state. o MARS MCS Multicast Group Table A list of IP multicast address blocks associated with a MARS MCS. o MARS MCS Backup Mars Group Table A list of backup MARS's associated with a MARS MCS. o MARS Multicast Server VC Table Information about VCs opened by a MCS. o MARS Multicast Server Statistics Table Statistics collected by a MCS. Chung & Greene Standards Track [Page 5] RFC 2366 Multicast MIB July 1998 3. IP Over ATM Multicast Address Resolution Server MIB Definitions IPATM-IPMC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP FROM SNMPv2-CONF snmpModules, MODULE-IDENTITY, NOTIFICATION-TYPE, Counter32, Integer32, Unsigned32, OBJECT-TYPE, IpAddress FROM SNMPv2-SMI AtmAddr FROM ATM-TC-MIB TruthValue, RowStatus FROM SNMPv2-TC ipAdEntAddr FROM RFC1213-MIB InterfaceIndex FROM IF-MIB; marsMIB MODULE-IDENTITY LAST-UPDATED "9804150145Z" -- 15 April 1998 ORGANIZATION "Internetworking Over NBMA (ion) Working Group" CONTACT-INFO " Chris Chung Postal: SAIC 1710 Goodridge Drive Mail Stop 1-4-7 McLean, VA 22102 Tel: +1 703 448 6485 Fax: +1 703 356 2160 E-mail: cchung@tieo.saic.com Editor: Maria Greene Postal: Independent Contractor E-mail: maria@xedia.com " DESCRIPTION "This module defines a portion of the managed information base (MIB) for managing classical IP multicast address resolution server (MARS) and related entities as described in the RFC2022. This MIB is meant to be used in conjunction with the ATM-MIB (RFC1695), MIB-II (RFC1213), and optionally the IF-MIB (RFC1573)." ::= { snmpModules 17 } --*************************************************************** -- IP ATM MARS Client Object Definitions --*************************************************************** Chung & Greene Standards Track [Page 6] RFC 2366 Multicast MIB July 1998 marsClientObjects OBJECT IDENTIFIER ::= { marsMIB 1 } marsClientTable OBJECT-TYPE SYNTAX SEQUENCE OF MarsClientEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The objects defined in this table are used for the management of MARS clients, ATM attached endpoints." ::= { marsClientObjects 1 } marsClientEntry OBJECT-TYPE SYNTAX MarsClientEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry contains a MARS client and its associated attributes. An entry in the marsClientTable has a corresponding entry in the ipAddrTable defined in RFC1213. Association between the ipAddrTable and the marsClientTable is made through the index, ipAdEntAddr." INDEX { ipAdEntAddr, marsClientIndex } ::= { marsClientTable 1 } MarsClientEntry ::= SEQUENCE { marsClientIndex Integer32, marsClientAddr AtmAddr, marsClientDefaultMarsAddr AtmAddr, marsClientHsn Unsigned32, marsClientRegistration INTEGER, marsClientCmi INTEGER, marsClientDefaultMtu INTEGER, marsClientFailureTimer INTEGER, marsClientRetranDelayTimer INTEGER, marsClientRdmMulReqAddRetrTimer INTEGER, marsClientRdmVcRevalidateTimer INTEGER, marsClientJoinLeaveRetrInterval INTEGER, marsClientJoinLeaveRetrLimit INTEGER, marsClientRegWithMarsRdmTimer INTEGER, marsClientForceWaitTimer INTEGER, marsClientLmtToMissRedirMapTimer INTEGER, marsClientIdleTimer INTEGER, marsClientRowStatus RowStatus } Chung & Greene Standards Track [Page 7] RFC 2366 Multicast MIB July 1998 marsClientIndex OBJECT-TYPE SYNTAX Integer32(1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The auxiliary variable used to identify instances of the columnar objects in the MARS MarsClientTable." ::= { marsClientEntry 1 } marsClientAddr OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS read-create STATUS current DESCRIPTION "The ATM address associated with the ATM Client." ::= { marsClientEntry 2 } marsClientDefaultMarsAddr OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS read-create STATUS current DESCRIPTION "The default MARS ATM address which is needed to setup the initial signalling path between a MARS client and its associated MARS." ::= { marsClientEntry 3 } marsClientHsn OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The cluster membership own 32 bit Host Sequence Number. When a new cluster member starts up, it is initialized to zero. When the cluster member sends the MARS_JOIN to register, the HSN will be correctly set to the current cluster sequence number (CSN) when the Client receives the copy of its MARS_JOIN from the MARS. It is is used to track the MARS sequence number." ::= { marsClientEntry 4 } marsClientRegistration OBJECT-TYPE SYNTAX INTEGER { notRegistered (1), registering (2), registered (3), reRegisteringFault (4), Chung & Greene Standards Track [Page 8] RFC 2366 Multicast MIB July 1998 reRegisteringRedirMap (5) } MAX-ACCESS read-create STATUS current DESCRIPTION "An indication with regards to the registration status of this client. The registration codes of 'notRegistered (1)', 'registered (2)', and registered (3) are self-explanatory. The 'reRegisteringFault (4)' indicates the client is in the process of re-registering with a MARS due to some fault conditions. The 'reRegisteringRedMap (5)' status code shows that client is re-registering because it has received a MARS_REDIRECT_MAP message and was told to register with a different MARS from the current MARS." ::= { marsClientEntry 5 } marsClientCmi OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "16 bit Cluster member identifier (CMI) assigned by the MARS which uniquely identifies each endpoint attached to the cluster. The value becomes valid after the 'marsClientRegistration' is set to the value of 'registered (1)'." ::= { marsClientEntry 6 } marsClientDefaultMtu OBJECT-TYPE SYNTAX INTEGER (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The default maximum transmission unit (MTU) used for this cluster. Note that the actual size used for a VC between two members of the cluster may be negotiated during connection setup and may be different than this