1 show You use the show command to display the value of one or more attributes of an entity. The general form of a show command is: ncl> show entity-name attribute-specifier,... An attribute-specifier can be the name of a particular attribute; for example: ncl> show node 0 ddcmp link link-5 protocol,transmit underruns,state displays the following attributes of the entity ddcmp link link-5: o The characteristic protocol o The counter transmit underruns o The status state An attribute-specifier can also specify an entire class of attributes, as follows: o all [attributes] o all characteristics o all counters o all identifiers o all status For example: ncl> show node 0 ddcmp link link-5 all counters, all status displays all counters and status attributes of the entity ddcmp link link-5. You can combine individual attribute names and attribute class names; for example: ncl> show node 0 ddcmp link link-5 protocol, all counters displays the value of the characteristic protocol and the value of all counters. There are a few attributes whose value cannot be displayed. These are usually attributes that represent secure information, such as passwords. The local node (node 0) is implied if no other node is specified. Therefore, "show implementation" is equivalent to "show node 0 implementation", which is the command used to show the DECnet and operating system versions of the local node. Select an entity below for more information on the showable attribute groups for that entity. Or if you wish to quickly view all the showable attributes of a particular entity at once, you may use the wildcard character. For example, to view the showable attributes of osi transport, you could enter "osi_tranport *" at the following "SHOW Subtopic?" prompt. 2 alias_(OpenVMS) show [node node-id] alias creation time all [attributes] all counters Example: show alias all 3 Counters o creation time Specifies the time at which the entity was created. 3 port show [node node-id] alias - port port-name attribute [,attribute...] all [attributes] all identifiers all status all characteristics all counters Example: show alias port * all 4 Characteristics o selection weight The number of sequential incoming connects to be passed to this member node in the round-robin sequence before proceeding to the next member node in the sequence. A value of zero means this node is not eligible to receive incoming connections to this alias address. Selection Weight is used to apportion incoming alias connections according to the capacity of each alias member. Nodes with greater capacity should have larger values of Selection Weight, while local area VMScluster satellities should generally have a value of zero. Values between 0 and 10 are suggested. NOTE The nsp maximum transport connection value determines the number of connections on an alias member. If the Alias Port is enabled, changing the nsp maximum transport connection value has no effect. o outgoing default Default: False Value: Boolean Controls whether this alias is to be used as the default alias for this node. If true, this alias node name will be used for connect requests on an outgoing connection from a session control application with the outgoing alias attribute set to true. 4 Counter o creation time Specifies the time at which the entity was created. 4 Identifier o name This string is the Port Identifier. If DECdns is in use, it is also the DECdns-registered node object name of the Alias psuedo-node. 4 Status o node-id The 6-byte node id field in the Alias pseudo-node's NSAP. o state Specifies the status of the alias entity. off The alias entity is enabled on The alias entity is enabled 2 csma-cd show [node node-id] csma-cd version all [attributes] all characteristics Example: show csma-cd all 3 Characteristic o version Default: Current version number Version number of the CSMA/CD Data Link architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 port show [node node-id] csma-cd - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status The port-name can be either a simple name to uniquely identify a particular PORT instance, or a wildcard to identify multiple PORT instances. Examples: show csma-cd port CSMACD$ETA_0010 all show csma-cd port * all 4 Counters Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers. o creation time Time at which the port was created. o multicast octets received Number of multicast data octets that were successfully received and made available to the port user. The count is the number of octets in the CSMA/CD user data field and does not include MAC (medium access control, a sublayer of the CSMA/CD Data Link layer) headers. Comparing this count to the octets received count yields the gross percentage of bandwidth that was consumed (over time) by multicast PDUs received by the port. o multicast octets sent Number of multicast data octets that were successfully sent through the port. The count is the number of octets in the MAC user data field, including any padding or length fields; it does not include MAC headers. Comparing this count to the octets sent count yields the gross percentage of bandwidth that was consumed (over time) by multicast pdus transmitted by the port. o multicast pdus received Number of multicast PDUs that were successfully received and made available to the port user. Counted PDUs passed address and protocol filtering and were received without errors. Comparing this count to the pdus received count yields a gross percentage of CSMA/CD usage for multicast pdus received by this port. o multicast pdus sent Number of multicast PDUs that were successfully sent through the port. Comparing this count to the pdus sent count yields a gross percentage of CSMA/CD usage for multicast pdus sent by this port. o octets received Total number of MAC user data octets that were successfully received and made available to the port user. Counted frames passed address and protocol filtering for both individual and multicast MAC addresses and were received without errors. The count is the number of octets in the CSMA/CD user data field plus any padding, Ethernet length fields, or logical link control (LLC) header fields; it does not include MAC headers. Adding the octets received count to the protocol overhead calculated from the pdus received count yields the amount of CSMA/CD bandwidth consumed by frames received by the port. o octets sent Total number of user data octets that were successfully sent through the port. The count is the number of octets in the MAC user data field including any padding or length fields; it does not include MAC headers. Adding the octets sent count to the protocol overhead calculated from the pdus sent count yields the amount of CSMA/CD bandwidth consumed (over time) by frames sent by the port. o pdus received Total number of PDUs that were successfully received and made available to the port user. Counted PDUs passed address and protocol filtering and were received without errors. The count provides a gross measurement of incoming CSMA/CD usage by the port. o pdus sent Total number of PDUs that were successfully sent through the port. The count provides a gross measurement of outgoing CSMA/CD usage by the port. o unavailable user buffers Number of times that no user buffer was available at the port for an incoming frame that passed all filtering for the port. Used in conjunction with the pdus received count, this counter can indicate the rate of user buffer receive problems. 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client Name specified by the data link user when the port was opened. o ethernet protocol types Set of Ethernet protocol types that are currently recognized for this port. o length present The data link adds (1) a length field on transmit frames, and (2) assumes the presence of a length field and attempts to remove it on received Ethernet frames. When false, the data link does not add and remove length fields. This attribute is irrelevant for ISO 8802-3 formatted frames, which always have a length field. false The data link does not add and remove length fields. true The data link adds and removes length fields. o llc sap addresses Set of individual and group logical link control (LLC) service access point (SAP) addresses that are currently recognized for this port. o llc service Type of LLC (logical link control) PDU processing that is required on the port (as defined by the user when the port was opened). class 1 The data link provides class 1, type 1 service. user- The user is responsible for handling the LLC supplied protocol. o mac addresses Set of individual and multicast MAC (medium access control) addresses that are currently recognized for this port. o receive mode Type of receive mode that is currently enabled for the port. normal The port receives only those frames that meet the normal address and protocol filtering requirements requested by the user. promiscuous The port receives all frames regardless of format and MAC address. o snap protocol identifiers Set of subnetwork access protocol (SNAP) identifiers that are currently recognized for this port. o station Name of the station associated with this port as specified by the user when the port was opened. o uid Entity's unique identifier, which is generated when the port is created. 3 station show [node node-id] csma-cd - station station-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show csma-cd station * station buffers show csma-cd station * all show csma-cd station csmacd-1 all 4 Characteristic o station buffers Default: implementation specific Value: 1-64 Number of receive buffers reserved for the station. You cannot modify this characteristic. 4 Counters Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers. o alignment errors Number of times a received frame did not contain an integral number of octets. o carrier check failures Number of times the data link did not sense the receive carrier signal or detected an error in the receive carrier signal during transmission of a frame. o collision detect check failures Number of times the collision detect test signal was not sensed after a transmission. If this count approximates the number of frames sent, either the collision detect circuitry is not working correctly or the test signal is not implemented. o creation time Time at which the station was created. o data overruns Number of times the hardware lost one or more consecutive, partially complete, incoming frames because it could not keep up with the incoming frame rate. Used in conjunction with pdus received, this count provides a measure of hardware resource and bandwidth failures. o excessive collisions Number of times a transmission failed because the maximum allowable number of retransmission attempts all culminated in collisions. o frame check errors Number of times a received frame containing an integral number of octets failed the frame check sequence (FCS). o frame size errors Number of times the user requested transmission of a frame outside the range of valid frame sizes. o frames too long Number of times a received frame exceeded the maximum length allowed by CSMA/CD medium access control. o initially deferred pdus sent Number of times a PDU was deferred by the station access algorithm on the first attempt at transmission, but was then transmitted successfully without collision. Used in conjunction with pdus sent, this count measures the rate of CSMA/CD contention with no collisions. o late collisions Number of times a collision was detected after the allotted time for collisions had expired. o multicast octets received Number of multicast data octets that were successfully received. The count is the number of octets in the CSMA/CD user data field and does not include MAC headers. Comparing this count to the octets received count yields the gross percentage of bandwidth that was consumed (over time) by multicast frames received by the local system. o multicast octets sent Number of multicast data octets that were successfully sent. The count is the number of octets in the MAC user data field, including any padding or length fields; it does not include MAC headers. Comparing this count to the octets sent count yields the gross percentage of bandwidth that was consumed (over time) by multicast frames transmitted by the local system. o multicast pdus received Number of multicast PDUs that were successfully received. Comparing this count to the pdus received count yields a gross percentage of CSMA/CD usage for multicast PDUs received by this system. o multicast pdus sent Number of multicast PDUs that were successfully sent. Comparing this count to the pdus sent count yields a gross percentage of CSMA/CD usage for multicast PDUs sent by this system. o multiple collisions pdus sent Number of times a PDU was successfully transmitted on the third or later attempt by the station access algorithm after normal collisions on previous attempts. Used in conjunction with pdus sent, this count provides a measure of CSMA/CD media contention at a level where there are collisions and the backoff algorithm no longer works efficiently. o octets received Total number of MAC user data octets that were successfully received from frames that passed address and protocol filtering for both individual and multicast MAC addresses. The count is the number of octets in the CSMA/CD user data field plus any padding, Ethernet length fields, or LLC header fields; it does not include MAC headers. Adding the octets received count to the protocol overhead calculated from the pdus received count yields the amount of CSMA/CD bandwidth consumed by frames received by the local system. o octets sent Total number of user data octets that were successfully sent. The count is the number of octets in the MAC user data field including any padding or length fields; it does not include MAC headers. Adding the octets sent count to the protocol overhead calculated from the pdus sent count yields the amount of CSMA /CD bandwidth consumed (over time) by frames sent by the local system. o pdus received Total number of PDUs that passed address and protocol filtering and were received without errors. The count provides a gross measurement of incoming CSMA/CD usage by the local system; this information can be used in conjunction with other counters to approximate the average receive frame size or to determine the ratio of errors to successful receives. o pdus sent Total number of PDUs successfully sent. The count provides a gross measurement of outgoing CSMA/CD usage by the local system; this information can be used in conjunction with other counters to approximate the average transmit frame size or to determine the ratio of errors to successful transmissions. o receive data length errors Number of times a frame was received with a length field value that was invalid for the number of octets actually received by medium access control. o send data length errors Number of times the user requested transmission of an 802.3 frame with a length field value that was not valid for the number of octets actually passed. o single collision pdus sent Number of times a PDU was successfully transmitted on the second attempt by the station access algorithm after a normal collision occurred on the first attempt. Used in conjunction with pdus sent, this count provides a measure of CSMA/CD media contention at a level where there are collisions, but the backoff algorithm still works efficiently. o station failures Number of times that the station self-testing procedures reported failure. o unavailable station buffers Number of times a complete, fully received PDU was discarded because no station buffer was available. Used with pdus received, this count provides a measure of receive problems related to the station buffer. o unavailable user buffers Number of times no user buffer was available for an incoming frame that passed all filtering for the port. Used in conjunction with the pdus received count, this counter can indicate the rate of user buffer receive problems. o unrecognized individual destination pdus Number of times a received PDU with an individual destination MAC address was discarded because there was no port with the correct Ethernet protocol type, SNAP protocol identifier, or link logical control SAP address enabled. o unrecognized multicast destination pdus Number of times a received PDU with a multicast destination MAC address was discarded because there was no port with the correct Ethernet protocol type, SNAP protocol identifier, or link logical control SAP address enabled. 4 Identifier o name Simple name assigned to the station when it is created. 4 Status o address filters All individual MAC addresses currently enabled by any of the ports on the station. o communication port DECnet-Plus device name for the station. o hardware address Individual medium access control (MAC) address that was assigned during manufacture of the communications hardware that is associated with the station. o mac address Current MAC address (if any) of the station. For more information about the MAC address, see the enable command. o receive mode Current receive mode for the station. Some stations may not support all modes. normal The station receives only those frames (individual and multicast) that meet the normal format, protocol, and access control requirements. all The station receives all individual-addressed multicast frames that meet the normal format, protocol, and address requirements, and all multicast-addressed frames regardless of their format, protocol, and address types. This function is only supported on OpenVMS. promiscuous The station receives all frames (individual and multicast) regardless of format, Ethernet protocol type, SNAP identifier, LLC SAP address, or MAC address. This function is only supported on OpenVMS. o state Operational state of the station. failed Either an attempt to enable the station failed during the self-test or the station was on and the data link determined that the station would now fail the self-test. initializing The station is currently being initialized and tested by the data link. off The station is disabled. on The station is enabled and available for use. For more information on station states, see the Network Management manual. o uid Entity's unique identifier, which is generated when the station is created. 2 ddcmp_(OpenVMS_VAX) show [node node-id] ddcmp dna version all [attributes] all characteristics Example: show ddcmp all 3 Characteristic o dna version Version number of the DDCMP architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 link show [node node-id] ddcmp - link link-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show ddcmp link * name show ddcmp link ddcmp-0 all char 4 Characteristics o dead timer Default: 10000 Value: 1-65535 Specifies the delay, in milliseconds, between polls of one of the set of dead tributaries. This attribute is supported only if the characteristic protocol is set to control. o delay timer Default: 0 Value: 0-65535 Specifies the minimum delay, in milliseconds, between polls. You can use this timer to limit the effect of a fast control station on slower tributaries. A value of 0 means that no delay is added. This attribute is supported only if the characteristic protocol is set to control. o physical line Default: No name Value: Local entity name Name of the Physical layer entity that the link operates over. A value for this characteristic must be set before the link entity is enabled. You can modify this characteristic only when the entity is disabled. o protocol Default: Point Value: See following description Protocol mode used by the local station. You cannot modify this characteristic. The value of this characteristic is a copy of the protocol argument specified when the ddcmp link entity is created. The default value is point and is the only permissible value. o receive buffers Default: 4 Value: 1-255 Specifies the number of receive buffers reserved for the link. You can modify this characteristic only when the entity is disabled. Also, you can only increase the characteristic value. o retransmit timer Default: 3000 Value: 1-65535 Maximum time (in milliseconds) to wait between sending a message and receiving a valid response. If this time expires, the local station takes error recovery action. On full-duplex point-to- point links, the timer is started immediately when a message is sent. o scheduling timer Default: 200 Value: 50-65535 Specifies the time, in milliseconds, between the recalculation of tributary polling priorities. This attribute is supported only if the characteristic protocol is set to control. o stream timer Default: 6000 Value: 0-65535 Specifies the time, in milliseconds, for which a tributary or the remote station (on a half-duplex point-to-point link) can hold the line. This characteristic is not supported if the characteristic protocol is set to tributary. 4 Counters o creation time Time at which this entity was created. o naks received indicating message header format error Number of NAK messages received that report errors in message headers sent from the local station. o naks received indicating receive overrun Number of NAK messages received that report a receive overrun at the remote station. o pdus received with message header format error Number of times the local station detected an error in a message header. o receive overruns Number of times the local station detected a receive overrun. o selection address errors Number of times that the controller of a multipoint link received a message with an address other than that of the currently selected station. This counter is supported only if the characteristic protocol is set to control. o streaming tributaries Number of times that the remote station (or a tributary station) exceeded the maximum transmission interval without releasing the line, or failed to release the line after sending a message with the select flag set. This counter is present only on half- duplex, point-to-point links, or when the local station is a controller of a multipoint link. This counter is not supported if the protocol characteristic is set to tributary. o transmit underruns Number of times the local station detected a transmit underrun. 4 Identifier o name Simple name assigned to the link when it is created. 4 Status o physical port Name of the port entity in the Physical layer returned when the port is opened. If this is null, the port is not open. o state State of the DDCMP link. The value of this attribute is determined by the enable and disable commands. off The entity is disabled. on The entity is enabled. In addition the link is disabled and its state set to off if the Physical layer port that the link uses is deleted. o uid Entity's unique identifier, which is generated when the entity is created. 4 logical_station show [node node-id] ddcmp - link link-name - logical station station-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status The link-name must be a simple name which uniquely represents a particular LINK instance. The station-name can be either a simple name which uniquely identifies a particular logical station or a wildcard which identifies multiple logical stations. Examples: show ddcmp link ddcmp-0 logical station * name show ddcmp link ddcmp-0 logical station ddcmp-0 all 5 Characteristics o active base Default: 255 Value: 0-255 Specifies the base priority to which an active tributary is reset after it has been polled. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o active increment Default: 0 Value: 0-255 Specifies the value to be added to the active tributary priority each time the scheduling timer expires. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o address Default: 1 Value: 1-255 Data link address of the remote station or tributary. You can modify this characteristic only when the entity is disabled. o babble timer Default: 6000 Value: 1-65535 Specifies the time, in milliseconds, for which a selected tributary or remote station is allowed to transmit. This characteristic is not used on full-duplex links. This characteristic is not supported if the characteristic protocol of the owning ddcmp link entity is set to tributary. o buffer source Default: Implementation-specific Value: See description Specifies the source of the receive buffers. client Buffers are provided by the client entity. supplied common pool Buffers are assigned from the common buffer pool. 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. o dead threshold Default: 8 Value: 0-255 Specifies the number of times that an active, inactive, or dying tributary is polled before its status attribute polling substate is changed to dead because of receive timeouts. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o dying base Default: 0 Value: 0-255 Specifies the base priority to which a dying tributary is reset after being polled. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o dying increment Default: 16 Value: 0-255 Specifies the value to be added to a dying tributary's priority each time the scheduling timer expires. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o dying threshold Default: 2 Value: 0-255 Specifies the number of times an active or inactive tributary is polled before its status attribute polling substate is changed to dying because of receive timeouts. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o holdback timer Default: 0 Value: 0-13000 Maximum time (in milliseconds) that the local station can delay acknowledging a received message if there is no data to send. 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. o inactive base Default: 0 Value: 0-255 Specifies the priority to which an inactive tributary is reset after it has been polled. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o inactive increment Default: 64 Value: 0-255 Specifies the value to be added to an inactive tributary's priority each time the scheduling timer expires. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o inactive threshold Default: 8 Value: 0-255 Specifies the number of times an active tributary is polled before its status attribute polling substate is changed to inactive because of no data response. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o maximum buffers Default: 4 Value: Implementation specific Specifies the maximum number of buffers that a tributary can use from the common buffer pool. A value of 0 means that there is no limit to the number of buffers that can be used. This characteristic is supported only if the buffer source characteristic is set to common pool. 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. o maximum transmit Default: 4 Value: 1-255 Specifies the maximum number of messages that a tributary or a remote half-duplex station can send at one time. The value of this characteristic must be greater than or equal to that of transmit window on the selected station. This characteristic is not supported if either of the following conditions is true: o The characteristic protocol of the owning ddcmp link entity is set to tributary. o The communications link is full-duplex and point-to-point. You cannot modify this characteristic. o polling state Default: Automatic Value: See description. Specifies the effect of the local station's polling algorithm on the state of a tributary. The value of this characteristic is reflected in the value of the status attribute polling substate. 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. o transmit timer Default: 0 Value: 0-65535 Specifies the time, in milliseconds, that the local station waits between data transmissions. This characteristic is supported only if the characteristic protocol of the owning ddcmp link entity is set to control. o transmit window Default: 1 Value: 1-255 Specifies the maximum number of data messages that the local station can send without receiving an acknowledgment. This characteristic applies only when the remote station is a control station or on a half-duplex, point-to-point link. The value of this characteristic must be less than or equal to the equivalent of the maximum transmit characteristic on the control station or remote station. 5 Counters o buffers temporarily unavailable Number of times the local station could not service messages from the remote station because there were no receive buffers available. o 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. o creation time Time at which this entity was created. o incomplete replies to select Specifies the 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. o local reply timeouts Number of times the local station failed to receive an acknowledgment before the reply timer expired. o locally initiated state changes Number of times that the station protocol state changed through action of the local station. o 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. o 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. o 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. o 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. o 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. o naks sent with rep response Number of times that the local station detected that not all of the messages sent from the remote station were received correctly. o no replies to select Specifies the number of times that the select timer expired for any of the following reasons: o No valid control message was received. o No valid header to a data message was received. o No valid header to a maintenance message from the selected station was received. o 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. o pdus received with data field check block error Number of messages received with a check error in the data field. o pdus received with header block check error Number of messages received with a check error in the header block. o receive error thresholds reached Number of times that the receive error threshold has been reached. o 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. o remotely initiated state changes Number of changes in the station protocol state caused by action of the remote station. o sdu octets received Number of data octets received from the remote station. o sdu octets sent Number of data octets sent to the remote station. o sdus received Number of data messages received from the remote station (not including retransmissions). o sdus sent Number of data messages sent to the remote station (not including retransmissions). o selection error thresholds reached Number of times that 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. o selection intervals Number of times that 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. o send error thresholds reached Number of times that the send error threshold has been reached. o strts received while in maintenance Number of times that the local station received a STRT protocol message while in the Maintenance state. 5 Identifier o name Simple name assigned to the link logical station when it is created. 5 Status o polling substate Specifies the 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 will be 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. o 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 is 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. o state Operational state of the local logical station. off The station is disabled. on The station is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] ddcmp - port port-name attribute [,attributes...] all [attributes] all identifiers all status Examples: show ddcmp port * all show ddcmp port $0 all 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client Name of the client entity. o link Name of the DDCMP link that the client is using. o logical station Name of the DDCMP link logical station supplied by the client when the port was opened. o state State of the port. call The port is assigned to a client and the link attached 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 The port is assigned to a client, but the link disabled or logical station entity used by the port is disabled. o type Type of port. normal For normal data communications. service For service operations. This is the value that modules such as MOP would use. 2 device show [node node-id] device attribute [,attribute] all [attributes] all characteristics all status Example: show device * all 3 Characteristic o version Version of the device architecture to which the implementation conforms. You cannot modify this characteristic. 3 Status o uid Entity's unique identifier, which is generated when the entity is created. 3 unit show [node node-id] device - unit simple-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Example: show device unit * name show device unit device-1 all 4 Characteristics o auto load Default: True Value: True or false Specifies whether the device should try to load its microcode without management intervention. Autoloading would occur after initialization, a failure, or a dump. o 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. o dump destination File specification to hold the contents of the device's microcode when a dump occurs. For Tru64 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. o dump on error Default: False Value: True or false 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. o load source Value: File specification File specification that contains the device's microcode. This is used during a load operation. For Tru64 UNIX, the default value is /usr/var/xxx.firmware, where xxx is the device specification. For example: /usr/var/dsv.firmware. 4 Counters o creation time Time at which this entity was created. o device failures Number of times the unit has failed. o failed dumps Number of times an attempt to dump the device's microcode has failed. o failed loads Number of times an attempt to load the device's microcode has failed. o forced dumps Number of times the dump command has been used to force the device to dump its microcode. o forced loads Number of times the load command has been used to load the device's microcode. o successful dumps Number of times the device has successfully dumped its microcode. o successful loads Number of times the device has successfully loaded its microcode. 4 Identifier o name Simple name assigned to the device unit when it is created. 4 Status o firmware identifier Implementation-specific string that identifies the firmware loaded into a device. o 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. o 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: o The device entity unit has been enabled and auto load is false. o The device has been reinitialized by the system. o The device failed, a dump operation has completed (the characteristic auto dump is true, but the characteristic auto load is false). o uid Entity's unique identifier, which is generated when the entity is created. 2 dns 3 clerk show [node node-id] dns clerk attribute [,attribute...] all all characteristics all counters all status You can also enter this command using the dns$control utility. You must have the NET$EXAMINE rights identifier on a OpenVMS system. No special privileges are required on a Tru64 Unix system. Examples: show dns clerk all show dns clerk default namespace 4 characteristics o clerk timeout Default: 60 seconds Specifies the default timeout of client interface calls. If no response is received in the specified time, an error message will be generated. o default namespace Contains the name of the clerk's default namespace. o solicit holddown Default: 15 seconds Specifies the time (in seconds) to wait after initialization before soliciting advertisements from servers. o UID Uniquely identifies the entity. o version Specifies the version of the DECdns architecture implemented by this clerk. 4 counters o athentication failures Specifies the number of times a requesting principal failed authentication procedures. o cache bypasses Specifies the number of requests to read attributes for which the clerk was specifically directed by the requesting application to bypass its own cache. Instead, a server is contacted to get the requested information. This counter does not account for requests that the clerk is unable to satisfy from the cache or for requests to look up names or enumerate the contents of directories. o cache hits Specifies the total number of read requests directed to this clerk that were satisfied entirely by the information contained in its own cache. This figure accounts only for requests to read attribute values and does not include requests to look up names or enumerate the contents of directories. o creation time Specifies the time at which this entity was created. o incompatible protocol errors Specifies the number of times this clerk received a response to one of its own requests from a server running a protocol version of DECdns software that was incompatible with the protocol version of DECdns software the clerk was running. Clerk requests directed to servers running incompatible protocol versions do not complete. o miscellaneous operations Specifies the number of operations other than read and write (that is, skulks, enumerating contents of directories, and so on) performed by this clerk. o read operations Specifies the number of lookup operations performed by this clerk. This counter accounts only for requests to read attributes and does not include name lookups or enumerations of multiple names. o write operations Specifies how many requests to modify data were processed by this clerk. 4 status o state Specifies the state of the DECdns clerk. Broken The DECdns clerk has a fatal error condition. Initial The DECdns clerk is in the process of initializing. Off The DECdns clerk is not available. On The DECdns clerk is running and available. Shut The DECdns clerk is in the process of an orderly shutdown. 4 known_namespace show [node node-id] dns clerk - known namespace namespace-ident attribute [,attribute...] all all characteristics all counters all identifiers all status You can use either the name or nscts in this command to specify the namespace-ident: name The name of the namespace. The name argument may be different from the nickname if the nickname is ambiguous. The name can contain wildcard character "*". nscts The value of the namespace creation timestamp (NSCTS) assigned to the specified namespace when it was created. The format is 14 pairs of hex digits (xx-xx). You can also enter this command using the dns$control utility. You must have the NET$EXAMINE rights identifier on a OpenVMS system. No special privileges are required on a Tru64 Unix system. Examples: show dns clerk known namespace * ! Displays the identifiers ! (both name and NSCTS) of ! all known namespace ! subentities of the local ! dns clerk. show node true dns clerk - ! Displays all the known known namespace * all ! namespace information for ! the dns clerk on node true. show dns clerk known namespace *, - ! Displays the names of all with ambiguous=true ! namespaces known to the ! local dns clerk which ! share the same nickname. 5 characteristics o UID Unique identifier for the entity. 5 counters o creation time Specifies the time at which the clerk added this known namespace to its cache. 5 identifiers o name Specifies an external, human-readable name by which the namespace can be identified. If the namespace nickname is unique, the Name is the same as the Nickname. Otherwise, the Name is generated by appending _n to the nickname for some value of n that makes it unique. The Ambiguous attribute is then set true for the known namespace. o NSCTS Specifies the creation timestamp of the namespace. 5 status o ambiguous Indicates whether the nickname for this namespace is ambiguous; that is, more than one namespace known to this clerk has the same nickname. If true, the namespace nickname is ambiguous. If false, the namespace nickname is unique. o explicit creation Specifies whether the namespace was created by a create command. If false, the namespace was created by the clerk itself. o nickname The name given to the namespace when it was created. 4 manual_nameserver show [node node-id] dns clerk - manual nameserver name attribute [,attribute...] all all characteristics all counters all identifiers all status Displays the knowledge in the clerk's cache about a server that exists across a wide area network (WAN). You can also enter this command using the dns$control utility. You must have the NET$EXAMINE rights identifier on a OpenVMS system. No special privileges are required on a Tru64 Unix system. Examples: show dns clerk manual nameserver * all show dns clerk manual nameserver DEC towers 5 characteristics o towers Specifes the address(s) of the server that this entity represents. o UID Unique identifier for the entity. 5 counters o creation time Specifies the time at which the clerk created knowledge of this server in its cache. o successful solicits The number of times the clerk made a successful solicit connection to the server and received clearinghouse advertisement data back. o failed solicits The number of times solicitation of clearinghouse advertisement data from the nameserver failed. 5 identifier o name Specifies an external, human-readable name by which the nameserver can be identified. 5 status o last solicit Indicates the time at which the clerk last tried to solicit this nameserver. 4 remote_clearinghouse show [node node-id] dns clerk - remote clearinghouse clearinghouse-name attribute [,attribute...] all all characteristics all counters all identifiers all status Displays current information about the specified remote clearinghouse. The clearinghouse-name can be a specific clearinghouse name or a complete directory specification followed by a wildcard template for matching simple names of clearinghouses. You can also enter this command using the dns$control utility. You must have the NET$EXAMINE rights identifier on a OpenVMS system. No special privileges are required on a Tru64 Unix system. Example: show dns clerk remote clearinghouse .paris2_ch all 5 characteristics o UID Identifies the remote clearinghouse entity. 5 counters o creation time Specifies the time at which this entity was created. o miscellaneous operations Specifies the number of operations other than read and write (that is, skulks, new epochs, and so on) performed by this clerk on the remote clearinghouse. o read operations Specifies the number of lookup operations of any sort performed by the clerk on the remote clearinghouse. o write operations Specifies the number of write operations performed by this clerk on the remote clearinghouse. 5 identifiers o CTS Indicates the creation timestamp (CTS) of this entity. o name Specifies the full name of the clearinghouse. 5 status o explicit creation Specifies whether the namespace was created by a create command. o towers Specifes the address(s) of the clearinghouse that this entity represents. 3 server show [node node-id] dns server attribute [,attribute...] all [characteristics] all characteristics all counters all status You can also enter this command using the dns$control utility. You must have the NET$EXAMINE rights identifier on a OpenVMS system. No special privileges are required on a Tru64 Unix system. Examples: show dns server all 4 characteristics o future skew Specifies the maximum amount of time that a timestamp can vary from local system time at the server node. This characteristic ensures data consistency. o maximum protocol version Specifies the maximum version of the DECdns clerk/server protocol that this particular DECdns server supports. o minimum protocol version Specifies the minimum version of the DECdns clerk/server protocol that this particular DECdns server supports. o UID Uniquely identifies the entity. o version Specifies the version of the architecture implemented by this server. 4 counters o authentication failures Specifies the number of times a requesting principal failed authentication procedures. o child pointer update failures Specifies the number of times the server background process was unable to contact all the clearinghouses where a replica of a particular child directory's parent directory is stored, and was therefore unable to apply the child updates that have occurred since the last skulk. This counter increases by one at each occurrence of the Cannot Update Child Pointer event. o creation time Specifies the time when the DECdns server entity was created. o crucial replica removals backed out Specifies the number of times a user attempted (from this server) to remove a replica that is crucial to the connectivity of a directory hierarchy. The server background process prevents users from accidentally disconnecting lower-level directories from higher-level directories. When it detects an attempt to remove a crucial replica, it will not execute the command to do so. This counter increases by one at each occurrence of the Crucial Replica event. o incompatible protocol errors Accounts for the total number of requests received by this server from a clerk running an incompatible protocol version. A server can communicate with any clerk running the same protocol version, or the version previous to the one it is running. This counter increases by one at each occurrence of the Incompatible Request event. o possible cycles Specifies the number of times this server followed a chain and encountered an entry already in the chain. For example, a soft link is created that points to a series of links that eventually point back to the first link, or a group which is a member of itself. This counter increases by one at occurrence of the Possible Cycles event. o read accesses Specifies the number of read operations directed to this DECdns server. o security failures Specifies the number of times the Security Failures event was generated. This counter is increased whenever a DECdns server has insufficient access rights to a directory or object to perform either a client-requested action or a background operation. o skulks completed Specifies the number of skulks that were successfully completed by this DECdns server. o Skulks Initiated Specifies the number of skulks that were initiated by this DECdns server. o times loopup paths broken Specifies the number of broken connections between clearinghouses on this server and clearinghouses closer to the root. Incoming requests to this server that require a downward lookup in the directory hierarchy may still succeed, but requests requiring lookup in directories closer to the root will fail. This counter increases by one at each occurrence of the Broken Lookup Paths event. o write accesses Specifies the number of write operations to this DECdns server. 4 status o state Specifies the state of the DECdns server. Broken The server has a fatal error condition. Initial The server is initializing. Off The server is not available. On The server is running and available. Shut The server is undergoing an orderly shutdown. 4 clearinghouse show [node node-id] dns server - clearinghouse clearinghouse-name attribute [,attribute...] all all characteristics all counters all identifiers all status Displays current information about the specified clearinghouse. The clearinghouse-name can be a specific clearinghouse name or a complete directory specification followed by a wildcard template for matching simple names of clearinghouses. You can also enter this command using the dns$control utility. You need read access to the clearinghouse to display a list of known attributes or the value of an attribute. You must have the NET$EXAMINE rights identifier on a OpenVMS system. No special privileges are required on a Tru64 Unix system. Examples: show dns server clearinghouse .paris2_ch all show dns server clearinghouse * 5 characteristic o CTS Indicates the creation timestamp (CTS) of this clearinghouse. o UID Uniquely identifies this entity. 5 counters o creation time Specifies the time when the clearinghouse entity was created. o data corruptions Specifies the number of times that the Data Corruption event was generated. o disable counts Specifies the number of times that the clearinghouse was disabled since it was last started. o enable counts Specifies the number of times that the clearinghouse was enabled since it was last started. o read accesses Specifies the number of read operations directed to this clearinghouse. o references returned Specifies the number of requests directed to this clearinghouse that resulted in the return of a partial answer instead of satisfying the client's request. o skulk failures Specifies the number of times that a skulk of a directory, initiated from this clearinghouse, failed to complete -- usually because one of the replicas in the replica set was unreachable. o times clearinhouse entry missing Specifies the number of times the Clearinghouse Entry Missing event was generated. o times root not reachable Specifies the number of times the Root Lost event was generated. o upgrades not possible Specifies the number of times that the clearinghouse tried to upgrade a directory and failed. o write accesses Specifies the number of write operations directed to this clearinghouse. 5 identifiers o name Specifies the full name of the clearinghouse. 5 status o state Specifies the state of the clearinghouse. Broken The clearinghouse has a fatal error condition. Initial The clearinghouse is in the process of initializing. Off The clearinghouse is not available. On The clearinghouse is running and available. Shut The clearinghouse is in the process of an orderly shutdown. 2 dtss show [node node-id] dtss attribute [,attribute...] all [characteristics] all characteristics all counters all status Examples: show dtss type show dtss all 3 Characteristics o acting courier role Default: noncourier Value: courier or noncourier Specifies whether a backup courier is currently functioning as a courier. If the role is noncourier, then the node is not attempting to synchronize with global servers. o advertisement interval Default: 0-01:30:00.000 Value: 0-00:00:30.000-99-99:99:99.999 Specifies the amount of time between a server's advertisement broadcasts. o check interval Default: 0-01:30:00.00 Value: 0-00:00:30.000-99-99:99:99.999 Specifies the amount of time between checks for faulty servers. Applicable only to servers that have external time-providers. o clock adjustment rate Specifies the rate at which the DECdts server or clerk entity adjusts the node's clock during a synchronization. o courier role Default: noncourier Value: See following description. Specifies a server's interaction with the set of global servers. backup courier The local server becomes a courier if none are available on the LAN. courier The local server synchronizes with the global set of servers. noncourier The local server does not routinely synchronize with the global set of servers. o DNA Version Specifies the Distributed Network Architecture version to which the DECdts software conforms. o DTSS Version Specifies the DTSS module/DECdts software version installed on the node. o epoch number Default: 0 Value: 0-255 Specifies the server's epoch number. The change command modifies this characteristic. o error tolerance Default: 0-00:10:00.000 Value: 0-00:00:00.500-99-99:99:99.999 Specifies the maximum separation allowed between the local clock and the computed time before synchronizations become abrupt rather than gradual (monotonic). o global directory Specifies the full name of the DECdns directory that contains the list of DECdts servers that belong to the global set. o lan timeout Default: 0-00:00:02.000 Value: 0-00:00:01.000-0-00:05:00.000 Specifies the amount of time the node waits for a response to a synchronization request before sending another request or declaring a server to be unavailable. The node sends three requests before declaring a non-responding server to be unavailable. o maximum clock drift rate Specifies the worst case drift rate of the node's clock, in nanoseconds per second, as determined by the manufacturer's specifications. o maximum inaccuracy Default: 0-00:01:40.00 Value: 0-00:00:00.0 - 99 99:99:99.99 Specifies the inaccuracy limit for the node. When the node exceeds the maximum inaccuracy setting, it attempts to synchronize. o query attempts Default: 3 Value: 1-10 Specifies the number of attempts that a node makes to contact a server before the node considers the server unavailable. o servers required Default: 3 (servers) Value: 1-32 1 (clerks) Specifies the minimum number of servers the specified node must successfully query for time values before it can synchronize. o synchronization hold down Default: 0-00:10:00.0(Clerks) Value: 0-00:00:30.0- 01 00:00:00.00 0-00:02.00.0-(Servers) Specifies the interval a node must wait to synchronize. Also specifies synchronization frequency when a node reaches the value specified by the maximum inaccuracy characteristic. o time provider present Default: false Value: True or false Specifies whether or not the entity used an external time-provider at the last synchronization. This attribute applies to servers only. o time representation version Specifies the timestamp version (format) used by the installed DECdts software. o type Specifies whether the node is a DECdts server or clerk. The create command modifies this characteristic. o wan timeout Default: 0-00:00:15.000 Value: 0-00:00:01.000-0-00:10:00.000 Specifies the amount of time the node waits for a response to a WAN synchronization request before sending another request and declaring a global server to be unavailable. The node sends three requests before declaring a non-responding global server to be unavailable. 3 Counters o clock settings Specifies the number of times that the node clock has been set nonmonotonically (abruptly). o creation time Specifies the time at which the DECdts entity was created and the counters were initialized. o different epochs detected Specifies the number of times that the node received time response messages from servers or clerks that had epoch numbers different from its own. o disable directives completed Specifies the number of times that DECdts has been disabled. o enable directives completed Specifies the number of times that DECdts has been enabled. o epoch changes completed Specifies the number of times that the server's epoch has changed. o insufficient resources detected Specifies the number of times that the node has been unable to allocate virtual memory. o invalid messages detected Specifies the number of times that the local node failed to process a received message that had an unknown message type or incorrect length. o local times not intersecting Specifies the number of times that the node's time interval failed to intersect with the computed interval of the servers. o no global servers detected Specifies the number of times that the courier server could not contact any global servers. o protocol mismatches detected Specifies the number of times that the local node failed to process a received message containing an incompatible protocol version. o server times not intersecting Specifies the number of times that a server has detected faulty servers (other than itself). o servers not responding Specifies the number of times that the courier server could not contact a specific global server. o synchronizations completed Specifies the number of times that the node has successfully synchronized. o system errors detected Specifies the number of times a DECdts operation has detected a system error. o time provider failures detected Specifies the number of times that the external time-provider signaled a failure or the node was unable to access the time- provider. o time representation mismatches detected Specifies the number of times that the local node failed to process a received message containing an incompatible timestamp format. o too few servers detected Specifies the number of times that a node failed to synchronize because it could not contact the required minimum number of servers. o too many servers detected Specifies the number of times that the responses to a synchronization request overflowed the assigned system buffer. o updates initiated Specifies the number of times that a server has attempted to update its clock. 3 Status o current time Specifies the current time on the node. o last synchronization Specifies the computed time at the last synchronization. o state Specifies the state of the DECdts software. Off The DECdts process is disabled. On The DECdts process is enabled. Synchronizing The DECdts process is synchronizing. Updating The DECdts process is updating the time. o uid Specifies the entity's unique identifier, which is generated when the entity is created. 3 decnet_global_server show [node node-id] dtss - decnet global server fullname attribute [,attribute...] all [attributes] all characteristics all identifiers all status Examples: show dtss decnet global server * - last time polled, last observed time show dtss decnet global server * all show dtss decnet - global server DEC:.DTSS_GlobalTimeServers.lkg-crackl all 4 Characteristic o transport Specifies the transport protocol used by the global server. You cannot modify this characteristic. 4 Identifier o name Specifies the full name of the global server, as registered in the namespace. 4 Status o last observed skew Specifies the skew between the node's clock and the time received from the specified global server after the most recent synchronization. o last observed time Specifies the time the node last received from the specified global server. o last time polled Specifies the time that the node last solicited a time value from the specified global server. o used in last synchronization Specifies whether or not a time value from the specified global server was used in the node's last clock synchronization. 3 decnet_local_server show [node node-id] dtss - decnet local server lan-address attribute [,attribute...] all [attributes] all characteristics all identifiers all status Examples: show dtss decnet local server * address show dtss decnet local server aa-00-04-00-dd-11 all 4 Characteristic o transport Specifies the transport protocol used by the local server. 4 Identifier o address Specifies the Ethernet address of the server. 4 Status o last observed skew Specifies the skew between the node's clock and the time received from the specified local server after the most recent synchronization. o last observed time Specifies the time the node last received from the specified local server. o last time polled Specifies the time that the node last solicited a time value from the specified local server. o used in last synchronization Specifies whether or not a time value from the specified local server was used in the node's last clock synchronization. 2 event_dispatcher show [node node-id] event dispatcher attribute [,attribute...] all [attributes] all characteristics all counters all status 3 Characteristic o DNA version Default: Current version number Version number of the DNA event-logging architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 Counters o creation time Time at which this entity was created. o events lost Number of events lost at the event dispatcher queue. o test requested (Tru64 UNIX) Number of events being generated with the test directive. 3 Status o state Status of the event dispatcher entity. off The event dispatcher entity is disabled. on The event dispatcher entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 outbound_stream show [node node-id] event dispatcher - outbound stream stream-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status The stream-name can be either a simple name which uniquely identifies a particular outbound stream instance, or a wildcard which identifies multiple outbound stream instances. Examples: show event dispatcher outbound stream * name, state show event dispatcher outbound stream local_stream all 4 Identifier o name Simple name assigned to the outbound stream when it was created. 4 Characteristics o catch all filter Default: Pass Value: Block or pass Action to take if neither the specific filter nor the global filter contains an entry that matches an event. block Discard the event. pass Report the event. o connect retry timer Default: 120 Value: 0-65535 Number of seconds to wait after a disconnect or connection reject before reattempting a connection. Connection attempts continue until a connection is made or until the connect timer enabled attribute is set to false or the outbound stream is disabled. If the outbound stream is already connected to the sink when the timer expires, no connection is attempted at that time. The timer resets and connection attempts continue whenever the timer expires. o connect timer enabled Default: True Value: True or false Specifies whether the connect timer is operational (see connect retry timer). o disconnect timer Default: 0; see Value: 0-4294967295 following description Number of seconds to wait before disconnecting an idle connection. Zero indicates that there is no disconnect timer and connections are never automatically disconnected. o global filter Current global filter as it has been constructed by block, ignore, and pass commands for this stream. By default, the global filter is set to block all events for the following entities: event dispatcher, event dispatcher sink, and event dispatcher sink inbound stream and to pass all events for the event dispatcher outbound stream entity. o sink address Default: No address Value: Sink address tower set Sink address tower for this stream. Modifying this characteristic affects only subsequent connect requests; existing connections are unaffected. o sink end user Default: Number = 82 Value: End-user specification Sink session control end user specification for this stream. o sink node Default: Local node Value: Full-name Full DNS node name of the sink for this stream. Modifying this characteristic affects only subsequent connect requests; existing connections are unaffected. This fullname is used in combination with the sink end user characteristic to establish the sink connection. o sink object Default: No sink object Value: Full-name Full DNS object name of the sink for this stream. Modifying this characteristic affects only subsequent connect requests; existing connections are unaffected. This fullname should match the object name characteristic of the target sink. o specific filter Default: No specific filter Current specific filter for this stream. o template (Tru64 UNIX) Default: No template Value: Simple name Transport template (see osi transport template) for this stream's connections. 4 Counters o confidence changes Number of times the confidence variable has changed while connections were in the open state. o connect requests Number of times a connection to a remote node was requested by this stream, either by an explicit command or by the connection timer. o connections accepted Number of times an outbound connection request was accepted by the sink partner. o creation time Time at which this entity was created. o disabled Number of disable events for this stream. o enabled Number of enable events for this stream. o events lost Number of events lost because of outbound stream buffer overrun. o filter changes Number of times the filter has changed. o shutdowns Number of times a shutdown command or operation was issued. 4 Status o buffer size Maximum number of octets allowed for event processing of this stream. This value is defined in the create command for the stream. o state Status of the outbound stream. off The stream is disabled. on The stream is enabled. onconnected The stream is enabled and has an established connection. onconnecting The stream is enabled and is in the process of establishing a connection. ondisconnecting The stream is enabled, but is in the process of disconnecting from a connection. onshutdownrequested The stream is enabled and has an established connection, but is in the process of shutting down; the stream will disconnect after it transmits all events that were outstanding when the shutdown command was issued. o uid Entity's unique identifier, which is generated when the entity is created. 3 relay show [node node-id] event dispatcher relay state all [attributes] all status Examples: show event dispatcher relay all show event dispatcher relay state 4 Status o state Status of the event dispatcher relay entity. off The event dispatcher relay entity is disabled. on The event dispatcher relay entity is enabled. 4 logging show [node node-id] event dispatcher - relay logging logging-name attribute [,attribute...] all [attributes] all counters all identifiers all status Logging-name can be CONSOLE, MONITOR, FILE or * to identify all three. Examples: show event dispatcher relay logging * name, state show event dispatcher relay logging console all show event dispatcher relay logging monitor all show event dispatcher relay logging file all 5 Counters o creation time Time at which this entity was created. o events relayed Number of Phase IV events relayed for this logging type. 5 Identifier o name Logging type is console, monitor, or file. 5 Status o state Status of the event dispatcher relay logging entity. off The event dispatcher logging entity is disabled. on The event dispatcher logging entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 sink show [node node-id] event dispatcher - sink sink-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status The sink-name can be either a simple name which uniquely identifies a particular sink instance, or a wildcard which identifies multiple sink instances. Examples: show event dispatcher sink local_sink all show event dispatcher sink * all show event dispatcher sink * client type, displayuids 4 Characteristics o catch all filter Default: Pass Value: Block or pass Specifies the action to take if neither the specific filter setting nor the global filter setting matches an event or if a filter setting that does match an event is set to Ignore. block Discard the event. pass Report the event. o client type Default: Console Value: See description. Specifies the application to accept the events received by the sink. This can only be set when the event dispatcher sink entity is disabled (when the sink state is off). console Events go to the operator's console (OPCOM-OpenVMS). device Events go to a device (see the device name characteristic). file Events go to a file (see the file name characteristic). o description Default: Null Value: Latin1String Application description string. o device name Default: Null Value: Latin1String Name of the device to which events are going to be logged, if the client type of the sink is device. o displayuids Default: True Value: Boolean A boolean value indicating whether to include the UIDs when displaying an event. o end user Default: Number = 82 Value: End-user specification Sink session control end user specification for this sink. For Tru64 UNIX, do not modify this characteristic. o file name Default for Tru64 UNIX: Value: File specification /usr/adm/event_file Default for OpenVMS: Value: File specification SYS$MANAGER:NET$EVD_SINK_sinkname.LOG Name of the file to which events are going to be logged if the client type of the sink is file. o global filter Current global filter as it has been constructed by block, ignore, and pass commands for this sink. By default, the global filter is set to block all events for the following entities: event dispatcher, event dispatcher sink, and event dispatcher sink inbound stream. You cannot modify this characteristic. o object name Default: No sink object Value: Full-name Full DNS object name of the sink. Modifying this characteristic affects only subsequent connect requests; existing connections are unaffected. o specific filter Default: No specific filter Current specific filter setting as constructed by block, ignore and pass commands for this sink. You cannot modify this characteristic. o template (Tru64 UNIX) Default: No template Value: Simple name Transport template (see the osi transport template entity) for this sink's connections. o user client (Tru64 UNIX) Default: Null Value: End-user specification Session control end user specification for a user program that has been set to receive events. 4 Counters o connections accepted Number of times a sink connection request was accepted by the sink partner. o creation time Time this entity was created. o events filtered Number of events for this sink that were filtered by its sink filter. o events lost Number of events lost due to sink queue overflow. o filter changes Number of times the filter has changed. 4 Identifier o name Simple name assigned to the sink when it is created. 4 Status o buffer size Maximum number of octets allowed for event processing of this sink. This value is defined in the create command for the sink. This value is limited by the value specified in the maximum buffer size argument of the create command. o state Status of the sink. off The sink is disabled. on The sink is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 4 inbound_stream show [node node-id] event dispatcher - sink sink-name - inbound stream stream-name attribute [,attribute...] all [attributes] all identifiers all characteristics all counters all status The sink-name must be a simple name which uniquely identifies a particular sink instance. The stream-name can be either a simple name which identifies a particular inbound stream instance, or a wildcard which identifies multiple inbound stream instances. Examples: show event dispatcher sink local_sink - inbound stream * name show event dispatcher sink local_sink - inbound stream EVD$IBS$0000 all 5 Counters o creation time Time at which this entity was created. o change confidence Number of times the confidence variable has changed while connections were in the on state. 5 Identifier o name Local name assigned to the entity by its sink parent when it is dynamically created. 5 Status o source end user Source end user specification, as provided by session control. o source node name Name of the source node, as provided by session control. o state Status of the inbound event stream. off The stream is disabled. on connected The stream is enabled and connected to the outbound stream. o uid Entity's unique identifier, which is generated when the entity is created. 2 fddi show [node node-id] fddi version all [attributes] all characteristics Examples: show fddi version show fddi all 3 Characteristic o version Default: Current version number Version number of the FDDI architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 station show [node node-id] fddi - station station-name attribute [,attribute...] all [attributes] all counters all identifiers all status The station-name can be either a simple name which identifies a particular station instance, or a wildcard which identifies multiple station instances. Examples: show fddi station * all show fddi station fddi-0 communication port, station id 4 Characteristics o communication port Name of the hardware port associated with this station, taken from the corresponding argument in the create directive. You cannot modify this characteristic. o smt maximum version id Highest SMT version ID this station supports. You cannot modify this characteristic. o smt minimum version id Lowest SMT version ID this station supports. You cannot modify this characteristic. o smt version id Currently active SMT version ID for this station. You cannot modify this characteristic. o station ID SMT station ID for this station. You cannot modify this characteristic. o type SMT station type for this station. You cannot modify this characteristic. 4 Counters Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers. o configuration changes Number of times the internal configuration of this station changed. (Not present in single attached stations (SAS)). o creation time Time at which the port was created. o selftest failures Total number of times a self-test of the station detected an error. o traces received Number of times the ECM state machine for this station entered the trace state due to a received trace signal. 4 Identifier o name Simple name assigned to the station when it is created. 4 Status o last set station id The station ID of the station that last performed an SMT Change /Add/Remove (PMF frame) operation. o state Value: Off, on or loopback Operational state of the station. o uid Entity's unique identifier, which is generated when the entity is created. 4 link show [node node-id] fddi - station station-name - link link-index attribute [,attribute...] all [attributes] all counters all identifiers all status The station-name must be a simple name which uniquely identifies a particular station instance. The link-index can be either an integer or a wildcard. OpenVMS Examples: show fddi station fddi-0 link * all show fddi station fddi-0 link 0 all show fddi station fddi-0 link 0 - requested trt, restricted token timeout Tru64 UNIX Examples: show fddi station fddi-1 link * all show fddi station fddi-1 link 1 all show fddi station fddi-1 link 1 - requested trt, restricted token timeout 5 Characteristics o link address MAC address assigned during manufacture of the communication hardware that is associated with the station (read-only). o requested trt Default: 8.0 Value: 1-65535 Requested token rotation timer. o restricted token timeout Default: 1000 Value: 1-65535 Length limit of a restricted token dialog. o ring purger enable Default: True Value: True or false Controls whether this station is eligible to be a ring purger and should participate in the ring purger election. o valid transmission time Default: 3.4 Value: 1-65535 Valid transmission time. 5 Counters o block check errors Number of times a received frame containing an integral number of octets failed the FCS check. o creation time Time at which the station was created. o directed beacons received Number of times the link detected the directed beacon process. o duplicate address test failures Number of times the duplicate address test failed (detected that the link address was a duplicate). o duplicate tokens detected Number of times the MAC address test failed (detected that the link address was a duplicate). o error count Total number of frames that were in error with the E indicator reset, indicating that the error occurred between the upstream MAC and this one. o fci strip errors Number of times a frame content independent strip operation (bridge strip) was terminated by receipt of a token. o frame count Total number of frames seen by this link, other than tokens. o frame status errors Number of times a received frame had the E indicator in error (missing or set) and the FCS was correct. o lost count Counter lost count. o multicast octets received Number of multicast data octets that were successfully received in multicast frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o multicast octets sent Number of multicast data octets that were successfully sent in multicast frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o multicast pdus received Number of multicast frames that were successfully received of type LLC, implementer, reserved, or SMT. o multicast pdus sent Number of multicast frames that were successfully sent of type LLC, implementer, reserved, or SMT. o octets received Number of octets successfully received in frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o octets sent Number of octets successfully sent in frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o pdu length errors Number of times a received frame had an invalid length, either too long or short for the type, or had an alignment error (odd number of symbols). o pdus received Number of frames successfully received in frames of type LLC, implementer, reserved, or SMT. o pdus sent Number of frames successfully sent in frames of type LLC, implementer, reserved, or SMT. o receive data overruns Number of times the hardware lost one or more consecutive, only partially complete incoming frames because it was unable to keep up with the medium rate. An example is overrun of a bit or octet FIFO queue because of inability to copy data from adapter to host promptly. In conjunction with total frames received, provides a measure of hardware resource and bandwidth failures. o ring beacons initiated Number of times the ring beacon process was initiated by this link. o ring initializations initiated Number of times a ring reinitialization was initiated by this link. o ring initializations received Number of times a ring reinitialization was initiated by some other link. o ring purge errors Number of times the ring purger received a token while still in the ring purge state. o token count Number of times a token has been seen by this link. o transmit underruns Number of times a transmit underrun occurred. This indicates the transmit FIFO became empty during frame transmission. o traces initiated Number of times the pc trace process was initiated by this link. o transmit failures Number of times a transmit error, other than underrun, occurred. This does not include errors in transmitting MAC type frames. o unavailable link buffers Number of times a complete, fully received frame was discarded because no link buffer was available. In conjunction with total frames received, provides a measure of station-buffer-related receive problems. o unavailable user buffers Number of times no user buffer was available for an incoming frame that passed all filtering for the port. These are the buffers supplied by users on receive requests. In conjunction with total frames received, provides a measure of user-buffer- related receive problems. o unrecognized individual destination pdus Number of times a received LLC frame with an individual destination MAC address was discarded because there was no port with the Ethernet protocol type, SNAP protocol identifier, or LLC SAP address enabled. Only frames containing individual destination MAC addresses are counted. o unrecognized multicast destination pdus Number of times a received LLC frame with a multicast destination MAC address was discarded because there was no port with the Ethernet protocol type, SNAP protocol identifier, or LLC SAP address enabled. Only frames containing multicast destination MAC addresses are counted. 5 Identifier o index An integer that uniquely identifies this link to the parent station entity. 5 Status o downstream neighbor MAC address of the downstream neighbor, if known. o duplicate address flag Summary output of the duplicate address test algorithm. o frame strip mode Current frame stripping mode of the MAC. SA match Source address match mode of the frame stripping algorithm matches the source address of the frame with the MAC's MyLongAddress (MLA), and if a match is found, the frame is removed from the token ring. FCI The FCIS mode counts the number of frames transmitted strip since the reception of a token, and strips equal number of frames. o loopback This is true if the link has been set up to receive frames transmitted by it. This allows loopback testing either on the ring or with one of the PHY port loopback modes. o negotiated trt Negotiated token rotation timer. o old downstream neighbor Previous value of the downstream neighbor. o old upstream neighbor Previous value of the upstream neighbor. o ring error reason Reason code for the most recent link error. duplicate Duplicate address algorithm detected a duplicate address address. detected duplicate A duplicate token was detected on the ring. token detected no error No errors have occurred on this ring. ring init Ring initialization was initiated by this link to initiated initialize the ring and create a token. ring init Ring initialization was initiated by some other received link to initialize the ring and create a token. ring Ring beaconing process was initiated by this link. beaconing This process in initiated as a result of serious initiated ring failure, such as loss of signal or jabbering station transmitting in violation of the protocol. This indicates to other links on the LAN that corrective action may be required. ring purge Link received a token while performing a ring error purge operation. FCI strip Frame content independent strip operation was error terminated by the receipt of a token. ring op Ring state has been continually changing from oscillation operational to initializing. directed Link received particular beacon data. beacon received PC trace PC-trace was initiated by this link. initiated PC trace PC-trace was initiated by some other link. received o ring latency Current ring latency as measured by this link entity. o ring purger state State of the ring purger election process. candidate The Link's Ring Purger process is participating in the Ring Purger election algorithm as a candidate to become the Ring Purger. nonpurger The Link's Ring Purger process is in an idle state listening for periodic Purger Hello frames. off The Link's Ring Purger process is disabled. purger The Link's Ring Purger process is performing the function of removing no owner frames and duplicate token from the ring. In this state, the process transmits periodic Purger Hello frames. o state State of the link entity. broken Attempt to turn the link on failed the initialization test, or link was on, but failure was detected. off-ready FDDI Data Link communication services are not available. off-fault State entered when a link entity detects recovery conditions that indicate faulty ring. on-ring init Physical layer service is available and the link entity enabled. on-ring run Link detected that the Ring Initialization has been successfully completed and the ring is operational. o uid Entity's unique identifier, which is generated when the entity is created. o upstream neighbor MAC address of the upstream neighbor, if known. o upstream neighbor duplicate address flag Default: false Value: True or false Upstream neighbor's reported result of its duplicate address test. 4 phy_port show [node node-id] fddi - station station-name - phy port port-index attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status The station-name must be a simple name which uniquely identifies a particular station instance. The port-index can be either an integer or a wildcard. OpenVMS Examples: show fddi station fddi-0 phy port * all show fddi station fddi-0 phy port 0 all Tru64 UNIX Examples: show fddi station fddi-1 phy port * all show fddi station fddi-1 phy port 1 all 5 Characteristics o lem threshold Value: For n, 10 to the -n th power Link error monitor threshold. o phy type Type of the physical port (A, B, S, or M). This characteristic cannot be set. o pmd type Type of the PDM (transceiver) for this physical port. This characteristic cannot be set. ANSI multimode Low power ANSI multimode type 1 Thinwire ANSI single mode type 2 Shielded twisted-pair ANSI SONET Unshielded twisted-pair 5 Counters o creation time Time at which the port was created. o connections completed Number of times the PHY port entered the in use state, having completed the initialization process. o elasticity buffer errors Number of times the elasticity buffer function had an overflow or underflow. o lct rejects Number of times a connection was rejected due to failure of the Link Confidence Test at either end of the physical connection. o lem rejects Number of times an active connection was disconnected due to rejection by the Link Error Monitor at this end of the physical connection, or by expiration of the Noise timer. o link errors Total number of raw link error input events seen by the Link Error Monitor. 5 Identifier o index An integer that uniquely identifies this physical port to the parent station entity. 5 Status o broken reason Reason phy port is in broken state, or if in broken state, none. o estimated link error rate Default: 15 Value: 0-15 Reports the number of errors during the Link Monitor Test as a negative power of 10. If there are no errors during the Link Monitor Test, then the Estimated Link Error Rate is 10(-15th power). An Estimated Link Error Rate of 15 indicates an excellent/clear link, 14-10 is a noisy link and around 7 would indicate an acceptable (failed) link. o neighbor phy type Status may be A, B, S, M or unknown. o reject reason Reason the phy port is in a failed or watch state. This is not meaningful when phy port is in some other state. LCT both Link Confidence Test failed on both sides of the sides physical connection. LCT protocol Neighboring physical port has been detected to error have prematurely exited the link confidence test (LCT). LEM reject Link error monitor disconnected this connection due to the error rate exceeding the LEM threshold. local LCT Link Confidence Test failed on this end of the physical connection. noise reject Noise timer expired because a single noise event lasted for more than 1.31072 ms. none No reason. remote LCT Link Confidence Test failed on the other end of the physical connection. remote Neighboring physical port broke the connection for reject an unknown reason. standby Physical port and its neighboring physical port form a redundant physical connection (dual- homing feature). In a dual-homed configuration, the B to M connection is the higher priority physical connection, and the A to M connection is the standby physical connection. The standby connection will become active if the B to M connection is lost. topology Neighboring physical port's physical port type is reason an illegal match for this physical port's physical port type. trace in Physical port was initializing when a pc-trace progress occurred. When a pc-trace occurs, any physical ports that have not yet established a physical connection are shut down to prevent the topology from changing. trace Physical port was momentarily disabled because it received- received a pc-trace when its own pc-trace function disabled was disabled. The pc-trace function is enabled by default. The trace disable switch is not remotely manageable. o state Operational state of the phy port entity (nonsettable). broken The physical port has failed initialization tests and is not available for use. failed Same as waiting, except the physical port has failed to complete the last connection attempt. Refer to the physical port's status parameter reject reason for the reason for connection failure. Connection attempts will continue until successful. internal The physical port has been configured to loopback internally present all transmitted symbols to the receive interface. The network connector is inactive. This allows internally generated test frames to be looped back for test purposes. in use The physical port has established a connection and is fully operational. Communications services are now available. off-ready The physical port is waiting to be enabled or has been disabled by management request. starting The physical port has received a response from the neighboring physical port and is exchanging information and performing the link confidence test (LCT) prior to completing the connection. waiting The physical port is beginning to establish a connection and is waiting for a response from the neighboring physical port. watch Same as starting, except the physical port has failed to complete the last connection attempt. Refer to the physical port's status parameter, reject reason for the reason for connection failure. Connection attempts will continue until successful. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] fddi - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show fddi port * all show fddi port FDDI$FXA_0010 mac addresses, client 4 Counters o creation time Time at which the port was created. o multicast octets received Number of multicast user data octets successfully received and available to the data-link user. o multicast octets sent Number of multicast user data octets successfully transmitted using the port. o multicast pdus received Number of multicast frames successfully received and available to the data-link user. o multicast pdus sent Number of multicast frames successfully transmitted using the port. o octets received Number of user data octets successfully received and available to the data-link user. o octets sent Number of user data octets successfully transmitted using the port. o pdus received Number of frames successfully received and available to the data link user. o pdus sent Number of frames successfully transmitted using the port. o unavailable user buffers Number of times no user buffer was available at the port for an incoming frame. 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client Name specified by the data link when the port is opened. o ethernet protocol types Set of Ethernet protocol types that are recognized for this port. Protocol types for a port may be enabled and disabled by the user at any time during the port's existence. o length present Default: Value: True or false Indicates whether the data link is to add a length field on transmit, and both assume the presence of and remove the length field on receive for Ethernet frames. This attribute is irrelevant for ISO 8802-3 formatted frames because the length field is always present. This is specified by the user when the port is opened. The value true means length fields are added and removed by the data link. o link Name of the link subentity associated with this port, specified by the user when the port is opened. o llc sap addresses Set of SNAP protocol identifiers that are recognized for this port. LLC SAP addresses for a port may be enabled and disabled by the user at any time during the port's existence. o llc service Default: Value: Class 1 or User supplied LLC PDU processing the data-link user requires from the port, specified by the user when the port is opened.This is either LLC Class 1, where the entire LLC protocol is handled by the data link, or user-supplied LLC, where the user is responsible for operating part of the LLC protocol. o mac addresses Set of individual and multicast MAC addresses that are recognized for this port. MAC addresses for a port may be enabled and disabled by the user at any time during the port's existence. o receive mode Default: Value: Normal or Promiscuous Indicates if the port is to receive all frames regardless of format, Ethernet protocol type, SNAP protocol identifier, LLC SAP address, or MAC address. Promiscuous receipt is enabled and disabled by the user. Support of promiscuous mode is optional. o snap protocol identifiers Set of SNAP protocol identifiers that are recognized for this port. Protocol identifiers for a port may be enabled and disabled by the user at any time during the port's existence. o type Type of port (LLC or SMT). o uid Entity's unique identifier, which is generated when the entity is created. 2 frame_(OpenVMS) show [node node-id] frame attribute [,attribute...] all [attributes] all characteristics all status Examples: show frame version, state show frame all 3 Characteristic o version Specifies the version of the frame architecture to which the implementation conforms. You cannot modify this characteristic. 3 Status o state Specifies the state of the frame entity. off The frame entity is disabled. on The frame entity is enabled. 3 link show [node node-id] frame - link link-id attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show frame link * name show frame link frame-0 all 4 Identifier o name Simple name assigned to the link when it is created. 4 Characteristics o bisync code Default: EBCDIC Value: ASCII or EBCDIC Character code to be used on the link. This characteristic is supported only when the characteristic protocol is set to one of the following: bisync, chips, genbyte, or swift. You can modify this characteristic only when the entity is disabled. o bits per character Default: 8 Value: 5-8 Number of bits in each character. This characteristic is supported only when the characteristic protocol is set to genbyte. You can modify this characteristic only when the entity is disabled. o buffer size Default: 512 Value: 0-65535 Size, in octets, of each receive buffer for the link. You can modify this characteristic only when the entity is disabled. Also, you can only increase the characteristic value. o control mode Default: point to Value: See description point Control mode in which the link is to operate. The value of this characteristic derives from the point to point argument to the create command. multipoint master multipoint tributary point to point You cannot modify this characteristic. o crc type Default: See Value: See description description CRC type used on the link. AUTO_DIN CRC_16 CRC_CCITT CRC_CCITT0 LRC_EVEN LRC_ODD LRC_VRC_ EVEN LRC_VRC_ ODD NONE The default value depends on the protocol. BISYNC CRC_16 CHIPS LRC_EVEN DDCMP CRC_16 GENBYTE NONE HDLC CRC_CCITT SDLC CRC_CCITT SWIFT CRC_16 genbyte crc checking is done in the genbyte framing routine. o framing timer Default: 25 Value: 10-1000 Maximum length of time, in milliseconds, to wait for the next character to arrive. This characteristic is supported only when the characteristic protocol is set to genbyte. o initial state one Default: 0 Value: See description First 32 bits of state information. This characteristic is supported only when the characteristic protocol is set to genbyte. You can modify this characteristic only when the entity is disabled. o initial state two Default: 0 Value: See description Last 32 bits of state information. This characteristic is supported only when the characteristic protocol is set to genbyte. You can modify this characteristic only when the entity is disabled. o local station address Default: 255 Value: 0-255 Address of the local station. The default value means that only broadcast messages are accepted. The interpretation of this characteristic is controlled by the value of the characteristic match station address. This attribute is supported only if the characteristic protocol is set to sdlc. You can modify this characteristic only when the entity is disabled. o match station address Default: False Value: True or False Specifies whether the value of the characteristic local station address is to be interpreted as a valid address. This attribute is supported only if the characteristic protocol is set to sdlc. You can modify this characteristic only when the entity is disabled. o number of buffers Default: 4 Value: 0-255 Number of receive buffers reserved for the link. You can modify this characteristic only when the entity is disabled. Also, you can only increase the characteristic value. o physical line Default: None Value: Local entity name Name of the Physical layer line entity on which the link operates. You must provide a value for this characteristic before you enable the link. You can modify this characteristic only when the entity is disabled. o protocol Framing protocol used on the line. The value of this characteristic derives from the protocol argument to the create command. You cannot modify this characteristic. bisync hdlc chips sdlc ddcmp swift genbyte o sync character Default: See Value: 0-FF description Hexadecimal code of the sync character to be used on the link. The default value depends on the value of the characteristic protocol, as follows: bisync 32 chips 32 ddcmp 96 genbyte 32 swift 32 This attribute is supported only if the characteristic protocol is set to bisync, chips, ddcmp, genbyte, or swift. You can modify this characteristic only when the entity is disabled. o sync count Default: 4 Value: 0-255 Number of sync characters that precede each message. This attribute is supported only if the characteristic protocol is set to bisync, chips, ddcmp, genbyte, or swift. You can modify this characteristic only when the entity is disabled. 4 Counters o abort characters received Number of times that the link was prematurely terminated by the remote station. This counter is supported only if the characteristic protocol is set to either hdlc or sdlc. o creation time Time at which this entity was created. o data block check errors Number of messages received with an error in the data field block check. o header block check errors Number of messages received with an error in the header block check. This counter is supported only if the characteristic protocol is set to ddcmp. o invalid characters received Number of times that an invalid character was received from the remote station. This counter is supported only if the characteristic protocol is set to either bisync or ddcmp. o receive buffer overflows with good crc Number of times that the local station received a message too large for the receive buffer and the message had a valid CRC. o receive overruns Number of times that the host memory was not able to handle all the data received from the communications channel. o sdus received Number of data messages received from the remote station. o sdus sent Number of data messages sent to the remote station. o service octets received Number of data octets received from the remote station. o service octets sent Number of data octets sent to the remote station. o transmit underruns Number of times that the host memory could not supply data fast enough to satisfy the communications channel. 4 Status o physical port name Name of the Physical layer port returned when the port is opened. If this value is missing, the port has yet to be opened. o state State of the frame link entity. off The link is disabled. on The link is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] frame - port port-name attribute [,attribute...] all [attributes] all identifiers all status Examples: show frame port * all show frame port * name, state 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client Name of the client entity that opened the port. o link Name of the frame link entity that the client supplied when the port was opened. o state State of the frame port entity. open The port is assigned to a client. open The port is assigned to a client, but the disabled appropriate link entity has been disabled. 2 hdlc show [node node-id] hdlc version all [attributes] all characteristics Example: show hdlc version 3 Characteristic o version Version of the HDLC architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 link show [node node-id] hdlc - link link-id attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show hdlc link * name, state show hdlc link hdlc-0 all 4 Characteristics o acknowledge timer Default: 3000 Value: 1-60000 Time (in milliseconds) to wait for an acknowledgment before using error recovery procedures. The value of this characteristic corresponds to the T1 parameter of HDLC. You can modify this characteristic only when the entity is disabled. o holdback timer Default: 0 Value: 1-60000 Maximum time to wait before sending an acknowledgment supervisory frame if no other frames carry the acknowledgment. A value of zero means that the frame will be sent immediately if no I-frame can be sent. You can modify this characteristic only when the entity is disabled. o link type Operational mode of the HDLC link. The value of this characteristic is a copy of the link type argument specified when the entity is created. You cannot modify this characteristic. o maximum data size Default: 1500 Value: 262-65532 Maximum number of bytes that users of the data link can specify. This number applies to both transmit and receive frames. The value of this characteristic must be greater than or equal to the value of the minimum data size characteristic. You can modify this characteristic only when the entity is disabled. o maximum unsequenced pdus Default: 1 Value: 1-127 Maximum number of unsequenced I-frames that a primary or secondary station can send in a single transmission. This characteristic is not used if the link type characteristic is balanced. o minimum data size Default: 576 Value: 262-65532 Minimum number of bytes that users of the data link can specify. This number applies to both transmit and receive frames. The value of this characteristic must be less than or equal to the value of the maximum data size characteristic. You can modify this characteristic only when the entity is disabled. o physical line Default: None Value: local entity name Local entity name of the the Physical layer entity over which the HDLC protocol is to operate. This characteristic must have a value before the HDLC link is enabled. You can modify this characteristic only when the entity is disabled. o preferred crc type Default: Either Value: 16 bit, 32 bit, or either CRC types available for negotiation. If the value of this characteristic is either, the station will try to use 32-bit but will use 16-bit if that is all that the remote station supports. o preferred local station address Default: 2 Value: 1-253 Address proposed for the local logical station during negotiation. If there is no negotiation, the value of this characteristic is the value that is used. If negotiation is necessary, the value of this characteristic must be between 2 and 253. You can modify this characteristic only when the entity is disabled. o preferred maximum data size Default: 1500 Value: 262-65532 Default size (in octets) of frames that the station receives and transmits. This value is used only if the link initialization does not specify a buffer value. The value of this characteristic must lie between those of the maximum data size and minimum data size characteristics. You can modify this characteristic to a lower value only when the entity is disabled. o preferred window size Default: 2 Value: 1-127 Window size to be offered during negotiation for both receive and transmit frames. The value of this characteristic must be compatible with that for the sequence modulus characteristic. o profile (OpenVMS) Simple name that can be used when the HDLC protocol is dependent on network subscription time commitments pertinent to the Data Link layer. The value of this characteristic is a copy of the profile argument specified when the entity is created. You cannot modify this characteristic. o receive buffers (OpenVMS) Default: 4 Value: 1-128 Number of receive buffers reserved for the link. This characteristic can only be set to a lower value when the entity is disabled. o retry maximum Default: 10 Value: 1-255 Maximum number of times that a frame will be retransmitted before the local station assumes that a fatal error has occurred. This characteristic can be modified only when the entity is disabled. o sequence modulus Default: 128 Value: 8 or 128 Whether modulo-8 or modulo-128 sequence numbering is allowed on the HDLC link. The value 8 means that only normal sequence numbering is allowed. The value 128 means that both extended and normal sequence numbering are supported for negotiation. 4 Counters o buffer unavailable errors Number of times that the Physical layer reported that no buffer was available to hold a message. This counter is not supported in all implementations. o crc errors received Number of frames received that had a bad CRC. o creation time Time at which this entity was created. o times pdu receive overrun Number of times a Physical line indicated an overrun condition to the Data Link layer. This counter is not supported in all implementations. o times pdu transmit failed Number of times that an attempt to send a frame failed. o up transitions Number of times that the entity's status attribute state has changed from off to on. 4 Identifier o name Simple name assigned to the HDLC link when it is created. 4 Status o actual sequence modulus Sequence number modulus in use on the link. Until negotiation is complete, this attribute has the value 128. However, if the value of the characteristic sequence modulus is 8, the modulus always appears as the value 8. 8 Indicates that modulo-8 numbering is in use. 128 Indicates that modulo-128 numbering is in use. o interframe delay Value: 0-109 Time required between frames to enable the local station to successfully receive them. o maximum pdu size Value: 1-65535 Maximum frame size (in octets) that can be used on the link. Until negotiation is complete, the value of this status attribute is the same as the characteristic preferred maximum data size. o negotiated crc type CRC mode that has been negotiated with the remote station. This mode will not be used until the station is next enabled. Until negotiation is complete, the value of this is 16-bit. o line type Value: Switched or nonswitched Defines whether the underlying physical line is switched or nonswitched. This status affects the subset of port states that are related to a given link. o physical port Name of the port in the Physical layer associated with the communications link. o response address Address that the remote station puts in response frames. o state State of the HDLC link. This reflects the last enable or disable command issued. off The link is disabled. on The link is enabled. o window size Value: 1-127 Maximum number of I-frames that can be outstanding before an acknowledgment must be received. Until negotiation is complete, the value of this status attribute is the same as the characteristic preferred window size. o uid Entity's unique identifier, which is generated when the entity is created. 4 logical_station show [node node-id] hdlc - link link-name - logical station station-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show hdlc link hdlc-0 logical station * all show hdlc link hdlc-0 logical station * name, state 5 Counters o creation time Time at which this entity was created. o data octets received Total number of octets received in the I-field of I-frames and UI-frames. This total excludes protocol ID information in UI- frames and frame retransmissions. o data octets sent Total number of octets sent in the I-field of I-frames and UI- frames. This total excludes protocol ID information in UI-frames and frame retransmissions. o data pdus received Total number of I-frames and UID-frames received. This number does not include frames that had to be retransmitted. o data pdus sent Total number of I-frames and UID-frames sent. This number does not include frames that had to be retransmitted. o frmrs generated Number of FRMRs (frame rejects) sent. o frmrs received Number of FRMRs (frame rejects) received. o invalid mode commands Number of command frames (SABME, SABM, SNRME, SNRM, SARM, and SIM) received that are not applicable to this station. o negotiation failures Number of times that the XID negotiation with the remote station has failed. o polls received Number of frames received with the poll bit set. o rejs received Number of REJ frames (rejects) received. o rejs sent Number of REJ frames (rejects) sent. o rnrs received Number of RNR (receive not ready) supervisory frames received from the remote station. o rnrs sent Number of RNR (receive not ready) supervisory frames transmitted. o times acknowledge timer expired Number of times that the acknowledge timer has expired. o times station halted Number of times the station halt event has occurred. o times station initializing Number of times the station initialized event has occurred. o times station inoperative Number of times the entity's status attribute state became inoperative. o times station maintenance Number of times the entity's status attribute state became maintenance. o times station resetting Number of times that the station reset event has occurred. o times station running Number of times that the station running event has occurred. o times station setup failed Number of times the station setup failure event has occurred. o unknown ui pdus received Number of UI-frames the local station received whose protocol ID does not match that of any open port. o xids received Number of XID (identification) command or response frames received. 5 Identifier o name Simple name assigned to the logical station when it is created. 5 Status o command address Address the local station uses when sending command frames to the remote station. o maintenance mode Whether the station is in maintenance mode. When set to true, the station will be used exclusively for maintenance operations. When set to false, the station operates in normal fashion. The limit command sets the value of this attribute to true, and the unlimit to false. o protocol state State of the data link protocol. error A protocol error occurred. For instance, the logical station received an invalid frame. halted The protocol could not start. For example, there is no client. initializing The protocol is being initialized. inoperative The protocol cannot be started because no contact has been established with the remote station. maintenance The logical station is in maintenance mode. resetting The protocol is resetting after an error. running The protocol is running and capable of exchanging frames with the remote station. o remote version Version number of the HDLC protocol that the remote station is using. This is received as part of an XID message from the remote station. o state State of the logical station. off The logical station is off because of a disable command. on The logical station is on because of an enable command. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] hdlc - port port-name attribute [,attribute...] all [attributes] all identifiers all status Example: show hdlc port * name, state show hdlc port * all 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client Name of the client using the port. o logical station hdlc link logical station entity that the port is operating over. o protocol id Protocol ID that the port is using. For sequenced ports, this value is decided during negotiation. For unsequenced ports, the value is sent in every UI-frame. o state State of the port. open The port is assigned to a client. If the communications line is unswitched, data transfer can begin. For switched lines, an association must be made with the line before data transfer can begin. open The port is associated with a client, but the link disabled or logical station associated with it is disabled. o type Type of port. sequenced The port can send and receive sequenced and unsequenced data. unsequenced The port can send and receive unsequenced data only. 2 known 3 links The NCP command SHOW KNOWN LINKS has no equivalent in NCL. However, you may obtain similar information using the "show know links" task of the Network Management GUI. You may wish to enable the displaying of NCL commands in that utility in order to see what NCL commands are necessary to produce the output. For more information, refer to HELP NETWORK_MANAGEMENT TOOLS GUI. 3 node_counters The NCP command SHOW KNOWN NODE COUNTERS has no equivalent in NCL. However, you may obtain similar information using the "show know node counters" task of the Network Management GUI. You may wish to enable the displaying of NCL commands in that utility in order to see what NCL commands are necessary to produce the output. For more information, refer to HELP NETWORK_MANAGEMENT TOOLS GUI. 2 lapb show [node node-id] lapb version all [attributes] all characteristics 3 Characteristic o version Default: None Value: Current version number Version number of the DNA HDLC architecture to which this implementation conforms. You cannot modify this characteristic. 3 link show [node node-id] lapb - link simple-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show lapb link * name, protocol state show lapb link link-0 all 4 Characteristics o acknowledge timer Default: Supplied by profile Value: 1-60000 Time, in milliseconds, to wait for an acknowledgment before initiating recovery action. This attribute corresponds to the LAPB parameter T1. You can modify this characteristic only when the entity is disabled. o holdback timer Default: Implementation specific Value: 0-60000 Delay, in milliseconds, before an acknowledgment must be sent. This characteristic corresponds to the LAPB parameter T2. You can modify this characteristic only when the entity is disabled. o interface type Default: dte Value: dce or dte Address mode for this link. dce Use DCE address mode. dte Use DTE address mode. You can modify this characteristic only when the entity is disabled. o maximum data size Default: Supplied by Value: 1-65532 profile Maximum frame size, in octets, of an information field in an I-frame. o physical line Default: No default Value: Local entity name Name of the Physical layer and line entity over which the LAPB protocol is to operate. You must give this characteristic a value before you enable the link. o poll timer Default: Implementation specific Value: Supplied by profile Maximum period in seconds that may elapse without frames being exchanged on the Data Link. On expiration, an RR(P) is sent to elicit a response from the other end. o profile Default: No default Value: String Name of the X.25 Level 2 Profile that defines subscription details associated with the PSDN to which this DTE is connected. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. o receive buffers (OpenVMS) Default: Implementation specific Value: 1-128 Specifies the number of receive data buffers. o retry maximum Default: Supplied by profile Value: 1-255 Maximum number of times that a frame will be retransmitted before assuming a fatal error, at which point more drastic error recovery action will be attempted. This characteristic corresponds to the LAPB parameter N2. o sequence modulus Default: Supplied by profile Value: 8 or 128 Type of sequence numbering. 8 Use normal sequence numbering. 128 Use extended sequence numbering. o window size Default: Supplied by profile Value: 1-127 Window size for transmitting and receiving I-frames. This characteristic corresponds to the LAPB parameter K. 4 Counters o buffer unavailable errors (OpenVMS) Number of times that the underlying framing level has indicated system buffer unavailability to the Data Link layer. o crc errors received Number of frames received with a bad CRC. o creation time Time at which the entity was created. o data octets received Number of data octets received from the remote station. This value does not include retransmissions. o data octets sent Number of data octets sent to the remote station. This value does not include retransmissions. o data pdus received Number of I-frames received from the remote station. This value does not include retransmissions. o data pdus sent Number of I-frames sent to the remote station. This value does not include retransmissions. o frmrs sent Number of FRMR frames generated as a result of invalid incoming frames. o frmrs received Number of FRMR frames received. o polls received Number of command frames received with the P-bit set. o rejs received Number of REJ frames received. o rejs sent Number of REJ frames transmitted. o rnrs received Number of RNR frames received. o rnrs sent Number of RNR frames transmitted. o times acknowledge timer expired Number of times the local acknowledge timer has expired. o times link halted Number of times the link halt event has been generated. o times link initializing Number of times the link initializing event has been generated. o times link inoperative Number of times the link inoperative event has been generated. o times link maintenance Number of times the link maintenance event has been generated. o times link resetting Number of times the link reset event has been generated. o times link running Number of times the link running event has been generated. o times link setup failed Number of times the link setup failure event has been generated. o times link state changed Number of times a link state transition has occurred. o times pdu receive overrun Specifies the number of times a physical line indicated an overrun condition to the Data Link layer. o times pdu transmit failed Number of times an attempt to transmit a frame has failed. 4 Identifier o name Simple name assigned to the link when it is created. 4 Status o line type Type of line over which this link operates. nonswitched The line is a nonswitched line. switched The line is a switched line. o maximum pdu size Maximum frame size, in octets, that this station will receive and transmit. This value includes the frame header. o physical port Name of the Physical layer port with which the link is associated. o protocol state State of the LAPB protocol with respect to the remote station. error The protocol is in a recognized error state. halted The protocol has halted. initializing The protocol is being initialized. inoperative The protocol cannot be started without connectivity to the remote station. maintenance The link is in maintenance mode. resetting The protocol is undergoing a reset operation. running The protocol is running normally. o state Status of the lapb link entity. off The link is disabled. on The link is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] lapb - port port-name attribute [,attribute...] all [attributes] all identifiers all status Examples: show lapb port * all show lapb port * name, state 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client name Name of the client with which the port is associated. o link Name of the link with which the port is associated. o state State of the lapb port entity. open The port is assigned to a client. open The port is assigned to a client, but the disabled associated link is disabled. o type Type of port. sequenced The port is used for sending LAPB data. unsequenced The port is used for sending loopback data. This is only possible if the maintenance mode characteristic of the relevant lapb link entity is set to true. 2 llc2 show [node node-id] llc2 version all [attributes] all characteristics 3 Characteristics o version Specifies the version number of the DNA LLC2 architecture to which this implementation conforms. You cannot modify this characteristic. To display this attribute, specify all or version. 3 port show [node node-id] llc2 - port simple-name attribute [,attribute...] all [attributes] all identifiers all status Examples: show llc2 port * name, client show llc2 port * all 4 Identifiers o name Specifies the simple-name assigned to the port when it is created. 4 Status o client Specifies the name of the client that opened the port. o link name Specifies the name of the llc2 sap link entity the port is associated with. o state Specifies the state of the llc2 port entity. open The port is assigned to a client and is enabled. disabled The port is assigned to a client but is disabled. 3 sap show [node node-id] llc2 - sap simple-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show llc2 sap * name show llc2 sap sap-0 local lsap address, lan station 4 Characteristics o lan station Default: No entity name Value: Local-entity-name Specifies the name of the LAN station entity used by the SAP. You must specify a value for this attribute before you enable the SAP. o local lsap address Default: 7E Value: Hex-number Specifies the address of the local link service access point (LSAP) to be used. The lowest significant bit of this value must be clear; the address specified must be an individual address. 4 Counters o creation time Specifies the time the entity was created. o times sap state changed Specifies the number of times the status attribute STATE has changed from On to Off, or from Off to On. 4 Identifiers o name Specifies the simple-name assigned to the SAP when it is created. 4 Status o lan port Specifies the name of the LAN port that is opened and enabled when this SAP is successfully enabled. If no port has been opened, this status has a null value. o maximum pdu size Specifies the largest frame size, in octets, that can be used to send or receive data on this SAP. o state Specifies the state of the llc2 sap entity. off The SAP is disabled. on The SAP is enabled. o uid Specifies the entity's unique identifier that is generated when the entity is created. 4 link show [node node-id] llc2 - sap simple-name - link simple-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show llc2 sap sap-0 link * name, state show llc2 sap sap-0 link dte-1 all 5 Characteristics o acknowledge timer Default: 1000 Value: 1-60000 Time, in milliseconds, that the link waits for an acknowledgment before initiating recovery action. The granularity of this timer is 10 milliseconds. Values that are not multiples of 10 are rounded up. o busy timer Default: 10000 Value: 1-60000 Time, in milliseconds, that the link waits for indication of the clearance of a busy condition at the remote station. The granularity of this timer is 10 milliseconds. Values that are not multiples of 10 are rounded up. o holdback timer Default: 500 Value: 0-60000 Delay, in milliseconds, before an acknowledgment must be sent. The granularity of this timer is 10 milliseconds. Values that are not multiples of 10 are rounded down. o local receive window size Default: 127 Value: 1-127 Window size used by the link for receiving frames. o maximum data size Default: 1028 Value: 1-65531 Largest frame size, in octets, the link can use to send or receive data. This value does not include the size of the frame header. o poll timer Default: 1000 Value: 1-60000 Time, in milliseconds, the link waits for a response with the F bit set. The granularity of this timer is 10 milliseconds. Values that are not multiples of 10 are rounded up. o reject timer Default: 3000 Value: 1-60000 Time, in milliseconds, the link waits for a reply to a REJ (reject) frame. The granularity of this timer is 10 milliseconds. Values that are not multiples of 10 are rounded up. o remote lsap address Default: 7E Value: Hex-number Address of the destination LSAP (local service access point) to be used by the link. The lowest significant bit must be clear; the specified address must be an individual address. o remote mac address Default: 00-00-00-00-00-00 Value: LAN-address Specifies the destination MAC address to be used by the link. The lowest significant bit of the first octet must be clear; that is, the address must be an individual address. o retry maximum Default: 10 Value: 1-255 Maximum number of times the link retransmits a frame before assuming a fatal error and taking more drastic recovery action. 5 Counters o acknowledge timer expirations Specifies the number of times the local acknowledge timer has expired. o busy timer expirations Specifies the number of times the local busy timer has expired. o creation time Specifies the time the entity was created. o data pdus received Specifies the number of I frames and UI frames received from the remote end of the link. This value does not include retransmissions. o data pdus sent Specifies the number of I frames and UI frames transmitted to the remote end of the link. This value does not include retransmissions. o data octets received Specifies the number of data octets received in I frames and UI frames from the remote end of the link. This value does not include data octets in retransmissions. o data octets sent Specifies the number of data octets transmitted in I frames and UI frames to the remote end of the link. This value does not include data octets in retransmissions. o frmrs received Specifies the number of FRMR (frame reject) frames received. o frmrs sent Specifies the number of FRMR (frame reject) frames generated as a result of invalid incoming frames. o polls received Specifies the number of command frames received with the P bit set. o poll timer expirations Specifies the number of times the local poll timer has expired. o reject timer expirations Specifies the number of times the local reject timer has expired. o rejs received Specifies the number of REJ (reject) frames received. o rejs sent Specifies the number of REJ (reject) frames transmitted. o rnrs received Specifies the number of RNR (receive not ready) frames received. o rnrs sent Specifies the number of RNR (receive not ready) frames transmitted. o times link changed state Specifies the number of times the link's status attribute state changed from On to Off, or from Off to On. o times link halted Specifies the number of times the link's status attribute protocol state was set to Halted. o times link initializing Specifies the number of times the link's status attribute protocol state was set to Initializing. o times link inoperative Specifies the number of times the link's status attribute protocol state was set to Inoperative. o times link resetting Specifies the number of times the link's status attribute protocol state was set to Resetting. o times link running Specifies the number of times the link's status attribute protocol state was set to Running. When the link enters the Running state, the protocol has been successfully initialized or reset. o times link setup failed Specifies the number of times the llc2 protocol fails to initialize correctly after the maximum number of retries. o xids received Specifies the number of XID frames received. o xids sent Specifies the number of XID frames transmitted. 5 Identifiers o name Specifies the simple-name assigned to the link when it is created. 5 Status o protocol state Specifies the state of the llc2 protocol with respect to the remote station. error The protocol is in a recognized error state. halted The protocol has halted. initializing The protocol is being initialized. inoperative The protocol cannot be started because the LAN station cannot provide a connection to a remote system. resetting The protocol is being reset. running The protocol is running normally. o remote llc class Specifies the class of the remote llc. 1 Class 1 llc. Only type 1 operation is supported. 2 Class 2 llc. Both type 1 and type 2 operation are supported. unknown The class has not yet been established. The class is not established until xid frames have been exchanged between the local and remote llc implementations. o remote receive window size Specifies the window size used by the remote station for receiving frames. The local station uses this value as its window for transmitting frames. o state Specifies the state of the llc2 link entity. off The link is disabled. on The link is enabled. o uid Specifies the entity's unique identifier that is generated when the entity is created. 2 loopback_application show [node node-id] loopback application attribute [,attribute] all [attributes] all characteristics Examples: show loopback application all show loopback application maximum mirrors, maximum data 3 Characteristics o maximum data Default: 4096 The maximum size, in octets, of the loop message data field that the loop mirror can reflect. If the loop mirror receives a loop message with a longer data field, an error occurs. You cannot modify this characteristic. o maximum mirrors Default: 0 Value: 0-4294967295 Enter the maximum number of loop mirrors supported. If you enter the value 0, the node supports an unlimited number of mirrors. For Tru64 UNIX, to limit the number of loop mirrors, use the maximum instances characteristic of the session control application mir (NOT MIRROR) entity. 2 modem_connect show [node node-id] modem connect version all [attributes] all characteristics 3 Characteristic version The version number of the DNA Modem Connect architecture to which the implementation conforms. You cannot modify this characteristic. 3 data_port show [node node-id] modem connect - data port port-name attribute [,attribute...] all [attributes] all identifiers all status Example: show modem connect data port * name, state 4 Identifier o name Simple name assigned to the data port. 4 Status o client Name supplied by the client when the port was opened. This defines which client owns the port. o line Name of the modem connect line entity that the client supplied when the port was opened. o state State of data port. open The port is assigned to a client. open disabled The port is assigned to a client, but the line entity that port refers to is disabled. 3 line show [node node-id] modem connect - line line-name attribute [,attribute] all [attributes] all characteristics all counters all identifiers all status all interchange circuits Examples: show modem connect line * name, state show modem connect line DSY-0-0 all show modem connect line ddcmp-0 all interchange circuits 4 Characteristics o alternate speed Default: 0 Alternate (low) speed (in bits per second) to operate the line. You can modify this characteristic only when the entity is disabled. This characteristic is supported only when the characteristic communications mode is asynchronous, the characteristic modem control is full, the characteristic modem options includes rateselect, the characteristic clock is internal, and when the alternate line speed is needed. o call accept timer Default: 0 Minimum time (in milliseconds) between the assertion of data set ready and accepting a call by asserting request to send. This characteristic is not supported if the characteristic modem control is none. o carrier loss timer Default: 15000 Maximum time (in milliseconds) that the carrier detect signal can be absent before the loss of carrier event is generated. This characteristic is not supported if the characteristic modem control is none. o clock Source of the transmit and receive clocks. external The modem provides the clock. internal The communications device provides the clock. reflected The DTE transmit clock is a reflection of the DCE transmit clock. This minimizes the clock to data skew that the DCE encounters when high line speeds are used. The default value depends on the setting of the characteristic communications mode. If communications mode is asynchronous, the default value of this characteristic is internal. Otherwise, the default value is external. The value of this attribute has no effect when the communications line is in loopback mode. In this case, the type of loopback determines the type of clock. You can modify this characteristic only when the entity is disabled. o communications mode Default: Sychronous Value: Asynchronous or synchronous Communications method to be used on the link, either asynchronous or synchronous. The value of this characteristic is a copy of the communications mode argument specified when the entity is created. You cannot modify this characteristic. o communications port Default: None Name of the communications port. The value of this characteristic is a copy of the communications port argument specified when the entity is created. You cannot modify this characteristic. o connection type (Tru64 UNIX) Default: Nonswitched Value: Nonswitched or switched Indicates whether the line is switched or non-switched. The value of this characteristic is a copy of the connection type argument specified when the entity is created. You cannot modify this characteristic. o duplex Default: Full Value: Full or half Indicates whether the line is full- or half-duplex. The value of this characteristic is a copy of the duplex argument specified when the entity is created. You cannot modify this characteristic. o encoding Default: normal Value: normal or nrzi Encoding technique used on the line. You can modify this characteristic only when the entity is disabled. o initial hold timer (Tru64 UNIX) Default: 10 Maximum time, in seconds, that the entity waits for an incoming call to be accepted. o maximum call setup timer (Tru64 UNIX) Default: 60 Maximum time, in seconds, that the entity waits for an outgoing call to connect. o maximum disable transmit timer Default: 500 Value: 0-60000 Maximum time, in milliseconds, that clear to send can remain asserted before the line is disconnected after Request to Send is deasserted. This attribute is not supported if the characteristic modem control is set to none. o maximum dsr deassertion timer Default: 5000 Value: 0-60000 Maximum time, in milliseconds, the entity will wait for data set ready to be deasserted after it has deasserted data terminal ready. If this timer expires, the entity assumes it can assert data terminal ready once again. This attribute is not supported if the characteristic modem control is set to none. o maximum enable transmit timer Default: 2000 Value: 1-5000 Maximum time, in milliseconds, between the assertion of the request to send signal and receiving the assertion of the clear to send signal. This attribute is not supported if the characteristic modem control is set to none. o minimum dtr deassertion timer Default: 1000 Value: 0-60000 Minimum timer, in milliseconds, that the DTE will deassert data terminal ready during a disconnection. This attribute is not supported if the characteristic modem control is set to none. o modem control Default: Full Value: Full or none Indicates whether the interchange circuits are to be monitored and used. The value none means that only the data leads are monitored. The value full must be used when the value of the characteristic duplex is half. This characteristic is supported only if the characteristic connection type is switched. o modem options Default: No options Value: Set of options Set of values that determine the capabilities of the modem. dialout The modem can dial the remote modem. Supported only if the value of communications type is switched. This value is supported by Tru64 UNIX only. direct The modem is directly connected to the remote modem through a non-switched line. Supported only if accompanied withdialout and used only when the modem protocol type supports direct dial. This value is supported by Tru64 UNIX only. rate select The modem is capable of data rate selection. o modem protocol format (Tru64 UNIX) Default: See following Value: See following description. description. Format to use for V.25bis protocol messages. This characteristic applies only when the characteristic modem protocol type is v25bis or dmcl. asynchronous Use the asynchronous format. hdlc Use the HDLC format. synchronous Use the synchronous format. The default value depends on the value of the characteristic communications mode. If communications mode is asynchronous, the default value of this characteristic is also asynchronous. If the value of communications mode is synchronous, the default value of this characteristic is hdlc. o modem protocol type (Tru64 UNIX) Default: V25bis Value: See description Protocol that the modem uses to select modem options and to set line control parameters. at A set of automatic calling procedures used in the Hayes Smart Modem 2400. dmcl The Digital Modem Control Language, based on V.25bis. v25 A set of automatic calling and answering procedures defined by CCITT. These procedures use the 200-series circuits defined in the CCITT recommendation V.24. The V.235 procedures are also known as parallel automatic calling procedures. v25bis A set of automatic calling and answering procedures defined by CCITT. These procedures use the 100-series circuits defined in the CCITT recommendation V.24. The V.25bis procedures are also known as serial automatic calling procedures. o profile Default: None Name of the local profile to be used with the line. This profile is used to restrict the range of various line attributes, and to change the defaults for those attributes. The value of this characteristic is a copy of the profile argument specified when the entity is created. o rate select Default: High Value: High or Low Specifies which of the line rates is to be used if none is specified when a call is set up. high The value of the speed characteristic is used. low The value of the alternate speed characteristic is used. o speed Default: 0 High speed, in bits per second, to be used on the line. This value is always used on asynchronous links. It is used on synchronous links only in the following circumstances: o When the value of the clock characteristic is internal o When a null modem cable is detected o When using a loopback mode that uses internal clocking o successful call indication timer Default: 30 Maximum time, in seconds, that the entity will wait for indication of a successful call before disconnecting the line. This attribute is not supported if the characteristic modem control is set to none. o suppress test indicator Default: False Value: True or false Specifies whether the Test Mode signal is to be monitored. If the value is false, a change in the circuit will be monitored and will cause the Test Indication event to be generated. You should set this characteristic to true in cases where the transitions of this signal are not produced by entering test mode, so that this signal should be ignored. o transmit holdoff timer Default: 0 Necessary delay, in milliseconds, between the transmitter being disabled and then reenabled. The value 0 means that the request to send signal can be asserted as soon as the client requests it. This characteristic is not supported if the characteristic modem control is set to none. 4 Counters o cable faults Total number of times that the communications cable was detected as missing or invalid. o creation time Time at which this entity was created. o device errors Total number of times that a potential device error has been reported. o framing errors Total number of framing errors detected on the line. This counter is not supported if the characteristic communications mode is synchronous. o losses of carrier Total number of times that the carrier on the line was lost. This counter is maintained only if the characteristic modem control is none. o losses of clock Total number of times that the transmit or receive clock was lost. o outgoing call failures (Tru64 UNIX) Total number of times that an outgoing call failed to connect. o rate fallbacks Number of times that the DTE changed from the high data rate to the low (alternate) rate. This counter is supported only if the characteristic modem options includes rate select, and if the characteristic modem control is full. o test indications Number of times the DCE was put into test mode by the remote system. This counter is maintained only if the characteristic modem control is set to none. o times cable detected Total number of times that a a valid communications cable was detected following a an error counted by the counter cable faults. o times dce not ready Total number of times that a dce not ready event occurred. This counter is maintained only if the characteristic modem control is set to none. o times reset (OpenVMS) Number of times that the data link client has performed a line reset. o transmit enable timeouts Number of times the DCE failed to assert clear to send in response to request to send. This counter is maintained only if the characteristic modem control is set to none. 4 Identifier o name Simple name assigned to the line. 4 Status o actual speed Actual speed of the line, in bits per second. For internal clocking on some microcoded devices, a value of 0 indicates that the device has selected a speed appropriate for the connected interface. For external clocking, a value of 0 indicates that the speed is unknown. o device availability (OpenVMS) Indicates whether the hardware device associated with the named communications port is installed. Support is mandatory on systems that support line card hot swap. When device availability has the value no device, the interface state takes the value pending DTE Ready and the interface type attribute takes the value unknown. o interface state State of the physical interface on the line. connected A switched line is connected but not yet ready to transmit or receive data. connecting Call setup on a switched line is in progress. disconnecting Call clear on a switched line is in progress. dte not ready The entity is disabled. dte ready The DTE is ready, but the DCE is not ready. full enabled The line is enabled for data transmission and reception. pending dte ready The entity is enabled but the ready state cannot be entered. For example, the communications cable is not connected. ready Both DTE and DCE are ready. receive enabled The line is ready to receive data. transmit enabled The line is ready for data transmission. o interface type Type of the physical interface connection. loopback A loopback connector has been detected on the interface. no cable No cable is connected to the interface. null modem A null modem cable is connected to the interface. rs232c A cable conforming to the RS232C standard is attached. rs422 A cable conforming to the RS422 standard is attached. rs423-v24 This value appears where a cable is attached but the connector cannot distinguish between the RS423 and V.24 standards. rs449 A cable conforming to the RS449 standard is attached. unknown A cable is attached but its type is not known v28 A cable conforming to any of the CCITT V.24, V.28 standards, the IS 2110 standard, or the EIA-232-D standard. v35 A cable conforming to the V35 standard is attached. x.21 A cable conforming to the X.21 standard is attached. o loopback mode Type of loopback in use on the line. The value of this status attribute is determined by the startloop and stoploop commands. connector Data is looped through a loopback connector attached to the communications device. device Data is looped in the communications device. driver Data is looped in the driver of the communications device. external Data is looped through a null modem or a modem in loopback mode. local The communications device has switched its local modem into loopback mode. null The line is not in loopback mode. remote The communications device has switched the remote modem into loopback mode. o modem type String identifying the local modem. If this status attribute has no value, the type could not be determined. o state Operating state of the line. The value of this attribute is affected by the enable and disable commands. off The line has been disabled on The line has been enabled o uid Entity's unique identifier, which is generated when the entity is created. 4 Interchange_Circuits show modem connect line line-id all interchange circuits The modem connect line entity has a special attribute group "interchange circuits", which lets you show a subset of the status attributes. This "interchange circuits" attribute group allows you to examine the instantaneous status of the interchange circuits on the line. These circuits are known by different names in the various interface standards. The following list shows how the status attribute names used in NCL correspond to those used in the interface standards. For instance, the data terminal ready attribute is the name used for the CCITT V.24 circuit 108/2, the EIA-232-D CD circuit, the RS-499 TR circuit, and so on. When entering commands, always use the NCL attribute name. When displayed, each attribute has one of the following values: asserted The circuit is asserted not applicable The circuit does not exist on the interface not asserted The circuit is not asserted unknown The modem cable is not connected or is invalid 5 CCITT_V.24_Circuits Modem Connect Line Interchange Circuits NCL Attribute Name Circuit Description ---------------------------------------------------------------------- carrier detect 109 Data channel received line signal detector clear to send 106 Ready for sending data set ready 107 Data set ready data terminal ready 108/2 Data terminal ready local loopback 141 Local loopback remote loopback 140 Loopback/Maintenance test request to send 105 Request to send ring indicator 125 Calling indicator signalling rate 112 Data signal rate selector(DCE) indicator signalling rate 111 Data signal rate selector (DTE) selector test mode 142 Test indicator 5 DIN_66020_Blatt_1_Circuits Modem Connect Line Interchange Circuits NCL Attribute Name Circuit Description ---------------------------------------------------------------------- carrier detect M5 - clear to send M2 - data set ready M1 - data terminal ready S1.2 - local loopback PS3 - remote loopback PS2 - request to send S2 - ring indicator M3 - signalling rate not - indicator supported signalling rate S4 - selector test mode PM1 - 5 EIA-232-D_Circuits Modem Connect Line Interchange Circuits NCL Attribute Name Circuit Description ---------------------------------------------------------------------- carrier detect CF Received Line Signal Detector clear to send CB Clear to Send data set ready CC DCE Ready data terminal ready CD DTE Ready local loopback LL Local Loopback remote loopback RL Remote Loopback request to send CA Request to Send ring indicator CE Ring Indicator signalling rate CI Data Signal Rate Selector (DCE) indicator signalling rate CH Data Signal Rate Selector (DTE) selector test mode TM Test Mode 5 RS-232-C_Circuits Modem Connect Line Interchange Circuits NCL Attribute Name Circuit Description ---------------------------------------------------------------------- carrier detect - Received Line Signal Detector clear to send - Clear to Send data set ready - Data Set Ready data terminal ready - Data Terminal Ready local loopback - not supported remote loopback - not supported request to send - Request to Send ring indicator - Ring Indicator signalling rate - Data Signal Rate Selector (DCE) indicator signalling rate - Data Signal Rate Selector (DTE) selector test mode - not supported 5 RS-449_Circuits Modem Connect Line Interchange Circuits NCL Attribute Name Circuit Description ---------------------------------------------------------------------- carrier detect RR Receiver Ready clear to send CS Clear to Send data set ready DM Data Mode data terminal ready TR Terminal Ready local loopback LL Local Loopback remote loopback RL Remote Loopback request to send RS Request to Send ring indicator IC Incoming Call signalling rate SI Signaling Rate Indicator indicator signalling rate SR Signaling Rate Selector selector test mode TM Test Mode 2 mop show [node node-id] mop attribute [,attribute...] all [attributes] all characteristics all status Example: show mop all show mop state, supported functions 3 Characteristics o supported functions MOP components supported on the system. This is a read-only attribute. configuration monitor load server console requester loop requester dump server query requester load requester (Tru64 UNIX) test requester o version Default: Current version number Version number of the Maintenance Operations Protocol specification to which the implementation conforms. This is a read-only attribute. 3 Status o state State of the mop entity. This is a read-only attribute. off The mop entity is disabled. on The mop entity is enabled. 3 circuit show [node node-id] mop - circuit circuit-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Example: show mop circuit * name, functions show mop circuit fddi-1 all 4 Identifiers o name Simple name assigned to the mop circuit when it was created. 4 Characteristics o known clients only Default: False Value: True or False Specifies whether MOP attempts to service load requests from remote systems which do not have a corresponding client entity. Some network servers are designed to request specific software by name, and in such a case there is no need for a client entity to exist. By default, MOP tries to process requests for named software from unknown clients. Set this attribute to true if you wish MOP to ignore such requests. o link name Default: No name Value: Data Link entity name Name of a station entity in the Data Link layer module indicated by the type characteristic. This name is passed to the Data Link layer module when MOP opens a portal for the circuit. o retransmit timer Default: 4 Value: 1-30 Time (in seconds) to wait for a response before retransmitting a MOP protocol message. o type Specifies the circuit type. This characteristic is set when the circuit is created (see the create command). The possible types are CSMA-CD, FDDI, HDLC (Tru64 UNIX loop only), DDCMP (OpenVMS VAX only), and LAPB (OpenVMS only). You cannot modify this characteristic. 4 Counters o creation time Time this entity was created. o dump requests completed Number of dump service requests that completed successfully. o failed dump requests Number of dump service requests that could not be completed. o failed load requests Number of load service requests that could not be completed. o load requests completed Number of load service requests that completed successfully. o unrecognized dump clients Number of dump service requests that could not be processed because a required client database entry could not be found. o unrecognized load clients Number of load service requests that could not be processed because a required client database entry could not be found. 4 Status o functions Which optional MOP functions are currently enabled for this circuit. configuration monitor load server console requester loop requester dump server query requester load requester (Tru64 UNIX) test requester To enable mop circuit functions, see the enable mop circuit command. o uid Entity's unique identifier, which is generated when the entity is created. 4 operation show [node node-id] mop - circuit circuit-name - operation operation-name attribute [,attribute...] all [attributes] all identifiers all status Example: show mop circuit csmacd-1 operation * all Displays mop circuit operation entities which are created automatically by MOP for all operations, including those initiated by NCL commands and those initiated by automatic load and dump service. These entities are deleted when the corresponding operation is commplete. 5 Identifier o name Simple name of the operation entity that is generated automatically by MOP. The simple name is derived from the operation being performed (load or dump) and a numeric suffix added to ensure uniqueness. 5 Status o address For LANs only, specifies the address of the client system. o client Client name of the client entity associated with the operation, if such an entity exists. o operation The operation being performed (boot, dump, load, loop, query, or test). 4 station show [node node-id] mop - circuit circuit-name - station station-name attribute [,attribute...] all [attributes] all identifiers all status Example: show mop circuit csmacd-1 station * all Displays mop circuit station entities which are created automatically by the Configuration Monitor. They are deleted when the circuit entity is deleted. NOTE The Configuration Monitor function must be enabled on the mop circuit to obtain the status information used by the show mop circuit station command. Refer to the enable mop circuit command for more information. 5 Identifier o name Name of the station entity, generated automatically by the Configuration Monitor. The name is identical to the source LAN address for the System ID message. 5 Status o command size Maximum acceptable console command size. A zero value means it is not applicable. o console user LAN address of the system which currently has the console reserved; all zeroes if the console is not in use. o data link Data Link protocol used by the remote station. o device Type of communication device used by the remote station. o dsdu size Maximum allowed size for a MOP message, not including data link protocol overhead. o functions The set of functions supported: loop server, dump requester, primary loader, secondary loader, boot, console carrier, and counters. o hardware address Default data link address for the circuit on which the system ID was transmitted by the remote station. o last report Time at which the most recent system ID message was received. o mop version Highest version of the MOP protocol supported by the remote station. o node id Node ID for the remote station. If not reported, the null ID (00-00-00-00-00-00) is displayed. o node name Node name for the remote station, as a DECdns full name. If not reported by the remote station, the null name is used; this is displayed as "0:.". o reservation timer Console reservation timer, in seconds. A zero values means it is not applicable. o response size Maximum acceptable console response size. A zero value means it is not applicable. 3 client show [node node-id] mop - client client-name attribute [,attribute...] all [attributes] all characteristics all identifiers 4 Identifiers o name Simplename assigned to the MOP Client entity when it was created. 4 Characteristics o addresses Default: Empty set Value: Set of LAN addresses Set of LAN addresses for this client on the circuit specified by the circuit characteristic. For OpenVMS, Phase IV nodes can use an extended DECnet LAN address in addition to their hardware address, so you must include both of these addresses in the addresses set. To calculate the extended DECnet address, express the Phase IV node address as a four-digit hex integer, then add the prefix AA-00-04-00. For example, if the Phase IV node address is 4.260: 4.260 => 4 * 1024 + 260 => 4356 (decimal) => 1104 (hex) => AA-00-04-00-04-11 o circuit Default: No circuit Value: Circuit-id Name of the MOP circuit that corresponds to the Data Link circuit that is to be used for communicating with this client. o device types (OpenVMS) Default: No device types Value: Set of device types Specifies one or more device types associated with this client. Use device types and omit addresses if you want to set up a generic client entity; the entity will be used for any incoming load or dump requests that specify a matching communications device type. To determine the communications device type for a particular network server, consult the server documentation, or use the Configuration Monitor Function of MOP. o diagnostic image Default: No file Value: Sequence of file specifications Files to be loaded when the client requests a diagnostic image during a downline load operation. File identifications are interpreted according to the file system of the local system. o dump address Default: 1 Value: 0 to 232 -1 Memory address at which to begin an upline dump. o dump file Default: No file Value: Sequence of file specifications Files to write to when the client is upline dumped. File identifications are interpreted according to the file system of the local system. o management image Default: No file Value: Sequence of file specifications Files to be loaded when the client requests a management image during a downline load operation. File identifications are interpreted according to the file system of the local system. o phase iv client address Default: 0.0 Value: Phase IV address Phase IV node address given to the client system when it is downline loaded. This address is passed in a load parameters message; whether it is needed depends on the software being loaded. o phase iv client name Default: No name Value: Phase IV name Phase IV node name given to the client system when it is downline loaded. This name is passed in a load parameters message; whether it is needed depends on the software being loaded. o phase iv host address Default: 0.0 Value: Phase IV address Phase IV node address to be passed as the host node address when a client is downline loaded. This address is passed in a load parameters message; whether it is needed depends on the software being loaded. o phase iv host name Default: No name Value: Phase IV name Phase IV node name that is passed as the host name when the client is downline loaded. This name is passed in a load parameters message; whether it is needed depends on the software being loaded. o script file Default: No file Value: Sequence of file specifications Files to be loaded when the client requests a CMIP initialization script during a downline load operation. File identifications are interpreted according to the file system of the local system. o secondary loader Default: No file Value: Sequence of file specifications Files to be loaded when the client requests a secondary loader during a downline load operation. File identifications are interpreted according to the file system of the local system. o system image Default: No file Value: Sequence of file specifications Files to be loaded when the client requests an operating system image during a downline load operation. File identifications are interpreted according to the file system of the local system. o tertiary loader Default: No file Value: Sequence of file specifications Files to be loaded when the client requests a tertiary loader during a downline load operation. File identifications are interpreted according to the file system of the local system. o verification Default: %x00-00-00-00-00-00 Hex string Verification string to be sent in a boot message to this client. The value must have an even number of digits from 2 to 16. 2 ncl 3 default show ncl default Shows default access control and entity information which was previously set using the SET NCL DEFAULT ACCESS and SET NCL DEFAULT ENTITY commands. Refer to HELP NCL DEFAULT_CONTEXT for more detailed information. For example, on OpenVMS: NCL>SET NCL DEFAULT ENTITY NODE remnod"user1 agoodpassword" NCL>SHOW NCL DEFAULT NCL Default Access by User user1, Password xxx NCL Default Entity Node remnod 4 access show ncl default access Shows default access control information which was previously set using the SET NCL DEFAULT ACCESS command. Refer to HELP NCL DEFAULT_CONTEXT for more information. 4 entity show ncl default entity Shows default entity information which was previously set using the SET NCL DEFAULT ENTITY command. Refer to HELP NCL DEFAULT_CONTEXT for more information. 3 logfile show ncl logfile This will display the name of the log file which was established earlier in the NCL session with the "set ncl logfile" and "enable ncl logging" commands. For example, on OpenVMS: NCL>set ncl logfile test NCL>enable ncl logging NCL>show all NCL>disable ncl logging NCL>show ncl logfile Logfile name is: test Logfile is Disabled The results will be in the file TEST.NCL. That file will contain the logged NCL command(s), and the output will be commented out. You may then reissue the command(s) you logged by: NCL>do test.ncl 2 node Shows all attributes of the specified node. show [node node-id] attribute [,attribute...] all counters all [attributes] all characteristics all identifiers all status Some command examples follow. The local node (node 0) is implied if a node is not provided in the command. Therefore, this will show the name and address of the local node: show name, address Note that the "show version" command does not give the DECnet version, it instead shows the version of the network management architecture. To view the operating system and DECnet version of the local node, use this command: show implementation To show all the node attributes of the remote node "remnod": show node remnod all 3 Characteristics o implementation Particular DECnet implementation of the node. You cannot modify this characteristic. o listener template (Tru64 UNIX) Name of the OSI transport template to be passed through the CMIP listener to session control. You cannot modify this characteristic. o maximum listeners (Tru64 UNIX) Maximum number of CMIP listeners that the node supports. Zero specifies an unlimited number of listeners. You cannot modify this characteristic. o version Version number of the network management architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 Counters o changes of address Number of times the node's address has changed. o changes of id Number of times the node's ID has changed. o creation time Time at which the entity was created. This time reflects the time at which the node was first booted. o idrom check failures Number of times an IDROM was checked for consistency and was found to be in error. o renames Number of times the node has been renamed (see the rename command. 3 Identifiers o address Set of protocol towers that together form a Session Control application address for the node's CMIP listener. o name Full name of the node as it is registered in your name space name is the primary identifier. 3 Status o functions enabled Functions that are currently enabled for the node (see the enable command). o id Indicates the unique 48-bit ID of the node. o state State of the node. booting The node is attempting to downline load. You cannot manage the node in this state. If the boot process is successful, the node enters the off state. (OpenVMS) dead The node is unusable and unmanageable as the result of a power failure or similar event. The node must be rebooted. (OpenVMS) off The node is manageable, but not all of its functions are enabled. on All of the node's functions are enabled and the node is fully manageable. The on state is the normal operating state. o uid Node's unique identifier, which is generated when the node is created. 2 nsp show [node node-id] nsp attribute [,attribute...] all [attributes] all characteristics all status Examples: show nsp all show nsp congestion avoidance, maximum transport connections 3 Characteristics o acknowledgment delay time Default: 3 Value for OpenVMS: 0-65 Default: 3 Value for Tru64 UNIX: 3 Maximum amount of time (in seconds) that an acknowledgment is to be withheld. You cannot modify this characteristic. o congestion avoidance Default: True Value: True or false Enables the use of the automatic congestion avoidance mechanism. This mechanism reduces the transport window size in response to an indication from the Network layer. o delay factor Default: 2 Value: 2-15 Factor by which to multiply the current value of the round-trip delay estimate status attribute in order to set a value for the retransmission timer. Note, the roundtrip delay estimate is an attribute of the nsp port entity. o delay weight Default: 3 Value: 0-255 Relative weighting to apply to the current estimate and to a new sample when estimating round-trip delay. o dna version Default: current version number Version number of the DNA NSP architecture specification to which the implementation conforms. You cannot modify this characteristic. o flow control policy Default: Segment flow control Value: Segment flow control no flow control Determines NSP flow control policy used. This attribute may not be changed when NSP state is "on." Flow control is the mechanism that determines when to send a Data or expedited messages. Flow control is performed separately for normal and expedited data. During transport connection formation, each end of the connection determines the kind of flow control policy it expects when acting as a data receiver. It is not required that both end operate with the same flow control policy. o keepalive time Default for Tru64 UNIX: 30 Value: 1-65535 Default for OpenVMS: 60 Value: 1-65535 Time (in seconds) that NSP waits for data to be transmitted or received before testing a transport connection. When this timer expires, NSP sends a data request PDU to the remote NSP. This PDU does not change the flow control parameters, but does require acknowledgment. For Tru64 UNIX, you can modify this characteristic to a lower value only when the entity is disabled. o maximum receive buffers (OpenVMS) Default: 2000 Value: 1-65535 Maximum number of receive buffers that can store received transport PDUs. You may not decrease the value while NSP is enabled. o maximum remote nsaps Default for Tru64 UNIX: 160 Value: 1-65535 Default for OpenVMS: 200 Value: 1-65535 Maximum number of remote NSAPs that can exist concurrently. Must be greater than the current value of maximum transport connections. You can modify this characteristic to a lower value only when the entity is disabled. For Tru64 UNIX, this characteristic can be increased when enabled. o maximum transport connections Default for Tru64 UNIX: 128 Value: 0-1023 Default for OpenVMS: 200 Value: 0-65535 Maximum number of active transport connections allowed at one time. Must not be less than the current value of maximum remote NSAPs. You may not decrease the value while NSP is enabled. o maximum window Default for Tru64 UNIX: 32 Value: 1-65535 Default for OpenVMS: 8 Value: 1-2047 Maximum credit window that can be granted on a transport connection. This is used for control of the number of data segments (PDUs) allowed to be transmitted over a particular transport connection before at least one acknowledgment must be returned from the destination system. If the number of PDUs already transmitted equals the maximum window and no corresponding acknowledgments have been received, transport stops sending PDUs over the transport connection and waits for an acknowledgment message. You cannot modify this characteristic. o nsap selector Default: 32 Value: 0-255 NSAP selector used by the nsp entity when opening a port to a network service. You cannot modify this characteristic. o retransmit threshold Default for Tru64 UNIX: 12 Value: 1-65535 Default for OpenVMS: 5 Value: 1-65535 Maximum number of times a source nsp entity is to restart an expired retransmission timer before the remote node is to be considered unreachable. When the threshold is reached, NSP sets the confidence variable to false. 3 Status o currently active connections Number of active transport connections. o state Status of the nsp entity. off The nsp entity is disabled. on The nsp entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 local_nsap show [node node-id] nsp - local nsap nsap-address attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show nsp local nsap * name, nsap address show nsp local nsap 490022AA000400818920 all 4 Counters o creation time Time this entity was created. o deleted remote nsaps Number of times a remote NSAP has been deleted in order to reclaim resources. 4 Identifier o name Simplename assigned to the local NSAP when it was automatically created. 4 Status o nsap address Address assigned to the local NSAP when it was created. o uid Entity's unique identifier, which is generated when the entity is created. 4 remote_nsap show [node node-id] nsp - local nsap nsap-address - remote nsap nsap-address attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show nsp local nsap 490022AA000400818920 - remote nsap * name, nsap address show nsp local nsap 490022AA000400818920 - remote nsap 490021AA0004009F8420 all 5 Counters o connects received Total number of CR transport PDUs, regardless of their disposition, that the local NSAP has received from the remote NSAP. o connects sent Total number of CR transport PDUs sent by the local NSAP to the remote NSAP, including retransmissions. o creation time Time this entity was created. o duplicate pdus received Total number of all types of detected duplicate transport PDUs received from the remote NSAP. o pdus received Total number of all types of transport PDUs received from the remote NSAP (excluding detected duplicates). o pdus sent Total number of all types of transport PDUs sent to the remote NSAP (excluding retransmissions). o rejects received Number of detected reject received events. o rejects sent Number of detected reject sent events. o remote protocol errors Number of detected remote protocol error events. o retransmitted pdus Total number of all types of retransmitted transport PDUs sent to the remote NSAP. o total octets received Total number of octets of all types of transport PDUs received from the remote NSAP, regardless of their disposition. This count includes detected duplicates. o total octets sent Total number of octets of all types of transport PDUs sent to the remote NSAP, including retransmissions. o user octets received Total number of user data octets received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as data retransmitted by the remote NSAP. o user octets sent Total number of octets of all types of transport PDUs the total number of user data octets sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include data retransmitted by the local NSAP. o user pdus discarded Number of PDUs received from the remote NSAP that were discarded because of insufficient buffer space. o user pdus received Total number of transport PDUs containing user data received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as transport PDUs retransmitted by the remote NSAP. o user pdus sent Total number of transport PDUs containing user data sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include retransmitted transport PDUs. 5 Identifier o name Simple name assigned to the remote NSAP when it was automatically created. 5 Status o nsap address Address assigned to the remote NSAP when it was created. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] nsp - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show nsp port * name show nsp port NSP$PORT_0000202A client name, remote nsap show nsp port NSP$PORT_0000202A all show nsp port * with remote nsap = 49::00-37:AA-00-04-00-63-DE:20 4 Counters o creation time Time the port was assigned. o duplicate pdus received Total number of all types of detected duplicate transport PDUs received from the remote service provider. o pdus received Total number of all types of transport PDUs received from the remote service provider (excluding retransmissions). o pdus sent Total number of all types of transport PDUs sent to the remote NSAP (excluding retransmissions). o retransmitted pdus Total number of all types of retransmitted transport PDUs sent to the remote NSAP. o total octets received Total number of octets of all types of transport PDUs received from the remote NSAP, regardless of their disposition. This count includes detected duplicates. o total octets sent Total number of octets of all types of transport PDUs sent to the remote NSAP, including retransmissions. o user octets received Total number of user data octets received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as data retransmitted by the remote NSAP. o user octets sent Total number of user data octets sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include data retransmitted by the local NSAP. o user pdus received Total number of transport PDUs containing user data received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as transport PDUs retransmitted by the remote NSAP. o user pdus sent Total number of transport PDUs containing user data sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include retransmitted transport PDUs. 4 Identifier name Simple name assigned to the port when it was created. 4 Status o client name Default: None Value: Local-entity-name Name designated by the port user when the port was opened. o local nsap Default: None Value: NSAP address Local NSAP address being used for the transport connection. o local reference Default: None Value: 0-65535 Unique reference number assigned to the transport connection by the local transport service provider. o network port Default: None Value: Local-entity-name Name of the network port being used. o remote nsap Default: None Value: NSAP address Remote NSAP address being used for the transport connection. o remote reference Default: None Value: 0-65535 Reference number assigned to the transport connection by the remote NSAP. o roundtrip delay estimate Default: None Value: 0-65535 Amount of time, in milliseconds, of the roundtrip delay on the transport connection. o uid Default: None Value: uid Entity's unique identifier, generated when the entity is created. 2 osak show [node node-id] osak attribute [,attribute...] all [attributes] all characteristics all counters all status Examples: show osak state, protocol versions show osak all 3 Characteristics o disconnect timer (OpenVMS) Default: 30 seconds Value: Time in seconds Length of time that the OSAK software waits when it expects the remote peer to disconnect a transport connection. If the timer expires and the remote peer has not disconnected the connection, the OSAK software disconnects the connection. You can modify this attribute using the set command. o protocol versions Default: {ACSE = {1}, Value: Set of protocol versions presentation = {1}, session = {1,2} } Specifies the ACSE, presentation and session protocol versions being used by the osak entity. The full range of possible sets of values is: {ACSE = {1}, presentation = {1}, session = {1,2} } {ACSE = {1}, presentation = {1}, session = {1} } {ACSE = {1}, presentation = {1}, session = {2} } You cannot modify this attribute. 3 Counters o aborts received Number of aborts received by this osak entity since its creation. o aborts sent Number of aborts sent by this osak entity since its creation. o connects accepted Number of connection requests accepted by this osak entity since its creation. o connects initiated Number of connection requests initiated by this osak entity since its creation. o connects rejected Number of connection requests rejected by this osak entity since its creation. o creation time Time at which the osak entity was created, in binary absolute time format. o releases received Number of release requests received by this osak entity since its creation. o releases sent Number of release requests sent by this osak entity since its creation. o unknown ae-titles Number of connection requests received that contain an unknown application entity title. This counter is incremented each time an unknown ae-title event occurs. o unknown invocations Number of connection requests received that contain an unknown invocation identifier. This counter is incremented each time an unknown invocations event occurs. o unknown paddresses Number of connection requests received that contain an unknown presentation address. This counter is incremented each time an unknown paddress event occurs. 3 Status o state State of the osak entity. The value is one of the following: noinbound osak entity cannot receive inbound association requests notavailable osak entity is not available operational osak entity is enabled and operational shutting osak entity is shutting down o uid Entity's unique identifier, which is generated when the entity is created. 3 application show [node node-id] osak - application "presentation address" attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Example: show osak application * show osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" all show osak application * paddress, ae titles, template 4 Characteristics o ae titles Default: None Value: See description The application entity titles that map to this application's presentation address. o startup policy Default: Existing Value: New or existing Defines the startup policy for invocations of this application. For Tru64 UNIX, the value is always existing. This indicates that a listener process must exist for an inbound connection to be processed. No new process is started up when an inbound connection arrives. For OpenVMS, the value is one of the following: new Indicates that, when no process is available to handle an inbound connection, a new process is started up. existing Indicates that one process handles all inbound connections. No new process is started up if the existing process is busy when an inbound connection arrives. For OpenVMS, you can modify this attribute using the set command. o template Default: Default OSI Value: See description transport template The transport template used for inbound association requests. For OpenVMS, you can modify this attribute using the set command. 4 Counters o creation time The time at which the application is created. o invalid mode failure The number of times that an inbound connection request is rejected because of a mismatch of modes. This counter is incremented each time an invalid mode event occurs. The possible modes are normal and X.410-1984. An application is running in normal mode if it uses the upper layers of the OSI stack. An application is running in X.410-1984 mode if it does not use the upper layers of the OSI stack. o resource failures The number of times that an inbound connection request was rejected due to insufficient system resources. o total invocations The number of times this application has been invoked. 4 Identifier o paddress The presentation address of this OSAK application. 4 Status o active invocations The number of existing invocations of this application. o uid Entity's unique identifier, which is generated when the entity is created. 4 invocation show [node node-id] osak - application "presentation address" - invocation invocation-identifier attribute [,attribute...] all [attributes] all char (OpenVMS) all counters all identifiers all status Examples: show osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" - invocation * all 5 Characteristic_(OpenVMS) o startup information Invocation startup information that is system-specific. This information is needed only for passive applications. Refer to the following table for specific startup information: Mandatory Item Value Description --------------------------------------------------------------- user name The username of the process that will respond to connect requests received by this application. file pathname The name of the file to run to start up the named application. The file is a command file or an executable image that is run each time a passive process starts. HP recommends that you use a command file for this purpose. Optional Item Value Description --------------------------------------------------------------- account name The account that is to start the process. max resp integer The highest permissible number of responders, for an application with the new setting for startup policy. password password The user's password. sversion {1}, The session version. {2}, or {1,2} You can modify the startup information attribute using the set command. You can specify the items in any order. Note that when you modify this attribute, any item for which you do not specify a value is set to its default, not to its previous value. For example, you could set up non-default values for all four items in this attribute using the following NCL command: set [node node-id] osak application "presentation address" - invocation invocation-identifier - startup policy "password=password, username=username, - file=file name, sversion=sversion" If you then decide to change the value of the password, but to keep the non-default values of the other items, you should use the following command: set [node node-id] osak application "presentation address" - invocation invocation-identifier - startup policy "password=new password, username=username - file=file name, sversion=sversion" 5 Counters o creation time Time at which this invocation was registered with OSAK. o total associations Number of associations set up to this invocation. 5 Identifier o ids The identifier of the invocation. For OpenVMS, you cannot modify this attribute. 5 Status o port list A list of the OSAK ports referenced by this application invocation entity. o state The state of the application invocation entity. For Tru64 UNIX, the value is always active. For OpenVMS, the value is one of the following: active An active application invocation is using an active process. passive A passive application invocation is waiting for inbound connection requests on its presentation address. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] osak - port port-id attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show osak port * show osak port 'A6000000A8701900'H all 4 Characteristic o template Default: Default OSI Value: See description transport template The name of the transport template used when establishing an association. 4 Counter o creation time Time at which the association was set up, in binary absolute time format. 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o application context Name of the application context for this association. o connection state Specifies the state of an association. This status attribute can have one of the following values: awaiting associate A port entity is in this confirm state when waiting for confirmation of an association from a remote peer entity. awaiting associate A port entity is in this response state when waiting for a response from the user application to an association request. awaiting inbound A port entity is in connection this state when waiting for an association indication from a remote peer entity. awaiting redirection A port entity is in this state when an application has opened a new port to which the association is to be redirected. connected A port entity is in this state when an association is set up and data exchange is taking place. not connected A port entity is in this state either after the port is opened but before an association request is received from a remote peer entity, or after an association is closed down but before the port is closed. disconnected A port entity is in this state when the local application has sent a request to release the association, but the remote peer entity has not sent a response. redirected A port entity is in this state after an association has been redirected to another process. o direction Specifies whether an association is inbound (the port was opened by a responder) or outbound (the port was opened by an initiator). o invocation UID of the invocation that opened this port. o local ae title Local application entity title. o local ae invocation id Local application entity invocation identifier. o local ap invocation id Local application process invocation identifier. o local paddress Local presentation address. o owner id Process id of the OSAK application. o remote ae title Remote application entity title. o remote ae invocation id Remote application entity invocation identifier. o remote ap invocation id Remote application process invocation identifier. o remote paddress Remote presentation address. o uid Entity's unique identifier, which is generated when the entity is created. 2 osi_transport show [node node-id] osi transport attribute [,attribute...] all [attributes] all characteristics all status Examples: show osi transport all show osi delay weight, delay factor 3 Characteristics o clns classes supported Default: Class {4} Value: Bit-set Set of protocol classes supported on the Connectionless Networt Service (CLNS). You cannot modify this characteristic. o cltp nsap selector (Tru64 UNIX) Default: 0 Value: 0-255 (except 32) The NSAP selector to use for CLTS when running over CLNS. If the value is 0 or 1, a single NSAP is shared between the Connection- Oriented Transport Service (COTS), and the connectionless transport protocol according to the osi transport attribute nsap selector. If both nsap selectors are 0 or 1, then COTS and CLTS over CLNS are disabled. This attribute cannot be set either to 32, which is the value of the NSP NSAP selector, or to the current setting of the osi transport attribute, nsap selector, if the attribute has a value other than 0 or 1. This attribute cannot be modified when transport is enabled. o congestion avoidance Default: True Value: True or false Enables the use of the automatic congestion avoidance mechanism to reduce the transport window size in response to an indication from the Network layer when operating on the Connectionless Network Service (CLNS). o cons classes supported Default: Classes {0, 2, 4} Value: set of classes Set of protocol classes supported on the Connection-Oriented Network Service (CONS). You cannot modify this characteristic. See X.25/CONS Configuration for more information. o cons filters Default: { } Value: Set of simple names The names of X.25 Access module filters used to determine which inbound network connection requests should be directed to the transport entity. On OpenVMS Modification of this attribute while OSI transport is enabled is permitted only with the add command. The set and remove commands can only be used to modify this attribute when the OSI transport is disabled. For each cons filter, there must be a corresponding x25 access template with the same name. One or more of these filters must be specified in order to run COTS over CONS. The X.25 access filter osi transport is typically used. See X.25/CONS Configuration for more information. o cons nsap addresses Default: { } Value: Set of NSAP addresses The set of valid NSAP addresses for use with CONS. One or more NSAPs must be specified to run COTS over CONS. See the DECnet-Plus for Tru64 UNIX Programming manual for more information. o delay factor Default: 4 Value: 2-15 Factor by which to multiply the current value of the round-trip delay estimate status attribute in order to set a value for the retransmission timer. This attribute works with protocol class 4 only. o delay weight Default: 5 Value: 0-255 Relative weighting to apply to the current estimate and to a new sample when estimating round-trip delay. This attribute works with protocol class 4 only. o disconnect holdback Default: 0 Value for Tru64 UNIX: 0-(2 raised to the power of 31 -1) Default: 0 Value for OpenVMS: 0-4294967295 When operating over the Connection-Oriented Network Service (CONS), the length of the time to maintain a network connection for possible reuse after all transport connections multiplexed upon it have been disconnected. Specified in seconds. This characteristic may not be changed while the transport entity is enabled. See X.25/CONS Configuration for more information. o dna version Default: Value: V1.0.0 Version number of the DNA OSI Transport architecture specification to which the implementation conforms. You cannot modify this characteristic. o iso version Default: Value: 1 Version number of ISO 8073 to which the implementation conforms. You cannot modify this characteristic. o maximum cltp ports (Tru64 UNIX) Default: 128 Value: 0-4294967295 Maximum number of CLTS ports at one time. This characteristic can only be increased while transport is enabled. You can modify this characteristic to a lower value only when the entity is disabled. o maximum listeners (Tru64 UNIX) Default: 32 Value: 1-65535 Maximum number of listeners at one time. This characteristic can only be increased while transport is enabled. You can modify this characteristic to a lower value only when the entity is disabled. o maximum multiplexing Default for Tru64 UNIX: 1023 Value: 1-1023 Default for OpenVMS: 4294967295 Value: 1-4294967295 When operating over the Connection-Oriented Network Service (CONS), the maximum number of transport connections that can be multiplexed on any single network connection. This characteristic can be increased only when the transport entity is enabled. You can modify this characteristic to a lower value only when the entity is disabled. See X.25/CONS Configuration for more information. o maximum network connections Default for Tru64 UNIX: 1023 Value: 0-1023 Default for OpenVMS: 4294967295 Value: 0-4294967295 When operating over the Connection-Oriented Network Service (CONS), the maximum number of network connections which can be in use concurrently by DNA OSI Transport. This characteristic can be incresed only when the transport entity is enabled. See X.25/CONS Configuration for more information. o maximum receive buffers (OpenVMS) Default: 2000 Value: 1-4294967295 Maximum number of receive buffers that can store received DT transport PDUs. You can modify this characteristic only when the entity is disabled. Also, you can only increase the characteristic value. o maximum remote nsaps Default for Tru64 UNIX: 160 Value: 1-65536 Default for OpenVMS: 201 Value: 0-4294967295 Maximum number of remote NSAPs that can exist concurrently. This value must be greater than the current value of maximum transport connections. You can modify this characteristic to a lower value only when the entity is disabled. This characteristic can be increased when enabled. o maximum transport connections Default for Tru64 UNIX: 128 Value: 0-1023 Default for OpenVMS: 200 Value: 0-4294967295 Maximum number of active transport connections allowed at one time. Must be less than the current value of maximum remote nsaps. You can modify this characteristic to a lower value only when the entity is disabled. o maximum window Default for Tru64 UNIX: 20 Value: 1-65535 Default for OpenVMS: 8 Value: 1-65535 Maximum credit window that can be granted on a transport connection. This is used for control of the number of data segments (PDUs) allowed to be transmitted over a particular transport connection before at least one acknowledgment must be returned from the destination system. If the number of PDUs already transmitted equals the maximum window and no corresponding acknowledgments have been received, transport stops sending PDUs over the transport connection and waits for an acknowledgment message. You can modify this characteristic to a lower value only when the entity is disabled. o nsap selector Default: 33 Value: 0-255 (except 32) The NSAP selector to use for the Connection-Oriented Transport Service (COTS) when running over CLNS. If 0 or 1, COTS over CLNS is not enabled. This attribute cannot be set to 32, which is the value of the NSP NSAP selector. Or, on Tru64 UNIX, to the current setting of the osi transport attribute cltp nsap selector if it is other than 0 or 1. This attribute cannot be modified when transport is enabled. o RFC1006 listener ports (OpenVMS) Default: { 102, 399 } Value: Set of TCP/IP port numbers The names of the TCP listener ports used to receive inbound RFC1006 connection requests. This is applicable for both RFC1006 and RFC1006 Extension connections. Modification of this attribute while OSI transport is enabled is permitted only with the add command. The set and remove commands can only be used to modify this attribute when the OSI transport is disabled. o RFC1006 listener ipaddresses (OpenVMS) Default: { 0.0.0.0 } Value: Set of IP Addresses The names of the listener IP addresses used to receive inbound RFC1006 connection requests. This is applicable for both RFC1006 and RFC1006 Extension connections. Modification of this attribute while OSI transport is enabled is permitted only with the add command. The set and remove commands can only be used to modify this attribute when the OSI transport is disabled. o support map Default: None Value: False Specifies whether the implementation supports the MAP (manufacturing automation protocol) entity. You cannot modify this characteristic. 3 Status o currently active cltp ports (Tru64 UNIX) Number of active CLTS ports. o currently active connections Number of active transport connections. o currently active listeners (Tru64 UNIX) Number of active listeners. The session control listener (local transport selector 'DEC0'H) can exist even when osi transport is disabled. All other listeners are deactivated when transport is disabled. o state Status of the osi transport entity. off The osi transport entity is disabled. on The osi transport entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 application_(OpenVMS) show [node node-id] osi transport - application application-name attribute [,attribute] all [attributes] all characteristics all counters all identifiers Examples: show osi transport application * all show osi transport application %x0003 called tsels, user name show osi transport application osit$ivp all 4 Characteristics o called tsels Default: No tsap Value: Hex-string A TSEL is a string of hex digits, the length of that string should be an even number between 2 and 64, inclusive. This attribute cannot have more than one member. Transport Service Access Point (TSAP) for which the image specified by the image name characteristic accepts connections. This characteristic, which is similar to the addresses characteristic, is used by applications that do not use the DNA session control protocol (for example, VOTS applications). o file name Default: No file name Value: Filename File name of the program to be invoked upon receipt of a connect request containing a TSEL matching the "Called TSELS" attribute of the application entity. o user name Default: No user name Value: Username User name portion of the access control information that identifies the account under which the application is to run. If invalid information or no user name is specified, system defaults are used to select the user. 4 Counter o creation time Time at which the entity was created. 4 Identifier o name Simple name assigned to the application when it is created. 3 local_nsap show [node node-id] osi transport - local nsap nsap-address attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show osi transport local nsap * all show osi transport local nsap 490004aa000400941321 all 4 Counters o creation time Time this entity was created. o deleted remote nsaps Number of times a remote NSAP has been deleted in order to reclaim the resources. 4 Identifier o name Simple name assigned to the local NSAP when it was automatically created. 4 Status o DTE address Default: Entity DTE address Value: DTE address Address assigned to the DTE when it is created. o IP address Default: Entity IP address Value: IP address Address assigned to the IP when it is created. o network service Default: CLNS Value: Any, CLNS, CONS, or RFC1006 (OpenVMS) Type of network service being used. o nsap address Default: Entity NSAP address Value: NSAP address NSAP address corresponding to entity. o uid Entity's unique identifier, generated when the entity is created. 4 remote_nsap show [node node-id] osi transport - local nsap nsap-address - remote nsap nsap-address attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show osi transport local nsap 490004aa000400941321 - remote nsap * all show osi transport local nsap 490004aa000400941321 - remote nsap 490004aa000400554421 all 5 Counters o connectionless bytes received (Tru64 UNIX) Number of bytes received in UD TPDUs from this remote service provider. o connectionless bytes sent (Tru64 UNIX) Number of bytes sent in UD TPDUs to this remote service provider. o connects received Total number of CR TPDUs, regardless of their disposition, that the local NSAP has received from the remote NSAP. o connects sent Total number of CR TPDUs sent by the local NSAP to the remote NSAP, including retransmissions. o creation time Time this entity was created. o duplicate pdus received Total number of all types of detected duplicate TPDUs received from the remote NSAP. o failed checksums Number of checksum failure events detected. o local protocol errors Number of reported local protocol error events. This event is generated whenever an ER (error) TPDU is received from the remote NSAP. o pdus received Total number of all types of TPDUs received from the remote NSAP (excluding detected duplicates). o pdus sent Total number of all types of TPDUs sent to the remote NSAP (excluding retransmissions). o rejects received Number of detected reject received events. o rejects sent Number of detected reject sent events. o remote protocol errors Number of reported invalid tpdu received events. This event is generated whenever the remote NSAP violates the Transport Protocol. o retransmitted pdus Total number of all types of retransmitted TPDUs sent to the remote NSAP. o total octets received Total number of octets of all types of TPDUs received from the remote NSAP, regardless of their disposition. This count includes detected duplicates. o total octets sent Total number of octets of all types of TPDUs sent to the remote NSAP, including retransmissions. o ud pdus received (Tru64 UNIX) Number of UD TPDUs received from this remote service provider. o ud pdus sent (Tru64 UNIX) Number of UD TPDUs sent to this remote service provider. o user octets received Total number of user data octets received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as data retransmitted by the remote NSAP. o user octets sent Total number of user data octets sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include data retransmitted by the local NSAP. o user pdus discarded Number of PDUs received from the remote NSAP that were discarded because of insufficient buffer space. o user pdus received Total number of TPDUs containing user data received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as TPDUs retransmitted by the remote NSAP. o user pdus sent Total number of TPDUs containing user data sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include retransmitted TPDUs. 5 Identifier o name Simple name assigned to the remote NSAP when it was automatically created. 5 Status o DTE address Address assigned to the DTE when it is created. o IP address Address assigned to the IP when it is created. o nsap address Address assigned to the local NSAP when it is created. o uid Entity's unique identifier, generated when the entity is created. 3 port show [node node-id] osi transport - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show osi transport port * remote nsap, client show osi transport port OSI$PORT_0_004E all 4 Counters o creation time Time the port was assigned to a transport connection. o duplicate pdus received Total number of all types of detected duplicate TPDUs received from the remote NSAP. This attribute applies only to COTS. o failed checksum Number of checksum failure events detected. o pdus received Total number of all types of TPDUs received from the remote NSAP (excluding detected duplicates). o pdus sent Total number of all types of TPDUs sent to the remote NSAP (excluding retransmissions). o retransmitted pdus Total number of all types of retransmitted TPDUs sent to the remote NSAP. For Tru64 UNIX, this attribute applies to CLTS only. o total octets received Total number of octets of all types of TPDUs received from the remote NSAP, regardless of their disposition. This count includes detected duplicates. o total octets sent Total number of octets of all types of TPDUs sent to the remote NSAP, including retransmissions. o user octets received Total number of user data octets received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as data retransmitted by the remote NSAP. o user octets sent Total number of user data octets sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include data retransmitted by the local NSAP. o user pdus received Total number of PDUs containing user data received from the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include duplicates such as TPDUs retransmitted by the remote NSAP. o user pdus sent Total number of TPDUs containing user data sent to the remote NSAP, including normal, expedited, connect, accept, and disconnect data. This count does not include retransmitted TPDUs. 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o acknowledgment delay time Default: None Value: 0-65 Maximum amount of time (in seconds) that an AK TPDU is to be withheld. This attribute applies to protocol class 4 only. o checksums Default: None Value: True or false Indicates whether checksums are in use on the transport connection. This attribute is supported only for class 4 protocol. o client Default: None Value: Local entity name Name designated by the port user when the port was opened. If DNA session control is being used, this is the name of the session control port being used. o clns inactive area address (OpenVMS) Default: none Value: Set of Area Address Specifies the inactive area address used by the transport template associated with this port. The maximum number of members this set can contain is one. o cons template Default: None Value: Simple name When operating over the CONS, the name of the X.25 Access module's template specified when establishing the underlying network connection. o cr timeout Default: None Value for Tru64 UNIX: 1-(2 raised to the power of 31 -1) Default: 30 Value for OpenVMS: 1-4294967295 Amount of time (in seconds) to wait for a response to a CR TPDU before assuming that the remote transport service provider will not respond. This attribute is valid for protocol classes 0 and 2 only. o direction Indicates whether the port is open to initiate an outgoing connection, to receive an incoming connection, or is listening for incoming connection requests. unknown Port direction is not known. incoming Transport connection initiated by remote transport service. outgoing Transport connection initiated by this transport service. listening Listening for incoming connection requests. o er timeout Default: None Value for Tru64 UNIX: 1-(2 raised to the power of 31 -1) Default: None Value for OpenVMS: 1-4294967295 Amount of time (in seconds) to wait for a response to an ER TPDU before disconnecting the network connection. This attribute is valid for protocol classes 0 and 2 only. o expedited data Default: None Value: True or false Indicates whether the expedited data option is in use for the transport connection. This attribute is supported only for class 2 and class 4 protocols. o extended format Default: None Value: True or false Indicates whether the use of extended formats should be negotiated for a transport connection which operates the class 2 or 4 protocol. o incoming network priority (OpenVMS) Default: None Value: 0-255 When operating over CLNS, indicates network priority encoded in NPDU header for all received packets. o inactivity time Default: None Value: 4-65532 Time (in seconds) being used for the inactivity timer. This value is the product of multiplying the keepalive time by the inactivity factor (architectural constant = 4). This attribute is valid for protocol class 4 only. o initial retransmit time Default: None Value for Tru64 UNIX: 1-(2 raised to the power of 31 -1) Default: None Value for OpenVMS: 1-4294967295 Time (in seconds) used for the retransmission timer when sending the first TPDU on the transport connection. The value of this attribute is derived from the template used when the port was initialized. This attribute applies to COTS only. o keepalive time Default: None Value: 1-16383 Time (in seconds) being used for the window timer. The value of this attribute is derived from the template used when the port was initialized. This attribute is valid for protocol class 4 only. o local DTE address Default: None Value: DTE address Local DTE address being used for the transport connection. This attribute applies if network service is CONS. o local nsap Default: None Value: NSAP address Local NSAP address being used for the transport connection. This attribute applies if network service is CLNS or CONS. o local RFC1006 IP address (OpenVMS) Default: None Value: IP address Local IP address being used for the transport connection. This attribute applies if network service is RFC1006. o local RFC1006 port number (OpenVMS) Default: None Value: TCP port number Local RFC1006 port number being used for the transport connection. This attribute applies if network service is RFC1006. o local reference Default: None Value: 1-65535 Unique reference number assigned to the transport connection by the local transport service provider. This attribute applies to COTS only. o local transport selector Default: None Value: Hex-string Local transport selector for this port. o maximum nsdu size Default: None Value for Tru64 UNIX: 128-4294967295 Default: None Value for OpenVMS: 2048 When operating over the CONS, the maximum NSDU size for transmitting and receiving buffers. Expressed as a number of octets. This attribute is valid for CONS only. o negotiable classes (Tru64 UNIX) Default: None Value: Bit-set Protocol classes which may be sent in response to an incoming connect request. This attribute is valid if direction = listening and applies to COTS only. o negotiated tpdu size Default: None Value: 128-4294967295 The TPDU size which was negotiated for this transport connection. This attribute applies to COTS only. o network port Default: None Value: Local entity name Name of the network service port being used. o network service Default: None Value: CLNS, CONS, or RFC1006 (OpenVMS) Type of network service over which the transport connection is operating. Attribute value derived from the template used when the port was initialized. CLNS Connectionless Network Service CONS Connection-Oriented Network Service RFC1006 ISO Transport Service on top of TCP o outgoing network priority (OpenVMS) Default: None Value: 0-255 When operating over CLNS, indicates network priority encoded in NPDU header for all transmitted packets. o protocol class Default: None Value: 0, 2, or 4 Protocol class operating on the transport connection. This attribute is not valid for CLTS. o remote DTE address Default: None Value: DTE address Remote DTE address being used for the transport connection. This attribute applies to COTS and if the network service is CONS. o remote identifier Default: None Value: Hex string Implementation identity and version of the remote NSAP. When present, this value is received in the identification of implementation parameter of the CR or CC TPDU. This attribute applies to COTS only. o remote nsap Default: None Value: NSAP address Remote NSAP address being used for the transport connection. This attribute applies to COTS and if network service is either CONS or CLNS. o remote reference Default: None Value: 0-65535 Reference number assigned to the transport connection by the remote transport service provider. The value will be 0 if the transport connection is operating the class 0 protocol. This attribute applies to COTS only. o remote RFC1006 port number (OpenVMS) Default: None Value: TCP port number Remote TCP port number used for the transport connection. This attribute applies to COTS and if the network service is RFC1006. o remote RFC1006 IP address (OpenVMS) Default: None Value: IP address Remote IP address used for the transport connection. This attribute applies to COTS and if the network service is RFC1006. o remote transport selector Default: None Value: Hex string Remote transport selector that identifies the remote transport service user. This attribute applies to COTS only. o request acknowledgment Default: None Value: True or false Indicates whether request acknowledgment was negotiated for this transport connection. This attribute is valid for class 4 protocol only. o retransmit threshold Default: None Value: 0-4294967295 Number of times a TPDU requiring acknowledgment is to be retransmitted without acknowledgment before the transmission completes with an error. This attribute is valid for class 4 protocol only. o round-trip delay estimate Default: None Value for Tru64 UNIX: 1-4294967295 Default: None Value for OpenVMS: 0-4294967295 Current estimate (in milliseconds) of the round-trip delay on the transport connection. This attribute is valid for protocol class 4 only. o send implementation id Default: None Value: True or false Indicates whether the implementation id will be sent in the CR. It is always returned in the CC if it is present in the CR. o send preferred maximum TPDU size Default: None Value: True or false Indicates whether the preferred maximum TPDU size parameter was sent in the CR or CC TPDU. o send request acknowledgment (OpenVMS) Default: None Value: True or false Indicates whether the request acknowledgment parameter was sent in the CR or CC TPDU. o type Default: None Value: CO or CL Indicates that the port is being used for the connection-oriented (CO) Transport protocol. CL Connectionless transport service. CO Connection-Oriented transport service. o uid Default: None Value: uid Entity's unique identifier, which is generated when the entity is created. o use clns error reports Default: None Value: True or false When operating over CLNS, indicates whether the network Routing layer's error reporting facility should be used when performing connection establishment. This attribute applies to COTS only. 3 template show [node node-id] osi transport - template template-id attribute [,attribute...] all [attributes] all characteristics all identifiers Examples: show osi transport template * name, network service show osi transport template osit$rfc1006plus all 4 Characteristics o acknowledgment delay time Default: 1 Value: 0-65 Maximum amount of time (in seconds) that an AK TPDU is to be withheld. This attribute is valid for protocol class 4 only. o checksums Default: False Value: True or false Specifies whether the use of checksums should be negotiated for a transport connection. This attribute is valid for protocol class 4 only. o classes Default: {4} Value: Bit-set Set of protocol classes that can be negotiated for use on a transport connection. If the value of the network service attribute is CLNS, the class must be a subset of the classes supported by the OSI transport attribute clns classes supported. If the value is CONS, the classes must be a subset of the classes supported by the OSI transport attribute cons classes supported. If the value of the network service attribute is ANY, the classes must be a subset of the combined classes in the clns classes supported and cons classes supported attributes. o clns inactive area address (OpenVMS) Default: Empty set Value: Set of area-address Specifies the inactive area address to be used by transport connections that use this template. This characteristic is relevant only for connections that use CLNS with Null Internet. The set must contain no more than one area address. o cons template Default: OSI Value: Simple-name Transport Name of the X.25 Access module template to be used when establishing a network connection over the CONS. Used only when the value of the network service attribute is cons. o cr timeout Default: 30 Value for Tru64 UNIX: 1-(2 raised to the power of 31 -1) Default: 30 Value for OpenVMS: 1-4294967295 During connection establishment, the amount of time (in seconds) to wait for a response to a CR TPDU before assuming that the remote transport service provider will not respond. This attribute is valid for protocol classes 0 and 2 only. o er timeout Default: 30 Value for Tru64 UNIX: 1-(2 raised to the power of 31 -1) Default: 30 Value for OpenVMS: 1-4294967295 The amount of time (in seconds) to wait for a response to an ER TPDU before disconnecting the network connection. This attribute is used for protocol classes 0 and 2 only. o expedited data Default: True Value: True or false Specifies whether use of the expedited data option should be negotiated for the transport connections. This attribute is not valid for protocol class 0. o extended format Default: None Value: True or false Specifies whether the use of extended TPDU format should be negotiated for the transport connections. Normal format gives 7-bit sequence numbers and 4-bit credit fields; extended format gives 31-bit sequence numbers and 16-bit credit fields. This attribute is supported only for class 2 and class 4 protocols. o inbound (OpenVMS) Default: True Value: True or false Indicates whether this template may be used as the template for an inbound transport connection. The algorithm of selection of the inbound template is different depending on the type of network service over which the transport connection is made. If an inbound template cannot be found for an inbound transport connection, then the template called DEFAULT will be selected as the default. For the CLNS network service, the inbound template selected is the first template found that has the Inbound attribute set to true , the Network Service attribute set to CLNS, and the CLNS Inactive Area Address attribute set to empty set. For the CLNS network service (using the inactive subset, that is, null internet), the incoming template selected is the first template found that has the Inbound attribute set to True, the Network Service attribute set to CLNS and the CLNS Inactive Area Address attribute matches the Inactive Area Address attribute of the Routing Circuit entity that the transport connection is using. For the CONS network service, the inbound template selected is the first template found that has the inbound attribute set to true , the network service attribute set to CONS and the CONS template attribute (that is, an X.25 Access template name) matches the name of the X.25 Access filter that was used to accept the inbound network connection. o initial retransmit time Default: 5 Value for Tru64 UNIX: 1-(2 raised to the power of 31 -1) Default: 5 Value for OpenVMS: 1-4294967295 Amount of time (in seconds) to wait for an acknowledgment before retransmitting the first TPDU over the transport connection. o keepalive time Default: 60 Value: 1-16383 Time (in seconds) to be used for the window timer. When the transport service provider has no TPDUs to send over a transport connection, it retransmits the last AK TPDU at the specified frequency to prevent expiration of the remote NSAP's inactivity timer. This attribute is valid for protocol class 4 only. o local nsap Default: System Value: NSAP address dependent, determined at run-time A local NSAP address to be used by default if one is not supplied across the service interface. o loopback (OpenVMS) Default: False Value: True or false Specifies whether transport connections using this template are looped back locally in the transport layer. o maximum nsdu size Default: 2048 Value for Tru64 UNIX: 128-4294967295 Default: 2048 Value for OpenVMS: 2048 When operating over the CONS, the maximum NSDU size to use for transmit and receive buffers. Expressed as a number of octets. o network priority (OpenVMS) Default: 0 Value: 0-255 When operating over CLNS, indicates network priority encoded in NPDU header for all transmitted packets. It may be used by intermediate systems to assign the packets to queues of appropriate priority. o network service Default: clns Value: Any, clns, cons, or RFC1006 (OpenVMS) Type of network service. On Tru64 UNIX, the default template network service cannot be set to any. The network service chosen must be compatible with the value of the protocol class attribute. any Either clns Connectionless Network Service cons Connection-Oriented Network Service RFC1006 ISO Transport Service on top of TCP o retransmit threshold Default: 8 Value: 0-4294967295 Number of times a TPDU requiring acknowledgment is to be retransmitted before it is assumed that network connectivity has failed. This attribute is valid for protocol class 4 only. o RFC1006 port number (OpenVMS) Default: 102 Value: TCP port number Specifies the TCP port number to use. Only applicable if the network service is RFC1006. o security Default: Null value Value: Octet string An octet string to be transmitted in the security parameter of a CR or CC TPDU. A null value causes the security parameter to be omitted from the TPDU. For security reasons, this attribute cannot be displayed. o send implementation id Default: None Value: True or false Indicates whether the implementation id should be sent in the CR if the proposed protocol class is 2 or 4. It is always returned in the CC if it is present in the CR. o send preferred maximum TPDU size Default: True Value: True or false Indicates whether the preferred maximum TPDU size parameter should be sent in the CR TPDU. If the preferred maximum TPDU size parameter was present in the CR TPDU, then it indicates whether the preferred maximum TPDU size parameter should be sent in the CC TPDU. NOTE The default value of this characteristic should not be changed unless the remote implementation does not conform to ISO 8073. o send request acknowledgment Default: True Value: True or false Indicates whether the request acknowledgment parameter should be sent in the CR TPDU. If the request acknowledgment parameter was present in the CR TPDU, then it indicates whether the request acknowledgment parameter should be sent in the CC TPDU. NOTE The default of this characteristic should not be changed unless the remote implementation does not conform to ISO 8073. o use clns error reports Default: False Value: True or false Indicates whether the network Routing layer's error report facility should be used when performing connection establishment. If set to true, this may result in faster detection of an unreachable node at the time of connection establishment. This characteristic should not be set to true on an end system that is either dual-railed or connected to a network that has a high probability of duplication. This is valid only if network service equals clns. 4 Identifier o name Simple name assigned to the template when it is created. The name default is reserved. 2 routing show [node node-id] routing attribute [,attribute...] all [attributes] all characteristics all counters all status Examples: show routing type, phaseiv address show routing all 3 Characteristics o area authentication type Support: L1,IP Default: None Value: None or simple Type of authentication to be used for level 1 LSPs, PSNPs, and CSNPs. o area receive passwords Support: L1,IP Default: No passwords Value: Set of hex-string Set of passwords that are valid in level 1 LSPs, PSNPs, and CSNPs when simple authentication is in use. You cannot use the show command to display the value of this attribute. o area send password Support: L1,IP Default: No password Value: Hex-string Password to be sent in level 1 LSPs, PSNPs, and CSNPs when simple authentication is in use. You cannot use the show command to display the value of this attribute. o autonomous system number Support: IP Default: 0 Value: 0-65535 Autonomous system number of the local system. This characteristic is supported only if the value of the routing protocols supported characteristic includes EGP. You can modify this characteristic only when the status attribute routing state is off. o dna address format Support: End Default: True Value: True or false If true, specifies that NSAP addresses are DNA structured, and that NSAP address autoconfiguring is possible. If false, this specifies that NSAP addresses for this node are constructed from the characteristic manual network entity titles and the selectors supplied by the transport protocol module (NSP and/or OSI transport). The DNA address format attribute controls only the interpretation of address structuring and no longer controls autoconfiguration. To control autoconfiguration, you need to use the manual network entity titles attribute by manually adding or removing NETs. o domain authentication type Support: L2,IP Default: None Value: None or simple Type of authentication to be used for level 2 LSPs, PSNPs, and CSNPs. o domain receive passwords Support: L2,IP Default: No passwords Value: Set of hex-string Set of passwords that are valid in level 2 LSPs, PSNPs, and CSNPs when simple authentication is in use. You cannot use the show command to display the value of this attribute. o domain send password Support: L2,IP Default: No password Value: Hex-string Password to be sent in level 2 LSPs, PSNPs, and CSNPs when simple authentication is in use. You cannot use the show command to display the value of this attribute. o generate checksums Support: All Default: False Value: True or false If true, specifies that checksums are generated for data, error report, and ES-IS PDUs initiated by this node. If false, these checksums are not generated. It is strongly recommended that, for performance reasons, you use the default value (indicating no checksum generation). o ip reassembly time Support: IP Default: 10 Value: 1-255 Maximum time, in seconds, for which IP fragments are held while awaiting reassembly. o lifetime Support: All Default: 63 Value: 2-255 Value to be placed in the "lifetime" field of originating data packets. This value should be greater than the maximum number of hops in any path in the network, plus the maximum packet lifetime in half-seconds. o manual area addresses Support: L1,L2 Default: No area Value: Set of area addresses addresses Area addresses to be used for this node. An area address cannot be a Phase IV address or the address DefaultArea. If the characteristic manual L1 algorithm has the value routing vector, this set must be empty, and the characteristic phase iv address must not be 0.0. If the characteristic phase iv address is 0.0, there must be at least one area address. o manual L1 algorithm Support: L1 Default: Routing Value: See description vector Type of routing algorithm to be used within the area. You can modify this characteristic only when the entity is disabled. link state The DECnet-Plus link-state algorithm is used. routing The Phase IV routing-vector algorithm is used. vector o manual L2 algorithm Support: L2 Default: Routing Value: See description vector Type of routing algorithm to be used at level 2. You can modify this characteristic only when the entity is disabled. link state The DECnet-Plus link-state algorithm is used. routing The Phase IV routing-vector algorithm is used. vector o manual network entity titles Support: End Default: No NETs Value: Set of NETs Network entity titles (NETs) to be used for this node. If the characteristic dna address format is set to false, there must be at least one NET. o maximum buffers Default: 100 Value: 0-65535 Specifies the guaranteed number of buffers for forwarding. More buffers may be used if they are available. You can only increase the characteristic value. o maximum path splits Support: L1,L2 Default: 2 Value: 1-32 Maximum number of equal cost paths to split traffic between. You can modify this characteristic only when the entity is disabled. o minimum lsp transmission interval Support: L1,L2 Specifies the minimum interval (in seconds) between transmissions of an LSP from a particular source. When changed the timer must be reset. o phaseiv address Support: All Default: 0.0 Value: PhaseIV address Specifies a Phase IV compatible address for communication with other Phase IV nodes. The default address, 0.0, indicates that no Phase IV compatible address is provided for the node. You can modify this characteristic only when the entity is disabled. o phaseiv area maximum cost Support: L2 Default: 1022 Value: 1-1022 Maximum cost of a path to a reachable Phase IV area. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv area maximum hops Support: L2 Default: 30 Value: 1-30 Maximum number of hops in a path to a reachable Phase IV area. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv broadcast routing timer Support: L1,L2 Default: 10 Value: 1-65535 Maximum interval, in seconds, between broadcast routing messages on broadcast circuits. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv buffer size Support: All Default: 576 Value: 1-65535 Size, in octets, of buffers used for routing to adjacent Phase IV nodes. This value is actually six octets greater than the maximum buffer size, and does not include the headers for the Routing and Data Link layers. o phaseiv maximum address Support: L1,L2 Default: 1023 Value: 1-1023 Maximum node number within the Phase IV area. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv maximum area Support: L2 Default: 63 Value: 1-63 Maximum Phase IV area number. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv maximum cost Support: L1,L2 Default: 1022 Value: 1-1022 Maximum cost of a path to a reachable node within the Phase IV area. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv maximum hops Support: L1,L2 Default: 30 Value: 1-30 Maximum number of hops in a path to a reachable node within the Phase IV area. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv maximum visits Support: All Default: 63 Value: 1-63 Maximum number of visits that a packet can make to this node before Routing assumes that the packet is looping. This characteristic is only used by the Phase IV routing algorithm (that is, the routing-vector algorithm). o phaseiv prefix Support: All Default: Hex 49 Value: Address prefix Prefix for Phase IV addresses. If the characteristic phase iv address is not 0.0, a DECnet-Plus area address is formed by adding the area portion of the Phase IV address to this prefix. You can modify this characteristic only when the entity is disabled. o probe rate Support: End Default: 20 Value for Tru64 UNIX: 10-1000 Default: 20 Value for OpenVMS: 1-65535 Number of packets after which a probe is sent. This characteristic is used only on multilink end systems, on circuits without cache entries for the destination. o protocols Support: IP Value: IP or ISO8473 The protocol stacks that are enabled on this system. These can be either or both of the above values. The value of this characteristic derives from an argument to the create command. You cannot modify this characteristic. o redirect holding time Support: L1,L2 Default: 600 Value: 1-65535 Holding time, in seconds, to be specified in Redirect PDUs generated by this node. o rip receive metric class Support: L2,IP Default: External Value: External or internal The class to be associated with routes received through RIP. This value may be overridden by a routing receive route entity. This characteristic is supported only if the routing protocols supported characteristic includes the RIP routing protocol. o rip send local metric Support: L2,IP Default: 1 Value: 0-16 The metric value used by RIP when announcing routes derived from local information. This value is used unless it is overridden by a routing send route entity. This characteristic is supported only if the routing protocols supported characteristic includes the RIP routing protocol. o rip send metric classes Support: L2,IP Default: Internal Value: Set of external, internal Routes received through routing protocols other than RIP with metric classes in this set are candidates for announcement in RIP messages (subject to the route propagation policy in force). Routes with metric classes not in this set will not be announced. Each value in this set may be overridden separately by a more specific propagation policy specified by a routing send route or routing send route route source entity. This characteristic is supported only if the routing protocols supported characteristic includes the RIP routing protocol. o rip send replacement metric Support: L2,IP Default: 1 Value: 0-16 The metric value used by RIP when announcing routes derived through other routing protocols. This value is used unless it is overridden by a routing send route entity. This characteristic is supported only if the routing protocols supported characteristic includes the RIP routing protocol. o routing mode Support: End Default: Integrated propogation Value: Segregated or Integrated Determines the behavior of the forwarding algorithm. When the routing mode is set to Segregated, data being transmitted to Phase IV destination addresses is sent in Phase IV format packets, to the adjacent Phase IV router, if available. In Integrated mode, data is sent to Phase V (OSI) router adjacencies in CLNP packets, if possible. This characteristic can only be set when Routing is disabled. For example, to switch to segregated mode from the default: NCL> disable routing NCL> set routing routing mode = segregated NCL> enable routing NCL> enable routing circuit * o route propagation Support: L2,IP Default: No route Value: Set of protocol pairs (see below) propagation The default route propagation to be performed. The set may include the following protocol pairs: EGP to IS-IS IS-IS to RIP EGP to RIP RIP to EGP IS-IS to EGP If a particular value is not present in the set, routes are not propagated between those two protocols in that direction. This characteristic is supported only if the routing protocols supported characteristic includes either of the EGP or RIP routing protocols. o routing mode Support: End Default: Integrated Value: Segregated or Integrated Determines the behavior of the forwarding algorithm. When the routing mode is set to Segregated, data being transmitted to Phase IV destination addresses is sent in Phase IV format packets, to the adjacent Phase IV router, if available. In Integrated mode, data is sent to Phase V (OSI) router adjacencies in CLNP packets, if possible. This characteristic can only be set when Routing is disabled. For example, to switch to segregated mode from the default: NCL> disable routing NCL> set routing routing mode = segregated NCL> enable routing NCL> enable routing circuit * o routing protocols supported Support: L2,IP The set of routing protocols supported by this implementation. You cannot modify this characteristic. EGP IS-IS RIP o segment buffer size Support: All Default: 570 Value: 0-65535 Maximum segment size, in octets, to be used by the Transport layer. A value of zero means that the segment size is unlimited. o send source quench Support: L1,L2,IP Default: False Value: True or false Specifies whether an ICMP source quench packet is sent when an IP packet is discarded because of congestion. If false, ICMP source quench packets are never sent. o source quench interval Support: L1,L2,IP Default: 100 Value: 1-65535 Minimum time, in milliseconds, between transmission of successive ICMP source quench packets. o summary addresses Support: L2,IP Default: No addresses Value: Set of summary addresses Summary address information to be included in level 2 link state packets sent by this node. o time to live Support: IP Default: 35 Value: 1-255 Specifies the value to be placed in the time to live field of originating IP packets. This value should be greater than the maximum number of hops in any path on the network. o type Support: All Default: No default Value: See description Routing type of this node. You cannot modify this characteristic. endnode The node is an end node. L1router The node is a level 1 router. L2router The node is a level 2 router. o version Default: Current version number Version number of the DNA Network Routing layer architecture specification to which this implementation conforms. You cannot modify this characteristic. 3 Counters o address unreachable pdus discarded Support: All Number of data PDUs that have been discarded because the destination was unreachable. o aged ip packets discarded Support: IP Number of IP packets that have been discarded because their time of life has expired. o aged pdus discarded Support: L1,L2 Number of data PDUs that have been discarded because their lifetime has expired. o attempts to exceed maximum sequence number Support: L1,L2 Number of times an attempt was made to increase the sequence number of a link state packet beyond the maximum allowed. o corrupted lsps detected Support: L1,L2 Number of times that the corrupted lsp detected event has been generated. o creation time Support: All Time this entity was created. o error reports generated Support: All Number of error report PDUs (or Phase IV data packets with RTS set) that have been generated. o icmp address mask reply messages received Support: IP Number of ICMP Address Mask Reply messages received. o icmp address mask reply messages sent Support: IP Number of ICMP Address Mask Reply messages sent. o icmp address mask request messages received Support: IP Number of ICMP Address Mask Request messages received. o icmp address mask request messages sent Support: IP Number of ICMP Address Mask Request messages sent. o icmp destination unreachable messages received Support: IP Number of ICMP Destination Unreachable messages received. o icmp destination unreachable messages sent Support: IP Number of ICMP Destination Unreachable messages sent. o icmp echo reply messages received Support: IP Number of ICMP Echo Reply messages received. o icmp echo reply messages sent Support: IP Number of ICMP Echo Reply messages sent. o icmp echo request messages received Support: IP Number of ICMP Echo Request messages received. o icmp echo request messages sent Support: IP Number of ICMP Echo Request messages sent. o icmp message send errors Support: IP Number of ICMP messages that could not be sent because of problems in the ICMP layer. Note that this value does not include errors that occur outside the ICMP layer, such as forwarding errors. o icmp messages received Support: IP Number of ICMP messages received. This value includes those messages counted by the icmp received message errors counter. o icmp messages sent Support: IP Number of ICMP messages of all types that the node has attempted to send. Note that this figure includes the value of the icmp message send errors counter. o icmp received message errors Support: IP Number of ICMP messages received with any type of error. o icmp parameter problem messages received Support: IP Number of ICMP Parameter Problem messages received. o icmp parameter problem messages sent Support: IP Number of ICMP Parameter Problem messages sent. o icmp redirect messages received Support: IP Number of ICMP Redirect messages received. o icmp redirect messages sent Support: IP Number of ICMP Redirect messages sent. o icmp source quench messages received Support: IP Number of ICMP Source Quench messages received. o icmp source quench messages sent Support: IP Number of ICMP Source Quench messages sent. o icmp time exceeded messages received Support: IP Number of ICMP Time Exceeded messages received. o icmp time exceeded messages sent Support: IP Number of ICMP Time Exceeded messages sent. o icmp timestamp reply messages received Support: IP Number of ICMP Timestamp Reply messages received. o icmp timestamp reply messages sent Support: IP Number of ICMP Timestamp Reply messages sent. o icmp timestamp request messages received Support: IP Number of ICMP Timestamp Request messages received. o icmp timestamp request messages sent Support: IP Number of ICMP Timestamp Request messages sent. o icmp unknown message types received Support: IP Number of ICMP messages received with an unknown message type. o ip address unreachable packets discarded Support: IP Number of IP packets discarded because their destination was unreachable. o ip destination address error packets discarded Support: IP Number of IP packets discarded because of an invalid destination address or the address of an unsupported class. o ip packets discarded Support: IP Number of IP packets discarded for either of the following reasons: o Error in the IP header, such as bad checksum or version number mismatch. Note, however, that format errors and time to live expired are excluded. o Packet received through data link broadcast when forwarding is not allowed. o ip packet format errors Support: IP Number of IP packets discarded because of a format error in the IP header. o ip protocol unreachable packets discarded Support: IP Number of IP packets received for the local system and discarded because there was no port with the protocol type specified in the IP datagram PROTO field. o ip source address error packets discarded Support: IP Number of IP packets discarded because of an invalid source address or the address of an unsupported class. o lsp L1 database overloads Support: L1,L2 Number of times that the lsp level 1 database overload event has been generated. o lsp L2 database overloads Support: L2 Number of times that the lsp level 2 database overload event has been generated. o manual addresses dropped from area Support: L1,L2 Number of times an address in the manual area addresses set is ignored when computing an area address (each address that is ignored is counted separately). o own lsp purges Support: L1,L2 Number of times that the own lsp purged event has been generated. o pdu format errors Support: All Number of data PDUs that have been discarded because of format errors. o phaseiv translation failures Support: All Number of times the phase iv translation failures event has been generated. o sequence number skips Support: L1,L2 Number of times that the sequence number skipped event has been generated. o unsupported options Support: All Number of data PDUs that have been discarded because they specified unsupported options in their header. 3 Preset_attributes Preset attributes are similar to characteristics, in that their values control the way in which the routing module operates. However, unlike characteristics, you cannot alter preset attribute values using the set command. NOTE These characteristics are preset attributes. They should only be set by an expert. o broadcast lsp transmission interval Support: L1,L2 Default: 33 Value: 1-65535 Interval, in milliseconds, between the transmission of Link State Packets (LSPs) on a broadcast circuit. o complete snp interval Support: L1,L2 Default: 10 Value: 1-600 Interval, in seconds, between generation of Complete Sequence Number Packets (SNPs) by a designated router on a broadcast circuit. o default es hello timer Support: All Default: 600 Value: 1-65535 Value to be used for the current suggested Hello timer, in the absence of any suggested value from the intermediate system (IS). On routers, this is the value to be suggested when the router is not required to poll the ES configuration. In routers, this value is suggested by the Suggested ES Configuration Timer option in IS Hellos. o dr isis hello timer Support: L1,L2 Default: 1 Value: 1-65535 Interval, in seconds, between the generation of IS-IS Hello PDUs by the designated router. o es cache holding time Support: End Default: 600 Value: 1-65535 Holding time, in seconds, for an entry in the node's end-node cache database. o es cache width Support: End Default: 3 Value for Tru64 UNIX: 1-4294967295 Default: 3 Value for OpenVMS: 1-65535 Maximum number of LAN address entries in the node's end-node cache database on a broadcast circuit. o holding multiplier Support: All Default: 3 Value: 2-63 Value by which to multiply the Hello timer to obtain the holding timer value for ES and IS Hellos and for point-to-point, router- to-router Hellos. o inactive selector Support: All Default: 33 Value: 2-255 This is the selector value identifying the port to which incoming Inactive Subset PDUs are to be sent. o initialization timer Support: All Default: 6 Value: 1-63 Delay, in seconds, between initialization of a data link and sending a DECnet-Plus message on a DDCMP circuit. o isis format Support: L1,L2 Default: 0 (ISO) Value: (ISO) or 1 (DNA Private) This attribute controls the protocol identification to be used for "DNA Private" PDUs. On broadcast circuits, this characteristic also controls the SAP on which they are transmitted. o isis holding multiplier Support: L1,L2 Default: 10 Value: 2-63 Value by which to multiply the ISIS Hello timer to obtain the value of the holding timer for LAN level 1 and level 2 router-to- router Hellos. o maximum age Support: L1,L2 Default: 1200 Value: 1-65535 Number of seconds before an LSP is considered to be expired. o maximum lsp generation interval Support: L1,L2 Default: 900 Value: 60-900 Maximum interval, in seconds, between link state packets (LSPs) generated by this node. o minimum lsp generation interval Support: L1,L2 Default: 30 Value: 1-65535 Minimum time, in seconds, between generation of LSPs by this node. o minimum lsp transmission interval Support: L1,L2 Default: 5 Value: 5-30 Minimum interval, in seconds, between retransmissions of an LSP. o multicircuit es hello timer Support: End Default: 10 Value: 1-65535 Value to be used for the current suggested Hello timer on a multicircuit end node with more than one circuit enabled, in the absence of any suggested values from the IS. o originating L1 lsp buffer size Support: L1,L2 Default: 1492 Value: 128-1492 Maximum size of level 1 LSPs and SNPs originated at this node. o originating L2 lsp buffer size Support: L2 Default: 1492 Value: 128-1492 Maximum size of level 2 LSPs and SNPs originated at this node. o partial snp interval Support: L1,L2 Default: 2 Value: 1-65535 Minimum interval, in seconds, between sending partial SNPs. o poll es hello rate Support: All Default: 50 Value: 1-65535 Interval, in seconds, between ES Hellos when a router requires to poll the ES configuration. o queue threshold Support: L1,L2 Default: 1 Value: 1-63 Average queue length at a router, above which the "congestion experienced" bit will be set in a forwarded data PDU. o waiting time Support: L1,L2 Default: 60 Value: 1-65535 Delay, in seconds, between routing databases being in the waiting state and entering the on state. o zero age lifetime Support: L1,L2 Default: 60 Value: 1-65535 Time, in seconds, for which the purge header of an expired LSP is retained. 3 Status o area addresses Support: All A set of area addresses. If the node is an end node, these are the area address portions of the NETs of all adjacent routers. If the node is a level 1 or level 2 router, this set is the union of the sets of manual area addresses reported in all level 1 LSPs received by this router. o egp port Support: IP Name of the routing port entity used for sending and receiving EGP messages. This attribute is set when a routing egp group entity is enabled. o icmp port Support: IP Name of the routing port entity used for sending and receiving ICMP messages. This attribute is set when the routing module is enabled and the protocols characteristic includes the value IP. o L1 state Support: L1,L2 State of the level 1 database. off Routing is disabled. on Routing is enabled and operating correctly. waiting Routing has received routing information that it cannot store and is waiting for the overload to be removed. o L2 state Support: L2 State of the level 2 database. off Routing is disabled. on Routing is enabled and operating correctly. waiting Routing has received routing information that it cannot store and is waiting for the overload to be removed. o nearest L2 router adjacencies Support: L1,L2 Names of adjacencies to be used for forwarding to the nearest level 2 router. If the node is a level 2 router adjacent to other areas, or if it is a level 1 router in an area with no attached level 2 routers, this set is empty. o rip port Support: IP Name of the udp port entity used by the routing module for sending and receiving RIP messages. This attribute is set when a routing circuit entity is enabled with its rip state characteristic set to any value other than off. o state Support: All State of the routing entity. off The entity is disabled. on The entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 circuit show [node node-id] routing - circuit circuit-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show routing circuit * name, state show routing circuit csmacd-1 all 4 Identifier o name Simple name assigned to the circuit when it is created. 4 Characteristics o alternative subnet addresses Support: L1,L2,IP Default: No addresses Value: Set of subnet-address A set of alternative IP addresses and subnet masks for this interface. You can modify this characteristic only when the entity is disabled. o arp holding time Support: IP Default: 600 Value: 30-65535 Number of seconds to hold on to a routing circuit ip address translation entity. This characteristic is supported only if the circuit's type characteristic is csma-cd. o arp response waiting time Support: IP Default: 3 Value: 1-10 Number of seconds to wait for an ARP response when an ARP request has been sent. This characteristic is supported only if the circuit's type characteristic is csma-cd. o authentication type Support: L1,L2,IP Default: None Value: None or simple Type of authentication to be used for LAN L1 Hellos, LAN L2 Hellos, or PtPt Hellos on this circuit. o data link entity Support: All Default: No data link Value: Local-entity-name name Name of the entity within the data link module to be created when a port is opened for that data link type. You can modify this characteristic only when the entity is disabled. This attribute is supported for all types of circuits, however for X.25 circuits set the attribute to x25 access. o directed broadcast Support: L1,IP Default: On Value: Off or On Specifies how an IP packet is to be forwarded on a broadcast link. off Discard the packet silently. on Broadcast the packet using data level link broa that either of the following conditions is true: o The packet's subnet address matches the value of the subnet address characteristic. o The packet's subnet address matches one of the values of the alternative subnet addresses characteristic. This characteristic is supported only if the characteristic type is set to csma-cd. o dna neighbor Support: L1,L2 Default: True Value: True or false If true, specifies that the neighbor is expected to be DNA compliant, and so proprietary mechanisms are possible. If false, no router-to-router Hellos or LSPs will be sent over this circuit. This characteristic is supported only if the characteristic type is not x25 da. You can modify this characteristic only when the entity is disabled. o enable phaseiv address Support: All Default: True Value: True or false Specifies whether the physical LAN address is to be set to the Phase IV style LAN address (that is, AA-00-04-00-xx-xx). The LAN address is set only if this attribute is true and the value of the Phase IV Address characteristic is not 0.0. If Phase IV Address is not 0.0 and there are multiple adaptors to the same LAN, only one circuit may have this attribute set to true. This characteristic is supported only if the characteristic type is set to csma-cd. o explicit receive verification Support: All Default: True Value: True or false Type of password verification performed at circuit initialization. If true, the received verifier is checked against the value of the characteristic receive verifier for this circuit, if any. If false, the received verifier is checked against the set of verifiers specified in the routing permitted neighbor entities. This attribute is supported only if the characteristic type is set to ddcmp, hdlc, x25 static incoming, x25 static outgoing, and x25 permanent. o hello timer Support: L1,L2 Default: 10 Value: 1-32767 Interval, in seconds, between IS Hello messages. o idle timer Support: All Default: 30 Value: 1-65535 Number of seconds of idle time before a call is cleared. This attribute is supported only if the characteristic type is x25 da. o inactive area address Support: All Default: No area Value: Set of area addresses address Area address associated with the use of the inactive subnet of ISO 8473. Maximum area address that may be present is 1. This characterisitic is supported only if the characteristic type is set to csma-cd. o initial minimum timer Support: All Default: 55 Value: 1-65535 Period, in seconds, for which an X.25 call remains connected after being established, irrespective of traffic. This should be set small enough that the call is cleared before the start of the next charging interval. This attribute is supported only if the characteristic type is x25 da. o isis hello timer Support: L1,L2 Default: 3 Value: 1-32767 Interval, in seconds, between LAN level 1 and level 2 router-to- router Hello messages. This value is also used as the interval between IS Hello messages when polling the ES configuration. o L1 cost Support: L1,L2 Default: 20 Value: 1-63 Cost of this circuit for level 1 traffic. o L1 router priority Support: L1,L2 Default: 64 Value: 1-127 Priority for becoming LAN level 1 designated router. This attribute is supported only if the circuit's characteristic type is csma-cd. o L2 cost Support: L2 Default: 20 Value: 1-63 Cost of this circuit for level 2 traffic. o L2 router priority Support: L2 Default: 64 Value: 1-127 Priority for becoming LAN level 2 designated router. This attribute is supported only if the circuit's characteristic type is csma-cd. o manual data link sdu size Support: All Default: 1492 Value: 128-65535 Preferred maximum data-link block size, in octets. You can modify this characteristic only when the entity is disabled. If the characteristic type is csma-cd, this characteristic is a read- only attribute whose value is fixed at 1492. o manual data link sdu size for ip Support: IP Default: See Value: 128-65535 description Preferred maximum DSDU size, in octets, for the transmission of IP packets. The DSDU size includes the size of the packet containing the IP header. On point-to-point HDLC links, the DSDU size also includes the 1-octet link encapsulation (that is, the maximum IP packet size is the value of this attribute minus 1). The default value depends on the circuit type, as follows: csma-cd 1500 ddcmp 1500 hdlc 1500 X.25 (all 576 types) You can modify this characteristic only when the entity is disabled. o manual L2only mode Support: L2 Default: False Value: True or false If true, specifies that this circuit is to be used only for level 2 traffic. If false, the circuit may be used for both level 1 and level 2 traffic. You can modify this characteristic only when the entity is disabled. o manual routers Support: End Default: No router Value: Set of LAN addresses IDs Manually entered IDs of routers. If this set is empty, the circuit will auto-configure the routers. This characteristic is supported only if the circuit's characteristic type is csma-cd. For Tru64 UNIX, a maximum of 5 routers can be in the set. o maximum arp retries Support: IP Default: 3 Value: 1-10 Maximum number of times that an ARP request can be sent for the same IP address. This characteristic is supported only if the circuit's characteristic type is set to csma-cd. o maximum call attempts Support: All Default: 10 Value: 0-255 Maximum number of successive X.25 call failures before the circuit is regarded as being halted. A value of zero means that there is no limit to the number of retries. This attribute is supported only if the characteristic type is set to x25 static outgoing. You can modify this characteristic only when the entity is disabled. Also, you can only increase the characteristic value. o maximum svc adjacencies Support: All Default: 1 Value: 1-65535 Number of routing circuit adjacency entities to reserve for SVCs on this circuit. This is effectively the maximum number of simultaneous calls possible on this circuit. This attribute is supported only if the characteristic type is x25 da. o originating queue limit Support: L1,L2 Default: 2 Value: 1-50 Maximum number of data PDUs originated by this node that can be on this circuit's transmit queue. This should be set to the minimum number required to keep the data link from idling. You can modify this characteristic to a higher value when the entity is disabled; you can never modify it to a lower value. o recall timer Support: All Default: 60 Value: 0-65535 Interval, in seconds, that must elapse between a call failure and a recall. This attribute is supported only if the characteristic type is set to x25 static outgoing, x25 da, hdlc, or ddcmp. o receive passwords Support: L1,L2,IP Default: No passwords Value: Set of hex-string Set of passwords that are valid in received LAN L1 Hellos, LAN L2 Hellos, and PtPt Hellos when simple authentication is in use on this circuit. You cannot use the show command to display the value of this attribute. o receive verifier Support: All Default: No verifier Value: Hex string, length 0-38 Value against which a neighbor node's received verifier is to be checked. If no verifier is specified, no verification is performed. This attribute is supported only if the characteristic type is either ddcmp, hdlc, x25 static incoming, x25 static outgoing, or x25 permanent. You cannot display this characteristic. o reserved adjacency Support: End Default: False Value: True or false If true, specifies that one SVC must be reserved for connection to a router. If false, no SVC needs to be reserved for this purpose. This characteristic is supported only if the circuit's characteristic type is x25 da). You can modify this characteristic only when the entity is disabled. o reserve timer Support: All Default: 600 Value: 1-65535 Interval, in seconds, during which the SVC remains reserved for the previous DTE address after a call is cleared due to lack of traffic. This attribute is supported only if the characteristic type is x25 da. o rip generated default route Support: L1,L2,IP Default: False Value: True or false If true, this specifies that the default route is announced in RIP messages sent on this circuit, with the metric value specified in the RIP generated default route metric characteristic. If false, the default route is not generated. o rip generated default route metric Support: L1,L2,IP Default: 1 Value: 0-16 Specifies the metric to be used when announcing a generated default route through RIP on this circuit. o rip neighbors Support: L2,IP Default: No addresses Value: Set of IP-addresses IP addresses of neighboring systems with which RIP will be exchanged on this circuit. If the circuit is a point-to-point circuit, this set must contain a single IP address if the rip state characteristic is to be set to send and receive. Also, you must disable the entity before altering this characteristic. If the rip send type characteristic is set to broadcast, only RIP messages from addresses specified in this set will be received; other messages will be silently discarded. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o rip poisoned reverse Support: L2,IP Default: True Value: True or false Specifies whether poisoned reverse routes are to be sent in RIP messages on this circuit. If false, poisoned reverse routes are not sent. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o rip receive default route Support: L2,IP Default: True Value: True or false Specifies whether the default route is accepted from RIP messages on this circuit. If false, the default route from RIP messages on this circuit is discarded. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o rip send type Support: L2,IP Default: Broadcast Value: Broadcast or point-to-point Specifies how RIP messages are sent on this circuit. broadcast RIP messages are sent via data link broadcast. point-to- RIP messages are sent directly to each IP address point specified in the rip neighbors characteristic. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol and if the circuit's type characteristic is csma-cd. o rip state Support: L2,IP Default: Off Value: See description Specifies how RIP messages are treated on this circuit. off RIP messages cannot be sent or received on this circuit. receive RIP messages can be received but not sent on this circuit. send and RIP messages can be sent and received on this receive circuit. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o send password Support: L1,L2,IP Default: No password Value: Hex-string Password to be sent in LAN L1 Hellos, LAN L2 Hellos, and PtPt Hellos when simple authentication is used on this circuit. You cannot use the show command to display the value of this attribute. o subnet address Support: IP Default: 0.0.0.0 Value: Subnet address IP address and subnet mask of this interface. You can modify this characteristic only when the entity is disabled. o template Support: All Default: No template Value: Template-id name Name of the template to be used when a port is opened for this data-link type. If no template name is specified, no template is used. You can modify this characteristic only when the entity is disabled. o transmit verifier Support: All Default: No verifier Value: Hex-string, length 0-38 Value to be transmitted for verifying the identity of this node. If no verifier is specified, no verifier is transmitted. This characteristic is supported only if the characteristic type is either ddcmp, hdlc, x25 static outgoing, x25 static incoming, or x25 permanent. You cannot display this characteristic. o type Support: All Type of circuit. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. csma-cd The circuit is a broadcast circuit. ddcmp The circuit is a DDCMP circuit. hdlc The circuit is an HDLC circuit. x25 da The circuit is a dynamically allocated X.25 circuit. x25 X.25 permanent virtual circuit. permanent x25 static Static incoming X.25 circuit. incoming x25 static Static outgoing X.25 circuit. outgoing o X.25 filters Default: See Value: Set of simple names description Specifies the set of X.25 filters to be used when a port is opened to the X.25 module. Typically, there will be two sets: one to specify the selection on the Call User Data field for DECnet-Plus and the other to specify the selection on the subaddress for Phase IV. This attribute is valid only if the characteristic type is x25 static incoming or x25 da. 4 Counters o authentication failures Support: L1,L2,IP Number of times a PDU has been received on this circuit with an Authentication Information field that is incompatible with the PDU type. o calls failed Support: All Number of unsuccessful call attempts on this circuit. This attribute is supported only if the characteristic type is x25 da. o calls placed Support: All Number of call attempts (successful and unsuccessful) on this circuit. This attribute is supported only if the characteristic type is x25 da. o changes in adjacency state Support: All Number of times the status attribute state of an adjacency belonging to this circuit changes from Up to Down (or Initializing), or the reverse. o changes in ip adjacency state Support: IP Number of times the status attribute state of an IP adjacency belonging to this circuit changes from Up to some other state, or the reverse. o changes in rip neighbor state Support: L2,IP Specifies the number of times the RIP state of IP adjacencies belonging to this circuit have changed. This attribute is supported only if the routing entity's characteristic routing protocols supported includes the routing protocol RIP. o circuit changes Support: All Number of times that the status attribute state has changed from on to off, or vice versa. o congestion discards Support: L1,L2 Number of data-and error-report NPDUs that have been discarded, before or after fragmentation, because of congestion. Any other discarding will already have been done by the forwarding process. This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data- and error-report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o control pdus received Support: All Number of control PDUs that have been received on this circuit. This number includes all Network layer PDUs, with the exception of DECnet-Plus data and error report PDUs and Phase IV data PDUs. o control pdus sent Support: All Number of control PDUs that have been sent on this circuit. o corrupted lsps received Support: L1,L2 Number of times a corrupted link state packet has been received on this circuit. o corrupted hello pdus received Support: All Number of times an ES-IS (end system to intermediate system) or IS-IS (intermediate system to intermediate system) Hello PDU has been received on this circuit that either cannot be parsed or contains an incorrect checksum. o creation time Support: All Time this entity was created. o da adjacency changes Support: All Number of DA adjacency change events that have been generated. o data pdus forwarded Support: L1,L2 Number of data- and error-report NPDUs that have been forwarded onto this circuit (either from another circuit or from a local port). This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data- and error-report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o data pdus fragmented Support: All Number of data NPDUs that have been fragmented on this circuit. o data pdus received Support: All Number of data- and error-report NPDUs that have been received on this circuit. This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data and error report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o data pdus transmitted Support: All Number of data- and error-report NPDUs, after fragmentation, that have been delivered to the port for transmission on this circuit. This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data- and error-report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o exceeded maximum svc adjacencies Support: End,L2 Number of exceeded maximum svc adjacency events that have been generated. This counter is supported only if the circuit's type is set to x25 da; only for nodes that are end nodes; and if the system supports dual routing (both DECnet and IP routing). o id reachablity changes Support: All Number of ID reachability change events that have been generated. o initialization failures Support: All Number of times that an attempt to initialize an adjacent node over this circuit has failed, either because of version skew or area mismatch. o ip fragmentation failure discards Support: IP Number of IP packets discarded because fragmentation was required to transmit them, but the IP header requested "do not fragment." This attribute is supported only if the system supports dual routing (both DECnet and IP routing). o ip fragments created Support: IP Number of IP fragments created for transmission on this circuit. o ip packets forwarded Support: IP Number of IP packets forwarded on this circuit before fragmentation. These IP packets may be from another circuit or from a local port. Note that this value includes those IP packets counted in the ip send discards counter. o ip packets fragmented Support: IP Number of IP packets that have been fragmented on this circuit. o ip packets received Support: IP Number of IP packets received on this circuit. This value includes all types of IP packet (control, data, etc.), and those that may subsequently be discarded for any reason. o ip received discards Support: IP Number of IP packets that have been received and then discarded because of congestion. o ip send discards Support: IP Number of IP packets for transmission that have been discarded because of congestion. o irrecoverable svc failures Support: All Number of times that the number of re-call attempts on this circuit has become equal to the value of the characteristic maximum call attempts. This attribute is supported only if the characteristic type is set to x25 static outgoing. o LAN l1 designated router changes Support: L1,L2 Number of times the local node has either elected itself or resigned as the LAN level 1 designated router on this circuit. This attribute is supported only if the circuit's characteristic type is set to csma-cd. o LAN l2 designated router changes Support: L2 Number of times the local node has either elected itself or resigned as the LAN level 2 designated router on this circuit. o LAN phaseiv designated router changes Support: L1,L2 Number of times the local node has either elected itself or resigned as the LAN Phase IV designated router on this circuit. o redirect discards Support: End Number of Redirect PDUs that have been discarded because of insufficient cache memory. o rejected adjacencies Support: All Number of times an attempt to create a new adjacency using this circuit has failed because of insufficient resources. o rejected ip adjacencies Support: L2,IP Number of times an attempt to automatically create a new IP adjacency to an IP router has failed because of lack of resources. o rip errors received Support: L2,IP Number of RIP messages received with any kind of received error on this circuit. This attribute is supported only if the routing entity's characteristic routing protocols supported includes the routing protocol RIP. o segmentation failure discards Support: L1,L2 Number of data NPDUs that have been discarded because segmentation was required to send them on this circuit but was not permitted in the NPDU header. o verification reject events Number of verification reject events that have been generated. This attribute is supported only if the characteristic type is set to ddcmp, hdlc, x25 static incoming, x25 static outgoing, or x25 permanent. 4 Status o data link port Support: All Name of the data link port used for this circuit. Not supported on DA circuits. o data link sdu size Support: All Maximum size, in octets, of a Data Link SDU for this circuit. This includes the Network layer header, but excludes the Data Link layer header. The value of this status is the lesser of the value of the characteristic manual data link sdu size and any limit imposed by the Data Link layer. o LAN L1 id Support: L1,L2 LAN ID allocated by the LAN level 1 designated router. This attribute is supported only if the circuit's characteristic type is csma-cd. o LAN L2 id Support: L2 LAN ID allocated by the LAN level 2 designated router. This attribute is supported only if the circuit's characteristic type is csma-cd. o L1 designated router Support: L1,L2 ID of the DECnet-Plus level 1 designated router on this circuit. This attribute is supported only if the circuit's characteristic type is csma-cd. If this node does not participate in the router election process, the value returned is 00-00-00-00-00-00. o L2 designated router Support: L2 ID of the DECnet-Plus level 2 designated router on this circuit. This attribute is supported only if the circuit's characteristic type is csma-cd. If this node does not participate in the router election process, the value returned is 00-00-00-00-00-00. o phaseiv designated router Support: L1,L2 ID of the Phase IV designated router on this circuit. This attribute is supported only if the circuit's characteristic type is csma-cd. If this node does not participate in the router election process, the value returned is 00-00-00-00-00-00. o point-to-point id Support: L1,L2 ID allocated to the circuit during its initialization. This attribute is supported only if the circuit's characteristic type is hdlc, ddcmp, or x25 static. o state State of the routing circuit entity. Support: All off The circuit is disabled. on The circuit is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 4 adjacency show [node node-id] routing - circuit circuit-name - adjacency adjacency-name attribute [,attribute...] all [attributes] all identifiers all status Examples: show routing circuit csmacd-1 adjacency * name, state, lan address show routing circuit csmacd-1 adjacency RTG$0001 all 5 Identifier o name Simple name assigned to the adjacency when it is created. 5 Status o data link port Support: All Name of the data link port used for this X.25 data adjacency. This attribute is supported only if the owning routing circuit entity's characteristic type is set to x25 da. o dte address Support: All DTE address of the neighboring node on an X.25 circuit. This status is supported only if the owning circuit entity's characteristic type is x25 da. o endnode ids Support: All System IDs of neighboring end nodes. This attribute is supported only if the node is an end node and the owning circuit entity's characteristic type is not x25 da. o endnode nets Support: All NETs computed from the system IDs in the endnode ids status and the set of area addresses in the owning routing entity's manual area addresses set. This attribute is supported only if the node is an end node and the owning circuit entity's characteristic type is not x25 da. o holding timer Support: L1,L2 Holding time for this adjacency, updated from the router-to- router Hello messages. This attribute is supported only if both the node and the adjacency are routers. o ip addresses Support: IP IP addresses of the neighbor node. If these are not known, the set is empty. o LAN address Data link address of the neighboring node on a broadcast circuit. This status is supported only if the owning circuit entity's characteristic type is csma-cd. o LAN priority Support: L1,L2 Priority of the neighbor of this adjacency for becoming the LAN level 1 designated router (if the adjacency is a DECnet-Plus level 1 router) or the LAN level 2 designated router (if the adjacency is a DECnet-Plus level 2 router). This status is supported only if the owning circuit entity's characteristic type is csma-cd; and the adjacency is a router rather than an end node. o level Support: L1,L2 The level of the adjacency. This attribute is supported only if both the node and the adjacency are routers. Level 1 The adjacency is used for level 1 routing. Level 2 The adjacency is used for level 2 routing. Level 1 & 2 The adjacency is used for level 1 and level 2 routing. Level 0 The usage is undefined. o neighbor areas Support: L1,L2 Area addresses of the neighboring node. This attribute is supported only if both the node and the adjacency are routers and the owning circuit entity's characteristic type is not x25 da. o neighbor node id Support: L1,L2 Node ID of the neighboring node. o neighbor node type Support: All Type of the neighboring node. This status is supported only if the owning circuit entity's characteristic type is not x25 da. non-dna The node is not a DNA router. router phase iv The node is a Phase IV end node. endnode phase iv The node is a Phase IV level 1 router. level 1 router phase iv The node is a Phase IV level 2 router. level 2 router DECnet-Plus The node is a DECnet-Plus end node. endnode DECnet-Plus The node is a DECnet-Plus level 1 router. level 1 router DECnet-Plus The node is a DECnet-Plus level 2 router. level 2 router DECnet-Plus The node is a DECnet-Plus router. router unknown The node type is unknown. phase iv The node is a Phase IV router. router o neighbor protocols supported Support: IP Network protocols supported by the neighboring node (either IP or ISO8473). o router nets Support: End Network Entity Title(s) (NETs) of a neighboring router. This status is supported only if the adjacency is a level 1 or level 2 router, and the owning circuit entity's characteristic type is not x25 da. o state Support: All State of the routing circuit adjacency entity. May be one of the following: failed initializing up up/dormant o type Type of adjacency. autoconfigured Created by autoconfiguration. manual Created manually by a create command. This attribute indicates whether the adjacency has been manually created, or whether the adjacency was created by means of hello PDUs. It will always have the value manual when it has been created by the create command; otherwise, it will have the value autoconfigured. 4 ip_address_translation show [node node-id] routing - circuit circuit-name - ip address translation ip-address attribute [,attribute...] all [attributes] all identifiers all status 5 Identifier o ip address IP address of the neighbor. 5 Status o LAN address Support: IP LAN address that corresponds to the IP address of this neighbor. 4 ip_reachable_address show [node node-id] routing - circuit circuit-name - ip reachable address ip-address attribute [,attribute...] all [attributes] all characteristics all identifiers all status 5 Characteristics o destination Support: L2,IP The IP address and subnet mask to which this reachable address refers. This value is derived from the destination argument of the create command. You cannot modify this characteristic. o dte addresses Support: L2,IP Default: No DTE Value: Set of DTE addresses addresses A set of DTE addresses to which a call may be directed in order to reach an address that matches the subnet address given by the subnet address characteristic. You can modify this characteristic only when the entity is disabled. This characteristic is supported only if the owning circuit is an X.25 circuit. o metric Support: L2,IP Default: 20 Value: 1-maximum link cost Default metric value for reaching the specified subnet over this circuit. You can modify this characteristic only when the entity is disabled. o metric class Support: L2,IP Default: External Value: External or internal Class of the default metric, which controls the preference for this route in the decision process. external The I/E bit for the default metric in the External Reachability Information option of level 2 link state packets is set to 1. The subnet address specified by this IP reachable address will have the same preference as level 2 external routes. internal The I/E bit for the default metric in the External Reachability Information option of level 2 link state packets is set to 0. The subnet address specified by this IP reachable address will have the same preference as level 2 internal routes. You can modify this characteristic only when the entity is disabled. o next hop Support: L2,IP Default: 0.0.0.0 Value: IP-address IP address of the neighboring node through which the destination is reachable. When you create this entity, this characteristic is set to the value of the IP address component of the destination argument of the create command if the IP reachable address is to an IP host. This characteristic is not used on circuits of type x25 da. You can modify this characteristic only when the entity is disabled. 5 Identifier o name Simple name assigned to the IP reachable address when it is created. 5 Status o state Status of the routing circuit reachable address entity. off The IP reachable address is disabled. on The IP reachable address is enabled. 4 reachable_address show [node node-id] routing - circuit circuit-name - reachable address simple-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status 5 Characteristics o address prefix Support: L2,End Default: None Value: Address Prefix Address prefix to which this reachable address refers. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. The value of this characteristic derives from an argument to the create command. This characteristic is supported only if the owning circuit has type set to x25 da. o block size Support: End, type outbound Default: 0 Value: 0-65536 The data link block size to be used for this prefix. For an end system, the data link block size to be used for this prefix. If the block size is set to the default, the manual block size of the circuit will be used instead. This attribute is supported only if the type characteristic is set to outbound. o cost Support: L2 Default: 20 Value: 1-63 Cost of reaching this address prefix over this circuit. o data format Support: L2 Default: Phase V Value: Phase IV (1) or Phase V (0) The PDU data format to be used when forwarding data (or error report) NPDUs using this reachable address. This attribute is supported only if the type characteristic is set to outbound. You can modify this characteristic only when the entity is disabled. o dte addresses Support: End,L2 Default: No DTE addresses={ } Value: Set of DTE addresses A set of DTE addresses to which a call may be directed in order to reach an address that matches the address prefix of this reachable address. This characteristic is supported if the node is a level 2 router, where the owning circuit's characteristic type is one of the X.25 circuit types, and the reachable address's characteristic type is outbound. It is also supported by end nodes operating over an x25 da circuit. You can modify this characteristic only when the entity is disabled. o ISDN address Support: L1,L2 Default: { } Value: Set of ISDN addresses A full set of E.164 ISDN network addresses that a call may be directed in order to reach a network number that matches the address prefix of the parent reachable address entity. Associated with each ISDN network address, but not visible to Network Management, is a variable last failure of type binary absolute time. This attribute is supported only if access type is ISDN DA. o LAN address Support: L2,End Default: 00-00-00-00-00-00 Value: ID A single LAN address to which an NPDU can be directed in order to reach an address that matches the address prefix of the parent reachable address entity. This attribute is supported only if the type characteristic is set to outbound on broadcast circuits only. A valid address is required here. You can modify this characteristic only when the entity is disabled. o mapping Support: End,L2 Default: X.121 Value: Manual or X.121 Type of mapping used to determine the SNPA address to which a call should be placed for this address prefix. You can modify this characteristic only when the entity is disabled. If the circuit is a broadcast circuit, this attribute must have the value manual. manual The mapping uses the set of addresses in the characteristic dte addresses or the address in the characteristic LAN address. X.121 The mapping uses the X.121 address extraction algorithm. This characteristic is supported only if either of the following conditions is satisfied: o The node is a level 2 router or an end node, and the owning circuit's characteristic type is one of the X.25 circuit types; or o The node is a level 2 router, the owning circuit's characteristic type is csma-cd, and the reachable address's characteristic type is outbound. o metric type Support: L2 Default: Internal Value: Internal, external The metric type of the cost metric for the circuits. If internal, the I/E bit for the metric in the Prefix Neighbors option of L2 LSPs is set to 0, otherwise (external) is set to 1. o modem addresses Support: L1,L2 Default: { } Value: Set of modem addresses A set of full dial sequence that contains the address (PSTN or ISDN) to which a call may be directed in order to reach a network number that matches the address prefix of the parent reachable address) entity. Associated with each modem address, but not visible to Network Management, is a variable last failure of type binary absolute time. This is valid only if mapping is manual and the parent circuit entity's access time is Modem DA. o modem address prefix Support: L1,L2 Default: L1,L2 Value: Address string The address that is to be inserted to the beginning of the address extracted from the NSAP address. This is valid only if mapping is not manual and the parent circuit entity's access type is Modem DA. It is used in conjunction with modem access suffix to form the complete dial sequence. o modem address suffix Support: L1,L2 Default: L1,L2 Value: Address string The address that is to be inserted to the end of the address extracted from the NSAP address. This is valid only if mapping is not manual and the parent circuit entity's access type is Modem DA. It is used in conjunction with modem access prefix to form the complete dial sequencence. o permitted LAN address Support: End Default: { } Value: Set of LAN addresses The set of LAN addresses corresponding to routers that are permitted to be used for forwarding to this prefix. This attribute is supported only if the type characteristic is set to filter on broadcast circuits only. The default is an empty set, and at least one LAN address is required. o type Support: L2,End Default: Outbound Value: Inbound, outbound, or filter Type of the reachable address. You can modify this characteristic only when the entity is disabled. inbound For L2 only, the address prefix corresponds to a Phase IV area that is reachable through this node and circuit by inbound traffic. outbound The address prefix is in an external domain that is reachable over this circuit by outbound traffic. filter The address prefix defines a set of addresses that should be reached via the set of routers listed in the permitted LAN address characteristic. 5 Identifier o name Simple name assigned to the reachable address when it is created. 5 Status o state State of the routing circuit reachable address entity. off The reachable address is disabled. on The reachable address is enabled. 3 destination_area show [node node-id] routing - destination area address-prefix attribute [,attribute] all [attributes] all identifiers all status This is supported only on nodes that are Level 2 routers. 4 Identifier o name Address prefix associated with this destination area. 4 Status o cost Support: L2 Cost of the least cost path(s) to this destination area. o output adjacencies Support: L2 Set of routing circuit and routing circuit adjacency (or routing circuit reachable address) entity names that represent the forwarding decisions for this destination area. 3 destination_cache_(Tru64_UNIX) show [node node-id] routing - destination cache address-prefix attribute [,attribute...] all [attributes] all identifiers all status 4 Identifier o name Address prefix associated with this destination area. 4 Status o information The set of records containing cache information relating to this address. 3 destination_node show [node node-id] routing - destination node node-id attribute [,attribute...] all [attributes] all identifiers all status This is supported on only on Level 1 and Level 2 routers. 4 Identifier o name System ID associated with this destination node. 4 Status o cost Support: L1,L2 Cost of the least cost path(s) to this destination node. o nets Support: L1,L2 Set of NETs computed from the system ID that is the entity's name and the area addresses in the routing entity's manual area addresses set. o output adjacencies Support: L1,L2 Set of routing circuit and routing circuit adjacency entity names representing the forwarding decisions for this destination node. 3 egp_group show [node node-id] routing - egp group group-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status This is supported only on Level 2 routers that support dual routing (and, in particular, the EGP routing protocol). 4 Characteristics o autonomous system number Support: L2,IP Default: 0 Value: 0-65535 The autonomous system number common to members of this group. You can modify this characteristic only when the entity is disabled. This attribute is supported only if the node is a level 2 router, and if the system supports dual routing (both DECnet and IP routing). o external routes Support: L2,IP Default: Receive Value: Set of send,receive If the set includes receive, external gateway routes are accepted from neighbors in the group; if the set does not include receive, external gateway routes are discarded. If the set includes send, external gateway routes will be sent to neighbors in this group; if the set does not include send, external gateway routes are not sent. You can modify this characteristic only when the entity is disabled. o maximum active neighbors Support: L2,IP Default: 1 Value: 0-255 The maximum number of neighbor systems in the group that this system will attempt to acquire and maintain in the Up state at any given time. You can modify this characteristic only when the entity is disabled. o receive metric class Support: L2,IP Default: External Value: Internal or external The class to be associated with routes received from EGP neighbors in this group (unless overridden by a routing receive route entity). You can modify this characteristic only when the entity is disabled. o send local metric Support: L2,IP Default: 1 Value: 0-255 The metric value to be used when announcing routes derived from local information (unless overridden by a routing send route entity). You can modify this characteristic only when the entity is disabled. o send metric classes Support: L2,IP Default: Internal Value: Set of external,internal Routes received through routing protocols other than EGP with metric classes in this set are candidates for announcement in EGP messages sent to neighbors in this group, subject to route propagation policy. Routes with metric classes not specified in this set will not be announced. You can modify this characteristic only when the entity is disabled. o send replacement metric Support: L2,IP Default: 1 Value: 0-255 Specifies the metric value to be used when announcing routes derived from non-EGP routing protocols (unless overridden by a routing send route entity). You can modify this characteristic only when the entity is disabled. 4 Identifier o name Simple name assigned to the EGP group when it is created. 4 Status o state Specifies the state of the routing egp group entity. off The entity is disabled. on The entity is enabled. 4 egp_neighbor show [node node-id] routing - egp group group-name - egp neighbor neighbor-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status This is supported only on Level 2 routers that support dual routing (and, in particular, the EGP routing protocol). 5 Characteristics o circuit Default: None Value: Circuit name Simple-name of the circuit. o ip address Support: L2,IP Internet address of this EGP neighbor. The value of this characteristic is derived from the ip address argument of the create command. You cannot modify this characteristic. o next hop Default: 0.0.0.0 Value: IP address IP address and the next routing node. o source network Default: 0.0.0.0 Value: Network number Network number to query. 5 Counters o creation time Support: L2,IP Time at which this entity was created. o error messages received Support: L2,IP Number of EGP error messages received from this neighbor. o error messages sent Support: L2,IP Number of EGP error messages sent to this neighbor. o messages received Support: L2,IP Number of EGP messages received without error from this neighbor. o messages sent Support: L2,IP Number of EGP messages sent to this neighbor. Note that this value does not include EGP messages counted by the counter send messages discarded. o received messages discarded Support: L2,IP Number of EGP messages received from this neighbor with any kind of error. o send messages discarded Support: L2,IP Number of EGP messages not sent to this neighbor because of resource limitations within the egp entity. o start events Support: L2,IP Number of times the EGP neighbor has been manually started. o stop events Support: L2,IP Number of times the EGP neighbor has been manually stopped. 5 Identifier o name Simple name assigned to the EGP neighbor when it is created. 5 Status o egp state Support: L2,IP EGP state of the system with respect to this EGP neighbor. acquisitionidle cease up down o hello time Support: L2,IP Interval, in hundredths of a second, between retransmissions of EGP Hellos. This value represents the t1 timer defined in RFC 904. o last event Support: L2,IP Specifies whether the last event issued on this EGP neighbor was a start or a stop event. start The last event was a start. stop The last event was a stop. This is the value with which an EGP neighbor is created, before either a start or stop command has been issued. o polling mode Support: L2,IP Polling mode of the EGP entity with respect to this neighbor as either active or passive. o poll time Support: L2,IP Interval, in hundredths of a second, between retransmissions of EGP polls. This value represents the t3 timer defined in RFC 904. o state State of the routing egp group egp neighbor entity. off The entity is disabled. on The entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 ip_destination_address show [node node-id] routing - ip destination address address-name attribute [,attribute...] all [attributes] all identifiers all status This is supported only on routers that support dual routing. 4 Identifier o name Subnet address of a destination subnetwork. 4 Status o level Support: L1,L2,IP Level at which the shortest path exists in the shortest paths database. Level 1 Level 2 External Level 2 Internal o metric Support: L1,L2,IP Default metric value for the shortest path to the destination subnetwork. o paths Support: L1,L2,IP Equal cost paths for this route. For each path the following information is given: 1. The name of the entity pair that represents the forwarding decision for this path (circuit and one of adjacency, IP adjacency, or IP reachable address). 2. The routing mechanism through which the route was learned: o Local: the route is derived from the subnet address or alternative subnet addresses characteristics of a local circuit. o Netmgnt: the route is derived from manually configured information on the local system. 3. The number of seconds since the route was last updated. 3 permitted_neighbor show [node node-id] routing - permitted neighbor neighbor-name attribute [,attribute...] all [attributes] all characteristics all identifiers 4 Characteristics o id Support: All Default: No default Value: Node ID Node ID of a potential neighbor node. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. o verifier Support: All Default: No verifier Value: Hex string, length 0-38 Verifier to be checked from this neighbor. You may change this characteristic at any time; however, the change will not take effect until the circuit is next initialized. You cannot display this characteristic. If the verifier is not set, then a connection to the neighboring node whose ID matches the ID in this entry is allowed. If the verifier is set, the connection is allowed only if the verifier sent by the remote node matches the one in this entry. 4 Identifier o name Simple name assigned to the permitted neighbor when it is created. 3 port show [node node-id] routing - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show routing port * name, client show routing port RTG$PORT21 all 4 Counters o creation time Support: All Time the entity was created. o data sdus received Support: All Number of data NSDUs delivered across Transport interface (after reassembly). o error reports received Support: All Number of error report PDUs delivered across Transport interface. o expired segments discarded Support: All Number of segments discarded because lifetime expired during reassembly. o ip packets reassembled Support: IP Number of IP packets that have been successfully reassembled from fragments. o sdus transmitted Support: All Number of data NSDUs requested for transmission across Transport interface. o segments discarded Support: All Number of segments (data- or error-report) discarded before delivery across the Transport interface, including segments discarded for any reason other than lifetime expiration during reassembly. o segments received Support: All Number of data- and error-report NPDUs received before reassembly. 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o client Support: All Name given by the user of the port when the port was opened. o nsap addresses Support: All Set of NSAP addresses to be received at this port. This attribute is supported only if the status attribute type is not set to IP. o nsap selector Support: All Network service access point (NSAP) selector octet supplied by the client. This attribute is supported only if the status attribute type is not set to ip. o protocol type Support: IP Value of the IP protocol field specified by the client. o type Support: IP Type of connectionless network service to be used: IP or ISO8473. o uid Entity's unique identifier, which is generated when the entity is created. 2 session_control show [node node-id] session control attribute [,attribute...] all [attributes] all characteristics all counters all status Examples: show session control naming search path show session control all 3 Characteristics o address update interval Default: 10 Values: 1-4294967296 Specifies the minimum time (in seconds) allowed between updates of address information. More frequent modification to the set of local towers is prohibited. o backtranslation search path Default: None Values: Search-path-information Describes the order in which name services will be searched for address-to-node-name translation requests (when more than one name service is in use on a node) and any associated naming templates for each directory service. o decnet-internet gateway enabled (Tru64 UNIX) Default: False Value: True or false If true, the DECnet-Internet Gateway is enabled. o decnet-internet gateway user (Tru64 UNIX) Name of a user under whose account to run gateway applications. o incoming proxy Default: True Value: True or false Specifies whether to honor incoming proxy requests. If this attribute is set to false, requests to invoke proxies on incoming requests are ignored. o incoming timer Default: 45 Values: 0-65535 Time (in seconds) to wait for a user module to issue an accept/reject call after a port enters a state indicating that a connection request was received. If the timer expires, Session Control aborts the transport connection with a timed out error. For OpenVMS, a zero (0) value directs Session Control to wait indefinitely without aborting the connection. o maintain backward soft links Default: True Value: True or false Specifies whether Session Control should attempt to update the backward translation soft links in the DECdns namespace when it detects an address change. In other words, when session control maintain backward soft links is true, session control will automatically attempt to ensure that the backtranslation softlinks in the DECdns namespace are consistent with those in the session control database on the local node. If this attribute is set to false, Session Control will not add any new backward translation soft links to the DECdns namespace, nor will it delete any that previously exist, in response to an address change. o modify acs Default: True Value: True or false Specifies whether Session Control should attempt to update the ACS (access control set) of the node object whenever it attempts to update the towers attribute for the node in the namespace. o naming cache checkpoint interval (OpenVMS) Default: 8 Value: Time Amount of time, in hours, between times when the address and node-name information is checkpointed to disk from the in-memory, local naming cache. o naming cache entry (OpenVMS) Default: None Value: Name Address and node-name information for a node that has been retrieved from a name service and is currently stored in the in-memory, local naming cache. o naming cache timeout (OpenVMS) Default: 7 Value: Time Amount of time, in days, after which the address and node-name information for a node is deleted from the in-memory, local naming cache. o naming search path Default: None Value: Search-path-information Describes the order in which name services will be searched for node-name-to-address translation requests (when more than one name service is in use on a node), and any associated naming templates for each name service. DNS Server nodes are required to specify DECdns as the first name service in this naming search path only when the server is initially configured. o node synonym directory (Tru64 UNIX) Default: .DNA_NodeSynonym Value: Full-name Full name of a DECdns directory that contains node synonyms. o non privileged user (OpenVMS) Specifies the Session Control on a non-privileged user account. o outgoing proxy Default: True Value: True or false Specifies whether to invoke a proxy on outgoing connection requests when the user does not explicitly specify to do so. If this attribute is set to false, no proxy is invoked. o outgoing timer Default: 60 Values: 0-65535 Time (in seconds) to wait for an outgoing transport connection to be accepted before Session Control aborts the connection with a timed out error. For OpenVMS, a zero (0) value directs Session Control to wait indefinitely without aborting the connection. o soft link timer (Tru64 UNIX) Default: 30 days Value: Binary relative time Interval of time (in days) DECdns checks that an object pointed to by a backward translation soft link still exists. o update retry interval Default: 60 Values: 1-4294967296 Time to wait before Session Control retries a failed attempt to update information in the namespace. The default is 60 minutes. o transport precedence Default: osi Values: Set of osi or nsp Note: On the DECnet/OSI for Digital UNIX V1.0 products the default was tp4 rather than osi. This command sets the order in which transports are selected when establishing a connection. The default order is to try OSI, then NSP. The command takes a set as input. Valid items in the set are SESSION CONTROL TRANSPORT SERVICE entity names. o version Default: Current version number Session control protocol version number. You cannot modify this characteristic. 3 Counters o access control violations Number of times Session Control has detected an access control violation event. o backtranslation deletions Number of times Session Control has detected a backtranslation deletion event. o bad backtranslation links Number of times Session Control has generated a bad backtranslation link event. o creation time Time this entity was created and all counters are zero. o dangling link Number of times Session Control has detected a dangling link event. o deleted maintained objects Number of times Session Control has detected a deleted maintained object event. o verification failures Number of times Session Control has detected a verification failure event. 3 Status o backtranslation directory Name of the root directory of the backtranslation tree. o state Status of the session control entity. off The entity is disabled. on The entity is enabled. restricted The entity is enabled and supports existing transport connections; it initiates outgoing transport connections, but it refuses incoming connections unless the request meets system privilege requirements. This function is only supported on Tru64 UNIX. shut The entity is enabled and supports existing transport connections, but it refuses any new connection requests. After all transport connections disappear, the state will automatically change to off. This function is only supported on Tru64 UNIX. o uid Entity's unique identifier, generated when the entity is created. 3 application show [node node-id] session control - application object-name-or-object-number attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status You can identify an application with an object name or an object number. Usually, applications are identified by network object number 0, but you can optionally assign it a nonzero object number, in the range from 128 to 255. A nonzero object number can be specified without an application name. Object numbers 1 through 127 are reserved for use by HP. Specific network services are identified by nonzero object numbers; for example, 27 represents the mail utility. Examples: show session control application * name, addresses show session control application 26 all 4 Characteristics o addresses Default: Empty set Value: Set of end-user specifications A set of end-user specifications, any one of which, when specified in the destination name field of an incoming connection request, causes applications defined by this entity to be invoked. An end-user specification can be either a name or a number. Usually, applications are identified by network object number 0, but you can optionally assign it a nonzero object number, in the range from 128 to 255. A nonzero object number can be specified without an application name. Object numbers 1 through 127 are reserved for use by HP. Specific network services are identified by nonzero object numbers; for example, 27 represents the mail utility. For example, the task application uses the address set {name=task}, and the mail application uses the address set {number=27}. o accept mode (Tru64 UNIX) Default: Immediate Value: Immediate or deferred If accept mode is immediate, then session control will automatically accept the connection before activating the end user. If accept mode is deferred, then it is up to the program to accept or reject the connection. o allow decnet-internet gateway access (Tru64 UNIX) Default: False Value: True or false If true, this application supports gateway access. If the user name supplied by the incoming connect request contains a @ or !, the application spawner starts up the application under the session control DECnet-Internet Gateway user. o client Data type: Entity name Identifies the name of the local user that will be activated upon receipt of a connect request containing a destination name matching one of the values in the destination names attribute. o data abstraction (Tru64 UNIX) Default: Message Value: Message or stream Type of data transfer interface the application will be using; message type or stream type. The message data abstraction is identical to the Sequenced-packet socket concept of the Phase IV session control. When writing applications, you should use the same data abstraction as that used by the program to which you connect. Table Data Abstraction Type Comparison compares Message and Stream data abstractions. Table 1-1 Data Abstraction Type Comparison Message Type Stream Type Preserves message Does not preserve message boundaries boundaries HP DECnet-Plus Commonly used for Tru64 UNIX applications for OpenVMS default abstraction Not available on Available on TCP/IP TCP/IP Supported by XTI Supported by XTI o image name Default: No image name Value: File specification File name of a program to be invoked upon receipt of a connection request containing an address that matches one of the values contained in the set described by the addresses characteristic. o incoming alias (Tru64 UNIX) Specifies how a particular application responds to incoming connect requests directed to the alias node address. If False, the application does not allow a specified application to receive incoming connect requests that have been directed to the alias node address. o incoming osi tsel (OpenVMS) Default: none Value: hex-string A TSEL is a string of hex digits, the length of that string should be an even number between 2 and 64, inclusive. The TSEL this image will accept connections for. This is similar to the destination names attribute. However, applications using this access point for in-connection matching do not use DNA Session Control protocol. o incoming proxy Default: True Value: True or false Specifies whether to honor incoming proxy requests. If this attribute is set to false, requests to invoke proxies on incoming requests are ignored. The setting of this characteristic overrides the setting of the session control incoming proxy characteristic for the specified application. o maximum instances (Tru64 UNIX) Default: 0 Maximum number of simultaneous instances of this application allowed. If a connect request comes in for this application while the maximum number of instances exist, the connect request will be rejected with ObjectTooBusy. A value of 0 indicates no maximum. o network priority (OpenVMS) Default: 0 Value: 0-255 When operating over CLNS, indicates network priority encoded in NPDU header for all transmitted packets. It may be used by intermediate systems to assign the packets to queues of appropriate priority. o node synonym Default: False Value: True or false Default form in which the remote node name is passed to the application. false The full node name is used. true The node synonym is used; if no synonym is available, the full name is used. o outgoing alias (OpenVMS) Default: True Value: True or false Specifies whether a particular object uses the alias node identifier in its outgoing connect requests. If false, the specified object is not allowed to use the alias node address in its outgoing connect requests. o outgoingalias name (OpenVMS) Default: None Value: fullname Specifies which alias name a particular object uses in its outgoing connect requests when multiple aliases are in use. If you do not set an application outgoingalias name and the application has the outgoing alias set to true, the alias name for which you set the alias port outgoing default true is used for outgoing connect requests. If you define application outgoingalias name, this supersedes the setting of alias port outgoing default. So if the application outgoing alias attribute is then set to false to disable the application outgoingalias name, the local node name is used. If neither alias port going default nor application outgoingalias name is set, the first alias created is used as the default for the system. If this alias is not enabled, the local node name is used. o outgoing proxy (OpenVMS) Default: True Value: True or false Default action to execute when user does not explicitly specify whether or not to invoke a proxy. o programming interface (Tru64 UNIX) Default: Phase IV Value: Phase IV or Phase V Programming interface used by the DECnet application (socket interface). o user name Default: None Data type: Latin1String Identifies the default account under which the application is to run. For OpenVMS, if null then system defaults are used to select the user. 4 Counters o access control violations (Tru64 UNIX) Number of connect requests for this application entity for which access could not be granted. o creation time Time the entity was created. o resource failures (Tru64 UNIX) Number of times a connect request for this application was rejected due to a resource failure. Resource failures include ObjectTooBusy (for example, due to Maximum Instances reached) and File is nonexistent or not executable. o total invocations (Tru64 UNIX) Number of instances of this application entity that have been invoked. 4 Identifier o name Simple name assigned to the application when it is created. 4 Status o active instances (Tru64 UNIX) Number of active instances of this application that are currently running. o last request (Tru64 UNIX) Time the last connect request for this application was received. o process identifiers (Tru64 UNIX) Specifies a set of processes that are active instances of the specified application. o uid UID allocated upon creation of this application subentity instance. 3 backtranslation_softlink show [node node-id] session control - backtranslation softlink softlinkname attribute [,attribute...] all [attributes] all counters all identifiers all status Shows the backtranslation softlink subentities in the session control database on the specified node. If the node is using the DECdns directory service, then such one softlink subentity should exist for each DECnet address held by the node. (Softlinks are NOT created for cluster alias addresses.) If an OpenVMS node is configured to run DECnet over IP and is using the DECdns namespace, then one softlink subentity should exist for each non-zero IP address as well. Softlinks in the DECdns namespace are used by all nodes in the namespace to associate a particular address with a nodename (DNS$LinkTarget). Therefore, if a node's backtranslation softlinks are not properly configured within a DECdns namespace, then other nodes using that namespace will not be able to associate that address with correct nodename. NCL can be used to show what softlinks the node can be configured to maintain in the specified DECdns namespace. If the session control attribute maintain backward softlinks is true, then the node will periodically attempt to update its softlinks in the DECdns namespace. If the NCL SHOW command indicates a high Update Failure rate, the Last Failure Reason may suggest the reason for the failure. You may then use the DNS$CONTROL and DECNET_REGISTER tools to troubleshoot. These tools can be used to confirm that a DECdns server is accessible and that the DECdns namespace contains the proper object and softlinks for this node. Examples: show node WINTER:.XPR.CASE session control backtrans softlink * all ! Shows all softlinks contained in the session control ! database of node WINTER:.XPR.CASE. show session control backtranslation softlink - WINTER:.DNA_BACKTRANSLATION.%X49.%X0018.%XAA0004002A60 all ! Shows a softlink contained in the session control database ! for the local node. It indicates that the node is the ! holder of DECnet address 24.42 within the WINTER namespace. show session control backtranslation softlink - WINTER:.DNA_BACKTRANSLATION.%XA1725E45 all ! This softlink indicates that the local node is configured ! as the holder of the IP address 161.114.94.69 in the ! WINTER namespace. (IP softlinks are on OpenVMS only) 4 Identifier o name Simplename assigned when it was created. 4 status o uid Entity's unique identifier, generated when it was created. o target Target (or nodename) associated with this softlink. o network entity title Network entity title for this softlink. Since the concept of a NET makes no sense for IP softlinks, the hexadecimal representation of the IP address is displayed instead. o state Status of this entity instance. Values include create, delete, exist and retarget. o last successful update Most recent time an update for this subentity succeeded. o last update completed Most recent time an update for this subentity completed. o last update started Most recent time an update for this subentity was initiated. o last failure reason Reason for the most recent update failure. 4 Counters o creation time Time when the subentity was created. o update failures Number of times an update for this subentity failed. o update successes Number of times an update for this subentity succeeded. 3 port show [node node id] session control - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show session control port * name, remote end user address show session control port SCL$PORT$12040008 all 4 Counters o creation time Time the entity was created. 4 Identifier o name Simple name assigned to the port when it is created. This name is passed to the Transport layer as the client name in a call to open a port. 4 Status o accept mode (Tru64 UNIX) Value: Immediate or deferred If accept mode is immediate, Session Control automatically accepts the connection before activating the end user. If accept mode is deferred, it is up to the end user to accept or reject the connection. o auto disconnect (Tru64 UNIX) Value: True or false True if Session Control will abort the transport connection for this port if Transport determines the network is partitioned. o client Value: Local-entity-name Network management name specified by the user of the port when it was opened. o data abstraction (Tru64 UNIX) Value: Message or stream Type of data transfer interface the application uses. o direction Specifies whether the port is open to initiate an outgoing transport connection or to receive an incoming one. incoming Port was opened to handle an incoming transport connection. outgoing Port is open to initiate an outgoing transport connection. unknown The port status is unknown at this time. listening The port is open to receive incoming transport connections. o incoming network priority (OpenVMS) Default: None Value: 0-255 Incoming network priority value received with incoming connect events. o listening parent port (Tru64 UNIX) Value: Local-entity-name Name of the session control port that this port came from as the result of a PollIncoming on the parent port. o local end user address Address assigned by the user of the port when it was opened. On outgoing connections this value is sent in the source name field of the connection request; on incoming connections this value is received in the destination name field of the request. o node name sent Node name that was received or sent in the connect request. o outgoing network priority (OpenVMS) Default: None Value: 0-255 Outgoing network priority value passed to transport. o process identifier (OpenVMS) Default: None Value: Hex string The Process Id of the process that owns the session port. o programming interface (Tru64 UNIX) Value: Phase IV or DECnet-Plus Programming interface the DECnet application uses. HP DECnet for Tru64 UNIX uses this socket interface. o proxy requested (Tru64 UNIX) Value: True or false True if the request proxy bit was turned on in the connect request that was received or sent. o queued connects (Tru64 UNIX) Value: Integer Number of connect requests pending that PollIncoming has not dequeued yet. o receive queue (Tru64 UNIX) Value: Integer Number of octets of unread data queued. o remote end user address Address of the remote end user of the port. This value was either sent in the destination name field of an outgoing connection request or was received in the source name field of an incoming connection request. If the value of the direction attribute is incoming or unknown and no connection request has been received, the value of this attribute is null. o send queue (Tru64 UNIX) Value: Integer Number of octets of unsent data queued. o transport port Value: Local-entity-name Network management name of the transport port being used by this session control port. o version sent Version that was received or sent in the connect request. 3 proxy_(Tru64_UNIX) show [node node-id] session control - proxy name attribute [,attribute...] all [attributes] all counters all identifiers all status 4 Identifier o name Simple name assigned to a particular entity instance. The name is the management identifier for the proxy database entry and is kept unique among the entries in this database maintained by Session Control. 4 Characteristics o applications Value: Set of simple-name Set of application identifiers, one of which must match the application requested. If this attribute value is null, any requested application will match. o source end users Value: Set of record Set of remote end users for whom this proxy entry applies. An unspecified end user implies all end users on the node specified in the same record. The record format has two fields: node which has a data type of fullname, and end user which has a data type of enduserspecification. o target user Default: None Value: Latin1String Local user name under which access is granted. o type Default: Explicit Value: Explicit or default Type of proxy entry. explicit means that the destination the user requested in the connect request must match the target user for this entry. default means if no explicit entry matches, this entry will be tried. An explicit proxy entry matches before a default one. 4 Counters o creation time Time the entity was created and associated counter attributes were zero. o used Number of times this proxy entry was used to gain access to one of the applications. 4 Status o last time used Last time this proxy entry was used to gain access to one of the applications. 3 tower_maintenance show [node node-id] session control - tower maintenance fullname attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show session control tower maintenance * all show session control tower maintenance DEC:.lkg.wzbang all 4 Identifier o name Fullname assigned to the tower maintenance entity when it is created. 4 Counters o creation time Time this entity was created. o update failures Number of times this entity detected an update failure event. o update successes Number of times that the DNA$Towers attribute of the DECdns object name associated with this entity has been successfully updated. 4 Status o client Network management name of the user who issued the keepmehere call that resulted in the creation of this entity. o higher towers Set of higher towers that was passed in the keepmehere call that created this entity. o last failure exception (Tru64 UNIX) Reason for the most recent update failure. If no update for this subentity ever failed, then it is zero. o last failure reason DECdns error code that indicates the reason for the last update failure. o last successful update Time of the last successful update to the DNA$Towers attribute for the specified entity. On OpenVMS, if no update for this subentity ever failed, then it is zero. o last update completed Time that the last attempt to update the DNA$Towers attribute completed (successfully or not). o last update started Time that the last attempt to update the DNA$Towers attribute for the specified entity was initiated. o uid Entity's unique identifier, which is generated when the entity is created. o user (Tru64 UNIX) User name of the user who created this tower maintenance subentity with the keepmehere procedure call. This is different from client, which refers to a local entity name. 3 transport_service show [node node-id] session control - transport service transport-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show session control transport service NSP all show session control transport service OSI all 4 Counter o creation time Time the entity was created. 4 Identifier o name Simple name assigned to the transport service when it is created. 4 Status o protocol Transport protocol used by this transport service, as specified by the user when this service was created. (See the create command description for a list of possible values.) o tsel Transport selector used by the OSI Transport Module to bind incoming connection requests to session control. With Tru64 UNIX, the TSEL value is specified in a create command. This attribute is not applicable for NSP transport. 2 token_ring_(Tru64_UNIX) show [node node-id] token ring attribute [,attribute...] all [attributes] all characteristics 3 Characteristics o version Default: Current version number Version number of the Token Ring architecture specification to which the implementation conforms. You cannot specify this characteristic. 3 station show [node node-id] token ring - station station-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status 4 Characteristics o aging timeout Default: 60 seconds Value: 1--655 Controls the timeout of the source routing information for nodes that the local node has not recently communicated with. o communication port Name of the hardware port associated with this station, taken from the corresponding argument in the create directive. You cannot modify this characteristic. o discovery timeout Default: 1 second Value: 1--255 Controls the timeout of the source routing discovery process. o etr Default: True Value: True or false Determines if Early Token Release is in use on this station. ETR may be supported only on 16 Mbps media. This attribute can only be set in the off state. o maximum source routes Default: 1024 Value: 256-2048 The maximum number of source route subentities this station will buffer. Can only be set in the off state. o monitor contender Default: False Value: True or false Determines if the station will try to become the Active Monitor, if a lower addressed station starts the monitor contention process. This attribute can only be set in the off state. o ring speed Default: Unknown Value: 4 or 16 Mbps The data rate of the media. Can only be set in the off state. o station address Default: Hardware ROM address Value: None The desired station address. Can only be set in the off state. 4 Counters Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers. o abort delimiter sent Number of times an abort delimiter was sent while transmitting. o auto-removal failures Number of times a failure during the beacon auto-removal process was detected and the station removed itself from the ring. o burst errors Number of times a lack of transitions was detected on the physical media. o creation time Time at which the station entity was created. o explorer frames received Number of SR explorer frames received by the source route entities. o explorer frames sent Number of source routing (SR) explorer frames sent by the source route entities. o frame copied errors Number of individually addressed frames received with the Address Recognized status bit = 1. o frequency errors Number of times an error was detected in the incoming signal frequency. o insertion failures Number of times that a ring insertion operation has failed. o internal errors Number of times a recoverable internal error was recognized. o line errors Number of times a CRC error or a non-data symbol in a frame or token with the E bit = 0 was detected. o lobe wire faults Number of times an open or shorted lobe data path was detected and the station removed itself from the ring. o lost frames Number of times this station has transmitted a frame and has failed to receive it for stripping before the Timer Return to Repeat (TRR) timer expired. o multicast octets received Number of octets successfully received in multicast frames of type LLC. (The count does not include the MAC envelope.) o multicast octets sent Number of octets successfully sent in multicast frames of type LLC. (The count does not include the MAC envelope.) o multicast pdus received Number of multicast frames successfully received of type LLC. o multicast pdus sent Number of multicast frames successfully sent of type LLC. o octets received Number of octets successfully received in frames of type LLC. o octets sent Number of octets successfully sent in frames of type LLC. o pdus received Number of frames successfully received of type LLC. o pdus sent Number of frames successfully sent of type LLC. o receive data overruns Number of times a frame was lost due to system or adapter transfer failure. o receiver congestions Number of frames recognized as matching one of this station's individual, group, or functional addresses, but could not be received for lack of buffers in the adapter. o remove frames received Number of times a remove MAC frame has been received and the station removed itself from the ring. o ring beaconings Number of times the condition of receiving or transmitted Beacon frames was detected due to a hard error. o ring failures Number of times the station left the ring due to failure. o ring recoveries Number of times detected the ring is in the monitor contention process. Indicates that the ring has attempted to recover from a soft error problem. o ring poll errors Number of times an error was detected in the A&C bits during the ring poll process. o route discovery failures Number of times the route discovery process failed to find a route to another station. o selftest failures Total number of times a self-test of the station detected an error. o signal losses Number of times detected loss of signal on the physical media. o single station conditions Number of times detected being the only station in the ring. o soft error reports sent Number of times sent a report error MAC frame to the ring error monitor. o unavailable station buffers Number of times a frame was discarded because no station level buffers were available. o unavailable user buffers Number of times a frame was discarded because no user buffer was available. o unrecognized individual destination pdus Number of times a received individually addressed LLC frame was discarded because there was no data link port with a matching SAP, SNAP PID, or Ethernet protocol type. o unrecognized multicast destination pdus Number of times a received LLC frame addressed to an enabled group or functional address was discarded because there was no data link port with a matching SAP, SNAP PID, or Ethernet protocol type. o token error Number of times when this station (when Active Monitor (AM)) has transmitted a new token due to errors on the ring. o transmit failures Number of times a transmit error, other than underrun occurred. Transmit error reasons can be tracked by event reasons, or by observing other 802.5 counters. o transmit underruns Number of times a transmit underrun occurred. o transmitting beacons Number of times initiated transmitting beacon frames. 4 Identifier o name Simplename assigned to token ring station when it was created. 4 Status o authorized access priority The maximum transmit priority allowed for this station. The value is set by the ring parameter server. o authorized function classes The bit map of the authorized function classes for this station. o functional address The functional address bit map enabled in the adapter for the reception on this station. o group addresses The set of group addresses enabled in the adapter for reception on this station. o insert error reason Reason code for an insertion error if there was a failure to insert into the ring, or insertion successful if no error. no open An error occurred during the insertion phase. bad parameters Invalid options specified to the adapter to insert into the ring. lobe fault Lobe test fault or MAC frames were received before physical insertion. signal loss Signal loss condition was detected during the insertion phase. timeout Logical insertion onto the ring failed before insertion timer expired. ring failure Unable to receive its own ring purge MAC frames after becoming the active monitor. ring beaconing A beacon MAC frame was received after physical insertion onto the ring. duplicate address Another station on the ring already has the address this station wishes to use. parameter server A Ring Parameter Server (RPS) is present on error the ring but does not respond to a request initialization MAC frame. remove frame A remove station MAC frame received was received during the insertion process. insertion successful The insertion phase was successful. o link state Data link state of this ring station. off Station is not on the ring. running Station is available to the user for processing. initializing Station is in process of inserting into the ring. recovery Station is beaconing. contending Station is participating in the monitor contention process. broken Station has failed the insertion process. o MAC address The currently active station address value for which the data link is receiving an individually addressed frame. o nearest upstream neighbor The MAC address of the last known upstream ring neighbor as heard from the ring poll process. o physical drop number The physical drop number assigned by the ring parameter server. o receive mode The receive mode of the station. Normal or promiscuous. o ring error reason Reason code for the most recent ring error detected by this station or no error if none has occurred. no error Successful operation, no error has occurred. ring in Claim token MAC frames were observed on the ring. recovery single It sensed this is the only station on the ring. station remove frame A remove ring station MAC frame request was received received and the station has deinserted from the ring. auto-removal The auto-removal process has failed and the station failure has deinserted from the ring. lobe fault An open or short circuit in the lobe wire cable was detected. transmitting Beacon frames are transmitted to the ring. beacon soft error A report error MAC frame has been transmitted. frame sent beaconing Beacon frames are presently transmitted or received condition to or from the ring. signal loss A loss of signal was detected on the ring. open in Station is in process of inserting into the ring. progress o ring number The local ring number as received from the ring parameter server. o ROM address The IEEE Universally Administered address present in the ROM of the adapter. o transparent source routing State of transparent source routing support. o state Operational state of the station. o uid Entity's unique identifier, which is generated when the entity is created. 4 source_route show [node node-id] token ring - station station-name- source route sourceroute-id attribute [,attribute...] all [attributes] all counters all identifiers all status This is supported on Tru64 UNIX only. 5 Counters o creation time Time at which the source route entity was created. 5 Identifiers o LANaddress The MAC address of the entity's destination station. 5 Status o routing information Source routing information to be used when communicating with the entity's destination station. o state State of the source route entity. no route No path known to the entity's destination address. on ring Destination station on the local token ring. No source routing information needed. have route Destination station on a remote token ring. Entity contains valid source routing information. rediscovering Route discovery on the extended token ring is in progress. stale Had source route but the Aging Timer expired. weak route Entity was created as a result of a Spanning Tree Explorer multicast frame. o uid Entity's unique identifier, which is generated when the entity is created. 4 FA_map show [node node-id] token ring - station station-name - FA map famap-id attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status This is supported on Tru64 UNIX only. 5 Characteristics o functional address Functional address used to send or receive frames on the token ring. o group address Group address used for sending or receiving frames. o SAP address LLC SAP address protocol of frames to be mapped. If SNAP SAP (AA) then the SNAP PID applies. o SNAP PID SNAP protocol identifier for SNAP SAP frames. 5 Counters o creation time Time at which the FA map entity was created. 5 Status o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] token ring - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status This is supported on Tru64 UNIX only. 4 Counters o creation time Time at which the port subentity was created. o multicast octets received Number of multicast user data octets successfully received and available to the data link user. This counter is optional. o multicast octets sent Number of multicast user data octets successfully transmitted using the port. This counter is optional. o multicast pdus received Total number of multicast frames successfully received and available the data link user. o multicast pdus sent Number of multicast frames successfully transmitted using the port. This counter is optional. o octets received Total number of user data octets successfully received and available to the data link user. This counter is optional. o octets sent Number of user data octets successfully transmitted using the port. This counter is optional. o pdus received Total number of frames successfully received and available to the data link user. o pdus sent Total number of user frames successfully transmitted using the port. o unavailable user buffers Number of times no user buffer was available at the port for an incoming frame. 4 Identifiers o name Simple name assigned to the port when it is created. 4 Status o client Name specified by the data user link when the port is opened. o ethernet protocol types Set of Ethernet protocol types that are recognized for this port. o FA map mode If set to enabled, indicates that functional address mapping is being performed. Specified by the user when the port is opened. o FA-GA map Set of functional-to-group address/PID mappings for this port. o length present Indicates whether a length field is used in Ethernet format frames sent or received on this port. o llc sap addresses Set of individual and group LLC SAP addresses that are recognized for this port. o llc service The LLC PDU processing the data link user requires from the port. Specified by the user when the port is opened. o mac addresses Set of individual and multicast MAC addresses that are recognized for this port. o receive mode If set to promiscuous, indicates if the port is to frames regardless of MAC address. Or, on ports of type LLC, regardless of Ethernet protocol type, SNAP protocol identifier, or LLC SAP address. o station Name of the station subentity associated with this port. Specified by the user when the port is opened. o SNAP protocol identifiers Set of SNAP protocol identifiers that are recognized for this port. o source routing mode If set to transparent, indicates that transparent source routing is in effect. Specified by the user when the port is opened. o type Type of port specified by the user when the port is opened. o uid Entity's unique identifier, which is generated when the entity is created. 2 x25_access show [node node-id] x25 access attribute [,attribute...] all [attributes] all characteristics all counters all status 3 Characteristics o maximum active ports Default: Implementation specific Value: Implementation specific Total number of ports that can be active simultaneously. You cannot modify this characteristic. It is supplied as an argument to the create directive. o version Default: Current version number Version number of the X.25 architecture specification to which the implementation conforms. You cannot modify this characteristic. 3 Counters o creation time Time at which this entity was created. o incoming calls blocked Number of incoming calls that have been cleared at the X.25 Access module because of security failures. o incoming calls failed Number of incoming calls that have been cleared at the X.25 Access module for reasons other than security failures. o outgoing call configuration errors Number of calls that have failed due to misconfiguration of security management databases. o outgoing calls blocked Number of outgoing calls that have been cleared at the X.25 Access module because of security failures. o pvc accesses blocked (Tru64 UNIX) Number of PVC accesses that have failed due to security blocking. o times port terminated Number of times the port terminated event has occurred. 3 Status o active ports Sum of the number of SVCs on which a call is either being set up or is in the data phase. Or, for OpenVMS, the number of PVCs that have been allocated to users. o state Status of the x25 access entity. off The x25 access entity is disabled. on The x25 access entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 application show [node node-id] x25 access - application application-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status Examples: show x25 access application * all show x25 access application X29_LOGIN all show x25 access application X25_MAIL file, user 4 Characteristics o account (Tru64 UNIX) Default: No service/account data Value: String Default service or account identifier to be used when starting the applications process. o activation data (Tru64 UNIX) Default: None Value: String Data required to start the application process. This characteristic is optional. This attribute is not valid for an application of type X29 login. o file Default: None Value: File name Indicates the file name or command that is associated with starting a process for the represented application. This attribute is not valid for an application of type X29 login. o filters Default: None Value: Set of names Set of filters that are associated with filtering calls for either X.25 or X.29 applications represented by this entity. o maximum activations (Tru64 UNIX) Default: 1 Value: 1-65535 Maximum number of concurrent activations of the represented application that are possible. This characteristic is optional. o template (Tru64 UNIX) Default: No template Value: String Template used by the application process to accept the incoming call. Attempting to set this attribute for an application of type X25 is not valid, and will generate a constraint error. o type Default: X25(0) Value: Enumerated (see description) Specifies the type of application. X25(0) This application operates in X.25 mode X29(1) This application operates in character mode. X29 login(2) This is an application of X.29 type devoted specifically to login sessions. o user Default: No user ID Value: String Default user identification to be used to start the application process. This attribute is not valid for an application of type X29 login. 4 Identifier o name Simple name assigned to the application when it is created. 4 Status o state Default: None Value: On(0), Off(1) State of the application. This state can be changed by invoking the enable and disable directives. 3 dte_class show [node node-id] x25 access - dte class class-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status Examples: show x25 access dte class * name, type show x25 access dte class AUSTPAC all 4 Characteristics o account (OpenVMS) Default: No service/account data Value: String Default service or account data to be used when connecting to the X.25 server on the gateway system specified by the node characteristic or service node characteristic. This attribute is supported only for DTE classes with characteristic type remote. o DNIC Default: Supplied by Value: DTE address of 3 or 4 digits length profile The first part of the Network User Address (NUA). This takes one of two forms: Either it is in the form of the Data Network Identification Code (DNIC) and is specified by 4 digits, or it is in the form of a Data Country Code (DCC) and is specified by 3 digits. If no profile is specified, the default is null. o International prefix Default: Supplied by Value: DTE address of 1 digit only. profile First digit of an X.121 address to indicate an international or internetwork call. If no profile is specified, the default is a null DTE address. o local dtes Default: No names Value: Set of names Names of the local x25 protocol dte entities that belong to this DTE class. Note that these DTE entities need not exist when their names are entered in this set; DTEs that do not exist when the DTE class is used are not considered when the DTE class is used for an outgoing call. If an x25 protocol dte entity has status attribute state set to running when its name is added to local dtes, you must disable the DTE entity and reenable it (see the disable x25 protocol dte and enable x25 protocol dte commands) in order for the DTE to be considered when this DTE class is used for an outgoing call. You can specify this characteristic only for DTE classes with characteristic type local. o local prefix Default: Supplied by Value: DTE address of 1 digit only profile First digit of a DTE address to indicate a local call. If no profile is specified, the default is a null DTE address. o node (OpenVMS) Default: No name Value: Full-name Node name of the remote gateway system on which the DTEs in this DTE class reside. Note that this characteristic is supported only if the service nodes characteristic is not supported. This characteristic is supported only for DTE classes with type characteristic set to remote. o outgoing session template (OpenVMS) Default: Default or no name Value: String (see description) Name of the OSI Transport template to be used by the X.25 client to connect to the X.25 server on the gateway system. The default value default is valid only if OSI session control is being used. This attribute is supported only for DTE classes with characteristic type remote. o profile Default: No profile Value: String Name of the profile that supplies the information required to perform X.121 mapping to or from a simple DTE address. The profile supplies the default values for the International prefix, Local prefix, DNIC and strip DNIC characteristics. This characteristic is specified by the profile argument in the create command. This argument is optional. o security dte class Default: Default Value: Name Name of the x25 access security dte class entity that controls inbound and outbound access using this DTE class. o service nodes (OpenVMS) Default: No records Value: Set of records Names of the nodes that may be used as candidate X.25 gateway systems and their associated ratings. Each record consists of a full name that describes the candidate node and an integer that indicates its ratings. The records are listed in order of descending rating. Values are entered as [node=nodename, rating=integer]. The rating represents the maximum number of session control connections to the node pair. o strip DNIC Default: False Value: True or false Defines whether the first part of the NUA (the DNIC or DCC specified by the DNIC characteristic) should be stripped for outgoing calls, and whether the network strips the first portion of the NUA from addresses it presents to the DTE. o type Type of DTE class. local The DTE class consists of local DTEs. remote The DTE class consists of DTEs on a remote gateway system. The value of this characteristic is specified by the type argument in the create command. o user (OpenVMS) Default: No user ID Value: String Default user identification to be used when connecting to the gateway system specified by the service nodes characteristic. 4 Identifier o name Simple name assigned to the DTE class when it is created. 4 Status o usable dtes Set of DTEs that are enabled and belong to this DTE class. For outgoing calls, a DTE is picked from this set if it is eligible (that is, if its status attribute state is set to running). If there is more than one eligible DTE, a round-robin algorithm is used to select one of the eligible DTEs. A DTE is added to the set when it is enabled, and is removed from the set when it is disabled (see the enable x25 protocol dte and disable x25 protocol dte commands). 3 filter show [node node-id] x25 access - filter filter-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show x25 access filter * name, incoming dte address show x25 access filter FILTER_1 all 4 Characteristics o call data mask Default: No mask Value: Hex string Mask to be applied to call user data in an incoming call. The result is compared, octet by octet, with the call data value characteristic. o call data value Default: No call user data Value: Hex string Call user data value to be matched by this filter. This value is compared, octet by octet, with the masked call user data in the call request. This string must have the same length as the string specified for the call data mask characteristic. o called address extension mask Default: No called address Value: Hex string extension mask Mask to be applied to the called address extension in an incoming call. The result is compared, octet by octet, with the called address extension value characteristic. o called address extension value Default: No called address Value: Hex string extension value Called address extension value to be matched by this filter. This value is compared, octet by octet, with the masked called address extension value. This string must have the same length as the string specified in the called address extension mask characteristic. o group Default: No group name Value: Group name Name of the x25 protocol group entity to be matched by this filter. The DTE must belong to this group for the filter to match. Wildcards can be used in the group name. o inbound dte class Default: No DTE class Value: Class name Name of the DTE class to be matched by this filter. The DTE must belong to this DTE class for the filter to match. This is the DECnet-Plus mechanism for specifying a local receiving DTE; see also the description of the receiving dte address characteristic. Wildcards can be used in the class name. o incoming dte address Default: No DTE address Value: DTE address Value to be matched with the "called address" field of an incoming call packet. Wildcards can be used in the incoming DTE address. o originally called address Default: No address Value: DTE address Value to be matched with the "originally called address" field of an incoming call that has been redirected. Wildcards can be used in the originally called DTE address. o called nsap Default: No NSAP address Value: NSAP address Value to be matched against the called address extension field of an incoming call packet when the field contents are encoded in ISO format. o priority Default: 1 Value: 0-65535 Filter's position in an ordered set of filters used for matching incoming calls. o receiving dte address Default: No DTE address Value: DTE address Address that is used to match the DTE address of the local receiving DTE. This characteristic is included for backward compatibility with Phase IV; the DECnet-Plus mechanism uses the dte class characteristic. Wildcards can be used in the receiving DTE address. o redirect reason Default: Not specified Value: See description Reason for matching a call that has been redirected. busy The original destination was busy. not specified Redirection was not checked. specified out of order The original destination was not operational. systematic Calls to the original destination are systematically redirected. This value must be the same as the redirect reason in the call request for the filter to match. o security filter Default: Default Value: Security filter Name of the x25 access security filter entity that controls access to this filter. Wildcards can be used in the security filter name. o sending dte address Default: No DTE address Value: DTE address Value to be compared with the "calling address" field of an incoming call packet. These values must be the same for the filter to match. Wildcards can be used in the sending DTE address. o subaddress range (OpenVMS VAX) Default: No range Value: Set of one range Subaddress range value to be matched by this filter. Format the values to specify this subaddress range. This set must either be empty or contain exactly one value. This attribute has been retired; it has been included to allow the value of the attribute to be seen, but it cannot be modified. 4 Counters o creation time Time at which this entity was created. o incoming calls blocked Number of times that an incoming call that matched this filter has been cleared by security. 4 Identifier o name Simple name assigned to the filter when it is created. 4 Status o listener When the status attribute state is set to in use, this specifies the name of the entity that is the listener with which this filter is associated. When the status attribute state is set to free, this status is undefined. o state Status of the x25 access filter entity. free The filter is not associated with a listener, and is therefore not currently used in matching incoming calls. in use The filter is associated with a listener, and is currently being used to match incoming calls. o uid Entity's unique identifier, which is generated when the entity is created. 3 port show [node node-id] x25 access - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Example: show x25 access port * name, call direction 4 Counters o data octets received Number of data octets received at the port. o data octets sent Number of data octets sent by the port. o pdus received Number of pdus received at the port. o pdus sent Number of pdus sent by the port. o reference time Time at which the port was created (if the circuit is a PVC), or the time at which the port was first used to send or receive a call at the X.25 user interface (if the circuit is an SVC). o segments sent Number of segments of data sent by this port. o segments received Number of segments of data received by this port. 4 Identifier o name Simple name assigned to the port when it is created. 4 Status o call association Name of the x25 access filter entity that matched an incoming call, or the name of the x25 access template entity used in making an outgoing call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o call direction Direction of the call on an SVC. incoming The call is an incoming call. outgoing The call is an outgoing call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o calling address extension Calling NSAP address that is carried transparently in an incoming or outgoing call packet. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o calling dte address Calling DTE address in a call request or incoming call packet (depending on the value of the status attribute call direction). This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o channel Channel number of the underlying virtual circuit. This status is valid only if the port is at a gateway system and the status attribute state is not open. o client Name of the entity that opened the port. o dte class Name of the DTE class to which the DTE of the underlying virtual circuit belongs. This attribute is supported only if the status attribute state is not set to Open. o fast select Specifies whether fast select is in operation for the call. fast select Fast select in operation. no fast select Fast select not in operation. not specified Facility not requested. with response Fast select with response in operation. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o group Name of the x25 protocol group entity (that is, CUG) associated with an incoming or outgoing call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o incoming packet size Packet size, in octets, for incoming data on a virtual circuit. This attribute is supported only if the status attribute state is not set to open. o incoming throughput class Throughput class for incoming data on a virtual circuit. o incoming window size Window size for incoming data on a virtual circuit. o local dte Name of the DTE entity associated with the call. o originally called address If a call is redirected, this is the DTE address from which the call was redirected; otherwise, the address is null. This status is valid only if the status attribute redirect reason is not [not] redirected. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o outgoing packet size Packet size, in octets, for outgoing data on a virtual circuit. This attribute is supported only if the status attribute state is not set to Open. o outgoing throughput class Throughput class for outgoing data on a virtual circuit. o outgoing window size Window size for outgoing data on a virtual circuit. This attribute is supported only if the status attribute state is not set to open. o protocol identifier First four octets of call data in the call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o pvc Name of the pvc to which this port belongs. This attribute is present only if the status attribute port type is set to permanent. o redirect reason Specifies whether a call has been redirected and, if so, the reason for the redirection. busy The call has been redirected because the original destination was busy. not redirected The call has not been redirected. out of order The call has been redirected because the original destination was not operational. systematic The call has been redirected because all calls to the original destination have been systematically redirected. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o remote port Port at the source (that is, accessing) node (when the client is an X.25 server). o reserved If the port is associated with a reserved Logical Channel Number (LCN), this specifies the name of the local DTE entity on which the LCN is reserved. A null string indicates that the port is not associated with a reserved LCN. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o reverse charging Specifies whether reverse charging is in operation for the call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o state Status of the x25 access port entity. called A call has been received and taken by a user. calling A user is making a call. cleared A Clear Indication or Clear Confirmation packet has been received, or the X.25 Protocol module has detected an error. cleared by The port was cleared by network management. directive clearing A user has requested that the call should be cleared. no communi- Communications with the PSDN have been lost. cation open The port is open. running The associated virtual circuit is available for data transfer. synchronizing A user has requested a reset, but the network has not yet responded with a Reset Confirmation or Reset Indication packet. unsynchronized A Reset Indication packet has been received, or the X.25 Protocol module has detected an error and the user has not yet responded with a reset request. o target address extension Called NSAP address that is transparently carried in an incoming or outgoing call packet. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o target dte address Called DTE address in a call request or incoming call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. o type Specifies that the port represents an SVC. switched The circuit is an SVC. permanent The circuit is a PVC. 3 reachable_address show [node node-id] x25 access - reachable address address-name attribute [,attribute...] all [attributes] all characteristics all identifiers Examples: show x25 access reachable address * name, address prefix show x25 access reachable address X121 all 4 Characteristics o address extensions Default: True Value: True or false Specifies whether the "called address extension" and "calling address extension" fields to be included in the outgoing call packet. o address prefix Address prefix to trigger the use of DTE class and destination. Supplied as an argument to the create command. You cannot modify this characteristic. o destination Default: No DTE address Value: DTE address Manually entered DTE address. This address is used only if the mapping characteristic has the value manual. o dte class Default: No class name Value: Class name Name of the DTE class to be used in making the outgoing call. If not specified, any DTE class may be used. o mapping Default: X.121 Value: Manual or X.121 Mechanism by which the destination DTE address is to be derived. manual The destination DTE address is supplied manually by means of the destination characteristic. X.121 The destination DTE address is derived by an algorithm from an NSAP address in X.121 format. X.121 address mapping may only be specified with address prefixes of 36, 37, 49, 52 and 53. 4 Identifier o name Simple name assigned to the reachable address when it is needed. 3 security_dte_class show [node node-id] x25 access - security dte class class-name attribute [,attribute...] all [attributes] all identifiers all status Examples: show x25 access security dte class * name show x25 access security dte class Default all 4 Identifier o name Simple name assigned to the security DTE class when it is created. 4 Status o guarded dte classes Names of the DTE classes that are protected by this security DTE class. 4 remote_dte show [node node-id] x25 access - security dte class class-name - remote dte dte-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers Examples: show x25 access security dte class Default - remote dte * name, rights identifiers show x25 access security dte class Default - remote dte remdte-0 all 5 Characteristics o acl Default: No acl Value: Access control list Access Control List (ACL) that is used when checking outbound calls to the set of DTE addresses that this remote DTE represents. Wildcards can be used in the identifiers that form part of each Access Control Entry (ACE) in an Access Control List (ACL). o remote address prefix DTE address prefix for this remote DTE. The value of this characteristic is specified by the remote address prefix argument in the create command. You cannot modify this characteristic. o rights identifiers Default: No rights identifiers Value: Set of names Rights identifiers possessed by this remote DTE. It is used for incoming call checking against the ACL attribute of a security filter entity that is used to guard a filter. 5 Counters o creation time Time at which the entity was created. o incoming calls blocked Number of times that an incoming call that matched the remote address prefix for this remote DTE has been blocked by security. o outgoing calls blocked Number of times that an outgoing call that matched the remote address prefix for this remote DTE has been blocked by security. 5 Identifier o name Simple name assigned to the remote DTE when it is created. 5 Status o uid Entity's unique identifier, which is generated when the entity is created. 3 security_filter show [node node-id] x25 access - security filter filter-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status Examples: show x25 access security filter * name, acl show x25 access security filter Default all 4 Characteristic o acl Default: No acl Value: Access control list Access control list that is used for checking inbound calls for all filters using this security filter. Wildcards can be used in the identifiers that form part of each Access Control Entry (ACE) in an Access Control List (ACL). 4 Identifier o name Simple name assigned to the security filter when it is created. 4 Status o guarded filters Names of the x25 access filters that are protected by this security filter. 3 template show [node node-id] x25 access - template template-name attribute [,attribute...] all [attributes] all characteristics all identifiers Examples: show x25 access template * name show x25 access template "OSI Transport" all 4 Characteristics o call data Default: No call user data Value: Hex string Call user data to be sent in the call. o calling address extension Default: No NSAP address Value: NSAP address Calling Network Service Access Point (NSAP) address is to be passed to a higher-level entity within the called DTE. A null address indicates that this facility is not included in the outgoing call. o charging information Default: False Value: True or false Specifies whether charging information is requested for this call. o destination dte address Default: No DTE address Value: DTE address Address of the remote DTE, including the remote subaddress (if any), to which the call is directed. o dte class Default: No DTE class name Value: Class name Name of the DTE class to be used for the call. o end-to-end delay Default: [0..0] Value: Range (see description) Lower and upper bounds of the acceptable end-to-end delay for the call. A zero value for either bound indicates that no range is included in the outgoing call. o expedited data Default: Not specified Value: See description Specifies whether expedited data is requested for the call. do not use Expedited data is not in use. not specified Expedited data is not requested. use Expedited data is in use. o fast select Default: Not specified Value: See description Specifies whether fast select is requested for the call. fast select Fast select is in use. no fast select Fast select is not in use. not specified Fast select is not requested. with response Fast select with response is in use. o local facilities Default: No facilities Value: Hex string Non-CCITT facilities that are available from the local PSDN. The string is placed in the outgoing call request packet without modification. The contents and interpretation of this string are implementation-dependent. o local subaddress Default: No DTE address Value: DTE address Local subaddress to be appended to the calling DTE address in the call. o network user identity Default: No network user identity Value: Hex string Network user identity to be included in the call packet. The format of the network user identity is specified by the PSDN administration. o nsap mapping Default: False Value: True or false Specifies whether an x25 access reachable address entity is used to map the supplied NSAP address to a destination DTE class/DTE address pair. o packet size Default: Supplied by profile Value: 0-4096 Packet size, in octets, for transmitted and received data packets. The value must be a power of 2 in the range 0 to 4096. The value zero indicates that no packet size is included in the outgoing call. o quality of service Default: No data Value: Hex string Quality of service data. The contents and interpretation of this string are implementation-dependent. o reverse charging Default: False Value: True or false Specifies whether reverse charging is requested for the call. o rpoa sequence Default: No DTE address Value: Set of DTE addresses Private Operating Agency sequence of transit networks to be used in setting up the call. Format the values to specify a set of DTE addresses. Each DTE address is four digits long. An empty set indicates that no sequence is included in the outgoing call. o selected group Default: No group name Value: Group name Name of the x25 protocol group entity that represents the CUG selected for the call. The index for group is included in the facility field of the call request packet. o target address extension Default: No NSAP address Value: NSAP address Called NSAP address to be sent to the called DTE should be supplied by a higher-level entity in the calling DTE. A null address indicates that this facility is not required. o throughput class request Default: [0..0] Value: Range (see the following description) Minimum acceptable throughput class (the lower bound of the range) and the target throughput class (the upper bound of the range) for a call. The only legal range values are as follows: 0 2400 75 4800 150 9600 300 19200 600 48000 1200 The range 0-0 indicates that no throughput class is included in the outgoing call. o transit delay selection Default: 0 Value: Integer Desired transit delay. A zero value indicates that no value is included in the outgoing call. o window size Default: Supplied by profile Value: 0-127 Window size for transmitted and received data packets. A zero value indicates that no window size is included in the outgoing call. 4 Identifier o name Name assigned to the template when it is created. 2 x25_client_(OpenVMS) show [node node-id] x25 client attribute [,attribute...] all [attributes] all characteristics all counters Example: show x25 client all 3 Characteristics o incoming session template The session control template specified for an open/incoming connection at the end-user session control interface. This characteristic is an optional argument on the create command. o maximum session connections Default: None Value: 1-65535 Maximum number of session control connections supported by this module. This characteristic is an optional argument on the create command. You cannot modify this characteristic. o version Default: Current version number Version number of the X.25 Gateway Access Protocol to which the implementation conforms. You cannot modify this characteristic. 3 Counters o connection attempts failed Number of session control connect requests that have failed prematurely or that have been rejected by the X.25 server at the gateway system. o creation time Time at which this entity was created. o times session control unavailable Number of times session control was not found or state of session control was not enabled. 3 Status o active inbound session connections Number of inbound session control connections to the X.25 Client module. o active outbound session connections Number of outbound session control connections to the X.25 Client module. o state Current state of the entity (on or off). o uid Entity's unique identifier, which is generated when the entity is created. 2 x25_protocol show [node node-id] x25 protocol version all [attributes] all characteristics 3 Characteristic o version Default: Current version number Version of DNA X.25 architecture to which this implementation conforms. You cannot modify this characteristic. 3 dte show [node node-id] x25 protocol - dte dte-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show x25 protocol dte * name, call timer show x25 protocol dte dte-0 all 4 Characteristics o call timer Default: Supplied by profile Value: Bounded by profile Elapsed time, in seconds, before which a clear packet is sent for outgoing calls from the DTE that have received no response. A zero value indicates that no clear is sent. o ccitt version Default: 1984 Value: 1-9999 Version of the CCITT X.25 recommendations to which the DTE conforms. o clear timer Default: Supplied by profile Value: Bounded by profile Value of the retransmit timer for outgoing clear packets from the DTE. The default value is profile dependent. o default packet size Default: 128 Value: 16-4096 raised to the power of 2 Default packet size, in octets, for all virtual circuits on the DTE. The value must not be less than the value of the minimum packet size characteristic. o default window size Default: 2 Value: 1-127 Default window size for all virtual circuits on the DTE; that is, the default number of unacknowledged packets. This value must not be greater than the value of the maximum window size characteristic, and must not be less than the value of the minimum window size characteristic. o description Manufacturer, product name and version of the hardware platform of the DTE. o extended packet sequencing Default: False Value: True or false Specifies whether the extended packet sequencing facility is subscribed to, in which modulo 128 packet numbering is used. If false, extended packet sequencing is not used. The profile may provide overriding default or legal values. o inbound dte class Default: No DTE class name Value: Simple-name Name of the DTE class to be associated with all incoming calls to the DTE. You must specify this characteristic before you enable the DTE. The x25 access dte class entity to which the name refers must exist when you enable the DTE. o incoming list Default: (0-4095) ranges Value: Set of range (0-4095) Channel number ranges that define the Logical Channel Numbers (LCNs) that are available for calls on incoming or bothway channels. Format the values to specify a set of channel number ranges. Each channel number is the concatenation of the logical channel group number and logical channel number of an SVC on the DTE. o interface type Default: DTE Value: See description Interface mode in which the packet protocol for the DTE will operate. You can modify this characteristic only when the entity is disabled. dce DCE mode. dte DTE mode. negotiated The interface mode is negotiated with the other end to be either DTE or DCE. This value applies only to point-to-point links. o interrupt timer Default: Supplied by profile Value: Bounded by profile Value of the interrupt timer. This timer is started when an interrupt packet is sent. If no interrupt confirmation packet is received before the timer expires, a reset is caused. A zero value indicates that there is no timer. o link service provider Default: No link service provider name Value: Full-name Name of the link service provider entity used by the DTE. You must give this characteristic a value before you enable the DTE. o maximum active circuits Default: 4096 Value: 1-4096 Maximum number of virtual circuits that can be active at any time on the DTE. This characteristic cannot be set. o maximum clear attempts Default: Supplied by profile Value: Bounded by profile Number of times that sending a clear packet can be attempted on a virtual circuit on the DTE. The value 1 indicates that a clear packet is sent only once; that is, there are no retries. o maximum packet size Default: 128 Value: 16-4096 raised to the power of 2 Maximum packet size, in octets, for all virtual circuits on the DTE. This value must be greater than or equal to the value of the minimum packet size and default packet size characteristics. o maximum reset attempts Default: Supplied by profile Value: Bounded by profile Number of times the DTE attempts to send a reset packet. The value 1 indicates that a reset packet is sent only once; that is, there are no retries. o maximum restart attempts Default: Supplied by profile Value: Bounded by profile Number of times that any virtual circuit on the DTE attempts to send a restart packet. The value 1 indicates that a restart packet is sent only once; that is, there are no retries. o maximum throughput class Default: 4800 Value: See description Maximum value for the throughput class (65535) of any virtual circuit on the DTE. The value specified must be one of the following: 0, 75, 150, 300, 600, 1200, 2400, 4800, 9600, 48000, or 64000. The value must be greater than or equal to the value of the minimum throughput class characteristic. o maximum window size Default: 2 Value: 1-127 Maximum number of unacknowledged packets for all virtual circuits on the DTE. This value must be greater than or equal to the value of the minimum window size and default window size characteristics. o minimum packet size Default: 128 Value: 16-4096 raised to the power of 2 Minimum packet size, in octets, for all virtual circuits on the DTE. This value must be less than or equal to the value of the maximum packet size and default packet size characteristics. o minimum throughput class Default: Supplied by profile Value: Bounded by profile Minimum throughput class for any virtual circuit on the DTE. The value specified must be one of the following: 0, 75, 150, 300, 600, 1200, 2400, 4800, 9600, 48000, or 64000. The value must be less than or equal to the value of the maximum throughput class characteristic. o minimum window size Default: 2 Value: 1-127 Minimum window size for all virtual circuits on the DTE. This value must be less than or equal to the value of the maximum window size characteristic. o outgoing list Default: [1...4095] Value: Set of range (0-4095) Channel number ranges that define the LCNs that are available for calls on outgoing or two-way channels. Format the values to specify a set of channel number ranges. Each channel number is the concatenation of the logical channel group number and logical channel number of an SVC on the DTE. o profile Default: No profile name Name of the profile that provides subscription details of the PSDN to which the DTE is connected. This characteristic cannot be set, it is specified when the DTE is created. o reset timer Default: Supplied by profile Value: Bounded by profile Value of the retransmit timer for outgoing reset packets from the DTE. The default value is profile-dependent. o restart timer Default: Supplied by profile Value: Bounded by profile Value of the retransmit timer for outgoing restart packets from the DTE. The default value is profile dependent. o segment size Segment size specified for data sent at this DTE. o x25 address Default: No DTE address Value: DTE-address Full address of the DTE. You must give this characteristic a value before you enable the DTE. 4 Counters o allocated pvc failures (OpenVMS) Number of times allocated PVCs have failed. o calls failed Number of outgoing or incoming calls on the DTE that were either rejected or were disconnected during the data phase. o creation time Time at which this entity was created. o data octets received Number of data octets received on all virtual circuits on the DTE. o data octets sent Number of data octets sent on all virtual circuits on the DTE. o data PDUs received Number of data packets received on all virtual circuits on the DTE. o data PDUs sent Number of data packets sent on all virtual circuits from the DTE. o diagnostic packets Number of diagnostic packets received on all virtual circuits on the DTE. o down transitions Number of times the status attribute state has changed from on to off, synchronizing, or unsynchronized. o fast selects received Number of Fast Select requests received at the DTE. o fast selects sent Number of Fast Select requests sent from the DTE. o illegal packets Number of illegal packets received at the DTE. o incoming calls connected Number of successful call requests received at the DTE. o locally initiated resets Number of times a reset was initiated by the local X.25 Protocol module. o locally initiated restarts Number of times a restart was initiated by the local X.25 Protocol module. o network initiated resets Number of times a reset was received. o network initiated restarts Number of times a restart was received. o outgoing calls connected Number of successful call requests sent from the DTE. o protocol errors Number of protocol errors detected at the DTE. o reject packets Number of reject packets received at the DTE. o retry failures One of the maximum retry counts has been reached. o up transitions Number of times the status attribute state has changed from off, synchronizing, or unsynchronized to on. 4 Identifier o name Simple name assigned to the DTE when it is created. 4 Status o available outgoing channels Number of LCNs enumerated by the outgoing list characteristic that are available for use. o dte class DTE classes to which the DTE belongs. o interface mode Mode in which the DTE is operating. o groups Groups to which the DTE belongs. o state Status of the x25 protocol dte entity. off The DTE is disabled, and all virtual circuits are terminated. running The DTE is enabled and synchronized at Protocol layer 3. synchronizing A restart operation initiated at the packet level is in progress. unsynchronized The line between the DTE and DCE is not synchronized at Protocol layer 2. o last state change Time at which the last change of state occurred. o uid Entity's unique identifier, which is generated when the entity is created. 4 pvc show [node node-id] x25 protocol - dte dte-name - pvc pvc-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show x25 protocol dte dte-1 pvc * name, channel show x25 protocol dte dte-1 pvc PVC-1 all 5 Characteristics o acl Default: No access Value: Access-control-list control list Access control list that controls access to this PVC. o channel Default: No default Value: 0-4095 Concatenated logical channel group and logical channel number for the PVC. The value of this characteristic derives from an argument to the create command. o packet size Default: No default Value: 16-4096 Packet size for the PVC, in octets. The value must be a power of 2 in the range 16 to 4096. The value of this characteristic derives from an argument to the create command. o window size Default: No default Value: 1-127 Window size for the PVC. The value of this characteristic derives from an argument to the create command. 5 Counters These counters record values over the lifetime of a PVC. For counters that refer to use of the PVC by individual clients, see the x25 access port entity. o accesses blocked Number of times an attempt to open a PVC has failed because of security. o creation time Time at which this entity was created. o data octets received Number of octets received by the PVC since it was created. o data octets sent Number of octets sent by the PVC since it was created. o data pdus received Number of data PDUs received by the PVC since it was created. o data pdus sent Number of data PDUs sent by the PVC since it was created. o pvc failures Number of times the PVC has failed while the entity has been allocated. 5 Identifier o name Simple name assigned to the PVC when it is created. 5 Status o allocated True if the PVC is allocated to a user. False if otherwise. o port X25 Access port with which the PVC is associated. o uid Entity's unique identifier, which is generated when the entity is created. 3 group show [node node-id] x25 protocol - group group-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show x25 protocol group * name, type show x25 protocol group GROUP-0 all 4 Characteristics o members Default: No DTEs Value: Set of records DTEs at a gateway system that make up the group. Format the values to specify a set of records. Each record consists of a name that identifies an X25 protocol dte entity and an integer (in the range 0 to 9999) that identifies the CUG number assigned by the network. If a DTE is already created and enabled and is then added to the set of members, it must be disabled and re- enabled to service the specified CUG number or BCUG. o remote dte address Default: No DTE address Value: DTE-address DTE address to be associated with this entity for matching x25 access security dte class remote dte entities for both incoming and outgoing calls. This characteristic is only supported if the characteristic type is bcug. o type Default: BCUG Value: CUG, BCUG, or CUGOA Type of the CUG. cug Normal CUG. bcug Bilateral CUG. cugoa CUG outgoing access. 4 Counters o creation time Time at which this entity was created. o incoming calls blocked Number of times that an incoming call to a bilateral CUG has been blocked by security from accessing a filter. o outgoing calls blocked Number of times that a call has been blocked by security from accessing this bilateral CUG. 4 Identifier o name Simple name assigned to the group when it is created. 4 Status o uid Entity's unique identifier, which is generated when the entity is created. 2 x25_relay_(Alpha) show [node node-id] x25 relay attribute [,attribute...] all [attributes] all characteristics 3 Characteristics o maximum active connections Maximum number of active connections supported by this module. This characteristic is an optional argument on the create command. You cannot modify this characteristic. o version Version number of the X.25 Relay architecture to which this implementation conforms. You cannot modify this attribute. 3 client show [node node-id] x25 relay - client client-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status 4 Characteristics o DTE class Default: No DTE class Value: Simple-name Name of the x25 access DTE class entity to use when making the outgoing call. o filters Default: No filters Value: Set of simple names Set of filters that are listened to by this client. Each name is the name of an x25 access filter entity. For the add and set commands, the x25 relay client entity must be in the Off state before the filters attribute can be modified. o rights identifiers Default: No rights identifiers Value: Set of simple names Set of rights identifiers that this client possesses. It is used when placing the outgoing call. o template Default: No template Value: Simple name Name of the x25 access template entity to be used for the outgoing call. 4 Counters o connections failed Number of times that a connection setup has failed. o connections lost Number of times that a successfully established connection has been abnormally terminated. o connections made Number of connections that have been made successfully. o creation time Time at which this entity was created. 4 Identifier o name Simple name assigned to the client when it is created. 4 Status o active connections Number of connections that are currently active on this client. A connection is a pair of incoming/outgoing calls. This value does not include connections that are still waiting to be established. o state Specifies the state of the x25 relay client entity. off The entity is disabled. on The entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created. 3 pvc show [node node-id] x25 relay - pvc pvc-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status 4 Characteristics o local PVC Default: No PVC name Value: Simple name Name of the PVC entity that represents the local end of the connection. o remote DTE class Default: No DTE class Value: Simple name DTE class to be used when setting up the remote end of the connection. It is only specified if the relayed PVC does not reside on the local system. This attribute is only applicable to connector nodes, and will not be visible in other implementations. o remote PVC Default: No PVC name Value: Simple-name Name of the PVC entity that represents the relayed end of the connection. o retry limit Default: 10 Value: 0-65535 Number of attempts that will be made to set up the PVC connection following the failure of an enable command. This attribute is only applicable to connector nodes, and will not be visible in other implementations. o retry timer Default: 60 Value: 1-65535 Interval, in seconds, between retries. This attribute is only applicable to connector nodes, and will not be visible in other implementations. o rights identifiers Default: No rights identifiers Value: Set of simple names Rights identifiers possessed by this entity. These rights are used to access the local PVC and relayed PVC if it resides on the local system. 4 Counters o connections made Number of successful connections made by this entity. o creation time Time at which this entity was created. o times connections lost Number of times that a successfully established PVC connection has been abnormally terminated. o times retry limit exceeded Number of times that the retry limit has been reached when trying to set up a PVC connection. 4 Identifier o name Simple name assigned to the PVC when it is created. 4 Status o state State of the x25 relay pvc entity. failed The retry mechanism has failed to set up the connection. off The PVC is disabled. on The PVC is enabled. retrying The Retry timer is running. o uid Entity's unique identifier, which is generated when the entity is created. 2 x25_server show [node node-id] x25 server attribute [,attribute...] all [attributes] all characteristics all counters all status 3 Characteristics o incoming session template (Tru64 UNIX) The Session Control template specified on an OpenIncoming invocation at the End User Session Control interface. You cannot modify this characteristic. o maximum session connections Default: 512 Value: [1..65535] Maximum number of session control connections with clients that the entity can support. This includes both incoming and outgoing connections. You cannot modify this characteristic. o version Default: Current version number Version number of the X.25 Gateway Access Protocol to which the implementation conforms. You cannot modify this characteristic. 3 Counters o connection attempts failed Number of session control connection requests to clients that have failed, due either to exceeding the maximum number of connections or rejection by X.25 clients in accessing systems. o creation time Time at which this entity was created. o times session control unavailable Number of times the session control unavailable event was raised. 3 Status o active inbound session connections Current number of active inbound session control connections with clients. o active outbound session connections Current number of active outbound session control connections with clients. o state Current state of the x25 server entity. off The x25 server entity is disabled. on The x25 server entity is enabled. o uid Specifies the entity's unique identifier, which is generated when the entity is created. 3 client show [node node-id] x25 server - client client-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status 4 Characteristics o account (OpenVMS) Default: No service/account data Value: String Default service or account data to be used when connecting to the system hosting the X.25 client. o application Default: 36 Value: End-user-specification Address information used by the destination Session Control module to select the X.25 client that will receive the connection request. o destination (OpenVMS) Default: No client name Value: Full-name Name of the X.25 client to which a connection is to be made when delivering a "filtered" call. o filters Default: No default Value: Set of simple names Set of filters to be used by the server to filter calls for this X.25 client. Each name is the name of an x25 access filter entity. o node Default: No node name Value: Full-name Name of the node that hosts the X.25 client to which connection is to be made. This characteristic is supported only if the service nodes characteristic is not supported. o outgoing session template (OpenVMS) Default: Default template Value: Simple-name Transport template to be used by the X.25 server to set up a session control connection to the X.25 client. The name is the name of an osi transport template entity. o password Default: No password Value: String Default password to be used for verification when connecting to the system that hosts the X.25 client. You cannot display this characteristic with the show command. o service nodes (Tru64 UNIX) Default: Empty set Value: Set of candidate records Set of nodes that host the x25 client entities to which connections can be made. o user Default: No user id Value: String Default user identification to be used in access verification when connecting to the system that hosts the X.25 client. 4 Identifier o name Simple name assigned to the client when it is created. 4 Status o state Status of the x25 server client entity. off The x25 server client entity is disabled. on The x25 server client entity is enabled. 3 security_nodes show [node node-id] x25 server - security nodes simple-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status 4 Characteristics o nodes Default: No node names Value: Set of full-name DNS full names of accessing systems, or the wildcard full name. o rights identifiers Default: No rights identifiers Value: Set of simple names Set of rights identifiers to be associated with the set of nodes named in the nodes characteristic for purposes of access control to DTE classes at the gateway node. 4 Counters o creation time Time at which this entity was created. o outgoing calls blocked Number of times that an attempt to establish a call or use a PVC has failed for security reasons. 4 Identifier o name Simple name assigned to the security node when it is created. 4 Status o uid Entity's unique identifier, which is generated when the entity is created. 2 xot_(OpenVMS_Alpha) Shows the X.25 Over TCP/IP module and its attributes. show [node node-id] xot attribute [,attribute...] all [attributes] all characteristics all status Examples: show xot currently active connections show xot maximum connections PORT and SAP are subentities of XOT. 3 Characteristics o version The version of the XOT implementation, initially "1.0.0". You cannot modify this characteristic. o maximum connections Default: 256 Value: 1-65535 The maximum number of connections allowed. Note that each XOT SAP LINK entity is limited to 4095 connections. The Maximum Connections attribute sets the limit for connections over all existing XOT SAP LINK entities. 3 Status o uid The universal identifier of the XOT module, which is generated when the entity is created. o currently active connections The number of currently active XOT connections, that is, the number of XOT PORTs. 3 port Shows a XOT PORT entity which provides information on an active XOT connection over TCP/IP. Ports are created and deleted dynamically as X.25 connections are requested. show [node node-id] xot - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status The port-name can be either a wildcard, or it can be a simple name that uniquely identifies a particular port instance. XOT port-names are automatically created in the form XOT-port-xxxx, where xxxx is a 4 digit hexadecimal value indicating the port number. Examples: show xot port * client, link, direction show xot port XOT-port-0000 all 4 Counters o creation time The time that the port entity was created. o octets received The number of data octets received from TCP/IP for the port. o octets sent The number of data octets sent to TCP/IP from the port. o pdus received The number of data PDUs (X.25 packets) received from TCP/IP. o pdus sent The number of data PDUs (X.25 packets) sent to TCP/IP. 4 Identifiers o name The simple name assigned to the port when it was created. It will consist of xot-port-xxxx, where xxxx is the hexadecimal representation of the connection id. 4 Status o client The client of the port, that is, the name of the X25 PROTOCOL DTE entity. o link The XOT SAP LINK entity with which this port is associated. o protocol state The state of the XOT protocol over this port: Idle The port is idle. Running The port is running. Connecting The entity is making an X.25 connection. Failed The port connection failed. o direction Whether the port is inbound or outbound. o type The type of X.25 connection: PVC or SVC. o uid The universal identifier of the PORT entity, which is generated when the entity is created. 3 sap Shows a XOT SAP entity which specifies the point at which the XOT entity gains access to the TCP/IP environment for the purposes of listening for inbound XOT connections. show [node node-id] xot - sap sap-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status The sap-name can be either a simple name that uniquely identifies a particular SAP instance, or a wildcard to identify multiple SAP instances. Examples: show xot sap * all show xot sap sap-0 local ip address, state LINK is a subentity of XOT SAP. 4 link Shows a XOT SAP LINK entity which represents a remote system with which XOT is allowed to communicate. show [node node-id] xot - sap sap-name link link-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status The sap-name must be a simple name which uniquely identifies a particular SAP instance. The link-name can be either a simple name that uniquely identifies a particular LINK instance, or a wildcard to identify multiple LINK instances. Examples: show xot sap sap-0 link * remote IP address, state show xot sap sap-0 link link-0 all 5 Characteristics o remote IP address Default: 0.0.0.0 Value: IP Address Specifies the remote IP address of the cooperating XOT system that implements RFC1613. The IP address is specified as a numeric address in the form a.b.c.d. o remote rfc1613 port number Default: 1998 Value: TCP port number Specifies the TCP port number to use for an outgoing connection. The remote system must be listening for inbound XOT connections on this port. 5 Counters o creation time The time that the XOT SAP LINK entity was created. o connects sent The number of connection requests sent. o connects received The number of connection requests received. o disconnects sent The number of disconnect requests sent. o disconnects received The number of disconnects received. o octets sent The number of data octets sent from TCP/IP for all ports on the link. o octets received The number of data octets received from TCP/IP for all ports on the link. o pdus sent The number of X.25 packets sent from TCP/IP for all ports on the link. o pdus received The number of X.25 packets received from TCP/IP for all ports on the link. o connects failed The number of times an attempt to establish an outgoing connection failed. o link state changed The number of times that the link has changed state from enabled to disabled or disabled to enabled. o protocol errors The number of protocol errors that occurred. 5 Identifiers o name The simple name assigned to the LINK entity when it was created. 5 Status o state The state of the LINK entity: On The LINK is enabled Off The LINK is disabled o uid The universal identifier of the LINK entity, which is generated when the entity is created. 4 Characteristics o local IP address Default: 0.0.0.0 Value: IP Address The IP interface (identified by the address) where the SAP entity will listen. Any available interface is specified with the address of 0.0.0.0. This characteristic is mainly set when a system has multiple TCP/IP interfaces. By default, XOT's single SAP entity is configured to listen on all available IP interfaces (as specified by the local IP address 0.0.0.0). You can create multiple SAP entities, each listening on a unique IP address. However, if you create more than one SAP entity, you must assign each entity a unique IP address; no SAP entity can use the 0.0.0.0 address. o local RFC1613 port number Default: 1998 Value: TCP port number The port number on which the SAP entity will listen for inbound XOT connections. HP strongly recommends that you use the value 1998 as specified in RFC1613. 4 Counters o creation time The time that the XOT SAP entity was created. o connections rejected The number of times an inbound connection was rejected. o sap state changed The number of times that the SAP entity state changed. 4 Identifiers o name The simple name assigned to the SAP entity when it was created. 4 Status o state The state of the SAP entity: On The entity is enabled. Off The entity is disabled. Connecting To PWIP The entity is connecting to TCP/IP. o uid The universal identifier of the SAP entity, which is generated when the entity is created.