Configuration Process of Application Example of OSI over DCC Solution

This section introduces the process of configuring the OSI over DCC solution.

NOTE:

This example provides only the configurations of the typical NEs: NE101, NE201, NE301, and NE302.

Set the IDs of the NEs. See Changing an NE ID.
- The extended ID of NE101 is 9 and the ID is 101.
- The extended ID of NE201 is 9 and the ID is 201.
- The extended ID of NE301 is 9 and the ID is 301.
- The extended ID of NE302 is 9 and the ID is 302.
Set the NSAP address information for the NEs. See Setting the NSAP Address for an NE.
- The area ID in the NSAP address of NE101 is 0x394F1190.
- The area ID in the NSAP address of NE201 is 0x394F1210.
- The area ID in the NSAP address of NE301 is 0x394F1200.
- The area ID in the NSAP address of NE302 is 0x394F1220.
Set the DCCs for the NEs. See Configuring Transparent Transmission of DCC Channels.
- Set Protocol for all the line ports of all the NEs to IP.
- Set Channel Type for all the ports of all the NEs to D1-D3 (default value).
- For each DCC channel, the LAPD role at the end closer to the Web LCT is set as Network, and that at the other end is set as User.
Configure the CLNS roles for the NEs. See Configuring the Node Type for an NE.
- The CLNS role of NE201 and NE302 is L1 (default value).
- The CLNS role of NE101 and NE301 is L2.
Query the OSI routes. See Querying the Route Information of a Node.
- In the L1 routing table, NE101, NE201, NE301, and NE302 have the routes to all the NEs that are in their respective areas.
- In the L2 routing table, NE101 and NE301 have the routes to other L2 NEs.

All NEs can be successfully created. The communication between the Web LCT and NEs is normal.