On (2008-12-01 14:50 -0500), Julio Arruda wrote:
And I understand Nexus is the EARL8, correct ?
And this would also mean the 3B, 3C and the XLs are all EARL7, but with
distinct sizes for the TCAMs tied to them ?
3C is EARL7.5.
--
++ytti
___
SIP/SPA does indeed provide per-port local VLAN significance for this
platform, please prepare your wallet in such case :)
Dave.
Saku Ytti wrote:
On (2008-11-28 18:07 +0200), Tassos Chatzithomaoglou wrote:
Just to add (if i remember right) that ES and SRB didn't support local VLAN
On (2008-12-01 12:02 +), David Freedman wrote:
SIP/SPA does indeed provide per-port local VLAN significance for this
platform, please prepare your wallet in such case :)
Not 100% sure where this reply was directed, but SIP/SPA has exactly
same caveats as ES+, you're still limited to 4k
On (2008-11-30 19:28 -0500), Julio Arruda wrote:
I was under impression the L3 forwarding and the L2 forwarding was done
by the same engine, in the PFC card(s) ? and behind it, the EARL for the
lookup and the rewriting of the header info (mac rewrite, dec ttl and
goes on) ?
Inside
On Mon, December 1, 2008 13:02, David Freedman wrote:
SIP/SPA does indeed provide per-port local VLAN significance for this
platform, please prepare your wallet in such case :)
Dave.
However, SIP/SPA still consume global (internal) VLAN resources per L3
subif..only the VLAN IDs need not
On (2008-12-01 13:20 +0100), Johannes Resch wrote:
As others have pointed out, using service instances on ES/ES+ will not
require global VLANs, but this only applies for terminating plain PWEs.
For L3 subif/VPLS, again a global VLAN/SVI is required.
This is not true for ES+, ES+ can have,
On Mon, December 1, 2008 14:30, Saku Ytti wrote:
On (2008-12-01 13:20 +0100), Johannes Resch wrote:
As others have pointed out, using service instances on ES/ES+ will not
require global VLANs, but this only applies for terminating plain PWEs.
For L3 subif/VPLS, again a global VLAN/SVI is
Saku Ytti wrote:
On (2008-11-30 19:28 -0500), Julio Arruda wrote:
I was under impression the L3 forwarding and the L2 forwarding was done
by the same engine, in the PFC card(s) ? and behind it, the EARL for the
lookup and the rewriting of the header info (mac rewrite, dec ttl and
Julio Arruda wrote:
I was under impression the L3 forwarding and the L2 forwarding was done
by the same engine, in the PFC card(s) ? and behind it, the EARL for the
lookup and the rewriting of the header info (mac rewrite, dec ttl and
goes on) ?
PFC/DFC - is the customer facing name for
Ian Cox wrote:
Julio Arruda wrote:
I was under impression the L3 forwarding and the L2 forwarding was done
by the same engine, in the PFC card(s) ? and behind it, the EARL for the
lookup and the rewriting of the header info (mac rewrite, dec ttl and
goes on) ?
PFC/DFC - is the customer
In article [EMAIL PROTECTED],
On Fri, Nov 28, 2008 at 07:52:23AM -0800, Mark Tech wrote:
Is there anyway around this? I want the 7600 to act like a router, not
a switch!
In that case, buy a router, not a switch...
The upside is that the 7600 can do proper ether channels - so if you
just
Hi,
On Sun, Nov 30, 2008 at 02:23:35PM +, Matthew Melbourne wrote:
And yes, this is one of the most serious design limitations of the
6500/7600 - global VLAN space (with LAN interfaces). But it's a
well-known and well-documented limitation, so usually people know in
advance and can
Gert Doering wrote:
Hi,
On Sun, Nov 30, 2008 at 02:23:35PM +, Matthew Melbourne wrote:
And yes, this is one of the most serious design limitations of the
6500/7600 - global VLAN space (with LAN interfaces). But it's a
well-known and well-documented limitation, so usually people know in
Hi,
On Sun, Nov 30, 2008 at 07:28:48PM -0500, Julio Arruda wrote:
I was under impression the L3 forwarding and the L2 forwarding was done
by the same engine, in the PFC card(s) ? and behind it, the EARL for the
lookup and the rewriting of the header info (mac rewrite, dec ttl and
goes on)
Hi
With my GSR, I can split traffic on seperate physical interfaces, reusing the
same vlan #, i.e.
interface GigabitEthernet0/0/6.2
encapsulation dot1Q 2
ip address 7.7.7.1 255.255.255.252
no ip directed-broadcast
no cdp enable
!
interface GigabitEthernet0/0/7.2
encapsulation dot1Q 2
ip
You're looking for local VLAN significance.
You probably have to get one of the WAN-style (ES20/40 for sure, don't know for
SIP/SPA) cards.
--
Tassos
Mark Tech wrote on 28/11/2008 17:52:
Hi
With my GSR, I can split traffic on seperate physical interfaces, reusing the
same vlan #, i.e.
Just to add (if i remember right) that ES and SRB didn't support local VLAN
significance under single tagged subifs.
I haven't checked if SRD and/or ES+ solve this problem.
--
Tassos
Tassos Chatzithomaoglou wrote on 28/11/2008 18:01:
You're looking for local VLAN significance.
You probably
Hi,
On Fri, Nov 28, 2008 at 07:52:23AM -0800, Mark Tech wrote:
Is there anyway around this? I want the 7600 to act like a router, not a
switch!
In that case, buy a router, not a switch...
The upside is that the 7600 can do proper ether channels - so if you
just want to distribute traffic for
On (2008-11-28 18:07 +0200), Tassos Chatzithomaoglou wrote:
Just to add (if i remember right) that ES and SRB didn't support local VLAN
significance under single tagged subifs.
I haven't checked if SRD and/or ES+ solve this problem.
ES+ does solve the issue indeed, but you're still limited
19 matches
Mail list logo
