rfc1156.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

McCloghrie & Rose                                              [Page 19]

RFC 1156                          MIB                           May 1990


          OBJECT:
          -------
               ifOutOctets { ifEntry 16 }

          Syntax:
               Counter

          Definition:
               The total number of octets transmitted out of the
               interface, including framing characters.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ifOutUcastPkts { ifEntry 17 }

           Syntax:
               Counter

          Definition:
               The total number of packets that higher-level protocols
               requested be transmitted to a subnet-unicast address,
               including those that were discarded or not sent.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
              ifOutNUcastPkts { ifEntry 18 }

          Syntax:
               Counter

          Definition:
               The total number of packets that higher-level protocols
               requested be transmitted to a non-unicast (i.e., a subnet
               broadcast or subnet multicast) address, including those



McCloghrie & Rose                                              [Page 20]

RFC 1156                          MIB                           May 1990


               that were discarded or not sent.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ifOutDiscards { ifEntry 19 }

          Syntax:
               Counter

          Definition:
               The number of outbound packets which were chosen to be
               discarded even though no errors had been detected to
               prevent their being transmitted.  One possible reason for
               discarding such a packet could be to free up buffer
               space.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ifOutErrors { ifEntry 20 }

          Syntax:
               Counter

          Definition:
               The number of outbound packets that could not be
               transmitted because of errors.

          Access:
               read-only.

          Status:
               mandatory.





McCloghrie & Rose                                              [Page 21]

RFC 1156                          MIB                           May 1990


          OBJECT:
          -------
               ifOutQLen { ifEntry 21 }

          Syntax:
               Gauge

          Definition:
               The length of the output packet queue (in packets).

          Access:
               read-only.

          Status:
               mandatory.




































McCloghrie & Rose                                              [Page 22]

RFC 1156                          MIB                           May 1990


5.3.  The Address Translation Group

   Implementation of the Address Translation group is mandatory
   for all systems.

   The Address Translation group contains one table which is the
   union across all interfaces of the translation tables for
   converting a NetworkAddress (e.g., an IP address) into a
   subnetwork-specific address.  For lack of a better term, this
   document refers to such a subnetwork-specific address as a
   "physical" address.

   Examples of such translation tables are:  for broadcast media
   where ARP is in use, the translation table is equivalent to
   the ARP cache; or, on an X.25 network where non-algorithmic
   translation to X.121 addresses is required, the translation
   table contains the NetworkAddress to X.121 address
   equivalences.

          OBJECT:
          -------
               atTable { at 1 }

          Syntax:
               SEQUENCE OF AtEntry

          Definition:
               The Address Translation tables contain the NetworkAddress
               to "physical" address equivalences.  Some interfaces do
               not use translation tables for determining address
               equivalences (e.g., DDN-X.25 has an algorithmic method);
               if all interfaces are of this type, then the Address
               Translation table is empty, i.e., has zero entries.

          Access:
               read-write.

          Status:
               mandatory.


          OBJECT:
          -------
               atEntry { atTable 1 }

          Syntax:
               AtEntry ::= SEQUENCE {
                    atIfIndex



McCloghrie & Rose                                              [Page 23]

RFC 1156                          MIB                           May 1990


                        INTEGER,
                    atPhysAddress
                        OCTET STRING,
                    atNetAddress
                        NetworkAddress
               }

          Definition:
               Each entry contains one NetworkAddress to "physical"
               address equivalence.

          Access:
               read-write.

          Status:
               mandatory.

          We now consider the individual components of each Address
          Translation table entry:


          OBJECT:
          -------
               atIfIndex { atEntry 1 }

          Syntax:
               INTEGER

          Definition:
               The interface on which this entry's equivalence is
               effective.  The interface identified by a particular
               value of this index is the same interface as identified
                by the same value of ifIndex.

          Access:
               read-write.

          Status:
               mandatory.


          OBJECT:
          -------
               atPhysAddress { atEntry 2 }

          Syntax:
               OCTET STRING




McCloghrie & Rose                                              [Page 24]

RFC 1156                          MIB                           May 1990


          Definition:
               The media-dependent "physical" address.

          Access:
               read-write.

          Status:
               mandatory.


          OBJECT:
          -------
               atNetAddress { atEntry 3 }

          Syntax:
               NetworkAddress

          Definition:
               The NetworkAddress (e.g., the IP address) corresponding to
               the media-dependent "physical" address.

          Access:
               read-write.

          Status:
               mandatory.

























McCloghrie & Rose                                              [Page 25]

RFC 1156                          MIB                           May 1990


5.4.  The IP Group

   Implementation of the IP group is mandatory for all systems.


          OBJECT:
          -------
               ipForwarding { ip 1 }

          Syntax:
               INTEGER {
                    gateway(1),   -- entity forwards datagrams
                    host(2)       -- entity does NOT forward datagrams
               }

          Definition:
               The indication of whether this entity is acting as an IP
               gateway in respect to the forwarding of datagrams
               received by, but not addressed to, this entity.  IP
               gateways forward datagrams; Hosts do not (except those
               Source-Routed via the host).

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ipDefaultTTL { ip 2 }

          Syntax:
               INTEGER

          Definition:
               The default value inserted into the Time-To-Live field of
               the IP header of datagrams originated at this entity,
               whenever a TTL value is not supplied by the transport
               layer protocol.

          Access:
               read-write.

          Status:
               mandatory.




McCloghrie & Rose                                              [Page 26]

RFC 1156                          MIB                           May 1990


          OBJECT:
          -------
               ipInReceives { ip 3 }

          Syntax:
               Counter

          Definition:
               The total number of input datagrams received from
               interfaces, including those received in error.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ipInHdrErrors { ip 4 }

          Syntax:
               Counter

          Definition:
               The number of input datagrams discarded due to errors in
               their IP headers, including bad checksums, version number
               mismatch, other format errors, time-to-live exceeded,
               errors discovered in processing their IP options, etc.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ipInAddrErrors { ip 5 }

          Syntax:
               Counter

          Definition:
               The number of input datagrams discarded because the IP
               address in their IP header's destination field was not a



McCloghrie & Rose                                              [Page 27]

RFC 1156                          MIB                           May 1990


               valid address to be received at this entity.  This count
               includes invalid addresses (e.g., 0.0.0.0) and addresses
               of unsupported Classes (e.g., Class E).  For entities
               which are not IP Gateways and therefore do not forward
               datagrams, this counter includes datagrams discarded
               because the destination address was not a local address.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ipForwDatagrams { ip 6 }

          Syntax:
               Counter

          Definition:
               The number of input datagrams for which this entity was
               not their final IP destination, as a result of which an
               attempt was made to find a route to forward them to that
               final destination.  In entities which do not act as IP
               Gateways, this counter will include only those packets
               which were Source-Routed via this entity, and the
               Source-Route option processing was successful.

          Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ipInUnknownProtos { ip 7 }

          Syntax:
               Counter

          Definition:
               The number of locally-addressed datagrams received
               successfully but discarded because of an unknown or
               unsupported protocol.



McCloghrie & Rose                                              [Page 28]

RFC 1156                          MIB                           May 1990


           Access:
               read-only.

          Status:
               mandatory.


          OBJECT:
          -------
               ipInDiscards { ip 8 }

          Syntax:
               Counter

          Definition:
               The number of input IP datagrams for which no problems
               were encountered to prevent their continued processing,
               but which were discarded (e.g. for lack of buffer space).
               Note that this counter does not include any datagrams