NETLINK-SPECIFIC-MIB: View SNMP OID List / Download MIB

This value is the poll address of the secondary link station for this SDLC link. It uniquely identifies the SDLC link station within a single SDLC port.

Maximum number of neighbor nodes. This value is currently always 64 for FRX8000 and 20 for an N7400 or 7500. A neighbor is the closest node in a path from the local node.

This nodes number. (1-250)

A table showing all nodes known to this node along with status and neighbor information.

Each entry of the node table is indexed by node number.

The node number of the desired node. This is the index into the node table.

The operational status of the node. The status is given as: 1 = Node is defined in the database; 9 = Node is operational;

Current number of neighbor nodes to this node.

The neighbor table lists the status of a nodes neighbors.

The table entries are indexed by the node number and the neighbors node number.

The node number of the node whose neighbor's status is being sought.

The node number of the neighbor whose status is being sought.

The status of the neighbor node given as: 1 = previously, but not currently, connected; 2 = Currently connected; Enumeration: 'notConnected': 1, 'connected': 2.

Describes the unit model Enumeration: 'frx4000': 6, 'rackmount': 3, 'highavail': 4, 'model2': 2, 'model1': 1, 'netfrad': 5, 'ss1800': 7.

Text of the last alarm generated

A table used to define the IP address of end-nodes to receive alarms generated by this node. Up to 16 addresses can be specified.

A Trap entry containing objects relating to SNMP traps.

The index into the trap configuration table

The IP Address of the end-station to send alarms

Defines the state of this entry as: 0 = Do not send traps to the Address; 1 = Send traps to the Address; 2 = This Address entry is deleted from the table; Enumeration: 'disableTraps': 1, 'enableTraps': 2, 'delete': 3.

Lowest severity level traps that will be sent to this Address; 1 is the highest, 4 is the lowest. Enumeration: 'major': 2, 'critical': 1, 'informational': 4, 'minor': 3.

Maximum number of protocols allowed on each RLP. This value is currently 11 for FRX4000s, 9 for FRX6000s, and 5 for FRX7000s and FRX8000s.

A Table to describe each RLP on the node

An RLP entry containing objects relating to RLPs.

The RLP number on the node

The current state of this RLP Enumeration: 'power-off': 9, 'loading': 4, 'failed': 7, 'operational': 8, 'configured': 2, 'power-on': 10, 'ipl-failed': 5, 'load-failed': 3, 'ipl-in-progress': 6, 'installed': 1.

The amount of memory installed on this RLP

The Type of Line Interface card in the first position Enumeration: 'none': 1, 'voice': 13, 'v35': 4, 'e1': 11, 'hs-rs232': 5, 't1': 10, 'rs449': 7, 'rs232': 2, 'x21': 6, 'universal': 8, 'rs422': 3.

The Type of Line Interface card in the second position Enumeration: 'none': 1, 'voice': 13, 'v35': 4, 'e1': 11, 'hs-rs232': 5, 't1': 10, 'rs449': 7, 'rs232': 2, 'x21': 6, 'universal': 8, 'rs422': 3.

The protocols configured on this RLP. This is an OCTET STRING where each octet represents a protocol type. The size of this is the maximum number of protocols allowed on an RLP (rlpMaxProtos). The protocol types are defined as: 00 = none 01 = X.25 02 = Frame Relay 03 = Async 04 = SDLC 05 = BSC Interactive 07 = IP 08 = SNMP 09 = RIP 0A = LLC2 0B = Trunk 0C = IPX 0D = Config 0E = LLC2-R 0F = IP-R 10 = NVSP 11 = Bridge

The group to which this RLP belongs- always 1 if not FRX7000.

The responsibility of this RLP within its group, always primary if not FRX7000. Enumeration: 'primary': 1, 'secondary': 2.

This table contains Netlink Enterprise specific objects to manage an X25 port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. Most of the objects in this read-write table have corresponding read-only objects in the portX25OperTable that return the current operating value. The operating values may be different from these configured values if a configured parameter was configured after the interface was started.

A list of configured values for an X25 port.

Physical port interface connector type. Enumeration: 'rs530': 7, 'v35': 5, 'e1': 11, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

This object defines the speed of the X25 port. The speed may only be set to one of a series of reasonable values, and if an attempt is made to set the speed to a value which is within the valid range but not equal to one of these values, the speed will be rounded up. If the connector type of the port is RS232, the port could be a standard port or a high speed port. If the port is a high speed RS232 port, the maximum valid speed is 256000. If the port is a standard RS232 port, the maximum valid speed is 64000 on the FRX4000/SS1840 and 19200 on all other products. It may be possible to set the speed of a standard RS232 port to a speed which is valid for a high speed RS232 port but invalid for a standard RS232 port. In this case, the port may not end up having the invalid speed. The default speed for a standard RS232 port on the FRX6000 is 19200.

Specifies whether the port will generate the clock necessary to synchronize traffic over the link. Enumeration: 'yes': 2, 'no': 1.

This object defines whether the receive clock will be used from the DTE. Enumeration: 'yes': 2, 'no': 1.

This flag indicates whether the port is connected to a dial modem, and whethter connections will be initiated through dial-in or dial-out calls. Enumeration: 'dialIn': 2, 'none': 1, 'dialOut': 3.

This timer defines in minutes, the period of inactivity allowed between calls. Once the timer expires, the port is disabled untill the next call is placed, if a Dial out port, or the Disconnect Timer expires, if a Dial in port. This variable is only meaningful if the port is a Dial port.

This timer defines, in seconds, the length of time a dial-in port will remain disabled after expiration of the InActivity Timer.

This timer determines the length of time, in seconds, that a response must be received by the port, after entering the Linkup state. If a response is not received, the port enters a Failed state.

This flag, when set, indicates the port is associated with a network trunk group. It will be disabled/enabled if the network trunk is not operational. Enumeration: 'yes': 2, 'no': 1.

This variable contains a string of 8 bytes, with each byte indicating 8 ports on an RLP that may be a part of a trunk group. Since a TurboFrad has only 1 RLP, only the first byte is valid if the node is an FRX4000. Each port is represented by a single bit within the RLP byte. The bit position represents the port number...for example, if port 2 on RLP 0 was in a trunk group, the first byte of the string would contain x04 and all other bytes would be 0.

This variable is used to manage the creation and deletion of conceptual rows in the portPhyX25AdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device, and which is supplied by a management station wishing to exercise an on-line update of the existing conceptual row. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

This table contains Netlink Enterprise specific objects to manage an X25 port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. All of the objects in this table are read-only. The operating values may be different from these configured values if a configured parameter was configured after the interface was started.

A list of configured values for an X25 port.

Physical port interface connector type. Enumeration: 'rs530': 7, 'v35': 5, 'e1': 11, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

This object defines the speed of the X25 port. The speed may only be set to one of a series of reasonable values, and if an attempt is made to set the speed to a value which is within the valid range but not equal to one of these values, the speed will be rounded up. If the connector type of the port is RS232, the port could be a standard port or a high speed port. If the port is a high speed RS232 port, the maximum valid speed is 256000. If the port is a standard RS232 port, the maximum valid speed is 64000 on the FRX4000/SS1840 and 19200 on all other products. It may be possible to set the speed of a standard RS232 port to a speed which is valid for a high speed RS232 port but invalid for a standard RS232 port. In this case, the port may not end up having the invalid speed. The default speed for a standard RS232 port on the FRX6000 is 19200.

Specifies whether the port will generate the clock necessary to synchronize traffic over the link. Enumeration: 'yes': 2, 'no': 1.

This object defines whether the receive clock will be used from the DTE. Enumeration: 'yes': 2, 'no': 1.

This flag indicates whether the port is connected to a dial modem, and whethter connections will be initiated through dial-in or dial-out calls. Enumeration: 'dialIn': 2, 'none': 1, 'dialOut': 3.

This timer defines in minutes, the period of inactivity allowed between calls. Once the timer expires, the port is disabled untill the next call is placed, if a Dial out port, or the Disconnect Timer expires, if a Dial in port. This variable is only meaningful if the port is a Dial port.

This timer defines, in seconds, the length of time a dial-in port will remain disabled after expiration of the InActivity Timer.

This timer determines the length of time, in seconds, that a response must be received by the port, after entering the Linkup state. If a response is not received, the port enters a Failed state.

This flag, when set, indicates the port is associated with a network trunk group. It will be disabled/enabled if the network trunk is not operational. Enumeration: 'yes': 2, 'no': 1.

This variable contains a string of 8 bytes, with each byte indicating a port on this RLP that may be a part of a trunk group.

This table contains Netlink Enterprise specific objects to manage an X25 Logical port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. The operating values may be different from these configured values if a configured parameter was configured after the interface was started.

A list of configured values for an X25 logical port.

The DLCI number used to identify the entry in the table. The range is 16-991.

This field sets the priority of the connection among others on the physical port. The range is 0 for lowest priority to 9 for the highest priority.

This field indicates the encapsulation method used Enumeration: 'rfc1490': 2, 'annexG': 1.

Assigns this DLCI to one of sixteen groups whose parameters regulate bandwidth usage. A 0 value indicates the DLCI does not use BAGs

This variable is used to manage the creation and deletion of conceptual rows in the portLogicalX25AdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device, and which is supplied by a management station wishing to exercise an on-line update of the existing conceptual row. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

This table contains Netlink Enterprise specific objects to manage an X25 Logical port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. The operating values may be different from these configured values if a configured parameter was configured after the interface was started.

A list of configured values for an X25 port.

The DLCI number used to identify the entry in the table. The range is 16-991.

This field sets the priority of the connection among others on the physical port. The range is 0 for lowest priority to 9 for the highest priority.

This field indicates the encapsulation method used Enumeration: 'rfc1490': 2, 'annexG': 1.

Assigns this DLCI to one of sixteen groups whose parameters regulate bandwidth usage.

