I got a call last night from China asking me to
change the IP on the fly to a few printers, then
they started working O.K.
So now I either suspect a faulty DHCP range limit
set at the remote Chinese location, or a rogue
engineer in China with a PC who keeps changing
his IP just for laughs.
BT
Tracy Johnson
MSI Schaevitz Sensors
> -----Original Message-----
> From: James P Hofmeister
> [mailto:[log in to unmask]]
> Sent: Friday, August 22, 2003 1:15 AM
> To: [log in to unmask]
> Subject: [HP3000-L] PrinterSpoolingHoldUpReasons
>
>
> Hello all @ 3000-l,
>
> RE: Printer Spooling Hold Up Reasons
>
> --------------------------------------------------
> We have a long distance circuit from our HP3000 in
> the U.S. to China over a frame-relay circuit.
> We're on 7.0 pp2. Oftentimes individual printers
> drop the spooler, startspool fixes it.
> --------------------------------------------------
>
> Assuming you are using hp's network printing and have a printer at the
> other end that supports PCL and has either an internal or external
> JETDIRECT card...
>
> I would tend to start network trouble shooting at 2 locations... First
> is at the frame-relay console. I would want to look at the link
> statistics for the WAN link (similar to what you can do on the 3000
> with :linkcontrol @;status=all). You would want to identify carrier
> losses, crc errors, etc. and resolve any significant issues with the
> frame-relay link service provider.
>
> Second is I would investigate the network status on the 3000 system:
>
> A) Any indication of resource issues:
>
> :nettool.net.sys;info="res;di;quit"
> FRI, AUG 22, 2003, 1:10:13 AM
> Item Subsystem Name G/N Description Used High Max
> ____________________________________________________________________
>
> 1 NS XPORT CP_POOL_ (G) Control Buf Pool 0 1 300 :)
> 2 NS XPORT 1536___S (G) Inbound Buf Pool 86 254 1365 :)
> 3 NS XPORT LAN1____ (N) Outbnd Buf Pool 0 14 512 :)
> 4 NS XPORT LOOP____ (N) Outbnd Buf Pool 0 26 128 :)
> 5 NS XPORT BT100___ (N) Outbnd Buf Pool 0 2 128 :)
> 6 NS XPORT UDP (G) GProt Msg Pool 0 N/A 512 :)
> 7 NS XPORT PXP (G) GProt Msg Pool 0 N/A 660 :)
> 8 NS XPORT PROBE (G) CM Prot Msg Pool 0 N/A 677 :)
> 9 NS XPORT PROBE (G) CM Prot Msg Pool 0 N/A 677 :)
> 10 NS XPORT IP_NI (G) IP-NI Msg Pool 0 N/A 2048 :)
> 11 NS XPORT IP_NI (G) IP-NI Msg Pool 0 N/A 2048 :)
> 12 NS XPORT IP_NI (G) IP-NI Msg Pool 0 N/A 2048 :)
> 13 NS XPORT (G) Node Name Cache 0 17 360 :)
> 14 NS XPORT (G) TCP Control pool 0 27 2048 :)
>
> B) Determine if you see any significant issues with the 3000 network
> Link:
>
> :linkcontrol @;status=all
> Linkname: SYSLINK Linktype: PCI 100BT Linkstate: CONNECTED
> Physical Path: 0/0/0/0
> Current Station Address: 00-30-6E-0C-4B-C6
> Default Station Address: 00-30-6E-0C-4B-C6
> Current Multicast Addresses:
> 09-00-09-00-00-01
>
> Transmit bytes 10816967 Receive bytes
> 3178758169
> Transmits 85781 Receives unicast
> 29448
> Transmits no error 85693 Receives broadcast
> 31753243
> Transmits dropped 0 Receives multicast
> 28255
> Transmits deferred 2224 Receives no error
> 30076179
> Transmits 1 retry 515 Recv CRC error
> 0
> Transmits >1 retry 451 Recv Maxsize error
> 0
> Trans 16 collisions 50 Recv dropped: addr
> 1734620
> Trans late collision 0 Recv dropped: buffer
> 0
> Trans underruns 0 Recv dropped: descr
> 0
> Carrier losses 0 Recv dropped: other
> 147
> Trans jabber timeout 0 Recv watchdg timeout
> 0
> Link disconnects 0 Recv collisions
> 0
> Link speed 10 Recv overruns
> 0
> Link duplex Half Link auto sensed
> No
> Link mode 10Base-T Core Secs since clear
> 219642
>
> Linkname: BT100LNK Linktype: PCI 100BT Linkstate: CONNECTED
> Physical Path: 0/2/0/0
> Current Station Address: 00-30-6E-06-03-9D
> Default Station Address: 00-30-6E-06-03-9D
> Current Multicast Addresses:
> 09-00-09-00-00-01
>
> Transmit bytes 1163 Receive bytes
> 724641
> Transmits 21 Receives unicast
> 9
> Transmits no error 21 Receives broadcast
> 5800
> Transmits dropped 0 Receives multicast
> 7
> Transmits deferred 0 Receives no error
> 5816
> Transmits 1 retry 0 Recv CRC error
> 0
> Transmits >1 retry 0 Recv Maxsize error
> 0
> Trans 16 collisions 0 Recv dropped: addr
> 0
> Trans late collision 0 Recv dropped: buffer
> 0
> Trans underruns 0 Recv dropped: descr
> 0
> Carrier losses 0 Recv dropped: other
> 0
> Trans jabber timeout 0 Recv watchdg timeout
> 0
> Link disconnects 0 Recv collisions
> 0
> Link speed 100 Recv overruns
> 0
> Link duplex Full Link auto sensed
> Yes
> Link mode 100Base-TX Addon Secs since clear
> 219639
>
> C) Determine frequency of TCP "re-transmitted segments":
>
> : nettool.net.sys;info="status;tcpstat;tcpglobal @;quit"
>
> Local IP Address : @
> ==============================================================
> ===============
> TCP GLOBAL Statistics
> Current Time: FRI, AUG 22, 2003, 1:12:05 AM
> ==============================================================
> ===============
> TCP GLOBAL Statistics
> Maximum number of connections allowed : 4096
> Maximum number of sockets allowed : 4096
> Number of connections currently open : 1
> Maximum re-transmissions per packet : 8
> Cumulative Statistics
> ---------------------
> . Total active opens : 69
> . Total passive opens : 475
> . Total inbound segments : 17044
> . Total outbound sengments : 23927
> . Total re-transmitted segments : 727 <<< here >>>
> . Total number of RESETS sent : 2945
> . Total connection failures : 27
>
> D) Further investigation by enabling and reading the NMLG files:
>
> Logging:
> Class Console Disk
> Subsystem Name Logging Logging Event
> SUB0003 CLAS0001 [Y] [Y] Serious internal error
> Network CLAS0002 [Y] [Y] Internal error/operator attention
> Transport CLAS0003 [N] [Y] Non-critical errors
> CLAS0004 [Y] [Y] Nodal messages (start/stop)
> CLAS0005 [N] [Y] Informative messages
> CLAS0006 [N] [Y] Statistical information
>
> :switchnmlog update
>
> :nmdump.pub.sys
> WOULD YOU LIKE TO FORMAT A LOG OR TRACE FILE? 1 = LOG, 2 =
> TRACE > 1
> WHICH SUBSYSTEMS' RECORDS WOULD YOU LIKE TO FORMAT? (ALL) > 3
> WOULD YOU LIKE TO CHANGE ANY SUBSYSTEM OPTIONS? (NO) > {cr}
> WHAT IS THE INPUT FILE NAME? (*NMDUMPEQ) > NMLG0686.pub.sys
> WHAT IS THE OUTPUT FILE NAME? ($STDLIST) > {cr}
> WOULD YOU LIKE TO SPECIFY A TIME RANGE? (NO) > {cr}
>
> Here is a TCP outbound retransmission indicating that the remote host
> did not reply with an Acknowledge before our timers popped and we
> retransmitted the data. If you find many TCP Retransmission it is an
> indication that the link quality or performance is poor.
>
> **********************************************************************
> * WED, MAY 10, 2000, 2:11:22.3 PM NETXPORT(3) *
> *--------------------------------------------------------------------*
> * Event : OUTBOUND *
> * Entity : TCP *
> * Internal Event : Retransmission *
> * Log Class : Informative *
> * Port ID/PIN/KSO : $00000840 *
> * Location : 16301 Parameter : $8687B000 *
> * Info Section (hex): *
> * 0000: 0067 0002 003C 3FAD 0000 0840 0005 8687 *
> * 0008: B000 0001 *
> *--------------------------------------------------------------------*
>
>
> Here is a TCP Retransmission Threshold Exceeded indicating that the
> remote host did not reply with an Acknowledge before our
> timers popped
> multiple times as per the TCP timer configuration.
>
> **********************************************************************
> * WED, MAY 10, 2000, 2:12:22.3 PM NETXPORT(3) *
> *--------------------------------------------------------------------*
> * Event : INTERNAL ERROR *
> * Entity : TCP *
> * Internal Event : Retransmission Threshold Exceeded *
> * Log Class : Non-critical error *
> * Port ID/PIN/KSO : $00000840 *
> * Location : 14101 Parameter : $00001D8C *
> * Info Section (hex): *
> * 0000: 0067 0003 01E1 3715 0000 0840 0003 0000 *
> * 0008: 1D8C 0001 *
> *--------------------------------------------------------------------*
>
>
> TCP Statistics can tell you a great deal about the connection history
> of a TCP connection:
> **********************************************************************
> * THU, AUG 21, 2003, 10:10:01.4 PM NETXPORT(3) *
> *--------------------------------------------------------------------*
> * Event : INFORMATIVE *
> * Entity : TCP *
> * Internal Event : Statistics *
> * Log Class : Statistics *
> * Port ID/PIN/KSO : $0000A260 *
> * Location : 19901 Parameter : $00000000 *
> * Info Section (hex): *
> * 0000: 0067 001C 0051 4DBD 0000 A260 0006 0000 *
> * 0008: 0000 0001 *
> *--------------------------------------------------------------------*
> * Statistics: *
> * Local_sap : $0019 Remote_sap : $EDD5 *
> * Local_ip_addr : $1071095C Remote_ip_addr : $0F2D599B *
> * IN_Total : 13 OUT_Total : 14 *
> * IN_Bytes : 9 OUT_Bytes : 588 *
> * IN_PM_PKTS : 4 OUT_PM_PKTS : 9 *
> * IN_User_PKTS : 8 OUT_User_PKTS : 5 *
> * IN_CKsum_Error : 0 OUT_RTX : 0 *
> * IN_ICMP_Msgs : 0 IN_Other : 1 *
> * Connection_Info : 0 Control : 0 *
> * Send : 5 Receive_Reply : 8 *
> * Flush_sends : 0 *
> ...
> **********************************************************************
>
> I hope this helps,
>
> Regards,
>
> James Hofmeister
> Email: <first>.<last>@hp.com
> Hewlett Packard - Global Solutions Engineering (WTEC)
> P.S. My Ideals are my own, not necessarily my employers.
>
>
> ________________________________________________________________
> The best thing to hit the internet in years - Juno SpeedBand!
> Surf the web up to FIVE TIMES FASTER!
> Only $14.95/ month - visit www.juno.com to sign up today!
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
