22.5 session control proxy (Digital UNIX)
A session control proxy entity stores the information that
grants remote users proxy access to given application subentity
instances. See Chapter 4 for further information about proxy access.
add [node node-id] session control proxy
name {application [set of simple names] | source end users
[set of records] }
create [node node-id] session control proxy
name
delete [node node-id] session control proxy
name
remove [node node-id] session control proxy
name {applications [set of simple names] | source end users
[set of records] }
set [node node-id] session control proxy
name
show [node node-id] session control proxy
name [all [attributes] | all characteristics | all counters |
all identifiers | all status ]
22.5.1 Characteristic Attributes
applications
Set of application identifiers, one of which must match the application requested. If this attribute value is null, any requested application will match.
Default: None Value: Set of simple name source end users
Set of remote end users for whom this proxy entry applies. An unspecified end user implies all end users on the node specified in the same record. The record format has two fields: node which has a data type of fullname, and end user which has a data type of enduserspecification.
Default: None Value: Set of record target user
Local user name under which access is granted.
Default: None Value: Latin1String type
Type of proxy entry: explicit means that the destination the user requested in the connect request must match the target user for this entry; default means if no explicit entry matches, this entry will be tried. An explicit proxy entry matches before a default one.
Default: Explicit Value: Explicit or default
creation time
Time the entity was created and associated counter attributes were zero.used
Number of times this proxy entry was used to gain access to one of the applications.
name
Simple name assigned to a particular entity instance. The name is the management identifier for the proxy database entry and is kept unique among the entries in this database maintained by Session Control.
last time used
Last time this proxy entry was used to gain access to one of the applications.
For create:
already exists
A session control proxy entity already exists.
22.6 session control tower maintenance
A session control tower maintenance entity stores information
about entries in the tower maintenance database. A tower maintenance
entity is created automatically when a client issues a
dnaKeepMeHere call, using the programming interface. The
name refers to the tower maintenance entity managed by this
command.
delete [node node-id] session control tower
maintenance name
show [node node-id] session control tower
maintenance name [all [attributes] | all counters | all
identifiers | all status ]
update [node node-id] session control tower
maintenance name
22.6.1 Commands
update
Updates tower maintenance entity.
creation time
Time this entity was created.update failures
Number of times this entity detected an update failure event.update successes
Number of times the DNA$Towers attribute of the DECdns object name associated with this entity has been successfully updated.
name
Full-name assigned to the tower maintenance entity when it is created.
client
Network management name of the user who issued the keepmehere call that resulted in the creation of this entity.higher towers
Set of higher towers that was passed in the keepmehere call that created this entity.last failure exception (Digital UNIX)
Reason for the most recent update failure. If no update for this subentity ever failed, then it is zero.last failure reason
DECdns error code that indicates the reason for the last update failure.last successful update
Time of the last successful update to the DNA$Towers attribute for the specified entity. On OpenVMS, if no update for this subentity ever failed, then it is zero.last update completed
Time that the last attempt to update the DNA$Towers attribute completed (successfully or not).last update started
Time that the last attempt to update the DNA$Towers attribute for the specified entity was initiated.uid
Entity's unique identifier, which is generated when the entity is created.user (Digital UNIX)
User name of the user who created this tower maintenance subentity with the keepmehere procedure call. This is different from client, which refers to a local entity name.
update failure
Generated each time an attempt to update a DNA$Towers attribute fails.
22.7 session control transport service
A session control transport service entity stores information
about modules in the Transport layer that support Session Control. The
transport-name refers to the transport service managed by this
command.
create [node node-id] session control
transport service transport-name {protocol
protocol-id | tsel hex-string }
delete [node node-id] session control
transport service transport-name
show [node node-id] session control transport
service transport-name [all [attributes] | all counters | all
identifiers | all status ]
22.7.1 Arguments
These arguments apply only to the create directive.
protocol protocol-id
Transport protocol to be used by this transport service.
'04'H This transport service uses the NSP transport protocol. '05'H This transport service uses version 1 of the OSI transport protocol. tsel hex-string
Transport selector used by the OSI transport module to bind incoming connection requests to Session Control. The default value is the hexadecimal representation of "DEC0." This argument is not applicable for NSP transport.
creation time
Time the entity was created.
name
Simple name assigned to the transport service when it is created.
protocol
Transport protocol used by this transport service, as specified by the user when this service was created. (See the create command description for a list of possible values.)tsel
Transport selector used by the OSI Transport Module to bind incoming connection requests to Session Control. For Digital UNIX, The TSEL value is specified in a create command. This attribute is not applicable for NSP transport.
For create:
already exists
The session control transport service entity already exists.duplicate protocol
The session control transport service entity fails on creation because the protocol already exists.protocol not supported
The session control transport service entity fails on creation because the protocol is not supported by this module.wrong state (Digital UNIX)
This entity cannot be deleted while there are connections using this transport.
This chapter describes all the commands you can use to manage the entities that constitute the IEEE 802.5/Token Ring module. The Token Ring module implements one of multiple possible Link level/Physical level modules in the OSI layered architecture model.
The DNA IEEE 802.5/Token Ring Data Link provides either a 4- or 16-Mb/s local area network (LAN). It provides communication services for multiple concurrent users. The services provided are logical link control (LLC), mapped Ethernet and station management (SMT) services.
Figure 23-1 shows the hierarchical relationship of the entities that constitute the Token Ring module.
Figure 23-1 Hierarchy of Token Ring Module Entities
The DNA IEEE 802.5/Token Ring module incorporates the functions and operations defined in the IEEE 802.5 Token Ring Access Method, parts of the ISO 8802-1 (IEEE 802.1) Addressing, Internetworking and Network Management, and parts of the ISO 8802-2 (IEEE 802.2) Logical Link Control (LLC) specifications. To this, the DNA 802.5/Token Ring Data Link adds features often needed by users of the data link. A typical such user is the Network layer of the Digital Network Architecture (DNA).
23.1 token ring
The token ring entity is the top-level entity in the hierarchy
of entities belonging to the Token Ring module.
create [node node-id] token ring
delete [node node-id] token ring
show [node node-id] token ring [all
[attributes] | all characteristics ]
23.1.1 Characteristic Attributes
version
Version number of the Token Ring architecture specification to which the implementation conforms. You cannot modify this characteristic.
Default: Current version number
For create:
already exists
A token ring entity already exists.For delete:
has children
Cannot delete while subentities exist.
23.2 token ring station
A token ring station entity manages a Token Ring controller.
Each station corresponds to a particular instance of logical link
control (LLC), medium access control (MAC), and physical attachment.
The Token Ring data link can be monitored and controlled through DNA
network management. The station-name refers to the station
managed by this command.
create [node node-id] token ring station
station-name communication port device-name
delete [node node-id] token ring station
station-name
disable [node node-id] token ring station
station-name
enable [node node-id] token ring station
station-name mode station-mode transparent source
routing function-mode
show [node node-id] token ring station
station-name [all [attributes] | all characteristics | all
counters | all identifiers | all status ]
23.2.1 Arguments
communication port device-name
A Digital UNIX device name to assign to this station. The name must be in the format ddn, where dd is the device name prefix and n is the device number.
Device device-name DETRA tra0 mode station-mode
The mode this station will be enabled to. Can be either normal (default) or loopback.transparent source routing function-mode
Indicates whether the transparent source routing functionality will be enabled. The default is enabled. This value cannot be disabled.
aging timeout
Controls the timeout of the source routing information for nodes with which the local node has not recently communicated.
Default: 60 seconds Value: 1--65535 communication port
Name of the hardware port associated with this station, taken from the corresponding argument in the create directive. You cannot modify this characteristic.discovery timeout
Controls the timeout of the source routing discovery process.
Default: 1 second Value: 1--255 etr
Determines if Early Token Release (ETR) is in use on this station. ETR may be supported only on 16-Mb/s media. This attribute can only be set in the off state.
Default: True Value: True or false maximum source routes
The maximum number of source route subentities this station will buffer. Can only be set in the off state.
Default: 1024 Value: 256--2048 monitor contender
Determines if the station will try to become the active monitor, if a lower addressed station starts the monitor contention process. This attribute can only be set in the off state.
Default: False Value: True or false ring speed
The data rate of the media. Can only be set in the off state.
Default: Unknown Value: 4 or 16 Mbps station address
The desired station address. The bits in each byte of an address must be reversed, for example, 08-00-2b-11-22-33 would become 10-00-d4-88-44-cc. This attribute can only be set in the off state.
Default: Hardware ROM address Value: None
Unless stated otherwise, counts include both normal and multicast traffic and all protocol types, service access points (SAPs), and protocol identifiers.
abort delimiters sent
Number of times an abort delimiter was sent while transmitting.auto-removal failures
Number of times a failure during the beacon auto-removal process was detected and the station removed itself from the ring.burst errors
Number of times a lack of transitions was detected on the physical media.creation time
Time at which the station entity was created.explorer frames received
Number of source routing (SR) explorer frames received by the source route entities.explorer frames sent
Number of source routing (SR) explorer frames sent by the source route entities.frame copied errors
Number of individually addressed frames received with the Address Recognized status bit = 1.frequency errors
Number of times an error was detected in the incoming signal frequency.insertion failures
Number of times a ring insertion operation has failed.internal errors
Number of times a recoverable internal error was recognized.line errors
Number of times a CRC error or a non-data symbol in a frame or token with the E bit = 0 was detected.lobe wire faults
Number of times an open or shorted lobe data path was detected and the station removed itself from the ring.lost frames
Number of times this station has transmitted a frame and has failed to receive it for stripping before the Timer Return to Repeat (TRR) timer expired.multicast octets received
Number of octets successfully received in multicast frames of type LLC. (The count does not include the MAC envelope.)multicast octets sent
Number of octets successfully sent in multicast frames of type LLC. (The count does not include the MAC envelope.)multicast pdus received
Number of multicast frames successfully received of type LLC.multicast pdus sent
Number of multicast frames successfully sent of type LLC.octets received
Number of octets successfully received in frames of type LLC.octets sent
Number of octets successfully sent in frames of type LLC.pdus received
Number of frames successfully received of type LLC.pdus sent
Number of frames successfully sent of type LLC.receive data overruns
Number of times a frame was lost due to system or adapter transfer failure.receiver congestions
Number of frames recognized as matching one of this station's individual, group, or functional addresses, but could not be received for lack of buffers in the adapter.remove frames received
Number of times a remove MAC frame has been received and the station removed itself from the ring.ring beaconings
Number of times the condition of receiving or transmitted beacon frames was detected due to a hard error.ring failures
Number of times the station left the ring due to failure.ring recoveries
Number of times detected the ring is in the monitor contention process. Indicates that the ring has attempted to recover from a soft error problem.ring poll errors
Number of times an error was detected in the A and C bits during the ring poll process.route discovery failures
Number of times the route discovery process failed to find a route to another station.selftest failures
Total number of times a self-test of the station detected an error.signal losses
Number of times detected loss of signal on the physical media.single station conditions
Number of times detected being the only station in the ring.soft error reports sent
Number of times sent a report error MAC frame to the ring error monitor.unavailable station buffers
Number of times a frame was discarded because no station level buffers were available.unavailable user buffers
Number of times a frame was discarded because no user buffer was available.unrecognized individual destination pdus
Number of times a received individually addressed LLC frame was discarded because there was no data link port with a matching SAP, SNAP PID, or Ethernet protocol type.unrecognized multicast destination pdus
Number of times a received LLC frame addressed to an enabled group or functional address was discarded because there was no data link port with a matching SAP, SNAP PID, or Ethernet protocol type.token errors
Number of times when this station (when Active Monitor (AM)) has transmitted a new token due to errors on the ring.transmit failures
Number of times a transmit error, other than underrun occurred. Transmit error reasons can be tracked by event reasons, or by observing other 802.5 counters.transmit underruns
Number of times a transmit underrun occurred.transmitting beacons
Number of times initiated transmitting beacon frames.
name
Simple name assigned to the station when it is created.
authorized access priority
The maximum transmit priority allowed for this station. The value is set by the ring parameter server.authorized function classes
The bit map of the authorized function classes for this station.functional address
The functional address bit map enabled in the adapter for the reception on this station.group addresses
The set of group addresses enabled in the adapter for reception on this station.insert error reason
Reason code for an insertion error if there was a failure to insert into the ring, or insertion successful if no error.
no open An error occurred during the insertion phase. bad parameters Invalid options specified to the adapter to insert into the ring. lobe fault Lobe test fault or MAC frames were received before physical insertion. signal loss Signal loss condition was detected during the insertion phase. timeout Logical insertion onto the ring failed before insertion timer expired. ring failure Unable to receive its own ring purge MAC frames after becoming the active monitor. ring beaconing A beacon MAC frame was received after physical insertion onto the ring. duplicate address Another station on the ring already has the address this station wishes to use. parameter server error A ring parameter server (RPS) is present on the ring but does not respond to a request initialization MAC frame. remove frame received A remove station MAC frame was received during the insertion process. insertion successful The insertion phase was successful. link state
Data link state of this ring station.
off Station is not on the ring. running Station is available to the user for processing. initializing Station is in process of inserting into the ring. recovery Station is beaconing. contending Station is participating in the monitor contention process. broken Station has failed the insertion process. MAC address
The currently active station address value for which the data link is receiving an individually addressed frame.nearest upstream neighbor
The MAC address of the last known upstream ring neighbor as heard from the ring poll process.physical drop number
The physical drop number assigned by the ring parameter server.receive mode
The receive mode of the station. Normal or promiscuous.ring error reason
Reason code for the most recent ring error detected by this station or no error if none has occurred.
no error Successful operation, no error has occurred. ring in recovery Claim token MAC frames were observed on the ring. single station It sensed this is the only station on the ring. remove frame received A remove ring station MAC frame request was received and the station has deinserted from the ring. auto-removal failure The auto-removal process has failed and the station has deinserted from the ring. lobe fault An open or short circuit in the lobe wire cable was detected. transmitting beacon Beacon frames are transmitted to the ring. soft error frame sent A report error MAC frame has been transmitted. beaconing condition Beacon frames are presently transmitted or received to or from the ring. signal loss A loss of signal was detected on the ring. open in progress Station is in process of inserting into the ring. ring number
The local ring number as received from the ring parameter server.ROM address
The IEEE universally administered address present in the ROM of the adapter.transparent source routing
State of transparent source routing support.state
Operational state of the station.uid
Entity's unique identifier, which is generated when the entity is created.
abort delimiter sent
Station has transmitted an abort delimiter.auto-removal failure
Self-test failed following a beacon auto-removal process.burst error
Absence of transitions on the physical media.frame copied error
This station received a frame addressed to its MAC address with the A and C bits set.internal error
Station has detected an internal error.line error
CRC error or Manchester violation detected in a token or frame with the E bit = 0.lobe wire fault
Short or open circuit detected on cable.lost frame error
TRR timer expired while this station was transmitting.receive data overrun
A receive overrun hardware error was detected.remove frame received
Remove ring station MAC frame received.ring beacon initiated
The station started the beacon process.ring beaconing
Beacon MAC frames being sent or received.ring poll error
Failure to properly set A and C bits during the ring poll process.ring recovery
Station is receiving or transmitting claim token MAC frames.route discovery failure
Route discover timer expired.selftest failure
The implementation-specific self-test procedures have detected a failure.signal loss
Loss of signal on the physical media.single station detected
The only station participating in the ring poll process.soft errors reported
Soft error report MAC frame sent to ring error monitor.station buffer unavailable
No buffer was available to receive a frame.token error
This station, as active monitor, has had to transmit a new token following an error condition.transmit failed
Failure to transmit operation other than underrun.transmit underrun
Transmit failed due to underrun.unrecognized individual pdu destination
An individually addressed frame with unrecognized DSAP or protocol ID.unrecognized multicast pdu destination
A globally addressed frame with unrecognized DSAP or protocol ID.user buffer unavailable
Data link user did not supply a receive buffer.
For create:
already exists
A token ring station entity already exists.communication port in use
A communication port is already reserved by another entity.invalid communication port
Cannot run Token Ring data link on this communication port.
Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]
![]()
NCL_PROFILE_028.HTML OSSG Documentation 2-DEC-1996 12:48:43.83Copyright © Digital Equipment Corporation 1996. All Rights Reserved.