Using the X.25 Network Interface

Table 49. Establishing Incoming X.25 Circuits for Closed User Groups

Incoming

 

 

 

Receiving DTE CUG De®nition

 

 

Call

 

 

 

 

 

 

 

 

 

Interface

Protocol

Address

 

Interface

Interface

Protocol

All CUGs

No CUGs

Request

 

CUG Only

CUG Only

Speci®c

 

and

and

and

 

 

Contains

 

 

 

 

 

CUG

 

Protocol

Address

Address

 

 

 

 

 

 

 

 

 

 

 

 

 

CUG

CUG

CUG

 

 

 

 

 

 

 

 

 

 

 

 

No CUG

Reject

Reject

Reject

 

Reject

Reject

Reject

Reject

Accept

 

 

 

 

 

 

 

 

 

 

Interface

Accept

Reject

Reject

 

Reject

Reject

Reject

Reject

Reject

CUG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Protocol

Reject

Accept

Reject

 

Accept

Reject

Reject

Reject

Reject

CUG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Address

Reject

Reject

Accept

 

Reject

Accept

Accept

Accept

Reject

Speci®c

 

 

 

 

 

 

 

 

 

CUG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

For outgoing calls on an interface, if you have enabled either the CUG or the BCUG facility, each call request will contain the con®gured preferred CUG (if any) for the destination or, if no address-speci®c CUG is con®gured, the CUG used is the CUG de®ned for the protocol, or if no protocol-speci®c CUG is con®gured, the CUG used is the CUG de®ned for the interface. If no CUG number has been con®gured, the CUG facility is not included in any outgoing call request.

Overriding Closed User Group Processing for CUG 0

You can con®gure the DTE such that it does not validate incoming calls with a CUG of 0 in the call request. This ability allows you to permit speci®c calls to complete even when you have not enabled incoming access. Using the national enable cug 0 override command forces the device to ignore the CUG facility if the CUG number is 0. The call request will not be compared with any con®gured CUG number.

Con®guring X.25 Closed User Groups

To use closed user groups on X.25 interfaces:

1.Request CUG numbers from your network provider. You will need these numbers when con®guring X.25.

2.Enable the closed user group facility using the national enable cug command and related commands.

3.Enable the bilateral closed user group facility, if desired, using the national enable bi-cugcommand and related commands.

4.Con®gure the appropriate CUG numbers for the DTEs. Specify the preferred CUG, CUG, preferred bilateral CUG, and bilateral CUG, as needed. This is done through the add address command.

5.Con®gure the appropriate CUG and bilateral CUG for the protocol, if required. This is done through the add protocol command.

Note: You should only con®gure these CUGs if you are restricting all X.25 circuits established over the X.25 interface for this protocol to DTEs belonging to this set of unique CUGs or BCUGs unless you override it with an address-speci®c CUG.

6.Con®gure the appropriate CUG and bilateral CUG for the interface, if required. This is done through the add cug command.

Chapter 26. Using the X.25 Network Interface 325

Page 361
Image 361
IBM SC30-3681-08 manual Conguring X.25 Closed User Groups, Overriding Closed User Group Processing for CUG