Hi Paul > I'm trying to figure out what MAC address an IRB assumes? In this case > IRB.61 interface.... >
I haven't got an MX handy, but on the EX, IRBs take MAC addresses from the same pool that physical interfaces use: r...@ex3200-uptown> show ethernet-switching table Ethernet-switching table: 1 entries, 0 learned VLAN MAC address Type Age Interfaces client 00:26:88:72:23:40 Static - Router r...@ex3200-uptown> show interfaces ge-0/0/0 | match Hardware Interface flags: Hardware-Down SNMP-Traps Internal: 0x0 Current address: 00:26:88:72:23:40, Hardware address: 00:26:88:72:23:40 In the above output, my client VLAN doesn't have ge-0/0/0 as a member. It is annoying that the irb interface (or vlan.x interface on the EX) doesn't report the MAC like a normal L3 interface would. > Logical interface irb.61 (Index 84) (SNMP ifIndex 187) > > Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2 > > Bandwidth: 10000mbps > > Routing Instance: default-switch Bridging Domain: vlan-61+61 > > Input packets : 32942 > > Output packets: 938 > > Protocol inet, MTU: 1500 > > Addresses, Flags: Is-Preferred Is-Primary > > Destination: xx.xx.xx/24, Local: xx.xx.xx.34, Broadcast: > xx.xx.xx.255 > > Protocol inet6, MTU: 1500 > > Flags: Is-Primary > > Addresses, Flags: Is-Default Is-Preferred Is-Primary > > Destination: xxxx:xxx:xxx::/64, Local: xxxx:xxx:xxx::34 > > Addresses, Flags: Is-Preferred > > Destination: fe80::/64, Local: fe80::222:83ff:fe07:7ff0 > > Protocol multiservice, MTU: 1500 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp