This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 2 | Value: 0--255 |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 0 | Value: 0--13000 |
The value of this characteristic is linked to the retransmit timer used on the remote station. A suggested value is between 10% and 20% of that timer. However, the actual values you can use may be limited by the communications product.
The default value indicates that no holdback is used and the local station must acknowledge immediately.
Default: 0 | Value: 0--255 |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 64 | Value: 0--255 |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 8 | Value: 0--255 |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 4 | Value: Implementation specific |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. You can modify this characteristic only when the entity is disabled. Also, you can only increase the characteristic value.
Default: 4 | Value: 1--255 |
This characteristic is not supported if either of the following conditions is true:
You cannot modify this characteristic.
Default: Automatic | Value: See description |
active | The state is locked to active. |
automatic | The state varies according to the operation of the polling algorithm. |
dead | The state is locked to dead. |
dying | The state is locked to dying. |
inactive | The state is locked to inactive. |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 0 | Value: 0--65535 |
This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control.
Default: 1 | Value: 1--255 |
buffers temporarily unavailable
Number of times the local station could not service messages from the remote station because there were no receive buffers available.buffers too small
Number of times the local station could not service messages from the remote station because the receive buffers were not large enough.creation time
Time at which this entity was created.incomplete replies to select
Number of selection intervals that were not properly terminated (that is, by a message with the Select bit set in the header), during which a transmission was received or an attempt at transmission was detected.This counter is supported only if the protocol characteristic of the owning ddcmp link entity is set to control, or when the link is a half-duplex, point-to-point link.
local reply timeouts
Number of times the local station failed to receive an acknowledgment before the reply timer expired.locally initiated state changes
Number of times the station protocol state changed through action of the local station.naks received indicating buffer too small
Number of times the remote station reported that it could not service a message because the receive buffer was not large enough.naks received indicating buffers temporarily unavailable
Number of times the remote station reported that it could not service a message because no receive buffer was available.naks received indicating data field block check error
Number of times the remote station reported that a block check error was detected in the data field of an incoming message.naks received indicating header block check error
Number of times the remote station reported that a block check error was detected in the header block of an incoming message.naks received indicating rep response
Number of times the remote station reported that it did not receive all the messages sent from the local station.naks sent with rep response
Number of times the local station detected that not all of the messages sent from the remote station were received correctly.no replies to select
Number of times the select timer expired for any of the following reasons:
- No valid control message was received.
- No valid header to a data message was received.
- No valid header to a maintenance message from the selected station was received.
- No transmission from the remote station was received.
This counter is supported only if the protocol characteristic of the owning ddcmp link entity is set to control, or when the link is a half-duplex, point-to-point link.
pdus received with data field check block error
Number of messages received with a check error in the data field.pdus received with header block check error
Number of messages received with a check error in the header block.receive error thresholds reached
Number of times the receive error threshold has been reached.remote reply timeouts
Number of times the local station received a REP message and sent an acknowledgment in return. This sequence indicates that all messages sent from the remote station have been correctly received.remotely initiated state changes
Number of changes in the station protocol state caused by action of the remote station.sdu octets received
Number of data octets received from the remote station.sdu octets sent
Number of data octets sent to the remote station.sdus received
Number of data messages received from the remote station (not including retransmissions).sdus sent
Number of data messages sent to the remote station (not including retransmissions).selection error thresholds reached
Number of times the selection error threshold has been reached.This counter is not supported if the characteristic protocol of the owning ddcmp link entity is set to tributary.
selection intervals
Number of times the local station selected the remote or a tributary station. The counter does not appear if the link uses the tributary protocol. In addition, the counter appears only when the local station is the control station for a number of tributaries, or is operating over a half-duplex, point-to-point link.This counter is supported only if the protocol characteristic of the owning ddcmp link entity is set to control, or when the link is a half-duplex, point-to-point link.
send error thresholds reached
Number of times the send error threshold has been reached.strts received while in maintenance
Number of times the local station received a STRT protocol message while in the Maintenance state.
name
Simple name assigned to the link logical station when it is created.
polling substate
State of a tributary as determined by the polling algorithm. This attribute applies only when the value of the link's protocol characteristic is set to control. The value of this attribute is affected by the value of the characteristic polling state. If the characteristic polling state is set to automatic, the value of this status attribute reflects the current state of the polling algorithm. For all other values of the polling state characteristic, the values of both attributes are the same.
active The tributary is active and responds with data when selected. dead The tributary did not respond when selected within the appropriate timeout period, when already in the Dying or Inactive state. The tributary is ignored until the station reinitializes. dying The tributary, currently in the Inactive or Active state, has not responded within the appropriate timeout period when selected. inactive The tributary has not sent any data when selected by the control station. However, the tributary has responded with an appropriate message when selected. protocol state
State of the data link protocol with the remote station.
halted The protocol is stopped and no messages are being exchanged with the remote station. maintenance The protocol is off line and dealing with maintenance messages only. running The protocol is on line and exchanging messages with the remote station. starting There is an attempt to initialize the protocol between the local and remote stations. This uses the STRT and STACK PDUs. state
Operational state of the local logical station.
off The station is disabled. on The station is enabled. uid
Entity's unique identifier, which is generated when the entity is created.
buffer too small
Generated each time a message is received whose data field is larger than the buffers available on the local station.Arguments:
buffer size Size of the receive buffer at the local station. count Size of the received data message as specified in the message header. locally initiated state change
Generated each time the state of the local station changes as a result of action on the local node.Arguments:
new state New value of the logical station's protocol state attribute. old state Previous value of the logical station's protocol state attribute. receive error threshold reached
Generated each time the number of consecutive receive-related errors reaches the receive error threshold limit of 7.remotely initiated state change
Generated each time the state of the link changes as a result of action on the remote node.Arguments:
new state New value of the logical station's protocol state attribute. old state Previous value of the logical station's protocol state attribute. selection error threshold reached
Generated each time the number of consecutive selection-related errors reaches the selection error threshold limit of 7. This event is supported only when the protocol characteristic of the owning ddcmp link entity is set to control, or when the link is half-duplex, point-to-point.send error threshold reached
Generated each time the number of consecutive transmit-related errors reaches the transmit error threshold limit of 7.strt received while in maintenance
Generated each time a strt message is received while the value of the status attribute protocol state of the local station is set to maintenance.
For create:
already exists
A ddcmp link logical station entity already exists.maximum stations exceeded
The station cannot be created because there are already the maximum stations defined for this link. This can occur when there is already one logical station defined for that link.For delete:
wrong state
Failure to delete the DDCMP link logical station because the logical station must be disabled before deletion.
name
Simple name assigned to the port when it is created.
client
Name of the client entity.link
Name of the DDCMP link that the client is using.logical station
Name of the DDCMP link logical station supplied by the client when the port was opened.state
State of the port.
call attached The port is assigned to a client and the link is associated with the current call on the line. Applies only when the link operates over a switched line. open The port is assigned to a client. open disabled The port is assigned to a client, but the link or logical station entity used by the port is disabled. type
Type of port.
normal For normal data communications. service For service operations. This is the value that modules such as MOP would use.
This chapter describes all the commands you can use to manage the entities that constitute the Device module. The Device module provides management of physical devices attached to a network system that must load microcode from a host system before it is operational.
Note
For Digital UNIX, the product DEC WAN Device Drivers is provided as an installable subset within the product X.25 for Digital UNIX systems. You must install this subset before you can refer to the LAPB module entities in an NCL command.
Figure 6-1 shows the hierarchical relationship of the entities that constitute the Device module.
Figure 6-1 Hierarchy of Device Module Entities
version
Version of the device architecture to which the implementation conforms. You cannot modify this characteristic.
uid
Entity's unique identifier, which is generated when the entity is created.
For create:
already exists
A device entity already exists.For delete:
has children
Cannot delete while subentities exist.
dump
Dumps the device corresponding to the unit subentity.load
Loads the device corresponding to the unit subentity.
name device-name
The physical device this device unit entity controls.
auto load
Specifies whether the device should try to load its microcode without management intervention. Autoloading would occur after initialization, a failure, or a dump.
Default: True Value: True or false device
Physical device to which this device unit entity is related. The value of this characteristic is a copy of the name argument specified when this entity is created.dump destination
File specification to hold the contents of the device's microcode when a dump occurs.For Digital UNIX, the default value for the dump destination is /usr/var/xxx.dump where xxx is the device specification. For example: /usr/var/dsv.dump.
dump on error
Whether a device should try to dump its microcode after a device failure. Set this characteristic only for those devices that support the dump operation.
Default: False Value: True or false load source
File specification that contains the device's microcode. This is used during a load operation.
Default: None Value: File specification For Digital UNIX, the default value is /usr/var/xxx.firmware, where xxx is the device specification. For example: /usr/var/dsv.firmware.
creation time
Time at which this entity was created.device failures
Number of times the unit has failed.failed dumps
Number of times an attempt to dump the device's microcode has failed.failed loads
Number of times an attempt to load the device's microcode has failed.forced dumps
Number of times the dump command has been used to force the device to dump its microcode.forced loads
Number of times the load command has been used to load the device's microcode.successful dumps
Number of times the device has successfully dumped its microcode.successful loads
Number of times the device has successfully loaded its microcode.
name
Simple name assigned to the device unit when it is created.
firmware identifier
Implementation-specific string that identifies the firmware loaded into a device.operational communication port (OpenVMS)
Specifies which channels of a multiple-line device unit are determined to be working by the module self-test. Each name identifies a working device communication port. Channels that are not named are not operational.state
Current state of the communications device.
disabled The device unit entity has been created, but an enable directive has not yet been issued. dump failed An attempt to dump the device's microcode has failed. This value appears only if the characteristic auto load is false. dumping An attempt to dump the device's microcode is in progress. load failed An attempt to load the device's microcode has failed. This value appears only if auto load is false. loading An attempt to load the device's microcode is in progress. running The device's microcode has been loaded and the device is ready to send and receive data. stopped This state can occur in one of the following circumstances:
- The device entity unit has been enabled and auto load is false.
- The device has been reinitialized by the system.
- The device failed, a dump operation has completed (the characteristic auto dump is true, but the characteristic auto load is false.)
uid
Entity's unique identifier, which is generated when the entity is created.
device failure
Generated each time a failure is detected on a device.Arguments:
failure reason Reason for the device failure. The values of this argument are implementation specific. firmware identifier Identifier of the device's microcode. next state Next state of the device. This depends on the values of the auto load and dump on error characteristics. dumping The entity will try to dump the device's microcode. loading The entity will try to load the device's microcode. stopped The entity will stop, awaiting a dump or load command.
Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]
![]()
NCL_PROFILE_005.HTML OSSG Documentation 2-DEC-1996 12:47:44.12Copyright © Digital Equipment Corporation 1996. All Rights Reserved.