Nevion Multicon SNMP - Manual (Page 7)

Multicon SNMP Data Model Rev. 0
nevion.com | 7
• bus (1): includes busSysType and busNum parameters that is used as index for tables
under netInterface (2), router (3), gydaBus (4) and module (5)
• netInterface (2): not in use
• router (3): includes table with general information about managed routers
• gydaBus (4): for internal use only
• module (5): this is the most important part of the MIB structure for Flashlink systems,
which includes tables corresponding to logical functions of each module. Note that a
module here is either a Flashlink card or a VikinX router.
• partition (6): deprecated and should not be used, includes partition info for VikinX
routers.
• level (7): this part of the MIB structure is used for controlling levels and cross-point
settings for VikinX routers, but also for controlling matrixes in Flashlink.
• event (8): not in use
2.3 Block functions – module
Each table in the MIB corresponds to a logical function on the card it belongs to. Any card
may have any number of each type of block, depending on the type of card.
Each table contains a superset of attributes for each function block, thus there is likely to be
unimplemented attributes for most blocks. In a future version of Gyda/Multicon, attributes
will be filtered so that only relevant attributes are presented.
For reference to the description for each table within the module tree please refer to the
description within the MIB file itself.
Example:
cableEQTable OBJECT-TYPE
SYNTAX SEQUENCE OF CableEQEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The cableEQTable lists all cableEQs for those modules that have them. A module can
have zero or more cableEQs."
::= { module 5 }
This tells you that this is a table containing all cable equalizers in the system.
2.4 Block addressing – module
Any number of function block of any time may reside on any single card, so the data model
is designed for flexibility. Every block is addressed with a 4-dimensional index, although in
practice only two of these dimensions are in use for any controller. The busSysType
parameter is always 2 (gyda) for Flashlink cards, and busNum is usually 1 for Flashlink cards.
This may have been changed in configuration of the Gyda controller.
The last two indices are in active use. moduleNum matches the card position, counting index-
0, i.e. card position 5 in rack 0 corresponds to moduleNum = 4, position 8 in rack 4
corresponds to moduleNum = 47. The last index is uniquely named for all blocks, but is
simple the address of an instance of that particular table.