% Librarian A09-30: V5@about$.actionsalias csmacdFDDCMPDpEVD`FDDINHFramehdlc=LAPB(llc2Modem&mopnodenspoptionsosi@8routingahSessiono session_appvV session_backyH session_port| session_tower session_transtW1 about=title Overview of NET$MGMTK The NET$MGMT utility provides a hierarchical graphical approach to the J management of DECnet-Plus. The manageable components of DECnet-Plus I (referred to as entities, subentities, or instances) are represented @ in a tree-like structure below the icon of the node you are managing. K The entities in the display that are "greyed out" are not yet supported by this application. 2 Addition_help =title Additional Help L Nearly all of the displays have a Help pulldown menu. These menus have K two options available: "On Window" and "About". Click on the "About" I option for a general overview of NET$MGMT. Click on the "On Window" + option for specific screen information.  2 expand_collapse (=title Expanding and Collapsing the View I Expanding means bringing into view any subentities associated with anF entity. Collapsing means taking t hose subentities away from view.J A highlighted icon (a dark diamond) in front of an entity or subentityI indicates that it has children and may be expanded or collapsed. ForG example, when you expand the Node entity, its subentities, such as . Event Dispatcher, Alias, etc. will appear.3 how_to_expand_collapse =title How to Expand or CollapseF There are two methods to perform the expand/collapse action. The N easiest way is to double-click the left-most mouse button on an entity in K the main window. (Of course, if you have changed your Session Manager L Options and are using the Left-Handed Mouse Button Arrangement, use the  right-most button instead.)G Another way to expand or collapse an entity is to single click the J left mouse button on the entity to select it and then select Expand or, Collapse from the Actions pulldown menu.3 how_to_see_ncl6=title How to Watch the NCL Commands in the BackgroundK Some entities take longer to expand than others because the applicationE is busy querying the system about the subentities. For example, K expanding routing circuit adjacencies will generally take longer on an K intermediate system than it will on an end system. If you are curious J about what NCL commands the application is performing on your behalf, G you can select Default Actions from the Options pulldown and enable" NCL to display those commands.2 permanent_changes2=title Makin g Permanent Network Management ChangesL Just as with NCL, any network management changes you make using NET$MGMTC will only be retained until the next reboot. In order to make H permanent network management changes, you can modify the NCL startupL scripts by running the SYS$MANAGER:NET$CONFIGURE.COM procedure and usingI the ADVANCED option. Do not modify the SYS$MANAGER:NET$*_STARTUP.NCLN scripts directly. Refer to the Installation and Configuration Manual for B more information about making permanent configuration changes. 2 Mouse_usage=Title Mouse UsageG The mouse is used to Select an entity; perform the Zoom, Expand and 5 Collapse actions; and move around in the displays.I Note: Right-handed button arrangement is the default for the Session I Manager. If you are using the left-handed button arrangement instead,: the action of mouse buttons described here is reversed.3 MB1=title Left Mouse Button  M A s ingle-click with the left mouse button while the pointer is positioned I over an unhighlighted entity will select (or highlight) that entity.  N A single-click with the left mouse button while the pointer is positioned F over an entity that has been highlighted previously will cause the J expansion of that entity if that entity is not already in the expanded I state. ("Expanding" the entity means that its subentities will become visible.)M A double-click with the lef t mouse button while the pointer is positioned L over any entity or subentity will cause the expansion or collapse of thatM entity. For example, double-clicking the left mouse button on the SessionJ Control entity after it has already expanded would cause that entity to be collapsed, and vice versa.3 MB3=title Right Mouse ButtonK A single-click with the right mouse button over any entity, subentity orK instance that currently has the Zoom action enabled, will automatically L bring up that entity's Zoom display. If the Zoom action is currently not 4 allowed for that entity, no action will be taken. 2 Pushbuttons=title Pushbutton UsageJ The following pushbuttons are located at the bottom of the appropriate displays: K OK - After you are finished making changes in a display, push OK L to approve the action. The appropriate NCL commands will be A issued, and the current display will be  dismissed.H APPLY - Does the same thing as the OK pushbutton, but the displayK remains up after the NCL commands have been issued. This isJ convenient because you can "try out" different settings by J APPLYing them. Since the display remains up, you can then F RESET to the previous values or set the values to theirJ DEFAULTs and re-APPLY if you like. The display will remain> up until you push CANCE L to dismiss the window.J RESET - Returns the values of all attributes back to what they wereL when you first entered the display. These values are changedJ in the display only -- no NCL commands are issued until youE push APPLY or OK. The display remains up for further 9 modifications until you push OK or CANCEL.J DEFAULTS - Sets the values of all attributes to their defaults. TheseL values are changed in t he display only -- no NCL commands areK issued until you push APPLY or OK. The display remains for A further modifications until you push OK or CANCEL.H CANCEL - Push to abort the action. The window is dismissed and no' NCL commands are issued.H CONTINUE - After all required arguments have been supplied, push to I approve the action. The appropriate NCL commands will be A issued, and the current display will be dismissed.2 Refresh_display=title Refreshing the DisplaysL Certain changes that occur are not immediately reflected in the display.% Examples of such changes include:K - Changes to the entity tree structure that occur when subentities or F instances are dynamically created or deleted during the normal C operation of DECnet-Plus, for example, changes in NSP Ports.B - Changes that occur as a result of some independent network F management ac tion. For example, another manager may be runningB NCL on the same node and making network management changes. ! - Changes to counter values.F As a result, you may occasionally wish to refresh the display. To B refresh any subentity within the entity tree, simply collapse G and re-expand its parent. To refresh counters, it is necessary to " perform the Zoom action again.O If you attempt to perform an action on an entity that no longer exists, an H informational message will be displayed, and the parent entity will  automatically be refreshed.2 Required_rights=title Required Rights I The same rights required to run NCL are also required to run NET$MGMT.H The process invoking NET$MGMT must have the following rights enabled,0 or the process must possess BYPASS privilege:F NET$EXAMINE - Allows you to view network management information. D NET$MANAGE - Permits you to view and modify network management   information.C NET$SECURITY - Allows you to modify Session Control Application  information.K When you use the Change To Remote Node to manage a remote Phase V node, L you can provide explicit access control information. That remote account E must have at least the NET$EXAMINE right in order to successfully H switch management control to the remote node. If you do not provide L explicit access control information, your rights on the remote node will 5 be determined by that node's CML$SERVER account. ? When you wish to return to managing the local node, use the ; "Change to Local Node" option from the options pulldown.  2 Viewer_Pulldown=title Viewer Pulldown 2 The Viewer pulldown menu provides two options: . Exit - This option exits the application. N Style - This option allows you to change the way you view the entity tree L in the main window at any time. By default, the Viewer Style is O Display as Outline. Options include a column view, a left-oriented3 tree view, or a top-oriented tree view.3 column_viewer_style=title Column Viewer StyleE Select Style, Displays as Columns from the Viewer menu to use theG column style display. Currently, this style is not much different  than the Outline style. 3 outline_viewer_style=title Outline Viewer Style ' This is the default Viewer Style. 3 Tree_viewer_st yle=title Tree Viewer Style D When you select Style, Display as Tree from the Viewer pulldown,J the main window will assume a tree-style display. You can then switchF between the left-oriented or top-oriented tree styles by selectingG Style, Display Left or Style, Display Top from the Viewer pulldown.4 tree_navigation =title Moving Around in the TreeL A tree navigator is available to help you move easily to other parts of E the tree. Click on the box in  the lower right corner of the mainL display to bring up the tree navigator. It will show you where you are I in relation to the rest of the tree. You can change position in the J tree by dragging the viewer to the area you wish to view. To dismiss G the navigator display, click on the lower right corner of the main  display again. L Alternatively, you may use the scroll bars to move through a tree-style L display. Whenever you drag a scroll bar, a navigator box will appear toA indicate where you are in relation to the rest of the tree. 2 Actions_Pulldown=title Actions Pulldown P The Actions pulldown menu allows you to select functions to be performed on O an entity. Examples of frequently performed actions are: Create, Delete, N Enable, Disable, etc. For the most part, the Actions are named for their O equivalent NCL directives. One exception to this naming convention is the J Zoom action. Zoom displays allow you to Show and in some cases, Set, ; Enable or Disable attributes for a particular entity. 3 possible_actions;=title How to Determine the Actions Available for an EntityN To determine which actions can be performed on a particular entity, place M the pointer on that entity and click the left mouse button to highlight L the entity. (Or, use the right mouse button if your Session Manager is O configured to use Left-Handed Button Arrangement.) Then place the pointer L over the Actions pulldown and click on the left mouse button; A list of M actions available for this entity will be displayed. Only those actions I that are not greyed out are currently available, note, this list may / change as the state of the entity changes. J Click on the action you wish to perform, and a display for that actionH will appear to prompt you for arguments if necessary. If an action H display is presented, you have the option of aborting the action by M pushing the CANCEL button or proceeding with the action by supplying any L required information and pushing a CONTINUE, OKAY or APPLY button. See > Pushbutton Usage for more information about these buttons. 3 frequently_performed_actions4=title Short-cuts for Zoom, Expand, Collapse ActionsM The most frequently performed actions (Zoom, Expand, and Collapse) can be M performed using the mouse instead of the Actions pulldown if you prefer.  M Double-clicking the l !eft mouse button while the pointer is positioned overG any entity or subentity will cause the expansion or collapse of thatM entity. For example, double-clicking the left mouse button on the SessionJ Control entity after it has already expanded would cause that entity to be collapsed, and vice versa.L Single-clicking the right-most mouse button over any entity, subentity orJ instance that currently has the Zoom action enabled will automatically L bring up that entity's Zoom" display. If the Zoom action is currently not 4 allowed for that entity, no action will be taken. J Note: If you have changed your Session Manager to use the left-handed K button arrangement, use the left button to Zoom and the right button to  Expand/Collapse.2 Options_pulldown=title Options Pulldown2 The Options pulldown provides three functions:K Change To Remote Node - This option allows you to set the node you are N managi #ng to any other Phase V node on the network.N Change To Local Node - This option returns you to managing the node from > which you originally ran NET$MGMT.O Default Actions - This option allows you to display the NCL commands M that are used to create the displays and perform L the actions requested. These NCL commands will M appear in the window where you originally is$sued 8 the command to run NET$MGMT. 2 tasks_pulldown=title Tasks PulldownG The Tasks pulldown provides access to commonly performed managementN activities. Tasks are functions that generally require many NCL commands G or are complex in some way. The number of available tasks will be L increased with future releases. Currently, the supported tasks include:  Show Known Links  Show Known Node Counters % Show Transports   ww߭ 1 actions2 Boot3 MOP 4 Circuit=title Boot Mop CircuitC Causes the system you are managing to send a boot message to an J adjacent system so the adjacent system will load itself. (The Phase V F NCL BOOT MOP CIRCUIT command is roughly equivalent to the Phase IV  NCP TRIGGER VIA command.)  L If you chose optionally to enter a Client name in the previous menu, the M default boot parame&ters for this operation are obtained by looking up the N information for that MOP Client, and the parameters present in the current display. 6 The required arguments for this boot operation are: o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit J The MOP circuit you have currently selected for the boot operation.7 The optional arguments for this boot operation are: o Cli'ent I A client entity to be used for this operation, if you provided one in the previous display. o DeviceF Provides some information required by the target system for the boot operation.  o Script ID : Script file required by the target system for boot. o Software ID ; System image required by the target system for boot.  o Verification  H A hex string that must match a verification cod (e at the receivingE system in order to trigger the bootstrap mechanism so that theK downline load can be performed. The default is '0000000000000000'H,$ or %x00-00-00-00-00-00-00-00. H Pressing the OK button will cause the boot command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing th)e CANCEL button will return you to the main window. No boot command will be issued. 4 Client=title Boot Mop ClientC Causes the system you are managing to send a boot message to an G adjacent system so that the adjacent system will load itself. (The D Phase V NCL BOOT MOP CLIENT command is roughly equivalent to the ( Phase IV NCP TRIGGER NODE command). 6 The required arguments for this boot operation are: o Address F The LAN address of the target* node on the circuit named in the  circuit argument.  o Circuit A The MOP circuit over which the boot operation is to occur.7 The optional arguments for this boot operation are: o Device F Provides some information required by the target system for the boot operation.  o Script ID : Script file required by the target system for boot. o Software ID ; System image required by the target system for +boot.  o Verification  H A hex string that must match a verification code at the receivingE system in order to trigger the bootstrap mechanism so that theK downline load can be performed. The default is '0000000000000000'H,$ or %x00-00-00-00-00-00-00-00. H Pressing the OK button will cause the boot command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset ,back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No boot command will be issued. 2 Connect3 evd=title Connect Event Dispatcher4 outbound_stream/=title Connect Event Dispatcher Outbound StreamL Pushing the CONTINUE button causes the outbound stream entity to request O a connection to its sink partner. This directive causes the entity to issue L a single session co-nnect request to its sink partner, unless the state isN already OnConnected, in which case the directive has no effect and returns  the success response.7 Pushing the CANCEL button will cancel the operation.; In either case, you will be returned to the main window. 2 Create3 Alias=title Create AliasL Press the CONTINUE button to create the Alias entity on the node you are L managing, or press the CANCEL button to cancel this operation. In either1 case, you w.ill be returned to the main window.4 Port=title Create Alias PortJ This window allows the user to create a new Alias Port. Both the Name H field and Node ID fields must be set prior to pressing APPLY or OK. F Name is the full name to be associated with the port, for example, H DEC:.lkg.bulean. The Node ID is the LAN address associated with the ( port, for example, AA-00-04-00-45-13. M The selection weight represents the number of sequential incoming connectsG / to be passed to this member node in the round-robin sequence before M proceeding to the next member node in the sequence. A value of zero meansJ this node is not eligible to receive incoming connections to this alias3 address. Values between 0 and 10 are suggested.I Select the Enable Port radio button if you want this node to become an1 active member of the alias you are specifying.J Pressing the OK button will create the specified Alias Port and return G you to the ma 0in window. Pressing the APPLY button will create the L specified alias port and leave the current window up. Pressing the RESETF button will reset the values back to what they were when you first E displayed the window. Pressing the CANCEL button will cancel this/ operation and return you to the main window. 3 CSMA-CD=title Create CSMA-CDL Press the CONTINUE button to create a CSMA-CD entity on the node you are L managing, or press the CANCEL button to cancel this o1peration. In either1 case, you will be returned to the main window. 4 Station=title Create CSMA-CD Station : Creates a CSMA-CD Station. The required arguments are: o Station Name H The name of the CSMA-CD Station you wish to create. For example,% CSMACD-0.  o Communication PortI The system device name assigned to this station. The name must beJ in the format ddc, where dd is the device name pref2ix, and c is theK controller letter. The following are examples of device prefixes. G For example, the Communications Port for the first controller onM an SGEC would be EZA. For the second controller it would be EZB, and  so on.  Device Type Prefix DEBNA ET DEBNI ET DELQA XQ DELUA XE DEMNA EX DEQTA XQ DESVA 3 ES DEUNA XE PMAD EC SGEC EZ TGEC TEK Press CONTINUE to create the CSMA-CD Station, or press CANCEL to cancel L this operation. In either case, you will be returned to the main window. 3 DDCMP=title Create DDCMPL Press the CONTINUE button to create the DDCMP entity on the node you are L managing, or press the CANCEL button to cancel this operation. In either1 case, you will 4be returned to the main window.4 Link=title Create DDCMP LinkJ Creates a DDCMP Link. The Name of the DDCMP Link you wish to create isK a required argument. Select one of the Protocol modes to be used by theC local station by single clicking on the associated radio button:D Point The local station is one end of a point-to-point link.; This is the default and only supported value.C Tributary The local station acts as a tributary of a multipoint5 link.F Press CONTINUE to create the DDCMP Link, or press CANCEL to cancel L this operation. In either case, you will be returned to the main window. 5 logical_station(=title Create DDCMP Link Logical StationH Creates a Logical Station for the DDCMP Link you have selected. The K Name of the Logical Station you wish to create is a required argument. K Press CONTINUE to create the Logical Station, or press CANCEL to cancel L this operation. In e6ither case, you will be returned to the main window. 3 evd=title Create Event DispatcherJ Press the CONTINUE button to create the Event Dispatcher entity on the D node you are managing, or press the CANCEL button to cancel this G operation. In either case, you will be returned to the main window.4 outbound_stream.=title Create Event Dispatcher Outbound StreamE Creates an Event Dispatcher Outbound Stream. The Outbound Name isE a required argument. Maximum B 7uffer Size is an optional argument D that specifies the maximum number of octets to be used for event D processing of this stream. The current value is displayed in the I buffer size status attribute. You can specify a size smaller than the I implementation's default, provided it is still sufficient to hold the H events lost event. It is recommended that you use the default buffer  size.K Press CONTINUE to create the Event Dispatcher Outbound Stream, or press J CANCEL to8 cancel this operation. In either case, you will be returned  to the main window. 4 Relay$=title Create Event Dispatcher RelayJ The Event Dispatcher Relay entity processes events from Phase IV DECnet systems.K Press the CONTINUE button to create an Event Dispatcher Relay entity on H the node you are managing, or press the CANCEL button to cancel this G operation. In either case, you will be returned to the main window.4 Sink#=title Create Event Dispat 9cher SinkF An Event Dispatcher Sink entity represents a sink. A sink manages I incoming connections and filters incoming events. Each sink maintainsJ a filter that is applied to all streams that are assigned to that link.G The Sink Name is a required argument specifying a simple name to be  assigned to the sink. F The Maximum Buffer Size is an optional argument that specifies the J maximum number of octets to be used for event processing of this sink. G The current : value is displayed in the buffer size status attribute. E You can specify a size smaller than the implementation's default, I provided it is still sufficient to hold the events lost event. If the E value specified in this argument is inadequate for the events lost: event, an insufficient resources exception is returned.J Press the CONTINUE button to create an Event Dispatcher Sink entity on H the node you are managing, or press the CANCEL button to cancel this G operation. ; In either case, you will be returned to the main window.3 FDDI=title Create FDDIG Press the CONTINUE button to create the FDDI entity on the node you G are managing, or press the CANCEL button to cancel this operation. ; In either case, you will be returned to the main window. 4 Station=title Create FDDI Station8 Creates an FDDI Station. The required arguments are: o Station Name E The name of the FDDI Station you wish to create. For< example,# FDDI-0.  o Communication PortI The system device name assigned to this station. The name must beJ in the format ddc, where dd is the device name prefix, and c is theH controller letter. Below are some examples of device prefixes. G For example, the Communications Port for the first controller on a DEMFA would be FXA.  Device Type Prefix DEMFA fx DEFZA = fcH Press CONTINUE to create the FDDI Station, or press CANCEL to cancel L this operation. In either case, you will be returned to the main window. 3 FRAME=title Create Frame G Press the CONTINUE button to create the FDDI entity on the node you G are managing, or press the CANCEL button to cancel this operation. ; In either case, you will be returned to the main window.4 Link=title Create Frame LinkL Creates a FRAME Link. The name of the FRAME Link, th>e control mode, and ' the protocol are required arguments. CONTROL MODE M Control mode in which the link operates. This argument determines the N value of the contol mode characteristic. The default is point-to-point. multipoint master multipoint tributary point to point PROTOCOLN Framing protocol to be used over the link. This argument determines the, value of the procotol characteristic. ( ? bisync hdlc( chips sdlc) ddcmp swift genbyte 3 HDLC=title Create HDLCG Press the CONTINUE button to create the HDLC entity on the node you G are managing, or press the CANCEL button to cancel this operation. ; In either case, you will be returned to the main window.4 Link=title Create HDLC LinkI Creates an HDLC Link. The Name of the HDLC Link you wish to cr @eate is a required argument. B The profile is an optional argument. It is a latin1 string of G information that can be used when the HDLC protocol is dependent on K network subscription time commitments pertinent to the Data Link layer. B When specified, the values of some link characteristics may be A overridden. This argument determines the value of the profile H characteristic. The default value of this argument is a null string, # meaning that no profile is used. AB The Link Type specifies the operational mode of the HDLC link, J determining how the logical station operates. This value is negotiated K with the remote station. This argument determines the value of the link= type characteristic. Select the appropriate radio button:D Balanced The logical station operates in asynchronous response> balanced mode. This is the default value of the argument.A Primary The logical station is the primary anBd operates in$ normal response mode.A Secondary The logical station is a secondary and operates in$ normal response mode. E Press CONTINUE to create the HDLC Link, or press CANCEL to cancel G this operation. In either case, you will return to the main window. 5 logical_station'=title Create HDLC Link Logical StationG Creates a Logical Station for the HDLC Link you have selected. The K name of the Logical Station you wish to creCate is a required argument. K Press CONTINUE to create the Logical Station, or press CANCEL to cancel L this operation. In either case, you will be returned to the main window. 3 Modem=title Create Modem ConnectH Press the CONTINUE button to create the MODEM entity on the node you G are managing, or press the CANCEL button to cancel this operation. ; In either case, you will be returned to the main window.4 Line =title Create Modem Connect LineF Creat Des a MODEM Connect Line. The line name, communications mode, B communication port, duplex, and profile are required arguments. LINE NAME% Name to associate to this line.  COMMUNICATIONS MODEL Communications method used on the link. This argument determines the M value of the communications mode characteristic. The default value is K taken from the device capability. If that is unknown the default is  synchronous. COMMUNICATION PEORTJ Name of the communications port to which the communications line is P connected. This argument determines the value of the communications port  characteristic. DUPLEXO Specifies whether the line is full-duplex or half-duplex. This argument 9 determines the value of the duplex characteristic.  MODE0 The method of startloop used on this line.H Press the CONTINUE button to create the MOP Circuit entity, or press I the CANCEL buFtton to cancel this operation. In either case, you will  return to the main window.3 MOP=title Create MOPK Pressing the CONTINUE button will create the MOP entity on the node you  are managing. J A NET$MOP process must already be present on the system before you can F successfully create the MOP entity. If a NET$MOP process does not 8 exist, you can start MOP using the following command:$ $ @SYS$SYSTEM:STARTUP NETWORK MOP; The NET$STARTUP_MOP system logi Gcal should be defined in I SYS$MANAGER:NET$LOGICALS.COM if you want to automatically start up MOPG when the system reboots. See the SYS$MANAGER:NET$LOGICALS.TEMPLATE I file if your SYS$MANAGER:NET$LOGICALS.COM file does not already exist.K Pressing the CANCEL button will dismiss the window with no action taken. 4 Circuit=title Create MOP CircuitF Creates a MOP Circuit entity that represents a data link circuit onD which MOP services are available. Both the CircuitH Name and the E Circuit Type are required arguments. An example of a Circuit Name9 is CSMACD-0. An example of a Circuit Type is CSMA-CD.H Press the CONTINUE button to create the MOP Circuit entity, or press I the CANCEL button to cancel this operation. In either case, you will  return to the main window. 4 Client=title Create MOP ClientH Creates a MOP Client entity. A MOP Client entity is a set of defaultK characteristics used by the MOP functions Dump Server I, Load Server, LoadG Requester, Loop Requester and Console Requester. When a command or H request for one of these services does not supply all of the requiredD arguments, the values stored by in the Client entity are used to  perform the operation. 4 The Client Name argument is a required argument. E Press the CONTINUE button to create the MOP Client entity with itsI default values, or press the CANCEL button to cancel this operation. 6 In either case, you will reJturn to the main window.3 nsp=title Create NSP G Press the CONTINUE button to create the NSP Transport entity on the D node you are managing, or press the CANCEL button to cancel this G operation. In either case, you will be returned to the main window.3 OSAK=title Create OSAK H Press the CONTINUE button to create the OSAK Transport entity on theD node you are managing, or press the CANCEL button to cancel thisH operation. In either case, you will be reKturned to the main window. 4 application=title Create OSAK Application G Creates an OSAK Application. Press the OK button to create the OSAK M Application entity, or press the CANCEL button to cancel this operation. 6 In either case, you will return to the main window. 4 invocation)=title Create OSAK Application InvocationH Creates an OSAK Application. Press the OK button to create the OSAK L Application Invocation entity, or press the CANCEL button tLo cancel this B operation. In either case, you will return to the main window. 3 osi_transport=title Create OSI TransportG Press the CONTINUE button to create the OSI Transport entity on the D node you are managing, or press the CANCEL button to cancel this G operation. In either case, you will be returned to the main window.4 Application'=title Create OSI Transport ApplicationF Creates an OSI Transport Application. An OSI Transport ApplicationE entity stMores information about an end user that is activated for F receipt of an incoming connection request when the request contains8 that end user's name in its Destination Name field. ( The following is a required argument: o Application Name5 Simple name to be assigned to the application.( The following arguments are optional: o FilenameF The name of the program to be invoked upon receipt of a connectF request containing a TSEL matching the "C Nalled TSELS" attribute! of the Application entity. o UsernameC The user name portion of the access control information thatC identifies the account under with the application is to run.B If invalid information or no user name is specified, system, defaults are used to select the user. F Press the OK button to create the OSI Transport Application entity,I or press the CANCEL button to cancel this operation. In either case, & you will retu Orn to the main window. 4 Template$=title Create OSI Transport Template= An OSI Transport Template entity provides a collection of J characteristics that supply default values for certain parameters that A influence the operation of a port on a transport connection. I One template, with the reserved identifier "default", is automaticallyF created when the OSI Transport entity is created. This template isE used by default when a user does not specify a template identifPierG in a call to establish a connection. The "default" template is alsoE used to determine the initial values for the attributes of any new, OSI Transport Template entity you create.0 The OSI Template Name is a required argument.I Press the CONTINUE button to create the OSI Transport Template entity,I or press the CANCEL button to cancel this operation. In either case, & you will return to the main window. 3 Routing=title Create Routing Creates theQ Routing entity.  The required arguments are: o Protocols H Protocols supported by this router. The value of this argument isH a set containing either or both of the values IP or ISO8473. ThisE argument determines the value of the protocols characteristic.E The default value of this argument depends on the value of the type argument. o TypeE Routing type for this node. This argument determines the value- of the type chaRracteristic attribute. , endnode The node is an end system./ L1router The node is a level 1 router./ L2router The node is a level 2 router. 4 Circuit=title Create Routing CircuitK Creates a Routing Circuit entity that represents a data link to another L node. The Circuit Name is a required argument. Select the Circuit Type - radio button that describes that circuit. L Press the CONTINUE button to create the Routing Circuit entity, or press SI the CANCEL button to cancel this operation. In either case, you will  return to the main window. 5 Adjacency'=title Create Routing Circuit AdjacencyH Creates a Routing Circuit Adjacency entity for particular circuit youB have selected. A Routing Circuit Adjacency entity describes a D neighboring node that is accessible through a particular circuit./ The required arguments for this display are: o Name7 The simple name to be assigned to the adjacency T. o Endnode IDs G A set of source system IDs. To add new Endnode IDs to this set,J type the Endnode ID in the "End Node IDs to Add" field and push theI ADD button. To remove old Endnode IDs from this set, click on theJ Endnode ID you wish to remove so that it becomes highlighted, then H push the REMOVE button. A scroll bar will appear to the right ofK the Endnode IDs field whenever it is necessary to allow you to move ) through the lisUt of Endnode IDs.   o LAN address C The Data Link address from which the adjacency receives end  system hellos.  The optional argument is:  o Data Format B This string describes the format of the reachable address.  M Press the CONTINUE button to create the Routing Circuit Adjacency entity, M or press the CANCEL button to cancel this operation. In either case, you " will return to the main window.5 ip_reachable_addresVs2=title Create Routing Circuit IP Reachable AddressD create [node node-id] routing circuit circuit-name ip reachable/ address destination subnet-address 6 Arguments o destination subnet-address< Specifies the IP address and subnet mask to which this IP> reachable address corresponds. This argument determines theC value of the destination characteristic. Note that if the subnet? address is for an IP host, this argument also determines the( value oWf the next hop characteristic.5 reachable_address/=title Create Routing Circuit Reachable Address@ create [node node-id] routing circuit circuit-name reachable< address simple-name address prefix address-prefix 6 Arguments o address prefix address-prefix> Address prefix to which this reachable address corresponds. 6 Identifier o nameD Simple name assigned to the reachable address when it is created. 4 egp_group=title Create RoutinXg EGP Group6 create [node node-id] routing egp group group-name o name< Simple name assigned to the EGP group when it is created.5 egp_neighbor,=title Create Routing EGP Group EGP NeighborC create [node node-id] routing egp group group-name egp neighbor/ neighbor-name ip address ip-address 6 Arguments o ip address ip-address& The IP address of the EGP neighbor. 6 Identifier o name? Simple name assigned to the EGPY neighbor when it is created.4 ptd_neighbor (=title Create Routing Permitted NeighborG A Routing Permitted Neighbor entity represents a neighboring node onD a nonbroadcast circuit that is permitted to connect to this node.B The Neighbor Name and the Node ID of the permitted neighbor are required arguments.N Press the CONTINUE button to create the Routing Permitted Neighbor entity, M or press the CANCEL button to cancel this operation. In either case, you " will Zreturn to the main window.3 session_control=title Create Session ControlJ! Press the CONTINUE button to create the Session Control entity on the E! node you are managing, or press the CANCEL button to cancel this H! operation. In either case, you will be returned to the main window.4 Application)=title Create Session Control ApplicationH Creates a Session Control Application. A Session Control ApplicationE entity stores information about an end user that is act[ivated for F receipt of an incoming connection request when the request contains8 that end user's name in its Destination Name field. ( The following is a required argument: o Application Name5 Simple name to be assigned to the application.L The following values will be set to false by default. You can set these F to true by pushing on their associated toggle buttons so that those- buttons are in the "on" state (filled in): o Incoming AliasJ \ Specifies how a particular application responds to incoming connectJ requests directed to the alias node address. The default is to notG allow the application to receive incoming connect requests that 4 have been directed to the alias node address. o Incoming ProxyJ Specifies whether to honor incoming proxy requests. The default isG to ignore requests to invoke proxies on incoming requests. ThisG setting on the Session Control Application ]entity overrides the C setting of the same attribute on the Session Control entity. o Outgoing ProxyF Specifies the default action to execute when the user does not I explicitly specify whether or not to invoke a proxy. The default H is not to invoke the proxy. This setting on the Session Control I Application entity overrides the setting of the same attribute on " the Session Control entity. o Outgoing AliasE Specifies wheth ^er a particular application uses the alias nodeG identifier in its outgoing connect requests. The default is notF to use the alias node address in its outgoing connect requests. o Node SynonymC Specifies the default form in which the remote node name is F passed to the application. The default is to use the fullname.F If this toggle is turned on (i.e., Node Synonym is set to true)E when there is no synonym available, then the fullname is used._( The following arguments are optional: o Client NameH Identifies the name of the local user that will be activated uponB receipt of a connect request containing a destination name E matching one of the values in the destination names attribute. o User NameG Identifies the default account under which the application is toC run. If this is null, then the system defaults are used to  select the user. o Image NameG ` Filename of a program to be invoked upon receipt of a connectionD request containing an address that matches one of the values H contained in the set described by the Addresses characteristic of. the Session Control Application entity. o Incoming OSI TSELH The TSEL this image will accept connections for. This is similarG to the destination names attribute. However, applications usingA the access point for in-connection matching do not use DNAa Session Control protocol. @ The TSEL must be entered as a hex octet, Example: '1234'H  o Network PriorityH Press the OK button to create the Session Control Application entity,I or press the CANCEL button to cancel this operation. In either case, & you will return to the main window.4 transport_service/=title Create Session Control Transport ServiceB Creates a Session Control Transport Service entity that stores A information about m bodules in the Transport layer that support  Session Control. G If the NSP Transport is selected, then the '04'H Protocol ID should 5 be selected, and the TSEL field is not applicable.F If the OSI Transport is selected, then the '05'H Protocol ID shouldI be selected, and the TSEL defaults to DEC0, ('DEC0'H). The Transport A selector is used by the OSI Transport Module to bind incoming * connection requests to session control.G Press the OK button to create the Sescsion Control Transport Service K entity, or press the CANCEL button to cancel this operation. In either , case, you will return to the main window. 3 x25_access=title Create X.25 Access I Creates the X.25 Access entity. The Maximum Active Ports argument is  an optional argument.  o Maximum Active Ports L The total number of ports that can be active simultaneously. You can M not modify this characteristic, to set it it must be supplied at created time.I Press the CONTINUE button to create the X.25 Access entity, or press I the CANCEL button to cancel this operation. In either case, you will  return to the main window.4 app%=title Create X.25 Access ApplicationH Creates a X.25 Access Application entity. The Application Name is a  required argument.  K Press the CONTINUE button to create the X.25 Access Application entity, M or press the CANCEL button to cancel this operation. In eithere case, you " will return to the main window.4 dte#=title Create X.25 Access DTE ClassL Creates a X.25 Access DTE Class entity. The Class Name, and Type values : are required arguments. The Profile value is optional.  o Class Name$ The name of this new DTE Class o ProfileL The name of the profile that supplies the information to perform X.121P Mapping to or from a simpel DTE address. The profile supplies the defaultL vaules for thef International prefix, Local prefix, DNIC and strip DNIC o Type The type of DTE class:7 Local - The DTE class consists of local DTEs.L Remote - The DTE class consists of DTEs on a remote gateway system. I Press the CONTINUE button to create the X.25 Access DTE Class entity, M or press the CANCEL button to cancel this operation. In either case, you " will return to the main window. 4 filter =title Create X.25 Access FilterG Creates a Xg.25 Access Filter entity. The Filter Name is a required  argument.  F Press the CONTINUE button to create the X.25 Access Filter entity, M or press the CANCEL button to cancel this operation. In either case, you " will return to the main window. 4 reachable+=title Create X.25 Access Reachable AddressO Creates a X.25 Access Reachable Address entity. The Name and Address Prefix are required arguments. o Name3 The Name of this new Reachable Address Ehntity  o Address PrefixJ The Address Prefix to trigger the use of DTE class and destination.  H Press the CONTINUE button to create the X.25 Access Reachable AddressK entity, or press the CANCEL button to cancel this operation. In either , case, you will return to the main window. 4 Security"=title Create X.25 Access Security5 Flt)=title Create X.25 Access Security Filter5 rmt-=title Create X.25 Access Security Remote DTE 4 template"=tit!ile Create X.25 Access Template 3 x25_client=title Create X.25 Client 3 x25_relay=title Create X.25 Relay 4 client=title Create X.25 Relay Client4 pvc=title Create X.25 Relay PVC 3 x25_server=title Create X.25 Server 4 security&=title Create X.25 Server Security DTE 4 client =title Create X.25 Server Client3 x25_protocol=title Create X.25 Protocol4 group!=title Create X.25 Protocol Group4 dte=title Create X.25 Protocol DTE5 pjvc#=title Create X.25 Protocol DTE PVC 2 Delete3 Alias=title Delete Alias J Pushing the CONTINUE button will delete the Alias entity and return youG to the main window. Any existing Alias Ports must be disabled and ? deleted before the Alias entity can be successfully deleted.K Pushing the CANCEL button will dismiss the window with no action taken. 4 Port=title Delete Alias PortI Pushing the CONTINUE button will cause the specified Alias Port to kbe K deleted from the system. The Alias Port must be disabled before it can  be successfully deleted. J Pushing the CANCEL button will dismiss the window with no action taken. 3 CSMA-CD=title Delete CSMA-CD K Pushing the CONTINUE button will cause the CSMA-CD entity to be deleted.L Any existing CSMA-CD Stations must be disabled and deleted before you can* successfully delete the CSMA-CD entity.J Pushing the CANCEL button will dismiss the window with nol action taken. 4 Station=title Delete CSMA-CD StationK Pushing the CONTINUE button will cause the CSMA-CD Station entity to be J deleted. The CSMA-CD Station must be disabled and all ports associatedL with this station must have gone away before you can successfully delete  this CSMA-CD Station entity.J Pushing the CANCEL button will dismiss the window with no action taken.3 DDCMP=title Delete DDCMP K Pushing the CONTINUE button will cause the DDCMP mentity to be deleted. H Any existing DDCMP Link entities must have been disabled and deleted 8 before this DDCMP entity can be successfully removed.J Pushing the CANCEL button will dismiss the window with no action taken.4 Link=title Delete DDCMP LinkF Pushing the CONTINUE button will cause the DDCMP Link entity to be J deleted. This DDCMP Link must be disabled, all of its Logical StationsI must be disabled and deleted, and all ports associated with this link I mnust have gone away before you can successfully delete this DDCMP Link entity.J Pushing the CANCEL button will dismiss the window with no action taken.5 LOGICAL_STATION(=title Delete DDCMP Link Logical StationI Pushing the CONTINUE button will cause this DDCMP Link Logical StationJ entity to be deleted. This DDCMP Link Logical Station must be disabled) before you can successfully delete it.J Pushing the CANCEL button will dismiss the window with no action taken.o3 evd=title Delete Event Dispatcher4 outbound_stream.=title Delete Event Dispatcher Outbound StreamI Pushing the CONTINUE button will cause the specified Event Dispatcher 3 Outbound Stream to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 Relay$=title Delete Event Dispatcher RelayI Pushing the CONTINUE button will cause the specified Event Dispatcher  Relay to be deleted. J Pusphing the CANCEL button will dismiss the window with no action taken.4 Sink#=title Delete Event Dispatcher SinkH Pushing the CONTINUE button will cause the specified Event Dispatcher( Sink to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.3 FDDI=title Delete FDDI H Pushing the CONTINUE button will cause the FDDI entity to be deleted.I Any existing FDDI Stations must be disabled and deleted before yoqu can' successfully delete the FDDI entity.J Pushing the CANCEL button will dismiss the window with no action taken. 4 Station=title Delete FDDI StationH Pushing the CONTINUE button will cause the FDDI Station entity to be G deleted. The FDDI Station must be disabled and all ports associatedL with this station must have gone away before you can successfully delete  this FDDI Station entity.J Pushing the CANCEL button will dismiss the window with no action takern.3 FRAME=title Delete Frame I Pushing the CONTINUE button will cause the FRAME entity to be deleted.G Any existing FRAME links must be disabled and deleted before you can( successfully delete the FRAME entity.J Pushing the CANCEL button will dismiss the window with no action taken.4 LINK=title Delete Frame LinkF Pushing the CONTINUE button will cause the FRAME Link entity to be E deleted. The FRAME Link must be disabled and all ports associatedI with thsis Link must have gone away before you can successfully delete  this FRAME Link entity.J Pushing the CANCEL button will dismiss the window with no action taken.3 HDLC=title Delete HDLC J Pushing the CONTINUE button will cause the HDLC entity to be deleted. G Any existing HDLC Link entities must have been disabled and deleted 7 before this HDLC entity can be successfully deleted.J Pushing the CANCEL button will dismiss the window with no action taken.4 Lintk=title Delete HDLC LinkE Pushing the CONTINUE button will cause the HDLC Link entity to be I deleted. This HDLC Link must be disabled, all of its Logical StationsI must be disabled and deleted, and all ports associated with this link H must have gone away before you can successfully delete this HDLC Link entity.J Pushing the CANCEL button will dismiss the window with no action taken.5 LOGICAL_STATION'=title Delete HDLC Link Logical StationH Pushing theu CONTINUE button will cause this HDLC Link Logical StationI entity to be deleted. This HDLC Link Logical Station must be disabled) before you can successfully delete it.J Pushing the CANCEL button will dismiss the window with no action taken.3 MODEM=title Delete Modem ConnectI Pushing the CONTINUE button will cause the MODEM Connect entity to be  deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 Line v=title Delete Modem Connect LineN Pushing the CONTINUE button will cause the MODEM Connect Line entity to be  deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.3 MOP=title Delete MOPJ Pushing the CONTINUE button will cause the specified MOP Circuit to be H deleted from the system. All MOP Clients must have been deleted, allH MOP Circuits must have been disabled and deleted, and the MOP entity B itself must bwe disabled before you can successfully delete MOP. J Pushing the CANCEL button will dismiss the window with no action taken. 4 Circuit=title Delete MOP CircuitJ Pushing the CONTINUE button will cause the specified MOP Circuit to be I deleted from the system. This MOP Circuit must be disabled before you can successfully delete it.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 Client=title Delete MOP ClientI Pushing thex CONTINUE button will cause the specified MOP Client to be  deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.3 NSP =title Delete NSPJ Pushing the CONTINUE button will cause the NSP Transport to be deleted L from the system. NSP must be disabled before you can successfully delete it. J Pushing the CANCEL button will dismiss the window with no action taken.3 osi_transport=title Delete OSI Transport yJ Pushing the CONTINUE button will cause the OSI Transport to be deleted L from the system. OSI must be disabled before you can successfully delete it. J The delete command disconnects the connection if the port direction is H either incoming or outgoing, and deletes the port. A local transport . disconnection event will also be generated.J The port that represents the session control listener (local transport J selector 'DEC0'H) is a special case and cannot be deletedz. An error is M not returned if an attempt is made to delete the session control listener.J Pushing the CANCEL button will dismiss the window with no action taken.4 Application'=title Delete OSI Transport ApplicationD Pushing the CONTINUE button will cause the selected OSI Transport6 Application entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 Port =title Delete OSI Transport PortK Pus{hing the CONTINUE button will cause the specified OSI Transport Port # to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 Template$=title Delete OSI Transport TemplateF Pushing the CONTINUE button will cause the specified OSI Transport , Template to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 Routing=title Delete RoutingK Pus|hing the CONTINUE button will cause the Routing entity to be deleted I from the system. All Routing Circuit entities must have been disabledL and deleted and the Routing entity itself must be disabled before you can successfully delete Routing. J Pushing the CANCEL button will dismiss the window with no action taken. 4 Circuit=title Delete Routing CircuitK Pushing the CONTINUE button will cause the specified Routing Circuit to be deleted from the system.  } J Pushing the CANCEL button will dismiss the window with no action taken. 5 Adjacency'=title Delete Routing Circuit AdjacencyH Pushing the CONTINUE button will cause the specified Routing Circuit H Adjacency entity to be deleted from the system. You cannot delete anC automatic adjacency, or an adjacency on a circuit that is not a % dynamically assigned X.25 circuit. J Pushing the CANCEL button will dismiss the window with no action taken. 5 ip_address_tran~slation4=title Delete Routing Circuit IP Address TranslationK Pushing the CONTINUE button will cause the specified Routing Circuit IP 7 Address Translation to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 ip_reachable_address2=title Delete Routing Circuit IP Reachable AddressK Pushing the CONTINUE button will cause the specified Routing Circuit IP 5 Reachable Address to be deleted from the system.   J Pushing the CANCEL button will dismiss the window with no action taken.5 reachable_address/=title Delete Routing Circuit Reachable AddressI Pushing the CONTINUE button will cause the specified Routing Circuit 5 Reachable Address to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 egp_group=title Delete Routing EGP GroupI Pushing the CONTINUE button will cause the specified Routing EGP Group# to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 egp_neighbor,=title Delete Routing EGP Group EGP NeighborI Pushing the CONTINUE button will cause the specified Routing EGP Group0 EGP Neighbor to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 permitted_neighbor (=title Delete Routing Permitted NeighborJ Pushing the CONTINUE button will cause the specified Routing Permitted , Neighbor to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 session 4 control =title Delete Session Control F! Pushing the CONTINUE button will cause the Session Control entity K! to be deleted from the system. Session Control must be disabled before! you can delete it.  K! Pushing the CANCEL button will dismiss the window with no action taken.5 Application)=title Delete Session Control ApplicationG Pushing the CONTINUE button will cause the specified Session Control/ Application to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 backtranslation_softlink6=title Delete Session Control Backtranslation SoftlinkH Pushing the CONTINUE button will cause the specified Session Control < Backtranslation Softlink to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 Port"=title Delete Session Control Port H Pushing the CONTINUE button will cause the specified Session Control ( Port to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 tower_maintenance/=title Delete Session Control Tower MaintenanceH Pushing the CONTINUE button will cause the specified Session Control < Tower Maintenance entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 transport_service/=title Delete Session Control Transport ServiceH Pushing the CONTINUE button will cause the specified Session Control 5 Transport Service to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_access=title Delete X.25 Access O Pushing the CONTINUE button will cause the X.25 Access entity to be deleted L from the system. X.25 Access must be disabled before you can delete it.  J Pushing the CANCEL button will dismiss the window with no action taken.4 dte=title Delete X.25 Access DTEM Pushing the CONTINUE button will cause the specified X.25 Access DTE Class* entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 filter =title Delete X.25 Access FilterK Pushing the CONTINUE button will cause the specified X.25 Access Filter * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 reachable+=title Delete X.25 Access Reachable AddressM Pushing the CONTINUE button will cause the specified X.25 Access Reachable2 Address entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 template"=title Delete X.25 Access TemplateM Pushing the CONTINUE button will cause the specified X.25 Access Template * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 Security"=title Delete X.25 Access SecurityM Pushing the CONTINUE button will cause the specified X.25 Access Security . DTE entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 app%=title Delete X.25 Access ApplicationO Pushing the CONTINUE button will cause the specified X.25 Access Application* entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 rmt1=title Delete X.25 Access Security DTE Remote DTEM Pushing the CONTINUE button will cause the specified X.25 Access Security 2 DTE Remote DTE to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 security_Flt)=title Delete X.25 Access Security FilterM Pushing the CONTINUE button will cause the specified X.25 Access Security 1 Filter entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_client=title Delete X.25 ClientO Pushing the CONTINUE button will cause the X.25 Client entity to be deleted L from the system. X.25 Client must be disabled before you can delete it.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_relay=title Delete X.25 RelayN Pushing the CONTINUE button will cause the X.25 Relay entity to be deleted K from the system. X.25 Relay must be disabled before you can delete it.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 client=title Delete X.25 Relay ClientJ Pushing the CONTINUE button will cause the specified X.25 Relay Client * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 pvc=title Delete X.25 Relay PVCN Pushing the CONTINUE button will cause the specified X.25 Relay PVC entity * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_server=title Delete X.25 ServerG Pushing the CONTINUE button will cause the X.25 Server entity to be L deleted from the system. X.25 Server entity must be disabled before you  can delete it.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 security&=title Delete X.25 Server Security DTEM Pushing the CONTINUE button will cause the specified X.25 Server Security . DTE entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 client =title Delete X.25 Server ClientK Pushing the CONTINUE button will cause the specified X.25 Server Client * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.3 x25_protocol=title Delete X.25 ProtocolI Pushing the CONTINUE button will cause the X.25 Protocol entity to be  deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 group!=title Delete X.25 Protocol GroupL Pushing the CONTINUE button will cause the specified X.25 Protocol Group 1 Filter entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.4 dte=title Delete X.25 Protocol DTEJ Pushing the CONTINUE button will cause the specified X.25 Protocol DTE * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken.5 pvc#=title Delete X.25 Protocol DTE PVCN Pushing the CONTINUE button will cause the specified X.25 Protocol DTE PVC * entity to be deleted from the system.  J Pushing the CANCEL button will dismiss the window with no action taken. 2 Disable3 ALIAS4 Port=title Disable Alias PortI Pushing the CONTINUE button will cause the specified Alias Port to be placed in the disabled state. J Pushing the CANCEL button will dismiss the window with no action taken. 3 CSMA-CD 4 Station=title Disable CSMA-CD StationH Pushing the CONTINUE button will cause the specified CSMA-CD Station & to be placed in the disabled state. J Pushing the CANCEL button will dismiss the window with no action taken.3 DDCMP4 Link=title Disable DDCMP LinkI Pushing the CONTINUE button will cause the specified DDCMP Link to be placed in the disabled state. J Pushing the CANCEL button will dismiss the window with no action taken.5 logical_station)=title Disable DDCMP Link Logical StationK Pushing the CONTINUE button will cause the specified DDCMP Link Logical . Station to be placed in the disabled state. J Pushing the CANCEL button will dismiss the window with no action taken.3 evd=title Disable Event DispatcherI Pushing the CONTINUE button will cause the Event Dispatcher to be set  to the disabled state. J Pushing the CANCEL button will dismiss the window with no action taken.4 outbound_stream/=title Disable Event Dispatcher Outbound StreamI Pushing the CONTINUE button will cause the specified Event Dispatcher 3 Outbound Stream to be set to the disabled state. J Pushing the CANCEL button will dismiss the window with no action taken.4 Relay%=title Disable Event Dispatcher RelayK Pushing the CONTINUE button will cause the Event Dispatcher Relay to be H disabled. All three Event Relay Logging entities (Console, File and F Monitor) will be automatically deleted. This will discontinue all A logging of DECnet Phase IV events to the DECnet-Plus system.  J Pushing the CANCEL button will dismiss the window with no action taken. 5 Logging-=title Disable Event Dispatcher Relay LoggingI Pushing the CONTINUE button will cause the specified Event Dispatcher J Relay Logging entity, either Console, Monitor, or File, to be disabled.I Disabling the Console logging will prevent Phase IV events from being ) logged to the operator console (OPA0).H Disabling the Monitor logging will prevent Phase IV events from being9 logged to the Operator Communication Facility (OPCOM).E Disabling the File logging will prevent Phase IV events from being recorded in binary format.  J Pushing the CANCEL button will dismiss the window with no action taken.4 Sink$=title Disable Event Dispatcher SinkI Pushing the CONTINUE button will cause the specified Event Dispatcher  Sink entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.3 FDDI 4 Station=title Disable FDDI StationE Pushing the CONTINUE button will cause the specified FDDI Station  entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.!5 LinkK! Pushing the CONTINUE button will cause the specified FDDI Station Link +! entity to be set to the disabled state. K! Pushing the CANCEL button will dismiss the window with no action taken. !5 Phy_port!=title PHY PortF! Pushing the CONTINUE button will cause the specified FDDI Station #! PHY Port entity to be disabled. K! Pushing the CANCEL button will dismiss the window with no action taken.3 FRAME=title Disable FrameJ Pushing the CONTINUE button will cause the FRAME entity to be disabled.J Pushing the CANCEL button will dismiss the window with no action taken.4 Link=title Disable Frame LinkJ Pushing the CONTINUE button will cause the specified FRAME Link entity  to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.3 HDLC4 Link=title Disable HDLC LinkI Pushing the CONTINUE button will cause the specified HDLC Link entity  to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.5 logical_station(=title Disable HDLC Link Logical StationJ Pushing the CONTINUE button will cause the specified HDLC Link Logical " Station entity to be disabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 MOP=title Disable MOPH Pushing the CONTINUE button will cause the MOP entity to be disabled.J Pushing the CANCEL button will dismiss the window with no action taken. 3 Modem =title Disable Modem Connect 4 line!=title Disable Modem Connect LineN Pushing the CONTINUE button will cause the MODEM Connect Line entity to be disabled.J Pushing the CANCEL button will dismiss the window with no action taken. 4 Circuit$=title Disable Modem Connect CircuitD Pushing the CONTINUE button will cause the specified MOP Circuit  entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.3 NSP=title Disable NSPH Pushing the CONTINUE button will cause the NSP entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.3 osak=title Disable OSAKJ Pushing the CONTINUE button will cause the specified OSAK entity to be  disabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 osi_transport=title Disable OSI Transport I Pushing the CONTINUE button will cause the OSI Transport entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 3 Routing=title Disable Routing L Pushing the CONTINUE button will cause the Routing entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 4 Circuit=title Disable Routing CircuitG Pushing the CONTINUE button will cause the selected Routing Circuit  to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.5 ip_reachable_address3=title Disable Routing Circuit IP Reachable AddressJ Pushing the CONTINUE button will cause the selected Routing Circuit IP $ Reachable Address to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.5 reachable_address0=title Disable Routing Circuit Reachable AddressG Pushing the CONTINUE button will cause the selected Routing Circuit $ Reachable Address to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 4 egp_group =title Disable Routing EGP GroupI Pushing the CONTINUE button will cause the selected Routing EGP Group  to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.5 group_egp_neighbor-=title Disable Routing EGP Group EGP NeighborI Pushing the CONTINUE button will cause the selected Routing EGP Group  EGP Neighbor to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_access=title Disable X.25 Access P Pushing the CONTINUE button will cause the X.25 Access entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.4 app&=title Disable X.25 Access ApplicationN Pushing the CONTINUE button will cause the selected X.25 Access Application entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_client=title Disable X.25 ClientP Pushing the CONTINUE button will cause the X.25 Client entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_relay 4 client =title Disable X.25 Relay ClientP Pushing the CONTINUE button will cause the selected X.25 Relay Client entity  to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.4 pvc=title Disable X.25 Relay PVCM Pushing the CONTINUE button will cause the selected X.25 Relay PVC entity  to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_server=title Disable X.25 ServerP Pushing the CONTINUE button will cause the X.25 Server entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 4 client!=title Disable X.25 Server ClientJ Pushing the CONTINUE button will cause the selected X.25 Server Client  entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.3 x25_protocol4 dte =title Disable X.25 Protocol DTEO Pushing the CONTINUE button will cause the selected X.25 Protocol DTE entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken.5 pvc#=title Delete X.25 Protocol DTE PVCL Pushing the CONTINUE button will cause the selected X.25 Protocol DTE PVC entity to be disabled. J Pushing the CANCEL button will dismiss the window with no action taken. 2 Disconnect3 evd"=title Disconnect Event Dispatcher4 outbound_stream2=title Disconnect Event Dispatcher Outbound StreamC Pushing the CONTINUE button will cause the disconnection of the I specified outbound stream from its sink partner. This will abort the = entity's specified outbound stream connection to the sink.J Pushing the CANCEL button will dismiss the window with no action taken.4 Sink5 inbound_stream1=title Disconnect Event Dispatcher Inbound StreamE Pushing the CONTINUE button will disconnect the entity's specifiedE stream connection. It disconnects the entity's stream connection H immediately. Event reports in transit are lost, and the sink cannot - perform an orderly shutdown on the stream.J Pushing the CANCEL button will dismiss the window with no action taken.2 Echo3 FDDI 4 Station5 Link=title Echo FDDI Station Link< Causes the link subentity to transmit an SMT Echo requestA frame and await the response. If a response is received, it is displayed.> echo [node node-id] fddi station station-name link link-id@ target lan address timeout integer-16 data octet-string 6 Argumentso data$ Data to transmit in echo request. o target$ 48-bit LAN address of the target. o timeout( Value: 1-65535! Timeout, in seconds, optional. 2 Enable3 Alias4 Port=title Enable Alias Port I Pushing the CONTINUE button will cause the specified Alias Port to be G enabled. When the Alias Port entity is enabled, the node becomes an7 active member of the VMScluster alias it specifies.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 CSMA-CD 4 Station=title Enable CSMA-CD Station L Enables the specified CSMA-CD Station entity. The MAC Address representsM an individual medium access control address for the station. Pushing the L CONTINUE button will cause the specified CSMA-CD Station to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 DDCMP4 Link=title Enable DDCMP Link I Pushing the CONTINUE button will cause the specified DDCMP Link to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.5 logical_station)=title Enable DDCMP Link Logical Station J Pushing the CONTINUE button will cause the specified DDCMP Link Logical" Station entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 event_dispatcher=title Enable Event DispatcherE Pushing the CONTINUE button will cause the Event Dispatcher to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.4 outbound_stream.=title Enable Event Dispatcher Outbound StreamI Pushing the CONTINUE button will cause the specified Event Dispatcher # Outbound Stream to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.4 relay$=title Enable Event Dispatcher RelayK Pushing the CONTINUE button will cause the Event Dispatcher Relay to be H enabled so that events from DECnet Phase IV systems will be processed3 and posted into the DECnet-Plus logging system. E Enabling the Event Dispatcher Relay will automatically create and F enable the three Event Dispatcher Relay Logging entities (Console, F File and Monitor). If you wish, each of these logging entities can* be disabled and reenabled individually. J Pushing the CANCEL button will dismiss the window with no action taken. 5 Logging,=title Enable Event Dispatcher Relay LoggingI Pushing the CONTINUE button will cause the specified Event Dispatcher C Relay Logging to be enabled (either Console, Monitor or File). H Enabling the Console logging will cause Phase IV events to be logged " to the operator console (OPA0).G Enabling the Monitor logging will cause Phase IV events to be logged2 to the Operator Communication Facility (OPCOM).G Enabling the File logging will cause Phase IV events to be recorded  in binary format. J Pushing the CANCEL button will dismiss the window with no action taken.4 Sink#=title Enable Event Dispatcher SinkI Pushing the CONTINUE button will cause the specified Event Dispatcher  Sink to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 FDDI 4 Station=title Enable FDDI StationK Pushing the CONTINUE button will cause the specified FDDI Station to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.!5 LinkN! Pushing the CONTINUE button will cause the specified FDDI Station Link to ! be enabled.  K! Pushing the CANCEL button will dismiss the window with no action taken. !5 phy_port!=title PHY Port=! enable [node node-id] fddi station station-name phy port(! port-id mode normal .! internal loopback 3 FRAME=title Enable FrameK Pushing the CONTINUE button will cause the FRAME entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.4 Link=title Enable Frame LinkI Pushing the CONTINUE button will cause the specified FRAME Link to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 HDLC4 Link=title Enable HDLC LinkH Pushing the CONTINUE button will cause the specified HDLC Link to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.5 logical_station(=title Enable HDLC Link Logical Station J Pushing the CONTINUE button will cause the specified HDLC Link Logical  Station to be enabled.   J Pushing the CANCEL button will dismiss the window with no action taken.3 MODEM=title Enable Modem Connect4 line =title Enable Modem Connect LineN Pushing the CONTINUE button will cause the Modem Connect Line entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 MOP=title Enable MOPI Pushing the CONTINUE button will cause the MOP entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 nsp =title Enable NSP TransportI Pushing the CONTINUE button will cause the NSP entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 Osak=title Enable OSAKJ Pushing the CONTINUE button will cause the specified OSAK entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 osi_transport=title Enable OSI TransportI Pushing the CONTINUE button will cause the OSI Transport entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 Routing=title Enable RoutingM Pushing the CONTINUE button will cause the Routing entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 Circuit=title Enable Routing CircuitK Pushing the CONTINUE button will cause the specified Routing Circuit to  be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.5 ip_reachable_address4= title Enable Routing Circuit IP Reachable Address J Pushing the CONTINUE button will cause the specified Routing Circuit IP% Reachable Address to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.5 reachable_address/=title Enable Routing Circuit Reachable AddressH Pushing the CONTINUE button will cause the specified Routing Circuit % Reachable Address to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 4 egp_group =title Enable Routing EGP Group J Pushing the CONTINUE button will cause the specified Routing EGP Group  to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 5 egp_neighbor,=title Enable Routing EGP Group EGP NeighborK Pushing the CONTINUE button will cause the specified Routing EGP Group's EGP Neighbor to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 session=title Enable Session Control F Pushing the CONTINUE button will cause the Session Control Entity  to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_access=title Enable X.25 Access M Pushing the CONTINUE button will cause X.25 Access entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 app%=title Enable X.25 Access ApplicationO Pushing the CONTINUE button will cause the specified X.25 Access Application entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_client=title Enable X.25 ClientK Pushing the CONTINUE button will cause the specified X.25 Client entity  to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_relay 4 client=title Enable X.25 Relay ClientI Pushing the CONTINUE button will cause the specified X.25 Relay Client entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.4 pvc=title Enable X.25 Relay PVCM Pushing the CONTINUE button will cause the specified X.25 Relay PVC entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken. 3 x25_server=title Enable X.25 ServerO Pushing the CONTINUE button will cause the X.25 Server entity to be enabled. J Pushing the CANCEL button will dismiss the window with no action taken. 4 client =title Enable X.25 Server ClientJ Pushing the CONTINUE button will cause the specified X.25 Server Client entity to be enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.3 x25_protocol4 dte=title Enable X.25 Protocol DTEJ Pushing the CONTINUE button will cause the specified X.25 Protocol DTE  entity enabled.  J Pushing the CANCEL button will dismiss the window with no action taken.2 enable_disable=title Enable or Disable3 MOP 4 Circuit$=title Enable or Disable MOP CircuitB Toggle buttons in the on state (filled in) represent those MOP G functions enabled for the circuit. Toggle butt ons in the off state D (empty) represent those MOP functions disabled for the circuit. J To enable a function, click on the associated toggle button until that  button is in the on state. K To disable a function, click on the associated toggle button until that  button is in the off state.K Once you have determined that all the toggle buttons are in their properI states, press the CONTINUE button to cause the appropriate Enable and K Disable commands to be issued . Or press the CANCEL button to cancel theG operation. In either case, you will be returned to the main window.3 Node=title Enable or Disable NodeH Toggle buttons in the on state (filled in) represent those functions L enabled for the Node. Toggle buttons in the off state (empty) represent J those functions disabled for the Node. To enable a function, click on F the associated toggle button until that button is in the on state. K To disable a function, click on the associated toggle button until that 2 button is in the off state. The functions are:@ Address Enables the address watcher function. Enabling= Watcher this function allows the node to update its@ address identifier when a change of address is detected.D Disabling this function causes the state attributeE to be set to off, but the node can still respond to9 management through its C MIP interface. = CMIP Enabled automatically by the software. ThisD Listener function permits the node to respond to management7 through its CMIP listener interface. K Once you have determined that all the toggle buttons are in their properI states, press the CONTINUE button to cause the appropriate enable and K disable commands to be issued. Or press the CANCEL button to cancel theG operation. In either case, you will be returned to the main window. 2 Getnif3 FDDI 4 Station5 Link =title Getnif FDDI Station Link < Causes the link subentity to transmit a SMT NIF (NeighborC Information) request frame and await the response. If a response is received, it is displayed.@ getnif [node node-id] fddi station station-name link link-id0 target lan address timeout integer-16 6 Arguments o target$ 48-bit LAN address of the target. o timeout( Value: 1-65535! Timeout, in seconds, optional. 2 Getsif3 FDDI 4 Station5 Link =title Getsif FDDI Station Link ; Causes the link subentity to transmit a SMT SIF (StationC Information) request frame and await the response. If a response if received, it is displayed.8 getsif [node node-id] fddi station station-name link= link-id target lan address timeout integer-16 typeF configurationB  operation 6 Arguments o target$ 48-bit LAN address of the target. o timeout( Value: 1-65535! Timeout, in seconds, optional. o type; Value: Configuration or operation. SIF configuration or SIF operation request. 2 Limit3 HDLC4 Link5 logical_station'=title Limit HDLC Link Logical Station A Limits the specified HDLC Link Logical Station exclusively to  unsequenced data service.2 Load3 MOP 4 Circuit=title Load MOP Circuit? Initiates a downline load from the node you are managing to C a target system. If you optionally chose to enter a Client nameG in the previous menu, the default load parameters for this operationH were obtained by looking up the information for that MOP Client, and 9 those parameters are present in the current display. 6 The required arguments for this load operation are:  o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit J The MOP circuit you have currently selected for the load operation.7 The optional arguments for this load operation are: o Client  I A client entity to be used for this operation, if you provided one in the previous display. o Management Image B A file containing initialization data for the node; data is F encoded in a product-specific format. (Also see the script fileE argument.) This argument may be required by the target system.  o Script FileB A file containing initialization data for the node; data isC encoded as a sequence of network management commands in CMIPH form. (Also see the management image argument.) This argument may( be required by the target system. o Secondary Loader E Specifies the name of a second file containing the software toF be downline loaded. This argument may be required by the target system.  o System ImageD Specifies the file containing the system image to be downlineH loaded. This argument is required for LAN circuits. If you do notH supply this information as an argument for this command, you mustG specify a client set of parameters to provide this data. See the client argument. o Tertiary Loader D Specifies the name of a third file containing the software toF be downline loaded. This argument may be required by the target system.  o Verification  K Is a hex string that must match a verification code at the receivingE system in order to trigger the bootstrap mechanism so that theK downline load can be performed. The default is '0000000000000000'H,$ or %x00-00-00-00-00-00-00-00. H Pressing the OK button will cause the load command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No load command will be issued.  4 Client=title Load MOP Client? Initiates a downline load from the node you are managing to  a target client system. 6 The required arguments for this load operation are: o AddressJ The LAN address of the target node on circuit named in the circuit  argument.  o Circuit A The MOP circuit over which the load operation is to occur.7 The optional arguments for this load operation are: o Management Image B A file containing initialization data for the node; data isF encoded in a product-specific format. (Also see the script fileE argument.) This argument may be required by the target system.  o Script FileB A file containing initialization data for the node; data isC encoded as a sequence of network management commands in CMIPH form. (Also see the management image argument.) This argument may( be required by the target system. o Secondary Loader E Specifies the name of a second file containing the software toF be downline loaded. This argument may be required by the target system.  o System ImageD Specifies the file containing the system image to be downlineH loaded. This argument is required for LAN circuits. If you do notH supply this information as an argument for this command, you mustG specify a client set of parameters to provide this data. See the client argument. o Tertiary Loader D Specifies the name of a third file containing the software toF be downline loaded. This argument may be required by the target system.  o Verification  K Is a hex string that must match a verification code at the receivingE system in order to trigger the bootstrap mechanism so that theK downline load can be performed. The default is '0000000000000000'H,$ or %x00-00-00-00-00-00-00-00. H Pressing the OK button will cause the load command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No load command will be issued.  2 Loop3 Loopback_application =title Loop Loopback Application> Starts a loop test between the loopback applications on the; specified source and destination nodes. The node keyword? specifies the node from which the loop messages are sent. If@ you omit this keyword, the test is performed from the node onA which you issue the loop command. The name or address argument> specifies the node whose loop mirror is used to reflect the> messages back to the originator. Specify either the name or address (but not both).? address tower-set; count integer? loop [node node-id] loopback application format hex-string<  length integer< name full-name4 Characteristicso address tower-set? Number of the destination for loopback messages, in the form@ of a protocol tower. Specify either this argument or the name argument. o count integer- Default: 1 Value: 0-4294967295B Number of loop messages to be sent to the loop mirror. The testC is complete when this number of loop messages has been reflected back by the loop mirror. o format hex-string& Default: 55 Value: 00-FF? Content of the data field of a loop message. Enter a pair of= hexadecimal digits. Each octet in the data field of a loop message has this value. o length integer( Default: 40 Value: 0-65534= Length, in octets, of the data field in each loop message. o name full-nameD DNS name of the node to which loopback messages are sent. Specify> either this argument or the address argument, but not both.3 MOP 4 Circuit=title Loop MOP CircuitE Performs a loop operation with another system. If you optionally G chose to enter a Client Name in the previous menu, the default loop A parameters for this operation were obtained by looking up the H information for that MOP Client, and those parameters are present in  the current display. 6 The required arguments for this loop operation are: o AddressF  The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit J The MOP circuit you have currently selected for the loop operation.7 The optional arguments for this loop operation are: o Client  I A client entity to be used for this operation, if you provided one in the previous display. o Count D An integer representing the number of messages to be looped. < On failure of the loop test, a the count of messages - successfully looped will be displayed.  o Format E Value of each byte in the test data part of each loop message.7 The default results in alternating 0 and 1 bits.  o Length F Integer representing length of the test data part of each loop G message. The maximum and minimum permitted values depend on the # particular data link in use. o Assistance Type E Degree of loopback assistance required, for LAN circuits only.: Valid values are none, transmit, receive, and full.  o Assistant Address F LAN address to be used as a loopback assistant. The involvementE of the assistant depends on the assistance type parameter. ForF assistance of type none, no assistant is needed, and is ignoredG if specified. For other values, an assistant is required. If notG specified, an assistant is located by first sending a request to0 the loopback assistant multicast address.  o Assistant System H A MOP Client entity, from which an assistant address is obtained.? Meaningful for LAN circuits only, see assistant address. H Pressing the OK button will cause the loop command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No loop command will be issued.  4 Client=title Loop MOP Client> Performs a loop operation with the specified client system.6 The required arguments for this loop operation are: o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit I The MOP circuit over which this loop operation is to be performed.7 The optional arguments for this loop operation are: o Count D An integer representing the number of messages to be looped. < On failure of the loop test, a the count of messages - successfully looped will be displayed.  o Format E Value of each byte in the test data part of each loop message.7 The default results in alternating 0 and 1 bits. o Length F Integer representing length of the test data part of each loop G mes sage. The maximum and minimum permitted values depend on the # particular data link in use. o Assistance Type E Degree of loopback assistance required, for LAN circuits only.: Valid values are None, Transmit, Receive, and Full.  o Assistant Address F LAN address to be used as a loopback assistant. The involvementE of the assistant depends on the assistance type parameter. ForF assistance of type none, no assistant is needed, and is ignoredG if specified. For other values, an assistant is required. If notG specified, an assistant is located by first sending a request to0 the loopback assistant multicast address. o Assistant System H A MOP Client entity, from which an assistant address is obtained.? Meaningful for LAN circuits only, see assistant address.H Pressing the OK button will cause the loop command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No loop command will be issued. 2 Query 3 MOP 4 Circuit=title Query MOP CircuitI Initiates an XID exchange between the system you are managing and the A system specified by the LAN Address below. If you optionally H chose to enter a Client Name in the previous menu, the default query A parameters for this operation were obtained by looking up the H information for that MOP Client, and those parameters are present in  the current display. 7 The required arguments for this query operation are: o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit H The MOP Circuit entity you have currently selected for the query  operation.8  The optional arguments for this query operation are: o Client  I A client entity to be used for this operation, if you provided one in the previous display. o SAPM An octet representing the Service Access Point (on the target system) . to which the XID message is to be sent.I Pressing the OK button will cause the query command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. K Pressing the CANCEL button will return you to the main window. No query command will be issued.  4 Client=title Query MOP ClientI Initiates an XID exchange between the system you are managing and the / system specified by the LAN Address below. 7 The required arguments for this query operation are: o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit I The MOP Circuit over which the query operation is to be performed.6 The optional argument for this query operation is: o SAPE An octet representing the Service Access Point (on the target 6 system) to which the XID message is to be sent.I Pressing the OK button will cause the query command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. K Pressing the CANCEL button will return you to the main window. No query command will be issued. 2 Rename3 Node=title Rename Node? Changes the node's name within the node and does not affectC the name server directly. It uses the new name and an immediateG "keep me here" transaction with the name servers which then update , themselves based on the node's new name.3 The node's new fullname is a required argument.E Pressing the CONTINUE button will cause the node to be renamed. F Pressing the CANCEL button will dismiss the window with no rename  action taken.2 Reset3 evd=title Reset Event Dispatcher4 outbound_stream-=title Reset Event Dispatcher Outbound StreamI Pushing the CONTINUE button resets the catchall, specific, and global B filters to the default value for the specified Event DispatcherF Outbound Stream entity. It causes these filters to be reset to the D values they had when the entity was created. It is equivalent to : setting the values for these filters to their defaults.G Pushing the CANCEL button dismisses the window, and no reset action is taken.4 Sink"=title Reset Event Dispatcher SinkI Pushing the CONTINUE button resets the catchall, specific, and global G filters to the default value for the specified Event Dispatcher SinkA entity. It causes these filters to be reset to the values theyC had when the entity was created. It is equivalent to setting the. values for these filters to their defaults.G Pushing the CANCEL button dismisses the window, and no reset action is taken. 2 Shutdown3 event_dispatcher =title Shutdown Event Dispatcher4 outbound_stream0=title Shutdown Event Dispatcher Outbound StreamC Pushing the CONTINUE button requests an orderly shutdown of the E connection between the specified Event Dispatcher Outbound Stream C entity and the sink partner. The shutdown directive attempts an C orderly shutdown of the connection in cooperation with the sink.C Pushing the CANCEL button dismisses the window, and no shutdown  action is taken.2 Test3 evd =title Test Event DispatcherE Pushing the CONTINUE button causes an event be logged to test the B entire event logging subsystem. This tests the complete event E logging system from entity to manager, causing the test requested  event to be logged.> Pushing the CANCEL button dismisses the window, and no test action is taken.3 MOP 4 Circuit=title Test MOP Circuit@ Initiates an XID test between the system specified by the LAN@ Address described below. If you optionally chose to enter a E Client Name in the previous menu, the default test parameters for G this operation were obtained by looking up the information for that I MOP Client, and those parameters are present in the current display. 6 The required arguments for this test operation are: o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit J The MOP circuit you have currently selected for the test operation.7 The optional arguments for this test operation are: o Client  I A client entity to be used for this operation, if you provided one in the previous display. o Count G An Integer representing the number of test messages to be sent.   o Format @ Value of each byte in the data part of each test message.7 The default results in alternating 0 and 1 bits.  o Length @ Integer representing Length of the data part of each testG message. The maximum and minimum permitted values depend on the # particular data link in use. o SAPE An octet representing the Service Access Point (on the target 6 system) to which the XID message is to be sent. H Pressing the OK button will cause the test command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No test command will be issued.  4 Client=title Test MOP Client 5 Circuit=title Test MOP Client Circuit@ Initiates an XID test between the system specified by the LAN Address described below. 6 The required arguments for this test operation are: o AddressF The LAN address of the target node on the circuit named in the  circuit argument.  o Circuit 7 The MOP circuit over which the test is to occur.7 The optional arguments for this test operation are: o Count G An integer representing the number of test messages to be sent.   o Format @ Value of each byte in the data part of each test message.7 The default results in alternating 0 and 1 bits.  o Length @ Integer representing Length of the data part of each testG message. The maximum and minimum permitted values depend on the # particular data link in use.  o SAPE An octet representing the Service Access Point (on the target 6 system) to which the XID message is to be sent. H Pressing the OK button will cause the test command to be executed and1 will return control back to the main window. K Pressing the RESET button will cause all the arguments to be reset back C to the state they were in when you first entered this display. J Pressing the CANCEL button will return you to the main window. No test command will be issued. 2 Testevent=title Test Event3 evd !=title Testevent Event Dispatcher4 outbound_stream1=title Testevent Event Dispatcher Outbound Stream?! Tests the filter action state for the specified event. This@! directive applies the filtering algorithm to the named eventE! instance returning the applicable FilterAction, and an indication=! of whether the search was resolved by the SpecificFilter,.! GlobalFilter, or CatchAllFilter attribute.>! testevent [node node-id] event dispatcher outbound stream;! simple-name event instance-name, event-name !5 Arguments !o event-nameE! Specifies all (for all events) or a specific event to be filtered(! for the specified class or instance. !o instance-name=! Specifies a full entity name, including the node name and"! including a specific instance. !5 Identifier !o nameD! Simple name assigned to the outbound stream when it was created. 4 Sink?! Tests the filter action state for the specified event. This@! directive applies the filtering algorithm to the named eventE! instance returning the applicable FilterAction, and an indication=! of whether the search was resolved by the SpecificFilter,.! GlobalFilter, or CatchAllFilter attribute.?! testevent [node node-id] event dispatcher sink simple-name/! event instance-name, event-name!5 Identifier !o name8! Simple name assigned to the sink when it is created. !5 Arguments !o event-nameE! Specifies all (for all events) or a specific event to be filtered(! for the specified class or instance. !o instance-name=! Specifies a full entity name, including the node name and"! including a specific instance. 2 UNLIMIT 3 HDLC4 Link5 logical_station(=title Unlimit HDLC Link Logical StationF Pressing the CONTINUE button will enable sequenced and unsequenced 2 data service for the specified Logical Station.E Pressing the CANCEL button will dismiss the window, and no Unlimit action will be taken. 2 Update3 session_control=title Update Session Control4 backtranslation_softlink6=title Update Session Control Backtranslation Softlink; Pushing the CONTINUE button will update a the specified # Backtranslation Softlink entity.C Pushing the CANCEL button will dismiss the window, and no update action will be taken. 4 tower_maintenance/=title Update Session Control Tower MaintenanceG Pushing the CONTINUE button updates the specified Tower Maintenance entity.C Pushing the CANCEL button will dismiss the window, and no update action will be taken. ww1 alias =title ALIASM The Alias module provides the means to define an alternate network address J which is shared by multiple nodes in the same VMScluster. This makes it K possible to treat a VMScluster, or several nodes within a VMScluster, as . though it were a single node in the network.M The alias entity is the top-level entity in the hierarchy belonging to the M Alias module. The entity is the root from which alias port subentities may be defined.2 port=title ALIAS PORTI An alias port entity provides the means to define an alternate network P address for this node, which is shared by other nodes in the same VMScluster. L When the alias port entity is enabled, this node becomes an active member ' of the VMScluster alias it specifies.L The first node in the VMScluster to create an Alias Port for a particular H alias address causes that alias to be created. Subsequent nodes which I create an Alias Port for the same alias establish connections ports to M that alias. The alias becomes active when the first node enables its Alias  Port for that alias.  K When a node enables an Alias Port, that node registers itself with other  members of the alias. 3 character$=title Characteristic Attributes SELECTION WEIGHTO The number of sequential incoming connects to be passed to this member N node in the round-robin sequence before proceeding to the next member N node in the sequence. A value of zero means this node is not eligible P to receive incoming connections to this Alias address. Selection Weight I is used to apportion incoming alias connections according to the O capacity of each Alias member. Nodes with greater capacity should have G larger values of Selection Weight, while local area VMScluster O satellites should generally have a value of zero. Values between 0 and  10 are suggested.L The NSP maximum transport connection value determines the number of N connections on an alias member. If the Alias Port is enabled, changingA the NSP maximum transport connection value has no effect.! OUTGOING DEFAULT!O! Set to the value true, this port name is used when making connections O! out of the VAXcluster. Only one alias can be the default for a system. 3 status=title Status Attributes NODE-IDA The 6-byte node id field in the Alias pseudo-node's NSAP. STATE6 Specifies the status of the alias port entity./ OFF - The alias port entity is disabled. ON - The alias port entity is enabled ww 1 csmacd=title CSMA-CDN A Carrier Sense Multiple Access with Collision Detection CSMA/CD Local Area I Network LAN provides high-speed communications channels for connecting F computers and other digital devices located within a moderate-sized C geographic area. Like other LANs, the CSMA/CD LAN falls between N long-distance, low-speed networks that carry data for hundreds or thousands J of kilometers, and specialized, high-speed intercommunications that are N generally limited to tens of meters. The CSMA/CD LAN is intended primarily K for use in such areas as office automation, distributed data processing, J terminal access, distributed systems, and other situations that require N economical connection to a local communication medium with sporadic traffic  at high-peak data rates.H The entities that constitute the CSMA-CD module are listed below. The L indentation indicates the hierarchical relationships between the entities. & CSMA-CD& Port) StationJ The CSMA/CD module incorporates the functions and operations defined in H the Ethernet Specification V2.0 and the ISO 8802-3 IEEE 802.3 CSMA/CD L Access Method and Physical Layer specification as well as parts of the ISOK 8802-1 IEEE 802.1 Addressing, Internetworking, and Network Management andK the ISO 8802-2 IEEE 802.2 Logical Link Control specifications. To this, L the CSMA-CD module adds features often needed by users of the Data Link. 5 A typical such Data Link user is the Network Layer.J The CSMA-CD entity is the top-level entity in the hierarchy of entities " belonging to the CSMA-CD module. 2 character$=title Characteristic Attributes VERSIONK Version number of the CSMA/CD Data Link architecture specification E to which the implementation conforms. You cannot modify this  characteristic.2 port=title CSMA-CD PortJ A CSMA-CD Port entity represents an access point to the service offered N by the CSMA-CD module. A client transmits and receives data through a port. H Ports are created and deleted by client use of open and close service  interface procedures.  3 counters=title Counter AttributesL Unless stated otherwise, counts include both normal and multicast traffic O and all protocol types, service access points SAPs, and protocol i dentifiers. MULTICAST OCTETS RECEIVEDL Number of multicast data octets that were successfully received and N made available to the port user. The count is the number of octets in K the CSMA/CD user data field and does not include MAC medium access N control, a sublayer of the CSMA/CD Data Link layer headers. Comparing L this count to the octets received count yields the gross percentage L of bandwidth that was consumed over time by multicas t PDUs received  by the port.  MULTICAST OCTETS SENTP Number of multicast data octets that were successfully sent through the L port. The count is the number of octets in the MAC user data field, H including any padding or length fields; it does not include MAC L headers. Comparing this count to the octets sent count yields the O gross percentage of bandwidth that was consumed over time by multicast & PDUs transmitted by the port.  MULTICAST PDUS RECEIVEDJ Number of multicast PDUs that were successfully received and made M available to the port user. Counted PDUs passed address and protocol P filtering and were received without errors. Comparing this count to the K PDUs received count yields a gross percentage of CSMA/CD usage for . multicast pdus received by this port.  MULTICAST PDUS SENTO Number of multicast PDUs that were successfully sent through t he port. N Comparing this count to the PDUs sent count yields a gross percentage ? of CSMA/CD usage for multicast PDUs sent by this port.  OCTETS RECEIVEDM Total number of MAC user data octets that were successfully received O and made available to the port user. Counted frames passed address and O protocol filtering for both individual and multicast MAC addresses and O were received without errors. The count is the number of octets in t he M CSMA/CD user data field plus any padding, Ethernet length fields, or I logical link control LLC header fields; it does not include MAC K headers. Adding the octets received count to the protocol overhead M calculated from the pdus received count yields the amount of CSMA/CD ; bandwidth consumed by frames received by the port.  OCTETS SENTM Total number of user data octets that were successfully sent through O the port. Th e count is the number of octets in the MAC user data field P including any padding or length fields; it does not include MAC headers.N Adding the octets sent count to the protocol overhead calculated from L the PDUs sent count yields the amount of CSMA/CD bandwidth consumed . over time by frames sent by the port.  PDUS RECEIVEDP Total number of PDUs that were successfully received and made available M to the port user. Counted PDUs passed address and protocol filtering E and were received without errors. The count provides a gross : measurement of incoming CSMA/CD usage by the port. PDUS SENTO Total number of PDUs that were successfully sent through the port. The L count provides a gross measurement of outgoing CSMA/CD usage by the port. UNAVAILABLE USER BUFFERSM Number of times that no user buffer was available at the port for an G incoming frame that passed all filtering for the port. Used in L conjunction with the PDUs received count, this counter can indicate 2 the rate of user buffer receive problems. 3 status=title Status Attributes CLIENTG Name specified by the data link user when the port was opened.  ETHERNET PROTOCOL TYPESN Set of Ethernet protocol types that are currently recognized for this  port.  LENGTH PRESENTN The data link adds a length field on transmit frames, and assumes the I presence of a length field and attempts to remove it on received K Ethernet frames. When false, the data link does not add and remove M length fields. This attribute is irrelevant for ISO 8802-3 formatted 2 frames, which always have a length field. = TRUE - The data link adds and removes length fields.D FALSE - The data link does not add and remove length fields. LLC SAP ADDRESSESL Set of individual and group logical link control LLC service access I point SAP addresses that are currently recognized for this port.  LLC SERVICE L Type of LLC logical link control PDU processing that is required on B the port as defined by the user when the port was opened. G CLASS 1 - The data link provides class 1, type 1 service.N USER-SUPPLIED - The user is responsible for handling the LLC protocol. MAC ADDRESSESL  Set of individual and multicast MAC medium access control addresses 5 that are currently recognized for this port.  RECEIVE MODEE Type of receive mode that is currently enabled for the port. H NORMAL - The port receives only those frames that meet the I normal address and protocol filtering requirements , requested by the user. L PROMISCUOUS - The port receives all frames regardless of format and #  MAC address.  SNAP PROTOCOL IDENTIFIERSN Set of subnetwork access protocol SNAP identifiers that are currently ! recognized for this port. STATIONO Name of the station associated with this port as specified by the user " when the port was opened. 2 station=title CSMA-CD StationK A CSMA-CD station entity manages a CSMA/CD controller. Wherever Phase IV Q DECnet manages a line, DECnet-Plus manages a station. Each station corresponds K to a particular logical link control LLC, medium access control MAC, and O physical attachment. The station name refers to the station managed by this command. 3 character%=title Charactersitics Attributes STATION BUFFERSK Number of receive buffers reserved for the station. You can modify > this characteristic only when the entity is disabled. 3 counters=title Counter AttributesP Unless stated otherwise, counts include both normal and multicast traffic and K all protocol types, service access points SAPs, and protocol identifiers. ALIGNMENT ERRORS O Number of times a received frame did not contain an integral number of  octets.  CARRIER CHECK FAILURESO Number of times the data link did not sense the receive carrier signal O or detected an error in the receive carrier signal during transmission  of a frame.# COLLISION DETE CT CHECK FAILURESN Number of times the collision detect test signal was not sensed after N a transmission. If this count approximates the number of frames sent, N either the collision detect circuitry is not working correctly or the ( test signal is not implemented.  DATA OVERRUNSM Number of times the hardware lost one or more consecutive, partially H complete, incoming frames because it could not keep up with the J incoming frame rate. Used in conjunction with pdus received, this N count provides a measure of hardware resource and bandwidth failures.  EXCESSIVE COLLISIONSL Number of times a transmission failed because the maximum allowable H number of retransmission attempts all culminated in collisions.  FRAME CHECK ERRORSJ Number of times a received frame containing an integral number of 4 octets failed the frame check sequence FCS.  FRAME SIZE ERRORSO Number of times the user requested transmission of a frame outside the $ range of valid frame sizes.  FRAMES TOO LONGM Number of times a received frame exceeded the maximum length allowed * by CSMA/CD medium access control. INITIALLY DEFERRED PDUS SENTN Number of times a PDU was deferred by the station access algorithm on D the first attempt at transmission, but was then transmitted L successfully without collision. Used in conjunction with PDUs sent, O this count measures the rate of CSMA/CD contention with no collisions.  LATE COLLISIONSM Number of times a collision was detected after the allotted time for collisions had expired.  MULTICAST OCTETS RECEIVEDM Number of multicast data octets that were successfully received. The N count is the number of octets in the CSMA/CD user data field and does M not include MAC headers. Comparing this count to the octets received N count yields the gross percentage of bandwidth that was consumed over ? time by multicast frames received by the local system.  MULTICAST OCTETS SENTO Number of multicast data octets that were successfully sent. The count J is the number of octets in the MAC user data field, including any L padding or length fields; it does not include MAC headers. ComparingK this count to the octets sent count yields the gro ss percentage of B bandwidth that was consumed over time by multicast frames ) transmitted by the local system.  MULTICAST PDUS RECEIVEDL Number of multicast PDUs that were successfully received. Comparing K this count to the pdus received count yields a gross percentage of B CSMA/CD usage for multicast PDUs received by this system.  MULTICAST PDUS SENTM Number of multicast PDUs that were successfully sent. Comparing this J  count to the pdus sent count yields a gross percentage of CSMA/CD 6 usage for multicast PDUs sent by this system. ! MULTIPLE COLLISIONS PDUS SENTK Number of times a PDU was successfully transmitted on the third or N later attempt by the station access algorithm after normal collisions M on previous attempts. Used in conjunction with pdus sent, this count N provides a measure of CSMA/CD media contention at a level where there N are coll isions and the backoff algorithm no longer works efficiently.  OCTETS RECEIVEDM Total number of MAC user data octets that were successfully received H from frames that passed address and protocol filtering for both K individual and multicast MAC addresses. The count is the number of I octets in the CSMA/CD user data field plus any padding, Ethernet E length fields, or LLC header fields; it does not include MAC K headers. Adding the octets  received count to the protocol overhead M calculated from the pdus received count yields the amount of CSMA/CD C bandwidth consumed by frames received by the local system.  OCTETS SENTJ Total number of user data octets that were successfully sent. The O count is the number of octets in the MAC user data field including any N padding or length fields; it does not include MAC headers. Adding the L octets sent count to the protocol overhead  calculated from the pdus M sent count yields the amount of CSMA/CD bandwidth consumed over time , by frames sent by the local system.  PDUS RECEIVEDL Total number of PDUs that passed address and protocol filtering and M were received without errors. The count provides a gross measurement O of incoming CSMA/CD usage by the local system; this information can be K used in conjunction with other counters to approximate the average M receive frame size or to determine the ratio of errors to successful  receives. PDUS SENTL Total number of PDUs successfully sent. The count provides a gross H measurement of outgoing CSMA/CD usage by the local system; this F information can be used in conjunction with other counters to N approximate the average transmit frame size or to determine the ratio / of errors to successful transmissions.  RECEIVE DATA LENGTH ERRORSP Number of times a frame was received with a length field value that was L invalid for the number of octets actually received by medium access  control.  SEND DATA LENGTH ERRORSO Number of times the user requested transmission of an 802.3 frame with I a length field value that was not valid for the number of octets  actually passed.  SINGLE COLLISION PDUS SENTI Number of times a PDU was successfully transmitted on the second I attempt by the station access algorithm after a normal collision K occurred on the first attempt. Used in conjunction with pdus sent, M this count provides a measure of CSMA/CD media contention at a level J where there are collisions, but the backoff algorithm still works  efficiently.  STATION FAILURESJ Number of times that the station self-testing procedures reported  failure. UNAVAILABLE STATION BUFFERSM  Number of times a complete, fully received PDU was discarded because M no station buffer was available. Used with pdus received, this count M provides a measure of receive problems related to the station buffer. UNAVAILABLE USER BUFFERSP Number of times no user buffer was available for an incoming frame that M passed all filtering for the port. Used in conjunction with the pdus J received count, this counter can indicate the rate of user buffer  receive problems. , UNRECOGNIZED INDIVIDUAL DESTINATION PDUSJ Number of times a received PDU with an individual destination MAC I address was discarded because there was no port with the correct J Ethernet protocol type, SNAP protocol identifier, or link logical % control SAP address enabled. + UNRECOGNIZED MULTICAST DESTINATION PDUSH Number of times a received PDU with a multicast destination MAC I address was discarded because there was no port with the correct J Ethernet protocol type, SNAP protocol identifier, or link logical % control SAP address enabled. 3 status=title Status Attributes ADDRESS FILTERSN All individual MAC addresses currently enabled by any of the ports on  the station.  COMMUNICATION PORT0 DECnet-Plus device name for the station. HARDWARE ADDRESSN Individual medium access control MAC address that was assigned during O manufacture of the communications hardware that is associated with the  station.  MAC ADDRESSN Current MAC address if any of the station. For more information about 5 the MAC address, refer to the enable command. RECEIVE MODEM Current receive mode for the station. Some stations may not support  all modes. N NORMAL - The station receives only those frames individual and M  multicast that meet the normal format, protocol, and 4 access control requirements.M ALL MULTICAST - The station receives all individual-addressed frames K that meet the normal format, protocol, and address I requirements, and all multicast-addressed frames J regardless of their format, protocol, and address  types. G PROMISCUOUS - The station receives all frames individual and J multicast regardless of format, Ethernet protocol G type, SNAP identifier, LLC SAP address, or MAC ! address. STATE) Operational state of the station.0 OFF - The station is disabled.E ON - The station is enabled and available for use.N FAILED - Either an attempt to enable the station failed during N  the self-test or the station was on and the data link G determined that the station would now fail the # self-test. N INITIALIZING - The station is currently being initialized and tested * by the data link. ww1 DDCMP =title DDCMPL The DDCMP module is a data link control procedure that ensures a reliable J data communication path between communication devices conn ected by data M links. DDCMP has been designed to operate over full-duplex and half-duplex N synchronous and asynchronous channels in both point-to-point and multipoint J modes. It can be used in a variety of applications such as distributed B computer networking, host/front end processing, remote terminal < concentration, and remote job entry-exit system operation.J The hierarchical relationship of the entities that constitute the DDCMP module: DDCMP  Port Link& Logical stationH The DDCMP entity is the top-level entity in the hierarchy of entities belonging to the DDCMP module. 2 character$=title Characteristic Attributes DNA VERSIONL Version number of the DDCMP architecture specification to which the A implementation conforms. You cannot modify this characteristic. 2 ddcmp link=title DDCMP LINKM The DDCMP link entity defines the attributes of a link to a communications & port that uses the DDCMP protocol.   3 character$=title Characteristic Attributes DEAD TIMER > Default: 10000 Value: 1-65535 N 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.  DELAY TIMER ? Default: 0  Value: 0-65535 M Specifies the minimum delay, in milliseconds, between polls. You can H use this timer to limit the effect of a fast control station on slower H tributaries. A value of 0 means that no delay is added. This attribute E is supported only if the characteristic protocol is set to control.  PHYSICAL LINE I Default: No Name Value: local-entity-name O Name of the Physical layer entity that the link operat es over. A value H for this characteristic must be set before the link entity is enabled. E You can modify this characteristic only when the entity is disabled. PROTOCOL % Default: Point H Protocol mode used by the local station. You cannot modify this C characteristic. The value of this characteristic is a copy of the D protocol argument specified when the DDCMP link entity is created. > The default value is point and is the only permissible value. RECEIVE BUFFERS = Default: 4 Value: 1-255M Number of receive buffers reserved for the link. You can modify this E characteristic only when the entity is disabled. Also, you can only # increase the characteristic value. RETRANSMIT TIMER @ Default: 3000 Value: 1-65535M Maximum time, in milliseconds, to wait between sending a message and E receiving a valid response. If this time expires, the local station G takes error recovery action. On full-duplex point-to-point links, the 6 timer is started immediately when a message is sent.  SCHEDULING TIMER @ Default: 200 Value: 50-65535N Time, in milliseconds, between the recalculation of tributary polling D priorities. This attribute is supported only if the characteristic  protocol is set to control.  STREAM TIMER ? Default: 6000   Value: 0-65535N Time, in milliseconds, for which a tributary or the remote station on < a half-duplex, point-to-point link can hold the line. This D characteristic is not supported if the characteristic protocol is  set to tributary. 3 counters=title Counter Attributes8 NAKS RECEIVED INDICATING MESSAGE HEADER FORMAT ERRORO Number of NAK messages received that report errors in message headers  sent from the local station.!, NAKS RECEIVED INDICATING RECEIVE OVERRUNM Number of NAK messages received that report a receive overrun at the  remote station.2 PDUS RECEIVED WITH MESSAGE HEADER FORMAT ERRORI Number of times the local station detected an error in a message  header. RECEIVE OVERRUNSF Number of times the local station detected a receive overrun. SELECTION ADDRESS ERRORSL Number of times that the controller of a multipoint link r "eceived a C message with an address other than that of the currently selected G station. This counter is supported only if the characteristic protocol is set to control.  STREAMING TRIBUTARIESG Number of times that the remote station or a tributary station H exceeded the maximum transmission interval without releasing the line, G or failed to release the line after sending a message with the select G flag set. This counter is present only on half-duplex, point-to-point #H links, or when the local station is a controller of a multipoint link. E This counter is not supported if the protocol characteristic is set  to tributary.  TRANSMIT UNDERRUNSG Number of times the local station detected a transmit underrun. 3 status=title Status Attributes PHYSICAL PORTM Name of the port entity in the Physical layer returned when the port 2 is opened. If this is null, the port is not open. STATEN 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.B In addition the link is disabled and its state set to off if the 3 Physical layer port that the link uses is deleted. 2 logical!=title DDCMP LINK LOGICAL STATIONM The DDCMP Link Logical Station entity manages a link to a remote station. J The link name is the DDCMP link associated with the logical %station and 1 the station name refers to the logical station. 3 Character#=title Charateristics Attribute ACTIVE BASE = Default: 255 Value: 0-255N Base priority to which an active tributary is reset after it has been E polled. This characteristic is supported only if the characteristic < protocol of the owning ddcmp link entity is set to control. ACTIVE INCREMENT = Default: 0 & Value: 0-255I Value to be added to the active tributary priority each time the I scheduling timer expires. This characteristic is supported only if the C characteristic protocol of the owning ddcmp link entity is set to control. ADDRESS = Default: 1 Value: 1-255M Data link address of the remote station or tributary. You can modify 6 this characteristic only when the entity is disabled. BABBLE TIM 'ER ? Default: 6000 Value: 1-65535P Time, in milliseconds, for which a selected tributary or remote station H is allowed to transmit. This characteristic is not used on full-duplex C links. This characteristic is not supported if the characteristic > protocol of the owning ddcmp link entity is set to tributary. BUFFER SOURCE A Default: Implementation_specific Value: see below& Source of the receive buffer(s.D CLIENT SUPPLIED - Buffers are provided by the client entity.K COMMON POOL - Buffers are assigned from the common buffer pool.F This characteristic is supported only if the characteristic protocol C of the owning ddcmp link entity is set to control. You can modify 6 this characteristic only when the entity is disabled. DEAD THRESHOLD < Default: 8 Value: 0-255O Number of times that an active, inactive, or dyi )ng tributary is polled A before its status attribute polling substate is changed to dead G because of receive timeouts. This characteristic is supported only if D the characteristic protocol of the owning ddcmp link entity is set to control. DYING BASE = Default: 0 Value: 0-255N Base priority to which a dying tributary is reset after being polled. F This characteristic is supported only if the characteristic protocol 3 of th*e owning ddcmp link entity is set to control. DYING INCREMENT > Default: 16 Value: 0-255H Value to be added to a dying tributary's priority each time the E scheduling timer expires. This characteristic is supported only if D the characteristic protocol of the owning ddcmp link entity is set to control. DYING THRESHOLD > Default: 2 Value: 0-255M Number of times an active or + inactive tributary is polled before its B status attribute polling substate is changed to dying because of @ receive timeouts. This characteristic is supported only if the C characteristic protocol of the owning ddcmp link entity is set to control. HOLDBACK TIMER ? Default: 0 Value: 0-13000H Maximum time, in milliseconds, that the local station can delay I acknowledging a received message if there is no data to send. The value ,F of this characteristic is linked to the retransmit timer used on the I 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 F communications product. The default value indicates that no holdback < is used and the local station must acknowledge immediately. INACTIVE BASE < Default: 0 Value: 0-255P Specifies the priority to which an inactive tributary is- reset after it ? has been polled. This characteristic is supported only if the C characteristic protocol of the owning ddcmp link entity is set to control. INACTIVE INCREMENT < Default: 64 Value: 0-255L Value to be added to an inactive tributary's priority each time the H scheduling timer expires. This characteristic is supported only if the C characteristic protocol of the owning ddcmp link entity is set to control. IN.ACTIVE THRESHOLD ; Default: 8 Value: 0-255H Number of times an active tributary is polled before its status A attribute polling substate is changed to inactive because of no = data response. This characteristic is supported only if the C characteristic protocol of the owning ddcmp link entity is set to control. MAXIMUM BUFFERS L Default: 4 Value: Implementation specificK Maximum number/ of buffers that a tributary can use from the common I buffer pool. A value of 0 means that there is no limit to the number of H buffers that can be used. This characteristic is supported only if the : buffer source characteristic is set to common pool. This D characteristic is supported only if the characteristic protocol of E the owning ddcmp link entity is set to control. You can modify this E characteristic only when the entity is disabled. Also, you can only # increase the characterist0ic value. MAXIMUM TRANSMIT : Default: 4 Value: 1-255L Maximum number of messages that a tributary or a remote half-duplex H station can send at one time. The value of this characteristic must be B 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:J o The characteristic protocol of the owning ddcmp link entity is  1 set to tributary.F o The communications link is full-duplex and point-to-point. . You cannot modify this characteristic. POLLING STATE > Default: Automatic Value: see below M Specifies the effect of the local station's polling algorithm on the H state of a tributary. The value of this characteristic is reflected in 4 the value of the status attribute polling substate.+ ACTIVE - The state is locked to active.H2 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.F This characteristic is supported only if the characteristic protocol 3 of the owning DDCMP link entity is set to control. TRANSMIT TIMER ; Default: 0 Value: 0-65535I Time, in milliseconds, that the lo 3cal station waits between data > transmissions. This characteristic is supported only if the @ characteristic protocol of the owning ddcmp link entity is set to control. TRANSMIT WINDOW 9 Default: 1 Value: 1-255H Maximum number of data messages that the local station can send H without receiving an acknowledgment. This characteristic applies only C when the remote station is a control station or on a half-duplex, E point-to-point li4nk. The value of this characteristic must be less 9 than or equal to the equivalent of the maximum transmit : characteristic on the control station or remote station. 3 Counters=title Counter Attributes# BUFFERS TEMPORARILY UNAVAILABLEN Number of times the local station could not service messages from the @ remote station because there were no receive buffers available. BUFFERS TOO SMALLN Number of times the local station could not service me 5ssages from the B remote station because the receive buffers were not large enough. INCOMPLETE REPLIES TO SELECTM Number of selection intervals that were not properly terminated that F is, by a message with the Select bit set in the header, during which I a transmission was received or an attempt at transmission was detected. F This counter is supported only if the protocol characteristic of the C owning ddcmp link entity is set to control, or when the link is a # half-dupl6ex, point-to-point link.  LOCAL REPLY TIMEOUTSN Number of times the local station failed to receive an acknowledgment before the reply timer expired.# LOCALLY INITIATED STATE CHANGESO Number of times that the station protocol state changed through action  of the local station.- NAKS RECEIVED INDICATING BUFFER TOO SMALLN Number of times the remote station reported that it could not service ; a message because the receive buffer was not large 7enough.< NAKS RECEIVED INDICATING BUFFERS TEMPORARILY UNAVAILABLEN Number of times the remote station reported that it could not service 3 a message because no receive buffer was available.9 NAKS RECEIVED INDICATING DATA FIELD BLOCK CHECK ERRORM Number of times the remote station reported that a block check error 7 was detected in the data field of an incoming message.6 NAKS RECEIVED INDICATING HEADER BLOCK CHECK ERROR M Number of times the 8remote station reported that a block check error 9 was detected in the header block of an incoming message.* NAKS RECEIVED INDICATING REP RESPONSE L Number of times the remote station reported that it did not receive . all the messages sent from the local station. NAKS SENT WITH REP RESPONSE L Number of times that the local station detected that not all of the @ messages sent from the remote station were received correctly.  NO REPLIES TO SELECT O 9 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.N o No valid header to a maintenance message from the selected station  was received.: o No transmission from the remote station was received.C This counter is supported only if the protocol characteristic of B the owning ddcmp link entity is set to control, or when the link ( i:s a half-duplex, point-to-point link. 3 PDUS RECEIVED WITH DATA FIELD CHECK BLOCK ERRORI Number of messages received with a check error in the data field./ PDUS RECEIVED WITH HEADER BLOCK CHECK ERRORK Number of messages received with a check error in the header block.$ RECEIVE ERROR THRESHOLDS REACHEDJ Number of times that the receive error threshold has been reached. REMOTE REPLY TIMEOUTSM Number of times the local station ;received a REP message and sent an E acknowledgment in return. This sequence indicates that all messages ; sent from the remote station have been correctly received.$ REMOTELY INITIATED STATE CHANGESP Number of changes in the station protocol state caused by action of the  remote station. SDU OCTETS RECEIVED? Number of data octets received from the remote station. SDU OCTETS SENT9 Number of data octets sent to the remote station.< SDUS RECEIVEDO Number of data messages received from the remote station not including  retransmissions. SDUS SENTJ Number of data messages sent to the remote station not including  retransmissions.& SELECTION ERROR THRESHOLDS REACHEDL Number of times that the selection error threshold has been reached.E This counter is not supported if the characteristic protocol of the / owning ddcmp link entity is set to tributary.  SELECTION =INTERVALSH Number of times that the local station selected the remote or a E tributary station. The counter does not appear if the link uses the D tributary protocol. In addition, the counter appears only when the I local station is the control station for a number of tributaries, or is D operating over a half-duplex, point-to-point link. This counter is C supported only if the protocol characteristic of the owning ddcmp C link entity is set to control, or when the link is a half->duplex, point-to-point link.! SEND ERROR THRESHOLDS REACHEDG Number of times that the send error threshold has been reached.' STRTS RECEIVED WHILE IN MAINTENANCEH Number of times that the local station received a STRT protocol ) message while in the Maintenance state. 3 status=title Status Attributes POLLING SUBSTATEK State of a tributary as determined by the polling algorithm. This > attribute applies only when the v ?alue of the link's protocol B characteristic is set to control. The value of this attribute is C affected by the value of the characteristic polling state. If the A characteristic polling state is set to automatic, the value of A this status attribute reflects the current state of the polling F algorithm. For all other values of the polling state characteristic, , the values of both attributes are the same.G ACTIVE - The tributary is active and responds with data when  @ selected.J DEAD - The tributary did not respond when selected within the E appropriate timeout period, when already in the Dying or D Inactive state. The tributary will be ignored until the " station reinitializes.F DYING - The tributary, currently in the Inactive or Active state, D has not responded within the appropriate timeout period ! when selected.E INACTIVE - The tributary has not sent any datAa when selected by the G control station. However, the tributary has responded with 1 an appropriate message when selected. PROTOCOL STATE@ State of the data link protocol with the remote station.H HALTED - The protocol is stopped and no messages are being 8 exchanged with the remote station.B RUNNING - The protocol is on line and is exchanging messages . with the remote station.F STARTBING - There is an attempt to initialize the protocol between L the local and remote stations. This uses the STRT and " STACK PDUs. E MAINTENANCE - The protocol is off line and dealing with maintenance  messages only. STATE8 Operational state of the local logical station. & OFF - The station is disabled.% ON - The station is enabled.2 port=title DDCMP PORTH A DDCMP port entitCy represents an access point to the Data Link layer N service offered by ddcmp. Ports are created and deleted automatically when $ a client of DDCMP uses the link.  3 status=title Status Attributes CLIENT" Name of the client entity. LINK8 Name of the DDCMP link that the client is using. LOGICAL STATIONO Name of the DDCMP link logical station supplied by the client when the  port was opened. STATE StDate of the port. 2 OPEN - The port is assigned to a client.C OPEN DISABLED - The port is assigned to a client, but the link or E logical station entity used by the port is disabled.B CALL ATTACHED - The port is assigned to a client and the link is F associated with the current call on the line. AppliesB only when the link operates over a switched line. TYPE Type of port. 3 NORMAL - For normal data Ecommunications.K SERVICE - For service operations. This is the value that modules ww#1 EVD=title Event DispatcherG The Event Dispatcher is an integral component of the Digital Network L Architecture that processes events generated by entities in the network. J Each component layer architecture of the Phase V DNA architecture, such F as Routing, NSP, and OSI Transport, may define certain occurrences, J actions, transitions, or conditions as eveFnts that are reported and may J be logged to assist network or system management. The Event Dispatcher G module allows these conditions to be logged and monitored to allow a 4 system manager to view the state of the network.  J The hierarchical relationship of the entities that constitute the Event  Dispatcher module are:   Event Dispatcher Outbound Stream Relay Logging Sink Inbound Stream JG The Event Dispatcher entity is the top-level entity in the hierarchy of 6 entities belonging to the Event Dispatcher module.  2 character$=title Characteristic Attributes DNA VERSIONK Version number of the DNA event-logging architecture specification E to which the implementation conforms. You cannot modify this  characteristic. 2 counters=title Counter Attributes EVENTS LOST= Number of events lost at the Event DHispatcher queue. 2 status =title Status Attributes STATE/ Status of the Event Dispatcher Entity. 7 OFF - The Event Dispatcher entity is disabled. 6 ON - The Event Dispatcher entity is enabled. 2 outbound(=title Event Dispatcher Outbound Stream D An Event Dispatcher Outbound Stream entity represents an outgoing E connection to a sink on a local or remote node. An Outbound Stream G entity manages the connection to the sink, and iIt filters, processes,% and transmits events to the sink.  3 character$=title Characteristic Attributes CATCH ALL FILTER B Default: Pass Value: Pass or BlockL Action to take if neither the specific filter nor the global filter 1 contains an entry that matches an event. ! PASS - Report the event." BLOCK - Discard the event.  CONNECT RETRY TIMER < Default: 120 J Value: 0-65535J Number of seconds to wait after a disconnect or connection reject G before reattempting a connection. Connection attempts continue F until a connection is made or until the connect timer enabled I attribute is set to false or the Outbound Stream is disabled. If F the Outbound Stream is already connected to the sink when the J timer expires, no connection is attempted at that time. The timer K resets and conKnection attempts continue whenever the timer expires. ENABLE CONNECT TIMERB Default: True Value: True or FalseG Specifies whether the connect timer is operational see connect  retry timer.  DISCONNECT TIMER B Default: 0 Value: 0-4294967295K Number of seconds to wait before disconnecting an idle connection. I Zero indicates that there is no disconnect timer and connect Lions . are never automatically disconnected. ! GLOBAL FILTER !!L! Current global filter as it has been constructed by block, ignore, M! and pass commands for this stream. By default, the global filter is O! set to block all events for the following entities: Event Dispatcher, M! Event Dispatcher sink, and Event Dispatcher sink inbound stream and M! to pass all events for the Event Dispatcher Outbound Stream entity. ! M!! SINK ADDRESS M! Default: No address Value: sink address tower set!K! Sink address tower for this stream. Modifying this characteristic L! affects only subsequent connect requests; existing connections are ! unaffected.!! SINK END USER L Default: Number=82 Value: end-user-specificationD Sink session control end user specification for this stream. SINK NODE N ? Default: Local Node Value: Full-nameG Full DNS node name of the sink for this stream. Modifying this J characteristic affects only subsequent connect requests; existing H connections are unaffected. This fullname is used in combinationD with the sink end user characteristic to establish the sink  connection. SINK OBJECT @ Default: No Sink Object Value: Full-nameH Full DNS Oobject name of the sink for this stream. Modifying this J characteristic affects only subsequent connect requests; existing K connections are unaffected. This fullname should match the object / name characteristic of the target sink.! SPECIFIC FILTER $! Default: No specific filter!3! Current specific filter for this stream. 3 counters=title Counter Attributes CONFIDENCE CHANGESB Number of times the confidenceP variable has changed while , connections were in the open state.  CONNECT REQUESTSL Number of times a connection to a remote node was requested by this J stream, either by an explicit command or by the connection timer.   CONNECTIONS ACCEPTEDK Number of times an outbound connection request was accepted by the  sink partner. DISABLED1 Number of disable events for this stream. ENABLED0 Q Number of enable events for this stream.  EVENTS LOSTH Number of events lost because of Outbound Stream buffer overrun. FILTER CHANGES 0 Number of times the filter has changed. SHUTDOWNSC Number of times a shutdown command or operation was issued. 3 status=title Status Attributes BUFFER SIZEF Maximum number of octets allowed for event processing of this L stream. This value is defined in tRhe create command for the stream. STATE' Status of the Outbound Stream. 5 OFF - The stream is disabled.4 ON - The stream is enabled.K ONCONNECTED - The stream is enabled and has an established ) connection.I ONCONNECTING - The stream is enabled and is in the process; of establishing a connection.K ONDISCONNECTING - SThe stream is enabled, but is in the process A of disconnecting from a connection.K ONSHUTDOWNREQUESTED - The stream is enabled and has an established L connection, but is in the process of shutting H down; the stream will disconnect after it I transmits all events that were outstanding C when the shutdown command was issued.2 rTelay=title Event Dispatcher Relay C The Event Dispatcher Relay entity processes events from Phase IV J DECnet-Plus systems. It receives Phase IV format events and posts them ( into the DECnet-Plus logging system. 3 status=title Status Attributes STATE5 Status of the Event Dispatcher Relay entity. < ON - The Event Dispatcher Relay entity is enabled. = OFF - The Event Dispatcher Relay entity is disabled. 2 relay_log%=title EUvent Dispatcher Relay LoggingH Three Event Dispatcher Relay Logging entities are created and enabled J automatically whenever an Event Dispatcher relay entity is enabled. The I logging entities console, file, and monitor control the destination of E Phase IV events. Each logging entity can be disabled and reenabled I individually. All three logging entities are deleted automatically when( the Phase IV relay entity is disabled. 3 counters=title Counter AttributesV EVENTS RELAYED@ Number of Phase IV events relayed for this logging type. 3 status=title Status Attributes STATE= Status of the Event Dispatcher relay logging entity. > ON - The Event Dispatcher logging entity is enabled. ? OFF - The Event Dispatcher logging entity is disabled. 2 sink=title Event Dispatcher SinkD An Event Dispatcher Sink entity represents a Sink. A Sink manages H incoming connections and filters incominWg events. Each Sink maintains J a filter that is applied to all streams that are assigned to that Sink.  3 character%=title Characteristic Attributes  CATCH ALL FILTER F Default: Pass Value: Pass or BlockL Specifies the action to take if neither the specific filter setting F nor the global filter setting matches an event or if a filter ; setting that does match an event is set to Ignore. ! PASS - XReport the event." BLOCK - Discard the event. CLIENT TYPE B Default: Console Value: See belowM Specifies the application to accept the events received by the sink. F This can only be set when the Event Dispatcher sink entity is , disabled when the sink state is off.6 CONSOLE - Events go to the operator's console.G DEVICE - Events go to a device referred to by the device name ! Y characteristic.B FILE - Events go to a file referred to by the filename ! characteristic. DESCRIPTION E Default: Null Value: Latin1String' Application description string. DEVICE NAME E Default: Null Value: Latin1StringJ Name of the device to which events are going to be logged, if the * client type of the sink is devZice. DISPLAYUIDS @ Default: True Value: BooleanD A boolean value indicating whether to include the UIDs when  displaying an event.  END USER K Default: Number=82 Value: End-user-specifiedD Sink session control end user specification for this sink.   FILE NAME 9 Default: SYS$MANAGER:NET$EVD_SINK_(sinkname).LOG$ [ Value: File specificaitonG Name of the file to which events are going to be logged if the ( client type of the sink is file.! GLOBAL FILTER !L! Current global filter as it has been constructed by block, ignore, L! and pass commands for this sink. By default, the global filter is >! set to block all events for the following entities: !G! Event Dispatcher, Event Dispatcher sink, and Event Dispatcher E! sink in\bound stream. You cannot modify this characteristic.!! OBJECT NAME E Default: No Sink object Value: full-nameH Full DNS object name of the sink. Modifying this characteristic G affects only subsequent connect requests; existing connections  are unaffected. TEMPLATE G Default: No Template Value: Simple-name 7 Transport template for this sink's connections. ]  USER CLIENTO Default: Null Value: end-user specification  G Session control end user specification for a user program that ' has been set to receive events. ! SPECIFIC FILTER $! Default: No specific filter!M! Current specific filter setting as constructed by block, ignore and M! pass commands for this sink. You cannot modify this characteristic. 3 counters=tit^le Counter Attributes  CONNECTIONS ACCEPTEDK Number of times a sink connection request was accepted by the sink  partner. EVENTS FILTEREDF Number of events for this sink that were filtered by its sink  filter.  EVENTS LOST9 Number of events lost due to sink queue overflow. FILTER CHANGES0 Number of times the filter has changed. 3 status=title Status Attributes BUFFER SIZE_F Maximum number of octets allowed for event processing of this I sink. This value is defined in the create command for the sink. D This value is limited by the value specified in the maximum 4 buffer size argument of the create command. STATE Status of the sink. # OFF - The sink is disabled." ON - The sink is enabled. 2 sink_inb+=title Event Dispatcher Sink Inbound StreamG The Event Dispatcher Sink Inbound St`ream entity is the sink-side end J of the communication between an Event Dispatcher and a sink. An inbound J stream entity is dynamically created, enabled, disabled, and deleted in + tandem with the connection it represents. 3 counters=title Counter Attributes CONFIDENCE CHANGES A Number of times the confidence variable has changed while) connections were in the on state. 3 status=title Status Attributes SOURCE END USERF a Source end user specification, as provided by session control. SOURCE NODE NAME@ Name of the source node, as provided by session control. STATE, Status of the inbound event stream. . OFF - The stream is disabled.K ON CONNECTED - The stream is enabled and connected to the outbound  stream.wwP:1 FDDI =title FDDII The FDDI module implements one of multiple possible Link level/Net bwork 6 level modules in the OSI layered architecture model.D Fiber Distributed Data Interface FDDI is the basis for the second I generation of network interconnect architecture for Digital. The FDDI J module implements one of the multiple possible Link level/Physical levelJ modules in the OSI layered architecture model. The FDDI Physical level I includes high-speed, 125 megabaud, fiber optic links which may be many H kilometers in length. The FDDI Link level provides a high bandwcidth, D 100 megabits per second local area network LAN, and uses the ANSI  standard FDDI Token Ring.I The hierarchical relationship of the entities that constitute the FDDI module:  FDDI Port Station Link Phy PortK The FDDI module incorporates the functions and operations defined in the J ANSI FDDI Token Ring Media Access Control MAC, the ANSI FDDI Token Ring I Physical Layer Protocol dPHY, FDDI Physical Layer Medium Dependent PMD, K Station Management SMT specifications, parts of the ISO 8802-1 IEEE 802.1J Addressing, Internetworking and Network Management, and parts of the ISO< 8802-2 IEEE 802.2 Logical Link Control LLC specifications.G The FDDI entity is the top-level entity in the hierarchy of entities  belonging to the FDDI module. 2 character$=title Characteristic Attributes VERSIONK Version number of the FDDI architecture speceification to which the @ implementation conforms. You cannot modify this characteristic. 2 station=title FDDI STATIONK An FDDI Station entity represents an access point to the service offered J by the FDDI module. The FDDI data link can be monitored and controlled " through DNA network management.   3 character$=title Characteristic Attributes COMMUNICATION PORTK Name of the hardware port associated with this station, taken from G the corrfesponding argument in the create directive. You cannot # modify this characteristic. SMT MAXIMUM VERSION IDI Highest SMT version ID this station supports. You cannot modify  this characteristic. SMT MINIMUM VERSION IDL Lowest SMT version ID this station supports. You cannot modify this  characteristic. SMT STATION ID@ SMT station ID for this station. You cannot modify this  characteristic. SMT VERSgION IDL Currently active SMT version ID for this station. You cannot modify  this characteristic. TYPEB SMT station type for this station. You cannot modify this  characteristic. 3 counters=title Counter AttributesL Unless stated otherwise, counts include both normal and multicast traffic C and all protocol types, service access points SAPs, and protocol  identifiers. CONFIGURATION CHANGESL Number of times the inhternal configuration of this station changed. 4 Not present in single attached stations SAS. SELFTEST FAILURESK Total number of times a self-test of the station detected an error. TRACES RECEIVEDK Number of times the ECM state machine for this station entered the 3 trace state due to a received trace signal. 3 status=title Status Attribtues LAST SET STATION IDA The station ID of the station that last performed ani SMT . Change/Add/Remove PMF frame operation. STATE) Operational state of the station. 2 sta_link=title FDDI Station LinkK The FDDI Station Link entity is a subentity of the FDDI Station entity. J The FDDI Station link subentity provides the management view of LLC and F the FDDI MAC. FDDI allows stations to be either single MAC or dualE MAC and therefore there can be up to two link subentities for each C station. In most cases, a station has at ljeast one link entity. G Concentrators may have no link entity and are not addressable on the ? FDDI, though they may be using other communications channels. 3 character$=title Characteristics Attribute LINK ADDRESSE MAC address assigned during manufacture of the communication ? hardware that is associated with the station read-only. REQUESTED TRT : Default: None Value: 8' Requested token rotaktion timer. RESTRICTED TOKEN TIMEOUT = Default: None Value: 10002 Length limit of a restricted token dialog. RING PURGER ENABLE @ Default: None Value: BooleanJ Controls whether this station is eligible to be a ring purger and 7 should participate in the ring purger election. VALID TRANSMISSION TIME < Default: None Value: 3.4l Valid transmission time. 3 counters=title Counter Attributes BLOCK CHECK ERRORSJ Number of times a received frame containing an integral number of $ octets failed the FCS check. DIRECTED BEACONS RECEIVEDF Number of times the link detected the directed beacon process.# DUPLICATE ADDRESS TEST FAILURESL Number of times the duplicate address test failed detected that the % link address was a duplicate.m DUPLICATE TOKENS DETECTEDK Number of times the MAC address test failed detected that the link address was a duplicate. ERROR COUNTG Total number of frames that were in error with the E indicator F reset, indicating that the error occurred between the upstream MAC and this one. FCI STRIP ERRORSK Number of times a frame content independent strip operation bridge 3 strip was terminated by receipt of a token.n FRAME COUNTD Total number of frames seen by this link, other than tokens. FRAME STATUS ERRORSE Number of times a received frame had the E indicator in error/ missing or set and the FCS was correct. LOST COUNT Counter lost count. MULTICAST OCTETS RECEIVEDK Number of multicast data octets that were successfully received in I multicast frames of type LLC, implementer, reserved, or SMT. The 0 count odoes not include the MAC envelope. MULTICAST OCTETS SENT O Number of multicast data octets that were successfully sent in F multicast frames ot type LLC, implementer, reserved, or SMT. 4 The count does not include the MAC envelope. MULTICAST PDUS RECEIVEDK Number of multicast frames that were successfully received of type + LLC, implementer, reserved, or SMT. MULTICAST PDUS SENTL Number of multicast pframes that were successfully sent of type LLC, & implementer, reserved, or SMT. OCTETS RECEIVEDF Number of octets successfully received in frames of type LLC, J implementer, reserved, or SMT. The count does not include the MAC envelope. OCTETS SENTB Number of octets successfully sent in frames of type LLC, J implementer, reserved, or SMT. The count does not include the MAC envelope. PDU LENGTH ERRORSK q Number of times a received frame had an invalid length, either too K long or short for the type, or had an alignment error odd number of symbols. PDUS RECEIVEDF Number of frames successfully received in frames of type LLC, & implementer, reserved, or SMT. PDUS SENTB Number of frames successfully sent in frames of type LLC, & implementer, reserved, or SMT. RECEIVE DATA OVERRUNSH Number of times the hard rware lost one or more consecutive, only L partially complete incoming frames because it was unable to keep up L with the medium rate. An example is overrun of a bit or octet FIFO E queue because of inability to copy data from adapter to host I promptly. In conjunction with total frames received, provides a < measure of hardware resource and bandwidth failures. RING BEACONS INITIATEDK Number of times the ring beacon process was initiated bys this link." RING INITIALIZATIONS INITIATEDK Number of times a ring reinitialization was initiated by this link.! RING INITIALIZATIONS RECEIVEDL Number of times a ring reinitialization was initiated by some other link. RING PURGE ERRORSL Number of times the ring purger received a token while still in the  ring purge state. TOKEN COUNT; Number of times a token has been seen by this link. TRACESt INITIATEDH Number of times the pc_trace process was initiated by this link. TRANSMIT FAILURESI Number of times a transmit error, other than underrun, occurred. E This does not include errors in transmitting MAC type frames. TRANSMIT UNDERRUNSJ Number of times a transmit underrun occurred. This indicates the = transmit FIFO became empty during frame transmission. UNAVAILABLE LINK BUFFERSG Number of times a complete u, fully received frame was discarded I because no link buffer was available. In conjunction with total F frames received, provides a measure of station-buffer-related  receive problems. UNAVAILABLE USER BUFFERSK Number of times no user buffer was available for an incoming frame F that passed all filtering for the port. These are the buffersJ supplied by users on receive requests. In conjunction with total K frames received, provvides a measure of user-buffer-related receive  problems., UNRECOGNIZED INDIVIDUAL DESTINATION PDUSL Number of times a received LLC frame with an individual destination E MAC address was discarded because there was no port with the E Ethernet protocol type, SNAP protocol identifier, or LLC SAP K address enabled. Only frames containing individual destination MAC addresses are counted.+ UNRECOGNIZED MULTICAST DESTINATION PDUSJw Number of times a received LLC frame with a multicast destination E MAC address was discarded because there was no port with the E Ethernet protocol type, SNAP protocol identifier, or LLC SAP F address enabled. Only frames containing multicast destination# MAC addresses are counted. 3 status=title Status Attributes DOWNSTREAM NEIGHBOR9 MAC address of the downstream neighbor, if known. DUPLICATE ADDRESS FLAG? x Summary output of the duplicate address test algorithm. FRAME STRIP MODE0 Current frame stripping mode of the MAC.E SA MATCH - Source address match mode of the frame stripping F algorithm matches the source address of the frame E with the MAC's MyLongAddress MLA, and if a match G is found, the frame is removed from the token ring.> FCI STRIP - The FCIS mode counts the number of frames D y transmitted since the reception of a token, and 2 strips equal number of frames. LOOPBACKC This is true if the link has been set up to receive frames H transmitted by it. This allows loopback testing either on the 8 ring or with one of the PHY port loopback modes. NEGOTIATED TRT( Negotiated token rotation timer. OLD DOWNSTREAM NEIGHBOR2 Previous value of the downstream nzeighbor. OLD UPSTREAM NEIGHBOR0 Previous value of the upstream neighbor. RING ERROR REASON3 Reason code for the most recent link error.I DIRECTED BEACON RECEIVED - Link received particular beacon data.K DUPLICATE ADDRESS DETECTED - Duplicate address algorithm detected a 6 duplicate address.J DUPLICATE TOKEN DETECTED - A duplicate token was detected on the ) {ring.D FCI STRIP ERROR - Frame content independent strip D operation was terminated by the 7 receipt of a token.I NO ERROR - No errors have occurred on this ring.H PC TRACE INITIATED - PC-trace was initiated by this link.I PC TRACE RECEIVED - PC-trace was initiated by some other ) link.L RING BEACONIN|G INITIATED - Ring beaconing process was initiated by L this link. This process in initiated as K a result of serious ring failure, such K as loss of signal or jabbering station E transmitting in violation of the G protocol. This indicates to other K links on the LAN that corrective } action4 may be required.I RING INIT INITIATED - Ring initialization was initiated by I this link to initialize the ring and 3 create a token.I RING INIT RECEIVED - Ring initialization was initiated by K some other link to initialize the ring 7 and create a token.M RING OP OSC~ILLATION - Ring state has been continually changing E from operational to initializing.M RING PURGE ERROR - Link received a token while performing a 9 ring purge operation. RING LATENCY= Current ring latency as measured by this link entity. RING PURGER STATE2 State of the ring purger election process.K CANDIDATE - The Link's Ring Purger process is pa rticipating in the L Ring Purger election algorithm as a candidate to become $ the Ring Purger.G 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.E PURGER - The Link's Ring Purger process is performing the G function of removing no owner frames and duplicate E  token from the ring. In this state, the process ; transmits periodic Purger Hello frames. STATE! State of the link entity.D BROKEN - Attempt to turn the link on failed the F initialization test, or link was on, but 2 failure was detected.K OFF-READY - FDDI Data Link communication services are not ' available.I ON-RING INIT - Physical layer service is available and the 1 link entity enabled.L ON-RING RUN - Link detected that the Ring Initialization has I been successfully completed and the ring is ) operational.F OFF-FAULT RECOVERY - State entered when a link entity detects B conditions that indicate faulty ring. UPSTREAM NEIGHBOR ADDRESS7  MAC address of the upstream neighbor, if known., UPSTREAM NEIGHBOR DUPLICATE ADDRESS FLAGJ Upstream neighbor's reported result of its duplicate address test. 2 st_phy_prt=title FDDI Station PHY PortK An FDDI Station PHY Port entity provides the management view of the FDDI M Station PHY Port and the FDDI pmd. Each station has at least one PHY port L and a concentrator is a device that has at least one phy port of type M. K A dual-attached station or dual-attached concentrator has a phy port typeD A and type B. A single-attached station has a phy port of type B. 3 character$=title Characteristic Attributes  LEM THRESHOLD % Link error monitor threshold. PHY TYPE M Type of the physical port A, B, S, or M. This characteristic cannot  be set. PMD TYPE A Type of the PMD transceiver for this physical port. This % characteristic cannot be set.9 ANSI SONET - unshielded twisted-pair+ ANSI multimode - low power* ANSI multimode type 1 - thinwire7 ANSI single mode type 2 - shielded twisted-pair 3 counter=title Counters Attributes CONNECTIONS COMPLETEDF Number of times the PHY port entered the in use state, having - completed the initialization process. ELASTICITY BUFFER ERRORSI Number of times the elasticity buffer function had an overflow or underflow. LCT REJECTSM Number of times a connection was rejected due to failure of the Link A Confidence Test at either end of the physical connection. LEM REJECTSD Number of times an active connection was disconnected due toH rejection by the Link Error Monitor at this end of the physical 8 connection, or by expiration of the Noise timer. LINK ERRORSK Total number of raw link error input events seen by the Link Error  Monitor. 3 status=title Status Attributes BROKEN REASONH Reason phy port is in broken state, or if in broken state, none. ESTIMATED LINK ERROR RATE: Link error monitor current estimate of error rate. NEIGHBOR PHY TYPE, Status may be A, B, S, M or unknown. REJECT REASONH Reason the phy port is in a failed or watch state. This is not 8 meaningful when phy port is in some other state., NONE - No reason.L STANDBY - Physical port and its neighboring physicalL port form a redundant physical connection G dual-homing feature. In a dual-homed J configuration, the B to M connection is K the higher priority physical connection, K  and the A to M connection is the standby D physical connection. The standby L connection will become active if the B to 7 M connection is lost.J LOCAL LCT - Link Confidence Test failed on this end = of the physical connection.K REMOTE LCT - Link Confidence Test failed on the other A  end of the physical connection.L LEM REJECT - Error monitor disconnected this connectionJ due to the error rate exceeding the LEM , threshold.S NOISE REJECT - Noise timer expired because a single noise event B lasted for more than 1.31072 ms.F REMOTE REJECT - Neighboring physical port broke the C  connection for an unknown reason.L LCT BOTH SIDES - Link Confidence Test failed on both sides = of the physical connection.L TOPOLOGY REASON - Neighboring physical port's physical port L type is an illegal match for this physical< port's physical port type.G TRACE IN PROGRESS - Physical port was initializing when aF  pc-trace occurred. When a pc-trace K occurs, any physical ports that have not L yet established a physical connection are I shut down to prevent the topology from + changing.E LCT PROTOCOL ERROR - Neighboring physical port has been J detected to have prematurely exited the ;  link confidence test LCT.I TRACE RECEIVED-DISABLED - Physical port was momentarily disabled I because it received a pc-trace when itsK own pc-trace function was disabled. The L pc-trace function is enabled by default. K The trace disable switch is not remotely - manageable. STATE= Operationa l state of the phy port entity nonsettable.K IN USE - The physical port has established a connection F and is fully operational. Communications 7 services are now available.H BROKEN - The physical port has failed initialization ? tests and is not available for use.K WATCH - Same as starting, except the physical port has L failed to complete the last connection attempt. K Refer to the physical port's status parameter, H reject reason for the reason for connection M failure. Connection attempts will continue until ' successful.J FAILED - Same as waiting, except the physical port has L failed to complete the last connection attempt. J  Refer to the physical port's status parameter H reject reason for the reason for connection M failure. Connection attempts will continue until ' successful.J WAITING - The physical port is beginning to establish a J connection and is waiting for a response from : the neighboring physical port.K STARTING - The physical por t has received a response from L the neighboring physical port and is exchanging K information and performing the link confidence H test LCT prior to completing the connection.J OFF-READY - The physical port is waiting to be enabled or D has been disabled by management request.E INTERNAL LOOPBACK - The physical port has been configured to J  internally present all transmitted symbols to L the receive interface. The network connector isL inactive. This allows internally generated testG frames to be looped back for test purposes.2 port=title FDDI PortK An FDDI Port entity represents an access point to the service offered by I the FDDI module. A client transmits and receives data through a port. H Ports are created and deleted by client use of open and close service  interface procedures.  3 counters=title Counter Attributes MULTICAST OCTETS RECEIVEDG Number of multicast user data octets successfully received and ( available to the data-link user. MULTICAST OCTETS SENTL Number of multicast user data octets successfully transmitted using  the port. MULTICAST PDUS RECEIVEDJ Number of multicast frames successfully received and available to  the data-link user. MULTICAST PDUS SENTK Number of multicast frames successfully transmitted using the port. OCTETS RECEIVEDJ Number of user data octets successfully received and available to  the data-link user. OCTETS SENTK Number of user data octets successfully transmitted using the port. PDUS RECEIVEDI Number of frames successfully received and available to the data  link user. PDUS SENTA Number of frames successfully transmitted using the port. UNAVAILABLE USER BUFFERSH Number of times no user buffer was available at the port for an  incoming frame. 3 status=title Status Attribute CLIENT@ Name specified by the data link when the port is opened. ETHERNET PROTOCOL TYPESJ Set of Ethernet protocol types that are recognized for this port. M Protocol types for  a port may be enabled and disabled by the user at - any time during the port's existence. LENGTH PRESENTD Indicates whether the data link is to add a length field on H transmit, and both assume the presence of and remove the length L field on receive for Ethernet frames. This attribute is irrelevant K for ISO 8802-3 formatted frames because the length field is always J present. This is specified by the user when the port is opened. H  The value true means length fields are added and removed by the  data link. LINKK Name of the link subentity associated with this port, specified by ) the user when the port is opened. LLC SAP ADDRESSESM Set of SNAP protocol identifiers that are recognized for this port. L LLC SAP addresses for a port may be enabled and disabled by the user0 at any time during the port's existence. LLC SERVICEF LLC PD U processing the data-link user requires from the port, I specified by the user when the port is opened.This is either LLC L Class 1, where the entire LLC protocol is handled by the data link, J or user-supplied LLC, where the user is responsible for operating ! part of the LLC protocol. MAC ADDRESSESJ Set of individual and multicast MAC addresses that are recognized D for this port. MAC addresses for a port may be enabled and E disabled by the user at any time during the port's existence. RECEIVE MODEM Indicates if the port is to receive all frames regardless of format, K Ethernet protocol type, SNAP protocol identifier, LLC SAP address, L or MAC address. Promiscuous receipt is enabled and disabled by the 7 user. Support of promiscuous mode is optional. SNAP PROTOCOL IDENTIFIERSM Set of SNAP protocol identifiers that are recognized for this port. K Protocol identifiers for a port may be enabled and disabled by the 5 user at any time during the port's existence. TYPE Type of port LLC or SMT.wwR1 hdlc =title HDLCK The HDLC module implements one of the protocols in the Data Link layer. G The HDLC High-level Data Link Control protocol is intended to cover aI wide range of applications; for example, one-way, two-way alternate or I two way simultaneous data communication between data stations which areD usually buffered, including operations on different types of data K circuits; for example multipoint/point-to-point, duplex/half-duplex, and I switched/non-switched. This implementation uses HDLC to offer reliable K communication at the Data Link layer for point-to-point synchronous data L lines over a wide area network link. The HDLC module typically runs as a 3 Data Link module under the CLNS Network protocol.I The hierarchical relationship of the entities that constitute the HDLC module: HDLC Port Link! Logical StationH You must install the WAN device drivers before you can refer to these entities.G The HDLC entity is the top-level entity in the hierarchy of entities belonging to the HDLC module. 2 character$=title Characteristics Attribute VERSIOND Version of the HDLC architecture specification to which the @ implementation conforms. You cannot modify this characteristic.2 Link=title HDLC LinkK An HDLC link entity is associated with a port of the supporting physical L layer module. It contains attributes common to local HDLC operations for $ all logical stations on the line.  3 character#=title Characteristic Attribute ACKNOWLEDGE TIMER ? Default: 3000 Value: 1-60000 I Time, in milliseconds, to wait for an acknowledgment  before usingC error recovery procedures. The value of this characteristicF corresponds to the T1 parameter of HDLC. You can modify this 8 characteristic only when the entity is disabled. HOLDBACK TIMER ? Default: 0 Value: 1-60000J Maximum time to wait before sending an acknowledgment supervisory K frame if no other frames carry the acknowledgment. A value of zeroK means that the frame will be sent immediately if no I-frame can be I sent. You can modify this characteristic only when the entity is  disabled. LINK TYPE K Operational mode of the HDLC link. The value of this characteristic? is a copy of the link type argument specified when the A entity is created. You cannot modify this characteristic. MAXIMUM DATA SIZE A Default: 1500 Value: 262-65532I Maximum number of bytes that users of the data link can specify. L This number applies to both transmit and receive frames. The value J of this characteristic must be greater than or equal to the value A of the minimum data size characteristic. You can modify = this characteristic only when the entity is disabled. MAXIMUM UNSEQUENCED PDUS = Default: 1 Value: 1-127K Maximum number of unsequenced I-frames t hat a primary or secondary J station can send in a single transmission. This characteristic is = not used if the link type characteristic is balanced. MINIMUM DATA SIZE A Default: 576 Value: 262-65532I Minimum number of bytes that users of the data link can specify. K This number applies to both transmit and receive frames. The value J of this characteristic must be less than or equal to the value of C  the maximum data size characteristic. You can modify this 8 characteristic only when the entity is disabled. PHYSICAL LINE I Default: None Value: Local-entity-nameJ Local entity name of the the Physical layer entity over which the K HDLC protocol is to operate. This characteristic must have a valueL before the HDLC link is enabled. You can modify this characteristic* only when the entity is disabled.  PREFERRED CRC TYPE I Default: Either Value: 16-bit, 32-bit or EitherB CRC types available for negotiation. If the value of this J characteristic is either, the station will try to use 32-bit but H will use 16-bit if that is all that the remote station supports.' PREFERRED LOCAL STATION ADDRESS < Default: 2 Value: 1-253K Address proposed for the local logical station  during negotiation. H If there is no negotiation, the value of this characteristic is J the value that is used. If negotiation is necessary, the value of L this characteristic must be between 2 and 253. You can modify this 8 characteristic only when the entity is disabled." PREFERRED MAXIMUM DATA SIZE A Default: 1500 Value: 262-65532I Default size, in octets, of frames that the station receives and K tr ansmits. This value is used only if the link initialization does K not specify a buffer value. The value of this characteristic must H lie between those of the maximum data size and minimum data sizeI characteristics. You can modify this characteristic to a lower / value only when the entity is disabled. PREFERRED WINDOW SIZE = Default: 2 Value: 1-127J Window size to be offered during negotiation for b oth receive and M transmit frames. The value of this characteristic must be compatible : with that for the sequence modulus characteristic. PROFILE L Simple name that can be used when the HDLC protocol is dependent on I network subscription time commitments pertinent to the Data Link I layer. The value of this characteristic is a copy of the profileI argument specified when the entity is created. You cannot modify   this characteristic.  RECEIVE BUFFERS = Default: 4 Value: 1-128M Number of receive buffers reserved for the link. This characteristic F can only be set to a lower value when the entity is disabled.  RETRY MAXIMUM = Default: 10 Value: 1-255J Maximum number of times that a frame will be retransmitted before I the local station assumes that a fatal error has occurred. This H characteristic can be modified only when the entity is disabled. SEQUENCE MODULUS @ Default: 128 Value: 8 or 128L Whether modulo-8 or modulo-128 sequence numbering is allowed on the L HDLC link. The value 8 means that only normal sequence numbering is L allowed. The value 128 means that both extended and normal sequence 0 numbering are supported for negotiation. 3 counters=title Counter Attributes BUFFER UNAVAILABLE ERRORS K Number of times that the Physical layer reported that no buffer wasI available to hold a message. This counter is not supported in all implementations.  CRC ERRORS RECEIVED5 Number of frames received that had a bad CRC. TIMES PDU RECEIVE OVERRUNJ Number of times a physical line indicated an overrun condition to B the Data Link layer. This counter is not supported in all  implementations. TIMES PDU TRANSMIT FAILED? Number of times that an attempt to send a frame failed. UP TRANSITIONSM Number of times that the entity's status attribute state has changed  from off to on. 3 status=title Status Attributes ACTUAL SEQUENCE MODULUSI Sequence number modulus in use on the link. Until negotiation is M complete, this attribute has the value 128. However, if the value of M the characteristic sequence modulus is 8, the modulus always appears  as the value 8. INTERFRAME DELAYD Time required between frames to enable the local station to  successfully receive them. LINE TYPED Defines whether the underlying physical line is switched or F nonswitched. This status affects the subset of port states that are  related to a given link. MAXIMUM PDU SIZEI Maximum frame size in octets that can be used on the link. Until C negotiation is complete, the value of this status attribute is the? same as the characteristic preferred maximum data size. NEGOTIATED CRC TYPEM 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. PHYSICAL PORTC Name of the port in the Physical layer associated with the  communications link. RESPONSE ADDRESS@ Address that the remote station puts in response frames. STATEI State of the HDLC link. This reflects the last enable or disable  command issued.# OFF - The link is disabled." ON - The link is enabled. WINDOW SIZEE Maximum number of I-frames that can be outstanding before an E acknowledgment must be received. Until negotiation is complete, the A value of this status attribute is the same as the characteristic preferred window size. 2 logical =title HLDC Link Logical StationJ The HDLC Link Logical Station entity controls the characteristics of an L HDLC Logical Station. There is one station for each remote termination of J a line associated with the HDLC link. The link name is the link entity L within the HDLC module and the logical station name refers to the logical station. 3 Counters=title Counter Attributes DATA OCTETS RECEIVEDG Total number of octets received in the I-field of I-frames and F UI-frames. This total excludes protocol ID information in UI-frames  and frame retransmissions.  DATA OCTETS SENTB Total number of octets sent in the I-field of I-frames andC UI-frames. This total excludes protocol ID information in , UI-frames and frame retransmissions. DATA PDUS RECEIVEDK Total number of I-frames and UID-frames received. This number does 8 not include frames that had to be retransmitted. DATA PDUS SENTK Total number of I-frames and UID-frames sent. This number does not - include frames that had to be retransmitted. FRMRS GENERATED+ Number of FRMRs frame rejects sent. FRMRS RECEIVED/ Number of FRMRs frame rejects received. INVALID MODE COMMANDSH Number of command frames SABME, SABM, SNRME, SNRM,SARM, and SIM 2 received that are not applicable to this station. NEGOTIATION FAILURESM Number of times that the XID negotiation with the remote station has  failed. POLLS RECEIVED8 Number of frames received with the poll bit set. REJS RECEIVED. Number of REJ frames rejects received. REJS SENT* Number of REJ frames rejects sent. RNRS RECEIVEDL Number of RNR receive not ready supervisory frames received from the remote station. RNRS SENTG Number of RNR receive not ready supervisory frames transmitted.# TIMES ACKNOWLEDGE TIMER EXPIRED? Number of times that the acknowledge timer has expired. TIMES STATION HALTED= Number of times the station halt event has occurred.  TIMES STATION INITIALIZINGC Number of times the station initialized event has occurred. TIMES STATION INOPERATIVEC Number of times the entity's status attribute state became inoperative. TIMES STATION MAINTENANCEC Number of times the entity's status attribute state became maintenance. TIMES STATION RESETTING B Number of times that the station reset event has occurred. TIMES STATION RUNNING D Number of times that the station running event has occurred. TIMES STATION SETUP FAILED E Number of times the station setup failure event has occurred. UNKNOWN UI PDUS RECEIVED I Number of UI-frames the local station received whose protocol ID . does not match that of any open port.  XIDS RECEIVEDI Number of XID identification command or response frames received. 3 status=title Status Attributes COMMAND ADDRESSJ Address the local station uses when sending command frames to the  remote station. MAINTENANCE MODEJ Whether the station is in maintenance mode. When set to true, the C station will be used exclusively for maintenance operations. When = set to false, the station operates in normal fashion.A The limit command sets the value of this attribute to true, and  the unlimit to false.  PROTOCOL STATE) State of the data link protocol. L ERROR - A protocol error occurred. For instance, the logical : station received an invalid frame. K HALTED - The protocol could not start. For example, there is "  no client. 9 INITIALIZING - The protocol is being initialized.M INOPERATIVE - The protocol cannot be started because no contact has 9 been established with the remote station.B MAINTENANCE - The logical station is in maintenance mode.@ RESETTING - The protocol is resetting after an error.I RUNNING - The protocol is running and capable of exchanging 6 frames with the remote station. REMOTE VERSIONN Version number of the HDLC protocol that the remote station is using. D This is received as part of an XID message from the remote station. STATE% State of the logical station.F OFF - The logical station is off because of a disable command.E ON - The logical station is on because of an enable command.2 PORT=TITLE HDLC PortL The HDLC Port entity represents one end of an HDLC connection. The entity G maintains information about that link. Ports are created and deleted 6 automatically when a client of HDLC uses the link.  3 status=title Status Attributes CLIENT* Name of the client using the port. LOGICAL STATIONJ hdlc link logical station entity that the port is operating over.  PROTOCOL IDK Protocol ID that the port is using. For sequenced ports, this valueK is decided during negotiation. For unsequenced ports, the value is  sent in every UI-frame. STATE State of the port. A OPEN - The port is assigned to a client. If the I communications line is unswitched, data transfer K can begin. For switched lines, an association must M be made with the line before data transfer can begin.K OPEN DISABLED - The port is associated with a client, but the link K or logical station associated with it is disabled.  TYPE Type of port. B SEQUENCED - The port can send and receive sequenced and ' unsequenced data.J UNSEQUENCED - The port can send and receive unsequenced data only.wwqb1 mop =title MOPF The MOP module is located in the Application layer described by the J Digital Network Architecture. MOP has a direct connection with the Data L Link layer; thus, for cert ain functions, MOP can bypass the higher layers L in the DNA protocol tower. This is useful for nodes which do not yet haveE all the higher layers of DNA protocol towers installed. Functions I provided by the MOP module include down-line loading, up-line dumping,  and communications testing.K The hierarchy of MOP Module Entities is shown with indentation as follows:  MOP" Client# Circuit'  Operation% StationF The MOP entity is the top-level entity in the hierarchy of entities  belonging to the MOP module. 2 character$=title Characteristic Attributes SUPPORTED FUNCTIONSD MOP components supported on the system. This is a read-only  attribute. DUMP SERVER  LOAD SERVER LOOP REQUESTER QUERY REQUESTER CONSOLE REQUESTER   CONFIGURATION MONITOR VERSIONL Version number of the Maintenance Operations Protocol specification L to which the implementation conforms. This is a read-only attribute. 2 status=title Status Attributes STATE? State of the mop entity. This is a read-only attribute.) OFF - The mop entity is disabled.( ON - The mop entity is enabled. 2 circuit=title MOP CIRCUITH A MOP Circuit entity is a data link circuit on which MOP services are K available. The status attribute functions specifies the services enabled  on the circuit.  3 character$=title Characteristic Attributes KNOWN CLIENTS ONLY @ Default: False Value: BooleanL Specifies whether MOP attempts to service load requests from remote N systems which do not have a corresponding client entity. Some network O servers are designed to request specific sof tware by name, and in such N a case there is no need for a client entity to exist. By default, MOP O tries to process requests for named software from unknown clients. Set G this attribute to true if you wish MOP to ignore such requests.  LINK NAME M Default: No Name Value: Data Link entity nameL Name of a station entity in the Data Link layer module indicated by L the type characteristic. This name is passed to the Data Link layer 8 module when MOP opens a portal for the circuit.  RETRANSMIT TIMER < Default: 4 Value: 1-30M Time, in seconds, to wait for a response before retransmitting a MOP  protocol message.  TYPE H Specifies the circuit type. This characteristic is set when the J circuit is created see the create command. The possible types are J CSMA-CD, FDDI, HDLC OSF/1 loop only, DDCMP OpenVMS only, and LAPB < OpenVMS only. You cannot modify this characteristic. 3 counters=title Counter Attributes DUMP REQUESTS COMPLETEDE Number of dump service requests that completed successfully.  FAILED DUMP REQUESTSE Number of dump service requests that could not be completed.  FAILED LOAD REQUESTSE Number of load service requests that could not be completed.  LOAD REQUESTS COMPLETEDE Number of load service requests that completed successfully.  UNRECOGNIZED DUMP CLIENTSN Number of dump service requests that could not be processed because a ; required client database entry could not be found.  UNRECOGNIZED LOAD CLIENTSN Number of load service requests that could not be processed because a ; required client database entry could not be found. 3 status=title Status Attributes FUNCTIONSL Which optional MOP functions are currently enabled for this circuit. 2 circ_OPER=Title MOP CIRCUITJ The MOP Circuit operation entities are created automatically by MOP for J all operations, including those initiated by NCL action directives and M those initiated by automatic load and dump service. They are deleted when * the corresponding operation is complete. 3 status=title Status Attributes ADDRESSB For LANs only, specifies the address of the client system. CLIENTK Client name of the client entity associated with the operation, if  such an entity exists. OPERATIONM The operation being performed boot, dump, load, loop, query, or test. 2 cir_sta=title MOP CIRCUIT STATIOND The MOP Circuit Station entities are created automatically by the M Configuration Monitor. They are deleted when the circuit entity is deleted.J The Configuration Monitor function must be enabled to obtain the status ; information used by the show MOP Circuit Station command. 3 status=title Status Attributes COMMAND SIZEN Maximum acceptable console command size. A zero value means it is not  applicable. CONSOLE USERL LAN address of the system which currently has the console reserved; 0 all zeroes if the console is not in use. DATA LINK6 Data Link protocol used by the remote station. DEVICE@ Type of communication device used by the remote station. DSDU SIZEH Maximum allowed size for a MOP message, not including data link  protocol overhead. FUNCTIONSM The set of functions supported: loop server, dump requester, primary F loader, secondary loader, boot, console carrier, and counters. HARDWARE ADDRESSM Default data link address for the circuit on which the system ID was * transmitted by the remote station. LAST REPORTE Time at which the most recent system ID message was received.  MOP VERSIONL Highest version of the MOP protocol supported by the remote station. NODE IDF Node ID for the remote station. If not reported, the null ID ' 00-00-00-00-00-00 is displayed. NODE NAMEH Node name for the remote station, as a DECdns full name. If not G reported by the remote station, the null name is used; this is  displayed as "0:.". RESERVATION TIMERN Console reservation timer, in seconds. A zero values means it is not  applicable. RESPONSE SIZEO Maximum acceptable console response size. A zero value means it is not  applicable.  2 client=title MOP CLIENT L A MOP Client entity is a set of default characteristics used by these MOP L functions: dump/load server, load requester, loop requester, and console L requester. When a command or a request for one of these services does not L supply all of the required arguments, the values stored by the client are O used to perform the operation. The client-name refers to the client managed  by this command. 3 character$=title Characteristic Attributes ADDRESSES H Default: Empty Set Values: Set of LAN AddressM Set of LAN addresses for this client on the circuit specified by  the K circuit characteristic. Phase IV nodes can use an extended DECnet O LAN address in addition to their hardware address, so you must include G both of these addresses in the addresses set. To calculate the H 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  CIRCUIT > Default: No circuit Value: Circuit-idO Name of the MOP circuit that corresponds to the Data Link circuit that : is to be used for communicating with this client.  DEVICE TYPES G Default: No device type Value: Set of device typesL Specifies one or more device types associated with this clie nt. Use H device types and omit addresses if you want to set up a generic M client entity; the entity will be used for any incoming load or dump E requests that specify a matching communications device type. M To determine the communications device type for a particular network K server, consult the server documentation, or use the Configuration ! Monitor Function of MOP.  DIAGNOSTIC IMAGE J Default: No File  Value: Sequence of file specsN Files to be loaded when the client requests a diagnostic image during H a downline load operation. File identifications are interpreted 9 according to the file system of the local system. DUMP ADDRESS J Default: 1 Value: 0 - (2 to the 23rd -1)9 Memory address at which to begin an upline dump.  DUMP FILE J Default: No File Value: Sequence of file specsB Files to write to when the client is upline dumped. File L identifications are interpreted according to the file system of the  local system.  MANAGEMENT IMAGE J Default: No File Value: Sequence of file specsN Files to be loaded when the client requests a management image during H a downline load operation. File identifications are interpreted 9 according to the file system of the local system. PHASE IV CLIENT ADDRESS E Default: 0.0 Value: Phase IV AddressM Phase IV node address given to the client system when it is downline M loaded. This address is passed in a load parameters message; whether : it is needed depends on the software being loaded. PHASE IV CLIENT NAME B Default: No Name Value: Phase IV nameJ Phase IV node name given to the client system when it is dow nline N loaded. This name is passed in a load parameters message; whether it 7 is needed depends on the software being loaded.  PHASE IV HOST ADDRESS E Default: 0.0 Value: Phase IV addressK Phase IV node address to be passed as the host node address when a E client is downline loaded. This address is passed in a load O parameters message; whether it is needed depends on the software being  loaded.  PHASE IV HOST NAME B Default: No name Value: Phase IV nameN Phase IV node name that is passed as the host name when the client is K downline loaded. This name is passed in a load parameters message; B whether it is needed depends on the software being loaded.  SCRIPT FILE K Default: No File Value: Sequence of file specsJ Files to be loaded when the client req uests a CMIP initialization J script during a downline load operation. File identifications are E interpreted according to the file system of the local system. SECONDARY LOADER L Default: No File Value: Sequence of file specsN Files to be loaded when the client requests a secondary loader during I a downline load operation. File identifications are interpreted 9 according to the file system of the local system.  SYSTEM IMAGE L Default: No File Value: Sequence of file specsN Files to be loaded when the client requests an operating system image P during a downline load operation. File identifications are interpreted 9 according to the file system of the local system. TERTIARY LOADER M Default: No File Value: Sequence of file specsO Files to be loaded when the client requests a tertiary loader during a P downline load operation. File identifications are interpreted according / to the file system of the local system. VERIFICATION A Default: %X00-00-00-00-00-00-00-00 Value: Hex stringM 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. wwn1 node =title Node K The Node module has one entity, the global node entity, wh ich crowns the M hierarchy represented in the entity model described by the Digital Network L Architecture. All other entities are subordinate to the Node entity. When M enabled, each node is visible to all other nodes on the network. Access to 2 a node's entities must be made through the node.N The following shows the hierarchical relationship of the Node global entity % to all of the other local entities. Node- Event Dispatcher" Alias, Session Control* NSP Transport* OSI Transport$ Routing MOP$ CSMA-CD! FDDI" DDCMP! HDLC: The node entity is the only entity in the Node module. 2 character =title Characteristic Attributes IMPLEMENTATIONM Particular DECnet implementation of the node. You cannot modify this  characteristic. VERSIONO Version number of the network management architecture specification to C which the implementation conforms. You cannot modify this  characteristic.# MAXIMUM LISTENERS ( OSF/1 only) H Maximum number of CMIP listeners that the node supports. Zero M specifies an unlimited number of listeners. You cannot modify this G characteristic. The characteristic has no meaning on OPEN VMS # LISTENER_TEMPLATE ( OSF/1 only)J Name of the OSI transport template to be passed through the CMIP M listener to session control. You cannot modify this characteristic.  SECONDARY NAMES N Lists the set of secondary fullnames the node might have due to more  than one nameservice. 2 counters=title Counter Attributes CHANGES OF ADDRESS 8 Number of times the node's address has changed.  CHANGES OF ID 2 Number of times the node's ID has changed. IDROM CHECK FAILURES N Number of times an IDROM was checked for consistency and was found to  be in error. RENAMES L Number of times the node has been renamed. See the rename command. 2 status=title Status Attributes FUNCTIONS ENABLED K Functions that are currently enabled for the node. See the enable  command.  ID3 Indicates the unique 48-bit ID of the node. STATE State of the node. M BOOTING - The node is attempting to downline load. You cannot manage M the node in this state. If the boot process is successful, G the node enters the off state. This function is only ' supported on Ope nVMS.K DEAD - The node is unusable and unmanageable as the result of a M power failure or similar event. The node must be rebooted. = This function is only supported on OpenVMS.K OFF - The node is manageable, but not all of its functions are  enabled.K ON - All of the node's functions are enabled, and the node is O fully manageable. The on state is the normal operating state.  wwtc1 nsp =title NSPI The NSP module implements one of the protocols in the Transport layer 1 described by the Digital Network Architecture.O The entities that constitute the NSP module are listed below. The indention A indicates the hierarchical relationships between the entities. NSP Port# Local NSAP' Remote NSAP' NSP performs the followi ng functions:L o Enables the creation and destruction of transport connections used for F sending messages within a network node and between network nodes.L o Manages the movement of expedited and normal data from transmit buffers7 to receive buffers, using flow control mechanisms.I o Breaks up normal data messages into segments that can be transmittedO individually, and reassembles these segments into correct order after they have been received.I o Guarantees the delivery of data and control messages to a specified 5 destination using an error correction mechanism.= The NSP entity is the top-level entity in the hierarchy of ( entities belonging to the NSP module. 2 character#=title Charateristics Attribute" ACKNOWLEDGMENT DELAY TIME : Default: 3 Value: 0-65I Maximum amount of time in seconds that an acknowledgment is to be 7 withheld. You cannot modify this characteristic. CONGESTION AVOIDANCE = Default: True Value: BooleanM Enables the use of the automatic congestion avoidance mechanism. This O mechanism reduces the transport window size in response to an indication from the Network layer. DELAY FACTOR : Default: 2 Value: 2-15 L Factor by which to multiply the current value of the roundtrip delay A estimate status attribute in order to set a value for the  retransmission timer. L NOTE - the roundtrip delay estimate is an attribute of the nsp port  entity. DELAY WEIGHT ; Default: 3 Value: 0-255O Relative weighting to apply to the current estimate and to a new sample ' when estimating roundtrip delay. DNA VERSION M Version number of the DNA NSP architecture spec ification to which the G implementation conforms. You cannot modify this characteristic. KEEPALIVE TIME > Default: 60 Value: 1-65535M Time in seconds that NSP waits for data to be transmitted or received K before testing a transport connection. When this timer expires, NSP L sends a data request PDU to the remote NSP. This PDU does not change F the flow control parameters, but does require acknowledgment.  MAXIMUM RECEIVE BUFFERS > Default: 2000 Value: 1-65535P Maximum number of receive buffers that can store received transport PDUs.< You may not decrease the value while NSP is enabled.  MAXIMUM REMOTE NSAPS > Default: 201 Value: 1-65535K Maximum number of remote NSAPs that can exist concurrently. Must be L greater than the current value of maximum transport connections. You O can modify this characteristic to a lower value only when the entity is  disabled. % MAXIMUM TRANSPORT CONNECTIONS > Default: 200 Value: 0-65535K Maximum number of active transport connections allowed at one time. O Must not be less than the current value of maximum remote NSAPs. You may3 not decrease the value while NSP is enabled. MAXIMUM WINDOW = Default: 8  Value: 1-2047L Maximum credit window that can be granted on a transport connection. L This is used for control of the number of data segments PDUs allowed O to be transmitted over a particular transport connection before at leastO one acknowledgment must be returned from the destination system. If the K number of PDUs already transmitted equals the maximum window and no I corresponding acknowledgments have been received, transport stops C  sending PDUs over the transport connection and waits for an F acknowledgment message. You cannot modify this characteristic.  NSAP SELECTOR < Default: 32 Value: 0-256M NSAP selector used by the nsp entity when opening a port to a network 7 service. You cannot modify this characteristic. RETRANSMIT THRESHOLD > Default: 5 Value: 1-65535L Maximum number of times a source nsp entity is to restart an expired G retransmission timer before the remote node is to be considered K unreachable. When the threshold is reached, NSP sets the confidence  variable to false. 2 status=title Status Attributes CURRENTLY ACTIVE CONNECTIONS/ Number of active transport connections. STATE! Status of the nsp entity. ( OFF - The nsp entity is disabled.' ON - The nsp entity is enabled. 2 local_nsap=title NSP LOCAL NSAPL An NSP Local NSAP entity is automatically created for each NSAP address M used by the nsp entity. Local NSAPs are used primarily to group together < remote NSAPs see the nsp local nsap remote nsap entity.   DELETED REMOTE NSAPSJ Number of times a remote NSAP has been deleted in order to reclaim  resources.  NSAP ADDRESS > Address assigned to the local NSAP when it was created.   2 loc_rmt!=title NSP LOCAL NSAP REMOTE NSAPM An NSP local NSAP remote NSAP entity maintains the transport counters andL generates events resulting from interactions between its superior local M NSAP and a remote transport service. The local nsap nsap-address refers B to the local NSAP associated with the specified remote NSAP.  3 counter=title Counter Attributes CONNECTS RECEIVEDK Total number of connect initiated CI messages, regardless of their K disposition, that the local service provider has received from the ! remote service provider.  CONNECTS SENTG Total number of connect initiate CI messages, sent by the localC service provider to the remote service provider, including  retransmissions. DUPLICATE PDUS RECEIVED O Total number of all types of detected duplicate transport PDUs received ) from the remote service provider.  PDUS RECEIVED L Total number of all types of transport PDUs received from the remote 6 service provider excluding detected duplicates. PDUS SENT N Total number of all types of transport PDUs sent to the remote service * provider excluding retransmissions. REJECTS RECEIVED1 Number of detected reject received events. REJECTS SENT- Number of detected reject sent events. REMOTE PROTOCOL ERRORS7 Number of detected remote protocol error events. RETRANSMITTED PDUSM Total number of all types of retransmitted transport PDUs sent to the remote service provider.  TOTAL OCTETS RECEIVED O Total number of octets of all types of transport PDUs received from the L remote service provider, regardless of their disposition. This count $ includes detected duplicates. TOTAL OCTETS SENT I Total number of octets of all types of transport PDUs sent to the : remote service provider, including retransmissions. USER OCTETS RECEIVED I Total number of user data octets received from the remote service N provider, including normal, expedited, connect, accept, and disconnect P data. This count does not include duplicates such as data retransmitted ' by the remote service provider.  USER OCTETS SENTM Total number of user data octets sent to the remote service provider, O including normal, expedited, connect, accept, and disconnect data. This P count does not include data retransmitted by the local service provider.  USER PDUS DISCARDEDJ Number of PDUs received from the remote service provider that were 6 discarded because of insufficient buffer space. USER PDUS RECEIVEDM Total number of transport PDUs containing user data received from the N remote service provider, including normal, expedited, connect, accept, K and disconnect data. This count does not include duplicates such as C transport PDUs retransmitted by the remote service provider. USER PDUS SENTN Total number of transport PDUs containing user data sent to the remote K service provider, including normal, expedited, connect, accept, and M disconnect data. This count does not include retransmitted transport PDUs.2 port=title NSP PORTH An NSP Port entity represents one end of a transport connection and M maintains status information about that connection. A port is visible to E the network only when it is assigned to a transport connection. 3 counter=title Counter Attributes DUPLICATE PDUS RECEIVEDN Number of all types of detected duplicate transport PDUs received from $ the remote service provider.  PDUS RECEIVEDN Number of all types of transport PDUs received from the remote service / provider excluding detected duplicates. PDUS SENTH Number of all types of transport PDUs sent to the remote service + provider excluding retransmissions.  RETRANSMITTED PDUSN Number of all types of retransmitted transport PDUs sent to the remote  service provider.  TOTAL OCTETS RECEIVEDO Number of octets of all types of transport PDUs received from the remoteN service provider, regardless of their disposition. This count includes  detected duplicates.  TOTAL OCTETS SENTJ Number of octets of all types of transport PDUs sent to the remote 3 service provider, including retransmissions. USER OCTETS RECEIVEDM Number of user data octets received from the remote service provider, O including normal, expedited, connect, accept, and disconnect data. This K count does not include duplicates such as data retransmitted by the remote service provider.  USER OCTETS SENTG Number of user data octets sent to the remote service provider, N including normal, expedited, connect, accept, and disconnect data. ThisP count does not include data retransmitted by the local service provider.  USER PDUS RECEIVEDN Number of transport PDUs containing user data received from the remote K service provider, including normal, expedited, connect, accept, and G disconnect data. This count does not include duplicates such as C transport PDUs retransmitted by the remote service provider. USER PDUS SENTO Number of transport PDUs containing user data sent to the remote serviceN provider, including normal, expedited, connect, accept, and disconnect G data. This count does not include retransmitted transport PDUs. 3 status=title Status Attributes CLIENT NAMEB Name designated by the port user when the port was opened.  LOCAL NSAPC Local NSAP address being used for the transport connection.  LOCAL REFERENCEK Unique reference number assigned to the transport connection by the ) local transport service provider.  NETWORK PORT# Name of the port being used. REMOTE NSAPD Remote NSAP address being used for the transport connection.  REMOTE REFERENCEK Reference number assigned to the transport connection by the remote " transport service provider. ROUNDTRIP DELAY ESTIMATEP Amount of time, in milliseconds, of the roundtrip delay on the transport D connection. Applicable only when operating class 4 protocol.ww 1 options 2 changenode=title Change to Remote NodeL Change to Remote Node allows you to switch management control to another < DECnet-Plus node. The Node Name is a required argument. G Explicit access control information is optional. How ever, if it is L provided, the remote account must have at least the NET$EXAMINE right in M order to successfully switch management control. The NET$MANAGE right is M required on the remote account if you wish to make modifications, and the M NET$SECURITY right is also required if you wish to change Session Control  Application information. K If you do not provide explicit access control information, your rights L will be determined by the account associated with the CML Application on D the remote node, in other words, the rights of the remote node's  CML$SERVER account. P When you wish to return to managing the local node use "Change to Local Node"$ option from the Options pulldown. 2 chn_lcl=title Change to Local NodeJ Change to Local Node returns management control back to the local node.C Your original access rights will be used to access the NCL data.  2 default_actions=title Default ActionsL The Default Act ions display allows you to set display controls. The onlyK display option currently available is one which allows you to enable theE logging of NCL commands to the window where you originally invoked NET$MGMT. ww$41 osi=title OSI TRANSPORTH This module implements the OSI Connection-Oriented Transport Protocol H specification International Standard ISO 8073; and for DEC OSF/1, the L Connectionless-Mode Transport Service Protocol International Standard IS O L 8602. These protocols implement the OSI Reference Model Transport Layer 4. H These protocols, as well as the NSP protocol, implement the transport 0 protocols in the Digital Network Architecture.M The entities that constitute the OSI Transport module are listed below. The J indention indicates the hierarchical relationships between the entities.+ OSI Transport- Application % Port)  Template+ Local NSAP/ Remote NSAP J The Connection-Oriented Transport Service COTS provides transparent and O reliable transfer of data between Transport Service users. It operates over O the Network layer, and employs end-to-end protocols that enhance the inherent6 characteristics of the underlying network service. K The protocol is structured to produce protocol classes that minimize the K possible incompatibilities and implementation costs. A protocol class isO selected for a particular transport connection, based on the characteristics O of the network service to be used, the requirements of the Transport Service H user, and the availability of classes at the remote Transport Service provider.L This module implements class 0, class 2, and class 4 of the COTS protocol.J Class 0 is the simplest class. It sets up a network connection for eachN tr ansport connection requested, and assumes that the network connection doesL not make errors. The transport protocol does neither sequencing nor flow N control, as it relies on the underlying network layer to perform everything correctly.K Class 2, like class 0, is designed to be used over reliable networks. ItG differs from class 0 in that two or more transport connections may be/ multiplexed over the same network connection.G Class 4, the most complex of the protocols, is des igned to work over O unreliable Network Services. It can handle the error detection and recovery G of lost transport packets. These packets are called TPDUs Transport N Protocol Data Units. Class 4 runs over either CLNS or CONS. Classes 0 and  2 run only over CONS.N The Routing module provides a connectionless network service CLNS; for more , information, refer to the Routing chapter.L The X.25 Access module, if configured into the system, provides a reliable+ connection-oriented network service CONS. G The OSI Transport entity is the top-level entity in the hierarchy of 3 entities belonging to the OSI Transport module. 2 character%=title Characteristics Attributes!! CLNS CLASSES SUPPORTED B! Default: Class {4} Value: Bit-set!I! Set of protocol classes supported on the Connectionless Network =! Service CLNS. You cannot modify this characteristic.!! CONGESTION AVOIDAN CE A Default: True Value: Boolean K Enables the use of the automatic congestion avoidance mechanism to N reduce the transport window size in response to an indication from theJ Network layer when operating on the Connectionless Network Service CLNS.!! CONS CLASSES SUPPORTED B! Default: Classes {0,2,4} Value: Bit-set!M! Set of protocol classes supported on the Connecti on-Oriented NetworkM! Service CONS. You cannot modify this characteristic. See ,! kernel_config for more information.!!! CONS FILTERS N! Default: {} Value: set of simple names!Q! The names of X.25 Access module filters used to determine which inbound Q! network connection requests should be directed to the transport entity. M! You can modify this characteristic only when the entity i s disabled.!H! For each cons filter, there must be a corresponding x25 access K! template with the same name. One or more of these filters must be O! specified in order to run COTS over CONS. The X.25 access filter osi &! transport is typically used. ! !! CONS NSAP ADDRESSES P! Default: {} Value: Set of NSAP Addresses!N! The set of valid NSAP addresses for use with CONS. One or more NSAPs2! must be specified to run COTS over CONS. ! ! DELAY FACTOR ? Default: 4 Value: 2-15 N Factor by which to multiply the current value of the round-trip delay B estimate status attribute in order to set a value for the O retransmission timer. This attribute works with protocol class 4 only. DELAY WEIGHT @ Default: 5 Value: 0-255P  Relative weighting to apply to the current estimate and to a new sample M when estimating round-trip delay. This attribute works with protocol class 4 only. DISCONNECT HOLDBACK G Default: 0 Value: 0 - ( 2 to the 23 )N When operating over the Connection-Oriented Network Service CONS, the O length of the time to maintain a network connection for possible reuse F after all transport connections multiplexed upon it have been M disconnected. Specified in seconds. This characteristic may not be 7 changed while the transport entity is enabled.  ISO VERSION M Version number of ISO 8073 to which the implementation conforms. You * cannot modify this characteristic. MAXIMUM MULTIPLEXING = Default: 2 to the 23rd Value: 1 - ( 2 to the 23rd)M Maximum number of transport connections that can be multiplexed on a J sing le network connection operating over the cons. You can modify N this characteristic to a lower value only when the entity is disabled.N This attribute applies only if X.25 has been configured in the kernel." MAXIMUM NETWORK CONNECTIONS H Default: 2000 Value: 1 - ( 2 to the 23rd)F Maximum number of concurrent network connections that the OSI I transport protocol can use when operating over the cons. You can L modify thi s characteristic to a lower value only when the entity is  disabled. MAXIMUM MULTIPLEXINGN When operating over the Connection-Oriented Network Service CONS, the O maximum number of transport connections that can be multiplexed on any N single network connection. This characteristic can be increased only B when the transport entity is enabled. You can modify this J characteristic to a lower value only when the entity is disabled.   MAXIMUM NETWORK CONNECTIONS K When operating over the Connection-Oriented Network Service CONS, F the maximum number of network connections which can be in use G concurrently by DNA OSI Transport. This characteristic can be = increased only when the transport entity is enabled.   MAXIMUM RECEIVE BUFFERS O Maximum number of receive buffers that can store received DT transport I PDUs. You can modify this characteristic only when the entity is H disabled. Also, you can only increase the characteristic value.  MAXIMUM REMOTE NSAPSP Maximum number of remote NSAPs that can exist concurrently. This value D must be greater than the current value of maximum transport N connections. You can modify this characteristic to a lower value only P when the entity is disabled. This characteristic can be increased when  enabled.! MAXIMUM TRANSPORT CONNECTION SL Maximum number of active transport connections allowed at one time. M Must be less than the current value of maximum remote nsaps. You can L modify this characteristic to a lower value only when the entity is  disabled. MAXIMUM WINDOW@ Default: 8 Value: 1-65535 N Maximum credit window that can be granted on a transport connection. M This is used for control of the number of data segments  PDUs allowed K to be transmitted over a particular transport connection before at O least one acknowledgment must be returned from the destination system. L If the number of PDUs already transmitted equals the maximum window K and no corresponding acknowledgments have been received, transport J stops sending PDUs over the transport connection and waits for an N acknowledgment message. You can modify this characteristic to a lower / value only  when the entity is disabled. NSAP SELECTORA Default: 33 Value: 0-255 O The NSAP selector to use for the Connection-Oriented Transport Service P COTS when running over CLNS. If 0 or 1, COTS over CLNS is not enabled. O This attribute cannot be set to 32, which is the value of the NSP NSAP P selector. Or, on DEC OSF/1, to the current setting of the osi transport @ attribute cltp nsap selector if it i s other than 0 or 1.D This attribute cannot be modified when transport is enabled. SUPPORT MAP D Default: None Value; False L Specifies whether the implementation supports the MAP manufacturing J automation protocol entity. You cannot modify this characteristic. VERSIONN Version number of the DNA OSI Transport architecture specification to C which the implementation conforms. You cannot  modify this  characteristic. 2 status=title Status Attributes CURRENTLY ACTIVE CONNECTIONS0 Number of active transport connections. STATE, Status of the osi transport entity. 2 ON - The OSI transport entity is enabled.3 OFF - The OSI transport entity is disabled.2 app =title OSI TRANSPORT APPLICATIONK An OSI Transport Application entity stores information about an end user K that is activated  for receipt of an incoming connection request when the F request contains that end user's name in its Destination Name field. 3 character$=title Characteristic Attributes CALLED TSELSG Default: No tsap Value: Hex-stringM Transport Service Access Point TSAP for which the image specified by @ the image name characteristic accepts connections. This M characteristic, which is similar to the addresses characteristic, is N used by applications that do not use the DNA session control protocol ' for example, VOTS applications. FILE NAMEB Default: No File Name Value: FilenameI File name of the program to be invoked upon receipt of a connect M request containing a TSEL matching the Called TSELS attribute " of the application entity.! OUTGOING ALIASP! Specifies whether the application uses the alias node ident ifier in itsN! outgoing connection requests. If this attribute is set to DISABLED, M! the application must not use the alias node address in its outgoing ! connection requests.! ! OUTGOING PRIVILEGE REQUIREDP! Specifies whether the object must be privileged in order to initiate a K! connection to the remote application. If this attribute is set to .! DISABLED, no privileges are required.!! OUTGOING PROXYM! Specifies whether t o invoke a proxy on outgoing connection requests P! when the user does not explicitly specify to do so. If this attribute G! is set to DISABLED, no proxy is invoked. The setting of this N! characteristic overrides the setting of the SESSION CONTROL OUTGOING =! PROXY characteristic for the specified application. !! REQUEST VERIFYM! Specifies whether the application automatically verifies the source J! node name on non-proxy requests. If Fa lse, the application must O! request verification when required. The node name is always verified B! for proxy access, regardless of this attribute's setting.!! USERNAMEB Default: No user Name Value: UsernameP User name portion of the access control information that identifies the N account under which the application is to run. If invalid information M or no user name is specified, system defaults are used to select the user. 2 local_nsap=title OSI TRANSPORT LOCAL NSAPL An OSI Transport Local NSAP entity is automatically created for each NSAP K address used by the OSI transport entity. Local NSAPs are used primarily H to group together remote NSAPs see the OSI transport local NSAP remote NSAP entity.   DELETED REMOTE NSAPSO Number of times a remote NSAP has been deleted in order to reclaim the  resources.  NETWORK SERVICE+ Type of network service being used. NSAP ADDRESS- NSAP address corresponding to entity. 2 local_rmt+=title OSI TRANSPORT LOCAL NSAP REMOTE NSAPI An OSI transport local nsap remote nsap entity maintains the transport H counters and generates events resulting from interactions between its 7 superior local NSAP and a remote transport service.  3 counters=title Counter Attributes CONNECTS RECEIVEDL Total number of CR TPDUs, regardless of their disposition, that the 5 local NSAP has received from the remote NSAP. CONNECTS SENTL Total number of CR TPDUs sent by the local NSAP to the remote NSAP, " including retransmissions. DUPLICATE PDUS RECEIVEDO Total number of all types of detected duplicate TPDUs received from the remote NSAP.  FAILED CHECKSUMS3 Number of checksum failure events detected. LOCAL PROTOCOL ERRORSP Number of reported local protocol error events. This event is generated C whenever an ER error TPDU is received from the remote NSAP. PDUS RECEIVEDI Total number of all types of TPDUs received from the remote NSAP & excluding detected duplicates. PDUS SENTM Total number of all types of TPDUs sent to the remote NSAP excluding  retransmissions. REJECTS RECEIVED2 Number of detected reject received events. REJECTS SENT. Number of detected reject sent events. REMOTE PROTOCOL ERRORSH Number of reported invalid tpdu received events. This event is K generated whenever the remote NSAP violates the Transport Protocol. RETRANSMITTED PDUSL Total number of all types of retransmitted TPDUs sent to the remote  NSAP.  TOTAL OCTETS RECEIVEDN Total number of octets of all types of TPDUs received from the remote L  NSAP, regardless of their disposition. This count includes detected  duplicates. TOTAL OCTETS SENTN Total number of octets of all types of TPDUs sent to the remote NSAP, " including retransmissions. USER OCTETS RECEIVEDH Total number of user data octets received from the remote NSAP, P including normal, expedited, connect, accept, and disconnect data. This L count does not include duplicates such as data retransmitted by the  remote NSAP.  USER OCTETS SENTL Total number of user data octets sent to the remote NSAP, including M normal, expedited, connect, accept, and disconnect data. This count ? does not include data retransmitted by the local NSAP.  USER PDUS DISCARDEDI Number of PDUs received from the remote NSAP that were discarded - because of insufficient buffer space. USER PDUS RECEIVEDL Total number of TPDUs containing user data received from the remote K NSAP, including normal, expedited, connect, accept, and disconnect D data. This count does not include duplicates such as TPDUs * retransmitted by the remote NSAP.  USER PDUS SENTL Total number of TPDUs containing user data sent to the remote NSAP, P including normal, expedited, connect, accept, and disconnect data. This 3 count does not include retransmitted TPDUs.! !2 status!=title Status Attributes!!! NSAP ADDRESS!@! Address assigned to the local NSAP when it is created. !!!!!2 port=title OSI TRANSPORT PORTL An OSI transport port entity represents one end of a transport connection H and maintains status information about that connection. Although the K connectionless transport protocol does not create transport connections, 8 ports are still used to maintain status information. 3 Counters=title Counter Attributes DUPLICATE PDUS RECEIVEDP Total number of all types of detected duplicate TPDUs received from the : remote NSAP. This attribute applies only to COTS. FAILED CHECKSUM3 Number of checksum failure events detected. PDUS RECEIVEDI Total number of all types of TPDUs received from the remote NSAP ' excluding detected duplicates. PDUS SENTL Total number of all types of TPDUs sent to the remote NSAP excluding  retransmissions.  RETRANSMITTED PDUSL Total number of all types of retransmitted TPDUs sent to the remote  NSAP.  TOTAL OCTETS RECEIVEDN Total number of octets of all types of TPDUs received from the remote K NSAP, regardless of their disposition. This count includes detected duplicates.  TOTAL OCTETS SENTN Total number of octets of all types of TPDUs sent to the remote NSAP, " including retransmissions. USER OCTETS RECEIVEDH Total number of user data octets received from the remote NSAP, P including normal, expedited, connect, accept, and disconnect data. This L count does not include duplicates such as data retransmitted by the  remote NSAP.  USER OCTETS SENTL Total number of user data octets sent to the remote NSAP, including M normal, expedited, connect, accept, and disconnect data. This count ? does not include data retransmitted by the local NSAP.  USER PDUS RECEIVEDK Total number of PDUs containing user data received from the remote K NSAP, including normal, expedited, connect, accept, and disconnect C data. This count does not include duplicates such as TPDUs * retransmitted by the remote NSAP.  USER PDUS SENTL Total number of TPDUs containing user data sent to the remote NSAP, P including normal, expedited, connect, accept, and disconnect data. This 4 count does not include retransmitted TPDUs. 3 status=title Status Attributes ACKNOWLEDGMENT DELAY TIMEO Maximum amount of time, in seconds, that an AK TPDU is to be withheld. 8 This attribute applies to protocol class 4 only. CHECKSUMSM Indicates whether checksums are in use on the transport connection. > This attribute is supported only for class 4 protocol. CLIENTJ Name designa ted by the port user when the port was opened. If DNA O session control is being used, this is the name of the session control  port being used. ! CLNS INACTIVE AREA ADDRESS !K! Specifies the inactive area address used by the transport template$! associated with this port. !! CONS TEMPLATEK When operating over the CONS, the name of the X.25 Access module's O template specified when establishing the underlying network connecti!on. CR TIMEOUTO Amount of time, in seconds, to wait for a response to a CR TPDU before O assuming that the remote transport service provider will not respond. B This attribute is valid for protocol classes 0 and 2 only. DIRECTIONN Indicates whether the port is open to initiate an outgoing connection,H to receive an incoming connection, or is listening for incoming  connection requests.O INCOMING - Transport connecti"on initiated by remote transport service.? LISTENING - Listening for incoming connection requests.M OUTGOING - Transport connection initiated by this transport service.0 UNKNOWN - Port direction is not known. ER TIMEOUTI Amount of time, in seconds, to wait for a response to an ER TPDU M before disconnecting the network connection. This attribute is valid * for protocol classes 0 and 2 only. EXPEDITED DATAP Indi#cates whether the expedited data option is in use for the transport M connection. This attribute is supported only for class 2 and class 4  protocols. EXTENDED FORMATO Indicates whether the use of extended formats should be negotiated for H a transport connection which operates the class 2 or 4 protocol. INACTIVITY TIMEM Time, in seconds, being used for the inactivity timer. This value is G the product of multiplying the keepa$live time by the inactivityH factor architectural constant = 4. This attribute is valid for  protocol class 4 only. INITIAL RETRANSMIT TIMEM Time, in seconds, used for the retransmission timer when sending the N first TPDU on the transport connection. The value of this attribute N is derived from the template used when the port was initialized. This ( attribute applies to COTS only.   KEEPALIVE TIMEM Time, in seconds%, being used for the window timer. The value of this F attribute is derived from the template used when the port was H initialized. This attribute is valid for protocol class 4 only. LOCAL NSAPD Local NSAP address being used for the transport connection.  LOCAL REFERENCEL Unique reference number assigned to the transport connection by the O local transport service provider. This attribute applies to COTS only.  LOCAL TRANSPORT &SELECTOR0 Local transport selector for this port.  MAXIMUM NSDU SIZEM When operating over the CONS, the maximum NSDU size for transmitting P and receiving buffers. Expressed as a number of octets. This attribute  is valid for CONS only. NEGOTIATED TPDU SIZEO The TPDU size which was negotiated for this transport connection. This ) attribute applies to COTS only.  NETWORK PORT5 Name of the network service 'port being used.  NETWORK SERVICEG Type of network service over which the transport connection is L operating. Attribute value derived from the template used when the  port was initialized.  PROTOCOL CLASSM Protocol class operating on the transport connection. This attribute  is not valid for CLTS. REMOTE IDENTIFIERN Implementation identity and version of the remote NSAP. When present, G this value is rece(ived in the identification of implementation N parameter of the CR or CC TPDU. This attribute applies to COTS only.  REMOTE NSAPJ Remote NSAP address being used for the transport connection. This ( attribute applies to COTS only.  REMOTE REFERENCEL Reference number assigned to the transport connection by the remote J transport service provider. The value will be 0 if the transport N connection is operating the class 0 protocol. ) This attribute applies  to COTS only. REMOTE TRANSPORT SELECTORO Remote transport selector that identifies the remote transport service 2 user. This attribute applies to COTS only. REQUEST ACKNOWLEDGMENTI Indicates whether request acknowledgment was negotiated for this P transport connection. This attribute is valid for class 4 protocol only. RETRANSMIT THRESHOLDO Number of times a TPDU requiring acknowledgment is t*o be retransmitted I without acknowledgment before the transmission completes with an A error. This attribute is valid for class 4 protocol only. ROUND-TRIP DELAY ESTIMATEJ Current estimate, in milliseconds, of the round-trip delay on the M transport connection. This attribute is valid for protocol class 4 only. SEND IMPLEMENTATION IDN Indicates whether the implementation id will be sent in the CR. It is = always ret+urned in the CC if it is present in the CR.$ SEND PREFERRED MAXIMUM tpdu SIZEL Indicates whether the preferred maximum TPDU size parameter was sent in the CR or CC TPDU. SEND REQUEST ACKNOWLEDGMENT O Indicates whether the request acknowledgment parameter was sent in the  CR or CC TPDU. TYPEM Indicates that the port is being used for the connection-oriented CO  Transport protocol.. CL - Connectionless tran,sport service.3 CO - Connection-Oriented transport service. USE CLNS ERROR REPORTSP When operating over CLNS, indicates whether the network Routing layer's K error reporting facility should be used when performing connection = establishment. This attribute applies to COTS only. 2 template=title OSI TRANSPORT TEMPLATEL An OSI transport template entity provides a collection of characteristics G that supply default values for certain param-eters that influence the H operation of a port on a transport connection. One template, with the O reserved identifier default, is automatically created when the osi transport K entity is created. This template is used by default when a user does not I specify a template identifier in a call to establish a connection. The M default template is automatically deleted when the osi transport entity is N deleted. Similarly, the initial values of the attributes in a template are : the sa.me as the current values in the default template.  3 character%=title Characteristics Attributes ACKNOWLEDGMENT DELAY TIME6 Default: 1 Value: 0-65P Maximum amount of time, in seconds, that an AK TPDU is to be withheld. : This attribute is valid for protocol class 4 only. CHECKSUMS= Default: False Value: BooleanJ Specifies whether the use of checksums should be negotiated fo /r a L transport connection. This attribute is valid for protocol class 4 only. ! CLASSES>! Default: {4} Value: Bit-set!O! Set of protocol classes that can be negotiated for use on a transport P! connection. If the value of the network service attribute is CLNS, the N! class must be a subset of the classes supported by the OSI transport N! attribute clns classes supported. If the value is CONS, the classe 0s H! must be a subset of the classes supported by the OSI transport H! attribute cons classes supported. If the value of the network P! service attribute is ANY, the classes must be a subset of the combined J! classes in the clns classes supported and cons classes supported ! attributes.!! ! CLNS INACTIVE AREA ADDRESS J! Default: Empty Set Value: Set of Area_address! Q! Specifies the inactive area address to be u 1sed by transport connections J! that use this template. This characteristic is relevant only for O! connections that use CLNS with Null Internet. The set must contain no %! more than one area address. !!  CONS TEMPLATEA Default: OSI Transport Value: Simple-name O Name of the X.25 Access module template to be used when establishing a K network connection over the CONS. Used only when the value of the * ne2twork service attribute is cons. CR TIMEOUTJ Default: 30 Value: 1 - ( 2 to the 23rd)L During connection establishment, the amount of time, in seconds, to I wait for a response to a CR TPDU before assuming that the remote N transport service provider will not respond. This attribute is valid * for protocol classes 0 and 2 only. ER TIMEOUTJ Default: 30 Value: 1 - ( 2 to the 23rd)M3 The amount of time, in seconds, to wait for a response to an ER TPDU M before disconnecting the network connection. This attribute is used * for protocol classes 0 and 2 only. EXPEDITED DATA> Default: True Value: BooleanP Specifies whether use of the expedited data option should be negotiated H for the transport connections. This attribute is not valid for  protocol class 0. EXTENDED FORMAT? 4 Default: None Value: BooleanO Specifies whether the use of extended TPDU format should be negotiated J for the transport connections. Normal format gives 7-bit sequence O numbers and 4-bit credit fields; extended format gives 31-bit sequence O numbers and 16-bit credit fields. This attribute is supported only for & class 2 and class 4 protocols. INBOUND @ Default: True Value: Boo 5leanK Indicates whether this template may be used as the template for an P inbound transport connection. The algorithm of selection of the inbound L template is different depending on the type of network service over N which the transport connection is made. If an inbound template cannot O be found for an inbound transport connection, then the template called G default will be selected as the default. For the CLNS network P service, the inb 6ound template selected is the first template found that M has the Inbound attribute set to true, the Network Service attribute O set to CLNS, and the CLNS Inactive Area Address attribute set to empty set.N For the CLNS network service using the inactive subset, that is, null M internet, the incoming template selected is the first template found H that has the Inbound attribute set to True, the Network Service K attribute set to CLNS and th7e CLNS Inactive Area Address attribute K matches the Inactive Area Address attribute of the Routing Circuit L entity that the transport connection is using. For the CONS network P service, the inbound template selected is the first template found that L has the inbound attribute set to true, the network service attributeL set to CONS and the CONS template attribute that is, an X.25 Access O template name matches the name of the X.25 Access filter that 8was used 2 to accept the inbound network connection.  INITIAL RETRANSMIT TIMEN Default: 5 Value: 1 - ( 2 to the 23rd )I Amount of time, in seconds, to wait for an acknowledgment before D retransmitting the first TPDU over the transport connection. KEEPALIVE TIMEB Default: 60 Value: 1 - 6383O Time, in seconds, to be used for the window timer. When the transport N 9 service provider has no TPDUs to send over a transport connection, it K retransmits the last AK TPDU at the specified frequency to prevent M expiration of the remote NSAP's inactivity timer. This attribute is ( valid for protocol class 4 only. LOCAL NSAPG Default: system dependent Value: NSAP address J A local NSAP address to be used by default if one is not supplied % across the service interface.! L:OOPBACK C! Default: False Value: Boolean!O! Specifies whether transport connections using this template are looped.! back locally in the transport layer. !! MAXIMUM NSDU SIZE? Default: 2048 Value: 2048P When operating over the CONS, the maximum NSDU size to use for transmit > and receive buffers. Expressed as a number of octets. NETWORK SERVICEN Default: CLN;S Value: any, CLNS, or CONSO Type of network service. The network service chosen must be compatible 7 with the value of the protocol class attribute. ANY - Either.. CLNS - Connectionless Network Service.3 CONS - Connection-Oriented Network Service. RETRANSMIT THRESHOLDO Default: 8 Value: 0 - ( 2 to the 23rd ) O Number of times a TPDU requiring acknowledgment is < to be retransmitted H before it is assumed that network connectivity has failed. This5 attribute is valid for protocol class 4 only. SECURITYE Default: Null Value Value: Octet String O An octet string to be transmitted in the security parameter of a CR or O CC TPDU. A null value causes the security parameter to be omitted from L the TPDU. For security reasons, this attribute cannot be displayed. SEND = IMPLEMENTATION ID@ Default: True Value: Boolean P Indicates whether the implementation id should be sent in the CR if the N proposed protocol class is 2 or 4. It is always returned in the CC if it is present in the CR.$ SEND PREFERRED MAXIMUM TPDU SIZEA Default: True Value: Boolean K Indicates whether the preferred maximum TPDU size parameter should  be sent >in the CR TPDU.K If the preferred maximum TPDU size parameter was present in the CR H TPDU, then it indicates whether the preferred maximum TPDU size 0 parameter should be sent in the CC TPDU.N The default value of this characteristic should not be changed unless ? the remote implementation does not conform to ISO 8073. SEND REQUEST ACKNOWLEDGMENTB Default: True Value: BooleanN Indicates whether th ?e request acknowledgment parameter should be sent  in the CR TPDU.Q If the request acknowledgment parameter was present in the CR TPDU, then L it indicates whether the request acknowledgment parameter should be  sent in the CC TPDU.K The default of this characteristic should not be changed unless the; remote implementation does not conform to ISO 8073. USE CLNS ERROR REPORTSC Default: False Value: @Boolean L Indicates whether the network Routing layer's error report facility L should be used when performing connection establishment. If set to L true, this may result in faster detection of an unreachable node at N the time of connection establishment. This characteristic should not F be set to true on an end system that is either dual-railed or L connected to a network that has a high probability of duplication. : This is valid Aonly if network service equals CLNS.wwp 1 routing=title ROUTINGK The Routing module implements the Network Routing layer described by the Digital Network Architecture.  I The entities that constitute the ROUTING module are listed below. The J indention indicates the hierarchical relationships between the entities.& Routing2 Destination area2 Destinat Bion node8 IP destination address& Port4 Permitted neighbor+ EGP group1 EGP neighbor) Circuit. Adjacency; IP address translation1 IP adjacency9 IP Creachable address6 Reachable address L The Routing module routes messages in the network and manages the message N packet flow. The Routing module components provide the following functions:K o Routing determines packet paths. A path is the sequence of connected P nodes and links between a source node and a destination node. The combined N knowledge of all the network Routing layer modules of all the nodes in a P network is used to Ddetermine the existence of a path, and route the packet J to its destination. The routing component at a routing node has the " following specific functions:= - Extracts and interprets the route header in a packet.D - Performs packet forwarding based on the destination address.6 - Performs packet fragmentation where necessary.O - Manages the characteristics of the path and if a node or link fails on ) a path, finds an alternate route.M - InterfacesE with the Network Routing Subnetwork Dependent sublayer to L receive reports concerning a circuit or node that has failed or the 1 subsequent recovery of a circuit or node.6 - Performs packet reassembly at the destination.O - Returns error reports to the source where necessary, for instance when O the destination is unreachable or when the packet would have needed to L be fragmented but segmentation permitted was not set in the packet. N Segmenta Ftion permitted is always set in data packets generated by DNA 8 nodes. However, non-DNA nodes may do otherwise.L o Congestion control manages the resources used at each packet switching / node each node that permits route-through.M o Packet lifetime control bounds the amount of time a packet can exist in  the network.I o Initialization identifies the adjacent node and the adjacent node's M network routing layer. It also performs node verification, if requir Ged.N o Dynamic circuit management -- determines when to dial calls, when to hangN up calls, and on dynamically assigned circuits which DTE address to dial.: It exists only on dynamically established data links.N Whether or not a particular attribute or event of a routing module entity isL supported often depends on the type of node on which the routing module isL operating. The description of an attribute or event indicates the type of N node for which the attribute or evHent is supported, using the following key:> L1 - The attribute is supported only for Level 1 routers.> L2 - The attribute is supported only for Level 2 routers.I L1,L2 - The attribute is supported only for Level 1 or Level 2 routers.8 End - The attribute is supported only for end nodes.P IP - The attribute is supported only for systems that support dual Routing + that is, both OSI and IP routing.< All - The attribute is supported by all implementations.IM The routing entity is the top-level entity in the Routing module hierarchy M of entities. The Routing module controls the operation of network routing  within a node. 2 CHARACTER$=TITLE Characteristic Attributes! AREA AUTHENTICATION TYPE  Support: L1,IP@ Default: None Value: None or Simple M Type of authentication to be used for level 1 LSPs, PSNPs, and CSNPs." AUTONOMOUS SYSTEM NUMBER  J Support: IP: Default: 0 Value: 1-65535 M Autonomous system number of the local system. This characteristic is G supported only if the value of the routing protocols supported M characteristic includes EGP. You can modify this characteristic only < when the status attribute routing state is off. " DNA ADDRESS FORMAT  Support: End; Default: True Value: Boolea KnL If true, specifies that NSAP addresses are DNA structured, and that K NSAP address autoconfiguring is possible. If false, this specifies C that NSAP addresses for this node are constructed from the F characteristic manual network entity titles and the selectors L supplied by the transport protocol module NSP and/or OSI transport. ! DOMAIN AUTHENTICATION TYPE  Support: L2,IPC Default: None Value: None orL simple M Type of authentication to be used for level 2 LSPs, PSNPs, and CSNPs." GENERATE CHECKSUMS  Support: All= Default: False Value: Boolean H If true, specifies that checksums are generated for data, error G report, and ES-IS PDUs initiated by this node. If false, these J checksums are not generated. It is strongly recommended that, for N performance reasons, you use the defMault value indicating no checksum  generation." IP REASSEMBLY TIME  Support: IP< Default: 10 Value: 1-255 H Maximum time, in seconds, for which IP fragments are held while  awaiting reassembly." LIFETIME  Support: All< Default: 63 Value: 2-255 L Value to be placed in the lifetime field of originating data NN packets. This value should be greater than the maximum number of hops H in any path in the network, plus the maximum packet lifetime in  half-seconds." MANUAL AREA ADDRESSES  Support: L1,L2M Default: No area address Value: Set of area addressesN Area addresses to be used for this node. An area address cannot be a L Phase IV address or the address DefaultArea. If the characteristic I manual L1 algo Orithm has the value routing vector, this set must N be empty, and the characteristic phaseiv address must not be 0.0. If N the characteristic phaseiv address is 0.0, there must be at least one  area address." MANUAL L1 ALGORITHM  Support: L1B Default: Routing Vector Value: see belowN Type of routing algorithm to be used within the area. You can modify = this characteristic only when the entity is disaPbled.F link state - The DECnet-Plus link-state algorithm is used.G routing vector - The Phase IV routing-vector algorithm is used." MANUAL L2 ALGORITHM  Support: L2A Default: Routing Vector Value: see below N Type of routing algorithm to be used at level 2. You can modify this 8 characteristic only when the entity is disabled.F LINK STATE - The DECnet-Plus link-state algorithm is useQd.G ROUTING VECTOR - The Phase IV routing-vector algorithm is used.% MANUAL NETWORK ENTITY TITLES  Support: EndC Default: No NETS Value: set of NETS E Network entity titles NETs to be used for this node. If the I characteristic dna address format is set to false, there must be  at least one NET. MAXIMUM BUFFERS ? Default: 100 Value: 1-65535 J R Specifies the guaranteed number of buffers for forwarding. More M buffers may be used if they are available. You can only increase the  characteristic value. " MAXIMUM PATH SPLITS  Support: L1,L2< Default: 2 Value: 1-32 M Maximum number of equal cost paths to split traffic between. You can D modify this characteristic only when the entity is disabled.* MINIMUM LSP TRANSM SISSION INTERVAL  Support: L1,L2K Specifies the minimum interval in seconds between transmissions of P an LSP from a particular source. When changed the timer must be reset. " PHASEIV ADDRESS  Support: AllG Default 0.0 Value: Phase IV address M Specifies a Phase IV compatible address for communication with other M Phase IV nodes. The default address, 0.0, indicates that no PhasTe IV I compatible address is provided for the node. You can modify this 8 characteristic only when the entity is disabled." PHASEIV AREA MAXIMUM COST  Support: L2= Default: 1022 Value: 1-1022 C Maximum cost of a path to a reachable Phase IV area. This O characteristic is only used by the Phase IV routing algorithm that is, % the routing-vector algorithm." PHASEIV AREA MAXIMUM HOPS U  Support: L2; Default: 30 Value: 1-30 L Maximum number of hops in a path to a reachable Phase IV area. This L characteristic is only used by the Phase IV routing algorithm that * is, the routing-vector algorithm. % PHASEIV BROADCAST ROUTING TIMER  Support: L1,L2? Default: 10 Value: 1-65535 L Maximum interval, in seconds, between broadcast routing Vmessages on M broadcast circuits. This characteristic is only used by the Phase IV @ routing algorithm that is, the routing-vector algorithm." PHASEIV BUFFER SIZE  Support: All? Default: 576 Value: 1-65535 J Size, in octets, of buffers used for routing to adjacent Phase IV J nodes. This value is actually six octets greater than the maximum J buffer size, and does not include the headers foWr the Routing and  Data Link layers." PHASEIV MAXIMUM ADDRESS  Support: L1,L2= Default: 1023 Value: 1-1023 M Maximum node number within the Phase IV area. This characteristic is A only used by the Phase IV routing algorithm that is, the ! routing-vector algorithm." PHASEIV MAXIMUM AREA  Support: L2< Default: 63 Value: 1-63 N X Maximum Phase IV area number. This characteristic is only used by the I Phase IV routing algorithm that is, the routing-vector algorithm." PHASEIV MAXIMUM COST  Support: L1,L2> Default: 1022 Value: 1-1022 M Maximum cost of a path to a reachable node within the Phase IV area. K This characteristic is only used by the Phase IV routing algorithm . that is, the routing-vector algorithm." PHYASEIV MAXIMUM HOPS  Support: L1,L2< Default: 30 Value: 1-30 N Maximum number of hops in a path to a reachable node within the Phase J IV area. This characteristic is only used by the Phase IV routing 8 algorithm that is, the routing-vector algorithm." PHASEIV MAXIMUM VISITS  Support: All< Default: 63 Value: 1-63L Maximum number of visits that a Zpacket can make to this node before P Routing assumes that the packet is looping. This characteristic is only K used by the Phase IV routing algorithm that is, the routing-vector  algorithm.# PHASEIV PREFIX  Support: AllF Default: Hex 49 Value: address prefix M Prefix for Phase IV addresses. If the characteristic phaseiv address L is not 0.0, a DECnet-Plus area address is formed by ad[ding the area L portion of the Phase IV address to this prefix. You can modify this 8 characteristic only when the entity is disabled.# PROBE RATE  Support: End? Default: 20 Value: 1-65535 O Number of packets after which a probe is sent. This characteristic is N used only on multilink end systems, on circuits without cache entries  for the destination.# PROTOCOLS \  Support: IPE Default: Value: IP or ISO8473 J The protocol stacks that are enabled on this system. These can be M either or both of the above values. The value of this characteristic J derives from an argument to the create command. You cannot modify  this characteristic.# REDIRECT HOLDING TIME  Support: L1,L2? Default: 600 Value ]: 1-65535 M Holding time, in seconds, to be specified in Redirect PDUs generated  by this node.# RIP RECEIVE METRIC CLASS  Support: L2,IPL Default: External Value: External or Internal J The class to be associated with routes received through RIP. This H value may be overridden by a routing receive route entity. This L characteristic is supported only if the routing protocols supported ^9 characteristic includes the RIP routing protocol.# RIP SEND LOCAL METRIC  Support: L2,IP; Default: 1 Value: 0-16 O The metric value used by RIP when announcing routes derived from local M information. This value is used unless it is overridden by a routing H send route entity. This characteristic is supported only if the L routing protocols supported characteristic includes the RIP ro _uting  protocol.# RIP SEND METRIC CLASSES  Support: L2,IPO Default: Internal Value: set of external, internalM Routes received through routing protocols other than RIP with metric L classes in this set are candidates for announcement in RIP messages M subject to the route propagation policy in force. Routes with metric O classes not in this set will not be announced. Each value in this set K `may be overridden separately by a more specific propagation policy F specified by a routing send route or routing send route route L source entity. This characteristic is supported only if the routing M protocols supported characteristic includes the RIP routing protocol.# RIP SEND REPLACEMENT METRIC  Support: L2,IP8 Default: 1 Value: 0-16 L The metric value used by RIP when announcing routes derived thro augh O other routing protocols. This value is used unless it is overridden by K a routing send route entity. This characteristic is supported only K if the routing protocols supported characteristic includes the RIP  routing protocol.# ROUTE PROPAGATION  Support: L2,IPJ Default: No Route Propagation Value: set of protocol pairsK The default route propagation to be performed. The set may include % the bfollowing protocol pairs:& EGP to IS-IS IS-IS to RIP& EGP to RIP RIP to EGP IS-IS to EGPH If a particular value is not present in the set, routes are not G propagated between those two protocols in that direction. This K characteristic is supported only if the routing protocols supportedK characteristic includes either of the EGP or RIP routing protocols." ROUTING PROTOCOLS SUPPORTED  Support: L2,IPK c The set of routing protocols supported by this implementation. You * cannot modify this characteristic. EGP IS-IS RIP" SEGMENT BUFFER SIZE  Support: All= Default: 570 Value: 0-65535 N Maximum segment size, in octets, to be used by the Transport layer. A ? value of zero means that the segment size is unlimited." SEND SOURCE QUENCH  Support: Ld1,L2,IP= Default: False Value: Boolean J Specifies whether an ICMP source quench packet is sent when an IP I packet is discarded because of congestion. If false, ICMP source & quench packets are never sent." SOURCE QUENCH INTERVAL  Support: L1,L2,IP= Default: 100 Value: 1-65535 J Minimum time, in milliseconds, between transmission of successive # ICMPe source quench packets." SUMMARY ADDRESSES  Support: L2,IPO Default: No address Value: Set of summary addresses I Summary address information to be included in level 2 link state # packets sent by this node. " TIME TO LIVE  Support: IP< Default: 35 Value: 1-255 F Specifies the value to be placed in the time to live field of N f originating IP packets. This value should be greater than the maximum 2 number of hops in any path on the network." TYPE  Support: All@ Default: No default Value: see below I Routing type of this node. You cannot modify this characteristic.+ ENDNODE - The node is an end node.0 L1router - The node is a level 1 router.0 L2router - The node is a level 2 router. VERSgIONE Version number of the DNA Network Routing layer architecture O specification to which this implementation conforms. You cannot modify  this characteristic. 2 counters=title Counter Attributes * ADDRESS UNREACHABLE PDUS DISCARDED  Support: AllM Number of data PDUs that have been discarded because the destination  was unreachable. ! AGED IP PACKETS DISCARDED  Support: IPL Number ohf IP packets that have been discarded because their time of  life has expired.! AGED PDUS DISCARDED  Support: L1,L2L Number of data PDUs that have been discarded because their lifetime  has expired.0 ATTEMPTS TO EXCEED MAXIMUM SEQUENCE NUMBER  Support: L1,L2O Number of times an attempt was made to increase the sequence number of 7 a link state packet beyond the maximum allowed. ! CORRiUPTED LSPS DETECTED  Support: L1,L2G Number of times that the corrupted lsp detected event has been  generated.! ERROR REPORTS GENERATED  Support: AllJ Number of error report PDUs or Phase IV data packets with RTS set ! that have been generated.4 ICMP ADDRESS MASK REPLY MESSAGES RECEIVED  Support: IP< Number of ICMP Address Mask Reply messages received.4 ICMP ADDRESS MASK REPLY MESSAGjES SENT  Support: IP8 Number of ICMP Address Mask Reply messages sent.4 ICMP ADDRESS MASK REQUEST MESSAGES RECEIVED  Support: IP> Number of ICMP Address Mask Request messages received.4 ICMP ADDRESS MASK REQUEST MESSAGES SENT  Support: IP: Number of ICMP Address Mask Request messages sent.4 ICMP DESTINATION UNREACHABLE MESSAGES RECEIVED  Support: IPA Number of ICMP Destination Uknreachable messages received.4 ICMP DESTINATION UNREACHABLE MESSAGES SENT  Support: IP= Number of ICMP Destination Unreachable messages sent.4 ICMP ECHO REPLY MESSAGES RECEIVED  Support: IP4 Number of ICMP Echo Reply messages received.. ICMP ECHO REPLY MESSAGES SENT  Support: IP0 Number of ICMP Echo Reply messages sent.. ICMP ECHO REQUEST MESSAGES RECEIVED  Supporlt: IP6 Number of ICMP Echo Request messages received.. ICMP ECHO REQUEST MESSAGES SENT  Support: IP2 Number of ICMP Echo Request messages sent.. ICMP MESSAGE SEND ERRORS  Support: IPN Number of ICMP messages that could not be sent because of problems in K the ICMP layer. Note that this value does not include errors that @ occur outside the ICMP layer, such as forwarding errors.. ICMPm MESSAGES RECEIVED  Support: IPM Number of ICMP messages received. This value includes those messages < counted by the icmp received message errors counter.. ICMP MESSAGES SENT  Support: IPL Number of ICMP messages of all types that the node has attempted to L send. Note that this figure includes the value of the icmp message  send errors counter.0 ICMP PARAMETER PROBLEM MESSAGEnS RECEIVED  Support: IP; Number of ICMP Parameter Problem messages received.- ICMP PARAMETER PROBLEM MESSAGES SENT  Support: IP7 Number of ICMP Parameter Problem messages sent.- ICMP RECEIVED MESSAGE ERRORS  Support: IP@ Number of ICMP messages received with any type of error.- ICMP REDIRECT MESSAGES RECEIVED  Support: IP2 Number of ICMP Redirect messages received.o- ICMP REDIRECT MESSAGES SENT  Support: IP. Number of ICMP Redirect messages sent.- ICMP SOURCE QUENCH MESSAGES RECEIVED  Support: IP7 Number of ICMP Source Quench messages received.+ ICMP SOURCE QUENCH MESSAGES SENT  Support: IP3 Number of ICMP Source Quench messages sent./ ICMP TIME EXCEEDED MESSAGES RECEIVED  Support: IP7 Number of ICMP Time Exceeded messapges received.+ ICMP TIME EXCEEDED MESSAGES SENT  Support: IP3 Number of ICMP Time Exceeded messages sent.0 ICMP TIMESTAMP REPLY MESSAGES RECEIVED  Support: IP9 Number of ICMP Timestamp Reply messages received., ICMP TIMESTAMP REPLY MESSAGES SENT  Support: IP5 Number of ICMP Timestamp Reply messages sent.3 ICMP TIMESTAMP REQUEST MESSAGES RECEIVED  Support: IP; Numbqer of ICMP Timestamp Request messages received.2 ICMP TIMESTAMP REQUEST MESSAGES SENT  Support: IP7 Number of ICMP Timestamp Request messages sent.. ICMP UNKNOWN MESSAGE TYPES RECEIVED  Support: IPF Number of ICMP messages received with an unknown message type.2 IP ADDRESS UNREACHABLE PACKETS DISCARDED  Support: IPE Number of IP packets discarded because their destination was  unreachablre.6 IP DESTINATION ADDRESS ERROR PACKETS DISCARDED  Support: IPI Number of IP packets discarded because of an invalid destination 7 address or the address of an unsupported class. IP PACKET FORMAT ERRORS  Support: IPK Number of IP packets discarded because of a format error in the IP  header. IP PACKETS DISCARDED  Support: IPK Number of IP packets discarded for either of the following reassons:I o Error in the IP header, such as bad checksum or version number O mismatch. Note, however, that format errors and time to live expired  are excluded.M o Packet received through data link broadcast when forwarding is not  allowed.0 IP PROTOCOL UNREACHABLE PACKETS DISCARDED  Support: IPI Number of IP packets received for the local system and discarded L because there was no port with the protocol typet specified in the IP datagram PROTO field./ IP SOURCE ADDRESS ERROR PACKETS DISCARDED  Support: IPO Number of IP packets discarded because of an invalid source address or , the address of an unsupported class.! LSP l1 DATABASE OVERLOADS  Support: L1,L2I Number of times that the lsp level 1 database overload event has  been generated.! LSP l2 DATABASE OVERLOADS  Support: L2I Numberu of times that the lsp level 2 database overload event has  been generated.( MANUAL ADDRESSES DROPPED FROM AREA  Support: L1,L2H Number of times an address in the manual area addresses set is M ignored when computing an area address. Each address that is ignored  is counted separately.  OWN LSP PURGES  Support: L1,L2I Number of times that the own lsp purged event has been generated. vPDU FORMAT ERRORS  Support: AllN Number of data PDUs that have been discarded because of format errors.' PHASEIV TRANSLATION FAILURES  Support: AllH Number of times the phaseiv translation failures event has been  generated. SEQUENCE NUMBER SKIPS  Support: L1,L2H Number of times that the sequence number skipped event has been  generated. UNSUPPORTED OPTIONS  Support: AwllL Number of data PDUs that have been discarded because they specified , unsupported options in their header.2 preset_attrib=title Preset AttributesI Preset attributes are similar to characteristics, in that their values H control the way in which the routing module operates. However, unlike J characteristics, you cannot alter preset attribute values using the set command.* BROADCAST LSP TRANSMISSION INTERVAL  Support: L1,L2J x Interval, in milliseconds, between the transmission of Link State , Packets LSPs on a broadcast circuit. COMPLETE SNP INTERVAL  Support: L1,L2M Interval, in seconds, between generation of Complete Sequence Number C Packets SNPs by a designated router on a broadcast circuit. DEFAULT ESHELLO TIMER  Support: AllO Value to be used for the current suggested Hello timer, in the absence L of any suggested value from ythe intermediate system IS. On routers, M this is the value to be suggested when the router is not required to O poll the ES configuration. In routers, this value is suggested by the = Suggested ES Configuration Timer option in IS Hellos. DR ISISHELLO TIMER  Support: L1,L2L Interval, in seconds, between the generation of IS-IS Hello PDUs by  the designated router. ES CACHE HOLDING TIME  Support: EndL z Holding time, in seconds, for an entry in the node's end-node cache  database. ES CACHE WIDTH  Support: EndK Maximum number of LAN address entries in the node's end-node cache ( database on a broadcast circuit. HOLDING MULTIPLIER  Support: AllO Value by which to multiply the Hello timer to obtain the holding timer L value for ES and IS Hellos and for point-to-point, router-to-router  Hellos.{ INACTIVE SELECTOR  Support: AllJ This is the selector value identifying the port to which incoming , Inactive Subset PDUs are to be sent. INITIALIZATION TIMER  Support: AllO Delay, in seconds, between initialization of a data link and sending a / DECnet-Plus message on a DDCMP circuit. ISIS FORMAT  Support: L1,L2K This attribute controls the protocol identification to be used for| L "DNA Private" PDUs. On broadcast circuits, this characteristic also8 controls the SAP on which they are transmitted. " ISIS HOLDING MULTIPLIER  Support: L1,L2O Value by which to multiply the ISIS Hello timer to obtain the value of N the holding timer for LAN level 1 and level 2 router-to-router Hellos. MAXIMUM AGE  Support: L1,L2E Number of seconds before an LSP is considered to be expired. * } MAXIMUM LSP GENERATION INTERVAL  Support: L1,L2F Maximum interval, in seconds, between link state packets LSPs  generated by this node.) MINIMUM LSP GENERATION INTERVAL  Support: L1,L2K Minimum time, in seconds, between generation of LSPs by this node., MINIMUM LSP TRANSMISSION INTERVAL  Support: L1,L2H Minimum interval, in seconds, between retransmissions of an LSP.& MULTICIRCUIT ESHELLO T~IMER  Support: EndD Value to be used for the current suggested Hello timer on a I multicircuit end node with more than one circuit enabled, in the 4 absence of any suggested values from the IS.( ORIGINATING l1 LSP BUFFER SIZE  Support: L1,L2F Maximum size of level 1 LSPs and SNPs originated at this node.+ ORIGINATING l2 LSP BUFFER SIZE  Support: L2F Maximum size of level 2 LSPs and SNPs originated at this node. PARTIAL SNP INTERVAL  Support: L1,L2C Minimum interval, in seconds, between sending partial SNPs.! POLL ESHELLO RATE  Support: AllO Interval, in seconds, between ES Hellos when a router requires to poll  the ES configuration. QUEUE THRESHOLD  Support: L1,L2F Average queue length at a router, above which the "congestion = experienced" bit will be set in a forwarded data PDU.! WAITING TIME  Support: L1,L2J Delay, in seconds, between routing databases being in the waiting ( state and entering the on state. ZERO AGE LIFETIME  Support: L1,L2J Time, in seconds, for which the purge header of an expired LSP is  retained. 2 status=title Status Attribute AREA ADDRESSES  Support: AllK A set of area addresses. If th e node is an end node, these are the J area address portions of the NETs of all adjacent routers. If the K node is a level 1 or level 2 router, this set is the union of the O sets of manual area addresses reported in all level 1 LSPs received by  this router. EGP PORT  Support: IPK Name of the routing port entity used for sending and receiving EGP L messages. This attribute is set when a routing egp group entity is   enabled.  ICMP PORT  Support: IPL Name of the routing port entity used for sending and receiving ICMP K messages. This attribute is set when the routing module is enabled @ and the protocols characteristic includes the value IP.  L1 STATE  Support: L1,L2& State of the level 1 database.' OFF - Routing is disabled.> ON - Routing is enabled and operating correctly.K WAITING - Routing has received routing information that it cannot H store and is waiting for the overload to be removed.  L2 STATE  Support: L2& State of the level 2 database.& OFF - Routing is disabled.= ON - Routing is enabled and operating correctly.J WAITING - Routing has received routing information that it cannot F store and is waiting for the overload to be removed.( NEAREST L2 ROUTER ADJACENCIES  Support: L1,L2N Names of adjacencies to be used for forwarding to the nearest level 2 M router. If the node is a level 2 router adjacent to other areas, or O if it is a level 1 router in an area with no attached level 2 routers,  this set is empty. RIP PORT  Support: IPK Name of the udp port entity used by the routing module for sending I and receiving RIP messages. This attribute is set when a routing K circuit entity is enabled with its rip state characteristic set to ! any value other than off. STATE  Support: All$ State of the routing entity.% OFF - The entity is disabled.$ ON - The entity is enabled. 2 circuit=title ROUTING CIRCUIT C A routing circuit entity represents a data link to another node.  3 character$=title Characteristic Attributes% ALTERNATIVE SUBNET ADDRESSES  Support: L1,L2,IPJ Default: No Address Value: Set of subnet_address O A set of alternative IP addresses and subnet masks for this interface. L You can modify this characteristic only when the entity is disabled. ARP HOLDING TIME  Support: IP= Default: 600 Value: 30-65535 E Number of seconds to hold on to a routing circuit ip address I translation entity. This characteristic is supported only if the 1 circuit's type characteristic is CSMA-CD.% ARP RESPONSE WAITING TIME  Support: IP9 Default: 3 Value: 1-10 N Number of seconds to wait for an ARP response when an ARP request has J been sent. This characteristic is supported only if the circuit's ' type characteristic is CSMA-CD. AUTHENTICATION TYPE  Support: L1,L2,IPC Default: None Value: None or Simple L Type of authentication to be used for LAN L1 Hellos, LAN L2 Hellos, ' or PtPt Hellos on this circuit. DATA LINK ENTITY  Support: AllF Default: NO Data Link name Value: Local_entity-name L Name of the entity within the data link module to be created when a D port is opened for that data link type. You can modify this L characteristic only when the entity is disabled. This attribute is L supported for all types of circuits; however, for X.25 circuits set $ the attribute to x25 access. DIRECTED BROADCAST  Support: L1,IP> Default: On Value: Off or On J Specifies how an IP packet is to be forwarded on a broadcast link.* OFF - Discard the packet silently.M ON - Broadcast the packet using data level link broa that either of / the following conditions is true:M o The packet's subnet address matches the value of the subnet ( address characteristic.N o The packet's subnet address matches one of the values of the > alternative subnet addresses characteristic. K This characteristic is supported only if the characteristic type is  set to CSMA-CD.  DNA NEIGHBOR  Support: L1,L2< Default: True Value: Boolean C If true, specifies that the neighbor is expected to be DNA L compliant, and so proprietary mechanisms are possible. If false, no N router-to-router Hellos or LSPs will be sent over this circuit. This K characteristic is supported only if the characteristic type is not L x25 da. You can modify this characteristic only when the entity is  disabled. ENABLE PHASEIV ADDRESS   Support: All= Default: True Value: Boolean P Specifies whether the physical LAN address is to be set to the Phase IV I style LAN address that is, AA-00-04-00-xx-xx. The LAN address is H set only if this attribute is true and the value of the phaseiv J address characteristic is not 0.0. If phaseiv address is not 0.0 N and there are multiple adaptors to the same LAN, only one circuit may J have this attrib ute set to true. This characteristic is supported : only if the characteristic type is set to CSMA-CD. $ EXPLICIT RECEIVE VERIFICATION  Support: All> Default: True Value: Boolean N Type of password verification performed at circuit initialization. If H true, the received verifier is checked against the value of the L characteristic receive verifier for this circuit, if any. If false, P the received verifier is checked against the set of verifiers specified F in the routing permitted neighbor entities. This attribute is I supported only if the characteristic type is set to ddcmp, hdlc, D x25 static incoming, x25 static outgoing, and x25 permanent.  HELLO TIMER  Support: L1,L2> Default: 10 Value: 1-32767 8 Interval, in seconds, between IS Hello messages. IDLE TIMER  Support:  All> Default: 10 Value: 1-32767 P Number of seconds of idle time before a call is cleared. This attribute @ is supported only if the characteristic type is x25 da.  INACTIVE AREA ADDRESS  Support: AllJ Default: No area Address Value: Set of area address K Area address associated with the use of the inactive subnet of ISO C 8473. Maximum area address that may be presen t is 1. This L characterisitic is supported only if the characteristic type is set  to csma-cd. INITIAL MINIMUM TIMER  Support: All> Default: 55 Value: 1-65535 K Period, in seconds, for which an X.25 call remains connected after M being established, irrespective of traffic. This should be set small N enough that the call is cleared before the start of the next charging N interval. This attribute is supported only if the characteristic type  is x25 da.  ISIS HELLO TIMER  Support: L1,L2> Default: 3 Value: 1-32767 O Interval, in seconds, between LAN level 1 and level 2 router-to-router K Hello messages. This value is also used as the interval between IS : Hello messages when polling the ES configuration.  L1 COST  Support: L1,L2; Default: 20  Value: 1-63 1 Cost of this circuit for level 1 traffic. L1 router priority  Support: L1,L2< Default: 64 Value: 1-127 O Priority for becoming LAN level 1 designated router. This attribute is G supported only if the circuit's characteristic type is csma-cd. L2 cost  Support: L2; Default: 20 Value: 1-63  1 Cost of this circuit for level 2 traffic. L2 router priority  Support: L2< Default: 64 Value: 1-127 O Priority for becoming LAN level 2 designated router. This attribute is H supported only if the circuit's characteristic type is csma-cd.% MANUAL DATA LINK SDU SIZE  Support: All@ Default: 1492 Value: 128-65535 O Preferred ma ximum data-link block size, in octets. You can modify this O characteristic only when the entity is disabled. If the characteristic L type is CSMA-CD, this characteristic is a read-only attribute whose  value is fixed at 1492., MANUAL DATA LINK SDU SIZE FOR IP  Support: IP@ Default: see below Value: 128-65535 K Preferred maximum DSDU size, in octets, for the transmission of IP O packets. The DS DU size includes the size of the packet containing the N IP header. On point-to-point HDLC links, the DSDU size also includes N the 1-octet link encapsulation that is, the maximum IP packet size is N 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 types - 576K You can modify this characteristic only when the entity is disabled.  MANUAL l2ONLY MODE  Support: L2> Default: False Value: Boolean L If true, specifies that this circuit is to be used only for level 2 H traffic. If false, the circuit may be used for both level 1 and J level 2 traffic. You can modify this characteristic only when the  entity is disabled. MANUAL ROUTERS  Support: EndJ Default: No router IDs  Value: Set of LAN Address L Manually entered IDs of routers. If this set is empty, the circuit O will auto-configure the routers. This characteristic is supported only ; if the circuit's characteristic type is CSMA-CD.   MAXIMUM ARP RETRIES  Support: IP; Default: 3 Value: 1-10 M Maximum number of times that an ARP request can be sent for the same K IP addre ss. This characteristic is supported only if the circuit's . characteristic type is set to CSMA-CD. MAXIMUM CALL ATTEMPTS  Support: All< Default: 10 Value: 0-255 N Maximum number of successive X.25 call failures before the circuit is O regarded as being halted. A value of zero means that there is no limit J to the number of retries. This attribute is supported only if the K characteristic typ e is set to x25 static outgoing. You can modify L this characteristic only when the entity is disabled. Also, you can / only increase the characteristic value.$ MAXIMUM SVC ADJACENCIES  Support: All> Default: 1 Value: 1-65535 L Number of routing circuit adjacency entities to reserve for SVCs on N this circuit. This is effectively the maximum number of simultaneous L calls possible on this  circuit. This attribute is supported only if + the characteristic type is X25 DA. % ORIGINATING QUEUE LIMIT  Support: L1,L2; Default: 2 Value: 1-50 P Maximum number of data PDUs originated by this node that can be on this L circuit's transmit queue. This should be set to the minimum number H required to keep the data link from idling. You can modify this N characteristic to a higher value when the entity is disabled; you can ) never modify it to a lower value. RECALL TIMER  Support: All> Default: 60 Value: 0-65535 L Interval, in seconds, that must elapse between a call failure and a M recall. This attribute is supported only if the characteristic type > is set to X25 static outgoing, X25 DA, HDLC, or DDCMP. RESERVE TIMER  Support: All> De fault: 600 Value: 1-65535 L Interval, in seconds, during which the SVC remains reserved for the M previous DTE address after a call is cleared due to lack of traffic. G This attribute is supported only if the characteristic type is  x25 da.  RESERVED ADJACENCY  Support: End? Default: False Value: Boolean M If true, specifies that one SVC must be reserved f or connection to a N router. If false, no SVC needs to be reserved for this purpose. This I characteristic is supported only if the circuit's characteristic K type is x25 da. You can modify this characteristic only when the  entity is disabled.' RIP GENERATED DEFAULT ROUTE  Support: L1,L2,IP> Default: False Value Boolean K If true, this specifies that the default route is announced in RIP O messages sent on this circuit, with the metric value specified in the I RIP generated default route metric characteristic. If false, the ' default route is not generated.) RIP GENERATED DEFAULT ROUTE METRIC  Support: L1,L2,IP> Default: False Value: Boolean P The metric to be used when announcing a generated default route through  RIP on this circuit. RIP NEIGHBORS   Support: L2,IPK Default: No address Value: set of IP-addresses M IP addresses of neighboring systems with which RIP will be exchanged N on this circuit. If the circuit is a point-to-point circuit, this set L must contain a single IP address if the rip state characteristic is J to be set to send and receive. Also, you must disable the entity B before altering this characteristic. If the rip send type N characteri stic is set to broadcast, only RIP messages from addresses P specified in this set will be received; other messages will be silently I discarded. This characteristic is supported only if the routing J protocols supported characteristic of the routing entity includes ! the RIP routing protocol. RIP POISONED REVERSE  Support: L2,IP? Default: True Value: Boolean H Specifies whether poisoned rev erse routes are to be sent in RIP M messages on this circuit. If false, poisoned reverse routes are not M sent. This characteristic is supported only if the routing protocols H supported characteristic of the routing entity includes the RIP  routing protocol.# RIP RECEIVE DEFAULT ROUTE  Support: L2,IP? Default: True Value: Boolean L Specifies whether the default route is accepted from RIP messages onL this circuit. If false, the default route from RIP messages on this K circuit is discarded. This characteristic is supported only if the I routing protocols supported characteristic of the routing entity * includes the RIP routing protocol. RIP SEND TYPE  Support: L2,IPN Default: Broadcast Value: Broadcast or point-to-point< Specifies how RIP messages are sent on this circuit.O BROA DCAST - RIP messages are sent by means of data link broadcast.K POINT-TO-POINT - RIP messages are sent directly to each IP address G specified in the rip neighbors characteristic.F This characteristic is supported only if the routing protocols G supported characteristic of the routing entity includes the RIP L routing protocol and if the circuit's type characteristic is csma-cd. RIP STATE  Support: L2,IP?  Default: Off Value: see below ? Specifies how RIP messages are treated on this circuit.K OFF - RIP messages cannot be sent or received on this # circuit.M RECEIVE - RIP messages can be received but not sent on this # circuit.I SEND AND RECEIVE - RIP messages can be sent and received on this # circuit. F This characteristic is supported only if the routing protocols G supported characteristic of the routing entity includes the RIP  routing protocol. SUBNET ADDRESS  Support: IPB Default: 0.0.0.0 Value: Subnet Address K IP address and subnet mask of this interface. You can modify this 8 characteristic only when the entity is disabled.  TEMPLATE  Support: All@ Defaul t: No template name Value: Template-id G Name of the template to be used when a port is opened for this O data-link type. If no template name is specified, no template is used.L You can modify this characteristic only when the entity is disabled. TRANSMIT VERIFIER  Support: AllL Default: No verifier Value: Hex-string, length 0-38 L Value to be transmitted for verifying the identity of th is node. If C no verifier is specified, no verifier is transmitted. This G characteristic is supported only if the characteristic type is J either ddcmp, hdlc, x25 static outgoing, x25 static incoming, or > x25 permanent. You cannot display this characteristic. TYPE  Support: All Default: All E Type of circuit. You cannot modify this characteristic. This L characteristic is set by means of an argument to the create command.A CSMA-CD - The circuit is a broadcast circuit.= DDCMP - The circuit is a DDCMP circuit.= HDLC - The circuit is an HDLC circuit.J X25 DA - The circuit is a dynamically allocated X.25 & circuit.= X25 PERMANENT - X.25 permanent virtual circuit.; X25 STATIC INCOMING - Static incoming X.25 circuit.; X25 STATIC OUTGOING - Stat ic outgoing X.25 circuit. X.25 FILTERS L Default: seee below Value: set of simple names M Specifies the set of X.25 filters to be used when a port is opened toP the X.25 module. Typically, there will be two sets: one to specify the P selection on the Call User Data field for DECnet-Plus, and the other to P specify the selection on the subaddress for Phase IV. This attribute is L valid only if the characteristic type is x25 static incoming or x25 da. 3 counters=title Counter Attributes! AUTHENTICATION FAILURES  Support: L1,L2,IPH Number of times a PDU has been received on this circuit with an P Authentication Information field that is incompatible with the PDU type. CALLS FAILED  Support: AllP Number of unsuccessful call attempts on this circuit. This attribute is < supported only if the characteristic type is x25 da.  CALLS PLACED  Support: AllM Number of call attempts successful and unsuccessful on this circuit. G This attribute is supported only if the characteristic type is  x25 da. CHANGES IN ADJACENCY STATE  Support: AllM Number of times the status attribute state of an adjacency belonging H to this circuit changes from Up to Down or Initializing, or the  reverse.& CHANGES IN IP ADJACENCY STATE  Support: IPF Number of times the status attribute state of an IP adjacency N belonging to this circuit changes from Up to some other state, or the  reverse. & CHANGES IN RIP NEIGHBOR STATE  Support: L2,IPJ Number of times the RIP state of IP adjacencies belonging to this N circuit have changed. This attribute is supported only if the routing J entity's characteristic routing protocols supported includes the  routing protocol RIP.  CIRCUIT CHANGES  Support: AllL Number of times that the status attribute state has changed from on  to off, or vice versa. CONGESTION DISCARDS  Support: L1,L2O Number of data-and error-report NPDUs that have been discarded, before L or after fragmentation, because of congestion. Any other discarding K will already have been done by the forwarding process. This nu mber I includes all PDUs recognized by the receive process as data PDUs K DECnet-Plus data- and error-report PDUs and Phase IV data packets, G even though they may subsequently be discarded for some reason.! CONTROL PDUS RECEIVED  Support: AllM Number of control PDUs that have been received on this circuit. This F number includes all Network layer PDUs, with the exception of F DECnet-Plus data and error report PDUs and Phase IV data PDUs. CONTROL PDUS SENT  Support: AllC Number of control PDUs that have been sent on this circuit.' CORRUPTED HELLO PDUS RECEIVED  Support: AllL Number of times an ES-IS end system to intermediate system or IS-IS F intermediate system to intermediate system Hello PDU has been M received on this circuit that either cannot be parsed or contains an  incorrect checksum.$ CORRUPTED LSPS RECEIVED  Support: L1,L2P Number of times a corrupted link state packet has been received on this  circuit.  DA ADJACENCY CHANGES  Support: AllG Number of DA adjacency change events that have been generated.  DATA PDUS FORWARDED  Support: L1,L2M Number of data- and error-report NPDUs that have been forwarded onto L this circuit either from another circuit or from a local port. This K number includes all PDUs recognized by the receive process as data O PDUs DECnet-Plus data- and error-report PDUs and Phase IV data packets,G even though they may subsequently be discarded for some reason. DATA PDUS FRAGMENTED  Support: AllG Number of data NPDUs that have been fragmented on this circuit. DATA PDUS RECEIVED  Support: AllO Number of data- and error-report NPDUs that have been received on this J circuit. This number includes all PDUs recognized by the receive N process as data PDUs DECnet-Plus data and error report PDUs and Phase L IV data packets, even though they may subsequently be discarded for  some reason. DATA PDUS TRANSMITTED  Support: AllO Number of data- and error-report NPDUs, after fragmentation, that have K been delivered to the port for transmission on this circuit. This P number includes all PDUs rec ognized by the receive process as data PDUs K DECnet-Plus data- and error-report PDUs and Phase IV data packets, G even though they may subsequently be discarded for some reason.) EXCEEDED MAXIMUM SVC ADJACENCIES  Support: End,L2G Number of exceeded maximum svc adjacency events that have been K generated. This counter is supported only if the circuit's type is M set to x25 da; only for nodes that are end nodes; and if the system 9 supports dual routing both DECnet and IP routing.! ID REACHABILITY CHANGES  Support: AllI Number of ID reachability change events that have been generated.! INITIALIZATION FAILURES  Support: AllL Number of times that an attempt to initialize an adjacent node over H this circuit has failed, either because of version skew or area  mismatch.- IP FRAGMENTATION FAILURE DISCARDS  Support: IPM Number of IP packets discarded because fragmentation was required to E transmit them, but the IP header requested "do not fragment."! IP FRAGMENTS CREATED  Support: IPI Number of IP fragments created for transmission on this circuit. ! IP PACKETS FORWARDED  Support: IPM Number of IP packets forwarded on this circuit before fragmentation. L These IP packets may be from another circuit or from a local port. J Note that this value includes those IP packets counted in the ip  send discards counter. IP PACKETS FRAGMENTED  Support: IPG Number of IP packets that have been fragmented on this circuit. IP PACKETS RECEIVED  Support: IPO Number of IP packets received on this circuit. This value includes all C types of IP packet control, data, etc., and those that may 1 subsequently be discarded for any reason." IP RECEIVED DISCARDS  Support: IPP Number of IP packets that have been received and then discarded because  of congestion. IP SEND DISCARDS  Support: IPO Number of IP packets for transmission that have been discarded because  of congestion.# IRRECOVERABLE SVC FAILURES  Support: AllL Number of times that the number of re-call attempts on this circuit I  has become equal to the value of the characteristic maximum call J attempts. This attribute is supported only if the characteristic + type is set to x25 static outgoing.+ LAN L1 DESIGNATED ROUTER CHANGES  Support: L1,L2M Number of times the local node has either elected itself or resigned M as the LAN level 1 designated router on this circuit. This attribute J is supported only if the circuit's characteristic type is set to   csma-cd., LAN L2 DESIGNATED ROUTER CHANGES  Support: L2M Number of times the local node has either elected itself or resigned > as the LAN level 2 designated router on this circuit. 1 LAN PHASEIV DESIGNATED ROUTER CHANGES  Support: L1,L2P Number of times the local node has either elected itself or resigned as ; the LAN Phase IV designated router on this circuit.  REDIRECT DISCARDS   Support: EndD Number of Redirect PDUs that have been discarded because of " insufficient cache memory. REJECTED ADJACENCIES  Support: AllH Number of times an attempt to create a new adjacency using this = circuit has failed because of insufficient resources.% REJECTED IP ADJACENCIES  Support: L2,IPN Number of times an attempt to automatically create a new IP adjacency @ to an IP router has failed because of lack of resources. RIP ERRORS RECEIVED  Support: L2,IPP Number of RIP messages received with any kind of received error on this K circuit. This attribute is supported only if the routing entity's H characteristic routing protocols supported includes the routing  protocol RIP.& SEGMENTATION FAILURE DISCARDS  Support: L1,L2O Number of data NPDUs that have been discarded because segmentation was K required to send them on this circuit but was not permitted in the  NPDU header. VERIFICATION REJECT EVENTS  L Number of verification reject events that have been generated. This I attribute is supported only if the characteristic type is set to F DDCMP, HDLC, X25 static incoming, X25 static outgoing, or X25  permanent. 3 status=title Status Attribute  DATA LINK PORT  Support: AllL Name of the data link port used for this circuit. Not supported on  DA circuits. DATA LINK SDU SIZE  Support: AllK Maximum size, in octets, of a Data Link SDU for this circuit. This L includes the Network layer header, but excludes the Data Link layer L header. The value of this status is the lesser of the value of the K characteristic manual data link sdu size and any limit imposed by  the Data Link layer. LAN L1 ID  Support: L1,L2 N LAN ID allocated by the LAN level 1 designated router. This attribute K is supported only if the circuit's characteristic type is csma-cd. LAN L2 ID  Support: L2N LAN ID allocated by the LAN level 2 designated router. This attribute K is supported only if the circuit's characteristic type is CSMA-CD. L1 DESIGNATED ROUTER  Support: L1,L2N ID of the DECnet-Plus level 1 designated router on this circuit. This M attribute is supported only if the circuit's characteristic type is K CSMA-CD. If this node does not participate in the router election : process, the value returned is 00-00-00-00-00-00. L2 DESIGNATED ROUTER  Support: L2N ID of the DECnet-Plus level 2 designated router on this circuit. This M attribute is supported only if the circuit's characteristic type is K CSMA-CD. If this node does not participate in the router election : process, the value returned is 00-00-00-00-00-00.% PHASEIV DESIGNATED ROUTER  Support: L1,L2M ID of the Phase IV designated router on this circuit. This attribute L is supported only if the circuit's characteristic type is CSMA-CD. O If this node does not participate in the router election process, the - value returned is 00-00-00-00-00-00. POINT-TO-POINT ID   Support: L1,L2N ID allocated to the circuit during its initialization. This attribute I is supported only if the circuit's characteristic type is HDLC,  DDCMP, or X25 static. STATE , State of the routing circuit entity.& OFF - The circuit is disabled.% ON - The circuit is enabled. 2 circ_adj =title ROUTING CIRCUIT ADJACENCYH A routing circuit adjacency entity describes an adjacency, which is a H neighboring node that is accessible through a particular circuit. The D circuit-name refers to the circuit associated with the specified  adjacency.  3 status=title Status Attributes DATA LINK PORT  Support: AllK Name of the data link port used for this X.25 data adjacency. This L attribute is supported only if the owning routing circuit entity's . characteristic type is set to x25 da. DTE ADDRESS  Support: AllO  DTE address of the neighboring node on an X.25 circuit. This status is J supported only if the owning circuit entity's characteristic type  is x25 da. ENDNODE IDS  Support: AllN System IDs of neighboring end nodes. This attribute is supported only C if the node is an end node and the owning circuit entity's * characteristic type is not x25 da. ENDNODE NETS  Support: AllL NETs computed from the  system IDs in the endnode ids status and the I set of area addresses in the owning routing entity's manual area K addresses set. This attribute is supported only if the node is an K end node and the owning circuit entity's characteristic type is not x25 da. HOLDING TIMER  Support: L1,L2K Holding time for this adjacency, updated from the router-to-router O Hello messages. This attribute is supported only if both the node and " the adjacency are routers. IP ADDRESSES  Support: IPO IP addresses of the neighbor node. If these are not known, the set is  empty.  LAN ADDRESS G broadcast circuit. This status is supported only if the owning 9 circuit entity's characteristic type is csma-cd.  LAN PRIORITY  Support: L1,L2N Priority of the neighbor of this adjacency for becoming the LAN level M  1 designated router if the adjacency is a DECnet-Plus level 1 router O or the LAN level 2 designated router if the adjacency is a DECnet-Plus M level 2 router. This status is supported only if the owning circuit H entity's characteristic type is csma-cd; and the adjacency is a( router rather than an end node.  LEVEL  Support: L1,L2M The level of the adjacency. This attribute is supported only if both / the node and the adjacency are routers.A Level 1 - The adjacency is used for level 1 routing.A Level 2 - The adjacency is used for level 2 routing.M Level 1 & 2 - The adjacency is used for level 1 and level 2 routing.. Level 0 - The usage is undefined. NEIGHBOR AREAS  Support: L1,L2L Area addresses of the neighboring node. This attribute is supported K only if both the node and the adjacency are routers and the owning ; circuit entity's characteristic type is not x25 da. NEIGHBOR NODE ID  Support: L1,L2( Node ID of the neighboring node. NEIGHBOR NODE TYPE  Support: AllK Type of the neighboring node. This status is supported only if the C owning circuit entity's characteristic type is not x25 da. H DECnet-Plus endnode - The node is a DECnet-Plus end node.N DECnet-Plus level 1 router - The node is a DECnet-Plus level 1 router.N DECnet-Plus level 2 router - The node is a DECnet-Plus level 2 router.F DECnet-Plus router - The node is a DECnet-Plus router.A non-dna router - The node is not a DNA router.D phaseiv endnode - The node is a Phase IV end node.J phaseiv level 1 router - The node is a Phase IV level 1 router.J phaseiv level 2 router - The node is a Phase IV level 2 router.B phaseiv router - The node is a Phase IV router.= unknown - The node type is unknown.% NEIGHBOR PROTOCOLS SUPPORTED  Support: IPI Network protocols supported by the neighboring node either IP or  ISO8473.  ROUTER NETS  Support: EndK Network Entity Titles NETs of a neighboring router. This status is M supported only if the adjacency is a level 1 or level 2 router, and F  the owning circuit entity's characteristic type is not x25 da. STATE  Support: AllJ State of the routing circuit adjacency entity. May be one of the  following: FAILED INITIALIZING UP UP/DORMANT TYPE   Type of adjacency.6 AUTOCONFIGURED - Created by autoconfiguration.> MANUAL - Created manually by a create command.I This attribute indicates whether the adjacency has been manually N created, or whether the adjacency was created by means of hello PDUs. N It will always have the value manual when it has been created by the I create command; otherwise, it will have the value autoconfigured. 2 cir_ip_trn-=title ROUTING CIRCUIT IP ADDRESS TRANSLATIONI A routing circuit ip address translation entity describes the mapping O between the IP address of an IP adjacency on a broadcast circuit and its LAN N address. This entity is supported only on systems that support dual routing.H ip address translation entities are created automatically, but can be  deleted manually. 3 status=title Status Attributes LAN ADDRESS  Support: IPH LAN address that corresponds to the IP address of this neighbor. 2 cir_ip_rch+=title ROUTING CIRCUIT IP REACHABLE ADDRESSL A routing circuit ip reachable address entity describes a manually enteredI subnet address that is  accessible by way of a specified circuit. An IP P reachable address allows a level 2 router at the boundary of a routing domain K to include information about the address and reachability of subnetworks P outside the domain. IP reachable addresses exist only on level 2 routers that  support dual routing. 3 character$=title Characteristic Attributes DESTINATION  Support: L2,IP O The IP address and subnet mask to which this reachable address r efers. J This value is derived from the destination argument of the create 9 command. You cannot modify this characteristic.  DTE ADDRESSES  Support: L2,IPH Default: No DTE addresses Value: Set of DTE addressesK A set of DTE addresses to which a call may be directed in order to N reach an address that matches the subnet address given by the subnet N address characteristic. You can modify this characteristic only when M the entity is disabled. This characteristic is supported only if the * owning circuit is an X.25 circuit. METRIC  Support: L2,IPH Default: 20 Value: 1-maximum link cost I Default metric value for reaching the specified subnet over this M circuit. You can modify this characteristic only when the entity is  disabled.  METRIC CLASS  Support: L2,IP I Default: External Value: External or Internal L Class of the default metric, which controls the preference for this ' route in the decision process. F EXTERNAL - The I/E bit for the default metric in the External I Reachability Information option of level 2 link state M packets is set to 1. The subnet address specified by this O IP reachable address will have the same preference as level  % 2 external routes.F INTERNAL - The I/E bit for the default metric in the External I Reachability Information option of level 2 link state M packets is set to 0. The subnet address specified by this O IP reachable address will have the same preference as level % 2 internal routes.L You can modify this characteristic only when the entity is disabled. NEXT HOP   Support: L2,IPD Default: 0.0.0.0 Value: Ip-addressL IP address of the neighboring node through which the destination is N reachable. When you create this entity, this characteristic is set to K the value of the IP address component of the destination argument L of the create command if the IP reachable address is to an IP host.L This characteristic is not used on circuits of type x25 da. You can E modify this characteristic only when the entity is disabled. 3 status=title Status Attributes STATE  ? Status of the routing circuit reachable address entity.3 OFF - The IP reachable address is disabled.2 ON - The IP reachable address is enabled. 2 cir_rch(=title ROUTING CIRCUIT REACHABLE ADDRESSJ A routing circuit reachable address entity contains information about a O manually entered address prefix accessible over that circuit. It exists only I on L2 routers and end nodes. On L2 routers the type may be outbound or J inbound. A reachable address of type outbound default describes address M prefixes in an external domain that are reachable by outbound traffic over N this circuit. The routing information contained in the reachable address is L entered directly into the L2 decision process. When ManualL2Algorithm has K the value routing vector, only reachable addresses with address prefixes D corr esponding to Phase IV areas are fed into the decision process.K An inbound reachable address describes address prefixes corresponding to O Phase IV areas which are reachable through the local node by inbound traffic P over this circuit. The routing information contained in the reachable address L area and cost is entered into a Phase IV routing vector message, which is - transmitted periodically over this circuit.L On an end system the type may be outbound or for a broadcast circuit  only O filter. A reachable address of type outbound behaves in a similar way to thatM on an L2 router except that the routing information is used to control the K operation of the ES cache. A reachable address of type filter is used to P specify the permitted LAN address of routers on the LAN which will be used by  the cache algorithm.  G The circuit-name refers to the circuit associated with the specified I reachable address. The address-prefix refers to the reachable address  managed by this command. 3 character%=title Characteristics Attributes ADDRESS PREFIX  Support: L2, EndE Default: No default Value: Address prefixJ Address prefix to which this reachable address refers. You cannot N modify this characteristic. This characteristic is set by means of an ( argument to the create command. I The value of this characteristic derives from an argument to the L create command. This characteristic is supported only if the owning ' circuit has type set to x25 da. COST  Support: L2: Default: 20 Value: 1-63 @ Cost of reaching this address prefix over this circuit.    DATA FORMAT  Support: L2M Default: DECnet-Plus Value: Phase IV or DECnet-Plus K The PDU data format to be used when forwarding data or error report, NPDUs using this reachable address.  K This attribute is supported only if the type characteristic is set M to outbound. You can modify this characteristic only when the entity  is disabled. DTE ADDRESSES  Support: End,L2K Default: No DTE addresses Value: set of DTE addresses K A set of DTE addresses to which a call may be directed in order to K  reach an address that matches the address prefix of this reachable  address. J This characteristic is supported if the node is a level 2 router, J where the owning circuit's characteristic type is one of the X.25 J circuit types, and the reachable address's characteristic type is J outbound. It is also supported by end nodes operating over an x25 L da circuit. You can modify this characteristic only when the entity  is disabled.  ISDN ADDRESS  Support: L1,L2 Default: O A full set of E.164 ISDN network addresses that a call may be directed N in order to reach a network number that matches the address prefix of G the parent reachable address entity. Associated with each ISDN N network address, but not visible to Network Management, is a variable O last failure of type binary absolute time. This attribute is supported ' only if access  type is ISDN DA.  LAN ADDRESS  Support: L2,End@ Default: 00-00-00-00-00-00 Value: id P A single LAN address to which an NPDU can be directed in order to reach N an address that matches the address prefix of this reachable address. F This characteristic is supported only if the owning circuit's D characteristic type is csma-cd, and the reachable address's L characteristic type is outbound. You c an modify this characteristic ) only when the entity is disabled.  MAPPING  Support: End,L2M Default: X.121 Value: Manual or X.121 K Type of mapping used to determine the SNPA address to which a call F should be placed for this address prefix. You can modify this M characteristic only when the entity is disabled. If the circuit is a E broadcast circuit, this attribute must have the value manual.M MANUAL - The mapping uses the set of addresses in the characteristic H dte addresses or the address in the characteristic LAN  address.I X.121 - The mapping uses the X.121 address extraction algorithm.H This characteristic is supported only if either of the following  conditions is satisfied:O 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.L o The node is a level 2 router, the owning circuit's characteristic J type is csma-cd, and the reachable address's characteristic type is outbound. METRIC TYPE  Support: L2 Default:  N The metric type of the cost metric for the circuits. If internal, the P I/E bit for the metric in the Prefix Neighbors option of L2 LSPs is set - to 0, otherwise external is set to 1 .*! modem addresses Support: L1,L2L! A set of full dial sequence that contains the address PSTN or ISDN Q! to which a call may be directed in order to reach a network number that L! matches the address prefix of the parent reachable address entity. L! Associated Network Management, is a variable last failure of type O! binary absolute time. This is valid only if mapping is manual and the 9! parent circuit entity's access time is Modem DA.!.! modem address prefix Support: L1,L2L! The address that is to be inserted to the beginning of the address O! extracted from the NSAP address. This is valid only if mapping is not O! manual and the parent circuit entity's access type is Modem DA. It is P! used in conjunction with modem access suffix to form the complete dial ! sequence.!.! modem address suffix Support: L1,L2P! The address that is to be inserted to the e nd of the address extracted P! from the NSAP address. This is valid only if mapping is not manual and L! the parent circuit entity's access type is Modem DA. It is used in Q! conjunction with modem access prefix to form the complete dial sequence.!! ;! permitted LAN address Support: End, type filterQ! The set of LAN addresses corresponding to routers that are permitted to /! be used for forwarding to this prefix.  TYPE   Support: L2,EndA Default: Outbound Value: see belowP Type of the reachable address. You can modify this characteristic only $ when the entity is disabled.M INBOUND - For L2 only, the address prefix corresponds to a Phase IV K area that is reachable through this node and circuit by # inbound traffic.G OUTBOUND - The address prefix is in an external domain that is C  reachable over this circuit by outbound traffic.P FILTER - The address prefix defines a set of addresses that should be N reached via the set of routers listed in the permitted LAN * address characteristic. 3 status =title Status Attributes STATE > State of the routing circuit reachable address entity.0 OFF - The reachable address is disabled./ ON - The reachable address is enabled. 2 dest_area=title ROUTING DESTINATION AREAM A routing destination area entity contains information about a destination L area or reachable address prefix. These entities are created and deleted % dynamically by the Routing module.  C Destination areas exist only on nodes that are level 2 routers. 3 stATUS=TITLE Status Attributes COST  Support: L2> Cost of the least cost paths to this destination area. OUTPUT ADJACENCIES  Support: L2H Set of routing circuit and routing circuit adjacency or routing M circuit reachable address entity names that represent the forwarding , decisions for this destination area.!!1 rout_dest_cache!K! A routing destination cache entity contains a collection of information F! corresponding to each remote system with which the local system is K! communicating, identified by the NSAP of the remote system. The set of N! information includes one or more collections of the following information, P! which reflect the network path taken by user data. Each record includes the ! following information:!J! Circuit name -- The name of the circuit over which data was received.M! Data link address -- The datalink address of the system that passed the O! data to the local system. This may be the address of Q! the actual source of the data, or it could the a ddress &! of a router.F! Remaining Time -- The amount of time in seconds this data will be Q! considered valid. If it is not updated by the end of that M! time by the arrival of more data, for example, it will !! be deleted.5! Reachability -- There are three values possible:J! Reverse -- Data has arrived from the indicated datalink address,I! with no further indication of t he source's location.I! Indirect -- One or more Routers IS have sent Redirect Packets toN! indicate that the specified datalink address is the best !! path to use.N! Direct -- The remote system has been shown to be directly connected0! or on the same LAN segment.!P! Data Format -- Indicates if PhaseIV or ISO CLNP packets are being used for :! communications with the remote system.I! Blocksize -- Shows what sized packets are being used, which for LAN H! circuits would be either Ethernet or FDDI frame sizes.! !!!! !2 Status !=title Status Attributes!!! informationJ! The set of records containing cache information relating to this ! address.!! 2 dest_node=title ROUTING DESTINATION NODEL A routing destination node entity contains information about a particular I destination node within the same area as this node. These entities are M created and deleted automatically by the Routing module. Destination nodes : exist only on nodes that are level 1 or level 2 routers. 3 status=title Status Attributes COST  Support: L1,L2> Cost of the least cost paths to this destination node. NETS  Support: L1,L2N Set of NETs computed from the system ID that is the entity's name and I the area addresses in the routing entity's manual area addresses set. OUTPUT ADJACENCIES  Support: L1,L2J Set of routing circuit and routing circuit adjacency entity names H representing the forwarding decisions for this destination node.2 route_egp_grp=title ROUTING EGP GROUPM A routing egp group entity defines a set of systems in the same autonomous J system with which this system may exchange EGP messages. This entity is F supported only on level 2 routers that support dual routing and, in ' particular, the EGP routing protocol. 3 character%=title Characteristics Attributes" AUTONOMOUS SYSTEM NUMBER  Support: L2,IP> Default: 0 Value: 0-65535 N The autonomous system number common to members of this group. You can J modify this characteristic only when the entity is disabled. This P attribute is supported only if the node is a level 2 router, and if the @ system supports dual routing both DECnet and IP routing. EXTERNAL ROUTES  Support: L2,IPJ Default: Receive Value: Set of send,recieve O If the set includes receive, external gateway routes are accepted from N neighbors in the group; if the set does not include receive, external I gateway routes are discarded. If the set includes send, external O gateway routes will be sent to neighbors in this group; if the set doesO not include send, external gateway routes are not sent. You can modify = this characteristic only when the entity is disabled. MAXIMUM ACTIVE NEIGHBORS  Support: L2,IP< Default: 1 Value: 0-255 M The maximum number of neighbor systems in the group that this system P will attempt to acquire and maintain in the Up state at any given time. L You can modify this characteristic only when the entity is disabled. RECEIVE METRIC CLASS  Support: L2,IPK Default: External Value: Internal or External N The class to be associated with routes received from EGP neighbors in L this group unless overridden by a routing receive route entity. You H can modify this characteristic only when the entity is disabled. SEND LOCAL METRIC  Support: L2,IP< Default: 1  Value: 0-255 N The metric value to be used when announcing routes derived from local J information unless overridden by a routing send route entity. You H can modify this characteristic only when the entity is disabled. SEND METRIC CLASSES  Support: L2,IPM Default: Internal Value: Set of external, internalM Routes received through routing protocols other than EGP with metric L  classes in this set are candidates for announcement in EGP messages M sent to neighbors in this group, subject to route propagation policy.I Routes with metric classes not specified in this set will not be O announced. You can modify this characteristic only when the entity is  disabled.# SEND REPLACEMENT METRIC  Support: L2,IP< Default: 1 Value: 0-255 M Specifies the metric value t o be used when announcing routes derived K from non-EGP routing protocols unless overridden by a routing send H route entity. You can modify this characteristic only when the  entity is disabled.#! SOURCE NETWORK ! Support: L2,IP! Default: N! Specifies the network number to query in Poll messages and to supply Q! in Update messages. If the default value is used, the network number is J! derived from the IP ADDRESS attribute of one of the EGP NEIGHBOR +! entities belonging to this entity.! 3 status=title Status Attributes STATE. State of the routing egp group entity.% OFF - The entity is disabled.$ ON - The entity is enabled. 2 egp_neghbr%=title ROUTING EGP GROUP EGP NEIGHBORL A routing egp group egp neighbor entity defines one of the systems in the K autonomous group defined by the owning egp group entity. This entity is F supported only on level 2 routers that support dual routing and, in ' particular, the EGP routing protocol. 3 character&=title Characteristics Attiributes CIRCUIT # Simple-name of the circuit. IP ADDRESS  Support: L2,IPP Internet address of this EGP neighbor. The value of this characteristic K is derived from the ip address argument of the create command. You * cannot modify this characteristic. NEXT HOP @ Default: 0.0.0.0 Value: IP address - IP address and the next routing node. SOURCE NETWORKD Default: 0.0.0.0 Value: Network number Network number to query. 3 counters=title Counter Attributes" ERROR MESSAGES RECEIVED  Support: L2,IPA Number of EGP error messages received from this neighbor. ERROR MESSAGES SENT  Support: L2,IP; Number of EGP error messages sent to this neighbor. MESSAGES RECEIVED  Support: L2,IPJ Number of EGP messages received without error from this neighbor.  MESSAGES SENT  Support: L2,IPL Number of EGP messages sent to this neighbor. Note that this value K does not include EGP messages counted by the counter send messages  discarded.) RECEIVED MESSAGES DISCARDED   Support: L2,IPL Number of EGP messages received from this neighbor with any kind of  error.& SEND MESSAGES DISCARDED  Support: L2,IPM Number of EGP messages not sent to this neighbor because of resource * limitations within the egp entity. START EVENTS  Support: L2,IPC Number of times the EGP neighbor has been manually started. STATE CHANGES FROM UP  Support: L2,IPL Specifies the number of times the EGP state of this neighbor changed$ from Up to some other state. STATE CHANGES TO UP  Support: L2,IPL Specifies the number of times the EGP state of this neighbor changed$ to Up from some other state. STOP EVENTS  Support: L2,IPD Number of times the EGP neighbor has been manually stopped. 3 status=title Status Attributes EGP STATE   Support: L2,IPC EGP state of the system with respect to this EGP neighbor.  ACQUISITION IDLE CEASE UP DOWN HELLO TIME  Support: L2,IPL Interval, in hundredths of a second, between retransmissions of EGP F Hellos. This value represents the t1 timer defined in RFC 904. LAST EVENT  Support: L2,IPK 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.O This is the value with which an EGP neighbor is created, before either 0 a start or stop command has been issued. POLLING MODE  Support: L2,IPO Polling mode of the EGP entity with respect to this neighbor as either  active or passive. POLL TIME  Support: L2,IPL Interval, in hundredths of a second, between retransmissions of EGP F polls. This value represents the t3 timer defined in RFC 904. STATE; State of the routing egp group egp neighbor entity.% ON - The entity is enabled.& OFF - The entity is disabled. 2 ip_dest%=title ROUTING IP DESTINATION ADDRESS K A routing ip destination address entity describes IP routing information P in the shortest paths database. This entity is supported only on routers that  support dual routing. 3 status=title Status Attribtues LEVEL  Support: L1,L2,IPO Level at which the shortest path exists in the shortest paths database. Level 1 Level 2 External Level 2 Internal METRIC  Support: L1,L2,IPF Default metric value for the shortest path to the destination  subnetwork. PATHS  Support: L1,L2,IPO Equal cost pat hs for this route. The following information appears for  each path:O o The name of the entity pair that represents the forwarding decision K for this path circuit and one of adjacency, IP adjacency, or IP  reachable address.E o The routing mechanism through which the route was learned:G LOCAL -- the route is derived from the subnet address or O alternative subnet addresses characteristics of a local  circuit.E NETMGNT-- the route is derived from manually configured 7 information on the local system.A o The number of seconds since the route was last updated.2 routing p_nghbr!=title ROUTING PERMITTED NEIGHBORI A routing permitted neighbor entity represents a neighboring node on a C nonbroadcast circuit that is permitted to connect to this node.  3 character%=title Characteristics Attributes ID  Support: All? Default: No default Value: NOde ID E Node ID of a potential neighbor node. You cannot modify this N characteristic. This characteristic is set by means of an argument to  the create command. VERIFIER  Support: AllO Default: No verifier Value: Hex-string, length 0-38 G Verifier to be checked from this neighbor. You may change this M characteristic at any time; however, the change will not take effect H until the circuit is next initialized. You cannot display this  characteristic. N If the verifier is not set, then a connection to the neighboring node N whose ID matches the ID in this entry is allowed. If the verifier is O set, the connection is allowed only if the verifier sent by the remote + node matches the one in this entry.2 port=title ROUTING PORTG A routing port entity represents a client of the Routing module, and 5 presents information associated with that client.  3 counter=title Counter Attributes DATA SDUS RECEIVED  Support: AllH Number of data NSDUs delivered across Transport interface after  reassembly. ERROR REPORTS RECEIVED  Support: AllI Number of error report PDUs delivered across Transport interface.$  EXPIRED SEGMENTS DISCARDED  Support: AllP Number of segments discarded because lifetime expired during reassembly." IP PACKETS REASSEMBLED  Support: IPJ Number of IP packets that have been successfully reassembled from  fragments.  SDUS TRANSMITTED  Support: AllI Number of data NSDUs requested for transmission across Transport  interface. SEGMENTS DISCARDED  Support: AllK Number of segments data- or error-report discarded before delivery M across the Transport interface, including segments discarded for any @ reason other than lifetime expiration during reassembly. SEGMENTS RECEIVED  Support: AllJ Number of data- and error-report NPDUs received before reassembly. 3 status=title Status Attribbutes CLIENT  Support: AllD Name given by the user of the port when the port was opened. NSAP ADDRESSES  Support: AllM Set of NSAP addresses to be received at this port. This attribute is E supported only if the status attribute type is not set to IP. NSAP SELECTOR  Support: AllI Network service access point NSAP selector octet supplied by the J client. This attribute is supported only if the status attribute  type is not set to ip. PROTOCOL TYPE   Support: IP@ Value of the IP protocol field specified by the client.   TYPE  Support: IPJ Type of connectionless network service to be used: IP or ISO8473.ww\1 Modem =title ModemK The Modem Connect module implements one of the protocols in the Physical8 layer described by the Digital Network Architecture. J! For Digital UNIX, the product DEC WAN Device Drivers is provided as an L! installable sub set within the product X.25 for Digital UNIX Systems. You M! must install this subset before you can refer to the LAPB module entities ! in an NCL command.L You must install the product DEC WAN Device Drivers before you can refer : to the Modem Connect Module entities in an NCL command.H The modem connect entity is the top-level entity in the hierarchy of 2 entities belonging to the Modem Connect module.' Modem Connect. Line   Data Port 2 character =title Characteristic Attributes DNA VERSIONH Version number of the DNA Modem Connect architecture to which the E implementation conforms. You cannot modify this characteristic.2 port=title Modem Connect Data PortL The modem connect data port entity is associated with a line and handles O the transfer of data. Data ports are created and deleted automatically when K a client of the Modem Connect module uses a line.  The port-name refers ( to data port managed by this command. 3 status=title Status Attributes CLIENTO Name supplied by the client when the port was opened. This defines which  client owns the port. LINEJ Name of the modem connect line entity that the client supplied when  the port was opened. STATE State of data port.  < OPEN - The port is assigned to a client.J OPEN DISABLED - The port is  assigned to a client, but the line B entity that port refers to is disabled.2 line=title Modem Connect LineL A modem connect line entity is associated with a physical circuit on the K node. Usually, there is one line entity for each circuit. The line-name. refers to the line managed by this command. 3 character =title Characteristics Attribute ALTERNATE SPEED Default: 0 L Alternate low speed, in bits per second, to operate the line. You can H modify this characteristic only when the entity is disabled. This N characteristic is supported only when the characteristic communications F mode is asynchronous, the characteristic modem control is full, @ the characteristic modem options includes rateselect, the J characteristic clock is internal, and when the alternate line speed  is needed. CALL ACCEPT TIMER Default: 0L Minimum time, in milliseconds, between t he assertion of data set readyK and accepting a call by asserting request to send. This attribute is I maintained only if the characteristic modem control is set to none. CARRIER LOSS TIMER Default: 15000K Maximum time, in milliseconds, that the carrier detect signal can be K absent before the loss of carrier event is generated. This attribute J is not supported if the characteristic modem control is set to none. CLOCK1 Source of the tr ansmit and receive clocks. 2 EXTERNAL - The modem provides the clock.B INTERNAL - The communications device provides the clock.G REFLECTED - The DTE transmit clock is a reflection of the DCE P transmit clock. This minimizes the clock to data skew that G the DCE encounters when high line speeds are used.E The default value depends on the setting of the characteristic O communications mode. If communications m ode is asynchronous, the default M value of this characteristic is internal. Otherwise, the default value  is external.O The value of this attribute has no effect when the communications line isO in loopback mode. In this case, the type of loopback determines the type L of clock. This characteristic can only be modified when the entity is  disabled. COMMUNICATIONS MODEM Default: Synchronous Value: Asynchronous or synchronousF Communications method to be used on the line. The value of this M characteristic is a copy of the communications mode argument specified H when the entity is created. You cannot modify this characteristic. COMMUNICATIONS PORT Default: NoneM Name of the communications port. The value of this characteristic is a L copy of the communications port argument specified when the entity is  created. DUPLEX= Default: Full  Value: Full or halfG Indicates whether the line is full- or half-duplex. The value of M this characteristic is a copy of the duplex argument specified when the entity is created.! CONNECTION TYPE (OSF/1)H! Default: Nonswitched Value: Nonswitched or switched!O! Indicates whether the line is switched or nonswitched. The value of this H! characteristic is a copy of the connection type argument specifiedH! when the entity is created. You cannot modify this characteristic. ENCODING? Default: Normal Value: Normal or nrziK Encoding technique used on the line. This characteristic can only be + modified when the entity is disabled.!! INITIAL HOLD TIMER (DEC OSF/1)! Default: 10!N! Maximum time, in seconds, that the entity waits for an incoming call to ! be accepted.'! MAXIMUM CALL SETUP TIMER (DEC OSF/1)! Default: 60!L! Maximum time, in seconds, that the entity waits for the outgoing call ! to connect.! MAXIMUM DISABLE TRANSMIT TIMER: Default: 500 Value: 0--60000L Maximum time, in milliseconds, that clear to send can remain asserted K before the line is disconnected after request to send is deasserted. M This attribute is not supported if the characteristic modem control is  set to none. MAXIMUM DSR DEASSERTION TIMER: Default: 5000  Value: 0--60000M Maximum time, in milliseconds, the entity will wait for data set ready L to be deasserted after it has deasserted data terminal ready. If this O timer expires, the entity assumes it can assert data terminal ready once J again. This attribute is not supported if the characteristic modem  control is set to none. MAXIMUM ENABLE TRANSMIT TIMER: Default: 2000 Value: 1--5000M Maximum time, in  milliseconds, between the assertion of the request to O send signal and receiving the assertion of the clear to send signal. ThisO attribute is not supported if the characteristic modem control is set to none. MINIMUM DTR DEASSERTION TIMER; Default: 1000 Value: 0--60000N Minimum time, in milliseconds, that the DTE will deassert data terminal K ready during a disconnection. This attribute is not supported if the 2 characteristic modem control is set to none. MODEM CONTROL@ Default: Full Value: Full or noneO Indicates whether the interchange circuits are to be monitored and used. C The value none means that only the data leads are monitored. G The value full must be used when the value of the characteristic D duplex is half. This characteristic is supported only if the 1 characteristic connection type is switched. MODEM OPTIONSD  Default: No options Value: Set of optionsA Set of values that determine the capabilities of the modem.N! DIALOUT - The modem can dial the remote modem. Supported only P! if the value of communications type is switched. This B! value is supported by Digital UNIX only. N! DIRECT - The modem is directly connected to the remote modem H! through a nonswitched line. Supported only if P! accompanied with dialout and used only when the modem L! protocol type supports direct dial. This value is 9! supported by Digital UNIX only.F RATE SELECT - The modem is capable of data rate selection. PROFILE% Default: None O Name of the local profile to be used with the line. This profile is used J to restrict the range of various line attributes, and to change the L defaults for those attributes. The value of this characteristic is a H copy of the profile argument specified when the entity is created. RATE SELECTD Default: High Value: High or lowK Specifies which of the line rates is to be used if none is specified  when a call is set up. B HIGH - The value of the speed characteristic is used.L LOW - The value of the alternate speed characteristic is used.H This characteristic is supported only if the characteristic modem H control is full, and if the characteristic modem options includes  rateselect. SPEED Default: 0 L High speed, in bits per second, to be used on the line. This value is N always used on asynchronous links. It is used on synchronous links only % in the following circumstances:= When the value of the clock characteristic is internal.*  When a null modem cable is detected.= When using a loopback mode that uses internal clocking.# SUCCESSFUL CALL INDICATION TIMER Default: 30N Maximum time, in seconds, that the entity will wait for indication of a K successful call before disconnecting the line. This attribute is not C supported if the characteristic modem control is set to none. SUPPRESS TEST INDICATORE Default: False Value: True or falseO  Specifies whether the test mode signal is to be monitored. If the value K is false, a change in the circuit will be monitored and will cause a , Test Indication event to be generated.D You should set this characteristic to true in cases where the L transitions of this signal are not produced by entering test mode, so ) that this signal should be ignored. TRANSMIT HOLDOFF TIMER% Default: 0 O Necessary delay, in milliseconds, between the transmitter being disabled L and then reenabled. The value 0 means that the request to send signal 9 can be asserted as soon as the client requests it.  M This attribute is not supported if the characteristic modem control is  set to none. 3 counter=title Counter Attributes  CABLE FAULTSJ Total number of times that the communications cable was detected as  missing or invalid. DEVICE ERRORSL Total number of times that a potential device error has been reported. FRAMING ERRORSO Total number of framing errors detected on the line. This counter is not I supported if the characteristic communications mode is synchronous. LOSSES OF CARRIERH Total number of times that the carrier on the line was lost. This L attribute is not supported if the characteristic modem control is set  to none. LOSSES OF CLOCKH Total number of times that the transmit or receive clock was lost.$! OUTGOING CALL FAILURES (DEC OSF1)! D! Total number of times that an outgoing call failed to connect. RATE FALLBACKSN Number of times that the DTE changed from the high data rate to the low K alternate rate. This counter is supported only if the characteristic J modem options includes rate select, and if the characteristic modem  control is full. TEST INDICATIONSK Number of times the DCE was put into  test mode by the remote system. M This attribute is not supported if the characteristic modem control is  set to none. TIMES CABLE DETECTEDK Total number of times that a valid communications cable was detected ? following a an error counted by the counter cable faults. TIMES DCE NOT READYF Total number of times that a dce not ready event occurred. This L attribute is not supported if the characteristic modem control is set  to none.! TIMES RESET L Number of times that the data link client has performed a line reset.  TRANSMIT ENABLE TIMEOUTSL Number of times the DCE failed to assert clear to send in response to N request to send. This attribute is not supported if the characteristic # modem control is set to none. 3 status=title Status Attributes ACTUAL SPEEDN Actual speed of the line, in bits per second. For internal clocking on J some microcoded devi "ces, a value of 0 indicates that the device has M selected a speed appropriate for the connected interface. For externalA clocking, a value of 0 indicates that the speed is unknown. DEVICE AVAILABILITY F Indicates whether the hardware device associated with the named N communications port is installed. Support is mandatory on systems that M support line card hot swap. When device availability has the value no L device, the interface state takes the va#lue pending DTE Ready and the 8 interface type attribute takes the value unknown.  INTERFACE STATE3 State of the physical interface on the line. K CONNECTED - A switched line is connected but not ready to 6 transmit or receive data.J CONNECTING - Call setup on a switched line is in progress.J DISCONNECTING - Call clear on a switched line is in progress.4 DTE NOT READY - The entity is$ disabled.H DTE READY - The DTE is ready, but the DCE is not ready.K FULL ENABLED - The line is enabled for data transmission and ' reception.N PENDING DTE READY - The entity is enabled but the ready state cannot O be entered. For example, the communications cable . is not connected.8 READY - Both DTE and DCE are ready.? RECEIVE ENABL%ED - The line is ready to receive data.E TRANSMIT ENABLED - The line is ready for data transmission. INTERFACE TYPE2 Type of the physical interface connection.  M LOOPBACK - A loopback connector has been detected on the interface.< NO CABLE - No cable is connected to the interface.F NULL MODEM - A null modem cable is connected to the interface.K RS232C - A cable conforming to the RS232C standard is attached.J & RS422 - A cable conforming to the RS422 standard is attached.J RS423-v24 - This value appears where a cable is attached but the M connector cannot distinguish between the RS423 and V.24  standards.J RS449 - A cable conforming to the RS449 standard is attached.B UNKNOWN - A cable is attached but its type is not knownG V28 - A cable conforming to any of the CCITT V.24, V.28 G ' standards, the IS 2110 standard, or the EIA-232-D  standard.I V35 - A cable conforming to the V.35 standard is attached.I X21 - A cable conforming to the X.21 standard is attached. LOOPBACK MODEN Type of loopback in use on the line. The value of this status attribute ; is determined by the startloop and stoploop commands.L CONNECTOR - Data is looped through a loopback connector attached to . ( the communications device.A DEVICE - Data is looped in the communications device.N DRIVER - Data is looped in the driver of the communications device.O EXTERNAL - Data is looped through a null modem or a modem in loopback  mode.K LOCAL - The communications device has switched its local modem ' into loopback mode.5 NULL - The line is not in loopback mode.L REMOTE - The commun)ications device has switched the remote modem ' into loopback mode. MODEM TYPEJ String identifying the local modem. If this status attribute has no / value, the type could not be determined.  STATE< Specifies the status of the modem connect line entity.* OFF - The line has been disabled.) ON - The line has been enabled.ww1 llc2 =title LLC2 J The LLC2 module implements one of the pro*tocols in the Data Link layer 2 described by the Digital Network Architecture. K The LLC2 entity is the top-level entity in the LLC2 module hierarchy of K entities. The LLC2 module controls the operation of the LLC Type 2 data . link protocol for local area networks LANs.I The hierarchical relationship of the entities that constitute the LLC2 module:" LLC2% Port Sap' Link +2 character =title Characteristics Attribute VERSIONN Version number of the DNA LLC2 architecture to which this implementationG conforms. You cannot modify this characteristic. To display this ( attribute, specify all or version.2 port=title LLC2 PortM An LLC2 port entity represents an access point to the services offered to M clients by the LLC2 module. The simple-name refers to the port managed by  this command.  2 status=title Sta,tus Attribute CLIENT/ Name of the client that opened the port. LINK NAMEK Name of the LLC2 sap link entity with which this port is associated. STATE% State of the LLC2 port entity.H OPEN - The port is assigned to a client and is enabled. J OPEN DISABLED - The port is assigned to a client but is disabled. 2 sap=title LLC2 SAPF Each LLC2 Port entity has an LLC2 SAP (service access point entity M associated w-ith it. An LLC2 Sap entity allows links to be multiplexed over  its associated port. 3 character =title Charateristics Attributes LAN STATIONI Default: No entity name Value: Local-entity-nameO Name of the LAN station entity used by the SAP. You must specify a value 3 for this attribute before you enable the SAP. LOCAL LSAP ADDRESSE Default: 7E Value: Hex-number L Address of the local. link service access point (LSAP) to be used. The O lowest significant bit of this value must be clear; that is, the address $ must be an individual address. 3 counter=title Counter Attributes TIMES SAP STATE CHANGED N Number of times the status attribute state has changed from on to off,  or from off to on. 3 status=title Status Attibutes LAN PORT H Name of the LAN port that is opened and enabled when this SAP is O s/uccessfully enabled. If the SAP is not enabled, this status has a null value. MAXIMUM PDU SIZE O Largest frame size, in octets, that can be used to send or receive data  on this SAP. STATE $ State of the llc2 sap entity." OFF - The SAP is disabled. " ON - The SAP is enabled. 2 sap_lnk=title LLC2 SAP LinkM An llc2 sap link entity represents one of the links that operates over a + particular SAP (service acces0s point ). 3 character!=title Characteristics Attributes ACKNOWLEDGE TIMER C Default: 1000 Value: 1--60000 N Time, in milliseconds, that the link waits for an acknowledgment before F initiating recovery action. The granularity of this timer is 10 G milliseconds. Values that are not multiples of 10 are rounded up. BUSY TIMER C Default: 10000 Value: 1--60000 G Time, in mil 1liseconds, that the link waits for indication of the N clearance of a busy condition at the remote station. The granularity of M this timer is 10 milliseconds. Values that are not multiples of 10 are  rounded up. HOLDBACK TIMER D Default: 500 Value: 0--60000 I Delay, in milliseconds, before an acknowledgment must be sent. The H granularity of this timer is 10 milliseconds. Values that are not % multiples of 10 ar2e rounded up. LOCAL RECEIVE WINDOW SIZE C Default: 127 Value: 1--127 8 Window size used by the link for receiving frames. MAXIMUM DATA SIZE E Default: 1028 Value: 1--65531 N Largest frame size, in octets, that the link can use to send or receive E data. This value does not include the size of the frame header. POLL TIMER E Default: 1000 3 Value: 1--60000 O Time, in milliseconds, that the link waits for a response with the F-bit M set. The granularity of this timer is 10 milliseconds. Values that are ) not multiples of 10 are rounded up. REJECT TIMER E Default: 3000 Value: 1--60000 P Time, in milliseconds, that the link waits for a reply to a REJ ( reject O frame. The granularity of this timer is 10 milliseconds. Values that are ) not multip4les of 10 are rounded up. REMOTE LSAP ADDRESS F Default: 7E Value: hex-number N Address of the destination LSAP (local service access point to be used J by the link. The lowest significant bit must be clear; that is, the , address must be an individual address. REMOTE MAC ADDRESS G Default: 00-00-00-00-00-00 Value: lan-address M Destination MAC address to be used by the link. The lowest sig5nificant L bit of the first octet must be clear; that is, the address must be an  individual address.  RETRY MAXIMUM D Default: 10 Value: 1--255 G Maximum number of times that the link retransmits a frame before E assuming a fatal error and taking more drastic recovery action. 3 counter=title Counter Attributes DATA OCTETS RECEIVED I Number of data octets received in I frames and UI frames from6 the J remote end of the link. This value does not include data octets in  retransmissions. DATA OCTETS SENT J Number of data octets transmitted in I frames and UI frames to the J remote end of the link. This value does not include data octets in  retransmissions. DATA PDUS RECEIVED L Number of I frames and UI frames received from the remote end of the 9 link. This value does not include retransmissions. DATA PDUS SENT M 7 Number of I frames and UI frames transmitted to the remote end of the 9 link. This value does not include retransmissions. FRMRS RECEIVED 5 Number of FRMR (frame reject) frames received. FRMRS SENT M Number of FRMR (frame reject) frames generated as a result of invalid  incoming frames. POLLS RECEIVED < Number of command frames received with the P bit set. REJS RECEIVED . Number of REJ (reject) frames received. 8 REJS SENT 1 Number of REJ (reject) frames transmitted. RNRS RECEIVED 9 Number of RNR (receive not ready) frames received. RNRS SENT < Number of RNR (receive not ready) frames transmitted.# TIMES ACKNOWLEDGE TIMER EXPIRED ? Number of times the local acknowledge timer has expired. TIMES BUSY TIMER EXPIRED 8 Number of times the local busy timer has expired. TIMES LINK HALTED M Number of times the link's status att9ribute protocol state was set to  halted. TIMES LINK INITIALIZING M Number of times the link's status attribute protocol state was set to  initializing. TIMES LINK INOPERATIVE N Number of times the link's status attribute protocol state was set to  inoperative. TIMES LINK RESETTING M Number of times the link's status attribute protocol state was set to  resetting. TIMES LINK RUNNING M Number of times t:he link's status attribute protocol state was set to O running. When the link enters the running state, the protocol has been( successfully initalized or reset. TIMES LINK SETUP FAILED M Number of times the LLC2 protocol fails to initialize correctly after % the maximum number of retries. TIMES LINK STATE CHANGED L Number of times the link's status attribute STATE changed from on to  off, or from off to on. TIMES POLL TIMER EXPI;RED 8 Number of times the local poll timer has expired. TIMES REJECT TIMER EXPIRED : Number of times the local reject timer has expired. XIDS RECEIVED % Number of XID frames received. XIDS SENT ( Number of XID frames transmitted. 3 status=title Status Attribute PROTOCOL STATE E State of the LLC2 protocol with respect to the remote station.D ERROR - The protocol is in a recognized error state.  < / HALTED - The protocol has halted. 9 INITIALIZING - The protocol is being initialized. N INOPERATIVE - The protocol cannot be started because the LAN station F cannot provide a connection to a remote system. 3 RESETIING - The protocol is being reset. 9 RUNNING - The protocol is running normally.  REMOTE LLC CLASS  Class of the remote LLC.C 1 - Class 1 LLC. Only type 1 o =peration is supported. P 2 - Class 2 LLC. Both type 1 and type 2 operations are supported. K UNKNOWN - The class has not yet been established. The class is not N established until XID frames have been exchanged between the8 local and remote LLC implementations.  REMOTE RECEIVE WINDOW SIZE N Window size used by the remote station for receiving frames. The local E station uses this value as its window for transmitting >frames. STATE % State of the llc2 link entity.$ OFF - The link is disabled. # ON - The link is enabled. ww\1 LAPBO The LAPB module implements one of the protocols in the Link layer described ( by the Digital Network Architecture. K You must install the product DEC WAN Device Drivers before you can refer1 to the LAPB Module entities in an NCL command.K The lapb entity is the top-level entity in the LAPB mod?ule hierarchy of N entities. The LAPB module implements the LAPB link-level protocol which is / a variation of the HDLC link-level protocol. 2 character!=title = Characteristic Attibutes VERSIONM Default: None Version: Current version numberO Version number of the DNA HDLC architecture to which this implementation 6 conforms. You cannot modify this characteristic.2 LINK=title LAPB Link K A lapb link entity is assoc@iated with a port of the supporting Physical K layer, and contains attributes that describe local LAPB operation. The : simple-name refers to the link managed by this command. 3 character=title Charateristic Attributes ACKNOWLEDGE TIMERF Default: Supplied by profile Value: 1--60000M Time, in milliseconds, to wait for an acknowledgment before initiating L recovery action. This attribute corresponds to the LAPB parameter T1. J You caAn modify this characteristic only when the entity is disabled. HOLDBACK TIMERF Default: Implementation specific Value: 0--60000J Delay, in milliseconds, before an acknowledgment must be sent. This O characteristic corresponds to the LAPB parameter T2. You can modify this 6 characteristic only when the entity is disabled. INTERFACE TYPEI Default: DTE Value: DCE or DTE! Address mode for this Blink.$ DCE - Use DCE address mode.$ DTE - Use DTE address mode.J You can modify this characteristic only when the entity is disabled. MAXIMUM DATA SIZEG Default: Supplied by profile Value: 1--65532K Maximum frame size, in octets, of an information field in an I-frame. PHYSICAL LINEM Default: No default Value: Local-entity-nameN Name of the Physical layer and line entity over whCich the LAPB protocol J is to operate. You must give this characteristic a value before you  enable the link. POLL TIMERN Default: Implementation specific Value: Supplied by profileO Maximum period in seconds that may elapse without frames being exchanged N on the Data Link. On expiration, an RR(P) is sent to elicit a response  from the other end. PROFILED Default: No default Value: StringI D Name of the X.25 Level 2 Profile that defines subscription details J associated with the PSDN to which this DTE is connected. You cannot L modify this characteristic. This characteristic is set by means of an % argument to the create command. RECEIVE BUFFERS D Default: Implementation specific Value: 1--1284 Specifies the number of receive data buffers.  RETRY MAXIMUMD Default: Supplied by profile Value: 1-E-255H Maximum number of times that a frame will be retransmitted before I assuming a fatal error, at which point more drastic error recovery L action will be attempted. This characteristic corresponds to the LAPB  parameter N2. SEQUENCE MODULUSF Default: Supplied by profile Value: 8 or 128! Type of sequence numbering.- 8 - Use normal sequence numbering. / 128 - Use extended sequence numbering. WFINDOW SIZEC Default: Supplied by profile Value: 1--127N Window size for transmitting and receiving I-frames. This characteristic * corresponds to the LAPB parameter K. 3 counter=title Counter Attributes BUFFER UNAVAILABLE ERRORS M Number of times that the underlying framing level has indicated system 4 buffer unavailability to the Data Link layer.  CRC ERRORS RECEIVED/ Number of frames received with a bad CRC.G DATA OCTETS RECEIVEDN Number of data octets received from the remote station. This value does " not include retransmissions. DATA OCTETS SENTL Number of data octets sent to the remote station. This value does not  include retransmissions. DATA PDUS RECEIVEDO Number of I-frames received from the remote station. This value does not  include retransmissions. DATA PDUS SENTI Number of I-frames sent to the remote station.H This value does not  include retransmissions. FRMRS RECEIVED% Number of FRMR frames received. FRMRS SENTM Number of FRMR frames generated as a result of invalid incoming frames. POLLS RECEIVED; Number of command frames received with the P-bit set. REJS RECEIVED$ Number of REJ frames received. REJS SENT' Number of REJ frames transmitted. RNRS RECEIVED$ Number of RNR frames received. RNRS SENT'I Number of RNR frames transmitted." TIMES ACKNOWLEDGE TIMER EXPIRED> Number of times the local acknowledge timer has expired. TIMES LINK HALTED= Number of times the link halt event has been generated. TIMES LINK INITIALIZINGE Number of times the link initializing event has been generated. TIMES LINK INOPERATIVED Number of times the link inoperative event has been generated. TIMES LINK MAINTENANCED Number of times the linkJ maintenance event has been generated. TIMES LINK RESETTING> Number of times the link reset event has been generated. TIMES LINK RUNNING@ Number of times the link running event has been generated. TIMES LINK SETUP FAILEDF Number of times the link setup failure event has been generated. TIMES LINK STATE CHANGED; Number of times a link state transition has occurred. TIMES PDU RECEIVE OVERRUNL Number of times a physical line indicaKted an overrun condition to the  Data Link layer. TIMES PDU TRANSMIT FAILED@ Number of times an attempt to transmit a frame has failed. 3 status=title Status Attributes LINE TYPE1 Type of line over which this link operates.4 NONSWITCHED - The line is a nonswitched line. 1 SWITCHED - The line is a switched line. MAXIMUM PDU SIZEH Maximum frame size, in octets, that this station will receive and 5 transmit. ThisL value includes the frame header. PHYSICAL PORTH Name of the Physical layer port with which the link is associated. PROTOCOL STATED State of the LAPB protocol with respect to the remote station.B ERROR - The protocol is in a recognized error state.. HALTED - The protocol has halted.8 INITIALIZING - The protocol is being initialized.M INOPERATIVE - The protocol cannot be started without connectivity to ) M the remote station.7 MAINTENANCE - The link is in maintenance mode.C RESETTING - The protocol is undergoing a reset operation.7 RUNNING - The protocol is running normally. STATE% Status of the lapb link entity." OFF - The link is disabled.! ON - The link is enabled.2 port=title Lapb PortL A lapb port entity represents an access point for LAPB module clients to O Data Link layer services. The poNrt-name refers to the port managed by this command. 3 status=title Status Attributes CLIENT NAME; Name of the client with which the port is associated. LINK9 Name of the link with which the port is associated. STATE$ State of the lapb port entity.7 OPEN - The port is assigned to a client.K OPEN DISABLED - The port is assigned to a client, but the associated ' link is disabled. TYPEO Type of port.< SEQUENCED - The port is used for sending LAPB data.N UNSEQUENCED - The port is used for sending loopback data. This is onlyL possible if the maintenance mode characteristic of the > relevant lapb link entity is set to true.wwL1 Frame =title FrameM The Frame module provides framing functions for a communications link. It O enables those who implement their own level 2 protocols t Po manage the links  that use those protocols.O You must install the product DEC WAN Device Drivers before you can refer to / the Frame Module entities in an NCL command.N The frame entity is the top-level entity in the hierarchy belonging to the L Frame module. The entity provides framing functions for a communications O link. The entity does not provide any data link protocol capabilities, and L is used by those who want or need to operate their own level 2 protocols.Q 2 Character%=title Characteristics Attribute VERSION N Version of the frame architecture to which the implementation conforms. , You cannot modify this characteristic. 2 status=title Status Attributes  STATE# State of the (frame) entity. - off - The frame entity is disabled., on - The frame entity is enabled. 2 frame_link=title Frame Link L A frame link entity is associated with a physical line, andR controls the K framing protocol used on that line. There is one frame link entity for  each physical line. 3 Character%=title Characteristics Attribute  BISYNC CODE ; Default: EBCDIC Value: ASCII or EBCDICN Character code to be used on the link. This characteristic is supported L only when the characteristic protocol is set to one of the following: M (bisync, chips, genbyte, or swift). You can modify this characteristic ' Sonly when the entity is disabled. BITS PER CHARACTER 1 Default: 8 Value: 5--8N Number of bits in each character. This characteristic is supported only N when the characteristic protocol is set to genbyte. You can modify this 6 characteristic only when the entity is disabled. BUFFER SIZE 4 Default: 512 Value: 0--65535K Size, in octets, of each receive buffer for the link. You can modify O this characterTistic only when the entity is disabled. Also, you can only ( increase the characteristic value. CONTROL MODE ; Default: Point-to-point Value: See descriptionF Control mode in which the link is to operate. The value of this K characteristic derives from the point to point argument to the create5 command. You cannot modify this characteristic. multipoint master multipoint tributary point-to-point CRC TYPE; Default: SUee description Value: See description CRC type used on the link. CRC_16 CRC_CCITT CRC_CCITT0 LRC_EVEN" LRC_ODD LRC_VRC_EVEN LRC_VRC_ODD NONE 0 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_16B genbyte crc checking is doVne in the genbyte framing routine. FRAMING TIMER3 Default: 25 Value: 10--1000N Maximum length of time, in milliseconds, to wait for the next character O to arrive. This characteristic is supported only when the characteristic ! protocol is set to genbyte. INITIAL STATE ONE: Default: 0 Value: See descriptionK First 32 bits of state information. This characteristic is supported M only when the characWteristic protocol is set to genbyte. You can modify; this characteristic only when the entity is disabled. INITIAL STATE TWO : Default: 0 Value: See descriptionO Last 32 bits of state information. This characteristic is supported only N when the characteristic protocol is set to genbyte. You can modify this 6 characteristic only when the entity is disabled. LOCAL STATION ADDRESS 1 Default: 255 Value: 0--255 XF Address of the local station. The default value means that only B broadcast messages are accepted. The interpretation of this L characteristic is controlled by the value of the characteristic match  station address. M This attribute is supported only if the characteristic protocol is set J to sdlc. You can modify this characteristic only when the entity is  disabled. MATCH STATION ADDRESS 8 Default: False Value: True or Y FalseN Specifies whether the value of the characteristic local station address L is to be interpreted as a valid address. This attribute is supported N only if the characteristic protocol is set to sdlc. You can modify this 6 characteristic only when the entity is disabled. NUMBER OF BUFFERS 0 Default: 4 Value: 0--255K Number of receive buffers reserved for the link. You can modify this J characteristic only when the entity isZ disabled. Also, you can only ( increase the characteristic value. PHYSICAL LINE ; Default: None Value: Local-entity-nameM Name of the Physical layer line entity on which the link operates. You O must provide a value for this characteristic before you enable the link. J You can modify this characteristic only when the entity is disabled. PROTOCOLJ Framing protocol used on the line. The value of this characteristic K derives [from the protocol argument to the create command. You cannot ! modify this characteristic. BISYNC HDLC CHIPS SDLC DDCMP SWIFT GENBYTE SYNC CHARACTER ; Default: See description Value: 0--FFI Hexadecimal code of the sync character to be used on the link. The L default value depends on the value of the characteristic protocol, as  follows: BISYNC\ CHIPS DDCMP GENBYTE SWIFT P This attribute is supported only if the characteristic protocol is set to E (bisync, chips, ddcmp, genbyte, or swift). You can modify this 7 characteristic only when the entity is disabled.  SYNC COUNT 7 Default: 4 Value: 0--255M Number of sync characters that precede each message. This attribute is N supported only if the characteristic protocol is] set to (bisync, chips, N ddcmp, genbyte, or swift). You can modify this characteristic only when  the entity is disabled. 3 counters=title Counter Attributes ABORT CHARACTERS RECEIVEDM Number of times that the link was prematurely terminated by the remote O station. This counter is supported only if the characteristic (protocol) ' is set to either (hdlc or sdlc).  DATA BLOCK CHECK ERRORSN Number of messages received with an error in ^ the data field block check. HEADER BLOCK CHECK ERRORSO Number of messages received with an error in the header block check. ThisK counter is supported only if the characteristic (protocol) is set to  (ddcmp).  INVALID CHARACTERS RECEIVEDM Number of times that an invalid character was received from the remote O station. This counter is supported only if the characteristic (protocol) , is set to either (bisync) or (ddcmp). ) RECEIVE BUFFER OVER_FLOWS WITH GOOD CRCN Number of times that the local station received a message too large for 9 the receive buffer and the message had a valid CRC. RECEIVE OVERRUNSN Number of times that the host memory was not able to handle all the data/ received from the communications channel. SDUS RECEIVED? Number of data messages received from the remote station. SDUS SENT9 Number of data messages sent to the remote station. SERVICE OCTETS RECEIVED`= Number of data octets received from the remote station. SERVICE OCTETS SENT7 Number of data octets sent to the remote station. TRANSMIT UNDERRUNSM Number of times that the host memory could not supply data fast enough , to satisfy the communications channel.3 status=title Status Attributes PHYSICAL PORT NAMEO Name of the Physical layer port returned when the port is opened. If this6 value is missing, the port has yet to be oapened. STATE' State of the (frame link) entity.! OFF - The link is disabled. ON - The link is enabled.2 port=title Frame PortK A frame port entity represents an access point to the data link service L offered by the Frame module. Ports are created and deleted automatically ) when a client of DDCMP uses the link. 3 status=title Status Attributes CLIENT5 Name of the client entity that opened the port. LINKbM Name of the (frame link) entity that the client supplied when the port  was opened. STATE% State of the frame port entity.7 OPEN - The port is assigned to a client.L OPEN DISABLED - The port is assigned to a client, but the appropriate 4 link entity has been disabled.ww  1 SessionB The Session layer is responsible for connection negotiation and N establishment. The Session Control module perfo crms the following functions:H o Manages transport connections on behalf of Session Control users.O o Enforces access control policies to restrict communication between users+ and between Session Control modules.M o Maps from a DNA Naming Service object name to protocols and addresses.N o Selects from the set of protocols supporting Session Control to attempt connection establishment.G o Maintains in the namespace the protocol and address information d J corresponding to objects that reside in the same node as the local  Session Control module.M The hierarchy of Session Control Module Entities is shown with indentation as follows:. Session Control/ Applications( Ports4 Tower Maintenance4 Transport service; Backtranslaetion softlink I The Session Control entity is the top-level entity in the hierarchy of 4 entities belonging to the Session Control module. 2 character!=title Characteristic Attributes  ADDRESS UPDATE INTERVAL= Default: 10 Value: 1-4294967296 P Minimum time, in seconds, allowed between updates of address information. J More frequent modification to the set of local towers is prohibited. BACKTRANSLATION SEARCH PATH fF Describes the order in which name services will be searched for O address-to-node-name translation requests when more than one name serviceF is in use on a node and any associated naming templates for each directory service. INCOMING PROXY? Default: True Value: Boolean O Specifies whether to honor incoming proxy requests. If this attribute is H set to false, requests to invoke proxies on incoming requests are  g ignored. INCOMING TIMER? Default: 45 Value: 0-65535K Time, in seconds, to wait for a user module to issue an accept/rejectL call after a port enters a state indicating that a connection request O was received. If the timer expires, Session Control aborts the transport E connection with a timed out error. For OpenVMS, a zero 0 value H directs Session Control to wait indefinitely without aborting the  connectionh.  MAINTAIN BACKWARD SOFT LINKS? Default: False Value: Boolean N Specifies whether Session Control should attempt to update the backward H translation soft links when it detects an address change. If this J attribute is set to false, Session Control will add no new backward H translation soft links and it may delete any that it has created.  MODIFY ACS CONTROL SET@ Default: True i Value: Boolean I Specifies whether Session Control should attempt to update the ACS K access control set of the node object whenever it attempts to update 9 the towers attribute for the node in the namespace.# NAMING CACHE CHECKPOINT INTERVAL  M Amount of time, in hours, between times when the address and node-name K information is checkpointed to disk from the in-memory, local naming cache.! NAMING CACHE ENTRY ! P! j Address and node-name information for a node that has been retrieved fromL! a name service and is currently stored in the in-memory, local naming ! cache.!! NAMING CACHE TIMEOUT E Amount of time, in days, after which the address and node-name O information for a node is deleted from the in-memory, local naming cache. NAMING SEARCH PATHE Describes the order in which name services will be searched forH node-name-to-address translation reqkuests when more than one name K service is in use on a node, and any associated naming templates for  each name service.  NON PRIVILEGED USER  F Specifies the Session Control on a non-privileged user account.   SOFTLINK TIMERI Default: 30 days Value: binary relative time N Interval of time, in days, DECdns checks that an object pointed to by a 2 backward translation soft link still exists.  OUTG lOING PROXY< Default: True Value: Boolean O Specifies whether to invoke a proxy on outgoing connection requests when N the user does not explicitly specify to do so. If this attribute is set $ to false, no proxy is invoked. OUTGOING TIMER< Default: 60 Value: 0-65535 K Time, in seconds, to wait for an outgoing transport connection to be M accepted before Session Control aborts the connemction with a timed out I error. For OpenVMS, a zero 0 value directs Session Control to wait 3 indefinitely without aborting the connection. UPDATE RETRY INTERVALA Default: 60 Value: 1-4294967296 L Time to wait before Session Control retries a failed attempt to update@ information in the namespace. The default is 60 minutes. ! TRANSPORT PRECEDENCEG! Default: OSI Value: Set of OSI or NSnP!J! Sets the order in which transports are selected when establishing a Q! 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. ! ! VERSIONF Session Control protocol version number. You cannot modify this  characteristic. 2 Counter =title Counter Attributes ACCESS CONTROL VIOLATIONS N Number of tiomes Session Control has detected an access control violation event. BACKTRANSLATION DELETIONSN Number of times Session Control has detected a backtranslation deletion event. BAD BACKTRANSLATION LINKSJ Number of times Session Control has generated a bad backtranslation  link event. DANGLING LINKJ Number of times Session Control has detected a dangling link event.  DELETED MAINTAINED OBJECTSO Number of times Session Contprol has detected a deleted maintained object event. VERIFICATION FAILURESP Number of times Session Control has detected a verification failure event. 2 status=title Status Attributes  BACKTRANSLATION DIRECTORY= Name of the root directory of the backtranslation tree. STATE, Status of the Session Control entity. wwH01 session_app"=title Session Control ApplicationI A Session Control application entity sqtores information about an end N user that is activated for receipt of an incoming connection request when N the request contains that end user's name in its destination name field. 2 character!=title Characteristics Attributes ADDRESSESL Default: empty-set Value: Set of end-user specificationsL A set of end-user specifications, any one of which, when specified in K the destination name field of an incoming connection request, causes 8 r applications defined by this entity to be invoked. CLIENT NAME= Default: None Value: Entity name O Identifies the name of the local user that will be activated upon receiptM of a connect request containing a destination name matching one of the 0 values in the destination names attribute. IMAGE NAMEE Default: No Image Name Value: File Specification O File name of a program to be invoked upon sreceipt of a connection requestP containing an address that matches one of the values contained in the set 1 described by the addresses characteristic.  INCOMING ALIAS J Specifies how a particular application responds to incoming connect M requests directed to the alias node address. If false, the application I does not allow a specified application to receive incoming connect B requests that have been directed to the alias node address.  INCOMI tNG OSI TSEL O The TSEL this image will accept connections for. This is similar to the L destination names attribute. However, applications using this access P point for in-connection matching do not use DNA Session Control protocol.  INCOMING PROXY@ Default: True Value: BooleanO Specifies whether to honor incoming proxy requests. If this attribute is H set to false, requests to invoke proxies on incoming requests are O u ignored. The setting of this characteristic overrides the setting of the F Session Control incoming proxy characteristic for the specified  application. NODE SYNONYMA Default: False Value: Boolean O Default form in which the remote node name is passed to the application. * FALSE - The full node name is used.N TRUE - The node synonym is used; if no synonym is available, the full  name is used.v OUTGOING ALIAS N Specifies whether a particular object uses the alias node identifier in K its outgoing connect requests. If false, the specified object is not N allowed to use the alias node address in its outgoing connect requests.  OUTGOING PROXY N Default action to execute when user does not explicitly specify whether or not to invoke a proxy. USER NAMEC Default: None Value: Latin1StringL Idenwtifies the default account under which the application is to run. L For OpenVMS, if null then system defaults are used to select the user. 2 status=title Status Attributes  PROCESS IDENTIFIERSM Specifies a set of processes that are active instances of the specific  application.  wwH01 session_back0=title Session Control Backtranslation SoftlinksM A Session Control backtranslation softlink entity stores information about xL entries in the backtranslation soft link database. The name is the uniqueL name among the set of backtranslation soft-link subentities maintained by  Session Control. 2 counters=title Counter Attributes UPDATE FAILURES: Number of times an update for this subentity failed. UPDATE SUCCESSES= Number of times an update for this subentity succeeded. 2 Status=title Status Attributes LAST FAILURE REASON8 Failure reason fory the most recent update failure. LAST SUCCESSFUL UPDATE> Most recent time an update for this subentity succeeded. LAST UPDATE COMPLETED> Most recent time an update for this subentity completed. LAST UPDATE STARTEDB Most recent time an update for this subentity was initiated. NETWORK ENTITY TITLE. Network entity title for this soft link. STATEK Status of this entity instance. Values include create, delete, exist  and !zretarget.  TARGET Target for softlink.wwH01 session_port=title Session Port O A Session Control port entity stores Session Control information about the  transport connection.  2 status=title Status Attributes CLIENTL Network management name specified by the user of the port when it was opened. DIRECTIONK Specifies whether the port is open to initiate an outgoing transport 0 conn{ection or to receive an incoming one.  6 UNKNOWN - Port status is unknown at this time.M INCOMING - Port was opened to handle an incoming transport connection.L OUTGOING - Port is open to initiate an outgoing transport connection.I LISTENING - Port is open to receive incoming transport connections. LOCAL END USER ADDRESSO Address assigned by the user of the port when it was opened. On outgoing P connections this value is sent in the sour|ce name field of the connection E request; on incoming connections this value is received in the , destination name field of the request. NODE NAME SENTA Node name that was received or sent in the connect request. REMOTE END USER ADDRESSM Address of the remote end user of the port. This value was either sent L in the destination name field of an outgoing connection request or wasM received in the source name field of an incoming connection requ}est. IfI the value of the direction attribute is incoming or unknown and no K connection request has been received, the value of this attribute is null.  TRANSPORT PORTN Network management name of the transport port being used by this session control port. VERSION SENT? Version that was received or sent in the connect request.ww V1 session_tower(=title Session Control Tower MaintenanceH A Session Control ~Tower Maintenance entity stores information about N entries in the Tower Maintenance data base. A Tower Maintenance entity is K automatically created when a client issues a dnaKeepMeHere call, using the programming interface.  2 counters=title Counter Attributes UPDATE FAILURESD Number of times this entity detected an update failure event.  UPDATE SUCCESSESM Number of times that the DNA$Towers attribute of the DECdns object nameA associated with this entity has been successfully updated. 2 status=title Status Attributes MANAGING CLIENTM Network management name of the user who issued the keepmehere call that/ resulted in the creation of this entity.  HIGHER TOWERSN Set of higher towers that was passed in the keepmehere call that created this entity.  LAST FAILURE REASONN DECdns error code that indicates the reason for the last update failure. LAST SUCCESSFUL UPDATEL Time of the last successful update to the DNA$Towers attribute for theP specified entity. On OpenVMS, if no update for this subentity ever failed, then it is zero. LAST UPDATE COMPLETEDM Time that the last attempt to update the DNA$Towers attribute completed successfully or not.  LAST UPDATE STARTEDK Time that the last attempt to update the DNA$Towers attribute for the& specified entity was initiated. ww V1 session_trans(=title Session Control Transport ServiceH A Session Control transport service entity stores information about B modules in the Transport layer that support Session Control.  2 status=title Status Attributes PROTOCOLL Transport protocol used by this transport service, as specified by theL user when this service was created. See the create command description$ for a list of possible values. TSELK Transport selector used by the OSI Transport Module to bind incoming E connection requests to Session Control. This attribute is not $ applicable for NSP transport. ww