Switching

Expand all | Collapse all

4300EX EX-BCM PIC errors

Jump to Best Answer
  • 1.  4300EX EX-BCM PIC errors

    Posted 01-12-2017 11:42

    Experts,

     

    I have started seeing these messages:

     

    Jan 12 13:40:00 MDF fpc3 [EX-BCM PIC] ex_bcm_linkscan_handler: Link 46 UP
     Jan 12 13:39:58 MDF fpc3 [EX-BCM PIC] ex_bcm_linkscan_handler: Link 46 DOWN

     

    as errors Thank You



  • 2.  RE: 4300EX EX-BCM PIC errors

    Posted 01-12-2017 12:56

    I think this might be something juniper support might look, since I really cannot find anything. 



  • 3.  RE: 4300EX EX-BCM PIC errors

    Posted 01-12-2017 13:00

    Hi,

     

    This is a  logging done due to some call to the reference value. These log messages are merely informational and not harmful, you can ignore them.

     

    You can use the below mentioned technical document to filter them if required:

    [Junos Platform] Example - How to prevent certain syslog messages from being written to the log file

     

    [KUDOS PLEASE! If you think I earned it!

    If this solution worked for you please flag my post as an "Accepted Solution" so others can benefit..]



  • 4.  RE: 4300EX EX-BCM PIC errors

    Posted 01-12-2017 13:43

    Yes I think the log is refering to some ports and flaping issue. 

     

    But the link is great - Thank You again. 



  • 5.  RE: 4300EX EX-BCM PIC errors

    Posted 01-12-2017 14:06

    Hi,

     

    If this solution worked for you please flag my post as an "Accepted Solution" so others can benefit..



  • 6.  RE: 4300EX EX-BCM PIC errors
    Best Answer

     
    Posted 01-12-2017 23:26

    Reported observation: “[EX-BCM PIC] ex_bcm_linkscan_handler" messages seen in the box

     

    Resolution: These log message “pfex: [EX-BCM PIC] ex_bcm_linkscan_handler:” is informational message which is about interface going up and down. This is system detection mechanism found that port link state has changed.



  • 7.  RE: 4300EX EX-BCM PIC errors

    Posted 09-12-2019 06:39

    Applies to the normal operation of regular revenue port going up/down as result of a host being powered off for example...

     

    Is that right ?