BIANCA-BRICK-MIB: View SNMP OID List / Download MIB

Community name for sending traps.

SNMP Version. version1 : SNMP version V1 version1_compat : SNMP version V1 compatibility mode without the appending private OID part (.i). This is for some SNMP managers that cannot handle this extension. In this mode rows with identical index variable content cannot be read correctly. p1 (patch1) : getnext returns the lexicographical next OID (ever!) version1p1_auto : use version1p1_compat if possible use version1p1 if nessesary Usually the OIDs have the format: .1.3.6.x.x .y.y .i .1.3.6.x.x: is the constant part of the OID of the variable specified in MIB-source .y.y : is the specific part of the OID to identify exactly a row. It is the content of all index variables. .i : is a consecutively incremented index number, to distinguish rows with identical index variables Enumeration: 'version1p1-compat': 4, 'version1p1-auto': 5, 'version1': 1, 'version1p1': 3, 'version1-compat': 2.

SNMP listen port.

SNMP trap port.

Local IP address. If this object is set, it's value will be used as the source address for all IP packets that are sent. Otherwise, the IP address used will be retrieved from the ipRouteTable, for the interface the IP packet is to be transmitted over.

Enable/disable trap broadcasting. Enumeration: 'on': 1, 'off': 2.

The biboAdmTrapHostTable defines where traps are sent (i.e., which hosts). If the table is empty traps are broadcasted. Creating entries: Entries are added by assigning an IP address value to the biboAdmTrapHostAddr field. Deleting entries: Entries can be removed by assigning ing the respective biboAdmTrapHostStatus field to 'delete'.

Ip-Address where traps are sent.

Status is always valid, and set to delete only to discard the whole entry. Enumeration: 'valid': 1, 'delete': 2.

Maximum Number of syslog messages stored in memory.

The biboAdmSyslogTable keeps track of syslog messages received. The size of the table (number of entries), is limited by the value of biboAdmSyslogMaxEntries. The columns specify attributes for each message generated. As this information only reports events on the system, all fields are read-only. Creating entries: Entries can only be created by the system and are made each time a syslog message is generated. Deleting entries: Entries are removed by the system once the size limit (biboAdmSyslogMaxEntries) is reached.

Time message was generated.

Level of syslog message. Enumeration: 'info': 7, 'notice': 6, 'err': 4, 'alert': 2, 'debug': 8, 'emerg': 1, 'crit': 3, 'warning': 5.

The text of the syslog message.

Subject of the syslog message. Enumeration: 'bridge': 8, 'rip': 19, 'ppp': 7, 'radius': 14, 'acct': 1, 'ipx': 5, 'ether': 13, 'isdn': 2, 'snmp': 10, 'pabx': 21, 'tapi': 15, 'x21': 11, 'inet': 3, 'fr': 17, 'x25': 4, 'capi': 6, 'ipsec': 22, 'config': 9, 'atm': 20, 'token': 12, 'modem': 18, 'ospf': 16.

The biboAdmLogHostTable lists hosts which are to receive syslog messages. This table also defines which types and levels of messages to send. Creating entries: Entries are created by setting a IP address to biboAdmLogHostAddr. Deleting entries: Entries are removed by setting the appropriate biboAdmLogHostLevel field to 'delete'.

Ip-Address where syslog messages are sent. If the facility is set to memory or console, this field is not used.

Priorities lower or equal this level are sent to loghost. The delete priority is used to discard the whole entry. Enumeration: 'info': 7, 'notice': 6, 'err': 4, 'alert': 2, 'debug': 8, 'emerg': 1, 'crit': 3, 'warning': 5, 'delete': 9.

The facility used for the syslog messages being generated. Enumeration: 'local5': 6, 'local4': 5, 'local7': 8, 'local6': 7, 'local1': 2, 'local0': 1, 'local3': 4, 'local2': 3.

The subject of the messages that are to be generated. system means all subjects except accounting, all means all subjects. Enumeration: 'acct': 2, 'all': 3, 'system': 1.

This object describes the format of the timestamp. none(1) = no timestamp, time(2) = only time is printed, all(3) = date and time is printed. Enumeration: 'none': 1, 'all': 3, 'time': 2.

The biboAdmConfigTable is used for assigning parameters for managing configuration files. Creating entries: Entries are added to this table by assigning a value to the biboAdmConfigCmd object. (i.e., The intermediate result of executing, cmd=save, creates an entry to this table.). Deleting entries: Entries can only be removed by the system and is done only after the requested action has been performed (i.e. Once the cmd=save action is complete.).

