Randy is correct. In most cases, the two protocols are running co-incident
for a while so you can do your table validation and topology mapping and
then you turn off OSPF. For vendors that aren't capable of supporting ISIS,
this is a feature and not a bug.
On Sun, May 12, 2013 at 1:57 AM, Randy
Randy is correct
But who'd follow his advice, he regularly encourages his competitors
to do stupid things.
brandon
On Sun, May 12, 2013 at 6:41 PM, Glen Kent glen.k...@gmail.com wrote:
I would like to understand the scenarios wherein the service
provider/network admin might run both ISIS and OSPF together inside their
network. Is this something that really happens out there?
One scenario that i can think
Sent from my iPhone
On May 12, 2013, at 1:41 AM, Glen Kent glen.k...@gmail.com wrote:
The other instance would be when say OSPF is used to manage the OOB network
and the ISIS is used for network reachability.
Is there any other scenario?
Yes, in virtualization world , where people no
Folks could, at least theoretically, use ISIS or OSPF multi instance/multi
topology extensions to support IPv4 and IPv6 topologies. This way they
would only need to run a single protocol and thereby requiring expertise in
handling only one protocol.
and, as is-is supports 4 and 6, why do you
Ospf offered as Pe-ce protocol to L3 mpls vpn customers and Isis as IGP for
MPLS Core.
Sent from my iPhone
On May 12, 2013, at 9:41 AM, Glen Kent glen.k...@gmail.com wrote:
Hi,
I would like to understand the scenarios wherein the service
provider/network admin might run both ISIS and
On Sun, 12 May 2013, Glen Kent wrote:
Is there any other scenario?
When you might run OSPFv3 (for IPv6) and ISIS (IPv4) together because you
have equipment that is buggy for ISIS multi topology.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
One scenario that i can think of when somebody might run the 2 protocols
ISIS and OSPF together for a brief period is when the admin is migrating
from one IGP to the other. This, i understand never happens in steady
state. The only time this can happen is if an AS gets merged into another
AS
Glen,
One transition scenario you noted below is often a use case. I have seen
networks move from OSPF to IS-IS (more cases then the reverse).
In those cases, the overlap period may not be very short (years vs.
weeks/months).
I have also seen some use one protocol (which I think was mentioned
Subject: ISIS and OSPF together Date: Sun, May 12, 2013 at 02:11:37PM +0530
Quoting Glen Kent (glen.k...@gmail.com):
Hi,
I would like to understand the scenarios wherein the service
provider/network admin might run both ISIS and OSPF together inside their
network. Is this something that
Victor,
Folks could, at least theoretically, use ISIS or OSPF multi instance/multi
topology extensions to support IPv4 and IPv6 topologies. This way they
would only need to run a single protocol and thereby requiring expertise in
handling only one protocol.
With whatever i remember, OSPFv3 can
highlighted the context before sorry.
Regards,
Victor K
From: Glen Kent glen.k...@gmail.com
Date: Mon, 13 May 2013 00:13:38 +0530
To: Victor Kuarsingh vic...@jvknet.com
Cc: nanog@nanog.org nanog@nanog.org
Subject: Re: ISIS and OSPF together
Victor,
Folks could, at least theoretically, use
13 matches
Mail list logo