This table contains Netlink Enterprise specific objects to manage an X25 port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. Most of the objects in this read-write table have corresponding read-only objects in the portX25OperTable that return the current operating value. The operating values may be different from these configured values if a configured parameter was configured after the interface was started.

A list of configured values for an X25 port.

A flag which when set, means the port should not be enabled after a boot-up of the node. Enumeration: 'yes': 2, 'no': 1.

A flag which if set, permits negotiation of the flow control parameters on a per call basis. If N is selected, the default packet and window sizes will be used. If Y is selected, the packet or window size in a call packet (up to the configured Max Packet Size or Max Window Size) is used. Enumeration: 'yes': 2, 'no': 1.

A flag which ,if set, permists negotiation of the throughput class for either direction of data transmission on a per call basis. If N is selected, the configured Max Throughput Class value is used. If Y, any throughput class in a call packet (up to the Max Thruput Class) is used. Enumeration: 'yes': 2, 'no': 1.

If Y is selected, no calls can be charged to port. Incoming calls from the network with reverse charge specified will be rejected. Outgoing calls will insert reverse charge in the call packet if not already included. Enumeration: 'yes': 2, 'no': 1.

A flag, if set, that authorizes transmission of incoming calls that request the reverse charge facility. If N is selected, and a call requests it, it will not be transmitted. Enumeration: 'yes': 2, 'no': 1.

A flag, if set, that authorizes transmission of incoming calls that request the Fast Select facility. Enumeration: 'yes': 2, 'no': 1.

An X25 facility that prevents transmission of incoming calls to the local DTE. Enumeration: 'yes': 2, 'no': 1.

An X25 facility that prevents transmission of incoming calls to the local DTE. Enumeration: 'yes': 2, 'no': 1.

The maximum data packet size that will be allowed to pass through this port.

This is the size that will be assigned to an incoming call setup packet if the packet does not request a packet size.

This is the maximum number of unacknowledged packets per logical channel that can pass through this port.

This size will be assigned to an incoming call setup packet if the packet doesn't request a window size.

This specifies the default throughput class that will be inserted into a Call Request packet if Thruput Class negotiation is not enabled or if a thruput class is not requested in the call request.

This flag, if set, indicates the port belongs to at least one CUG. Enumeration: 'yes': 2, 'no': 1.

This number is an index into a Closed User Group table which identifies the default Closed User Group for the port.

This flag, when set, indicates whether this port will be allowed to receive calls from outside its CUGs. Enumeration: 'yes': 2, 'no': 1.

This flag, when set, indicates whether this port will be allowed to make calls outside its CUGs. Enumeration: 'yes': 2, 'no': 1.

This table contains Netlink Enterprise specific objects to manage an X25 port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. The objects in this read-only table corresponding read-only objects in the portX25OperTable that return the current operating value. The operating values may be different from these configured values if a configured parameter was configured after the interface was started.

A list of configured values for an X25 port.

A flag which when set, means the port should not be enabled after a boot-up of the node. Enumeration: 'yes': 2, 'no': 1.

A flag which if set, permits negotiation of the flow control parameters on a per call basis. If N is selected, the default packet and window sizes will be used. If Y is selected, the packet or window size in a call packet (up to the configured Max Packet Size or Max Window Size) is used. Enumeration: 'yes': 2, 'no': 1.

A flag which ,if set, permists negotiation of the throughput class for either direction of data transmission on a per call basis. If N is selected, the configured Max Throughput Class value is used. If Y, any throughput class in a call packet (up to the Max Thruput Class) is used. Enumeration: 'yes': 2, 'no': 1.

If Y is selected, no calls can be charged to port. Incoming calls from the network with reverse charge specified will be rejected. Outgoing calls will insert reverse charge in the call packet if not already included. Enumeration: 'yes': 2, 'no': 1.

A flag, if set, that authorizes transmission of incoming calls that request the reverse charge facility. If N is selected, and a call requests it, it will not be transmitted. Enumeration: 'yes': 2, 'no': 1.

A flag, if set, that authorizes transmission of incoming calls that request the Fast Select facility. Enumeration: 'yes': 2, 'no': 1.

An X25 facility that prevents transmission of incoming calls to the local DTE. Enumeration: 'yes': 2, 'no': 1.

An X25 facility that prevents transmission of incoming calls to the local DTE. Enumeration: 'yes': 2, 'no': 1.

The maximum data packet size that will be allowed to pass through this port.

This is the size that will be assigned to an incoming call setup packet if the packet does not request a packet size.

This is the maximum number of unacknowledged packets per logical channel that can pass through this port.

This size will be assigned to an incoming call setup packet if the packet doesn't request a window size.

This specifies the default throughput class that will be inserted into a Call Request packet if Thruput Class negotiation is not enabled or if a thruput class is not requested in the call request.

This flag, if set, indicates the port belongs to at least one CUG. Enumeration: 'yes': 2, 'no': 1.

This number is an index into a Closed User Group table which identifies the default Closed User Group for the port.

This flag, when set, indicates whether this port will be able to receive calls from outside its CUGs. Enumeration: 'yes': 2, 'no': 1.

This flag, when set, indicates whether this port will be able to make calls outside its CUGs. Enumeration: 'yes': 2, 'no': 1.

A list of Frame Relay ports . The number of entries will be the number of Frame Relay ports on the node.

An Frame Relay Port entry containing objects relating to the port that are configurable by the user.

The RLP number of the Frame Relay port. It will be in the range 1-8.

The Port number of the Frame Relay port. It will be in the range 1-8 for a physical port. It will be in the range 9-64 for a Frame Relay logical port.

A flag which when set, means the port should not be enabled after a boot-up of the node. Enumeration: 'yes': 2, 'no': 1.

The maximum number of bytes allowed in an I Frame for this Frame Relay port.

This timer indicates how long the network will wait between Status Enquiry messages before recording an error. It should be greater than or equal to the frDlcmiPollingInterval variable in the RFC1315 Mib.

This is a flag which, when set, enables the enforcement of the Outgoing Rate Control parameters. Enumeration: 'yes': 2, 'no': 1.

This is a flag which, when set, enables whether the bandwidth allocation will be enforced. Enumeration: 'yes': 2, 'no': 1.

This defines the connector type of the Frame Relay port. Enumeration: 'rs530': 7, 'v35': 5, 'e1': 11, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

This defines the port as logical DCE or DTE. Enumeration: 'yes': 2, 'no': 1.

This specifies whether the port will generate the clock necessary to synchronize traffic over the link. Enumeration: 'yes': 2, 'no': 1.

This allows the clock to be looped back from the DTE using the TT (Terminal Timing) signal, which can be helpful on high-speed lines. Enumeration: 'yes': 2, 'no': 1.

This determines whether, and what type of, configurable network management (status enquiries) will be allowed. Enumeration: 'lmi': 2, 'none': 1, 'annexd': 3.

This variable is used to manage the creation and deletion of conceptual rows in the portFrConfigTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device, and which is supplied by a management station wishing to exercise an on-line update of the existing conceptual row. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

This object defines the speed of the Frame Relay port. The speed may only be set to one of a series of reasonable values, and if an attempt is made to set the speed to a value which is within the valid range but not equal to one of these values, the speed will be rounded up. If the connector type of the port is RS232, the port could be a standard port or a high speed port. If the port is a high speed RS232 port, the maximum valid speed is 256000. If the port is a standard RS232 port, the maximum valid speed is 64000 on the FRX4000/SS1840 and 19200 on all other products. It may be possible to set the speed of a standard RS232 port to a speed which is valid for a high speed RS232 port but invalid for a standard RS232 port. In this case, the port may not end up having the invalid speed. The default speed for a standard RS232 port on the FRX6000 is 19200.

This object determines whether all DLCIs on the port will be reserved exclusively as backups for other DLCIs in the same node. If yes is specified for this object, the port will remain disabled until needed for backup. Enumeration: 'yes': 2, 'no': 1.

A list of DLCI's on Frame Relay ports . The number of entries will be the number of DLCIs on all the Frame Relay ports on a node.

An Frame Relay Port DLCI entry relating to the Rate Control Information that is configurable by the user.

The RLP number on which the DLCI is located. The range for this is 1-8.

The port number on which the DLCI is located. The range for this is 1-8 for a physical FR port and 9-64 for a logical FR port.

The DLCI number used to identify the entry in the table. The range is 16-991.

The committed information rate that is supported on the DLCI for incoming data.

The committed information rate that is supported on the DLCI for outgoing data.

The committed burst size is the maximum amount of data to be transmitted under normal conditions within the time period defined by Bc/Cir that is supported on the DLCI for incoming data.

The committed burst size is the maximum amount of data to be transmitted under normal conditions within the time period defined by Bc/Cir that is supported on the DLCI for Outgoing data.

The excess burst size is the maximum amount of incoming data in excess of the committed burst size that the network will try to transfer during the time interval determined by Bc/Cir on this DLCI.

The excess burst size is the maximum amount of incoming data in excess of the committed burst size that the network will try to transfer during the time interval determined by Bc/Cir on this DLCI.

The BECN recovery Count is a method of controlling the rate of return to max traffic flow after it has been reduced due to congestion. The value determines the number of packets received sequentially without BECN set, before increasing the Excess Burst Size by 1/8 of it's configured value.

This field sets the priority of the DLCI among others on the physical port. The range is 0 for lowest priority to 4 for the highest priority.

This variable is used to manage the creation and deletion of conceptual rows in the portDLCIConfigTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned. Also note that deleting a DLCI entry will only remove it from the database file, and it's existence will still be known by the protocol until the node is rebooted.

This object specifies (if configured as any number other than zero) that this is a primary DLCI, and identifies the backup DLCI(s) (in a Frame Relay backup group) that will take over if this DLCI fails. This is applicable only on an initiating node, which is the node that will initiate the switchover to a backup DLCI. At switchover, the initiating node notifies the remote node of the change.

This object specifies whether the DLCI will be used as a non-initiating backup DLCI. The DLCI will wait for a backup protocol message from the initiating end, telling the backup where to send the rest of the messages. Enumeration: 'yes': 2, 'no': 1.

