Switching

Hi,

Now i have LACP  between router and switch: 4x10G - two mics, each have 2x10G. Because of case in jtac i have to replace both modules. I see that lacp use virtual mac address (multicast ?) ending with x:x:2f:c0. I hope that if replace first modules, mac will stay the same but when i will replace second module, mac address can change ? Am i right ? what can i do to minimalize  this time ? AFAIK router should send gratuitous arp with new mac ? 

thx for help

Tedy

I might not got tcorrectly what you are looking for.

The MAC associated with the LAG interface comes from a reserved pool of MAC addresses and has nothing to do with the child link interfaces:

lab@MX80> show chassis mac-addresses
MAC address information:
  Public base address     80:71:1f:c0:11:00
  Public count            192
  Private base address    80:71:1f:c0:11:c0
  Private count           64

lab@MX80> show interfaces ae1 | match Hard
  Current address: 80:71:1f:c0:11:c1, Hardware address: 80:71:1f:c0:11:c1

lab@MX80> show lacp interfaces ae1
Aggregated interface: ae1
    LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
      xe-0/0/0       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
      xe-0/0/0     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
    LACP protocol:        Receive State  Transmit State          Mux State
      xe-0/0/0                  Current   Fast periodic Collecting distributing

lab@MX80> show interfaces xe-0/0/0 | match Hard
  Current address: 80:71:1f:c0:11:c1, Hardware address: 80:71:1f:c0:11:00

lab@MX80>


ae1 is configured with family inet and on the remote device, the ARP for the IP address configured on MX80 is pointing to the LAG MAC:

lab@MX480-re1> show arp no-resolve | match 172.25.100.34
80:71:1f:c0:11:c1 172.25.100.34   ae1.100                  none

lab@MX480-re1>

So you should not see any service impact during the change.


=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Thanks for reply,

I suppose that part of virtual mac address in LACP is from hardware address and last 2 bits from the special pool:

MX1# run show chassis mac-addresses
MAC address information:
 Public base address     ac:4b:c8:95:28:00
 Private base address    ac:4b:c8:95:2f:c0

MX2# run show chassis mac-addresses
MAC address information:
  Public base address     a8:d0:e5:f2:60:00
  Private base address    a8:d0:e5:f2:67:c0

i have two completly 2x new modules MIC-3d-2xge so i suppose they have different mac address each other and different than mics currently in router. So i suppose mac will change

greetings

Ted

Check this test:

[edit]
root@EX9204-RE0# run show chassis mac-addresses
MAC address information:
  Public base address     dc:38:e1:15:54:40
  Public count            1984
  Private base address    dc:38:e1:15:5c:00
  Private count           64

[edit]
root@EX9204-RE0# run show chassis fpc
                     Temp  CPU Utilization (%)   Memory    Utilization (%)
Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
  0  Online            38      8          0       2048       17         14
  1  Online            38      8          0       2048       17         14
  2  Online            36      9          0       2048        9         13

[edit]
root@EX9204-RE0# run show interfaces ae13 | match Hard
  Current address: dc:38:e1:15:5c:0d, Hardware address: dc:38:e1:15:5c:0d

[edit]
root@EX9204-RE0# run request chassis fpc slot 0 offline
Offline initiated, use "show chassis fpc" to verify

[edit]
root@EX9204-RE0# run request chassis fpc slot 1 offline
Offline initiated, use "show chassis fpc" to verify

[edit]
root@EX9204-RE0# run request chassis fpc slot 2 offline
Offline initiated, use "show chassis fpc" to verify

[edit]
root@EX9204-RE0# run show chassis fpc
                     Temp  CPU Utilization (%)   Memory    Utilization (%)
Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
  0  Offline         ---Offlined by cli command---
  1  Offline         ---Offlined by cli command---
  2  Offline         ---Offlined by cli command---

[edit]
root@EX9204-RE0# run show chassis mac-addresses
MAC address information:
  Public base address     dc:38:e1:15:54:40
  Public count            1984
  Private base address    dc:38:e1:15:5c:00
  Private count           64

[edit]
root@EX9204-RE0# run show interfaces ae13 | match Hard
  Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000
  Current address: dc:38:e1:15:5c:0d, Hardware address: dc:38:e1:15:5c:0d
    Flags: Hardware-Down Device-Down SNMP-Traps 0x4004000 Encapsulation: ENET2

[edit]
root@EX9204-RE0#

As you can see, you can assign a large continuous pool of MAC addresses. It's very unlikely that every time you need to RMA a MIC/FPC, you will get one that will have its MAC addresses from the pool of the device. Hence it makes more sense that the chassis will assign the MAC address from the its own pool to the interfaces.

Also, this KB explains how the LAG MAC addresses are assigned.

http://kb.juniper.net/InfoCenter/index?page=content&id=KB30423&actp=RSS


=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Confirmed, all mac's are from private pool, not connected with mic's.

Replace without packets drop

Thanks for help and explanation

Ted