Operation and Management Area Working Chen. Li Group Lianyuan. Li Internet-Draft China Mobile Intended status: Standards Track July 4, 2011 Expires: January 5, 2012 Management Information Base for loadbalance draft-li-opsawg-loadbalance-mib-00 Abstract This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a MIB module for loadbalance device. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 5, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Li & Li Expires January 5, 2012 [Page 1] Internet-Draft MIB for loadbalance July 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Overview of Load-Balance MIB objects . . . . . . . . . . . . . 3 4. Loadbalance-MIB Module Definitions . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7. Normative References . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Li & Li Expires January 5, 2012 [Page 2] Internet-Draft MIB for loadbalance July 2011 1. Introduction Load Balance device is a performance optimization equipment. The trouble associated with the improvement of traffic volume and the rapid growth of data flow can be solved by Load Balance(LB).There are increasing requirements to implement LB in network. This document defines 4 MIB Modules which together support the configuration and monitoring of Load Balance device. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410[RFC3410] . Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578[RFC2578], STD 58, RFC 2579[RFC2579] and STD 58, RFC 2580[RFC2580] 3. Overview of Load-Balance MIB objects The following subsections describe the purpose of each of the objects contained in the loadbalance-MIB. 3.1. Loadbalance System Entity Table The LBSysEntityTable specificed in [RFC1907] and [RFC2233] is used to inquire and modify configuration management information. Each entry row in this table represents a single loadbalance entity. The operator should inquire or modify system/interface/routing protocol parameters by the table. 3.2. Loadbalance config Table Since loadbalance device provides traffic dispatch ,health detection and session persistence function, it is neccessory to monitor loadbalance parameters such as disptach method , health detection method and session persistence policy. The LBConfigTable is a read and write table. Each entry in this table represents the LB working parameter. Li & Li Expires January 5, 2012 [Page 3] Internet-Draft MIB for loadbalance July 2011 3.3. Loadbalance Alarm Table Loadbalance device should report the alarm to operating system in real-time when fault happens. The fault can be divided into general alarm and specific alarm. The general alarm contains system alarm, link alarm and authentication failed alarm. while, the specific alarm contains network protocol alarm, for example OSPF or ISIS. 3.4. Loadbalance Performance Table LBPerfTable is a read-only table which contains statistical information related to L3(IP layer) interface performance parameter, L3 network protocol parameter , L4/L7(transport layer or application layer) current active connections. 4. Loadbalance-MIB Module Definitions Loadbalance-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, Counter32, Unsigned32 FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] RowStatus, TimeStamp, StorageType FROM SNMPv2-TC -- [RFC2579] IndexInteger, IndexIntegerNextFree FROM DIFFSERV-MIB -- [RFC3289] LAST-UPDATED "20110704" -- July 4, 2011 CONTACT-INFO "To be added Li Chen (lichenyj@chinamobile.com) China Mobile." Li & Li Expires January 5, 2012 [Page 4] Internet-Draft MIB for loadbalance July 2011 DESCRIPTION "This MIB contains managed object definitions for the Loadbalance device." ::= { LBSysEntityMIB 1 } -- Loadbalance System Entity Table LBSysEntityEntry OBJECT-TYPE SYNTAX SEQUENCE OF LBSysEntityEntry MAX-ACCESS accessible STATUS current DESCRIPTION "This table contains information about the Loadbalance system Entities which exist on operating system." ::= { LBSysEntityObjects 2 } LBSysEntityEntry OBJECT-TYPE SYNTAX LBSysEntityEntry MAX-ACCESS accessible STATUS current DESCRIPTION "An entry in this table represents an LB System entity. An entry can be created by a network administrator or by an SNMP agent as instructed by LDP." INDEX { LBSysEntitySys, LBSysEntityInt} ::= { LBSysEntityTable 1 } LBSysEntitySys::= SEQUENCE { LBSysEntityId sysObjectID, LBSysEntityName String, Li & Li Expires January 5, 2012 [Page 5] Internet-Draft MIB for loadbalance July 2011 LBSysEntityAdminStatus INTEGER, LBSysEntitySysServices INTEGER, LBSysEntitySysLocation String, LBSysEntitySysUpTime TimeTicks, LBSysEntitySysIntfNumber INTEGER, LBSysEntitySysIntfIndex INTEGER, LBSysEntitySysIntfMtu INTEGER, LBSysEntitySysIntfSpeed Gauge32, LBSysEntitySysIntfPhysAddress PhysAddress, LBSysEntitySysIntfAdminStatus INTEGER{ up(1), down(2), testing(3)}, LBSysEntitySysIntfLastChange TimeTicks } LBSysEntityId OBJECT-TYPE SYNTAX LBSysIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "LB operates identifier." REFERENCE "RFC1907,SNMPv2, Management Information Base for Version 2 of the Simple Network Management Protocol ." ::= { LBSysEntityEntry 1 } LBSysEntityAdminStatus OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only Li & Li Expires January 5, 2012 [Page 6] Internet-Draft MIB for loadbalance July 2011 STATUS current DESCRIPTION "The administrator status of loadbalance device." ::= { LBSysEntityEntry 2 } LBSysEntitySysIntfNumber OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is used to describe the number of physical interface." ::= { LBSysEntityEntry 3 } LBSysEntitySysIntfMtu OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This index is used to describe the MTU vlaue of a physical interface." DEFVAL { 1500 } ::= { LBSysEntityEntry 4 } -- Loadbalance config Table LBConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF LBConfigEntry MAX-ACCESS not-accessible STATUS current Li & Li Expires January 5, 2012 [Page 7] Internet-Draft MIB for loadbalance July 2011 DESCRIPTION "A table of loadbalance config. The content in this table represents indispensable functions of loadbalance." ::= { LBConfigObjects 5 } LBConfigObjectsEntry OBJECT-TYPE SYNTAX LBConfigObjectsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a LB device. The information contained in a row is read-only." ::= { LBConfigTable 1 } LBConfigEntry ::= SEQUENCE { LBConfigDispatchMethod INTEGER, LBConfigL7PolicyName String, LBConfigHealthCheckElementId INTEGER, LBConfigHealthCheckStatus INTEGER, LBConfigHealthCheckMethod INTEGER, } LBConfigDispatchMethod OBJECT-TYPE SYNTAX INTEGER { MAX-ACCESS read-only STATUS current DESCRIPTION "The loadbalance dispatch methods include the following ways: route map,round robin, weighted round robin, random,response time, least Li & Li Expires January 5, 2012 [Page 8] Internet-Draft MIB for loadbalance July 2011 connection. The index should reflect current dispatch method. ::= { LBConfigEntry 1 } LBConfigL7PolicyName OBJECT-TYPE SYNTAX String MAX-ACCESS read-only STATUS current DESCRIPTION "The Policy name of current status. The mainly L7 policy we used is HTTP balance." ::= { LBConfigEntry 2 } LBConfigHealthCheckElementId OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the check object." ::= { LBConfigEntry 3 } LBConfigHealthCheckStatus OBJECT-TYPE SYNTAX INTEGER{normal(1),fault(0)} MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the result of health check." DEFVAL { 1 } ::= { LBConfigEntry 4 } Li & Li Expires January 5, 2012 [Page 9] Internet-Draft MIB for loadbalance July 2011 LBConfigHealthCheckMethod OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents health check method. There are always three ways to check health: IP ping detection, TCP open detection and HTTP URL detection." ::= { LBConfigEntry 5 } -- Loadbalance Alarm Table LBAlarmTable OBJECT-TYPE SYNTAX SEQUENCE OF LBAlarmTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies loadbalance alarm information. Entries in this table define alarm event." ::= { LBAlarmObejcets 4 } LBAlarmObejcetEntry OBJECT-TYPE SYNTAX LBAlarmObejcetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information about LB alarm. The information contained in a row is read-only." ::= { LBAlarmtable 1 } Li & Li Expires January 5, 2012 [Page 10] Internet-Draft MIB for loadbalance July 2011 LBAlarmEntry ::= SEQUENCE { LBAlarmSystem INTEGER, LBAlarmLink INTEGER, LBAlarmAuthentication INTEGER, LBAlarmNetworkProtocol INTEGER, } LBAlarmSystem OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The loadbalance system alarm is caused by coldstart and warmstart." ::= { LBAlarmEntry 1 } LBAlarmLink OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The loadbalance system alarm is caused by linkdown and linkup." ::= { LBAlarmEntry 2 } LBAlarmAuthentication OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current Li & Li Expires January 5, 2012 [Page 11] Internet-Draft MIB for loadbalance July 2011 DESCRIPTION "The loadbalance system alarm is caused by authentication failure." ::= { LBAlarmEntry 3 } LBAlarmNetworkProtocol OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The loadbalance system alarm is caused by physical interface routing update. the routing protocol mentioned here includes OSPF and ISIS." ::= { LBAlarmEntry 4 } -- Loadbalance Performance Table LBPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF LBPerfTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies the performance of loadbalance device. The performance should be divided into hardware and software. The hardware performance includes CPU utility, interface performance, while as to the software performance, we focus on active connection on L4 or L7." ::= { LBPerfObejcets 4 } LBPerfEntry OBJECT-TYPE SYNTAX LBPerfEntry MAX-ACCESS not-accessible STATUS current Li & Li Expires January 5, 2012 [Page 12] Internet-Draft MIB for loadbalance July 2011 DESCRIPTION "An entry in this table represents LB performance information. The information contained in a row is read-only." ::= { LBPerfTable 1 } LBPerfEntry ::= SEQUENCE { LBPerfCPUUtility INTEGER, LBPerfIntf INTEGER, LBPerfL4Connection INTEGER, LBPerfL7Connection INTEGER, } LBPerfCPUUtility OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This index represents CPU average usage in LB device." ::= { LBPerfEntry 1 } LBPerfIntf OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This index represents interface performance of LB device. The interface performance should include many parameters. Such as packet loss, delay, jitter and so on." "However, we only mention the interface usage here. This object Li & Li Expires January 5, 2012 [Page 13] Internet-Draft MIB for loadbalance July 2011 should be continued later." ::= { LBPerfEntry 2 } LBPerfL4Connection OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This index represents current active TCP connections of LB." ::= { LBPerfEntry 3 } LBPerfL7Connection OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This index represents current active HTTP connections of LB." ::= { LBPerfEntry 4 } 5. Security Considerations It needs to be further identified. 6. IANA Considerations It is no necessary to request new IANA code in the draft. 7. Normative References [RFC1097] Jeff Case,Marshall T. Rose,Steven Waldbusser,Keith McCloghrie, "Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1097, Dec 1995. Li & Li Expires January 5, 2012 [Page 14] Internet-Draft MIB for loadbalance July 2011 [RFC2233] Keith McCloghrie,F. Kastenholz "The Interfaces Group MIB using SMIv2", RFC 2233, Nov 1997. Authors' Addresses Chen Li China Mobile Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District Beijing 100053 P.R. China Email: lichenyj@chinamobile.com Lianyuan Li China Mobile Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District Beijing 100053 P.R. China Email: lilianyuan@chinamobile.com Li & Li Expires January 5, 2012 [Page 15]