I think that ISIS is not an issue here, because you can connect the two spoke sites together using L1/L2 link in ISIS and advertiese L2 routes with large metric, so the link between spokes is not used for L2 traffic, while your link to the hub is up. for L1 route optimal roiting can be achieved without carying traffic through the hub
the basic requirement in any MPLS environment is to have LSPs between PE routers in place. Hence from an MPLS perspective the requirement towards IP routing is that the Loopbacks should not be summarized and exist in the routing table as host routes (/32).
You can achieve f.e. by taking all loopback IPs from a separate IP address block and summarize the only rest. This can be done in OSPF multi (normal) area topologies or in ISIS L1/L2 topologies. In the latter you need "redistribute l2 in l1" command, because ISIS by default only inserts 0.0.0.0/0 from L2 into L1, which would break LSPs.
On the other hand: area size is only limited by memory and CPU load. There are implementations in the real world with nearly 1000 routers in one area (OSPF or ISIS). Those shouldn?t be 836 though ;-)
So multi area can be done, but single area will also scale quite a bit in case carrier class equipment is used.
Question: Have the phone connected and can ring out-but no sound coming from the handset - analog home phone - phone makes connection and pick up at the other end is ok. Can you help?
Question: Have the phone connected and can ring out-but no sound coming from the handset - analog home phone - phone makes connection and pick up at the other end is ok. Can you help?Answer
iPXE boot in ASR9K
This document applies to NCS5500 and ASR9000 routers and has been verified as such.
traditional ECMP or equal cost multipath loadbalances traffic over a number of available paths towards a destination. When one path fails, the traffic gets r...