A Table describes the Frame Relay Backup MIB .

This Entry contains the SNMP objects that are used for configurating the Frame Relay Backup.

This RLP number identifies the RLP containing the primary and backup DLCIs.

This Port number is the physical port on which the backup DLCI is being configured.

This DLCI number is the backup being configured.

This Group number is the backup being configured.

This is the time after a primary DLCI failure that the software will wait for this DLCI to become active before checking the next backup DLCI. If the backup does not become active before the timer expires, the software will search the backup group for the next available backup.

This enables or disables the backup protocol on the specified DLCI. It should be set to yes if and only if the remote device is an FRX4000 or FRX6000 with the backup protocol enabled on the remote DLCI connected to this backup group entry. Enumeration: 'yes': 2, 'no': 1.

This variable is used to manage the creation and deletion of conceptual rows in the portFrBackupGroupTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A list of BSC Interactive ports . The number of entries will be the number of BSC Interactive ports on the node.

A BSCI Interactive Port entry containing objects relating to the port that are configurable by the user.

Causes the port to be enabled or disabled at node IPL. Enumeration: 'disabled': 1, 'enabled': 2.

Physical port interface connector type. Enumeration: 'rs530': 7, 'v35': 5, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

Data transmission rate in bits per second.

Length of time before the node will transmit an I-frame if the previous transmission is not acknowledged.

Maximum number of times the node will attempt to send an I-frame after a retransmission period expiration.

Maximum frame size that will be transmitted on the port.

Specifies whether the port will generate the clock necessary to synchronize traffic over the link. Enumeration: 'yes': 2, 'no': 1.

Allows the clock to be looped back from the DTE using the TT (Terminal Timing) signal. Enumeration: 'yes': 2, 'no': 1.

BSCI Pad Type Enumeration: 'hpad': 2, 'tpad': 1.

Specifies whether all devices on a line use the same character set for successive session polls. Enumeration: 'yes': 2, 'no': 1.

Specifies whether the user will have the option of including call information in a call request packet. Enumeration: 'yes': 2, 'no': 1.

Causes the virtual circuit to be cleared when no terminals are using it. Enumeration: 'yes': 2, 'no': 1.

Causes all characters transmitted to be treated as data. Enumeration: 'yes': 2, 'no': 1.

Allows management of acknowledgments end to end across the network rather than locally at each end. Enumeration: 'yes': 2, 'no': 1.

Specifies full-duplex transmission. Enumeration: 'yes': 2, 'no': 1.

Specifies whether transmission will be multidrop. Enumeration: 'yes': 2, 'no': 1.

Specifies how many times the control unit will be polled before it is put on the slow poll list.

Specifies the number of times active control units will be polled between pollings on the slow poll list.

Specifies the number of synchronization characters that will be added to the beginning of each frame.

Specifies the number of padding characters that will be added to the end of each frame.

Specifies the time between passes through the polling list.

Activated after transmission of a general poll or a data frame.

Specifies how many times the user device will be polled before control is passed on the next cluster.

Specifies the number of times the Netlink device will resend a block of data after the receiving device has detected an error in that block.

Specifies the number of times the Netlink device will send a frame when the receiving device is unable to acknowledge.

Sets the redundancy check parameter. Enumeration: 'odd-lrc': 3, 'even-lrc': 2, 'crc16': 1.

Sets the parity parameter. Enumeration: 'odd-7bit': 1, 'even-7bit': 2, 'none-8bit': 3.

This variable is used to manage the creation and deletion of conceptual rows in the portBsciAdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device, and which is supplied by a management station wishing to exercise an on-line update of the existing conceptual row. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

Only valid if pad type is HPAD. If yes, the HPAD will respond to all devices on the line. If no, the HPAD will respond only to those devices that are configured on the node. Enumeration: 'yes': 2, 'no': 1.

Only valid if pad type is TPAD. If yes, will active the TPAD connection without a poll of the connected device. Enumeration: 'yes': 2, 'no': 1.

A list of BSC Interactive ports . The number of entries will be the number of BSC Interactive ports on the node.

A BSCI Interactive Port entry containing objects relating to the port that are configurable by the user.

Causes the port to be enabled or disabled at node IPL. Enumeration: 'disabled': 1, 'enabled': 2.

Physical port interface connector type. Enumeration: 'rs530': 7, 'v35': 5, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

Data transmission rate in bits per second.

Length of time before the node will transmit an I-frame if the previous transmission is not acknowledged.

Maximum number of times the node will attempt to send an I-frame after a retransmission period expiration.

Maximum frame size that will be transmitted on the port.

Specifies whether the port will generate the clock necessary to synchronize traffic over the link. Enumeration: 'yes': 2, 'no': 1.

Allows the clock to be looped back from the DTE using the TT (Terminal Timing) signal. Enumeration: 'yes': 2, 'no': 1.

BSCI Pad Type Enumeration: 'hpad': 2, 'tpad': 1.

Specifies whether all devices on a line use the same character set for successive session polls. Enumeration: 'yes': 2, 'no': 1.

Specifies whether the user will have the option of including call information in a call request packet. Enumeration: 'yes': 2, 'no': 1.

Causes the virtual circuit to be cleared when no terminals are using it. Enumeration: 'yes': 2, 'no': 1.

Causes all characters transmitted to be treated as data. Enumeration: 'yes': 2, 'no': 1.

Allows management of acknowledgments end to end across the network rather than locally at each end. Enumeration: 'yes': 2, 'no': 1.

Specifies full-duplex transmission. Enumeration: 'yes': 2, 'no': 1.

Specifies whether transmission will be multidrop. Enumeration: 'yes': 2, 'no': 1.

Specifies how many times the control unit will be polled before it is put on the slow poll list.

Specifies the number of times active control units will be polled between pollings on the slow poll list.

Specifies the number of synchronization characters that will be added to the beginning of each frame.

Specifies the number of padding characters that will be added to the end of each frame.

Specifies the time between passes through the polling list.

Activated after transmission of a general poll or a data frame.

Specifies how many times the user device will be polled before control is passed on the next cluster.

Specifies the number of times the Netlink device will resend a block of data after the receiving device has detected an error in that block.

Specifies the number of times the Netlink device will send a frame when the receiving device is unable to acknowledge.

Sets the redundancy check parameter. Enumeration: 'odd-lrc': 3, 'even-lrc': 2, 'crc16': 1.

Sets the parity parameter. Enumeration: 'odd-7bit': 1, 'even-7bit': 2, 'none-8bit': 3.

Only valid if pad type is HPAD. If yes, the HPAD will respond to all devices on the line. If no, the HPAD will respond only to those devices that are configured on the node. Enumeration: 'yes': 2, 'no': 1.

Only valid if pad type is TPAD. If yes, will active the TPAD connection without a poll of the connected device. Enumeration: 'yes': 2, 'no': 1.

A list of BSC Interactive port subscribers.

A BSCI Interactive Port Subscriber entry containing objects relating to the port that are configurable by the user.

Subscriber index for a specific BSCI port subscriber.

Subscriber address of the local end of a BSCI connection.

Subscriber address of the remote end of a BSCI connection.

Causes a BSCI TPAD to automatically call its HPAD when the controller becomes active. Enumeration: 'yes': 2, 'no': 1.

Time between autocall retries.

Maximum number of times an autocall will be sent.

Identifier that will link the BSCI port with a device configured in the BSCI Devices Table.

This variable is used to manage the creation and deletion of conceptual rows in the bsciDevAdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A list of BSC Interactive port subscribers.

A BSCI Interactive Port Subscriber entry containing objects relating to the port that are configurable by the user.

Subscriber index for a specific BSCI port subscriber.

Subscriber address of the local end of a BSCI connection.

Subscriber address of the remote end of a BSCI connection.

Causes a BSCI TPAD to automatically call its HPAD when the controller becomes active. Enumeration: 'yes': 2, 'no': 1.

Time between autocall retries.

Maximum number of times an autocall will be sent.

Identifier that will link the BSCI port with a device configured in the BSCI Devices Table.

A list of BSC Interactive devices.

A BSCI Interactive Device entry containing objects relating to the device that are configurable by the user.

Control Unit identifier.

Device Unit identifier.

The BSCI port connection ID for the device.

Specifies whether each end of the connection is within a same Control Unit/Device Type pair. Enumeration: 'yes': 2, 'no': 1.

Causes all characters transmitted to be treated as data. Enumeration: 'yes': 2, 'no': 1.

Specifies whether the device has a printer attached. Enumeration: 'yes': 2, 'no': 1.

This variable is used to manage the creation and deletion of conceptual rows in the bsciDevAdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

Determines how the BSCI port will report the status of the attached device. Normal status- the port will report what the device reports. No status- the port will report status only if the device is active. Always active status- the port will always report the device as active. Enumeration: 'none': 2, 'always-active': 3, 'normal': 1.

A list of BSC Interactive devices.

A BSCI Interactive Device entry containing objects relating to the device that are configurable by the user.

Control Unit identifier.

Device Unit identifier.

The BSCI port connection ID for the device.

Specifies whether each end of the connection is within a same Control Unit/Device Type pair. Enumeration: 'yes': 2, 'no': 1.

Causes all characters transmitted to be treated as data. Enumeration: 'yes': 2, 'no': 1.

Specifies whether the device has a printer attached. Enumeration: 'yes': 2, 'no': 1.

Determines how the BSCI port will report the status of the attached device. Normal status- the port will report what the device reports. No status- the port will report status only if the device is active. Always active status- the port will always report the device as active. Enumeration: 'none': 2, 'always-active': 3, 'normal': 1.

This table contains Netlink Enterprise specific objects to manage SDLC port. Changing on of the these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. Most of the objects in this read-write table have corresponding read-only objects in the portSdlcOperTable that return the current operating value. The operating values may be different from these configured values if a configured parameter was configured afterthe interface was started.

A list of configured values for an SDLC port.

Writing a value to this object commits the the SDLC port related modified configuration values to the database.

