HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Need explanation of N_DCNX_KO netsub.c (nettl)
Operating System - HP-UX
1834196
Members
2566
Online
110065
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2004 12:18 AM
09-27-2004 12:18 AM
Need explanation of N_DCNX_KO netsub.c (nettl)
Hi,
I have a problem with X.25 subadressing,
and therefor i logged some records using nettl.
Can anyone explain the Flags and Reasonscodes,
or point me to some manual...
Sending:
***********************************HP OSI MGMT******************************@#%
Timestamp : Mon Sep 27 METDST 2004 13:48:26.857217
Process ID : [ICS] Subsystem : NETWORK
User ID ( UID ) : -1 Log Class : INFORMATIVE
Device ID : -1 Path ID : -1
Connection ID : -1 Log Instance : 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[3002] N_ESTAB netmai2.c 1071
[....] ENT=30 CTX=1 Pr-state=2 Sndcp=1 N-sap=55 SN-sap=20
[....] Called Snpa=e02062380123110f Calling Snpa=71702235
[....] Called Nsap=2062380123 Calling Nsap=01702235
[....] Flags=01 Org/Reas=0000 CHN=1 1 Qos=00 Prio=0 SN-pdu size= 128 128
Resulting in:
***********************************HP OSI MGMT******************************@#%
Timestamp : Mon Sep 27 METDST 2004 13:48:27.452836
Process ID : [ICS] Subsystem : NETWORK
User ID ( UID ) : -1 Log Class : ERROR
Device ID : -1 Path ID : -1
Connection ID : -1 Log Instance : 2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[3005] N_DCNX_KO netsub.c 803
[....] ENT=30 CTX=1 Pr-state=6 Sndcp=1 N-sap=55 SN-sap=20
[....] Called Snpa=e02062380123110f Calling Snpa=71702235
[....] Called Nsap=2062380123 Calling Nsap=01702235
[....] Flags=41 Org/Reas=0120 CHN=1 0 Qos=00 Prio=0 SN-pdu size= 128 128
[....] SHcntrs=0 LGcntrs=3 235 1 31
I see a change in Flags: 00->41
and a Org/Reas=0000 -> 0120 (!!)
What is this?
Regards,
Ceesjan van Hattum
I have a problem with X.25 subadressing,
and therefor i logged some records using nettl.
Can anyone explain the Flags and Reasonscodes,
or point me to some manual...
Sending:
***********************************HP OSI MGMT******************************@#%
Timestamp : Mon Sep 27 METDST 2004 13:48:26.857217
Process ID : [ICS] Subsystem : NETWORK
User ID ( UID ) : -1 Log Class : INFORMATIVE
Device ID : -1 Path ID : -1
Connection ID : -1 Log Instance : 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[3002] N_ESTAB netmai2.c 1071
[....] ENT=30 CTX=1 Pr-state=2 Sndcp=1 N-sap=55 SN-sap=20
[....] Called Snpa=e02062380123110f Calling Snpa=71702235
[....] Called Nsap=2062380123 Calling Nsap=01702235
[....] Flags=01 Org/Reas=0000 CHN=1 1 Qos=00 Prio=0 SN-pdu size= 128 128
Resulting in:
***********************************HP OSI MGMT******************************@#%
Timestamp : Mon Sep 27 METDST 2004 13:48:27.452836
Process ID : [ICS] Subsystem : NETWORK
User ID ( UID ) : -1 Log Class : ERROR
Device ID : -1 Path ID : -1
Connection ID : -1 Log Instance : 2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[3005] N_DCNX_KO netsub.c 803
[....] ENT=30 CTX=1 Pr-state=6 Sndcp=1 N-sap=55 SN-sap=20
[....] Called Snpa=e02062380123110f Calling Snpa=71702235
[....] Called Nsap=2062380123 Calling Nsap=01702235
[....] Flags=41 Org/Reas=0120 CHN=1 0 Qos=00 Prio=0 SN-pdu size= 128 128
[....] SHcntrs=0 LGcntrs=3 235 1 31
I see a change in Flags: 00->41
and a Org/Reas=0000 -> 0120 (!!)
What is this?
Regards,
Ceesjan van Hattum
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2004 03:16 AM
09-27-2004 03:16 AM
Re: Need explanation of N_DCNX_KO netsub.c (nettl)
Hi to myself,
I'm sorry not to be able to explain the question, but the solution is to check the
selectors:
Above you see the low levvel Nsap.
The Snpa is the same, preceeding with hex e is decimal 14, so nsap=14 digits, appended with f (just to complete it), Snpa starts with 7, meaning, 7 digits to use.
But it can't go further to higher levels,
if the Destinationsystem does explicitly use SSAP and PSAP.
I'm used to use only TSAPs, but not the other fields.
By configuring the SSAP and PSAP of the adjecent MTA, the connection was set immediatly, without any problem.
Regards,
Ceesjan
I'm sorry not to be able to explain the question, but the solution is to check the
selectors:
Above you see the low levvel Nsap.
The Snpa is the same, preceeding with hex e is decimal 14, so nsap=14 digits, appended with f (just to complete it), Snpa starts with 7, meaning, 7 digits to use.
But it can't go further to higher levels,
if the Destinationsystem does explicitly use SSAP and PSAP.
I'm used to use only TSAPs, but not the other fields.
By configuring the SSAP and PSAP of the adjecent MTA, the connection was set immediatly, without any problem.
Regards,
Ceesjan
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP