% Librarian A09-30x@}h~5R CALCULATE<EXITHELP 8SET7SHOWjSTARTtSTOPs 1 CALCULATE= Calculates values you can use with SET commands to control: OpenVMS Cluster communications. Currently, this command> calculates the window size that can be used with the SET VCD /WINDOW=TRANSMIT_SIZE=value and SET VC /WINDOW=RECEIVE_SIZE=value commands.C Parameters for calculating other values might be added in future releases. Format CALCULATE Parameter 2 Parameters WINDOW_SIZEC Calculates a VC window size based on distance and aggregate line speed between two nodes. 2 Qualifiers /SPEED /SPEED=linespeedC Supplies the total speed in Megabits/Sec. of all LAN connections? between two nodes to be used in calculating the window size. /DISTANCE/ /DISTANCE=KILOMETERS [or =MILES]=distanceB Supplies the distance in kilometers or miles of the cable route? between two nodes to be used in calculating the window size. /OPTIMIZE) /OPTIMIZE=LOCKING [or =IO]=distance> Supplies the calculation with the type of intersite cluster- communications to be optimized as follows:? o LOCKING indicates that the window size is to be optimized= for lock messages that are relatively small, or for ICC? communications using message sizes of up to a few hundred bytes.C o IO indicates that the window size is to be optimized for MSCP@ served IO, or for ICC communications using large messages.  2 ExampleA SCACP> CALCULATE WINDOW_SIZE /SPEED=1000/DISTANCE=KILOMETERS=500A The command in this example calculates the window size to beD used between two nodes that are 500 kilometers apart, connectedA by a 1Gigabit/Second line speed. The command produces output similar to the following:6 Calculate Window Size 2-JUN-2006 17:49:18.41:@ Inter-node link DISTANCE: 500 KILOMETERS: Inter-node link SPEED: 1000 Mb/s A ------------------------ ------------------< Recommended WINDOW SIZE: 1024 framesC Note that the calculated window size is never smaller than theB window size PEdriver automatically selects for the VC between? two nodes, which is based solely on the reported local and? remote line speeds. However, the calculated value is often@ larger because it includes packets stored in the inter-site> link and the packet-size mix th at the /OPTIMIZE qualifier enforces. wws1 EXITB Stops execution of SCACP and returns control to the DCL command8 level. You can also enter Ctrl/Z at any time to exit. Format EXIT 2 Example SCACP> EXIT $A This command stops execution of SCACP and returns control to the DCL command level. wws1 HELPB The SCA Control Program (SCACP) is a cluster management utilityA that performs certa in privileged cluster management functions.? With SCACP, you can modify cluster operational parameters to> specify management characteristics of cluster communication? paths. You can look at status and counters that describe the; operational state of these cluster communications paths. Format HELP [topic] 2 Parameter topic? Specifies a subject for which you want information: an SCACP@ command or a command plus a command keyword. If you enter the A HELP command with a command name only, such as HELP SET, SCACPC displays a list of all of the command keywords used with the SET command. 2 Example SCACP> HELP SET TRACED The HELP command in this example displays information about the SET TRACE command. ww1 SET 2 CHANNELD Sets CHANNEL management parameters, currently limited to priority values.& NOTE9 If a LAN device/IP int erface is disabled for use by? cluster communications, all channels associated with thatB device/interface are deleted. This means that all managementB settings for that device and its associated channels will be deleted. Format SET CHANNEL nodename 3 Parameter nodename[,...]C Includes channels to specific nodes, which you can use wildcards< to specify. Each node name can be accompanied by optionalC qualifiers to specify local and r emote device names. If no localD or remote device name is specified, all channels to the specified node name are included.C Use the SHOW CHANNEL command to display node names and local and remote device names. 3 Qualifiers /EXCLUDE /EXCLUDE=(nodename[,...])C Excludes channels to specific nodes, which you can use wildcards< to specify. Each node name can be accompanied by optionalC qualifiers to specify local and remote device names. If no localC or remote device name is specified, all channels associated with# the specified node are included. /LOCAL_DEVICE9 /LOCAL_DEVICE=(landevicename/IPinterfacename[,...])D Specifies a LAN device/IP interface that identifies the local endB of the channel; you can use wildcards to specify LAN devices/IP interfaces.C Use the SHOW CHANNEL command to display node names and local andD remote device names, or use the SHOW LAN_DEVICE/SHOW IP_INTERFACE# command to display device names. /PRIORITY /PRIORITY=n> Sets the management priority value for channels to selectedB nodes. n can be a value between -128 and +127. Suggested values are:) 2 to cause channels to be preferred -2 to exclude channels& NOTE: Starting with OpenVMS Version 7.3-2, a channel whose> priority is -128 is not used for cluster communications.@ The priority of a LAN channel is the sum of the management? priority assigned to the local LAN device and the channel@ itself. Similarly the priority of IP channel is the sum of@ the management priority assigned to local IP interface and? channel itself. Therefore, you can assign any combination@ of channel and LAN/IP device management priority values to achieve a total of -128.' CAUTIONB If you set the priority of all channels to -128, you totally? disable use of the LAN/IP for cluster communication. This& can cause the system to CLUEXIT. /REMOTE_DEVICE: /REMOTE_DEVICE=(landevicename/IPinterfacename[,...])A Specifies a LAN device/IP interface that identifies the remote> end of the channel; you can use wildcards to specify LAN/IP devices.C Use the SHOW CHANNEL command to display node names and local andD remote device names, or use the SHOW LAN_DEVICE/SHOW IP_INTERFACE# command to display device names.B Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command on the remote' node to display remote device names. 3 Example$ SCACP> SET CHANNEL/PRIORITY=3 NODE5D The command in this example sets the priorities of all channels to node NODE5 to 3. 2 CIRCUIT. Sets the circuit management priority value.& NOTE@ If a circuit is closed, it is deleted. This means that the? management settings for that circuit are also deleted. If@  the circuit is opened again, it has the default values for its management settings. Format SET CIRCUIT nodename 3 Parameter nodename[,...]? Names a circuit or circuits to specific nodes, which you can@ use wildcards to specify. You can qualify each node name with? additional parameters to uniquely identify a single circuit. 3 Qualifiers /EXCLUDE< /EXCLUDE=(nodename[/PORT=portname[/RSTATION=n]][,...])B Allows you to exclude a specific circuit to a node. If multiple= circuits to the same node exist, you can use the /PORT and9 /RSTATION qualifiers to uniquely identify the circuit. /PORT! /PORT=portname[/RSTATION=n]? If multiple circuits to the same node exist, you can use theC /PORT and /RSTATION qualifiers to uniquely identify the circuit.C You can use the /RSTATION qualifier only in conjunction with the /PORT qualifier. 3 Example- SCACP> SET CIRCUIT CLUIO1 /PORT=PIB0 /PRI=10A The command in this example sets the priority of the circuitA to node CLUIO1 through PIB0 to 10. You need to use the /PORTA qualifier if multiple circuits to node CLUI01 exist and onlyC the circuit through PIB0 is meant to have its priority raised. 2 IP_INTERFACE3 Sets IP interface management priority parameter. Format" SET IP_INTERFACE ipinterface 3 Parameter ipinterface[,...]@ Includes one or more specific IP interface, which you can use wildcards to specify.< o Use the /EXCLUDE qualifier to exclude an IP interface.@ o Use the SHOW IP_INTERFACE command to display device names. 3 Qualifiers /EXCLUDE# /EXCLUDE=(ipinterface1[,...])? Excludes one or more specific IP interface which you can use wildcards to specify. /PRIORITY /PRIORITY=nD Sets the management priority value for the selected interfaces. n> can be a value between -128 and +127. Suggested values are:( o 2 to cause devices to be preferred o -2 to exclude devices& NOTE: Starting with OpenVMS Version 7.3-2, a channel whose> priority is -128 is not used for cluster communications.< The priority of a channel is the sum of the management; priority assigned to the IP interface and the channelB itself. Therefore, you can assign any combination of channel> and IP interface management priority values to achieve a total of -128.' CAUTIONA If you set the priority of all devices to -128, you totally? disable use of the IP for cluster communication. This can" cause the system to CLUEXIT. 3 Example' SCACP> SET IP_INTERFACE/PRIORITY=3 WE0A The command in this example sets the management priority for device WE0 to 3. 2 LAN_DEVICE- Sets device management priority parameter. Format"  SET LAN_DEVICE landevicename 3 Parameter landevicename[...,]@ Includes specific LAN devices, which you can use wildcards to specify.5 Use the /EXCLUDE qualifier to exclude LAN devices.; Use the SHOW LAN_DEVICE command to display device names. 3 Qualifiers /EXCLUDE% /EXCLUDE=(landevicename1[,...])? Excludes one or more specific LAN devices, which you can use wildcards to specify. /PRIORITY /PRIORITY=nA S ets the management priority value for the selected devices. n> can be a value between -128 and +127. Suggested values are:( o 2 to cause devices to be preferred o -2 to exclude devices& NOTE: Starting with OpenVMS Version 7.3-2, a channel whoseB priority is -128 is not used for cluster communications. TheA priority of a channel is the sum of the management priority> assigned to the local LAN device and the channel itself.> Therefore, you can assign any combination of channel andA LAN device management priority values to achieve a total of -128.' CAUTIONA If you set the priority of all devices to -128, you totally@ disable use of the LAN for cluster communication. This can" cause the system to CLUEXIT. 3 Example% SCACP> SET LAN_DEVICE/PRIORITY=3 EWAA The command in this example sets the management priority for device #EWA to 3. 2 PORT) Sets a port management priority value. Format SET PORT portname 3 Parameter portname[,...]@ Specifies SCA port names, in which you can include wildcards.8 Use the /EXCLUDE qualifier to exclude specific ports.C Use the SHOW PORT command to display all ports available on your system. 3 Qualifiers /EXCLUDE /EXCLUDE=(portname[,...]). Excludes specific ports from the operation. /PRIORITY /PRIORITY=nC Sets the management priority value for the selected ports. n can& be any value between -128 and +127. 3 Examples$ 1.SCACP> SET PORT PEA0/PRIORITY=5A The command in this example sets the management priority for the PEA0 port to 5.3 2.SCACP> SET PORT PEA0 /PRIORITY=5 /EXCLUDE=PEA0B The command in this example sets all ports with the exception+ of PEA0 to a management priority of 5. 2 TRACE: SET TRACE sets or modifies PEdriver tracing parameters.& NOTEA This command is reserved for use by HP Services and OpenVMS@ Engineering only. Trace commands and output are subject to% change from release to release. Format SET TRACE nodename 3 Parameter nodename[,...]= Includes channels and VCs to specific nodes, which you canA use wildcards to specify. Each node name can be accompanied by@ optional qualifiers to specify local and remote device names.? If no local or remote device name is specified, all channelsB associated with the specified node are included, as well as the VC to the specified node.C Use the SHOW CHANNEL command to display node names and local and remote device names. 3 Qualifiers /AFTER /AFTER=n> After the trace stop condition has been satisfied, continue= tracing for n events, and then stop. If you do not specify@ /AFTER, tracing does no t continue after the trace stop event., n can be any value between 0 and FFFFFFF. /DEFAULTB Sets the trace context back to the default settings, which are:$ trace all channels and VCs /AFTER=0! /EVENT=default settings /STOP /SIZE=512 /EVENT /EVENT=(event1[,...])B Enables tracing on specific events, which you can use wildcardsD to specify. The default is a subset of the events, which includesB most erro!rs and state changes when the system parameter SYSTEM_? CHECK is set to 0. The default is "all events included" when SYSTEM_CHECK is set to 1.= Use the SHOW TRACE/CONTEXT command to display event names. /EXCLUDE /EXCLUDE=(nodename[/LOCAL_+ DEVICE=landevicename/ipinterfacename]: [/REMOTEDEVICE=landevicename/ipinterfacename][,...])B Excludes VCs or channels, or both, to specific nodes, which youB can use wildcards to specify. Each node name can be accom"paniedC by optional qualifiers to specify local and remote device names.A If no local or remote device name is specified, the VC and all< channels associated with the specified node are excluded. /LOCAL_DEVICE9 /LOCAL_DEVICE=(landevicename/ipinterfacename[,...])C Includes specific LAN devices that identify the local end of the9 channel. You can use wildcards to specify LAN devices. /REMOTE_DEVICE: /REMOTE_DEVICE=(landevicename/ipinterfacename[,...])#D Includes specific LAN devices that identify the remote end of the9 channel; you can use wildcards to specify LAN devices.; Use the SHOW LAN_DEVICE command to display device names. /STOP /STOP=(event1[,...])C Stops tracing on specific events, which you can use wildcards to0 specify. The default is "no events included."= Use the SHOW TRACE/CONTEXT command to display event names. /SIZE /SIZE=nB Specifies a trace buffer size of n byte$s to be used by PEdriverC for each trace buffer: one for global PEdriver use, one for each? selected channel, and one for each selected VC. n can be any value between 0 and FFFFFFF. 3 Examples. 1.SCACP> SET TRACE/EVENT=CC_STATE/SIZE=1000A The command in this example specifies that the trace buffersC for each channel, VC, and the global buffer each be 1000 bytes in length.5 2.SCACP> SET TRACE/EVENT=* NODE10/LOCAL=EWA,NODE20D The command in th %is example specifies that all events are to beB recorded; when applicable to a particular node, however, onlyD channels and VCs to nodes NODE10 and NODE20 are to be included.0 3.SCACP> SET TRACE/EVENT=(ALL,NOTIMER) NODE10A The command in this example specifies that all events except4 timer events on node NODE10 are to be included. 2 VC< Sets values for the virtual circuit management parametersC (checksumming, compression, ECS delay threshold, transmit window&) size, and receive window size values). Format SET VC nodename 3 Parameter nodename[,...]A Includes VCs to specific nodes, which you can use wildcards to specify.? Use the /EXCLUDE qualifier to exclude VCs to specific nodes.? Use the SHOW CHANNEL or SHOW VC command to display VC names,. which are simply the names of remote nodes. 3 Qualifiers /CHECKSUMMING /CHECKSUMMING /NOCHECKSUMMINGC Enables or di'sables checksum verification on the selected VCs to the specified nodes.C You can use this command alone or in combination with the systemD parameter NISCS_PORT_SERV. (For more information, see online help for NISCS_PORT_SERV.)D Note that the the SET VC/CHECKSUMMING setting is not valid beyondC the life of the system. Therefore, you might want to include SETB VC/CHECKSUMMING commands in your startup file, or reissue these commands at the next boot. /COMPRESSI(ON /COMPRESSION /NOCOMPRESSIOND Enables or disables sending compressed data by the specified VCs.! The default is /NOCOMPRESSION. Usage notes:A o Compression is used only if the partner node has a PEdriver version that supports it.@ o You can also enable the use of compression with the NISCS_C PORT_SERV system parameter. For more information about NISCS_B PORT_SERV, see the System Parameter appendix in this manual.@ o The /NOCOMPR)ESSION qualifier does not override compression2 enabled by setting bit 2 of NISCS_PORT_SERV. /ECS_MAX_DELAY /ECS_MAX_DELAY=n /NOECS_MAX_DELAYC Sets a management-specified lower bound on the maximum delay (inD microseconds) an ECS member channel can have. The value for n canB be any value between 0 and 3000000. /NOECS_MAX_DELAY disables a" prior management delay setting.B You can use this command to override the PEdriver automatically? calculated dela *y thresholds to ensure that all channels with@ delays less than the value supplied for n are included in the VC's ECS.D The command operates as follows: Whenever at least one tight peerB channel has a delay of less than the management-supplied value,@ all tight peer channels with delays less than the management-A supplied value are automatically included in the ECS. When all? tight peer channels have delays equal to or greater than the> management setting, the ECS members +hip delay thresholds areD automatically calculated and used. The /NOECS_MAX_DELAY qualifierD disables management control by setting the management delay value to zero.D You must determine an appropriate value for your configuration byB experimentation. An initial value of 2000 (2 ms) to 5000 (5 ms) is suggested.' CAUTION9 By overriding the automatic delay calculations, you= can include a channel in the ECS whose average delay is ,@ consistently greater than 1.5 to 2 times the average delay< of the fastest channels. When this occurs, the overall? VC throughput becomes the speed of the slowest ECS member channel.? An extreme example is when the management delay permits aB 10 Mb/s Ethernet channel to be included with multiple 1 Gb/s= channels. The resultant VC throughput drops to 10 Mb/s.A Note that the SET VC/ECS_MAX_DELAY setting is not valid beyondC the life of the syste-m. Therefore, you might want to include SETB VC/ECS_MAX_DELAY commands in your startup file or reissue these commands at the next boot. /EXCLUDE /EXCLUDE=(nodename[,...])A Excludes VCs to specific nodes, which you can use wildcards to specify. /WINDOW /WINDOW=RECEIVE=n /WINDOW=NORECEIVE@ Sets a management-specified upper bound on the receive windowB size (that is, the number of out-of-order packets this VC holdsD in its resequen.cing cache while awaiting the next in-order packet or packets).; You can use this qualifier to override the automatically? calculated receive window size. This ensures that the VC hasB enough buffering to receive the expected maximum number of out- of-order packets. Usage notes:: o The window size value n must be an exact power of 2.A Never use settings that cause the receive window of a VC to> be smaller than the transmit window of the partner node.< / Otherwise, the partner can send packets that cannot be? cached when a packet is lost. This results in unnecessary> retransmissions, and might cause channels not to be used> because they become "lossy." This leads to the remaining restrictions listed.D o Always decrease the receive window size of a VC's partner node3 before decreasing a VC's receive window size.C HP recommends using SYSMAN to decrease both the local and theA remote VC transmit 0 window sizes before increasing the local@ and remote receive window sizes (as shown in the example).D o Always increase the receive window size of a VC's partner node4 before increasing a VC's transmit window size.C HP recommends using SYSMAN to increase both the local and theD remote VC receive window sizes before increasing the local and# remote transmit window sizes.? o Whenever you enter the SET VC/WINDOW=RECEIVE command, the* following sequen1ce of events occurs:8 1. The VC's current resequencing cache is emptied.D 2. The VC partner node automatically retransmits any discarded packets.? 3. As a result of 2, the VC and channel retransmit counts increase.D 4. A few messages similar to the following might be displayed,D indicating that one or more channels has temporarily become "lossy":G %PEA0, Excessive packet losses on LAN Path from EWA to EWC' 2 on REMOTE NODE STAR= 5. The partner node recovers automatically within a few seconds.D o You can use the SCACP> CALCULATE WINDOW_SIZE command to assist? you in selecting the size to use for transmit and receive windows. /WINDOW /WINDOW=TRANSMIT=n /WINDOW=NOTRANSMITA Sets a management-specified upper bound on the transmit windowB size (that is, the number of out-of-order packets this VC sendsB while awaiting ackn 3owledgment of the transmitted packets) to n.D The /WINDOW=NOTRANSMIT qualifier resumes automatic control of theA window size and changes the management transmit window size to zero.= You can use the /WINDOW=TRANSMIT qualifier to override theC automatically calculated transmit window size to ensure that theD VC has enough buffering to receive the expected maximum number of out-of-order packets. Usage notes:: o The window size value n must be an exact power of 2. 4A Never use settings that cause the receive window of a VC to> be smaller than the transmit window of the partner node.< Otherwise, the partner can send packets that cannot be? cached when a packet is lost. This results in unnecessary> retransmissions, and might cause channels not to be used> because they become "lossy". This leads to the following restrictions.@ o Always decrease the transmit window size of a VC's partner8 node before decrea 5sing a VC's receive window size.C HP recommends using SYSMAN to decrease both the local and theA remote VC transmit window sizes before increasing the local& and remote receive window sizes.D o Always increase the receive window size of a VC's partner node4 before increasing a VC's transmit window size.C HP recommends using SYSMAN to increase both the local and theD remote VC receive window sizes before increasing the local and= remote transmit wi6ndow sizes (as shown in the example).C o You can use the SCACP CALCULATE WINDOW_SIZE command to assistC you in selecting the size to be used for transmit and receive windows. 3 Examples 1. $RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENV/NODE=LARRY1 DO MC SCACP SET VC LARRY/WINDOW=TRANSMIT=16 SET ENV/NODE=CURLY1 DO MC SCACP SET VC CURLY/WINDOW=TRANSMIT=16 SET ENV/NODE=LARRY0 DO MC SCACP SET VC LARRY/WINDOW=RECEIVE=16 SET ENV/NO7DE=CURLY0 DO MC SCACP SET VC CURLY/WINDOW=RECEIVE=16 EXITA This example shows how to decrease window size. The transmitD and receive window sizes are 32 on both nodes, and the commandsA decrease the window size for the VC between LARRY and CURLY.1 (You can enter the commands on either node.) 2. $RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENV/NODE=LARRY0 DO MC SCACP SET VC LARRY/WINDOW=RECEIVE=64 SET ENV/NODE=CURLY0 DO MC SCACP SET VC CURLY/W8INDOW=RECEIVE=64 SET ENV/NODE=LARRY1 DO MC SCACP SET VC LARRY/WINDOW=TRANSMIT=64 SET ENV/NODE=CURLY1 DO MC SCACP SET VC CURLY/WINDOW=TRANSMIT=64 EXITA This example shows how to increase window size. The transmitD and receive window sizes are 32 on both nodes, and the commandsA increase the window size for the VC between LARRY and CURLY.1 (You can enter the commands on either node.) wwŌ1 SHOW 2 CHANNELA 9 Displays PEdriver channel information for specific nodes. Each> channel is a single NISCA communications path between a LAN@ device on a local system and a LAN device on a remote system.C Use the SHOW CHANNEL command to display node names and local and remote device names. Format SHOW CHANNEL nodename 3 Parameter nodename[,...]C Includes channels to specific nodes, which you can use wildcards< to specify. Each node name can be accompanied by :optionalC qualifiers to specify local and remote device names. If no localC or remote device name is specified, all channels associated with( the specified node name are included. 3 Qualifiers /ALL Includes all channel data. /COUNTERS" Includes channel counters data. /ECS /ECS /NOECSC Includes only channels that are (or are not) members of the ECS. /EXCLUDE /EXCLUDE=(nodename[,...])C Excludes channels to ;specific nodes, which you can use wildcards< to specify. Each node name can be accompanied by optionalC qualifiers to specify local and remote device names. If no localC or remote device name is specified, all channels associated with# the specified node are included. /INTERVALD For the /COUNTERS display, displays the changes to counters since the last SHOW command. /LOCAL_DEVICE9 /LOCAL_DEVICE=(landevicename/IPinterfacename[,...])C Includes spec<ific LAN devices that identify the local end of the9 channel; you can use wildcards to specify LAN devices.; Use the SHOW LAN_DEVICE command to display device names. /nD Displays the nth page. To select a particular page of a multipage? display, specify the number of the page you want to display. /OUTPUT /OUTPUT=filespec7 Creates the specified file and directs output to it. /REMOTE_DEVICE: /REMOTE_DEVICE=(landevicename/IPinterfacename[,.=..])@ Includes specific LAN devices/IP interfaces that identify theB remote end of the channel; you can use wildcards to specify LAN devices/IP interfaces.; Use the SHOW LAN_DEVICE command to display device names. /SDAC Includes channel data displayed in SDA format, with all the data, collected in one display for one channel. /SUMMARY> Includes channel summary data. This is the default if /ALL,4 /COUNTERS, and /SDA qualifiers are not specified. >3 Examples) 1.SCACP> SHOW CHANNEL NODE20/LOCAL=EWAA The command in this example displays channel definition data? for all nodes defined with local device EWA and any remote6 device and remote node name starting with NODE20.* 2.SCACP> SHOW CHANNEL/COUNTERS/INTERVAL SCACP> SPAWN WAIT 0:0:10* SCACP> SHOW CHANNEL/COUNTERS/INTERVAL@ The first command in this example displays channel countersA since the last SHOW command. The SPAWN command tells the DC?L> WAIT command to insert a 10-second delay. The second SHOWB CHANNEL command displays counters after the 10-second period. 3.SCACP> SHOW CHANNEL/1/3C The command in this example displays the first and third pages> of data for all channels. The first page contains ChannelA Summary data, and the third page contains Channel Equivalent Channel Set (ECS) data. 4.SCACP> SHOW CHANNEL/ALLC The following is a snapshot of the output for SHOW CHANNEL/ALL @ command. 9 Channel Error Data describes the channel error data. Table 1 Channel Error Data Data DescriptionA Seq Number of times a sequenced VC packet sent onC Retransmit this channel was retransmitted, and the channel6 was penalized for the lost packet.> Note that the sequential retransmit is not? necessarily a reflection of lost packet. ItB is posAsible that there can be a PE which couldC have triggered a retransmitted and results in aB duplicate packet to be sent. This is reflectedB in the number of duplicate packets received inA the remote node. The XMIT:REXMT ratio is alsoA a measure of for how many transmitted packet,@ a packet was retransmitted. A very low value@ (less than 1000) reflects a possible B network congestion.A LAN Transmit Number of times the local LAN device reportedC Failures a failure to transmit a packet, and channel was2 penalized for the lost packet.C Restart Close or restart because channel control packetA Channel received indicating that the other end closed= the channel and is restarting the channel handshake.= Channel Init Channel initializa Ction handshake timeout. TimeoutsB Listen No packets of any kind, including HELLOs, were7 Timeouts received in LISTEN_TIMEOUT seconds.A Bad Received a Channel Control (CC) packet with a, Authorization bad authorization field. MsgC Bad ECO CC Received a CC packet with an incompatible NISCA2 Msg protocol ECO rev. field value.7 Bad Received a bad multicast CC packet. Multicast Msg8 CC DShort Received a CC packet that was short. PacketC CC Received a CC packet that was incompatible with? Incompatible existing channels for this virtual circuit.? Rcv Old Received a packet from an old instance of a Channel channel.< No MSCP No MSCP server available to respond to aC Server received channel control solicit service packet@ asking this node to boot serve another node.6 Disk NoEt Disk is not served by this system. Served* Buffer Size Change in buffer size. Change 5.SCACP> SHOW CHANNEL/ECSC The following is a snapshot of the output for SHOW CHANNEL/ECS command.1 ECS State Channel ECS Membership InformationC OpenVMS uses multiple interfaces to communicate with any otherB node in order to do load balancing of communication. However,A at a given time not all interfaces that link the remote node? aFre used to transmit datagrams. OpenVMS maintains a set ofB equivalent channels ECS (Equivalent Channel Set) within a VC.> These channels have approximately equivalent transmission> quality at a given time. Only the channels within the ECSA are used to transmit datagrams to the given node. "A" is the> generic format above may be "Y" (Yes) or "N" (No) stating< whether the channel is in the ECS or not. The remaining> characters specify the quality of the channel as thGey areC derived from the channel performance data. The characters are:$ o A: T or L for Tight or Lossy> o B: P, S, I, U for Peer, Superior, Inferior or Ungraded" o C: F or S for Fast or Slow@ For more details about ECS, see the section NISCA Transport@ Protocol Channel Selection and Congestion Control in the HP$ OpenVMS Cluster Systems manual.& NOTE> From OpenVMS Version 8.3 onwards, Topology change column< H from SHOW CHANNEL/FULL or /5 has been removed. This is> because you must not consider this as an 'error' instead? it is the count of failovers from one interconnect to the= other interconnect. Whenever failover occurs to another? interconnect the buffer size changes. Hence this topology> change is counted under "Buffer SizeDecr" column in SHOW VC/FULL output.: You can view the IP channel data summary by using the' /IPCHANNEL qualifier, for exampleI:* $ SHOW CHANNEL /IPCHANNEL; You can view the LAN channel data summary by using the( /LANCHANNEL qualifier, for example: $ SHOW CHANNEL/LANCHANNEL 2 CIRCUITA Displays SCA circuit information. You can further qualify each? node name you specify with additional parameters to uniquely identify a single circuit. Format SHOW CIRCUIT nodename 3 Parameter nodename[,...]D Includes specific circuits to individJual nodes, which you can use wildcards to specify. 3 Qualifiers /EXCLUDE< /EXCLUDE=(nodename[/PORT=portname[/RSTATION=n]][,...])B Allows you to exclude a specific circuit to a node. If multiple= circuits to the same node exist, you can use the /PORT and9 /RSTATION qualifiers to uniquely identify the circuit. /PORT! /PORT=portname[/RSTATION=n]? If multiple circuits to the same node exist, you can use theC /PORT and /RSTATION qualifiers Kto uniquely identify the circuit.C You can use the /RSTATION qualifier only in conjunction with the /PORT qualifier. 3 Example SCACP>SHOW CIRCUITD The command in this example displays all circuits to nodes over port PEA0.5 Circuit data for CLUIO2 at 07-DEC 11:55:31.80E Node Port Priority Load Remote RemoteD Name Name Cur Mgt Class State Station TypeH -------- -------- ---- ---- --------L -------- ------- --------F LYNX03 PEA0 0 0 10 Open dc NIF CLUIO1 PEA0 0 0 10 Open dd NIF PRMMC2 PEA0 0 0 10 Open de NIF RXBOT1 PIB0 5 0 48 Open 4 RF72F RXTOP1 PIB0 5 0 48 Open 1 RF73F RXTOP0 PIB0 5 0 48 Open 0 RF73F CLUIO1 PIB0 5 0 48 M Open 7 N710F R4JC3I PIC0 5 0 48 Open 7 RF73F R4HLEK PIC0 5 0 48 Open 5 RF73F R4XEWM PIC0 5 0 48 Open 3 RF73F R4A1FN PIC0 5 0 48 Open 2 RF73F R4XSVE PIC0 5 0 48 Open 4 RF73F R4VLNI PIC0 5 0 48 Open 1 RF73  SCACP>SHOW CIRCUIT* /PORT=PEA0B N This SHOW CIRCUIT command displays all circuits to all nodes.5 Circuit data for CLUIO2 at 07-DEC 12:42:23.03D Node Port Priority Load Remote_PortE Name Name State Cur Mgt Class Number TypeH -------- -------- -------- ---- ---- -------- ------- --------F LYNX03 PEA0 Open 0 0 100 dc NIF CLUIO1 PEA0 Open 0 0 10 dd NIF PRMMC2 PEAO0 Open 0 0 10 de NI 2 IP_INTERFACE> Displays the PEdriver device IP interface data. Each device@ is an IP interface on the system, which can be used for NISCA communications. Format# SHOW IP_INTERFACE ipinterface 3 Parameter ipinterfacename[,...]? Includes one of more specific IP interface which you can use wildcards to specify.: o Use the /EXCLUDE qualifier to exclude IP interfaces.@ o Use the SHOW!P IP_INTERFACE command to display device names. 3 Qualifiers /ALL" Includes all IP interface data. /COUNTERSD Includes device counter data maintained by PEdriver and counters. /EXCLUDE$ /EXCLUDE=(IP_INTERFACES[,...])? Excludes specific IP devices, which you can use wildcards to specify. /INTERVALD For the /COUNTERS display, displays the changes to counters since the last SHOW command. /nD Displays the nth page. ToQ select a particular page of a multipage? display, specify the number of the page you want to display. /OUTPUT /OUTPUT=filespec7 Creates the specified file and directs output to it. /SDAB Includes IP interface data displayed in the SDA format with all9 the data collected in one display for an IP interface. /SUMMARYC Includes IP interface summary data. This is the default if /ALL,4 /COUNTERS, and /SDA qualifiers are not specified. 3 ExaRmple SCACP>SHOW IP_INTERFACE/ALL; The following is a snapshot of the output for SHOW IP_ INTERFACE/ALL command.! SCACP>SHOW IP_INTERFACE/COUNTERS$ Displays IP interface counters.@ IP or LAN Device Error Data describes the IP/LAN device error data.& Table 2 IP or LAN Device Error Data! Data DescriptionC Bad SCSSYSTEM ID Received a packet with the wrong SCSSYSTEM ID in it.A MC Msgs Directed Number of mult Sicast packets directed to the, to TR Layer NISCA Transport layer.> Short CC Messages Number of packets received were short to= Received contain a NISCA channel control header.> Short DX Messages Number of packets received were short toA Received contain a NISCA DX header for a LAN device.C CH Allocation Number of times the system failed to allocate> Failures memory for use as a channel structure in? response to Ta packet received by this LAN device.C VC Allocation Number of times the system failed to allocateB Failures memory for use as a VC structure in responseD to a packet received by this LAN or IP device.D Wrong Port Number of packets addressed to the wrong NISCA= address (Invalid cluster group number).D Port Disabled Number of packets discarded because the LAN or- IP devicUe was disabled.? H/W Transmit Number of local hardware transmit errors. Errors> Hello Transmit Number of transmit errors during HELLOs. Errors5 Last Transmit Reason for last transmit error. Error Reason@ Time of Last Time of last transmit error:date and time. Transmit Error D For IP interfaces, the error count can increase for the following@ reasons. These errors will be displayed with any of the error codes.: o The interfacVe is unable to send data (SS$_SUSPENDED)+ o Link is disconnected (SS$_LINKDISCON) 2 LAN_DEVICEC Displays PEdriver device data. Each device is a local LAN device= on the system, which can be used for NISCA communications. Format# SHOW LAN_DEVICE landevicename 3 Parameter landevicename[,...]@ Includes specific LAN devices, which you can use wildcards to specify.5 Use the /EXCLUDE qualifier to exclude LAN devices.; Use the SHOW WLAN_DEVICE command to display device names. 3 Qualifiers /ALL Includes all device data. /COUNTERSD Includes device counters data maintained by PEdriver and counters& data maintained by the LAN drivers. /EXCLUDE$ /EXCLUDE=(landevicename[,...])@ Excludes specific LAN devices, which you can use wildcards to specify. /INTERVALD For the /COUNTERS display, displays the changes to counters since the last SHOW command. /nXD Displays the nth page. To select a particular page of a multipage? display, specify the number of the page you want to display. /OUTPUT /OUTPUT=filespec7 Creates the specified file and directs output to it. /SDAA Includes LAN device data displayed in SDA format, with all the4 data collected in one display for one LAN device. /SUMMARY= Includes device summary data. This is the default if /ALL,4 /COUNTERS, and /SDA qualifiers are not specYified. 3 Example SCACP> SHOW LAN_DEVICE/COUNTERS: The command in this example displays device counters.) SCACP> SHOW LAN_DEVICE/COUNTERS/INTERVAL SCACP> SPAWN WAIT 0:0:10) SCACP> SHOW LAN_DEVICE/COUNTERS/INTERVAL? The first command in this example displays device countersA since the last SHOW command. The SPAWN command tells the DCL> WAIT command to insert a 10-second delay. The second SHOW: command displays counters after the 10-second period. SZCACP> SHOW LAN_DEVICE/COUNTERS? The following is a snapshot of the output for SHOW LAN/ALL command.? For list of all LAN errors, see IP or LAN Device Error Data. 2 PORT1 Displays information about selected SCA ports. Format SHOW PORT portname 3 Parameter portname[,...]C Displays information about specific SCA ports, which you can useB wildcards to specify. If no portname is specified, all ports on the node are displayed. [ 3 Qualifiers /EXCLUDE /EXCLUDE=(portname[,...])@ Excludes specific port names from the display. You cannot use# wildcards to specify port names. /OUTPUT /OUTPUT=filespecC Creates the specified file and directs the output of the command to this file. 3 Example SCACP> SHOW PORT? The command in this example produces output similar to the following:3 Port data for CLUIO2 at 06-DEC 15:01:25.82A P \ort Mgt Msgs Msgs Dgrams DgramsA Name Prio Sent Rcvd Sent RcvdB ------ ---- ---------- ---------- ---------- ----------A PEA0 0 64582 92237 0 0A PIB0 0 95276 148937 0 0A PIA0 0 0 0 0 0A PIC0 0 62030 115148 0 0 2 TRACE1 Displays PEdriver traci]ng data and parameters.& NOTEA This command is reserved for use by HP Services and OpenVMS@ Engineering only. Trace commands and output are subject to% change from release to release. Format SHOW TRACE nodename 3 Parameter nodename[,...]C Includes channels to specific nodes, which you can use wildcards to specify.> Each node name can be accompanied by optional qualifiers to? specify local and r^emote device names. If no local or remote= device name is specified, all channels associated with the specified node are included.C Use the SHOW CHANNEL command to display node names and local and remote device names. 3 Qualifiers /CONTEXTB Displays only PEdriver trace settings and the event definition.D If this qualifier is not included, trace event data is displayed. /EVENT /EVENT=(event1[,...])B Enables tracing on specific events, w_hich you can use wildcards? to specify. The default is all of the events that are in the trace buffer.= Use the SHOW TRACE/CONTEXT command to display event names. /EXCLUDE /EXCLUDE[=(nodename[,...])C Excludes channels to specific nodes, which you can use wildcards< to specify. Each node name can be accompanied by optional7 qualifiers to specify local and remote device names.? If no local or remote device name is specified, all channels3 associated wi`th the specified node are included. /GLOBAL3 /GLOBAL (default when no nodes are specified)2 /NOGLOBAL (default when nodes are specified)@ Specifies whether or not global trace data is to be returned. /INPUT /INPUT=filename< Reads trace data from the specified file and displays it. /LOCAL_DEVICE) /LOCAL_DEVICE=(landevicename[,...])C Includes specific LAN devices that identify the local end of the9 channel. You can use wildcardas to specify LAN devices.; Use the SHOW LAN_DEVICE command to display device names. /OUTPUT /OUTPUT=filename> Creates the specified file and directs output to it. If the= filename extension is .DMP, the trace data is written to a@ dump file so that you can use the /INPUT qualifier to display it later. /REMOTE_DEVICE* /REMOTE_DEVICE=(landevicename[,...])A Includes specific LAN devices which identify the remote end of7 the channel, which yobu can use wildcards to specify.; Use the SHOW LAN_DEVICE command to display device names. /SORT /SORT /NOSORT (default)A Returns trace data sorted across channels, VCs, and the global= trace buffer by sequence number. The default is trace dataA returned for channels and VCs one at a time, in order, for the2 channel or VC, but not across channels and VCs. 3 Examples 1.SCACP> SHOW TRACE/CONTEXT< The command in this example displays ctrace settings and definition.( 2.SCACP> SHOW TRACE/OUTPUT=NODE10.TRCB The command in this example displays trace data and writes it to the specified file.D An example of the screen output of a SHOW TRACE/CONTEXT command follows.4 SYS999 Trace Context 31-JAN-2001 10:59:28.25:/ Trace buffer size requested 2048 bytes1 Trace buffer total allocated 92160 bytes/ Trace buffer allocations 45 successful* Trace buffer allodcations 0 failed0 Current trace sequence number 812286047( System cycle counter 404196 cps/ Stop tracing 0 events after stop event$ Trace Stop Default Event$ ----- ---- ------- -----$ Active Y Error* Active Penalize_ch$ Active Timer* Active Listen_timr* Active Handsh_timr) Active Size_probe) Active e Delay_msmt( Active Verf_vack' Active Y CC_event' Active Y CC_state) Active Y Path_state( Active Y ECS_state* Active ACK_process* Active Y Chan_update* Active Rcvd_CC_msg* Active Rcvd_TR_msg* Active Send_TR_msg) Active Xmt_failed' f Active Y VC_state* Active ACK_timeout) Active Y TMO_listen& Y No_path Channel Selection:? Local Dev Remote Dev Remote Node Name Selection? --------- ---------- ---------------- ---------( All channels and VCs selected 2 VC> Displays PEdriver virtual circuit data. Each VC is an SCACPC communications path between the local system and %ga remote system" comprised of a set of channels.B Use the SHOW CHANNEL or SHOW VC commands to display node names,2 which are simply the names of the remote nodes. Format SHOW VC nodename 3 Parameter nodename[,...]C Includes specific nodes, which you can use wildcards to specify. 3 Qualifiers /ALL Includes all VC data. /COUNTERS Includes VC counter data. /EXCLUDE /EXCLUDE=(nodename[,...])C Excludehs specific nodes, which you can use wildcards to specify.@ Use the SHOW CHANNEL or SHOW VC commands to display VC names,2 which are simply the names of the remote nodes. /INTERVALD For the /COUNTERS display, displays the changes to counters since the last SHOW command. /nD Displays the nth page. To select a particular page of a multipage? display, specify the number of the page you want to display. /OUTPUT /OUTPUT=filespec7 Creates the sipecified file and directs output to it. /SDA, Includes VC data displayed in SDA format. /SUMMARYD Includes VC summary data. This is the default if /ALL, /COUNTERS,) and /SDA qualifiers are not specified. 3 Examples# 1.SCACP> SHOW VC/COUNTERS NODE10A The command in this example displays VC counters for all VCs? whose name (that is, remote node name) starts with NODE10.% 2.SCACP> SHOW VC/COUNTERS/INTERVAL SCACP> SPAWN WAIT 0:0:10% j SCACP> SHOW VC/COUNTERS/INTERVALA The first command in this example displays VC counters since@ the last SHOW command. The SPAWN command tells the DCL WAITD command to insert a 10-second delay. The second SHOW VC command2 displays counters after the 10-second period. 3 SPAWNA Creates a subprocess of the current process. The SPAWN commandA copies the context of the subprocess from the current process. Format SPAWN [command-string] 2 Parkameter command-stringD A string of commands to be executed in the context of the createdD subprocess. After the command string is executed, control returns to SCACP. 2 Qualifiers None. 2 Example SCACP> SPAWN SHOW TIME 24-AUG-2005 15:22:39 SCACP>D The command in this example creates a subprocess of the current# process and displays the time. ww1 START 2 IP_INTERFACE> Directs PEdriver to start usingl the specified IP interface. Format$ START IP_INTERFACE ipinterface 3 Parameter ipinterface[,...]B Includes specific IP interfaces, which you can use wildcards to specify.: o Use the /EXCLUDE qualifier to exclude IP interfaces.A o Use the SHOW IP_INTERFACE command to display IP interfaces. 3 Qualifiers /EXCLUDE" /EXCLUDE=(ipinterface[,...])> Excludes specific IP interface, which you can use wildcards> to specify. Usem the SHOW IP_INTERFACE command to display IP interface names. 3 Example SCACP> START IP_INTERFACE WE0: This command starts PEdriver on the IP interface WE0. 2 LAN_DEVICE@ Directs PEdriver to start using the specified LAN device. The@ original (and still supported) way to start PEdriver on a LAN) device is SYS$EXAMPLES:LAVC$START_BUS. Format$ START LAN_DEVICE landevicename 3 Parameter landevicename[,...]@ Includes specific LnAN devices, which you can use wildcards to specify.5 Use the /EXCLUDE qualifier to exclude LAN devices.; Use the SHOW LAN_DEVICE command to display device names. 3 Qualifiers /EXCLUDE$ /EXCLUDE=(landevicename[,...])@ Excludes specific LAN devices, which you can use wildcards to specify.; Use the SHOW LAN_DEVICE command to display device names. 2 Example SCACP> START LAN_DEVICE EWA8 This command starts PEdriver on the LAN devicoe EWA. 2 TRACEA Starts or resumes PEdriver tracing, optionally setting tracing options.& NOTEA This command is reserved for use by HP Services and OpenVMS= Engineering only. Trace commands, their qualifiers, and; output are subject to change from release to release. Format START TRACE nodename 3 Parameter nodename[,...]A Includes information about communications with specific nodes,@ whipch you can use wildcards to specify. Each node name can beA accompanied by optional qualifiers to specify local and remote device names.A If no local or remote device name is specified, the VC and all< channels associated with the specified node are included.C Use the SHOW CHANNEL command to display node names and local and remote device names. 3 Qualifiers /AFTER /AFTER=n? After the trace stop condition has been satisfied, continues> traciqng for n events, and then stops. If you do not specify@ /AFTER, tracing does not continue after the trace stop event., n can be any value between 0 and FFFFFFF. /DEFAULTB Sets the trace context back to the default settings, which are: channelname=* /AFTER=0! /EVENT=default settings /STOP /SIZE=512 /EVENT /EVENT=(event1[,...])B Enables tracing on specific events, which you can use wildcardsD to specifry. The default is a subset of the events, which includes! most errors and state changes.= Use the SHOW TRACE/CONTEXT command to display event names. /EXCLUDE0 /EXCLUDE=(landevicename/IPinterface[,...])A Excludes specific LAN devices/IP interfaces, which you can use wildcards to specify.? Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command to display device names. /LOCAL_DEVICE5 /LOCAL_DEVICE=(landevicename/IPinterface[,...])? Includes spsecific LAN devices that identify the local end of? the channel. You can use wildcards to specify LAN devices/IP interfaces.? Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command to display device names. /REMOTE_DEVICE6 /REMOTE_DEVICE=(landevicename/IPinterface[,...])@ Includes specific LAN devices that identify the remote end of? the channel. You can use wildcards to specify LAN devices/IP interfaces.? Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command tto display device names. /STOP /STOP=(event[,...])C Stops tracing on specific events, which you can use wildcards to- specify. The default is to stop no events.= Use the SHOW TRACE/CONTEXT command to display event names. /SIZE /SIZE=nB Specifies a trace buffer size of n bytes to be used by PEdriverC for each trace buffer: one for global PEdriver use, one for each? selected channel, and one for each selected VC. n can be any valueu between 0 and FFFFFFF. 3 Examples0 1.SCACP> START TRACE/EVENT=CC_STATE/SIZE=2000B The command in this example changes the Trace Channel Control/ layer state with a 2000-byte trace buffer./ 2.SCACP> START TRACE/EVENT=ALL NODE10,NODE20C The command in this example traces all events but only for the NODE10 and NODE20 channels. ww@1 STOP 2 IP_INTERFACE= Directs PEdriver to stop using the specified IP interface.' v CAUTION> If you use STOP IP_INTERFACE to stop the only connection? you have to a cluster, it results in a system CLUEXIT. If@ you use STOP IP_INTERFACE to stop the only the connection,? connected to a cluster, the system will CLUEXIT even when? you have another connection that uses a different cluster@ port. However, if you stop all the IP_INTERFACE results in> excessive activity. When PEdriver loses access to all ofA w its IP interfaces, it makes an effort to restore cluster IP= interfaces communications by completely re-initializing: itself. After the displayed retry count is exceeded,? PEdriver permanently goes offline. To disable cluster use? of all but one IP interface, enter the following command:5 SCACP> STOP IP_INTERFACE * /EXCLUDE=ipinterfaceA All IP interfaces are stopped except the excluded interface- and PEdriver does not need to be reset. Format x) STOP IP_INTERFACE ipinterface[,...] 3 Parameter ipinterface[,...]A Includes specific IP interface, which you can use wildcards to specify.: o Use the /EXCLUDE qualifier to exclude IP interfaces.? o Use the SHOW IP_INTERFACE command to display IP interface names. 3 Qualifiers /EXCLUDE" /EXCLUDE=(ipinterface[,...])A Excludes specific IP interface, which you can use wildcards to specify. 3 Example SCAyCP> STOP IP_INTERFACE WE09 This command stops PEdriver on the IP interface WE0. 2 LAN_DEVICE? Directs PEdriver to stop using the specified LAN device. The? original (and still supported) way to stop PEdriver on a LAN( device is SYS$EXAMPLES:LAVC$STOP_BUS.' CAUTIONB If you use either STOP LAN_DEVICE or SYS$EXAMPLES:LAVC$STOP_@ BUS to stop the only connection you have to a cluster, you" cause the system to CLUEXIT.8 z Even when you have have another connection using a> different cluster port, stopping all LAN devices results> in excessive activity. When PEdriver loses access to all? of its LAN devices, it makes an effort to restore cluster: communications by completely re-initializing itself.? After the last LAN device is stopped, the reinitilization9 produces an error message similar to the following: SCACP> STOP LAN *Q ;%PEA0, Port is Reinitiali{zing ( 49 Retries Left). Check the Error Log.; After the displayed retry count is exceeded, PEdriver permanently goes offline.? To disable cluster use of all but 1 LAN device, enter the following command:2 SCACP> STOP LAN * /EXCLUDE=landevicenameA All LAN devices except the excluded device are stopped, and) PEdriver does not need to be reset. Format# STOP LAN_DEVICE landevicename 3 Parameter landevicename[,...|]@ Includes specific LAN devices, which you can use wildcards to specify.5 Use the /EXCLUDE qualifier to exclude LAN devices.; Use the SHOW LAN_DEVICE command to display device names. 3 Qualifier /EXCLUDE$ /EXCLUDE=(landevicename[,...])@ Excludes specific LAN devices, which you can use wildcards to specify. 3 Example SCACP> STOP LAN_DEVICE EWA7 This command stops PEdriver on the LAN device EWA. 2 TRACEB Stops PEDRI}VER tracing. You can read the trace data recorded so! far with a SHOW TRACE command.B To revert trace behavior to initial settings, enter the command SET TRACE/DEFAULT.& NOTEA This command is reserved for use by HP Services and OpenVMS@ Engineering only. Trace commands and output are subject to% change from release to release. Format STOP TRACE 3 Parameters None. 3 Qualifiers None. 3 Example SCACP> STOP TRACE8 The command in this example stops PEDRIVER tracing.ww