Title: | Terminal Servers |
Notice: | See Note 2 for Directory of important notes. Please use keywords. |
Moderator: | LAVC::CAHILL ON |
Created: | Tue May 14 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3547 |
Total number of notes: | 12300 |
Hello folks I am not sure which notes file to ask these questions but here goes anyway. I cannot find a Product Service Plan. Does anyone know who the product manager is? I have a customer with a problem on a RapidPrint 500. The customer has five of these things and is printing from VMS. All is ok for a day or so and then the box seems to go IP brain dead. It is still possible to connect to it via mop. Counters show sys buffer unavailable incrementing and in six hours managed to get to 250000. When the box is power cycled its OK again for a while, sounds like a memory leak problem?? They are printing to TCP port 3001 Unfortunately the server was rebooted before I did a cut and paste of the counters but the only thing that looked nasty was the 244500 system buffer unavailable. The rest of the information below was taken when the problem was apparent. regards Jim CSC Basingstoke Some info from the Rapid print:- Digital DSTRP Version V3.4/5(961028) Local> sh server DSTRP Version V3.4/5(961028) Uptime: 6 Days 18:47 Hardware Addr: 00-80-a3-0d-dc-d6 Name/Nodenum: RAP502/ 0 Ident String: Micro Print Server LAT Circuit Timer (msec): 80 Password Limit: 3 Inactive Timer (min): 30 Console Port: 1 Queue Limit: 32 Retrans Limit: 10 Keepalive Timer (sec): 20 Session Limit: N/A Multicast Timer (sec): 30 Node/Host Limits: 20/20 TCP/IP Address: 194.36.213.159 Subnet Mask: 255.255.255.0 TCP/IP Gateway: 194.36.213.2 Backup Gateway: 194.36.213.2 Domain Name: N/A Daytime Queries: Enabled Serial Delay (msec): 30 Network Buffering: 4096 Prompt: Local_%n%P> Groups: 0 Characteristics: Announce Incoming Logins: Telnet (No Passwords Required) Local> sho server status DSTRP Version V3.4/5(961028) Uptime: 6 Days 18:47 Hardware Addr: 00-80-a3-0d-dc-d6 Name/Nodenum: RAP502/ 0 Ident String: Micro Print Server Cur High Max Cur High Max Active Ports: 0 1 1 Active Users: 1 2 1 Active Circuits: 0 0 4 Queue Entries: 0 1 32 Available Services: 0 0 --- Local Services: 3 3 1 Time to Shutdown: N/A Port Framing Errors: 0 Load Address: aa-00-04-00-02-10 Parity Errors: 0 Dump Address: aa-00-04-00-02-10 Overrun Errors: 0 Memory Usage (%): 14 100 Allocated Pkts: 3705 Free Bytes: 247520 284692 Freed Pkts: 3521 Memory Fragments: 8 Largest Packet: 238744 NVRAM Memory: 448 890 Allocation Failures: 0 Local> Local> sh service local Service Identification RAP502_TEXT DSTRP Parallel Port Text Service RAP502_PCL DSTRP Parallel Port PCL/binary Service RAP502_PS DSTRP Parallel Port PostScript Service Local> show protocol DSTRP Version V3.4/5(961028) Uptime: 6 Days 18:53 Hardware Addr: 00-80-a3-0d-dc-d6 Name/Nodenum: RAP502/ 0 Ident String: Micro Print Server Received Sent Seconds since zeroed: 586439 LAT (disabled.) TCP Messages: 264 320 Connect Failure Reasons: 0000 Invalid Packets: 4 0 Invalid Packet Reasons: 0031 APPLE (disabled.) NETW (disabled.) NetBIOS (disabled.) Counters ***AFTER*** reboot Local> sho server count DSTRP Version V3.4/5(961028) Uptime: 3:09:57 Hardware Addr: 00-80-a3-0d-dc-d6 Name/Nodenum: RAP502/ 0 Ident String: Micro Print Server Received Sent Seconds since zeroed: 11397 Bytes: 2037230 1728844 Frames Deferred: 79 Frames: 28137 28283 Send Failure Reasons: 0004 Multicast Bytes: 2142699 23871 Recv Failure Reasons: 0000 Multicast Frames: 13623 53 Data Overrun: 0 Network Failures: 0 0 Unknown Protocols: 57141 Frames Sent 1 Coll: 34 NIC Buffer Unavailable: 0 Frames Sent 2+ Coll: 45 Sys Buffer Unavailable: 0 LAT (disabled.) TCP Messages: 596 719 Connect Failure Reasons: 0000 Invalid Packets: 7 0 Invalid Packet Reasons: 0033
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3526.1 | CSC32::D_PELTONEN | Fri May 09 1997 15:10 | 9 | ||
Well, we're getting RP500 calls these days, but haven't seen that one yet. They all do this? You did a great job documenting the problem, why not just roll that all up into an IPMT? That way your problem is documented and you don't have to wory about the exact product manager; it'll get routed accordingly. DAP (CSC/CS NSU) |