Cisco MCS-7825-H3-IPC1, Руководство по обслуживанию

Страница: 835 / 974

8-31
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 8 Industry-Standard Management Information Base
RFC1213-MIB (MIB-II)
sysContact OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
The textual identification of the contact person for this managed node, together with information on
how to contact this person.
::= { system 4 }
sysName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
An administratively-assigned name for this managed node. By convention, this is the node's
fully-qualified domain name.
::= { system 5 }
sysLocation OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
The physical location of this node (e.g., telephone closet, 3rd floor).
::= { system 6 }
sysServices OBJECT-TYPE
SYNTAX Integer (0..127)
ACCESS read-only
STATUS mandatory
DESCRIPTION
A value which indicates the set of services that this entity primarily offers. The value is a sum. This
sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node
performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which
performs primarily routing functions would have a value of 4 (2^(3-1)). In contrast, a node which
is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the
context of the Internet suite of protocols, values should be calculated accordingly (layer first, then
functionality):
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)