This object defines the max. number of retries to a non-responding Link station, before putting the Link station to slow-poll list if it is not Normal response Mode OR disconnecting the link station if it is data txfr state.

This object defines the number of outstanding frames for triggering window full condition.

This object defines the SNA PAD types. Enumeration: 'hpad': 3, 'xpad': 1, 'npad': 4, 'tpad': 2.

This object defines if the port would generate clock. Enumeration: 'yes': 2, 'no': 1.

This object defines if the rcv clock will be used from DTE. Enumeration: 'yes': 2, 'no': 1.

This object defines the data encoding at the physical layer Enumeration: 'yes': 2, 'no': 1.

This object defines the packet size of the X25 layer used by SNA PAD

This object defines if a Request To Disconnect(RD) will be sent when remote PAD clear the connection Enumeration: 'yes': 2, 'no': 1.

This object defines the type LPDA support on SDLC port. Enumeration: 'none': 1, 'lpda-1': 2, 'lpda-2': 3.

This object defines the connector type of the SDLC port. Enumeration: 'rs530': 7, 'v35': 5, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

This object defines the speed of the SDLC port. The speed may only be set to one of a series of reasonable values, and if an attempt is made to set the speed to a value which is within the valid range but not equal to one of these values, the speed will be rounded up. If the connector type of the port is RS232, the port could be a standard port or a high speed port. If the port is a high speed RS232 port, the maximum valid speed is 256000. If the port is a standard RS232 port, the maximum valid speed is 64000 on the FRX4000/SS1840 and 19200 on all other products. It may be possible to set the speed of a standard RS232 port to a speed which is valid for a high speed RS232 port but invalid for a standard RS232 port. In this case, the port may not end up having the invalid speed. The default speed for a standard RS232 port on the FRX6000 is 19200.

This variable is used to manage the creation and deletion of conceptual rows in the portSdlcAdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device, and which is supplied by a management station wishing to exercise an on-line update of the existing conceptual row. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

This object specifies a character that wll be inserted into the stream when the SNA link is idle. Enumeration: 'hex-ff': 1, 'hex-7e': 2.

This object determines how long the node will wait with no activity on the port before it will declare the attached device down.

This object determines whether level-1 (physical layer) transmission can be in one (half duplex) or both (full duplex) directions at once. Enumeration: 'half-duplex': 2, 'full-duplex': 1.

This table contains current Netlink enterprise specific port parameters

A list of operational values for an SDLC port.

This object is not used.

This object defines the max. number of retries to a non-responding Link station, before putting the Link station to slow-poll list if it is not Normal response Mode OR disconnecting the link station if it is data txfr state.

This object defines the number of outstanding frames for triggering window full condition.

This object defines the SNA PAD type Enumeration: 'hpad': 3, 'xpad': 1, 'npad': 4, 'tpad': 2.

This object defines if the port would generate clock. Enumeration: 'yes': 2, 'no': 1.

This object defines if the rcv clock will be used from DTE. Enumeration: 'yes': 2, 'no': 1.

This object defines the data encoding at the physical layer Enumeration: 'yes': 2, 'no': 1.

This object defines the packet size of the X25 layer used by SNA PAD

This object defines if a Request To Disconnect(RD) will be sent when remote PAD clear the connection Enumeration: 'yes': 2, 'no': 1.

This object defines the type LPDA support on SDLC port. Enumeration: 'none': 1, 'lpda-1': 2, 'lpda-2': 3.

This object defines the operational connector type of the SDLC port. Enumeration: 'rs530': 7, 'v35': 5, 't1': 10, 'rs449': 6, 'rs232': 3, 'x21': 8.

This object defines the operational speed of the SDLC port.

This object specifies a character that wll be inserted into the stream when the SNA link is idle. Enumeration: 'hex-ff': 1, 'hex-7e': 2.

This object determines how long the node will wait with no activity on the port before it will declare the attached device down.

This object determines whether level-1 (physical layer) transmission can be in one (half duplex) or both (full duplex) directions at once. Enumeration: 'half-duplex': 2, 'full-duplex': 1.

This table contains Enterprise specific Link station configurable parameters to manage the link stations.

A list of configured values for an SDLC port.

This object defines the local subscriber ID of the Link Station

This object defines the remote subscriber ID used to connect to remote Link Station

This object defines if auto call is enabled for the link station. If enabled, the link station will initiate connection establishment, when appropriate. Else, it will passively listen to the connection request for establish a connection with the remote PAD Enumeration: 'yes': 2, 'no': 1.

This object is used, only when lSSdlcAdminAutoCall object is yes. This defines the time interval measured in seconds in which the connection request is retried

This object is used, only when lSSdlcAdminAutoCall object is yes. This defines the number of times the connection initiation is retried before given up. The value of Zero(0) means to try indefinitely

This object defines if this link station connects to a LLC2 device/host. Enumeration: 'yes': 2, 'no': 1.

This objects the resource ID used during LPDA command support

This variable is used to manage the creation and deletion of conceptual rows in the lSSdlcAdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned. Also note that deleting a PU entry will only remove it from the database file, and it's existence will still be known by the protocol until the node is rebooted or until an online update of the port is performed.

This object determines whether transmission can be in one (alternate) or two (simultaneous) directions at the same time. Enumeration: 'two-way-simultaneous': 2, 'two-way-alternate': 1.

This table contains the operational parameters of the SDLC port

A list of configured values for an SDLC port.

This object defines the local subscriber ID of the Link Station

This object defines the remote subscriber ID used to connect to remote Link Station

This object defines if auto call is enabled for the link station. If enabled, the link station will initiate connection establishment, when appropriate. Else, it will passively listen to the connection request for establish a connection with the remote PAD Enumeration: 'yes': 2, 'no': 1.

This object is valid, only when lSSdlcAdminAutoCall object is yes. This defines the time interval measured in seconds in which the connection request is retried

This object is used, only when lSSdlcAdminAutoCall object is yes. This defines the number of times the connection initiation is retried before given up. The value of Zero(0) means to try indefinitely

This object defines if this link station connects to a LLC2 device/host. Enumeration: 'yes': 2, 'no': 1.

This objects the resource ID used during LPDA command support

This object determines whether transmission can be in one (alternate) or two (simultaneous) directions at the same time. Enumeration: 'two-way-simultaneous': 2, 'two-way-alternate': 1.

This table contains the LLC2 related parameters used to configure LLC2 session, when the SDLC station is connected to a LLC2 device at the remote end

A list of configured values for an SDLC port.

This object defines Local SAP address (multiple of 4)

This object defines the local MAC address

This object defines idblk used in XID

This object defines idnum used in XID

This object defines LLC2 inactivity timer measured in units of seconds

This object defines LLC2 reply timer measured in units of 100 milliseconds

This object defines Receiver Ack Timer measured in units of milliseconds

This object defines Maximum Retransmissions

This object defines count of I-format LPDU's before sending Ack

This object defines Outstanding Frames

This object defines bandwidth allocation group

This object defines priority for traffic within the node

This variable is used to manage the creation and deletion of conceptual rows in the lSSdlcLlc2AdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned. Also note that deleting a PU entry will only remove it from the database file, and it's existence will still be known by the protocol until the node is rebooted or until an online update of the port is performed.

This object prevents (if yes) the returning of an XID in response to a null XID. This might be desirable if the remote TPAD is not running PU 2.1. It should be noted that even if an XID is sent, an SNRM (Set Normal Response Mode) immediately follows, so the connection will be established. Enumeration: 'yes': 2, 'no': 1.

This table contains operartional parameters related to LLC2 session of this link station.

A list of configured values for an SDLC port.

This object defines Local SAP address (multiple of 4)

This object defines the local MAC address

This object defines idblk used in XID

This object defines idnum used in XID

This object defines LLC2 inactivity timer measured in units of seconds

This object defines LLC2 reply timer measured in units of 100 milliseconds

This object defines Receiver Ack Timer measured in units of milliseconds

This object defines Maximum Retransmissions

This object defines count of I-format LPDU's before sending Ack

This object defines Outstanding Frames

This object defines bandwidth allocation group

This object defines priority for traffic within the node

This object prevents (if yes) the returning of an XID in response to a null XID. This might be desirable if the remote TPAD is not running PU 2.1. It should be noted that even if an XID is sent, an SNRM (Set Normal Response Mode) immediately follows, so the connection will be established. Enumeration: 'yes': 2, 'no': 1.

The configuration information pertaining to a T1 port. T1 ports can operate at full T1 bandwidth or DS0A channelized which provides 24 separate channels.

A T1 port entry containing objects relating to T1 ports.

Enumeration: 'yes': 2, 'no': 1.

Enumeration: 'yes': 2, 'no': 1.

Specifies how this T1 port is to function. ds0AT1 specifies a 24 channelized T1. Enumeration: 'fullT1': 1, 'ds0aT1': 2.

Enumeration: 'esf': 2, 'd4': 1.

Enumeration: 'ami': 2, 'b8zs': 1.

Enumeration: 'x266-399ft': 3, 'x133-266ft': 2, 'x533-655ft': 5, 'minus15db': 7, 'minus22p5db': 8, 'zerodb': 1, 'x399-533ft': 4, 'minus7p5db': 6.

Enumeration: 'bisync': 2, 'sync': 1.

Enumeration: 'yes': 2, 'no': 1.

The configuration information pertaining to a T1 port. T1 ports can operate at full T1 bandwidth or DS0A channelized which provides 24 separate channels.

A T1 port entry containing objects relating to T1 ports.

Enumeration: 'yes': 2, 'no': 1.

Enumeration: 'yes': 2, 'no': 1.

Specifies how this T1 port is to function. ds0AT1 specifies a 24 channelized T1. Enumeration: 'fullT1': 1, 'ds0aT1': 2.

Enumeration: 'esf': 2, 'd4': 1.

Enumeration: 'ami': 2, 'b8zs': 1.

