If you want to operate on the local node, you can either omit the node identifier in your NCL command, or you can specify node 0, which identifies the local node.
enable
Turns on the node entity with or without the address watcher.rename
Changes the node's name within the node and does not affect the name server directly. It uses the new name and an immediate keep me here transaction with the name servers which then update themselves based on the node's new name.
function function
Specifies a function to disable or enable on the node. For the enable command, the function argument is optional. Specifying one, both, or neither has the effect of changing the state to on.
address watcher Enables the address watcher function. Enabling this function allows the node to update its address identifier when a change of address is detected. Disabling this function causes the state attribute to be set to off, but the node can still respond to management through its CMIP interface. The disable function is only supported on OpenVMS. CMIP listener Enabled automatically by the software. This function permits the node to respond to management through its CMIP listener interface. The CMIP listener function is only supported on Digital UNIX. new name full-name
Specifies the new name to be assigned to the node.
implementation
Particular DECnet implementation of the node. You cannot modify this characteristic.listener template (Digital UNIX)
Name of the OSI Transport template to be passed through the CMIP listener to Session Control. You cannot modify this characteristic.maximum listeners (Digital UNIX)
Maximum number of CMIP listeners that the node supports. Zero specifies an unlimited number of listeners. You cannot modify this characteristic.version
Version number of the network management architecture specification to which the implementation conforms. You cannot modify this characteristic.
changes of address
Number of times the node's address has changed.changes of id
Number of times the node's ID has changed.creation time
Time at which the entity was created. This time reflects the time at which the node was first booted.idrom check failures
Number of times an IDROM was checked for consistency and was found to be in error.renames
Number of times the node has been renamed (see the rename command).
address
Set of protocol towers that together form a Session Control application address for the node's CMIP listener.name
Full name of the node as it is registered in your namespace; name is the primary identifier.
functions enabled
Functions that are currently enabled for the node (see the enable command).id
Indicates the unique 48-bit ID of the node.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. This function is only supported on OpenVMS. dead The node is unusable and unmanageable as the result of a power failure or similar event. The node must be rebooted. This function is only supported on 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. uid
Node's unique identifier, which is generated when the node is created.
address changed
Generated each time the node address changes.Arguments:
old address Protocol tower set that constituted the old node address. new address Protocol tower set that constitutes the new node address. id changed
Generated each time the node's ID status attribute changes value.Arguments:
old id Node's old 48-bit ID. new id Node's new 48-bit ID. idrom check failure
Generated each time an IDROM was checked and failed the test.Arguments:
contents Value of the failed IDROM. owner Name of the device on which the failed IDROM address exists. renamed
Generated each time the node's name changes.Arguments:
old name Old full name of the node. new name New full name of the node.
For rename:
update of backtranslation soft links failed
Update of backtranslation soft links failed on the rename directive.update of new name failed
New name update has failed on the rename directive.unregistered name
The attempt to rename the node failed because the name and/or UID were not registered in DNS.
This chapter describes all the commands you can use to manage the entities that constitute the Alias module. The Alias module provides the means to define an alternate network address that is shared by multiple nodes in the same OpenVMS cluster. This makes it possible to treat an OpenVMS cluster, or several nodes within an OpenVMS cluster, as though it were a single node in the network.
The alias entity is the top-level entity in the hierarchy
belonging to the Alias module. The entity is the root from which
alias port subentities may be defined.
create [node node-id] alias
delete [node node-id] alias
show [node node-id] alias [all [attributes] |
all counters]
creation time
Specifies the time at which the entity was created.
For create:
already exists
An alias entity already exists.wrong node type
An alias entity cannot be created on an alias node.For delete:
module enabled
Disable the alias entity before trying to delete it.
The first node in the OpenVMS cluster to create an alias port for a particular alias address causes that alias to be created. Subsequent nodes that create an alias port for the same alias establish connections (ports) to that alias. The alias becomes active when the first node enables its alias port for that alias. The port-name refers to the port managed by this command.
Note
When a node enables an alias port, that node registers itself with other members of the alias.
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 OpenVMS cluster satellites 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.
creation time
Specifies the time at which the entity was created.
name
This string is the port identifier and is also the DECdns-registered node object name of the Alias psuedonode.
node-id
The 6-byte node-id field in the Alias pseudonode's NSAP.state
Specifies the status of the alias port entity.
off The alias port entity is enabled on The alias port entity is enabled
For create:
already exists
An alias port entity already exists.too many alias port entities
The maximum number of alias port entities has been exceeded.For delete:
cannot delete the entity while it is enabled
Disable the alias port entity before trying to delete it.
This chapter describes all the commands you can use to manage the entities that constitute the CSMA-CD module. A Carrier Sense Multiple Access with Collision Detection (CSMA-CD) local area network (LAN) provides high-speed communications channels for connecting computers and other digital devices located within a moderate-sized geographic area. Like other LANs, the CSMA-CD LAN falls between long-distance, low-speed networks that carry data for hundreds or thousands of kilometers, and specialized, high-speed intercommunications that are generally limited to tens of meters. The CSMA-CD LAN is intended for use primarily in such areas as office automation, distributed data processing, terminal access, distributed systems, and other situations that require economical connection to a local communication medium with sporadic traffic at high-peak data rates.
Figure 4-1 shows the hierarchical relationship of the entities that constitute the CSMA-CD module.
Figure 4-1 Hierarchy of CSMA-CD Module Entities
The Digital Network Architecture (DNA) CSMA-CD module incorporates the functions and operations defined in the Ethernet Specification Version 2.0 and the ISO 8802-3 (IEEE 802.3) CSMA-CD Access Method and Physical Layer specification as well as parts of the ISO 8802-1 (IEEE 802.1) Addressing, Internetworking, and Network Management and the ISO 8802-2 (IEEE 802.2) Logical Link Control specifications. To this, the DNA CSMA-CD module adds features often needed by users of the data link. A typical such data link user is the Network layer of the DNA. <>
The csma-cd entity is the top-level entity in the hierarchy of
entities belonging to the CSMA-CD module.
create [node node-id] csma-cd
delete [node node-id] csma-cd
show [node node-id] csma-cd [all [attributes]
| all characteristics]
version
Version number of the CSMA-CD data link architecture specification to which the implementation conforms. You cannot modify this characteristic.
Default: Current version number
For create:
already exists
A csma-cd entity already exists.For delete:
has children (Digital UNIX)
Cannot delete while subentities exist.cannot delete while subentities exist (OpenVMS)
Cannot delete while subentities exist.
Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers.
creation time
Time at which the port was created.multicast octets received
Number of multicast data octets that were received successfully 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 (media 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.multicast octets sent
Number of multicast data octets that were sent successfully 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.multicast pdus received
Number of multicast PDUs that were received successfully 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.multicast pdus sent
Number of multicast PDUs that were sent successfully 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.octets received
Total number of MAC user data octets that were received successfully 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.octets sent
Total number of user data octets that were sent successfully 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.pdus received
Total number of PDUs that were received successfully 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.pdus sent
Total number of PDUs that were sent successfully through the port. The count provides a gross measurement of outgoing CSMA-CD usage by the port.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.
name
Simple name assigned to the port when it is created.
client
Name specified by the data link user when the port was opened.ethernet protocol types
Set of Ethernet protocol types that are currently recognized for this port.length present
The data link adds a length field on transmit frames. It 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. llc sap addresses
Set of individual and group logical link control (LLC) service access point (SAP) addresses that are currently recognized for this port.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-supplied The user is responsible for handling the LLC protocol. mac addresses
Set of individual and multicast MAC (medium access control) addresses that are currently recognized for this port.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. snap protocol identifiers
Set of subnetwork access protocol (SNAP) identifiers that are currently recognized for this port.station
Name of the station associated with this port as specified by the user when the port was opened.uid
Entity's unique identifier, which is generated when the port is created.
communication port
The system device name assigned to this station.
![]()
The name must be in the format ddn, where dd is the Digital UNIX device name prefix and n is the device number.<>
![]()
The name must be in the format ddc, where dd is the OpenVMS device name prefix and c is the controller letter.<>
Device Type Digital UNIX OpenVMS DEBNA et DEBNI et DELQA xq DELUA xe DEMNA xna ex DESVA es DEUNA xe DE422 ln er KFE-32 ef LANCE ln PMAD ln ec SGEC ez TGEC te TULIP ew mac address
Individual medium access control (MAC) address for the station. If you do not specify a MAC address, the network uses the address specified in the first EnableMacAddress user interface call directed to this station.
station buffers
Number of receive buffers reserved for the station. You cannot modify this characteristic.
Default: 4 Value: 1--64
Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers.
alignment errors
Number of times a received frame did not contain an integral number of octets.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.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.creation time
Time at which the station was created.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.excessive collisions
Number of times a transmission failed because the maximum allowable number of retransmission attempts all culminated in collisions.frame check errors
Number of times a received frame containing an integral number of octets failed the frame check sequence (FCS).frame size errors
Number of times the user requested transmission of a frame outside the range of valid frame sizes.frames too long
Number of times a received frame exceeded the maximum length allowed by CSMA-CD medium access control.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.late collisions
Number of times a collision was detected after the allotted time for collisions had expired.multicast octets received
Number of multicast data octets that were received successfully. 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.multicast octets sent
Number of multicast data octets that were sent successfully. 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.multicast pdus received
Number of multicast PDUs that were received successfully. Comparing this count to the pdus received count yields a gross percentage of CSMA-CD usage for multicast PDUs received by this system.multicast pdus sent
Number of multicast PDUs that were sent successfully. Comparing this count to the pdus sent count yields a gross percentage of CSMA-CD usage for multicast PDUs sent by this system.multiple collisions pdus sent
Number of times a PDU was transmitted successfully 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.octets received
Total number of MAC user data octets that were received successfully 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.octets sent
Total number of user data octets that were sent successfully. 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.
Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]
![]()
NCL_PROFILE_003.HTML OSSG Documentation 2-DEC-1996 12:47:39.64Copyright © Digital Equipment Corporation 1996. All Rights Reserved.