⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1604.txt

📁 <VC++网络游戏建摸与实现>源代码
💻 TXT
📖 第 1 页 / 共 5 页
字号:
      N391 - Full status (status of all PVCs) polling counter      N392 - Error threshold      N393 - Monitored events count      T391 - Link integrity verification polling timer      T392 - Polling verification timer      nT3 - Status enquiry timer      nN3 - Maximum status enquiry counter3.3.  Apply MIB II to a Frame Relay Service      Use the System Group to apply to the SNMP proxy-agent, since the      proxy-agent may be monitoring many Frame Relay devices in one      network.  System Group applies to only one system.  This group is      not instantiated.Frame Relay Service MIB Working Group                           [Page 7]RFC 1604                Frame Relay Service MIB               March 1994          sysDescr:  ASCII string describing the SNMP proxy-agent.                     Can be up to 255 characters long. This field is                     generally used to indicate the network providers                     identification and type of service offered.          sysObjectID:  Unique OBJECT IDENTIFIER (OID) for the SNMP                        proxy-agent.          sysUpTime:  Clock in the SNMP proxy-agent; TimeTicks                      in 1/100s of a second.  Elapsed type since                      the proxy-agent came on line.          sysContact:  Contact for the SNMP proxy-agent.                       ASCII string of up to 255 characters.          sysName:  Domain name of the SNMP proxy-agent, for example,                    acme.com          sysLocation:  Location of the SNMP proxy-agent.                        ASCII string of up to 255 characters.          sysServices:  Services of the managed device.  The value "2",                        which implies that                        the Frame Relay network is providing                        a subnetwork level service, is recommended.   This specifies how the Interfaces Group defined in MIB II shall be   used for the management of Frame Relay based interfaces, and in   conjunction with the Frame Relay Service MIB module. This memo   assumes the interpretation of the evolution of the Interfaces group   to be in accordance with: "The interfaces table (ifTable) contains   information on the managed resource's interfaces.  Each sub-layer   below the internetwork layer of a network interface is considered an   interface." Thus, the ifTable allows the following Frame Relay-based   interfaces to be represented as table entries:          - Frame Relay interfaces in the Frame Relay equipment (e.g.,            switches, routers or networks) with Frame Relay interfaces.            This level is concerned with generic frame counts and            not with individual virtual connections.   In accordance with the guidelines of ifTable, frame counts per   virtual connection are not covered by ifTable, and are considered   interface specific and covered in the Frame Relay Service MIB module.   In order to interrelate the ifEntries properly, the Interfaces Stack   Group shall be supported.   Some specific interpretations of ifTable for Frame Relay follow.Frame Relay Service MIB Working Group                           [Page 8]RFC 1604                Frame Relay Service MIB               March 1994           Object   Use for the generic Frame Relay layer           ======   =========================================           ifIndex          Each Frame Relay port is represented                            by an ifEntry.           ifDescr          Description of the Frame Relay interface.                            ASCII string describing the UNI/NNI                            logical port.  Can be up to                            255 characters long.           ifType           The value allocated for Frame Relay                            Service is equal to 44.           ifMtu            Set to maximum frame size in octets for                            this frame relay logical port.           ifSpeed          Peak bandwidth in bits per second                            available for use.  This could be the                            speed of the logical port and not                            the access rate. Actual user information                            transfer rate (i.e., access rate) of the                            UNI or NNI logical port in bits per second                            (this is not the clocking speed).  For                            example, it is 1,536,000 bits per                            second for a DS1-based UNI/NNI logical                            port and 1,984,000 bits per second for an                            E1-based UNI/NNI logical port.           ifPhysAddress    The primary address for this logical port                            assigned by the Frame Relay interface                            provider.  An octet string of zero length                            if no address is used for this logical                            port.           ifAdminStatus     The desired administrative status of the                             frame relay logical port.           ifOperStatus      The current operational status of the                             Frame Relay UNI or NNI logical port.           ifLastChange      The elapsed time since the last                             re-initialization of the logical port.                             The value of sysUpTime at the time the                             logical port entered its current                             operational state.  If the current                             state was entered prior to the last                             re-initialization of the local                             network management subsystem, thenFrame Relay Service MIB Working Group                           [Page 9]RFC 1604                Frame Relay Service MIB               March 1994                             this object contains a zero value.           ifInOctets        The number of received octets.                             This counter only counts octets from the                             beginning of the frame relay header field                             to the end of user data.           ifInUcastPkts     The number of received unerrored,                             unicast frames.           ifInDiscards      The number of received frames discarded.                             Possible reasons are as follows:                             policing, congestion.           ifInErrors        The number of received frames that are                             discarded, because of an error.                             Possible errors can be the following: the                             frame relay frames were too long or were                             too short, the frames had an invalid or                             unrecognized DLCI values, or incorrect                             header values.           ifInUnknownProtos  The number of packets discarded because                              of an unknown or unsupported protocol.                              For Frame Relay Service interfaces, this                              counter will always be zero.           ifOutOctets       The number of transmitted octets.                             This counter only counts octets from the                             beginning of the frame relay header field                             to the end of user data.           ifOutUcastpkts    The number of frames sent.           ifOutDiscards     The number of frames discarded in the                             egress direction. Possible                             reasons are as follows:  policing,                             congestion.           ifOutErrors       The number of frames discarded in the                             egress direction, because of errors.                             Possible reason is transmit underruns.           ifName            This variable is not applicable for                             Frame Relay Service interfaces,                             therefore, this variable contains a                             zero-length string.Frame Relay Service MIB Working Group                          [Page 10]RFC 1604                Frame Relay Service MIB               March 1994           ifInMulticastPkts  The number of received unerrored,                              multicast frames.           ifInBroadcastPkts  This variable is not applicable for                              Frame Relay Service interfaces,                              therefore, this counter is always zero.           ifOutMulticastPkts  The number of sent unerrored,                               multicast frames.           ifOutBroadcastPkts  This variable is not applicable for                               Frame Relay Service interfaces,                               therefore, this counter is always zero.           ifHCInOctets      Only used for DS3-based (and greater)                             Frame Relay logical ports.                             The number of received octets.                             This counter only counts octets from the                             beginning of the frame relay header field                             to the end of user data.           ifHCOutOctets     Only used for DS3-based (and greater)                             Frame Relay logical ports.                             The number of transmitted octets.                             This counter only counts octets from the                             beginning of the frame relay header field                             to the end of user data.           ifLinkUpDownTrapEnble  The value of this object is                                  implementation specific for Frame                                  Relay logical ports.           ifHighSpeed         Set to the user data rate of the frame                               relay logical port in millions of                               bits per second.  If the user data rate                               is less than 1 Mbps, then this value is                               zero.           ifPromiscuousMode   Set to false(2).           ifConnectorPresent  Set to false(2).   Frame Relay Network Service interfaces support the Interface Stack   Group.  Frame Relay Network Service interfaces do not support any   other groups or objects in the Interfaces group of MIB II.  Also,   supporting the SNMP Group of MIB II is an implementation choice.Frame Relay Service MIB Working Group                          [Page 11]RFC 1604                Frame Relay Service MIB               March 19944.  Object Definitions FRNETSERV-MIB DEFINITIONS ::= BEGIN IMPORTS    MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,    Counter32, Integer32,    TimeTicks                                FROM SNMPv2-SMI    DisplayString, PhysAddress,    TimeStamp, RowStatus                     FROM SNMPv2-TC    MODULE-COMPLIANCE, OBJECT-GROUP          FROM SNMPv2-CONF    ifIndex, transmission                    FROM RFC-1213; frnetservMIB MODULE-IDENTITY      LAST-UPDATED "9311161200Z"      ORGANIZATION "IETF Frame Relay Network MIB Working Group"      CONTACT-INFO            "   Tracy A. Brown                Bellcore                331 Newman Springs Rd.                Red Bank, NJ 07701 USA                Tel: 1-908-758-2107                Fax: 1-908-758-4177                E-mail: tacox@mail.bellcore.com."      DESCRIPTION               "The MIB module to describe generic objects for               Frame Relay Network Service."      ::= { transmission 44 }      IfIndex ::= TEXTUAL-CONVENTION            STATUS  current            DESCRIPTION               "The value of this object identifies the               interface for which this entry contains               management information.  The value of this               object for a particular interface has the same               value as the ifIndex object, defined in RFC               1213, for the same interface."            SYNTAX Integer32      frnetservObjects  OBJECT IDENTIFIER ::= { frnetservMIB 1 }      frnetservTraps    OBJECT IDENTIFIER ::= { frnetservMIB 2 } -- The Frame Relay Service Logical Port Group --  the Frame Relay Logical Port GroupFrame Relay Service MIB Working Group                          [Page 12]RFC 1604                Frame Relay Service MIB               March 1994 --  This table is an interface specific addendum --  to the generic ifTable from MIB-II.frLportTable OBJECT-TYPE SYNTAX  SEQUENCE OF FrLportEntry MAX-ACCESS  not-accessible STATUS  current DESCRIPTION         "The Frame Relay Logical Port Information table." ::= { frnetservObjects 1 }frLportEntry OBJECT-TYPE SYNTAX  FrLportEntry MAX-ACCESS  not-accessible STATUS  current DESCRIPTION          "An entry in the Frame Relay Logical Port          Information table." INDEX   { ifIndex } ::= { frLportTable 1 }FrLportEntry ::=  SEQUENCE {      frLportNumPlan          INTEGER,      frLportContact          DisplayString,      frLportLocation          DisplayString,      frLportType          INTEGER,      frLportAddrDLCILen          INTEGER,      frLportVCSigProtocol          INTEGER,      frLportVCSigPointer          OBJECT IDENTIFIER } frLportNumPlan OBJECT-TYPE     SYNTAX  INTEGER {               other(1),               e164(2),               x121(3),               none(4)             }     MAX-ACCESS  read-onlyFrame Relay Service MIB Working Group                          [Page 13]RFC 1604                Frame Relay Service MIB               March 1994     STATUS  current     DESCRIPTION             "The value of this object identifies the network             address numbering plan for this UNI/NNI logical

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -