Hi We are getting some errors while commiting synchronize on a MX device (Re0:Master) running 10.4R7.5
re0: configuration check succeeds re1: configuration check succeeds error: timeout waiting for response from re1 re0: error: remote unlock-configuration failed on re1 error: timeout waiting for response from re1 We checked both Re for zombie process locking the configuration on backup RE, but they show normal behavior, the backup RE shows the following log on the mastership log Oct 25 20:57:31 mcontrol hipri thread scheduling slip 2 sec, 22725 usec Also the following logs are displayed while RE is commiting Oct 25 20:57:31 -re1 /kernel: invalid_device = 0 inv_bio_err = 0 soft_err = 0 abort_err = 0 Oct 25 20:57:31 -re1 /kernel: ucrc_err = 0 dma_err = 0 illen_err = 0 nomedia_err = 0 Oct 25 20:57:31 -re1 /kernel: mcr_err = 0 id_err = 0 mc_err = 0 uncorr_err = 0 transxn_err = 0 Oct 25 20:57:31 -re1 /kernel: busy_timeout = 0 cmd_issue_err = 0 dma_load_err = 0 dma_start_err = 0 Oct 25 20:57:31 -re1 /kernel: invalid_device = 0 inv_bio_err = 0 soft_err = 0 abort_err = 0 Oct 25 20:57:31 -re1 /kernel: ucrc_err = 0 dma_err = 0 illen_err = 0 nomedia_err = 0 Oct 25 20:57:31 -re1 /kernel: mcr_err = 0 id_err = 0 mc_err = 0 uncorr_err = 0 transxn_err = 0 Oct 25 20:57:31 -re1 /kernel: busy_timeout = 0 cmd_issue_err = 0 dma_load_err = 0 dma_start_err = 0 anybody has getting this behavior before? Thanks in advance Mario _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
