[j-nsp] Directed/targeted broadcast on EX-series
Hi all,
I'm looking at enabling targeted broadcasts on specific edge VLANs to
support Wake-on-LAN.
It looks like there aren't any knobs to control the behaviour:
admin@switch# set interfaces vlan unit 100 family inet targeted-broadcast ?
Possible completions:
[Enter]Execute this command
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
|Pipe through a command
{master:0}[edit]
Is there any way to control which source IPs can send targeted
broadcasts, or is it as it seems -- i.e. that it's all or nothing?
The forward-and-send-to-re and forward-only knobs to control
forwarding aren't there on my JUNOS EX boxes. Does anyone know what
the behaviour is on EX-series?
Cheers,
Dale
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Problems with Link Aggregation
Hi, http://kb.juniper.net/InfoCenter/index?page=contentid=KB10926actp=searchviewlocale=en_USsearchid=136661818 Here is written that it uses layer 2,3 and 4 for load balancing hash algorithm. And yes, the forwarding-options hash is not configurable on EX-series. HTH, Ivan, On Sun, Apr 21, 2013 at 6:11 PM, Mark Tinka mark.ti...@seacom.mu wrote: On Wednesday, March 06, 2013 04:15:45 PM Filippo Cugini wrote: However, when we send traffic on the aggregated link, just one ge works, and we experience packet loss when we exceed the throughput of 1000mbps. Indeed, the statistics of all interfaces show that only the ge-0/0/12 is utilized to forward the data traffic, while the other two interfaces send and receive only signaling packets. We've seen this when flows are non-IP, i.e., in our case, the flows were MPLS-based. TAC came back to say the system won't load share if the flows aren't direct IP (unlike Cisco switches, it can't look beyond the MPLS frames to reveal the IP packets and hash on that). Not sure if this was your traffic type. We saw the issue on the EX4200's. Mark. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp -- Best Regards! Ivan Ivanov ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Problems with Link Aggregation
22.04.2013 12:16, Ivan Ivanov wrote: http://kb.juniper.net/InfoCenter/index?page=contentid=KB10926actp=searchviewlocale=en_USsearchid=136661818 Here is written that it uses layer 2,3 and 4 for load balancing hash algorithm. And yes, the forwarding-options hash is not configurable on EX-series. http://kb.juniper.net/InfoCenter/index?page=contentid=KB22943 For L3 (bridged and routed) EX switches construct hash value from several (6, IIRC) least significant bits of L3 and L4 addresses/ports. MAC addresses (and only MAC addresses) are used for non IP bridged traffic. So, say, (with an exception of EX8200, which can has labels) all MPLS streams between a given pair of routers will follow a single link in spite of labels and payload. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
