Remove the "DATABASES" from the vlan members list.. The native VLAN will take care of it... Right now incoming untagged goes to Databases and outgoing it gets tagged.
Outside of that, multicast should work. If you don't have an igmp router somewhere you may need to enable igmp querrier support (I do believe that's what it is called).. On Aug 8, 2010 2:52 PM, "Bill Blackford" <[email protected]> wrote: The basic question here is, does Juniper handle multicast on a single vlan differently than Cisco? I have two Linux mysql hosts configured in a cluster connected to the same switch on the same vlan. They communicate on multicast when that switch is a Cisco 3560 and not at all when that switch is a EX3200. The EX's have igmp-snooping enabled by default, as I believe the Cisco does. Both interfaces are pretty straight forward. MGT vlan-id is "1", DATABASES vlan-id is "5". Both hosts need to send un-tagged traffic on 802.1q tag 5. <snip> ge-0/0/2 { description data-01.mysql; unit 0 { family ethernet-switching { port-mode trunk; vlan { members [ MGT DATABASES ]; } native-vlan-id 5; } } } ge-0/0/3 { description data-02.mysql; unit 0 { family ethernet-switching { port-mode trunk; vlan { members [ MGT DATABASES ]; } native-vlan-id 5; } } } </snip> Thank you in advance for any insight, -b -- Bill Blackford Senior Network Engineer Technology Systems Group Northwest Regional ESD Logged into reality and abusing my sudo priviledges _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
