Menu ▾ ▴

#11 ER: ndscheck need to be modified to monitor 9100 port

release_3.25
open
nobody
core (24)
2013-06-04
2008-02-28
Krishna
No

As of now ndscheck pings each and every printer registered on CEPS and checks if its reachable on the network. While this ensures whether printer is reachable or not, however, there is no guarantee that the device is actually a printer.

This happens if a printer is removed physically and the IP is re-used for some other device (like for eg: a linux system), but the same device is not deleted from CEPS DB. Now, since CEPS does not monitor whether 9100 port is present on the device, it simply attempts to open a connection to 9100 and tries to send the job infinitely, (which would fail). And CEPS continues to retry sending job to the wrong device.

If ndscheck is modified to monitor 9100 port, such rogue printers could be easily identified and deleted from CEPS DB directly avoiding all the mess.

This was a major problem at GENESIS site that could've created P1 (if it wasn't found early). There were actually 200 jobs (100 each on pscache server and active server) getting re-tried to print jobs for over 4 months.

Printers could never be made 'inactive' because the IP was in use by other device and always reachable!

Discussion

  • Saravana Kumar, C

    Saravana Kumar, C - 2008-07-02
    • milestone: 386952 --> release_3.25
     

  • Bits

    Bits - 2008-08-13

    Logged In: YES
    user_id=1531600
    Originator: NO

    Hi,

    As the L2 Team is faced the same issue at the time of configuration of a new device, after the configuration of device & its dropped of from the network due to some printer/Network issue, the next day the IP is re-used by a non CEPS device which don't have 9100 port.Due to this reason, we need to take the help of NE/DNS team to delete the DNS entry & need to re-add it again in CEPS.

    The impact of this issue is

    1/. L2 team not able to resolve the case in time
    2/. The partner/non partner is not able to use the device during this period, until the DNS team, removes the DNS entry.
    3/. If its unnoticed, the application/user is not able to proceed with the print jobs, creates a P1.

    For you reference please find the cases below.

    1. HD8529174 - Case created from the partner site to add a new device.
    2. HD8541394 - Case created by L2 team to remove the DNS entry.
    3. HD8323552 - Case created from the partner site to add a new device.

    Thanks,
    Bits,
    CEPS Team,India

     

  • Kiran Yagnavajhala

    Kiran Yagnavajhala - 2013-06-04

    Ticket moved from /p/ceps/feature-requests/274/

    Can't be converted:

    • _milestone: release_3.25
    • _priority: 5
     

Log in to post a comment.