TIGER
Detailed view of the defined objects, syntax rules, and hierarchical paths.
218
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
218 total| Object Name |
|---|
ngcan OBJECT IDENTIFIER .1.3.6.1.4.1.1978 |
IMPORTS Unknown .1.3.6.1.4.1.1978 |
tiger OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2 |
generalTiger OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1 |
ifTStack OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.1 |
ifTStackTableThe table containing information on the relationships
between the multiple sub-layers of network interfaces.
In particular, it contains information on which sub-
layers run 'on top of' which other sub-layers. Each
sub-layer corresponds to a conceptual row in the
ifTable. SEQUENCE OF IfTStackEntry .1.3.6.1.4.1.1978.2.1.1.1 |
ifTStackEntryInformation on a particular relationship between two
sub-layers, specifying that one sub-layer runs on
'top' of the other sub-layer. Each sub-layer
corresponds to a conceptual row in the ifTable. IfTStackEntry .1.3.6.1.4.1.1978.2.1.1.1.1 |
ifTStackIndexA 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-initialization of the entity's
network management system to the next re-
initialization.rw INTEGER .1.3.6.1.4.1.1978.2.1.1.1.1.1 |
ifTStackHigherLayerThe value of ifIndex corresponding to the higher
sub-layer of the relationship, i.e., the sub-layer
which runs on 'top' of the sub-layer identified by the
corresponding instance of ifTStackLowerLayer. If there
is no higher sub-layer (below the internetwork layer),
then this object has the value 0.rw INTEGER .1.3.6.1.4.1.1978.2.1.1.1.1.2 |
ifTStackLowerLayerThe value of ifIndex corresponding to the lower sub-
layer of the relationship, i.e., the sub-layer which
runs 'below' the sub-layer identified by the
corresponding instance of ifTStackHigherLayer. If
there is no lower sub-layer, then this object has the
value 0.rw INTEGER .1.3.6.1.4.1.1978.2.1.1.1.1.3 |
ifTStackStatusThe status of the relationship between two sub-layers.
Changing the value of this object from 'active' to
'notInService' or 'destroy' will likely have
consequences up and down the interface stack. Thus,
write access to this object is likely to be
inappropriate for some types of interfaces, and many
implementations will choose not to support write-
access for any type of interface.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.1978.2.1.1.1.1.4 |
tsystem OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.2 |
tigSystemDateThe host's notion of the local date and time of day.rw TigerDateAndTime .1.3.6.1.4.1.1978.2.1.2.1 |
tigSystemExceptionEchoWhen enabled it allows the system to send copies of any
exceptions to the console port. When disabled, exceptions are
not sent to the console port.rw Enumeration .1.3.6.1.4.1.1978.2.1.2.2 |
tigSystemExceptionLoggingWhen enabled, the system will copy exceptions into its log
file on the ram file system (/ramdisk/system.log). When disabled, exceptions are
not logged into the file.rw Enumeration .1.3.6.1.4.1.1978.2.1.2.3 |
tigSystemExceptionSaveLogWhen enabled, any FATAL exception will cause the file
'/ramdisk/system.log' to be save onto the flash file system
as '/flash/error.log'.
When disabled, all logging information saved in
'/ramdisk/system.log' is lost.rw Enumeration .1.3.6.1.4.1.1978.2.1.2.4 |
tigPCMCIATableAn entry shall be placed in the table for each PCMCIA slot that is in use. SEQUENCE OF TigPCMCIAEntry .1.3.6.1.4.1.1978.2.1.2.5 |
tigPCMCIAEntryA (conceptual) entry for one logical token ring port on the host. TigPCMCIAEntry .1.3.6.1.4.1.1978.2.1.2.5.1 |
tigPCMCIASlotThe PCMCIA slot identified by this table entry.ro INTEGER .1.3.6.1.4.1.1978.2.1.2.5.1.1 |
tigPCMCIAIfThe Interface index that is bound to this PCMCIA slot.
In the current Tiger environment, slot 0 uses ifIndex 7 and
slot 1 uses ifIndex 8.rw InterfaceIndex .1.3.6.1.4.1.1978.2.1.2.5.1.2 |
tigTokenRingSpeedDefines the Token Ring speed used on this interface (in Mbit/sec).rw Enumeration .1.3.6.1.4.1.1978.2.1.2.5.1.3 |
tigPCMCIATypeSpecifies the type of cards that is configured in the slot:
token-ring - a Madge Token Ring card
modem - a modem cardrw Enumeration .1.3.6.1.4.1.1978.2.1.2.5.1.4 |
tigConfigFileThis field contains the file specification for the configuration
file used at boot time.ro OCTET STRING .1.3.6.1.4.1.1978.2.1.2.6 |
tigRestartReasonInforms the NMS why the Tiger most recently restarted:
power - due to a power failure
reset-button - someone pushed the reset button
watchdog - the internal watchdog timer forced a reset
config-fail - there was a catastrophic failure in the configuration file causing a system reset.
('tigConfigFile' informs you which config file is currently being used)
other - someother unknown reason. (these should never occur)
double-bus-fault - a invalid address was being reference while the exception handler for a bus-fault
exception (an invalid address was referenced) was being executed.
fatal-exception - a fatal software exception occured inside Tiger
reboot-command - a user issued a 'reboot' command on a consolero Enumeration .1.3.6.1.4.1.1978.2.1.2.7 |
tigClearStatsWhen set to 'clear' all of TIGERs statistics are cleared to zero.
It will affect each of the ports statistics herarcially, and also
AUTIF statistics.
When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:
1/ all of the statistics have actually been zeroed, and
2/ tigClearStatsTime has been updated with the correct time.
Should an NMS read the object and receive a 'cleared' indication, the SNMP agent
will set this object to 'cleared-confirmed'. This aids the NMS in determining
whether or not the agent successfully received subsequent clear request.
Normal operation would be:
NMS Agent
set 'clear'
.
read
'clear' <
clearing complete, set to 'cleared'
.
read
'cleared' <
.
read
'cleared-confirmed' <
Rules:
1/ NMS must read 'cleared-confirmed' BEFORE attempting
to set 'clear'.
2/ After setting 'clear' the NMS must read 'cleared'.
then the NMS must read 'cleared-confirmed'.
In this manner, if a 'clear' command was missed by the agent,
the variable will still be set to either 'cleared' or 'cleared-confirmed'.rw Enumeration .1.3.6.1.4.1.1978.2.1.2.8 |
tigClearStatsTimeThe number of ticks when the Tiger last received a tigClearStats command.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.1978.2.1.2.9 |
tigCpuTrapControlThis option allows a tigCpu trap to be sent when:
a) the idle CPU time falls below 5%
b) when the idle CPU times exceeds 60% only after having fallen below 5%.rw Enumeration .1.3.6.1.4.1.1978.2.1.2.10 |
tigCpuIdleStateThis tell us if the TIGER is in its CPU idle alarm state.
idle (1) - means that the CPU idle time is above 60&
alarm (2) - means that the CPU idle time is below 5%.ro Enumeration .1.3.6.1.4.1.1978.2.1.2.11 |
tigSystemSerialNumThis is used to determine the TIGERs hardware serial number.
Although it is defined as a writable variable, TIGER may silently
discard that information. If the serial number given does not match
the actual number, an error message may be shown.rw INTEGER .1.3.6.1.4.1.1978.2.1.2.12 |
tigDomainNameThe domain name that this TIGER belongs to.
This value must contain a leading and trailing dot.
(You do not need to enter these when using the Tiger
Configuration Tool. It will automatically add them.)
To create the FQDN, concatenate sysName with this value.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.2.13 |
buffers OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.3 |
tigPoolNumEntriesThe number of:
WRITE: buffer pools I want to create,
READ: buffers that can be created.ro INTEGER .1.3.6.1.4.1.1978.2.1.3.1 |
tigPoolTableAn entry shall be placed in the storage table for
each buffer pool.
This table is intended to be a useful diagnostic
and performance monitoring tool for `out of memory'
and `out of buffers' types of failures and tracking. SEQUENCE OF TigPoolEntry .1.3.6.1.4.1.1978.2.1.3.2 |
tigPoolEntryA (conceptual) entry for one logical storage area on the host. TigPoolEntry .1.3.6.1.4.1.1978.2.1.3.2.1 |
tigPoolIndexA unique value for each buffer pool contained by the host.
It is the MQX pool number.rw INTEGER .1.3.6.1.4.1.1978.2.1.3.2.1.1 |
tigPoolSizeThe number of buffers in this pool.rw INTEGER .1.3.6.1.4.1.1978.2.1.3.2.1.2 |
tigPoolBufSizeThe size of each buffer in bytes.rw INTEGER .1.3.6.1.4.1.1978.2.1.3.2.1.3 |
tigPoolLowThresholdIf the number of free buffers remaining in the pool
drops below the low water mark (threshold) as a percentage,
a trap may be generated if enabled.
default: 20%
UNITS: percentrw INTEGER .1.3.6.1.4.1.1978.2.1.3.2.1.4 |
tigPoolHighThresholdIf the Low threshold has been reached, this defines
the number of buffers that must be free in the pool
in order to turn off the alarm.
A trap may be generated if enabled.
default: 50%
UNITS: percentrw INTEGER .1.3.6.1.4.1.1978.2.1.3.2.1.5 |
tigPoolFreeThe number of free buffers in this pool.ro INTEGER .1.3.6.1.4.1.1978.2.1.3.2.1.6 |
tigPoolCommandStatusWhen written with a 'create' it causes the pool
as defined by the other parameters to be created.
As a result, of pool creation, this variable, when
read will inform the management system whether the
poll was successfuly 'created' or if the create 'failed'.rw Enumeration .1.3.6.1.4.1.1978.2.1.3.2.1.7 |
tigPoolAllocationFailuresThe number of requests for buffers from this pool that could
not be honored due to insufficient buffers. It should be noted
that as this object has a SYNTAX of Counter, that it does not
have a defined initial value. However, it is recommended that
this object be initialized to zero.ro Counter .1.3.6.1.4.1.1978.2.1.3.2.1.8 |
tigPoolTrapControlThis option allows a tigPool trap to be sent when:
a) the number of buffers remaining in the pool falls
below the low water mark.
b) when the number of buffers remaining in the pool exceeds
the high water mark (only after having fallen below the
low water mark).rw Enumeration .1.3.6.1.4.1.1978.2.1.3.2.1.9 |
tigPoolTrapStatusInforms the NMS of the reason for the tigPool trap that was received.
When read asynchronously, it also indicates the last known state of this pool entry.ro Enumeration .1.3.6.1.4.1.1978.2.1.3.2.1.10 |
generalTraps OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.4 |
tigPoolAn tigPool trap signifies that the number of buffers
remaining in a pool has crossed either the high or low threshold
as defined by: tigPoolLowThreshold and tigPoolHighThreshold.
The trap returns:
1/ Index of the pool that changed state,
2/ That pools current status: alarm or recovery,
3/ That pools current number of buffers
The 'number of buffers' parameter is really only marginally
useful during the 'alarm' state. TRAP-TYPE .1.3.6.1.4.1.1978.2.1.4.0.1 |
tigRestartAn tigRestartTrap signifies that the Tiger has recently
restarted for the reason given by 'tigRestartReason' at the
(local) time 'tigSystemDate'. TRAP-TYPE .1.3.6.1.4.1.1978.2.1.4.0.2 |
tigIdleAn tigIdle trap signifies that the Tiger has recently
changed idle state to/from idling, alarm with the current
state given by 'tigCpuIdleState'.
It can only be generated if 'tigCpuTrapControl' is enabled. TRAP-TYPE .1.3.6.1.4.1.1978.2.1.4.0.3 |
autif OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.5 |
autifNumEntriesThe number of entries in the table.ro INTEGER .1.3.6.1.4.1.1978.2.1.5.1 |
autifTableAn entry is be placed in the table for each address mapping. SEQUENCE OF AutifEntry .1.3.6.1.4.1.1978.2.1.5.2 |
autifEntryA (conceptual) entry for each address pairing between
a Tiger user stream and a TCP or UDP socket/address pair.
An autifEntry may support a client, a listener or both
depending on the service configured. AutifEntry .1.3.6.1.4.1.1978.2.1.5.2.1 |
autifIndexA unique value for each address entry.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.1 |
autifServiceSpecifies the type of connection required for this address set.
'udp' implies:
- UDP client
- Northrop Grumman's proprietary data encapsulation format
for message delimiting, using a SYN octet (16h) followed
by 2 octets of user data length (big endian), followed by user data:
SYN(1) len(2) user data(n)
'tcp' implies:
- TCP client
- Northrop Grumman's proprietary data encapsulation format
for message delimiting, using a SYN octet (16h) followed
by 2 octets of user data length (big endian), followed by user data:
SYN(1) len(2) user data(n)
'system-1' implies:
- UDP
- each autif socket is mapped to a (specified) IA
- each IA/socket carries an alias source IP address
- port numbering:
- host destination port = base = remote port
- source port = base + TA (converted TA)
- encapsulation format:
ip header (dstip = autifRemAddress, srcip = autifAliasAddress)
udp header (dstport = autifRemotePort, srcport = autifRemotePort + ta)
alc data (no header, ends with EOMx)
'continental' implies:
- UDP client
- each autif socket is mapped to a (specified) IA
- each IA/socket carries an alias source IP address
- port numbering:
- host destination port = base = remote port
- source port = base + ta (converted TA)
- encapsulation format:
ip header (dstip = autifRemAddress, srcip = autifAliasAddress)
udp header (dstport = autifRemotePort, srcport = autifRemotePort + ta)
header (autifLNIA(2) ta)
alc data (ends with EOMx)
'dlsw' implies:
- TCP dlsw client(2065) + TCP dlsw listener(2065)
- 1 or 2 TCP sockets supporting the flow of DLSw traffic with the defined
peer (autifRemAddress).
- autifAliasAddress defines this DLSw peer source ip address.
- Uses RFC1795 defined message encapsulation format.
- TIGER always initiates the connection
'listener' implies:
- TCP listener
- creates a socket with autifLocalPort defining the 'well known port'
for the listener.
- A conditional accept is done on all incoming connect requests
to verify the remote address. If autifRemAddress is defined as:
0.0.0.0 - a call from any source address is accepted,
'non-zero' - only a call from the specified address is accepted.
- Northrop Grumman's proprietary data encapsulation format
for message delimiting, using a SYN octet (16h) followed
by 2 octets of user data length (big endian), followed by user data:
SYN(1) len(2) user data(n).
'matip' implies:
- TCP Client/Server depending upon the Mode of the MATIP module
- MATIP header contains 4 bytes. The first is version field and is used as
as MATIP sync. The 2nd is ignored by AUTIF. The 3rd and 4th is the length
of this TCP message.
'ofep-sabre' implies:
- TCP Client process for SABRE OFEP Encapsulation/Protocol.
- the Load Balancer header is 3 long (a version field and a 2 byte length)
- the OFEP header is 4 bytes long (a version field, 2 byte length and a
control field.
'ofep-sabre-listener' implies:
- TCP Listener process for SABRE OFEP Encapsulation/Protocol
- used ONLY for testing purposes.
- the Load Balancer header is 3 long (a version field and a 2 byte length)
- the OFEP header is 4 bytes long (a version field, 2 byte length and a
control field.rw Enumeration .1.3.6.1.4.1.1978.2.1.5.2.1.2 |
autifRemAddressThe IP address signifying the destination device used for this entry.
client operation - it defines the destination host.
listener operation -
0.0.0.0 - a call from any source address is accepted,
'non-zero' - only a call from the specified address is accepted.rw IpAddress .1.3.6.1.4.1.1978.2.1.5.2.1.3 |
autifLocalPortThe local port number for this connection. This field has no meaning
for a TCP client since the source port is dynamically assigned. For a
TCP listener it specifies the 'well-known port' for the particular
application/streams that is attached.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.4 |
autifRemotePortThe remote port number for this connection.
client - this is the 'well-known port' of the application.
When used with an OFEP mode, this is the port of the load balancer.
TCP listener - no meaning.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.5 |
autifRxBufSizeThe size of the socket receive buffer represented by
this entry in bytes. For UDP sockets it must be as large as
the largest message to be received, because UDP delivers in
a single recv() operation. For TCP sockets it may be configured
to be less than the maximum message size, and the autif recieve
application will reassemble in Tiger buffers.
For TCP = autifTypeAMaxMsgSize / 2
For UDP = autifTypeAMaxMsgSize
UNITS: bytesrw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.6 |
autifTxBufSizeThe size of the transmit buffer represented by this entry in bytes.
For UDP sockets it must be as large as the largest message to be
transmitted, because UDP expects to deliver in a single send()
operation. For TCP sockets it may be configured to be less than the
maximum message size, and the autif transmit application will
coordinate multiple send() operations from the Tiger buffers.
For TCP = autifTypeAMaxMsgSize / 2
For UDP = autifTypeAMaxMsgSize
UNITS: bytesrw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.7 |
autifSockQueueSizeThe size of the socket receive queue represented by this entry
in buffers. For TCP this reflects flow control responsiveness in
outbound traffic (streams to socket to Host).
UNITS: buffersrw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.8 |
autifTypeAQueueSizeThe size of the Type A message user stream queue size represented
by this entry in buffers. For TCP, this reflects flow control
responsiveness for inbound traffic (Host to socket to streams).
UNITS: buffersrw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.9 |
autifTypeAMaxMsgSizeThe maximum size of the message expected to flow between the
sockets and streams interfaces.
UNITS: bytesrw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.10 |
autifInOctetsThe total number of octets received from the streams interface,
destined to the socket/Host, including header characters.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.11 |
autifInUcastPktsThe number of subnetwork-unicast packets received from the streams
interface, destined to the socket/Host TCP/UDP higher-layer protocol.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.12 |
autifInNUcastPktsThe number of non-unicast (i.e., subnetwork- broadcast or
subnetwork-multicast) packets received from the streams interface,
destined to the socket/Host higher-layer protocol.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.13 |
autifInDiscardsThe number of packets received from the streams interface,
destined to the socket/Host which were flused from queues and
discarded because the socket went down, and the traffic was not
deliverable.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.14 |
autifInErrorsThe number of inbound packets received from the streams interface,
destined to the socket/Host that could not be sent due to errors
in socket transmision, or instance routing faults.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.15 |
autifInUnknownProtosThe number of packets received via the interface which were
discarded because of an unknown or unsupported protocol. Currently
not supported in Tiger.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.16 |
autifOutOctetsThe total number of octets from the Host/sockets interface,
destined to the concerned user stream, including header characters.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.17 |
autifOutUcastPktsThe total number of packets from the Host/sockets interface,
destined to the concerned user stream.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.18 |
autifOutNUcastPktsThe total number of packets from the Host/sockets
interface, destined to the concerned user stream.
(i.e., a subnetwork-broadcast or subnetwork-multicast) address.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.19 |
autifOutDiscardsThe number of outbound packets from the Host/sockets interface,
destined to the concerned user stream which could not be delivered
for various error reasons, such as insufficient buffers, queuing
errors, etc.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.20 |
autifOutErrorsThe number of outbound packets from the Host/sockets interface,
destined to the concerned user stream that could not be transmitted
because of errors.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.21 |
autifIAThis is the IA value associated with this connection. Note that the Configurator
will automatically establish this value when an ALC user stream is linked to
the autif instance. (The Configurator displays this value in the more human form
of hex whereas it is provided here to the Tiger as correspondance code). In system-1 mode,
Tiger will strip it from the data message on transmit, and add it (in correpsondance code)
on reception prior to passing into the stream.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.5.2.1.22 |
autifAliasAddressThis is another IP address to which the Tiger will respond and associate with
this autif entry (on this socket). When the socket is in use with the DLSw
service this IP address should be the IP address of the network peer that
supports this service.
Used when autifService = tcp, udp, system-1, continental, dlsw.rw IpAddress .1.3.6.1.4.1.1978.2.1.5.2.1.23 |
autifSockPrecedenceSpecifies the precedence that IP traffic on this socket will
be transmitted with. These values define the upper 3 bits of
the Type Of Service byte in the IP header.rw Enumeration .1.3.6.1.4.1.1978.2.1.5.2.1.24 |
autifDestAddrTypeThis object controls whether or not the destination address
is present in the outgoing data stream from a Type A user to
the IP interface logic. It is only applicable for UDP type
services (see autifService).
To handle alternate access operation, the Destination address
can be inserted by the alternate access module (see altaHostSupplementalAddr).
'none' - no additional address information is present, and the message
is sent to the sockets default destination IP address.
'ip' - this indicates that the first 4 bytes of the data stream holds the
IP address of the destination host. For a UDP style socket this
address is used in the applications sendto() call.
If the address is all zeros, then the message will be sent to the
sockets default destination IP address defined in autifRemAddress.
On messages sourced from the IP layer, the source IP address is
pre-pended to the data stream before it is forwarded to the
alternate access module and multiplexor.rw Enumeration .1.3.6.1.4.1.1978.2.1.5.2.1.25 |
autifSockOptionsControls which socket options are enabled. This integer is actually
a bit field. With all bits off, no options are enabled.
Bit 0 - TCP Keep Alive
Bits 1-n - not currently defined, must be zero.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.26 |
autifLNIAThis parameter represents the line and IA characters for the ALC user
that may be connected to this AUTIF instance. Although the LNIA is an
arbitrary 16 bit hexadecimal quantity, it has various meanings:
Continental Mode:
- the parameter contains the LNIA characters that are substitute internal
values of Line and IA for all socket transmissions to the host. On socket
reception the fields are stripped, and internal values of 'line' and 'IA'
are applied.
OFEP Modes:
- the parameter contains the actual line and IA values for the user
connected to this AUTIF instance.
This parameter is only used when autifService is continental or one of the OFEP modes.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.5.2.1.27 |
autifLBNameThe DNS Name of the Load Balancer.
This variable is only written to if the item 'autifService' is set to either
'ofep-sabre' or 'ofep-sabre-listener'.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.5.2.1.28 |
autifOFEPKeepAliveTimeoutOFEP Keepalive period (in SECONDS). OFEP Keepalive messages are generated
by the OFEP processor ONLY. The Tiger will monitor the time intervals between
OFEP Keepalive messages - this counter is the timeout period that will lead to
recovery action by the Tiger (i.e. the reset of the TCP socket). If the timer
is set to zero (0), then KeepAlive monitoring is disabled.
The KeepAlive monitor is active for all terminal devices associated with this
IA.
This variable is only written to if the item 'autifService' is set to either
'ofep-sabre' or 'ofep-sabre-listener'.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.29 |
autifUserIdleTimeoutThis is the OFEP inactivity timer (in SECONDS). If set, the Tiger will reset
the socket after 'autifUserIdleTimeout' many seconds. A value of zero (0) means
that the socket is never timed out.
This variable is only written to if the item 'autifService' is set to either
'ofep-sabre' or 'ofep-sabre-listener'.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.30 |
autifXlatToSocketThis is an index into the capXlatTable that is used for translating data
received from the stream and being sent to the socket.
Currently only used in OFEP mode.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.31 |
autifXlatFromSocketThis is an index into the capXlatTable that is used for translating data
received from the socket and being sent to the stream.
Currently only used in OFEP mode.rw INTEGER .1.3.6.1.4.1.1978.2.1.5.2.1.32 |
autifRealToVTRoutingErrorsCount of the times we were unable to route from Real to Virtual TAro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.33 |
autifVTToRealRoutingErrorsCount of the times we were unable to route from Virtual TA to Real.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.34 |
autifRealToVTHashDepthCount of the times we encountered maximum hash depth encountered in
this direction.ro Counter .1.3.6.1.4.1.1978.2.1.5.2.1.35 |
apath OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.6 |
apathNumEntriesNumber of type A paths in the table.ro NonNegativeInteger .1.3.6.1.4.1.1978.2.1.6.1 |
apathTableA list of Apath table entries. The number of entries
is given by the value of apathNumEntries. SEQUENCE OF ApathEntry .1.3.6.1.4.1.1978.2.1.6.2 |
apathEntryAn entry containing information applicable to a
particular type A path. ApathEntry .1.3.6.1.4.1.1978.2.1.6.2.1 |
apathIndexA unique value for each Apath entry.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.2.1.1 |
apathTypeDefines the mode of operation for this Apath:
Primary: We send enquiry messages.
Secondary: We respond to enquiry messages.
Primary-Mute: We won't send enquiry messages.
The path is up on on the basis of the connected stream.
Primary-Mute-Xlat: Same as Primary-Mute except it enables SABRE/PIA
character set translation.rw Enumeration .1.3.6.1.4.1.1978.2.1.6.2.1.2 |
apathIdleTimerMax(1..1000 seconds) default=30 (Primary)
Timeout to send an enquiry message when no data received.
default=39 (Secondary)
Timeout to declare the Apath down when nothing received.
UNITS=secondsrw INTEGER .1.3.6.1.4.1.1978.2.1.6.2.1.3 |
apathResponseTimerMax(1..100 seconds) default=3 (Primary only)
Timeout to wait for a positive end user response to an enquiry message.
A negative end user response will allow the timeout to occur.
UNITS=secondsrw INTEGER .1.3.6.1.4.1.1978.2.1.6.2.1.4 |
apathRetryCounterMaxdefault=3 (Primary only)
Number of consecutive Response Timeouts to declare the Apath down.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.2.1.5 |
apathEndUserStatusEnabledefault = enabled
Defines whether or not the end user status will be included in the path state.
A user down status will declare Apath down.rw Enumeration .1.3.6.1.4.1.1978.2.1.6.2.1.6 |
apathTrafficIdleTimerdefault=15
A non-zero value indicates amount of time that has to pass with no user traffic
being sent before this path is declared idle. The path will only be re-connected
on user traffic. If the value is zero, then no timming will occur and the path
will never be automatically disconnected.
This is useful for dial-up connections for 'type A' connections, but is useless
for X2X traffic which won't initiate traffic unless the path is already up.
UNITS: secondsrw INTEGER .1.3.6.1.4.1.1978.2.1.6.2.1.7 |
apathConnectTimerMax(1..1000 seconds) default=30
This amount of time is allowed for the underlying connection to take
place, before Apath will begin polling the other end for a path connection.
i.e.
TimeTillDeclaredDead = apathConnectTimerMax + (apathResponseTimerMax * apathRetryCounterMax)
UNITS=secondsrw INTEGER .1.3.6.1.4.1.1978.2.1.6.2.1.8 |
apathPathUpMsgThis message is sent on this stream to the host when the host path status changes to UP.
This option only applies when apathType is set to any of the primary options.
This text is transmitted as entered without any manipulations, translations, headers or trailers.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.6.2.1.9 |
apathUserNumEntriesNumber of type A path users in the table.ro NonNegativeInteger .1.3.6.1.4.1.1978.2.1.6.3 |
apathUserTableA list of User table entries. The number of entries
is given by the value of apathNumUserConfiged. SEQUENCE OF ApathUserEntry .1.3.6.1.4.1.1978.2.1.6.4 |
apathUserEntryAn entry containing information applicable to a particular APATH line. ApathUserEntry .1.3.6.1.4.1.1978.2.1.6.4.1 |
apathUserIndexThe line interface identifier that can be used to locate this user.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.4.1.1 |
apathUserApathOperationdefault = mainPrefered
This defines the switching characteristics of main and alternate paths.
MAIN PREFERED
Re-connect to the main path only.
- continuous retry of main path.
- disconnect the alternate path in use and switch to the main path
when it is known to be UP.
- When the main path fails, then attempt to re-establish the path on
one of the alternate paths in the order Alternate 1, then Alternate
2, then Alternate 3.
SWITCH TO BEST PATH
Connect to the best path.
- continuous retry of the main path and any path that is higher
than the path currently in use.
- disconnect the path ans select the highest priority path that is
known to be UP.
- when a the current path fails, then attempt to re-establish the
path based on the priority order of: main, alternate 1, 2, 3.
AVOID SWITCHING
No automatic switching occurs.
- remain connected with the current path as long as it remains UP.
- when it fails, or is commanded to disconnect, then re-establish
path based on the priority order of: main, alternate 1, 2, 3.rw Enumeration .1.3.6.1.4.1.1978.2.1.6.4.1.2 |
apathUserMainApathIndexThe index into the apath table that specifies the primary trunk path connection.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.4.1.3 |
apathUserAlt1ApathIndexThe index into the apath table that specifies the first alternate trunk path
connection to use if the main path is down.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.4.1.4 |
apathUserAlt2ApathIndexThe index into the apath table that specifies the second alternate trunk
to use if the both the main and alternate 1 path connection is down.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.4.1.5 |
apathUserAlt3ApathIndexThe index into the apath table that specifies the third alternate trunk
to use if the main, alternate 1 AND alternate 2 path connections are down.rw INTEGER .1.3.6.1.4.1.1978.2.1.6.4.1.6 |
apathUserTypeDefines the type of user traffic that is flowing across this Apath connection.
This information is really only used when the Tiger is configured ('apathType')
for an Apath primary or primary-mute mode of operation.
When it is configured for secondary mode. This field must match the type of
user traffic that will be send to it from the remote Tiger.rw Enumeration .1.3.6.1.4.1.1978.2.1.6.4.1.7 |
apathUserDevStatusEnabledefault = 1 (Primary only)
Include the device status in the Apath enquiry message if enabled.rw Enumeration .1.3.6.1.4.1.1978.2.1.6.4.1.10 |
apathUserAuxilliaryInfoThis octet string contains any additional clarification information for this APATH User
stream.
For the IA Diversion function, the first octet contains the Tiger Port number (values
can be 0x01 - 0x04). The second contains the IA (valid numbers are 0x01 - 0x3F). If the IA
Diversion function is not selected, then these values are both zero (i.e. 0x00 0x00);
the remainding octets of the string are available for other functions.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.6.4.1.11 |
svcmsg OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.7 |
svcmsgNumEntriesNumber of service message profiles in the table.ro NonNegativeInteger .1.3.6.1.4.1.1978.2.1.7.1 |
svcmsgTableA list of service message table entries.
The number of entries is given by the value of svcmsgNumEntries. SEQUENCE OF SvcmsgEntry .1.3.6.1.4.1.1978.2.1.7.2 |
svcmsgEntryAn entry containing information applicable to a
particular service message profile. SvcmsgEntry .1.3.6.1.4.1.1978.2.1.7.2.1 |
svcmsgIndexA unique value for each service message profile entry.rw INTEGER .1.3.6.1.4.1.1978.2.1.7.2.1.1 |
svcmsgDescriptionThis is the description field for this table entry.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.2 |
svcmsgNetDownMessage sent when:
All links to the network are down, or the network is not responding,
Or when an ICMP message 'net unreachable' is received.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.3 |
svcmsgNetUpMessage sent when:
The network is available.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.4 |
svcmsgConnectingMessage sent when:
Trying to make a connection with the remote end user.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.5 |
svcmsgConnectedMessage sent when:
Connection with the remote end user has been established.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.6 |
svcmsgIdleMessage sent when:
The network is available, but the local end user has not yet initiated a connection.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.7 |
svcmsgDisconnectingMessage sent when:
The connection is currently in the process of being cleared.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.8 |
svcmsgDisconnectedMessage sent when:
The connection has broken. No reason is associated with the outage.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.9 |
svcmsgDiscRestartMessage sent when:
The connection has broken due to a restart condition being received.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.10 |
svcmsgDiscUserMessage sent when:
The connection has been cleared by local intervention, i.e. console command.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.11 |
svcmsgDiscMgmtMessage sent when:
The connection has been cleared by local network management.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.12 |
svcmsgDiscBusyMessage sent when:
The connection has been cleared by the remote end because it already has
a connection established with another user.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.13 |
svcmsgDiscRPErrMessage sent when:
The connection has been cleared because a protocol error associated with the
remote end has been detected.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.14 |
svcmsgDiscLPErrMessage sent when:
The connection has been cleared because a protocol error associated with the
local end has been detected.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.15 |
svcmsgDiscCongestMessage sent when:
The connection has been cleared because of network congestion.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.16 |
svcmsgDiscNotObMessage sent when:
The connection has been cleared because the address used for the remote
end user is unknown.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.17 |
svcmsgDiscOutOrderMessage sent when:
The connection has been cleared because:
a) the connection cannot be completed,
b) has been cleared,
c) the remote end user is, or becomes unavailable.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.18 |
svcmsgDiscInvFacMessage sent when:
The connection has been cleared because a facility that was
requested was invalid.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.19 |
svcmsgDiscAcsBarMessage sent when:
The connection has been cleared because a the local end user does
not have permission to access the remote end.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.20 |
svcmsgDiscRvsChargeMessage sent when:
The connection has been cleared because the remote end user cannot
accept the reverse charge requested by the local end.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.21 |
svcmsgDiscIncDestMessage sent when:
The connection has been cleared because the remote end user application
is incompatible with the local end.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.22 |
svcmsgDiscNoTrafMessage sent when:
The connection has been cleared because no traffic has been detected over
a specified period of time.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.23 |
svcmsgUpAgainMessage sent when:
A device is detected as having become operable.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.24 |
svcmsgNoRouteMessage sent when:
1/ No route to the host is configured.
2/ There is no alternate host access selected.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.25 |
svcmsgOverLengthMessage sent when:
A message was received by a protocol whose length was greater than
the configured maximum allowable message length.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.26 |
svcmsgCongestionMessage sent when:
There is congestion preventing traffic from reaching the destination.
Typically due to receiving an ICMP 'source quench'.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.27 |
svcmsgHostUnreachMessage sent when:
The host, or host application is unreachable.
Typically when an ICMP message is received that indicates 'host unreachable'
or 'port unreachable'.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.28 |
svcmsgZeroLengthMessage sent when:
There was no data in a message that was received by a protocol.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.7.2.1.29 |
bootp OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.8 |
bootpNumEntriesNumber of bootp command entries in the table.ro NonNegativeInteger .1.3.6.1.4.1.1978.2.1.8.1 |
bootpTableA list of bootp command entries.
The number of entries is given by the value of bootpNumEntries. SEQUENCE OF BootpEntry .1.3.6.1.4.1.1978.2.1.8.2 |
bootpEntryAn entry containing information applicable to a particular bootp action. BootpEntry .1.3.6.1.4.1.1978.2.1.8.2.1 |
bootpIndexA unique value for each bootp command entry.rw INTEGER .1.3.6.1.4.1.1978.2.1.8.2.1.1 |
bootpServerNameAn optional string signifying the name of the server that should respond to the
BOOTP request. If bcastServerName contains a string, only the server that matches
that name/address will answer the request. If bcastServerName is an empty string,
then any BOOTP server that received the request may answer.
This entry is only required for the first entry of the bootp table since subsequent
bootp table entries are only used to perform FTP operations. Any subsequent FTP
transactions will be performed to the 'server IP' address that was found in the
bootp response.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.8.2.1.2 |
bootpUserNamebootpUserName defines the user name used for performing an FTP file transfer.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.8.2.1.3 |
bootpPasswordbootpPassword defines the password used for performing an FTP file transfer.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.8.2.1.4 |
bootpRemoteFileIf bootpRemoteFile is an empty string, the responding server will use its database
entry to inform TIGER of the servers filename to use for this transaction.
If bootpRemoteFile contains a value, the BOOTP server will use that string
to access its configuration database to determine the corresponding file that
will be filled in the BOOTP response to inform TIGER of the servers filename
to use for this transaction.
Normally, the bootp database will contain a entry that defines this name as the
name of the configuration file that should be downloaded first (see bootpLocalFile).rw OCTET STRING .1.3.6.1.4.1.1978.2.1.8.2.1.5 |
bootpLocalFileWhen Tiger's bootp application is performing an FTP transaction, the bootpLocalFile
object contains the destination path and filename for the incoming file.
If this field is empty, the downloaded file will be placed into a filename
created by concatenating '/flash' with the filename (only) from the bootp response.
That response will either contain a value specified in the BOOTP server database
or if none there, then the value of bootpRemoteFile will be used.
When bootpLocalFile is specified it must always contain one of the valid TIGER
filesystems of: '/flash' or '/ramdisk'.
It is assumed that this variable will always be written last when defining a bootpEntry.
When this variable is written, the Bootp (or FTP) transaction will begin.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.8.2.1.6 |
mount OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.9 |
mountNumEntriesNumber of filesystem entries in the table.ro NonNegativeInteger .1.3.6.1.4.1.1978.2.1.9.1 |
mountTableA list of filesystem entries.
The number of entries is given by the value of mountNumEntries. SEQUENCE OF MountEntry .1.3.6.1.4.1.1978.2.1.9.2 |
mountEntryAn entry containing information applicable to a particular mount point. MountEntry .1.3.6.1.4.1.1978.2.1.9.2.1 |
mountIndexmountIndex is a unique value for each mount table entry.rw INTEGER .1.3.6.1.4.1.1978.2.1.9.2.1.1 |
mountRemotePathThe mountRemotePath variable is a string defines the filesystem
mount point on the remote machine. It will typically be of the form:
//fulko/u/here/thererw OCTET STRING .1.3.6.1.4.1.1978.2.1.9.2.1.2 |
mountLocalPathThe mountLocalPath variable is a string defines the filesystem
mount point on the local machine. It will typically be of the form:
/mnt/thisdirrw OCTET STRING .1.3.6.1.4.1.1978.2.1.9.2.1.3 |
mountModemountMode defines how the remote file system has been mounted on the local machine.
A remote file system can either be mounted as read-only or as read-write.
This overides any permission that may be granted by the remote machine.rw Enumeration .1.3.6.1.4.1.1978.2.1.9.2.1.4 |
mountRemoteInfomountRemoteInfo returns both the connection status of this entry with respect to
the remote machine, as well as the access rights that the remote file system
allows. This value is actually a bit field, where:
the first two bits represent the read and write permissions respectively,
the next bit represents the connection status: 0 = not connected, 1 = connected.ro Enumeration .1.3.6.1.4.1.1978.2.1.9.2.1.5 |
dnsRes OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.10 |
dnsResLocalResolvesThe count of the number of times that a cached entry resolved the request.ro Counter .1.3.6.1.4.1.1978.2.1.10.1 |
dnsResCacheFullThe number of occurences when DNS responses were not cached because the cache was full.ro Counter .1.3.6.1.4.1.1978.2.1.10.2 |
dnsResQueueFullThe number of occurences when DNS responses were not cached because the cache
queue was full.ro Counter .1.3.6.1.4.1.1978.2.1.10.3 |
dnsResClearCacheWhen set to reset(2), any persistant resolver state (such as a process)
is reinitialized as if the resolver had just been started, and the cache is
initialized. When read this variable will always return other(1).rw Enumeration .1.3.6.1.4.1.1978.2.1.10.4 |
dnsResConfigMaxCnamesLimit on how many CNAMEs the resolver should allow
before deciding that there's a CNAME loop. Zero means
that resolver has no explicit CNAME limit.rw INTEGER .1.3.6.1.4.1.1978.2.1.10.5 |
dnsResNumHostsNumber of DNS host entries.ro NonNegativeInteger .1.3.6.1.4.1.1978.2.1.10.6 |
dnsResTableA list of DNS host entries.
The number of entries is given by the value of dnsResNumEntries. SEQUENCE OF DnsResEntry .1.3.6.1.4.1.1978.2.1.10.7 |
dnsResEntryAn entry containing information applicable to a particular dns point. DnsResEntry .1.3.6.1.4.1.1978.2.1.10.7.1 |
dnsResServerIPThe IP address associated with this DNS host.rw IpAddress .1.3.6.1.4.1.1978.2.1.10.7.1.1 |
dnsResServerNameThe fully qualified domain name of this DNS host.ro OCTET STRING .1.3.6.1.4.1.1978.2.1.10.7.1.2 |
dnsResQueriesSentThe total count of DNS requests made by this Tiger of this DNS host.ro Counter .1.3.6.1.4.1.1978.2.1.10.7.1.3 |
dnsResSendErrorsro Counter .1.3.6.1.4.1.1978.2.1.10.7.1.4 |
dnsResGoodResponsesThe number of valid responses received from the requested DNS.ro Counter .1.3.6.1.4.1.1978.2.1.10.7.1.5 |
dnsResTimeoutsThe number of occurences when this DNS host did not respond.ro Counter .1.3.6.1.4.1.1978.2.1.10.7.1.6 |
dnsResBadResponsesThe number of occurences when this DNS host responded incorrectly.ro Counter .1.3.6.1.4.1.1978.2.1.10.7.1.7 |
dnsResCmdThe dnsResCmd can be set to delete to remove this row from the table.
If you need to change the IP address of a host in the DNS table, you
must create a new entry corresponding to the new host, and then use
this field on the old host entry that should be removed.rw Enumeration .1.3.6.1.4.1.1978.2.1.10.7.1.8 |
dnsResCacheNumEntriesNumber of entries in the Tiger's DNS Cache.
This is currently not a dynamically sized table, but has a finite
length of 16 entries.ro INTEGER (1 .. 16) .1.3.6.1.4.1.1978.2.1.10.8 |
dnsResCacheTableA list of DNS Cache entries.
The number of entries is given by the value of dnsResNumEntries. SEQUENCE OF DnsResCacheEntry .1.3.6.1.4.1.1978.2.1.10.9 |
dnsResCacheEntryAn entry containing information applicable to a particular dns point. DnsResCacheEntry .1.3.6.1.4.1.1978.2.1.10.9.1 |
dnsResCacheHostNameThe fully quailfied domain name (FQDN) of the host contained in this entry.ro OCTET STRING .1.3.6.1.4.1.1978.2.1.10.9.1.1 |
dnsResCacheIpAddressThe IP address associated with the host contained in this entry.ro IpAddress .1.3.6.1.4.1.1978.2.1.10.9.1.2 |
dnsResCacheRRTTLTime-To-Live of RR in this cache entry. This is the initial
TTL value which was received with the RR when it was
originally received.ro Gauge32 .1.3.6.1.4.1.1978.2.1.10.9.1.3 |
dnsResCacheRRElapsedTTLElapsed seconds since RR was received.ro Gauge32 .1.3.6.1.4.1.1978.2.1.10.9.1.4 |
dnsResCacheRRSourceHost from which RR was received, 0.0.0.0 if unknown.ro IpAddress .1.3.6.1.4.1.1978.2.1.10.9.1.5 |
vt OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.1.11 |
vtTableThis is table associated with each Terminal Device configured on the Tiger
to be used in the SABRE OFEP network. SEQUENCE OF VtEntry .1.3.6.1.4.1.1978.2.1.11.1 |
vtEntryEach row represents the configuration characteristics, status and statistics
of each defined terminal/printer. VtEntry .1.3.6.1.4.1.1978.2.1.11.1.1 |
vtAutifIndexA copy of the AUTIF table index.rw INTEGER .1.3.6.1.4.1.1978.2.1.11.1.1.1 |
vtRealLnIaTaThe actual LNIATA associated with this ALC device.
When an AUTIF needs to reference this information, it will
use only the first two bytes of this value for matching.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.11.1.1.2 |
vtLnIaTaThe LNIATA associated with this ALC Device.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.11.1.1.3 |
vtOptionsDODSelection for Dial On Demand (DOD). If 'connect-always' is selected, then
the session starts immediately. If 'connect-on-data' is selected, then
the session is started only when data is received from the ALC device.rw Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.4 |
vtOptionsPrinterSelection of the ALC Device type. If the device is a printer, then OFEP and
Load Balancer Service Messages will not be forwarded to it. 'Free' indicates
that the entry is part of a pool of addresses that can be dynamically allocated.rw Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.5 |
vtOptionsClassThis variable determines whether we request service from the OFEP Load Balancer
by LNIATA or Class.
When handled by LNIATA, the 3 byte LNIATA value is known at configuration.
When handled by Class, the 3 byte LNIATA is provided to the Tiger by the
Load Balancer as part of a Pooling mechanism.rw Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.6 |
vtCommandSNMP command trigger to activate or deactivate this LNIATA.rw Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.7 |
vtClassNameThe name of the class or host service that this virtual
terminal will request.rw OCTET STRING .1.3.6.1.4.1.1978.2.1.11.1.1.8 |
vtStateThis variable represents the State of this ALC device. The variable is defined
as follows:
vts-init : init vt instance
vts-dod-wait : dial on demand - wait for user enq
vts-con-lb : connect to Load Balancer
vts-lb-dialog : negotiate with LB
vts-lb-config : analyze config, and establish
vts-gen-fail : general failure - send svc msg, close, clean up
vts-con-ofep : connect to OFEP
vts-ofep-dialog : negotiate with OFEP
vts-ofep-config : accept OFEP config and establish
vts-ofep-up : OFEP data transfer state
vts-ofep-shutdown : OFEP shutdown procedurero Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.9 |
vtFailReasonThis variable represents the last known failure reason code. The
variable is defined as follows:
vte-err-gen : general failure - no resources, etc
vte-err-sock-down : socket connection failure
vte-err-timeout : timeout expired
vte-err-ka-timeout : keep alive timer expired
vte-err-lb : trouble with load balancer
vte-err-ofep : trouble with OFEP
vte-err-idle-timeout : user idle timeout
vte-deactivate : deactivate command disabled this entry
vte-cap-off : IA stream CAP state change - path switchro Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.10 |
vtFailStringThe last received failure message from either
the Load Balancer or the OFEP.ro OCTET STRING .1.3.6.1.4.1.1978.2.1.11.1.1.11 |
vtLBTokenThe received token for this OFEP session.
This is provided by the Load Balancerro OCTET STRING .1.3.6.1.4.1.1978.2.1.11.1.1.12 |
vtCommandStatusResult of the SNMP 'vtCommand'.ro Enumeration .1.3.6.1.4.1.1978.2.1.11.1.1.13 |
vtLBRequestsThe number of request service packets sent to Load Balancer.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.14 |
vtLBErrorResponsesThe number of bad responses from Load Balancer.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.15 |
vtLBTimeoutsThe number of timeout errors with Load Balancer.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.16 |
vtOFEPRequestsThe number of config/startup packets sent to OFEP.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.17 |
vtOFEPErrorResponsesThe number of error responses from OFEP.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.18 |
vtOFEPTimeoutsThe number of timeout errors with OFEP.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.19 |
vtOFEPKeepAliveTimeoutsThe number of keep alive timeout errors with OFEP.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.20 |
vtOFEPReassemblyFailuresThe number of bad or incomplete message reassemblies.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.21 |
vtOFEPUserEnquiriesThe number of number of user enquiries sent to OFEP.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.22 |
vtOFEPUserResponsesThe number of number of user responses received from OFEP.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.23 |
vtOFEPUserInDiscardsThe number of number of user enquiries discarded.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.24 |
vtOFEPUserOutDiscardsThe number of number of user responses discarded.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.25 |
vtOFEPKeepAlivesThe number of user OFEP KeepAlive messages received.ro Counter .1.3.6.1.4.1.1978.2.1.11.1.1.26 |