Enumeration: 'x266-399ft': 3, 'x133-266ft': 2, 'x533-655ft': 5, 'minus15db': 7, 'minus22p5db': 8, 'zerodb': 1, 'x399-533ft': 4, 'minus7p5db': 6.

Enumeration: 'bisync': 2, 'sync': 1.

Enumeration: 'yes': 2, 'no': 1.

A list of Voice ports. The number of entries will be the number of Voice ports on the node.

A Voice Port entry containing objects relating to the port that are configurable by the user.

The RLP number of the Voice port.

The Port number of the Voice port.

The flag which causes the port to be enabled or disabled at node IPL. The port will remain in that state until this flag is changed and the node is rebooted, or until an on- line enable or disable is performed. Enumeration: 'disabled': 1, 'enabled': 2.

The speed of the port which is transmitted as part of a Call Setup frame. A Voice call will be established if there is enough bandwidth at each end to provide the minimum configured rate. Enumeration: 'bps-64000': 4, 'bps-4800': 1, 'bps-32000': 3, 'bps-8000': 2.

The flag to enable, disable, or specify a time span over which DTMF (Dual Tone Multi Frequency) tones will be regenerated. 0 = pass tones transparently to the remote device. 1 = detect incoming tones and regenerate as received. 2-255 = regenerate tones for the specified seconds.

The type of interface (in conjunction with the Telephony Interface Type) that will be used by the Voice channel. This requires rebooting for the change to take effect. Telephony Type Interface Type -------------- -------------- OPX (FXO) Loop Start SLT (FXS) Loop Start E&M 4W E&M, 4W E&M TE, 2W E&M, 2W E&M TE AC15 AC15A, AC15C Enumeration: 'loop-start': 3, 'em-2w': 2, 'em-4w-te': 10, 'em-4w': 1, 'em-2w-te': 11, 'ac15-b': 6, 'ac15-a': 4.

The delay at which the E&M 'E' lead follows the 'M' lead.

The local voice level into the voice port. This adjusts the sensitivity of the local voice channel to the signal from the attached device. The purpose of this is to match the voice channel dB level to the input signal. A more negative setting produces a higher input gain. If the level is reduced, the voice channel will be more sensitive to the input. This will also cause the voice output at the remote device to sound louder.

The local voice level out of the voice port. A more positive setting produces a higher volume.

The amount of time the node will wait for a response to a Call Connect or Call Clear request. When the node issues a request, it will set a timer to the value configured here. If that timer expires with no response from the destination, the node will generate a busy tone.

The hunt group that includes the voice channel. Enumeration: 'a': 2, 'none': 1, 'b': 3.

The character that will be required preceeding calls using the long call format. When the user at an attached device dials a long form number, it must be preceeded by the prefix character specified here.

The time the local port will wait before an actual fax transmission begins. If there is no fax tone when this timer expires, the connection will be terminated.

This flag enables or disables automatic busy-out of channels when the link is down. When enabled, the system will automatically busy-out channels when the composite link is down. When disabled, channels remain on-hook when the link is down. If your application is connected to a PBX that can route calls to another alternate source based on an all busy condition, enable this so the PBX will recognize this condition and reroute the calls while the composite link is down. Enumeration: 'disabled': 1, 'enabled': 2.

The flag to indicate whether or not faxes will be transmitted on the port. If no, all calls will be treated as voice. If yes, both voice and fax will be transmitted. Enumeration: 'yes': 2, 'no': 1.

The type of interface (in conjunction with the Interface Type) that will be used by the Voice channel. This requires rebooting for the change to take effect. Telephony Type Interface Type -------------- -------------- OPX (FXO) Loop Start SLT (FXS) Loop Start E&M 4W E&M, 4W E&M TE, 2W E&M, 2W E&M TE AC15 AC15A, AC15C Enumeration: 'slt': 2, 'em': 3, 'ac15': 4, 'opx': 1.

The amount of jitter delay.

The amount of sample delay.

The delay the node will use to determine when variable length dialing is complete. (Variable length dialing allows the user to place a call without entering the configured number of digits for the speed dial number.)

The flag to enable or disable the auto dial feature. Note that enabling this feature will disable the variable length dialing feature for this channel. Enumeration: 'disabled': 1, 'enabled': 2.

The silence suppression level. A larger silence suppression level allows more data channels to operate simultaneously with the voice channels. Enumeration: 'high': 4, 'very-low': 1, 'medium': 3, 'very-high': 5, 'low': 2.

The number to which the node will attempt to connect when the handset attached to this port is taken off-hook. This is applicable only when the Auto Dial feature is enabled.

The flag to enable or disable auto polling. This is applicable only when the Auto Dial feature is enabled. When enabled, the node periodically polls the destination. If the poll is not acknowledged, the node will busy-out the channel. This can be useful in situations where the destination is an emergency number that must always be available. If the destination does not answer the automatic poll, the busy-out condition will notify an attached PBX that the emergency call should be routed to another call routing device. Enumeration: 'disabled': 1, 'enabled': 2.

The frequency with which an Auto Poll will be sent. This is applicable only when auto poll is enabled.

The source of the extended digits when the user of attached equipment dials a speed dial number. This is applicable only when the number of extended dial digits is greater than zero. When map is specified, extended digits are taken from the extended digits field in the map table. When user is specified, extended digits are taken from the user of attached equipment. Enumeration: 'map': 1, 'user': 2.

The number of leading dial digits that will be deleted before a dial string is forwarded. This is primarily used to delete leading dial digits that may be inserted by an attached PBX.

The length of a pause that can be inserted in an extended dial string that is being forwarded. This is applicable only when forwarded output digits is all or extended. When a comma is encountered in an extended digits string, the node will pause for the length of time specified here before additional extended digits are forwarded.

The method how the dial digits will be forwarded. This is applicable only when forwarded output digits is all or extended. Enumeration: 'dtmf': 1, 'pulse': 2.

The flag indicating which dial digits, if any, to forward. If none, dial digits are not forwarded to the destination device when a call is initiated on this channel. If all, the dialed speed dial number and associated extended digits are forwarded to the destination device. If extended, only the extended digit string is forwarded. Enumeration: 'none': 1, 'extended': 3, 'all': 2.

The make ratio of each digit pulse that is forwarded. This is applicable only when forwarded output digits is all or extended and forwarded digit type is pulse.

The break ratio of each digit pulse that is forwarded. This is applicable only when forwarded output digits is all or extended and forwarded digit type is pulse.

The length of a tone that will be used to produce a single DTMF digit. This is applicable only when forwarded output digits is all or extended and forwarded digit type is DTMF.

The length of silence between DTMF tones in a dial digit string. This is applicable only when forwarded output digits is all or extended and forwarded digit type is DTMF.

The tone type to detect/regenerate for forwarding DTMF/MF. Enumeration: 'mf': 2, 'dtmf': 1.

This variable is used to manage the creation and deletion of conceptual rows in the portVoiceAdminTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device, and which is supplied by a management station wishing to exercise an on-line update of the existing conceptual row. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A list of Voice ports. The number of entries will be the number of Voice ports on the node.

A Voice Port entry containing objects relating to the port that are configurable by the user.

The RLP number of the Voice port.

The Port number of the Voice port.

The flag which causes the port to be enabled or disabled at node IPL. The port will remain in that state until this flag is changed and the node is rebooted, or until an on- line enable or disable is performed. Enumeration: 'disabled': 1, 'enabled': 2.

The speed of the port which is transmitted as part of a Call Setup frame. A Voice call will be established if there is enough bandwidth at each end to provide the minimum configured rate. Enumeration: 'bps-64000': 4, 'bps-4800': 1, 'bps-32000': 3, 'bps-8000': 2.

The flag to enable, disable, or specify a time span over which DTMF (Dual Tone Multi Frequency) tones will be regenerated. 0 = pass tones transparently to the remote device. 1 = detect incoming tones and regenerate as received. 2-255 = regenerate tones for the specified seconds.

The type of interface (in conjunction with the Telephony Interface Type) that will be used by the Voice channel. This requires rebooting for the change to take effect. Telephony Type Interface Type -------------- -------------- OPX (FXO) Loop Start SLT (FXS) Loop Start E&M 4W E&M, 4W E&M TE, 2W E&M, 2W E&M TE AC15 AC15A, AC15C Enumeration: 'loop-start': 3, 'em-2w': 2, 'em-4w-te': 10, 'em-4w': 1, 'em-2w-te': 11, 'ac15-b': 6, 'ac15-a': 4.

The delay at which the E&M 'E' lead follows the 'M' lead.

The local voice level into the voice port. This adjusts the sensitivity of the local voice channel to the signal from the attached device. The purpose of this is to match the voice channel dB level to the input signal. A more negative setting produces a higher input gain. If the level is reduced, the voice channel will be more sensitive to the input. This will also cause the voice output at the remote device to sound louder.

The local voice level out of the voice port. A more positive setting produces a higher volume.

The amount of time the node will wait for a response to a Call Connect or Call Clear request. When the node issues a request, it will set a timer to the value configured here. If that timer expires with no response from the destination, the node will generate a busy tone.

The hunt group that includes the voice channel. Enumeration: 'a': 2, 'none': 1, 'b': 3.

The character that will be required preceeding calls using the long call format. When the user at an attached device dials a long form number, it must be preceeded by the prefix character specified here.

The time the local port will wait before an actual fax transmission begins. If there is no fax tone when this timer expires, the connection will be terminated.

This flag enables or disables automatic busy-out of channels when the link is down. When enabled, the system will automatically busy-out channels when the composite link is down. When disabled, channels remain on-hook when the link is down. If your application is connected to a PBX that can route calls to another alternate source based on an all busy condition, enable this so the PBX will recognize this condition and reroute the calls while the composite link is down. Enumeration: 'disabled': 1, 'enabled': 2.

The flag to indicate whether or not faxes will be transmitted on the port. If no, all calls will be treated as voice. If yes, both voice and fax will be transmitted. Enumeration: 'yes': 2, 'no': 1.

