![[previous]](../../../graphics/l_arrow.gif){kind=icon}
![[next]](../../../graphics/r_arrow.gif){kind=icon}
This chapter describes the parameters that are related to data link connectivity for local area and wide area traffic using the Synchronous Data Link Control (SDLC) Service. Table 111 lists the SDLC Service parameters and commands.
.
Syntax
SETDefault !<CU Name> -SDLC CUAddr = <value> (hex 01-FF)
SHow [!<CU Name> | !*] -SDLC CUAddr
C1
The CUAddr parameter specifies the poll address of the secondary control unit (CU). If the bridge/router is acting as the SDLC primary for this CU, the address must match the poll address recognized by the CU. If the bridge/router is acting as the SDLC secondary, the address must match the poll address configured by the SDLC primary, for example the Network Control Program (NCP).
Syntax
SHow [!<CU Name> | !*] -SDLC CUCONFig
No default
The CUCONFig parameter displays the value of all CU-related parameters for the specified CU and the current state of the CU connection.
Syntax
SETDefault !<CU Name> -SDLC CUCONTrol = Enabled | Disabled
SHow [!<CU Name> | !*] -SDLC CUCONTrol
Disabled
The CUCONTrol parameter sets the state of the CU when the bridge/router is started or rebooted. Once enabled, the bridge/router continually tries to activate the CU at initial startup time (after a system reboot). If this parameter is disabled, the CU connection is disabled at startup. After the bridge/router has started, the state of the CU may be changed with this parameter.
Although the CU may be enabled by CUCONTrol, it cannot become active with frames being sent and received until PCONtrol (see "PCONtrol" later in this chapter) for the port, and the PORT and PATH CONTrol are enabled, and PORT OWNer is set to SDLC.
Syntax
SHow [!<CU Name> | !*] -SDLC CUInfo
FLUSH [!<CU Name> | !*] -SDLC CUInfo
No default
The CUInfo parameter displays counters and statistics for the current SDLC connection with the specified CU (or all CUs). If the CU is not currently active, counters are displayed from the last connection for that CU.
Syntax
SETDefault !<CU Name> -SDLC CULocalMac = <MAC address>
SHow [!<CU Name> | !*] -SDLC CULocalMac
No default
The CULocalMac parameter specifies the LAN source address to use in logical link control 2 (LLC2) frames being sent by the bridge/router on behalf of the specified CU. This media access control (MAC) address is also compared with the destination MAC address of the local LLC2 frames received by the bridge/router to determine to which CU the frame is sent.
3Com recommends using a locally administered address. See the Configuring LAN Address Administration chapter in Using Enterprise OS Software.
Values
|
<MAC address> |
The MAC address of the CU. The SDLC Service interprets MAC addresses in the form: %123456789123 or noncanonical (token-ring) address form. |
The display of MAC addresses for the CULocalMac parameter now includes both canonical and noncanonical format.
No two CUs on the same bridge/router can have the same CULocalMac and CULocalSap configuration. The system may not be able to correctly route received LLC2 packets to the intended CU. MAC addresses must be unique within a network.
Syntax
SETDefault !<CU Name> -SDLC CULocalSap = <sap value> (Hex 04-EC)
SHow [!<CU Name> | !*] -SDLC CULocalSap
0x04
The CULocalSap parameter sets the Service Access Point (SAP) being used for the local end of a LAN (LLC2) connection for the specified CU. The SAP value specified is used as the source SAP for LLC2 frames sent by the bridge/router for the CU. This value is also compared to the destination SAP on LLC2 frames received by the system to determine which CU should receive the frames.
|
<sap value> |
Enter the SAP value of the CU that is the source of the LLC2 frames. |
The SAP value for this parameter must be from 0x04 through 0xEC. The SAP value must be divisible by 4. No two CUs on the same bridge/router may have the same CULocalMac and CULocalSap combination.
Syntax
SETDefault !<CU Name> -SDLC CUMAXout = <number> (1-7)
SHow [!CU Name> | !*] -SDLC CUMAXout
4
The CUMAXout parameter specifies the maximum number of unacknowledged data frames that can be sent to the CU on the specified port. For example, if this value is set to 3, the bridge/router will send no more than three data frames to a CU before requesting an acknowledgment even if it has more data to send.
The value selected for this parameter should be consistent with the host configuration of the CUs attached to this port; the bridge/router should be configured to send no more frames than a CU can handle. See your host configuration for this CU.
The CUMAXout parameter only applies when PMODulo (see "PMODulo" later in this chapter) is set to 8. If PMODulo is set to 128 a value of 12 is used for CUMAXout.
When modulo 128 sequencing is used, the bridge/router accepts no more than 12 unacknowledged I frames; if a station attempts to send the bridge/router more than 12 frames in a single polling cycle, the bridge/router disconnects the station.
Values over 7 are not used unless PMODulo is 128.
Syntax
SETDefault !<CU Name> -SDLC CUMOde = Originate | Answer
SHow [!<CU Name> | !*] -SDLC CUMOde
Originate
The CUMOde parameter configures the CU to either originate a network connection request or answer a connection request from the network. This parameter must be set correctly to ensure that SDLC connections and LLC2 connections are initiated at the correct time and in the correct order. See the Configuring Synchronous Data Link Control Connectivity chapter in Using Enterprise OS Software.
Syntax
SHow -SDLC CUNAme
The CUNAme parameter displays all of the CUs defined on the bridge/router.
Syntax
SETDefault !<CU Name> -SDLC CUPollTimer = <milliseconds> (200-1000)
200
The CUPollTimer parameter specifies the minimum delay time in milliseconds before a station is polled. The poll delay occurs in the following cases:
This parameter is used only on ports on which the PROle parameter is set to Primary.
Syntax
SETDefault !<CU Name> -SDLC CUPOrt = <port number>
SHow [!<CU Name> | !*] -SDLC CUPOrt
The port number that is assigned by the PortCU parameter (see "PortCU" later in this chapter) becomes the default for the specified CU.
The CUPOrt parameter displays the port assignment you create with PortCU , or changes the port assignment of the CU specified by that definition.
Values
|
<port number> |
The port to which the CU should be assigned. |
Syntax
SETDefault !<CU Name> -SDLC CURemoteMac = <MAC address>
SHow [!<CU Name> | !*] -SDLC CURemoteMac
No default
The CURemoteMac parameter specifies the MAC address for the destination CU. When the system initiates an LLC2 connection (see "CUMOde" earlier in this chapter) for the specified CU, this value is used as the destination MAC address in the LLC2 frames.
Values
The display of MAC addresses for the CURemoteMac parameter now includes both canonical and noncanonical format.
Syntax
SETDefault !<CU Name> -SDLC CURemoteSap = <sap address> (Hex 04-EC)
SHow [!<CU Name> | !*] -SDLC CURemoteSap
0x04
The CURemoteSap parameter specifies the SAP for the destination CU. When the system initiates an LLC2 connection (see "CUMOde" earlier in this chapter) for the specified CU, this value is used as the destination SAP in the LLC2 frames. The valid values for the SAP address used by this parameter are from 0x04 to 0xEC and must be divisible by 4.
Syntax
SHow [!<CU Name> | !*] -SDLC CUStatus
No default
The CUStatus parameter shows the current status of a CU. The listed status information for the CU is Disabled, Disconnected, Connecting, Internal XID Exchange, XID Exchange, Set Mode State, Information Transfer State, Disconnecting.
The values displayed by CUStatus represent changes in the internal connection state and SDLC and DLSw connection. Actual sequences of states depend on specific configuration options, many are transitory and are rarely displayed.
The following describes the status information:
Syntax
SETDefault !<CU Name> -SDLC CUType = T2.0 | T1 | T2.1 | T4
SHow [!<CU Name> | !*] -SDLC CUType
T2.0
The CUType parameter defines the physical unit (PU) type category. If the bridge/router is acting as the SDLC primary for the CU specified, the type must be set to the actual CU type. If the system is acting as the SDLC secondary, the type must match the type expected by the SDLC primary, for example, the NCP for the specified CU.
Syntax
SETDefault !<CU Name> -SDLC CUXId = <value> (8 Hexadecimal digits)
SHow [!<CU Name> | !*] -SDLC CUXId
01700001
The CUXId parameter sets the CU exchange identification (XID) used by bridge/router to establish LLC2 and DLSw sessions. The XID configured with this parameter must match the XID definition on the host for the specified CU. This parameter is required only when the bridge/router is an SDLC primary unit for the specified CU and the CU does not respond to session identification requests (XIDs type 2.01 and type 1nodes).
When CUXIdDefined is set to Yes, the system uses the configured value in the LLC2 XID frame which is sent when the port connection is being established. If the CUXidDefined is set to No, the system attempts to obtain the XID from the CU itself.
Syntax
SETDefault !<CU Name> -SDLC CUXidDefined = No | Yes
SHow [!<CU Name> | !*] -SDLC CUXidDefined
No
The CUXidDefined parameter specifies whether the value of CUXId is used. If set to Yes, the CUXId value is used by the bridge/router when initiating LLC2 connections for T1 and T2.0 devices.
If set to No, the bridge/router attempts to solicit the XID value from the CU. For T2.1 devices, the CUXId value is never used.
Syntax
SETDefault -SDLC HostMac = <address>
SHow [!<CU Name> | !*] -SDLC HostMac
000000000000
The HostMac parameter is used to configure the remote CU. The MAC address is interpreted in noncanonical (token ring) format if the CURemoteMac parameter is not defined.
Syntax
SETDefault -SDLC MaxTRaceData = <max_bytes_traced> (0-76)
SHow -SDLC MaxTRaceData
16
The MaxTRaceData parameter sets the maximum number of bytes of SDLC data captured using the Trace facility. The value sets the number of bytes captured over and above the SDLC address and control bytes. The number of bytes affects the types of data captured; the higher the value entered, the more detailed the trace data that is captured. The number entered is rounded up to the nearest four; for example, if you enter the value as 29, the number is rounded up to 32.
Syntax
SETDefault !<port> -SDLC PCallTimer = <seconds> (0-300)
SHow [!<port> | !*] -SDLC PCallTimer
1
The PCallTimer parameter sets the number of seconds to wait between attempts to contact a failed or newly activated secondary CU on the bridge/router. This parameter is used on primary ports only.
The default value for PCallTimer is used for the first 10 poll attempts. After 10 poll attempts, twice the default value is used. Each contact attempt (SNRM or XID) uses the configured PT1Timer to timeout the poll, then waits the number of seconds set with PT1Timer, or twice the number of seconds set with PCallTimer, before the next contact attempt. On a multidrop link, you may want to set the PCallTimer to a larger value.
Syntax
SHow [!<port> | !*] -SDLC PCONFig
No default
The PCONFig parameter displays the values of all port-related parameters for the ports specified and all CUs assigned to the ports.
Syntax
SETDefault !<port> -SDLC PCONtrol = Enabled | Disabled
SHow [!<port> | !*] -SDLC PCONtrol
Disabled
The PCONtrol parameter determines the state of the SDLC port. When PCONTrol is enabled, the bridge/router continually tries to activate the port at initial startup (after a system reboot). If this parameter is disabled, the port is disabled at startup. After startup, you may use this parameter to change the state of the SDLC port.
The PCONtrol, CUCONTrol (see "CUCONTrol" earlier in this chapter), PORT and PATH CONTrol, and PORT OWNer parameters are interdependent. For example, when ports are enabled through PCONtrol, the CUs configured for that port only become active with frames being sent and received if their CUCONTrol parameters are enabled. Also, the corresponding CONTrol parameters in the PATH and PORT Services must be enabled (see the PATH Service Parameters chapter and the PORT Service Parameters chapter) and the PORT OWNer must be set to SDLC (see the PORT Service Parameters chapter).
Syntax
SETDefault !<port> -SDLC PDatMode = Full | Half
SHow [!<port> | !*] -SDLC PDatMode
Half
The PDatMode parameter sets the communication mode of the port to two-way alternate (half duplex) or two-way simultaneous (full duplex). This parameter applies to the port. The physical duplex (Request-To-Send/Clear-To-Send) signalling is controlled by DUplex in the PATH Service (see the PATH Service Parameters chapter) using the DUplex parameter.
The PDatMode parameter must be set to FULL for a primary multidrop port, allowing the bridge/router to send frames to one PU while receiving from another.
Syntax
SETDefault !<port> -SDLC PldleDiscTimer = <seconds> (0-1000)
0
The PldleDiscTimer parameter specifies the number of seconds that a port remains active without receiving frames. If the specified amount of time passes and no frames are received on the port, all control units (CUs) are disconnected. Reconnection is attempted by the SDLC port after approximately 30 seconds. A value of 0 disables this parameter so that the port will never time out. The PldleDiscTimer parameter provides a method for SDLC secondary ports to detect the loss of the primary port.
Syntax
SETDefault !<port> -SDLC PMaxData = <value> (265 | 521 | 1033 | 2057)
SHow [!<port> | !*] -SDLC PMaxData
1033
The PMaxData parameter specifies the maximum amount of data in bytes (including the transmission and request/response header) allowed for the CU in one data transfer. The setting of this parameter should be the same as the host configuration for the CU on the port.
Syntax
SETDefault !<port> -SDLC PMinFrameDelay = <milliseconds> (0-1000)
0
The PMinFrameDelay parameter specifies the minimum delay that must be inserted between frame transmissions on the specified port. A value of 0 disables the inter-frame delay. This parameter is only useful on ports on which the PROle parameter is set to primary.
Syntax
SETDefault !<port> -SDLC PMODulo = 8 | 128
SHow [!<port> | !*] -SDLC PMODulo
Default
8
The PMODulo parameter sets the frame numbering used for all CUs configured for this port. For example, if 8 is selected, modulo-8 sequencing is used. That is, frames are numbered 0 through 7. If 128 is selected, modulo-128 sequencing is used. That is, frames are numbered 0 through 127. The setting of this parameter must be the same as the other SDLC devices configured for the port. If module 128 is set, the bridge/router can accept no more than 15 frames in a single poll cycle.
Syntax
ADD !<port> -SDLC PortCU <CU Name> [<CU Name>...]
DELete !<port> -SDLC PortCU <CU Name> | ALL
No default
The PortCU parameter defines a CU, gives it a name, and assigns the CU to a port. Use ADD to set up a new CU on a port. You can specify more than one CU name to configure more than one CU at a time with ADD. Use DELete to remove a single CU from a port, or all of the CUs that are configured for that port.
Values
Syntax
SETDefault !<port> -SDLC PRetryTimer = <seconds> (0-300)
SHow [!<port> | !*] -SDLC PRetryTimer
30
The PRetryTimer parameter sets the time between attempts by the bridge/router to contact the network datalink (LLC2) partner defined by CURemoteMac and CURemoteSap for a CU whose CUMOde parameter is set to Originate. For example, if the PRetryTimer is set to 3 seconds, when contact is established, the bridge/router tries to establish contact with the LLC2 partner every 3 seconds until contact is established or contact with the SDLC partner is lost. If the contact is successfully established with the CU, the datalink connections are started. This parameter has no effect when applied to ports whose CUMOde parameter is set to Answer.
Do not set PRetryTimer to less than 20 seconds, or timing conflicts with DLSw may prevent sessions on that port from coming up.
Syntax
SETDefault !<port> -SDLC PROle = Primary | Secondary
SHow [!<port> | !*] -SDLC PROle
Primary
The PROle parameter specifies the role for the SDLC port. The role applies to the port and all the CUs configured for the port. If the port is primary, then all the CUs attached to this port must be secondary.
Syntax
SETDefault !<port> -SDLC PT1Retry = <number> (1-25)
SHow [!<port> | !*] -SDLC PT1Retry
3
The PT1Retry parameter sets the number of times the bridge/router attempts to complete a protocol exchange (that is, poll) with a connected device before considering that device a failed device. This parameter tunes the system performance by not prematurely failing devices because of a temporary loss of response. This parameter is used on primary ports only.
Syntax
SETDefault !<port> -SDLC PT1Timer = <milliseconds> (0-10000)
SHow [!<port> | !*] -SDLC PT1Timer
1000
The PT1Timer parameter sets the no-response timeout wait for an SDLC port on the bridge/router. If the CU does not send a response to a poll or message from the SDLC port before the T1 timer stops, the transmission is retried until the retry count setting completes. This parameter is used on primary ports only.
Syntax
SHow -SDLC SdlcLOG
No default
The SdlcLOG parameter displays a log of SDLC activity messages captured on the bridge/router and stored in a buffer. The display shows the most recent activity messages. Table 112 lists the event types captured in the log, and the corresponding message displayed.
Syntax
SET -SDLC SuppressDM = Yes | No
SHow -SDLC SuppressDM
No
The SuppressDM parameter disables DM responses from an enabled secondary/answer CU if the following occurs:
If you specify Yes, then the DM responses are suppressed. If you specify No, then the NETBuilder bridge/router sends a DM response to an XID or SNRM for an enabled secondary/answer CU that is not ready (has no established DLSw circuit).
SHow -SDLC TRaceData
No default
The TRaceData parameter displays all SDLC entries in the trace buffer.
SETDefault -SDLC TrapCONTrol = ([PortUp | NoPortUp], [PortDown | NoPortDown], [CUUp | NoCUUp], [CUDown | NoCUDown]) | ALL | None
SHow -SDLC TrapCONTrol
NoPortUp, PortDown, NoCUUp, CUDown
The TrapCONTrol parameter defines control of the transmission of SNMP traps for the SDLC Service. If the control is enabled, the specific trap is sent to the SNMP Service for transmission; if the control is disabled, the particular trap is blocked from being sent to SNMP.
Whether the trap is sent or not is dependent on how the -SNMP COMmunity, -SNMP CONTrol, and -SNMP MANager parameters are configured. For more information about parameters in the SNMP Service, see the SNMP Service Parameters chapter.
Values
Syntax
SET -SDLC XidKeepAlive = Enabled | Disabled
SHow -SDLC XidKeepAlive
Disabled
The XidKeepAlive parameter controls whether XIDs are sent over a DLSw circuit while waiting for the host poll. If you specify Enabled, then the CU configuration in the NETBuilder bridge/router sends NUL XID messages across the DLSw circuit, keeping the circuit alive longer, in order to receive the host poll. This is helpful in situations where the host poll rate of a secondary/answer CU is slow and does not coincide with the "ready" time of the CU (when a DLSw circuit is in place). If you specify Disabled, these XIDs are not sent.
These XIDs are sent only for the amount of time configured using the -SDLC PRetryTimer parameter. After that, the DLSw circuit is allowed to time out as usual.
This parameter was developed and tested in a PU 1 environment with a slow-polling host. The XidKeepAlive parameter is not recommended for general use, and may be removed in future software releases.