|
IBM Communication Server Setup in Windows NT IBM Communication Server Setup in Windows NT
At this point, we assume that the IBM Communication Server software has been
installed. The SYNC/570i or SYNC 2000 device driver should also be installed and
at least one line of the adapter be setup up for SNA support.
- From the IBM Communication Server program group, launch SNA Node
Configuration.
- A Welcome to Communications Server Configuration! dialog box will
be displayed, with an option to create a New configuration of use an
existing one. We need to create a new one, so select New.
- Select Next.
- The next dialog that comes up asks you to Choose a Configuration Scenario.
Select APPN Network Node.
- Select Finish.
- You should be back to the main Communications Server SNA Node
Configuration dialog. Double-click on 1. Network node setup
(located in the left hand window).
- We are now at the Define the Node dialog. In the Basic tab,
we need to assign this node a Fully qualified CP name, let's use DIGI .
NODE1.
- None of the other tabs need to be modified, so select OK.
- Double-click on 2. Device configuration (located in the left hand
window).
- From the Device Type dialog, open the drop down box and select Digi
SDLC.
- Select OK.
- You should now see the Adapter/Line Selection dialog. You
should see a list of available Digi SYNC adapters and Lines. Select
the adapter and line of the adapter that you wish to use. NOTE:
Any line that has previously been selected in a previous Node Configuration
will not be listed in this dialog.
- Select OK.
- You are now in the Digi SDLC dialog window, at the Basic tab.
Select Full-duplex communication and then move to the Digi tab.
- In the Digi tab, select the Line Speed at which you are going to be
running, the default is 56000.
- Also enable the Internal Clocks option, if you need the adapter to
generate its own clock.
- The remaining tabs can be left at default, so select OK.
- Back at the Node Configuration window, double-click on Peer
Connections. No changes are needed, but you must enter and exit
this dialog to finish the configuration process.
- When exiting the Peer Connections dialog, you will asked if you want to automatically
route all APPC sessions over this connection Answer No.
- You are finished with the creation of a New Node Configuration, you need
to select File and Save, from the menu bar. You can name
it whatever you would like.
- Once the node config. has been saved, you are asked if you wish to start
the node using this configuration. You can answer either way, but if
you answer No, now, you will have to start it later from SNA Node
Operations.
- You are done with the Node Configuration, so it can be closed.
Once the new node configuration has been created, you are ready to move on to
SNA Node Operations, where the Node can be started, stopped and monitored.
- From the IBM Communications Server program group select SNA Node
Operations.
- If you started the Node after you created it in SNA Node Configuration,
the right hand window displays some information concerning the node that has
been started.
- If no node has been started, select Operations and Start Node from
the menu bar. Select the desired Node Configuration (assuming that
more than one has been created).
- Once the node has been started, we can move on to the configuration of the
second IBM Comm. Server.
Configuration of the second IBM Comm. Server.
- The steps to follow on the second server are pretty much the same as the
first, keeping in mind the clocking source, the type of Sync adapter on each
end, etc.
- TO ensure that communication is truely being routed over our connection,
make the Fully Qualified CP name (FQCP differently on each of the servers
(i.e. DIGI.NODE1 and DIGI.NODE2)
- Once the second system has been configured and both nodes are up and
running, move on to testing your SDLC connection.
Testing your SDLC connection between two IBM Comm. Servers.
- From the IBM Communications Server program group, select Check
Connection (APING).
- At the Winaping setup dialog, we will need to enter in the Partner LU Name
or Symbolic Name, this is the FQCP of the remote server.
- You can modify the Packet Size, if desired.
- Increase the Itertations: count, from 2 to a larger number.
- Enable the Verify Last Echoed Packet of Each Iteration option.
- Select OK.
- Select Action and Start from the menu bar, or click the
green circle on the button bar, to start APING.
|