Switching

Expand all | Collapse all

How to verify MAC-Move or Enable MAC-Move logs

  • 1.  How to verify MAC-Move or Enable MAC-Move logs

    Posted 03-24-2018 21:11

    Hi ;

     

    we have recently deployed qfx5100 switches , in old enviroment we use to have alot of MAC moves happening .

    How can we make sure if its not happening in new topology , also do we need to enable any logging to send such events to Syslog



  • 2.  RE: How to verify MAC-Move or Enable MAC-Move logs

     
    Posted 03-25-2018 04:02


  • 3.  RE: How to verify MAC-Move or Enable MAC-Move logs

    Posted 03-25-2018 14:30

    Thanks for that , is there a way to send this info to Syslog ?

    Also the buffer seems to be pretty low , any way to increase the buffer size .

    using following

     

     show ethernet-switching mac-learning-log



  • 4.  RE: How to verify MAC-Move or Enable MAC-Move logs

     
    Posted 03-27-2018 03:06

    There is no configuration option to send the show command logs to syslog.  You would have to create an event script on the box to run the command periodically and send the syslog messages for the mac moves it sees in the output.

     

    https://www.juniper.net/documentation/en_US/junos/topics/concept/junos-script-automation-event-notifications-and-policy-overview.html

     

    There is an automation forum here where you might be able to get help with a script.

     



  • 5.  RE: How to verify MAC-Move or Enable MAC-Move logs

     
    Posted 03-25-2018 22:18

    Hi Folks,

    Just my 2 cents on this…

     

    I love to analyze the logs on the box with inbuilt shell as below,

     

    start shell

     

    % cat mac

    Mar 18 21:33:14 2018 vlan_name TEST mac 00:05:86:74:e5:ef was learned on ae10.0 with flags: 0x2001f

    Mar 18 21:33:14 2018 vlan_name TEST mac 00:05:86:74:e5:ef was deleted from ae10.0 with flags: 0x1000

    Mar 18 21:33:14 2018 vlan_name TEST mac 00:05:86:74:e5:ef was learned on ae10.0 with flags: 0x2001f

    Mar 18 21:33:14 2018 vlan_name TEST mac 00:05:86:74:e5:ef was deleted from ae10.0 with flags: 0x1000

    Mar 18 21:33:14 2018 vlan_name TEST mac 00:05:86:74:e5:ef was learned on ae10.0 with flags: 0x2001f

    Mar 18 21:33:14 2018 vlan_name TEST mac 00:05:86:74:e5:ef was deleted from ae10.0 with flags: 0x1000

     

    % cat mac | awk '{print $1"-"$2,$4, $5"-"$6,$8,$10,"interface "$12}' | sort | uniq -c

       3 Mar-18 2018 vlan_name-TEST 00:05:86:74:e5:ef deleted interface ae10.0

       3 Mar-18 2018 vlan_name-TEST 00:05:86:74:e5:ef learned interface ae10.0

    %

     

    These one-liners will give us with some good pointers during troubleshooting a live box with multiple mac-moves…

     

    Juniper boxes are really cool… for automation

     



  • 6.  RE: How to verify MAC-Move or Enable MAC-Move logs

    Posted 03-25-2018 10:38

    Hi,

    You can enable different actions on mac-move :

     

    Configuring MAC Move Limiting (CLI Procedure)

     

    //Regards

    AD



  • 7.  RE: How to verify MAC-Move or Enable MAC-Move logs

    Posted 03-25-2018 14:32

    @ Good one ; i will check . thanks



  • 8.  RE: How to verify MAC-Move or Enable MAC-Move logs

    Posted 04-04-2018 06:37

    So guys i tried this on new QFX switches and it bunmped everything BFD,ISIS and BGP ; NOT Recomended

     

    > configure

    Entering configuration mode

     

     

    set vlans Private_Wi-Fi1 switch-options mac-move-limit 1 packet-action log

     

    {master:0}[edit]

    commit synchronize

    fpc0:

    Apr  5 01:14:01  AKDCS1.FTC.NEW mgd[54325]: UI_COMMIT: User '' requested 'commit synchronize' operation (comment: none)

    configuration check succeeds

    commit complete

     

    {master:0}[edit]

    Apr  5 01:14:03  AKDCS1.FTC.NEW mgd[54325]: UI_COMMIT_COMPLETED: commit complete

    Apr  5 01:14:04  AKDCS1.FTC.NEW fpc0 BRCM-VIRTUAL,brcm_virtual_bd_change(),558:Could not enable transient traffic for BD(211) MC-IP(0x0) ret -4

    Apr  5 01:14:05  AKDCS1.FTC.NEW bfdd[1719]: BFDD_TRAP_SHOP_STATE_DOWN: local discriminator: 21, new state: down, interface: ae1.0, peer addr: 10.200.100.22

    Apr  5 01:14:05  AKDCS1.FTC.NEW bfdd[1719]: BFD Session 10.200.100.22 (IFL 556) state Up -> Down LD/RD(21/21) Up time:12:33:51 Local diag: CtlExpire Remote diag: None Reason: Detect Timer Expiry.

    Apr  5 01:14:05  AKDCS1.FTC.NEW rpd[1714]: RPD_ISIS_ADJDOWN: IS-IS lost L2 adjacency to AKDCS3.BTNS.NEW on ae1.0, reason: BFD Session Down

    Apr  5 01:14:05  AKDCS1.FTC.NEW bfdd[1719]: BFD Session 10.200.100.2 (IFL 555) state Up -> Down LD/RD(22/19) Up time:00:37:07 Local diag: CtlExpire Remote diag: None Reason: Detect Timer Expiry.

    Apr  5 01:14:05  AKDCS1.FTC.NEW bfdd[1719]: BFDD_TRAP_SHOP_STATE_DOWN: local discriminator: 22, new state: down, interface: ae0.0, peer addr: 10.200.100.2

    Apr  5 01:14:05  AKDCS1.FTC.NEW rpd[1714]: RPD_ISIS_ADJDOWN: IS-IS lost L2 adjacency to AKDCS2.FTC.NEW on ae0.0, reason: BFD Session Down

    Apr  5 01:14:06  AKDCS1.FTC.NEW mib2d[1713]: SNMP_TRAP_LINK_DOWN: ifIndex 553, ifAdminStatus down(2), ifOperStatus down(2), ifName vtep.32770

    Apr  5 01:14:06  AKDCS1.FTC.NEW mib2d[1713]: SNMP_TRAP_LINK_DOWN: ifIndex 552, ifAdminStatus down(2), ifOperStatus down(2), ifName vtep.32769

    Apr  5 01:14:06  AKDCS1.FTC.NEW mib2d[1713]: SNMP_TRAP_LINK_DOWN: ifIndex 554, ifAdminStatus down(2), ifOperStatus down(2), ifName vtep.32771

    Apr  5 01:14:15  AKDCS1.FTC.NEW fpc0 Anchor rule add/chg update failed(1000): (10.200.100.22:3784), Gencfg op:3, OP:1

    Apr  5 01:14:15  AKDCS1.FTC.NEW fpc0 Anchor rule add/chg update failed(1000): (10.200.100.2:3784), Gencfg op:3, OP:1