The type of interface (in conjunction with the Interface Type) that will be used by the Voice channel. This requires rebooting for the change to take effect. Telephony Type Interface Type -------------- -------------- OPX (FXO) Loop Start SLT (FXS) Loop Start E&M 4W E&M, 4W E&M TE, 2W E&M, 2W E&M TE AC15 AC15A, AC15C Enumeration: 'slt': 2, 'em': 3, 'ac15': 4, 'opx': 1.

The amount of jitter delay.

The amount of sample delay.

The delay the node will use to determine when variable length dialing is complete. (Variable length dialing allows the user to place a call without entering the configured number of digits for the speed dial number.)

The flag to enable or disable the auto dial feature. Note that enabling this feature will disable the variable length dialing feature for this channel. Enumeration: 'disabled': 1, 'enabled': 2.

The silence suppression level. A larger silence suppression level allows more data channels to operate simultaneously with the voice channels. Enumeration: 'high': 4, 'very-low': 1, 'medium': 3, 'very-high': 5, 'low': 2.

The number to which the node will attempt to connect when the handset attached to this port is taken off-hook. This is applicable only when the Auto Dial feature is enabled.

The flag to enable or disable auto polling. This is applicable only when the Auto Dial feature is enabled. When enabled, the node periodically polls the destination. If the poll is not acknowledged, the node will busy-out the channel. This can be useful in situations where the destination is an emergency number that must always be available. If the destination does not answer the automatic poll, the busy-out condition will notify an attached PBX that the emergency call should be routed to another call routing device. Enumeration: 'disabled': 1, 'enabled': 2.

The frequency with which an Auto Poll will be sent. This is applicable only when auto poll is enabled.

The source of the extended digits when the user of attached equipment dials a speed dial number. This is applicable only when the number of extended dial digits is greater than zero. When map is specified, extended digits are taken from the extended digits field in the map table. When user is specified, extended digits are taken from the user of attached equipment. Enumeration: 'map': 1, 'user': 2.

The number of leading dial digits that will be deleted before a dial string is forwarded. This is primarily used to delete leading dial digits that may be inserted by an attached PBX.

The length of a pause that can be inserted in an extended dial string that is being forwarded. This is applicable only when forwarded output digits is all or extended. When a comma is encountered in an extended digits string, the node will pause for the length of time specified here before additional extended digits are forwarded.

The method how the dial digits will be forwarded. This is applicable only when forwarded output digits is all or extended. Enumeration: 'dtmf': 1, 'pulse': 2.

The flag indicating which dial digits, if any, to forward. If none, dial digits are not forwarded to the destination device when a call is initiated on this channel. If all, the dialed speed dial number and associated extended digits are forwarded to the destination device. If extended, only the extended digit string is forwarded. Enumeration: 'none': 1, 'extended': 3, 'all': 2.

The make ratio of each digit pulse that is forwarded. This is applicable only when forwarded output digits is all or extended and forwarded digit type is pulse.

The break ratio of each digit pulse that is forwarded. This is applicable only when forwarded output digits is all or extended and forwarded digit type is pulse.

The length of a tone that will be used to produce a single DTMF digit. This is applicable only when forwarded output digits is all or extended and forwarded digit type is DTMF.

The length of silence between DTMF tones in a dial digit string. This is applicable only when forwarded output digits is all or extended and forwarded digit type is DTMF.

The tone type to detect/regenerate for forwarding DTMF/MF. Enumeration: 'mf': 2, 'dtmf': 1.

A Table to describe each interface on a node. This table is indexed by RLP and Port number and can be used to identify the corresponding MIB-II ifIndex of a Port as well as additional port information maintained by Netlink.

An Interface entry containing objects relating to interfaces.

The RLP number on the node. RLP numbers 1-8 are Physical RLP cards, and RLP number 250, 251 and 252 define IP, IPX and LLC2 interfaces respectively.

The Port number on the RLP. Port numbers 1-8 are known to be physical ports, and 9-64 are logical ports. If the RLP number identifies an IP, IPX or LLC2 interface, then the port number can be 1-257 (IP), 1-64 (IPX), or 1-96 (LLC2).

The type of interface Enumeration: 'smdsIcip': 52, 'ethernet3Mbit': 26, 'propPointToPointSerial': 22, 'miox25': 38, 'arcnetPlus': 36, 'rfc877x25': 5, 'softwareLoopback': 24, 'basicISDN': 20, 'ds3': 30, 'ppp': 23, 'frameRelay': 32, 'slip': 28, 'modem': 48, 'v35': 45, 'ipx': 206, 'hssi': 46, 'iso88023Csmacd': 7, 'sip': 31, 'ddnX25': 4, 'iso88026Man': 10, 'proteon10Mbit': 12, 'sonet': 39, 'x25ple': 40, 'iso88022llc': 41, 'voice': 208, 'other': 1, 'sdlc': 17, 'ip': 205, 'lapb': 16, 'sonetVT': 51, 'aal5': 49, 'llc2': 207, 'sonetPath': 50, 'para': 34, 'hippi': 47, 'iso88024TokenBus': 8, 'localTalk': 42, 'hyperchannel': 14, 'iso88025TokenRing': 9, 'arcnet': 35, 'trunk': 200, 'primaryISDN': 21, 'proteon80Mbit': 13, 'bsci': 202, 'rs232': 33, 'e1': 19, 'fddi': 15, 'smdsDxi': 43, 'ethernetCsmacd': 6, 'starLan': 11, 'frameRelayService': 44, 'atm': 37, 'eon': 25, 'ds1': 18, 'hdh1822': 3, 'nsip': 27, 'regular1822': 2, 'propVirtual': 53, 'logicalPort': 203, 'async': 201, 'ultra': 29, 't1': 204, 'propMultiplexor': 54.

The associated index into the MIB-II ifTable for this port

The associated index into an enterprise table used to describe additional information for this port. See nlIfTableOid as the pointer to the actual table.

The OID of the table Entry that contains additional information about this port. The OID will point to a specific table depending on the type of port.

The physical connector type used for this port. Valid for ports 1-8 only. Enumeration: 'rs530': 7, 'voice': 13, 'v35': 5, 'v25bis-dial': 4, 'e1': 11, 'none': 2, 't1': 10, 'rs449': 6, 'csuds': 9, 'rs232': 3, 'x21': 8.

The status of this port state. Valid for ports 1-64 only. Enumeration: 'configured': 6, 'onHook': 18, 'ipl': 12, 'disabled': 4, 'linkUp': 1, 'redAlarm': 17, 'quiesced': 8, 'disconnect': 5, 'na': 13, 'operational': 3, 'failed': 9, 'other': 11, 'dialReady': 7, 'onHookPending': 22, 'hardwareFault': 10, 'activeVoiceCall': 21, 'yellowAlarm': 16, 'blueAlarm': 15, 'offHook': 19, 'dialing': 20, 'remoteLoopback': 14, 'restarting': 2.

The Underlying Physical Port number on the RLP of this logical port. Port numbers 1-8 are valid, but this field is only applicable if the nlIfPort field is 9-64.

A Table to define LLC2 interfaces over LAN.

An LLC2 LAN Interface entry containing objects relating to LLC2 LAN interfaces.

The RLP number on the node. For LLC2 LAN interfaces, this must be 252.

The Port number on the RLP. For LLC2 LAN interfaces, this corresponds to the LAN card number.

The type of the LLC2 interface- either ethernet or token ring. Enumeration: 'ethernet': 1, 'token-ring': 2.

The LAN card that the LLC2 interface is running on.

Valid only if the type of the LLC2 LAN interface is token ring. Identifies the token ring adapter to the network.

The LLC2 interface number.

This variable is used to manage the creation and deletion of conceptual rows in the nlIfLlc2LANTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

Interface priority- allows setting a priority for traffic within the node. The higher the number, the higher the priority relative to other intra-nodal traffic.

The blocked port flag. Enumeration: 'yes': 2, 'no': 1.

A Table to define LLC2 interfaces over Frame Relay.

An LLC2 FR Interface entry containing objects relating to LLC2 FR interfaces.

The RLP number on the node.

The Port number on the RLP. Port numbers 1-8 are known to be physical ports, and channels are 193-241.

The DLCI number used to identify the entry in the table. The range is 16-991.

The RFC1490 encapsulation method used for LLC2 traffic. Enumeration: 'tb-8023': 2, 'native-llc2': 1, 'srb-8025': 3.

Interface priority- allows setting a priority for traffic within the node. The higher the number, the higher the priority relative to other intra-nodal traffic.

Assigns the interface to one of sixteen groups whose parameters regulate bandwidth usage.

The MAC address of the host or workstation to which the remote device needs to connect. Valid only if the format is native-llc2.

If originated, means that LLC2 connects from the configured Host MAC address can use this interface. If terminated, connections to the configured address can use this interface. Valid only if the format is native-llc2. Enumeration: 'originated': 2, 'terminated': 1, 'not-applicable': 3.

Identifies the ring number used by a frame relay-compliant source-route bridge at the other end of this PVC. Valid only if the format is srb-8025.

LLC2 interface number.

This variable is used to manage the creation and deletion of conceptual rows in the nlIfLlc2FrTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

The blocked port flag. Enumeration: 'yes': 2, 'no': 1.

The IPX Static Route Configuration Table

Each entry corresponds to one instance of IPX Static Routing on the system

The unique identifier of the circuit used to reach the first hop in the static route

The IPX network number of the route's destination

The hex value of the node address of the router that will forward a packet when this route is used. If Novell's IPXWAN is used on the interface, this field will be ignored

This variable is used to manage the creation and deletion of conceptual rows in the ipxStaticRouteTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

The IPX Static Route Configuration Table

Each entry corresponds to one instance of IPX Static Routing on the system

The Service Type, a SAP service code

The Sercice Name, identifies a specific server in the IPX network.

The IPX network number portion of the IPX address of the server identified by ServName

The node portion of the IPX address of the service

The socket portion of the IPX address of the service

The number of routers that a packet must pass through t reach the server

The node address of the router thar will forward a packet

The IPX network number assigned to the interface used to send packets that are destined for this server

