Operation and Management Area Working Chen. Li Group Lianyuan. Li Internet-Draft China Mobile Intended status: Standards Track Tina. TSOU Expires: May 3, 2012 Huawei October 31, 2011 Management Information Base for Load Balancers draft-li-opsawg-loadbalance-mib-02 Abstract Load balancer is deployed widely in datacenter nowadays. There is a requirement to build a unique LB network management system where two or more vendors' LB devices are used. We propose the standard MIBs for unique NMS. Load balancer description is introduced at "http://en.wikipedia.org/wiki/Load_balancing_(computing)". 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 load balance 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 May 3, 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 Li, et al. Expires May 3, 2012 [Page 1] Internet-Draft Load Balancer MIB October 2011 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Structure of Load-Balance MIB objects . . . . . . . . . . . . 3 5. Loadbalance-MIB Module Definitions . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. Normative References . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Li, et al. Expires May 3, 2012 [Page 2] Internet-Draft Load Balancer MIB October 2011 1. Introduction Load balancer is deployed widely in datacenter nowadays. There is a requirement to build a unique LB network management system where two or more vendors' LB devices are used. We propose the standard MIBs for unique NMS. 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, [RFC2578] STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 4. Structure of Load-Balance MIB objects The following subsections describe the purpose of each of the objects contained in the loadbalance-MIB. 3.1. Load balance System Entity Table The LBSysEntityTable is used to inquire and modify configuration management information. Each entry row in this table represents a single loadbalance entity. The operator can inquire or modify system/interface/routing protocol parameters from the table. 3.2. Load balance config Table Li, et al. Expires May 3, 2012 [Page 3] Internet-Draft Load Balancer MIB October 2011 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. 3.3. Load balance 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. Load balance 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. 5. Loadbalance-MIB Module Definitions LOAD-BALANCER-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Integer32 FROM SNMPv2-SMI -- RFC2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC2580 ; lbMIB MODULE-IDENTITY LAST-UPDATED "201110310000Z" ORGANIZATION "IETF Operations and Management Area Working Group http://datatracker.ietf.org/wg/opsawg/" CONTACT-INFO "email: Li Chen (lichenyj@chinamobile.com) China Mobile" DESCRIPTION "MIB objects for load-balancing devices. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Li, et al. Expires May 3, 2012 [Page 4] Internet-Draft Load Balancer MIB October 2011 Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)." REVISION "201110310000Z" ::= { mib-2 XXX } lbMIBNotifications OBJECT IDENTIFIER ::= { lbMIB 0 } lbMIBObjects OBJECT IDENTIFIER ::= { lbMIB 1 } lbMIBConformance OBJECT IDENTIFIER ::= { lbMIB 2 } lbMIBCompliances OBJECT IDENTIFIER ::= { lbMIBConformance 1 } lbMIBGroups OBJECT IDENTIFIER ::= { lbMIBConformance 2 } -- -- Load-balancer system entity table -- lbSysEntityTable OBJECT-TYPE SYNTAX SEQUENCE OF LbSysEntityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about the load-balancing system entities." ::= { lbMIBObjects 1 } lbSysEntityEntry OBJECT-TYPE SYNTAX LbSysEntityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row describing an entity of the load-balancing system." INDEX { lbSysEntityId } ::= { lbSysEntityTable 1 } LbSysEntityEntry ::= SEQUENCE { lbSysEntityId Unsigned32, lbSysEntityAdminStatus Integer32 } lbSysEntityId OBJECT-TYPE SYNTAX Unsigned32 (1..'ffffffff'H) Li, et al. Expires May 3, 2012 [Page 5] Internet-Draft Load Balancer MIB October 2011 MAX-ACCESS not-accessible STATUS current DESCRIPTION "LB operates identifier." ::= { lbSysEntityEntry 1 } lbSysEntityAdminStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The administrative status of the load-balancer." ::= { lbSysEntityEntry 2 } -- -- Load-balancer configuration table -- lbConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF LbConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains configuration information about the load-balancer." ::= { lbMIBObjects 2 } lbConfigEntry OBJECT-TYPE SYNTAX LbConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Configuration information for a load-balancer." INDEX { lbConfigDispatchMethod } ::= { lbConfigTable 1 } LbConfigEntry ::= SEQUENCE { lbConfigDispatchMethod Integer32, lbConfigL7PolicyName OCTET STRING, lbConfigHealthCheckElementId Unsigned32, lbConfigHealthCheckStatus Integer32, lbConfigHealthCheckMethod Integer32 } lbConfigDispatchMethod OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current Li, et al. Expires May 3, 2012 [Page 6] Internet-Draft Load Balancer MIB October 2011 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 Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index represents the check object." ::= { lbConfigEntry 3 } lbConfigHealthCheckStatus OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the result of health check." ::= { lbConfigEntry 4 } lbConfigHealthCheckMethod OBJECT-TYPE SYNTAX Integer32 (1..2147483647) 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 } -- -- Load-balancer alarms -- lbAlarm OBJECT-TYPE SYNTAX INTEGER { Li, et al. Expires May 3, 2012 [Page 7] Internet-Draft Load Balancer MIB October 2011 lbAlarmSystem(1), lbAlarmLink(2), lbAlarmAuthentication(3), lbAlarmNetworkProtocol(4) } MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies loadbalance alarm information. The system 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." ::= { lbMIBObjects 3 } -- -- Load-balancer 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." ::= { lbMIBObjects 4 } lbPerfEntry OBJECT-TYPE SYNTAX LbPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents LB performance information." INDEX { lbPerfCPUUtility } ::= { lbPerfTable 1 } LbPerfEntry ::= SEQUENCE { lbPerfCPUUtility Integer32, lbPerfL4Connection Integer32, lbPerfL7Connection Integer32 } Li, et al. Expires May 3, 2012 [Page 8] Internet-Draft Load Balancer MIB October 2011 lbPerfCPUUtility OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index represents CPU average usage in LB device." ::= { lbPerfEntry 1 } lbPerfL4Connection OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents current active TCP connections of LB." ::= { lbPerfEntry 2 } lbPerfL7Connection OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The index reprensents the result of health check." ::= { lbPerfEntry 3 } -- -- Conformance statements -- lbMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP engines that support the LOAD-BALANCER-MIB." MODULE MANDATORY-GROUPS { lbMIBGroup } ::= { lbMIBCompliances 1 } lbMIBGroup OBJECT-GROUP OBJECTS { lbSysEntityAdminStatus, lbConfigL7PolicyName, lbConfigHealthCheckElementId, lbConfigHealthCheckStatus, lbConfigHealthCheckMethod, lbPerfL4Connection, lbPerfL7Connection } STATUS current DESCRIPTION Li, et al. Expires May 3, 2012 [Page 9] Internet-Draft Load Balancer MIB October 2011 "A collection of objects for managing load-balancer." ::= { lbMIBGroups 1 } END 6. Security Considerations [TBD] 7. IANA Considerations IANA is requested to assign a value for "XXX" under the 'mib-2' subtree and to record the assignment in the SMI Numbers registry. When the assignment has been made, the RFC Editor is asked to replace "XXX" (here and in the MIB module) with the assigned value and to remove this note. 8. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. Li, et al. Expires May 3, 2012 [Page 10] Internet-Draft Load Balancer MIB October 2011 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 Tina TSOU Huawei Email: Tina.Tsou.Zouting@huawei.com Li, et al. Expires May 3, 2012 [Page 11]