My 2 cents.
2011/3/8 Ben Dale <[email protected]> > > Yes this can be done - control link traffic on the branch SRXs is actually > sent 802.1Q tagged in VLAN 4094, so you'll need to make the interface you > plug into the control link a trunk on your EX. > > As I've mentioned a couple of days ago in some of the neighboring threads, this behavior is slightly changed since 10.2. http://www.juniper.net/techpubs/en_US/junos10.2/information-products/topic-collections/release-notes/10.2/topic-45729.html#rn-junos-srx-j-CIDBS *Removing Control VLAN 4094 in Chassis Cluster*—For SRX Series branch > devices (SRX100, SRX210, SRX240, and SRX650), the existing virtual LAN *(VLAN) > tag* used for control-link traffic will be replaced with the use of > experimental Ether type *0x88b5*. However, backward compatibility is also > supported for devices that have already deployed chassis cluster with VLAN > tagging in place. > > - To toggle between VLAN and Ether type modes, use the following > command: > > set chassis cluster control-link-vlan enable/disable > > *Note: *You must perform a reboot to initialize this configuration > change. > - To show whether control port tagging is enabled or disabled, and to > view the chassis cluster information, use the following command: > > show chassis cluster information > > > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
