Be mindful of the software version you are using. We stumbled across a
problem on the SRX240 (different class of device, I know). When we
SNMP querry a VLAN interface, there was a memory leak. Over time, it
caused all control plane memory to be consumed. When that happened,
the SRX would stop learning new ARP entries and all kinds of things
broke.
We were running Junos 9.6R2 when we first saw the issue. I believe
9.6R3 has a fix for the issue. I'm not sure what (if any) versions of
10.x are impacted.
I'd suggest building one box with your VLAN configuration and watching
it for 3-4 weeks. Just be sure to point your supporting systems at it
as well. If you suddenly start seeing a log message similar to this,
get worried:
/kernel: kmem type tlv_stat using 143048K, exceeding limit 91352K
--
Brad Fleming
On Mar 15, 2010, at 10:41 AM, Quoc Hoang wrote:
Hi,
Looking to trunk (vlan tagging) on the SRX 3600 to reduce the
number of physical interfaces required. Anyone currently using it
that can provide feedback or issues? Good or bad idea?
Doesn't appear to be any details of vlan tagging in the srx docs so
not sure if it's officially supported.
TIA,
quoc
_______________________________________________
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