This variable is used to manage the creation and deletion of conceptual rows in the ipxServTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

The IPX Interface Table

The Interface Number, a sequential number to identify the interface

This flag causes the IPX interface to be enabled (N) or disabled (Y) at node IPL. The port will remain in that state until this parameter is changed Enumeration: 'yes': 2, 'no': 1.

The interface type. 802.5 is not valid on FRX4000 Enumeration: 'x25': 3, 'ethernet': 1, 'eight025': 2, 'frl': 4.

The frame type - depends on the interfece type. Valid combinations are: Ethernet, 802.5 - typeII, raw, llc, snap Frame relay, X25 - typeII Enumeration: 'llc': 3, 'raw': 2, 'typeII': 1, 'snap': 4.

Maximum frame size that can be transmitted or received over the IPX interface.: Valid ranges are: Ethernet - (45-1518) 802.5 - (48-4096) Frame relay, X25 - (31-4096)

Identifies the local interface to the Novell Network

Assigns the IPX interface to one of sixteen groups whose parameters regulate bandwidth usage

Enables/Disables the IPX interface's ability to handle Novell diagonistics packets Enumeration: 'yes': 2, 'no': 1.

Determines whether Novell-encapsulated NetBIOS frames received on the interface will be processed Enumeration: 'yes': 2, 'no': 1.

Maximum number of hops allowed for routing a Novell-encapsulated NetBIOS frame

Determines whether the node will originate periodic IPX Routing Information Protocol messages from this interface to inform the network that the route through this interface is viable Enumeration: 'yes': 2, 'no': 1.

This is the interval between the periodic IPX RIP broadcasts from this interface

Determines whether the node will originate periodic IPX SAP messages from this interface to inform the network which SAP entries in the routing table are viable Enumeration: 'yes': 2, 'no': 1.

The interval between the periodic SAP broadcasts from this interface

Datermines whether this interface will support RIP proceswsing Enumeration: 'yes': 2, 'no': 1.

This is used to delete route entries in the routing information table. The timer starts/restarts each time an entry is created/updated. If the timer expires, the router will assume that the entry is no longer valid and the entry will be deleteda from the table

Maximum possible RIP packet size

Determines whether the interface will support SAP or not Enumeration: 'yes': 2, 'no': 1.

This is used to delete route entries from the router information table. The timer starts/restars each time an entry is created/updated. If the timer expires, the router will assume that the entry is no longer valid and the entry will be deleted from the table

is the time (in 55 milliseconds unit) that will normally take to forward frames out of interface. Recommmended values are 1 for LAN interfaces and 30 for WAN interfaces. A value of 0 indicates that the back to back frame forwarding is acceptable. This time is used to calculate the least cost path during routing. If IPXWAMN is (Y), Transport time will be overridden by the value calculated by IPXWAN

Determines whether NetWare file server serialization security frames will be forwarded on the interface. These broadcasts frames are used by Novell to hold informations regarding the licensing of the file server executables Enumeration: 'yes': 2, 'no': 1.

Determines whether this interface will be used by the local node to respond to (keep alive) messages on behalf of the client workstations. Novell servers periodically issue these messages to all clients to determine whether each client is still alive Enumeration: 'yes': 2, 'no': 1.

The card number installed in an FRX6000. The first or only LAN card installed is always 0, and the second is card 1

Determines whether Novell's IPXWAN protocol will be used on the interface. IPXWAN specifies a method for IPX routers to communicate across WAN links. FRX6000 and FRX4000 implement IPXWAN running over RFC 1490-complaint frame relay and RFC1356-complaint X.25 Enumeration: 'yes': 2, 'not-applicable': 3, 'no': 1.

Subscruber id that defines an IPX interface in the node, by associating itself with port 66 (a number reserved for the IPXinterface) on the RLP that has an IPX installed on it. .. Valid only for type X.25

Subscriber ID associated with the physical X.25 port that will be used for the IPX interface . .. Valid only for type X.25

The frequency with which calls will be placed to try to establish a connection .. Valid only for type X.25

is a period that an IPX connection can remain active with no traffic before the connection is cleared. .. Valid only for type X.25

This specifies a number of virtual circuits over which IPX traffic will be transmitted in parallel. .. Valid only for type X.25

Identifies this interface as one of a PVC. .. Valid only for type X.25 Enumeration: 'yes': 2, 'not-applicable': 3, 'no': 1.

Identifies the location of this end of the frame relay IPX interface. .. Valid only for frame relay

Identifies the location of this end of the frame relay IPX interface. .. Valid only for frame relay

Identifies the location of this end of the frame relay IPX interface. .. Valid only for frame relay

This variable is used to manage the creation and deletion of conceptual rows in the ipxInterfaceTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

Identifies the node to the IPX network

The minimum delay between consecutive RIP and SAP transmissions

An unique identifier within the IPX network

A Table to define IP interfaces over frame relay, X.25, or LAN (ethernet, 802.3, 802.5).

An IP Interface entry containing objects relating to IP interfaces.

The interface number which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this number is NOT the same interface as defined by the same value of ifIndex.

The maximum size (in bytes) of the data field that can be used to encapsulate an IP datagram for transmission over the interface. If the interface type is LAN based, then the maximum size value cannot exceed 1500.

The mask used during routing to determine the portion of the address associated with the network.

The number of network hops (network gateways in the overall path over the internet) associated with this interface.

The flag which indicates whether IP may add routes obtained by ICMP, whose error and control function is used to send re-direction options back to the source if problems are discovered. Enumeration: 'yes': 2, 'no': 1.

The frequency with which RIP messages will be sent to every neighbor node, containing any changes to the routing table that occurred since the last full update.

The frequency with which updates of the entire routing table will be sent to every neighbor node, via one or more RIP messages.

The priority setting for traffic within the node. The higher the number, the higher the priority relative to other intra-nodal traffic.

The bandwidth allocation group to which this interface is assigned to. This object is only valid when the interface type is frame relay or proprietary virtual.

The type of IP interface. Enumeration: 'ethernetCsmacd': 6, 'propVirtual': 53, 'iso88025TokenRing': 9, 'other': 1, 'frameRelay': 32, 'rfc877x25': 5, 'iso88023Csmacd': 7.

The IP address of the end-to-end sender.

The IP address of the end-to-end receiver. This object is only valid when the interface type is X.25 or proprietary virtual, or when the interface type is frame relay and the inverse ARP flag indicates disabled.

The IP address that is used to send to all LAN hosts on the network. This object is only valid when the interface type is LAN based.

The LAN card that contains the interface. This object is only valid when the interface type is LAN based.

The subscriber ID associated with the source IP interface port. This object is only valid when the interface type is X.25.

The subscriber ID associated with the destination IP interface port. This object is only valid when the interface type is X.25.

The frequency with which calls will be placed to try to establish a connection. This object is only valid when the interface type is X.25.

The period that an IP connection remains active with no traffic before the connection is cleared. This object is only valid when the interface type is X.25.

The number of virtual circuits over which IP traffic will be transmitted in parallel. This object is only valid when the interface type is X.25.

The flag which indicates whether this interface is a PVC. This object is only valid when the interface type is X.25. Enumeration: 'yes': 2, 'no': 1.

The RLP of the logical interface of this end of the frame relay link. This object is only valid when the interface type is frame relay.

The port of the logical interface of this end of the frame relay link. This object is only valid when the interface type is frame relay.

The DLCI of the logical interface of this end of the frame relay link. This object is only valid when the interface type is frame relay.

The RIP support that is being run on the interface. Enumeration: 'disabled': 1, 'receive-only': 3, 'enabled': 2.

The flag which indicates whether inverse ARP is enabled or disabled. This object is only valid when the interface type is frame relay. Enumeration: 'disabled': 1, 'enabled': 2.

The flag which indicates whether proxy ARP is enabled or disabled. This object is only valid when the interface type is LAN based. Enumeration: 'disabled': 1, 'enabled': 2.

The flag which indicates whether this interface is an unnumbered interface (i.e., does not require a specific source IP address). This object is only valid when the interface type is frame relay or X.25. Enumeration: 'yes': 2, 'no': 1.

This variable is used to manage the creation and deletion of conceptual rows in the nlIfIpTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to define secondary IP interfaces on a LAN (ethernet, 802.3, 802.5) interface.

An IP Secondary Address entry containing objects relating to IP secondary addresses.

The maximum number of secondary IP addresses that may be configured on an interface.

The mask used during routing to determine the portion of the address associated with the network.

The number of network hops (network gateways in the overall path over the internet) associated with this interface.

The IP address of the end-to-end sender.

The IP address that is used to send to all LAN hosts on the network.

The RIP support that is being run on the interface. Enumeration: 'disabled': 1, 'receive-only': 3, 'enabled': 2.

This variable is used to manage the creation and deletion of conceptual rows in the nlIfIpSecondaryAddrTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to define Voice interfaces over frame relay.

A Voice Interface entry containing objects relating to the interface that are configurable by the user.

The interface number which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this number is NOT the same interface as defined by the same value of ifIndex.

The node type for the node at the remote end of the frame relay connection. Enumeration: 'netlink': 1, 'act': 2.

The node number of the remote device.

The voice port on the remote device.

The node number of the local device.

The voice port on the local device.

The RLP of the logical interface of this end of the frame relay link.

The port of the logical interface of this end of the frame relay link.

The DLCI of the logical interface of this end of the frame relay link.

Enumeration: 'yes': 2, 'no': 1.

This variable is used to manage the creation and deletion of conceptual rows in the noIfVoiceTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to define each local subscriber.

A Local Subscriber entry containing objects relating to local subscribers.

The Subscriber ID. A valid subscriber ID is a string of numeric digits represented by their ASCII equivalents. The ASCII equivalents of the wildcard characters '*' and '?' are also allowed. A '*' is a wildcard that matches any number of digits, including zero. A '?' is a wildcard that matches any single digit.

The Subscriber name. The subscriber name is not accessible from SNMP, and a blank string is always returned.

