1 / 8

Troubleshooting X.25 Calls

Troubleshooting X.25 Calls. Gcom_ssd. User. Kernel. NPI Provider. NPI Call Routing. pktlvl.1. pktlvl.2. DLPI User. Troubleshooting X.25 Calls. X.25 Stack Processing Connect Request. NPI Connect Request From SS_OP_CONN_REQ. Consult routing tables Address pattern User data pattern

joshua
Download Presentation

Troubleshooting X.25 Calls

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Troubleshooting X.25 Calls

  2. Gcom_ssd User Kernel NPI Provider NPI Call Routing pktlvl.1 pktlvl.2 DLPI User Troubleshooting X.25 Calls X.25 Stack Processing Connect Request NPI Connect Request From SS_OP_CONN_REQ • Consult routing tables • Address pattern • User data pattern • Least cost calculation • Load balancing Choose an X.25 packet level Process X.25 Call Request Send downstream to LAPB

  3. Gcom_ssd User Kernel NPI Provider NPI Call Routing pktlvl.1 pktlvl.2 DLPI User Troubleshooting X.25 Calls X.25 Stack Debugging Routing Gcom_stats -n -D0x42004 0x40000 = Debug routing 0x02000 = Decode Call Req 0x00004 = Decode Clr Req

  4. Gcom_ssd User Kernel NPI Provider NPI Call Routing pktlvl.1 pktlvl.2 DLPI User Troubleshooting X.25 Calls X.25 Stack Debugging Routing cmessages File Compare addresses Compare user data Route outgoing Connect Req Attempting route to '321' Minor LPA=0 PU-ID=0 Considering route to pktlvl.1: LPA=1 PUID=1 Up/Dwn=1 Comparing '321' to '*' Match ...Comparing '00 00 00 00' to '00 00 00 00' Match, add to list Comparing '321' to '100' Not match: pattern match failed Considering route to pktlvl.2: LPA=2 PUID=2 Up/Dwn=1 Comparing '321' to '*2' Not match: pattern match failed Comparing '321' to '200' Not match: pattern match failed Route List: Route to pktlvl.1: LPA=1 PUID=1 Up/Dwn=1 '*' Call Request: UPA 1: pktlvl.1: Called='321' Calling='' Choose X.25 Pkt Lvl Send down stream

  5. Gcom_ssd User Kernel NPI Provider NPI Call Routing pktlvl.1 pktlvl.2 DLPI User Troubleshooting X.25 Calls X.25 Stack Debugging Routing cmessages File Called DTE address Route incoming X.25 Call Req Call Request: UPA 2: pktlvl.2: Called='321' Calling='' Facilities: 42 08 08 packet size negotiation 43 02 02 window size negotiation NPI-find-listener: lpa=2 pu_id=2 nsap="321" rnsap="" ? minor 1: lstn_lpa=0 lstn_pu_id=0 nsap="*" rnsap="*" return minor 1 Call Accept: UPA 2: pktlvl.2 LC 1: Called='' Calling='' Facilities: 42 08 08 packet size negotiation 43 02 02 window size negotiation Success X.25 LCN Find a listening stream Call Accept triggered by user interaction

  6. Gcom_ssd User Kernel NPI Provider NPI Call Routing pktlvl.1 pktlvl.2 DLPI User Troubleshooting X.25 Calls X.25 Stack Debugging Facilities cmessages File An X.25 call fails with diagnostic information similar to the following. Received DISC_REQ: 0x83410307 Disc: Connection rejection-reason unspecified Cause: Invalid facility request Diagnostic: Facility/registration code not allowed Check the cmessages file for messages similar to the following. X.25 facility not allowed: 420808 X.2-selected[6]&0x10 = 0x0 This tells you that a facility was rejected because the selected structure index [6] needed to have the 0x10 bit set, but it was zero. You can adjust your configuration accordingly. X.25 always prints a message like this when rejecting a Call Request packet because of improper facilities. Back to back test. Call goes out on port 1 and comes in on port 2.

  7. Gcom_ssd User Kernel NPI Provider NPI Call Routing pktlvl.1 pktlvl.2 DLPI User Troubleshooting X.25 Calls X.25 Stack Debugging Facilities cmessages File • You can cause X.25 to print more information about facility field checking by using the following command to turn on a debug bit. • Gcom_stats -X0x1000 • You will then see messages like the following. • send: pktlvl.1: packet type call_req • send: X.25 window size isz=2 osz=2 • send: X.25 packet size isz=8 osz=8 • recv: pktlvl.2: packet type call_req • recv: X.25 validate_facil[6]&0x10: 420808 • X.25 facility not allowed: 420808 X.2-selected[6]&0x10 = 0x0 • recv: pktlvl.1: packet type clr_req • send: pktlvl.1: packet type clr_conf • recv: pktlvl.2: packet type clr_conf Facils OK on port 1 Facils invalid on port 2 Back to back test. Call goes out on port 1 and comes in on port 2.

  8. End of Presentation Troubleshooting X.25 Calls

More Related