Command for configuration handling. Possible values are : save(1) = save configuration (to FLASH) load(2) = load configuration (from FLASH) put(3) = write configuration (via TFTP) get(4) = read configuration (via TFTP) state(5) = write complete configuration (via TFTP) delete(6) = delete configuration (within FLASH) move(7) = move configuration (within FLASH) copy(8) = copy configuration (within FLASH) reboot(9) = reboot the system reorg(10) = reorganizes the flash Enumeration: 'load': 2, 'copy': 8, 'get': 4, 'reorg': 10, 'move': 7, 'reboot': 9, 'state': 5, 'put': 3, 'save': 1, 'delete': 6.

Table object id (OID) to save/load. If this field is set, only this table is saved/loaded. Otherwise all tables are saved/loaded.

NAme of the configuration file in flash memory to save/load.

New name of configuration file in flash memory to move/copy

TFTP host's IP address to send/receive the file to/from. The configuration is transfered directly from flash memory (biboAdmConfigPath) to TFTP-file (biboAdmConfigFile).

The state of this command (i.e., biboAdmConfigCmd). todo(1) = The command has not started; running(2) = The command is executing; done(3) = The command successfully completed; error(4) = The command failed (see the biboAdmSyslogTable). Enumeration: 'done': 3, 'running': 2, 'todo': 1, 'error': 4.

TFTP filename to read/write from/to the specified host. The configuration file received is stored in flash memory specified by biboAdmConfigPath. The actual configuration is not changed.

Configuration directory table. This table contains all available configuration files in flash memory.

Name of the configuration file in flash memory.

Number of tables saved in the file.

Description of directory's contents (e.g., or a series of table numbers).

The biboAdmBoardTable lists information about the installed communications modules. This table is updated after every system boot up. Creating entries: Entries are created by the system upon detecting the installed hardware. Deleting entries: Entries are removed by the system as a result of removed hardware.

The slot, or location of this module.

The name of this module.

The hardware release of this module.

The firmware release of this module.

The part number of this module.

The type of connector used for this module. For modules with more than one connector this value can be changed/switched by setting this object. For example, the CM-BNCTP module supports both twisted pair (RJ45) and 10Base2 (BNC) connectors. If this object is set to 'AUTO' then the BRICK will automatically detect which connector type is being used. Enumeration: 'rj45-100mbit-fdup': 8, 'auto': 1, 'subd15': 4, 'rj45-10mbit-hdup': 5, 'rj45-100mbit-hdup': 7, 'rj45': 2, 'rj45-10mbit-fdup': 6, 'bnc': 3.

The logical unit number of this interface.

The serial number of this module.

The biboAdmUsrTrapTable lists user-defined objects that are used to create traps. These traps are sent locally, but can also be sent to remote hosts using the biboAdmTrapHostTable. Creating entries: Entries are created by assigning the biboATrpObj object a valid object identifier. Deleting entries: Entries are removed by setting the entry's biboATrpStatus object to 'delete'.

The object identifier of an object to use. Each time this object's value changes, a trap is created and sent. Either a single leaf (single variable) or a table (of objects) can be specified.

The status of this entry. Upon creation of a new entry, this object's value is set to 'valid'. Enumeration: 'valid': 1, 'delete': 2.

Domain name.

IP address of name server.

IP address of second name server.

Sets bridging to enable / disable status. Enumeration: 'disabled': 2, 'enabled': 1.

TCP port for remote CAPI demon.

TCP port for trace demon.

UDP port for RIP. Setting this object to zero disables RIP.

This is the software release version

The IP address of the time server.

This is the time offset from GMT in seconds. If the set value is in the range from -24 to 24, it means hours, and is automatically converted to seconds.

Specifies whether to direct syslog messages to the console. Enumeration: 'enable': 1, 'disable': 2.

Specifies which message levels to post to the biboAdmSyslogTable and the console, if applicable. Enumeration: 'info': 7, 'notice': 6, 'err': 4, 'alert': 2, 'debug': 8, 'emerg': 1, 'crit': 3, 'warning': 5.

This object contains the system Identification String.

This table contains an entry for each feature, that can be activated by a license. The licenses have to be entered in the biboAdmLicenseTable. This tabl indicates the current state of the different licenses.

The licenseable feature. Enumeration: 'ipsec': 33, 'bridge': 3, 'modem': 132, 'frame-relay': 7, 'ip': 1, 'extended-wan': 13, 'pri': 131, 'tapi': 8, 'taf': 12, 'g703': 130, 'stac': 6, 'bri': 129, 'extended-lan': 10, 'x25': 4, 'ethernet': 128, 'ipx': 5, 'tunneling': 11, 'ospf': 9, 'leased-line': 14, 'capi': 2.

