[j-nsp] EX Switch Question

[James S. Smith]

Just avoid the 4500 if you need anything less than 1G copper.  The ports on the 4500 won't negotiate to 10 or 100.  I was told by the sales engineer that this switch is a "top of rack" switch so it doesn't support anything less than 1G. 

I found that funny since I have a whole rack of Avaya gear that Avaya insists must have the switch set to 100/Full.


----- Original Message -----
From: Tobias Heister [mailto:lists at tobias-heister.de]
Sent: Thursday, January 10, 2013 08:31 AM
To: Paul Stewart <paul at paulstewart.org>
Cc: juniper-nsp at puck.nether.net <juniper-nsp at puck.nether.net>
Subject: Re: [j-nsp] EX Switch Question

Hi,

Am 10.01.2013 14:03, schrieb Paul Stewart:
> Per port ingress and egress bandwidth control (rate limiting with burst)
> 
> Per VLAN ingress and egress bandwidth control (rate limiting on a per VLAN
> basis with burst)

As you mentioned this could be the problem or showstopper.
We have not yet found an EX platform (tried 2200/3200/4200/4500/8200) which supported policing on egress (using Firewall filters and policing, never tried using QoS)

Just tested it on en EX8216 running 10.4R9
"Referenced filter 'test123' can not be used as policer not supported on egress"

I do not know if this is a hardware or software problem and if it may be solved in later releases (if software problem). The latest code we run is 11.4R1 on EX2200/3200/4200/4500 and there
it is not possible. I kind of remember it being a hardware problem but i am not sure.

We would have a couple use cases for this feature too so we would be interested in any findings.

regards
Tobias


_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp