[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ozrock::x25_avms

Title:	DEC X.25 for OpenVMS AXP

Moderator:	OZROCK::MUGGERIDGE

Created:	Mon Jan 18 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	524
Total number of notes:	2218

511.0. "x25 access DTE Class Profile" by COMICS::HESS () Wed Apr 16 1997 23:50

Hello,
        I suspect there is a simple answer to this , but I don't know it.

How do you set the profile on an x25 access dte class, the create command seems
to work but the profile is not set when I do a show

eg.
NCL> create x25 acc dte cl bt type local, profile "PSS"

Node 0 X25 Access DTE Class bt
at 1997-04-16-14:26:08.656+01:00I0.212


NCL>show x25 acc dte class bt all

Node 0 X25 Access DTE Class bt
at 1997-04-16-14:26:13.936+01:00I0.212

Identifiers

    Name                              = bt

Status
Status

    Usable DTEs                       =
       {
       }

Characteristics

    Type                              = Local
    Local DTEs                        =
       {
       }
    Security Dte Class                = Default
    International Prefix              =
    Local Prefix                      =
    DNIC                              =
    Strip DNIC                        = False
    Profile                           = ""


        I have tried various commands and also the configurator, which does not
seem to have the profile as an option although the Help in ncl indicates it can
be set/created.

Pete.

T.R	Title	User	Personal Name	Date	Lines
511.1	What are you trying to accomplish?	OZROCK::HARTWIG	Arthur Hartwig, TaN Engineering-Australia	`Thu Apr 17 1997 01:05`	6
	Essentially the profile for an x25 access dte class "does nothing". What are you trying to accomplish by setting a profile on the DTE class? The profile on a x25 protocol dte sets a lot of parameters. Is that where you want to set a profile?
511.2		COMICS::HESS		`Thu Apr 17 1997 01:52`	8
	Arthur, Well a customer has migrated to Alpha and can not now make calls through his Gateway, comparing his configuration he noticed that the only diffbetween his VMS and Alpha config was that he had a profile set on fis x25 access dte class, he then tried to set it on the alpha and found he couldn't despite everything indicating he can. I dont suspect the cause of his problem is down to this parameter but if as you point out it "does nothing" ... why is it there
511.3	Just guessing ...	MARVIN::CARLINI		`Thu Apr 17 1997 17:30`	8
	> I dont suspect the cause of his problem is down to this parameter > but if as you point out it "does nothing" ... why is it there I thought that the profile on the DTE Class only applied to those of type remote and was only used to determine some attributes needed for the NSAP mapping functionality. Antonio
511.4		OZROCK::HARTWIG	Arthur Hartwig, TaN Engineering-Australia	`Fri Apr 18 1997 00:20`	14
	My recollection is that (comparatively) fairly late in the piece the profile argument was added for creation of DTE classes. The idea was that the profile would supply attributes needed for NSAP mapping. This was a good idea BUT as far as I know, no-one ever got around to adding the necessary details to the profiles. As far as I can see, no-one is ever likely to add these details to the profiles. Until such information is added to the profiles there is little point making other changes to support the use of NSAP mapping information in the profiles. Concerning things not working, my guess is that its most likely to be a security problem in the gateway. as always, events on the Alpha and the gateway will give vital clues to resolving the problem.
511.5		MARVIN::CARLINI		`Fri Apr 18 1997 06:03`	11
	I think that when this work was done for VAX PSI (in DECnet/OSI V5.7A) some changes were made to the profile file format - in fact it was the last thing Eric did if I recall correctly. Walter added this NSAP mapping to PSI and he explicitly changed the configurator to ask an extra question to get the profile; I'm sure he can supply the sordid details if needed. I agree that it is very unlikely to be the problem and OPCOM messages coupled with traces are the way to go. Antonio