The current state of the license. Enumeration: 'invalid-license': 3, 'valid-license': 2, 'builtin': 1, 'erase-internal': 5, 'no-license': 4.

The complete serial id string of the special license.

In case of a hardware license corresponding to a dedicated module serial number, it is the slot number of the module.

The max number of allowed chunks.

The current number of chunks in use.

The complete serial id string of the special license.

In case of a hardware license corresponding to a dedicated module serial number, it is the unit number of the module.

This object contains the destination IP address to which BOOTP/DHCP request are forwarded by the BIANCA/BRICK BOOTP relay agent. If this entry is empty no BOOTP forwarding is done.

This object contains the IP address of the RADIUS server (remote dial in user service). If set to 0.0.0.0 RADIUS services are generally disabled (default). The corresponding Radius password is configured in the biboAdmRadiusSecret variable.

This is the local ID string used for PPP authentication (PAP/CHAP). In pre4.3 versions the sysName has been used as the local ID string. This is, for increased ease and transparency of system configuration, no longer true.

TCP port for the HTTP server. Default port is 80, 0 disables the HTTP server.

TCP port for remote TAPI demon.

This field specifies from which source the bricks internal clock is synchronised: none(1) = no time synchronisation time-udp(2) = UDP/TIME (RFC 868), from biboAdmTimeServer time-tcp(3) = TCP/TIME (RFC 868), from biboAdmTimeServer time-sntp(4) = SNTP (RFC 1769), from biboAdmTimeServer isdn(5) = examines ISDN time, from controller stack 0 Enumeration: 'isdn': 5, 'time-tcp': 3, 'none': 1, 'time-udp': 2, 'time-sntp': 4.

This is the intervall for timeserver requests (in seconds). If the set value is in the range from -24 to 24, it means hours, and is automatically converted to seconds. If the time comes from ISDN, the time is updated with the next call after this intervall.

The IP address of the WINS server (NetBIOS Name Server).

The IP address of the alternate WINS server.

The biboAdmCardTable lists installed cards.

The slot, or location of this card.

The name of this card.

State of the card. Enumeration: 'down': 1, 'fail': 3, 'running': 2, 'stopped': 4.

Version of onboard CPLD.

Version of loaded FPGA firmware.

This variable shows the actual card temperature in the unit Celsius.

Card temperature threshold.

If the card temperature raises above the threshold, a trap is generated every 60 seconds. Enumeration: 'critical': 2, 'normal': 1.

Defines the ifOperStatus transition(s) of an ifTable object that generates a SNMP linkUp/linkDown trap: none : disable linkUp/linkDown trap generation. any : enable bintec like trap generation. - entering the up state generates a up trap - any other state change generates a down trap up : enable rfc1157 like trap generation. - entering the up state generates a up trap - leaving the up state generates a down trap down : enable rfc2233 like trap generation. - leaving the down state generates a up trap - entering the down state generates a down trap Seven parameters are sent in each linkUp/linkDown trap pdu: 1. ifEntry.ifIndex (mandatory for linkUp/Down traps) 2. ifEntry.ifDescr 3. ifEntry.ifType 4. ifEntry.ifAdminStatus 5. ifEntry.ifOperStatus 6. system.Description 7. system.Name Enumeration: 'down': 4, 'none': 1, 'any': 2, 'up': 3.

This trap signifies that the Card temperature raises above the critical alarm-threshold

A normal Card temperature has been restored.

This trap signifies that the specified Card is down

This trap signifies that the specified Card is up/running

This trap signifies that the specified Card has failed

This trap signifies that the specified Card is stopped

The IP address of the host machine running the Activity Monitor program. This program displays the information about the current state of all interfaces. Periodically UDP packets are send to this IP address, to refresh the data automatically on the target host. The value 255.255.255.255 represents the broadcast address of the first LAN interface (e.g. 10.255.255.255), so more than one Activity Monitor on different hosts can receive the data.

UDP port for the Activity Monitor protocol.

This parameter configures the content of the Activity Monitor packets, or disables it: off : Activity Monitor disabled physical : send only physical interfaces information physical-virt: send physical and virtual interface information. Enumeration: 'physical-virt': 3, 'off': 1, 'physical': 2.

This is the time interval for the Activity Monitor for sending packets (in seconds) to the specified IP address. The value of 0 disables sending Activity Monitor packets.