Switching

Expand all | Collapse all

Ex4600 'Error in: SBUS transaction.'

  • 1.  Ex4600 'Error in: SBUS transaction.'

    Posted 02-22-2017 16:13

    Hi all,

     

    Not able to find much on this one but I am seeing a reoccuring log entries on one member of a 2 Node ex4600 Chassis.

     

    Any help would be great

    Log as follows

    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x10cc0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x108c0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x108c0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x10cc0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:59:04 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 47984 is_lag_port 1 flags 0x104c0 trunk_id 1 port 0
    Feb 23 09:59:04 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:59:04 swi-02 fpc0 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 44448 is_lag_port 1 flags 0x104c0 trunk_id 1 port 0
    Feb 23 09:59:04 swi-02 fpc0 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry

    Feb 23 09:59:09 swi-02 fpc1 Unit: 0
    Feb 23 09:59:09 swi-02 fpc1 Mem:
    Feb 23 09:59:09 swi-02 fpc1 Parity error..
    Feb 23 09:59:09 swi-02 fpc1 Error in: SBUS transaction.
    Feb 23 09:59:09 swi-02 fpc1 Blk: 1, Pipe: 1, Address: 0x28401698, base: 0x10, stage: 10, index: 5784
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: mem: 2046=L3_DEFIP blkoffset:10
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: RESTORE[from X pipe]: L3_DEFIP[2046] blk: ipipe0 index: 5784
    Feb 23 09:59:09 swi-02 fpc1 Unit: 0
    Feb 23 09:59:09 swi-02 fpc1 Mem:
    Feb 23 09:59:09 swi-02 fpc1 Parity error..
    Feb 23 09:59:09 swi-02 fpc1 Error in: SBUS transaction.
    Feb 23 09:59:09 swi-02 fpc1 Blk: 1, Pipe: 1, Address: 0x284016a8, base: 0x10, stage: 10, index: 5800
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: mem: 2046=L3_DEFIP blkoffset:10
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: RESTORE[from X pipe]: L3_DEFIP[2046] blk: ipipe0 index: 5800



  • 2.  RE: Ex4600 'Error in: SBUS transaction.'

    Posted 04-25-2017 14:34

    Running across the exact same message myself. Did you ever come up with a fix?



  • 3.  RE: Ex4600 'Error in: SBUS transaction.'

    Posted 04-25-2017 22:13

    HI Joel

     

    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x10cc0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x108c0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x108c0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 0 is_lag_port 1 flags 0x10cc0 trunk_id 1 port 0
    Feb 23 09:57:38 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry
    Feb 23 09:59:04 swi-02 fpc1 LBCM-L2,pfe_bcm_l2_mac_add(),690:modid 1 port 47984 is_lag_port 1 flags 0x104c0 trunk_id 1

    On QFX5100 and EX4600 switches, every time a MAC address is learned, some messages might be output to syslog and be repeated frequently. The logged messages have no impact on service traffic.

    https://prsearch.juniper.net/PR1171523

    Feb 23 09:59:04 swi-02 fpc0 LBCM-L2,pfe_bcm_l2_mac_add(),702:same mac entry

    Feb 23 09:59:09 swi-02 fpc1 Unit: 0
    Feb 23 09:59:09 swi-02 fpc1 Mem:
    Feb 23 09:59:09 swi-02 fpc1 Parity error..
    Feb 23 09:59:09 swi-02 fpc1 Error in: SBUS transaction.
    Feb 23 09:59:09 swi-02 fpc1 Blk: 1, Pipe: 1, Address: 0x28401698, base: 0x10, stage: 10, index: 5784
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: mem: 2046=L3_DEFIP blkoffset:10
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: RESTORE[from X pipe]: L3_DEFIP[2046] blk: ipipe0 index: 5784
    Feb 23 09:59:09 swi-02 fpc1 Unit: 0
    Feb 23 09:59:09 swi-02 fpc1 Mem:
    Feb 23 09:59:09 swi-02 fpc1 Parity error..
    Feb 23 09:59:09 swi-02 fpc1 Error in: SBUS transaction.
    Feb 23 09:59:09 swi-02 fpc1 Blk: 1, Pipe: 1, Address: 0x284016a8, base: 0x10, stage: 10, index: 5800
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: mem: 2046=L3_DEFIP blkoffset:10
    Feb 23 09:59:09 swi-02 fpc1 Unit 0: RESTORE[from X pipe]: L3_DEFIP[2046] blk: ipipe0 index: 5800

    External-Title
    QFX5100 reports false parity error messages like "soc_mem_array_sbusdma_read" & "soc_ser_correction: mem write".
    Customer-Risk
    minor
    Release-Note
    SDK can raise false alarms for parity error messages like  "soc_mem_array_sbusdma_read" & "soc_ser_correction: mem write" on QFX5100.


    Workaround-Provided
    yes
    Workaround
    Reboot resolves the issue temporarily. Issue might come back later.


    External-Description
    1. Software Development Kit mistakenly believes existence of parity errors.  This false reporting manifests itself via following log messages on the switch:

    Feb 10 14:41:47.422 H01-387A-D25-250 feb1 _soc_mem_array_sbusdma_read: ING_FLEX_CTR_COUNTER_TABLE_5_X.ipipe0 failed(ERR)
    Feb 10 14:41:47.422 H01-387A-D25-250 feb1 H/W received sbus nack with error bit set.
    Feb 10 14:41:47.423 H01-387A-D25-250 feb1 Error in: SBUS transaction.
    Feb 10 14:41:47.424 H01-387A-D25-250 feb1 Unit 0: soc_ser_correction: mem write ING_FLEX_CTR_OFFSET_TABLE_4.ipipe0[33797] failed: Invalid parameter
    Nov 17 07:03:25   fpc0 Unit: 0  
    Nov 17 07:03:25   fpc0 Mem:
    Nov 17 07:03:25   fpc0 Parity error..
    Nov 17 07:03:25   fpc0 Error in: SBUS transaction.
    Nov 17 07:03:25   fpc0 Blk: 1, Pipe: 0, Address: 0x284013db, base: 0x10, stage: 10, index: 5083
    Nov 17 07:03:25   fpc0 Unit 0: mem: 2046=L3_DEFIP blkoffset:10
    Nov 17 07:03:25   fpc0 Unit 0: RESTORE[from Y pipe]: L3_DEFIP[2046] blk: ipipe0 index: 5083
     
    2. The SW fix for this issue is in 14.1X53-D37 onwards

    https://prsearch.juniper.net/PR1161821

     

    Thanks

    Partha

     

    Hope the information helps.