-nsp] General MX notes for use as a core ethernet
switch...
Somewhat related, I seem to recall reading/hearing/imagining
somewhere that an MX chassis couldn't provide enough power to 'fuel' a
full complement of DPCE-EQ cards (not sure if this was tied to a
particular chassis o
Somewhat related, I seem to recall reading/hearing/imagining
somewhere that an MX chassis couldn't provide enough power to 'fuel' a
full complement of DPCE-EQ cards (not sure if this was tied to a
particular chassis or not). Sounds strange, I know, but can anyone
confirm/deny this potentially im
> No option to distribute by src/dst IP, TCP/UDP src/dst port, MPLS label ?
>
>
>
We were only looking at layer-2 interfaces that are part of
bridge-domains... Good question though. You can configure all of those
things you mentioned, it really depends on what family is configured on
the int
On Mon, Aug 18, 2008 at 11:33:25PM -0300, Rubens Kuhl Jr. wrote:
> > 3) To be 100% compatible with Cisco's PVST+, you need to use "force-version"
> > and make sure you are configured for STP and not rapid-pvst...
>
> Any references whether this is the case with EX-series ?
Interoperability betwee
On Mon, Aug 18, 2008 at 10:12 PM, Derick Winkworth <[EMAIL PROTECTED]> wrote:
> Fiddling with the MX for a POC-like session, I found a couple of things
> others may find interesting...
>
> 1) On etherchannel bundles, traffic is distributed per destination-mac, per
> source-mac, or both. Unfortunat
Fiddling with the MX for a POC-like session, I found a couple of things
others may find interesting...
1) On etherchannel bundles, traffic is distributed per destination-mac,
per source-mac, or both. Unfortunately, this is not configurable on a
per-link basis, only globally. So, for us, this
6 matches
Mail list logo
