Interfaces (2) - Avaya Communication Manager IP DECT Installation, Administration And Maintenance Manual

sysName (5)
An administratively-assigned name for this managed node. By convention, this is the node's
fully-qualified domain name.
sysLocation (6)
The physical location of this node (e.g., "telephone closet, 3rd floor").
sysServices (7)
A value which indicates the set of services that this entity potentially 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 only 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
1
2
3
4
7
For systems including OSI protocols, layers 5 and 6 may also be counted.

interfaces (2)

Implementation of the interfaces group is mandatory for all systems.
ifNumber (1)
The number of network interfaces (regardless of their current state) present on this system.
ifTable (2)
The Interfaces table contains information on the entity's interfaces. Each interface is thought of
as being attached to a "subnetwork". Note that this term should not be confused with "subnet"
which refers to an addressing partitioning scheme used in the Internet suite of protocols.
A list of interface entries:
ifEntry (1)
An interface entry containing objects at the sub network layer and below for a particular
interface.
ifIndex (1)
A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The
value for each interface must remain constant at least from one re- initialisation of the entity's
network management system to the next re-initialisation.
functionality
physical (e.g., repeaters)
data link/sub network (e.g., bridges)
internet (e.g., supports the IP)
end-to-end (e.g., supports the TCP)
applications (e.g., supports the SMTP)
MIB-II
Issue 1 August 2006 105