Operation and Management Area Working Chen. Li Group Lianyuan. Li Internet-Draft China Mobile Intended status: Standards Track July 11, 2011 Expires: January 12, 2012 Management Information Base for loadbalance draft-li-opsawg-loadbalance-mib-01 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 12, 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 12, 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 . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. Normative References . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Li & Li Expires January 12, 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 12, 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 -- -- MIB objects for Loadbalance module -- IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI SnmpAdminString FROM SNMP-FRAMEWORK-MIB netSnmp FROM NET-SNMP-MIB RowStatus, StorageType FROM SNMPv2-TC InetAddressType, InetAddress FROM INET-ADDRESS-MIB ; LAST-UPDATED "20110711" -- July 11, 2011 CONTACT-INFO "To be added Li Chen (lichenyj@chinamobile.com) China Mobile." Li & Li Expires January 12, 2012 [Page 4] Internet-Draft MIB for loadbalance July 2011 DESCRIPTION "MIB objects for Loadbalance device." ::= { loadBalance 2 } -- -- top level structure -- loadbalanceSystemEntity OBJECT IDENTIFIER ::= { loadbalance 1 } loadbalanceConfig OBJECT IDENTIFIER ::= { loadbalance 2 } loadbalanceAlarm OBJECT IDENTIFIER ::= { loadbalance 3 } LoadbalancePerformance OBJECT IDENTIFIER ::= { loadbalance 4 } -- -- Loadbalance System Entity Tables -- LBSysEntityTable OBJECT-TYPE SYNTAX SEQUENCE OF LBSysEntityEntry MAX-ACCESS not-accessible DESCRIPTION "This table contains information about the Loadbalance system Entities which exist on operating system." ::= { loadbalanceSystemEntityTables 1 } LBSysEntityEntry OBJECT-TYPE SYNTAX LBSysEntityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Li & Li Expires January 12, 2012 [Page 5] Internet-Draft MIB for loadbalance July 2011 "A row describing represents an LB System entity." INDEX { LBSysEntityId } ::= { LBSysEntityTable 1 } LBSysEntityEntry ::= SEQUENCE { LBSysEntityId Integer32 , LBSysEntityAdminStatus OCTET STRING, } LBSysEntityId OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only 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 Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The administrator status of loadbalance device." ::= { LBSysEntityEntry 2 } -- Li & Li Expires January 12, 2012 [Page 6] Internet-Draft MIB for loadbalance July 2011 -- Loadbalance config Table -- LBConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF LBConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about the Loadbalance system Entities which exist on operating system." ::= { loadbalanceConfigTables 1 } LBConfigEntry OBJECT-TYPE SYNTAX LBConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of loadbalance config. The content in this table represents indispensable functions of loadbalance." INDEX { LBConfigDispatchMethod } ::= { LBConfigTable 1 } LBConfigEntry ::= SEQUENCE { LBConfigDispatchMethod Integer32, LBConfigL7PolicyName OCTET STRING, LBConfigHealthCheckElementId Integer32, LBConfigHealthCheckStatus Integer32, LBConfigHealthCheckMethod Integer32, Li & Li Expires January 12, 2012 [Page 7] Internet-Draft MIB for loadbalance July 2011 } LBConfigDispatchMethod OBJECT-TYPE SYNTAX Integer32 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 connection. The index should reflect current dispatch method." ::= { LBConfigEntry 1 } LBConfigL7PolicyName OBJECT-TYPE SYNTAX OCTET 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 Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the check object." ::= { LBConfigEntry 3 } LBConfigHealthCheckStatus OBJECT-TYPE Li & Li Expires January 12, 2012 [Page 8] Internet-Draft MIB for loadbalance July 2011 SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the result of health check." ::= { LBConfigEntry 4 } LBConfigHealthCheckMethod OBJECT-TYPE SYNTAX Integer32 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 HTTPV URL detection." ::= { LBConfigEntry 5 } -- -- Loadbalance Alarm -- LBAlarm OBJECT-TYPE SYNTAX Integer32{LBAlarmSystem (1),LBAlarmLink (2),LBAlarmAuthentication (3),LBAlarmNetworkProtocol (4)} MAX-ACCESS not-accessible STATUS current DESCRIPTION SYNTAX INTEGER{normal(1),fault(0)} "This table specifies loadbalance alarm information. The system Li & Li Expires January 12, 2012 [Page 9] Internet-Draft MIB for loadbalance July 2011 alarm is caused by coldstart and warmstart. The link alarm is caused by linkdown and linkup. The authentication alarm is caused by authentication failure. The network protocol alarm is caused by physical interface routing update. the routing protocol mentioned here includes OSPF and ISIS." ::= { loadbalanceAlarm 1 } -- -- Loadbalance Performance Table -- LBPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF LBPerfEntry 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." ::= { loadbalancePerformanceTables 1 } LBPerfEntry OBJECT-TYPE SYNTAX LBPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents LB performance information." ::= { LBPerfTable 1 } LBPerfEntry ::= SEQUENCE { Li & Li Expires January 12, 2012 [Page 10] Internet-Draft MIB for loadbalance July 2011 LBPerfCPUUtility Integer32, LBPerfL4Connection Integer32, LBPerfL7Connection Integer32, } LBPerfCPUUtility OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This index represents CPU average usage in LB device." ::= { LBPerfEntry 1 } LBPerfL4Connection OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents current active TCP connections of LB." ::= { LBPerfEntry 2 } LBPerfL7Connection OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the result of health check." Li & Li Expires January 12, 2012 [Page 11] Internet-Draft MIB for loadbalance July 2011 ::= { LBPerfEntry 3 } 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. [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 12, 2012 [Page 12]