|
If I understand the question, the sort of link redundancy that you're
looking for (a link fails, and traffic immediately goes to the backup
link without applications being aware of the failure) isn't available
in ATM the way that it is in FDDI.
The model in ATM is that when a link fails, all the switched circuits
through that link are broken, and it is up to the end nodes to redial
any important calls. The switches are only responsible for trying to
route new calls around failed paths.
This carries over to LANE. When a LEC loses a connection to an ELAN,
it gets the connection back not by switching to standby circuits, but
by restarting the Configure/Join stage.
Every vendor's ATM products are this way; this limitation on failover
transparency isn't unique to us.
Aside: At one time, our ATM switches had a proprietary feature called
Resilient Virtual Circuits which DID provide nearly instant failover.
Unfortunately, some technical problems proved insurmountable.
Now ...
o Connecting two links between each pair of ATMswitches sounds like
it should work, as long as you understand the nature of ATM fault
tolerance ("redial, not transparent").
I don't know enough about our switching/routing implementation to
<guarantee> that it will work. You'll have to ask somebody who's
got more knowledge of that area of the code about that.
o I believe we currently use our own routing algorithm, and/or PNNI
Level 0 (e.g., static routing). I believe "full" PNNI support is
on the list for some release following Version 2.5.
|
| Re: .1
>o I believe we currently use our own routing algorithm, and/or PNNI
> Level 0 (e.g., static routing). I believe "full" PNNI support
> is on the list for some release following Version 2.5.
As far as I understood it, the first PNNI V1.0 implementation will only
support one Peer group.
Pedro
|