Hi George,
Are you able to share the configuration you used to achieve point '4':
'L2protocol forwarding for both tagged and untagged PDUs is supported
with port-based EoMPLS'
I currently have a setup like this:
interface GigabitEthernet0/4
mtu 9000
no ip address
negotiation auto
l2proto-fo
We have replaced all our sup-s with sup-2s and shipped back the sup-1s, but
kept the slot0: flash cards because they still had sensitive data. We have
been trying to format the flash cards using different DISK utilities and CLIs
but cannot seem to find anything that will work.
I used to do th
Previously there was a bug that effected the 6500s.
In this bug if you had a route that covered 0::/96, it would cause the
TestFibDevices fail.
This bug is back in the 15.2 code for the 7600.
Specifically: 15.2(4)S3a
I am guessing this is a result of the re-merge of the 7600/6500 code trains.
Mac
Dear Eggsperts,
I'm playing with a 7301 in the lab as an L2TP LAC for punting PPPoE subscribers
off to a monster LNS. I was trying to figure out a solution for link redundancy
with one of our wholesale relationships and the solution I came up with was IRB
with an SVI bonding two sub-interfaces
Hi Psem,
We also did some tests with the ASR901 and we had issues with l2protocol
forwarding
After some research with cisco, we concluded that
- L2protocol tunnelling is not supported and there is no plan to support it
- L2protocol forwarding is supported on EFPs only for untagged PDUs
- L2protoc
Good read about BGP in different scenarios:
http://tools.ietf.org/html/draft-lapukhov-bgp-routing-large-dc-02
Guilherme Loch Góes
On Sat, Aug 24, 2013 at 1:16 PM, Mark Tinka wrote:
> On Tuesday, August 13, 2013 11:07:07 AM Adam Vitkovsky
> wrote:
>
>> I'd like the BGP-LS to take over that role,
