Thanks - that's what threw me off as I'm used to Cisco where you would see
the MAC.... ends up my problem isn't actually related to the MAC, rather
it's my IRB configuration for some reason...

Sorry to change the topic, but does anyone know what's wrong with this
configuration?  I cannot ping any remote hosts but can see ARP entries:

    ge-5/0/2 {
        unit 0 {
            family bridge {
                interface-mode trunk;
                vlan-id-list 61;
            }
        }
    }
    irb {
        unit 61 {
            family inet {
                address xxx.xx.xxx.34/24;
            }
            family inet6 {
                address xxxx:xxx:xxx::34/64;
            }
        }
    }

bridge-domains {
    vlan-61 {
        domain-type bridge;
        vlan-id 61;
        routing-interface irb.61;
    }
}


p...@core1.toronto1> show arp | match 5/0/2.0
00:10:7b:6e:64:2a xxx.xx.xxx.4    xxxxxxxxxxxxxxxxxx        ge-5/0/2.0
none
00:e0:1e:ee:ce:a2 xxx.xx.xxx.5    xxxxxxxxxxxxxxxxxx        ge-5/0/2.0
none
<snipped>

Thanks in advance,

Paul



-----Original Message-----
From: Ben Dale [mailto:bd...@comlinx.com.au] 
Sent: May-18-10 9:22 PM
To: Paul Stewart
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] IRB MAC Address Question

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

Reply via email to