The Subscriber routing algorithm. The following 4 types of routing algorithms are supported. 1 - round robin selects ports specified cyclicly in numerical order according to the list of Redirection addresses. If the port is unreachable or congested, the call request is sent to the next port. 2. Alternate Route on Line Failure - selects the first port not in a failed state. If a connection is not made, the call will be cleared even if other ports are available. 3. Alternate Route on Line Busy - selects the first port that has LCN's available (not busy). If a port has failed, the next available port is selected. 4. Least LCN with throughput selects the line with the minumum loading, calculated by weight and number of LCN's in use. If use of a routing algorithm is not desired, accept the default and specify only one routing path. Enumeration: 'round-robin': 1, 'line-busy': 3, 'least-lcn': 4, 'line-failed': 2.

Systematic Redirection. Enumeration: 'yes': 2, 'no': 1.

Redirect calls according to Redirection Addresses if the primary subscriber device is busy. Enumeration: 'yes': 2, 'no': 1.

Redirect calls according to Redirection Addresses if the primary subscriber device is out of order. Enumeration: 'yes': 2, 'no': 1.

Allows setting a priority for traffic within the node.

This variable is used to manage the creation and deletion of conceptual rows in the nlLocalSubscriberTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to define local subscriber route paths.

A Local Subscriber Route entry containing objects relating to local subscriber routes.

Route path index for a specific subscriber route path.

Flag to indicate if the LP/port routing path to the subscriber device is configured or not. This object is read- only. The route is always configured for an entry in the table. Enumeration: 'yes': 2, 'no': 1.

Instance of the LP that makes up the routing path

Instance of the port that makes up the routing path

This variable is used to manage the creation and deletion of conceptual rows in the nlLocalSubscriberRouteTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to list local subscriber redirection addresses.

A Local Subscriber Redirection Address entry containing objects relating to local subscriber redirection addresses.

Redirection entry index for a local subscriber.

Subscriber redirection address.

This variable is used to manage the creation and deletion of conceptual rows in the nlLocalSubscriberRedirTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to define LLC2 host entries.

An LLC2 Host entry containing objects relating to LLC2 hosts.

LLC2 Host Index

The LLC2 Host MAC Address.

The mode in which the Host is operating Enumeration: 'originated': 1, 'terminated': 2.

Reply Timer used to detect a failure of the Remote node.

Receive Ack Timer used to delay sending an acknowledgement of a received information LPDU.

Timer used to detect inoperative condition of the remote link station or transmission medium.

The number of Information LPDUs that need to be received before an acknowledgement is sent.

Maximum number of sequentially numbered information LPDUs that can be outstanding at any time.

Maximum number of LPDU retransmissions occur following the expiration of Timer T1.

Traffic priorities within the node.

Bandwidth Allocation group to which the LLC2 Host belongs. This object is read-only. Bandwidth allocation groups do not apply to LLC2 hosts.

LLC2 hosts Routing Subscriber Id

LLC2 Host's Source MAC Address Mask

Specifies different type(s) of interface(s) that can be used for connections to a terminated host session. Enumeration: 'lan': 1, 'all': 5, 'tokenRing': 3, 'frameRelay': 2, 'not-applicable': 6, 'ethernet': 4.

Row status convention for LLC2 Host entry.

LLC2 interface number associated with this host entry, always 300 for non-FRX7000.

Traffic group associated with LLC2 interface, always 1 for non-FRX7000.

A Table to describe LLC2 Terminated Host Connections.

An LLC2 Terminated Host Connection entry containing objects relating to LLC2 terminated host connections.

LLC2 Host connection Sequence number

Service Access point used to connect to the Host

LLC2 Host Connection's Local Subscriber Id

LLC2 Host Connection's Remote Subscriber Id

This variable is used to manage the creation and deletion of conceptual rows in the nlLlc2TermConnectionTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

A Table to describe LLC2 Originated Host Connections.

An LLC2 Originated Host Connection entry containing objects relating to LLC2 originated host connections.

LLC2 Host connection Sequence number

Service Access point used to connect to the Host

Specifies Remote subscriber device type Enumeration: 'sdlc': 1, 'llc2': 2.

LLC2 Host Connection's Local Subscriber Id

LLC2 Host Connection's Remote Subscriber Id

This field is obsolete

This field is obsolete

This field is obsolete

This field is obsolete

This variable is used to manage the creation and deletion of conceptual rows in the nlLlc2OrigConnectionTable and follows the SNMPv2 RowStatus conventions by supporting the following values: - `active', which indicates that the conceptual row is available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row does not exist. - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device. For a management protocol set operation, a genErr response is returned when the row already exists. - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Note that all of the above values may be specified in a management protocol set operation, and only the 'active' value will be returned in response to a management protocol retrieval operation. For a management protocol set operation, if other variable bindings are included in the same PDU, then a genErr response is returned.

The host number to be used for the next created host record, always 1 on non-FRX7000.

A Table to describe the status of each pin on a physical port. This table is indexed by RLP and Port

A port pin entry containing objects relating to ports.

The RLP number on the node

The Port number on the RLP. Port numbers 0-7 are known to be physical ports.

The status of all pins for this physical port. There is one octet value for each of the pins. Each octet value is defined as follows: 00 = unknown 01 = active 02 = inactive 03 = unused

A Table to describe Statistics on each RLP

An RLP statistics entry containing objects relating to RLP statistics.

The RLP number

The number of frames queued on the RLP

The percentage of total buffers available being used at the moment of inquiry

The number of frames received.

The number of frames transmitted.

The number of frames rejected.

The number of frames retransmitted . If this value is consistently greater than zero and there are no other problems, then increase the retransmission parameter.

A Table to describe Statistics on each RLP

A port statistics entry containing objects relating to port statistics.

The RLP number

The Port number

The number of frames received.

The number of frames transmitted.

The number of frames retransmitted.

The number of Frame Check Sequence (FCS) errors. A value consistently greater than zero indicates line probelms.

The sum of Rejects and Frame Rejects. A value consistently greater than zero indicates line probelms.

The ratio of non-flag characters to total characters being received by the port.

The ration of non-flag characters to total characters being transmitted by the port.

A Table to describe Frame Relay Frame Level Statistics on each Port

A frame relay port statistics entry containing objects relating to frame relay port statistics.

The RLP Number.

The Port number.

The number of frames transmitted on the port with the Discard Eligibility bit set.

The number of frames received on the port with the discard eligibility bit set.

The of number of frames transmitted on the port with FECN.

The number of frames received on the port with FECN.

The number of frames transmitted on the port with BECN.

The number of frames received on the port with BECN.

The number of LMI frames transmitted on the port.

The number of LMI frames received on the port.

The number of AnnexD frames transmitted on the port

The number of AnnexD frames received on the port

The total number of discarded frames on the port.

A Table to describe X25 Frame Level Txmit Statistics on each Port

An X25 frame level transmit statistics entry containing objects relating to x25 frame level transmit statistics.

The RLP Number.

The Port number.

The number of SABM's transmitted on the port.

The number of UA Frames transmitted on the port.

The number of DISC Frames transmitted on the port.

The number of DM frames transmitted on the port.

The of Number of FRMR frames transmitted on the port.

The number of Reject Frames transmitted on the port.

The number of RR frames transmitted on the port.

The number of RNR Frames transmitted on the port.

The number of INFO Frames transmitted on the port

A Table to describe X25 Frame Level Rxmit Statistics on each Port

An X25 frame level receive statistics entry containing objects relating to x25 frame level receive statistics.

The RLP Number.

The Port number.

The number of SABM's received on the port.

The number of UA Frames received on the port.

The number of DISC Frames received on the port.

The number of DM frames received on the port.

The of Number of FRMR frames received on the port.

The number of Reject Frames received on the port.

The number of RR frames received on the port.

The number of RNR Frames received on the port.

The number of INFO Frames received on the port

A Table to describe T1 Statistics.

A T1 port statistics entry containing objects relating to T1 port statistics.

The RLP Number.

The Port Number.

Total received frames.

Total transmitted frames.

Line code violation count.

PCVR Bit error count.

Multiframe out of sync count.

Blue alarm count.

Yellow alarm count.

Red alarm count.

Receive port utilization.

Transmit port utilization.

Total aborted transmit frames.

Total aborted receive frames.

Total receive overruns.

Total bad receives.

Total bad receives.

A Table to describe DS0A Statistics.

A DS0A port statistics entry containing objects relating to DS0A port statistics.

The RLP Number.

The Port Number.

The Channel Number.

Total transmitted frames.

Total received frames.

Total receive aborted frames.

Total receive overruns.

Total receive errors.

A Table to describe Voice over Frame Relay Statistics.

A voice port statistics entry containing objects relating to voice port statistics.

The RLP Number.

The Port Number.

The Number of Calls Received from the Network.

The Number of Calls Transmitted to the Network.

The Number of Call Accepts Received from the Network.

The Number of Call Accepts Transmitted to the Network.

The Number of Call Receives cleared.

The Number of Call Transmitts cleared.

The Number of calls which received Busy indication.

The Number of calls which transmitted time-out to the network.

The number of congestion management frames Received.

The number of congestion management frames Transmitted.

A Table to describe Statistic thresholds on each RLP

An RLP statistics threshold entry containing objects relating to RLP statistics thresholds.

The RLP Number.

The threshold for Percent of Buffers in use on the RLP

The threshold for Percent of Buffers in use on the RLP

The threshold for Rcvd frames per second on the RLP

The threshold for Txmitted frames per second on the RLP

The threshold for Rejected Frames per second on the RLP

The threshold for Retransmitted frames per second on the RLP

A Table to describe Statistic thresholds on each port

A port statistics threshold entry containing objects relating to port statistics thresholds.

The RLP Number.

The Port Number.

The threshold for Rcvd frames per second on the port.

The threshold for Txmitted frames per second on the port.

The threshold for Retransmitted frames per second on the port.

The threshold for FCS errors per second on the port.

The threshold for Logical Rejects per second on the port.