Rogueone
11-12-2007, 02:29 PM
Hi,
I had to fudge the network build in ch 6 as NetVis 5 doesn't have the requisite routers. So I built a network of 6 2600's, with 2 of them playing Corp with a FE connection between them.
I just finished the EIGRP setup, and am NOT getting load balancing across 10.1.2.0 and 10.1.3.0 to my Corp A (initially I had R1 split between my Corp A and B, and so I moved it to try the next step with the bundling)
After getting s0/0 setup as 10.1.3.1, it's the only EIGRP route in my routing table. 10.1.2.2 isn't showing up as an option. They both have the same clock rate, so any thoughts on why this isn't working?
Also, when I try to bundle, I get an error that 10.1.2.0 overlaps with s0/1 and it won't allow me to make them both in the same subnet. Is this a 2600 limitation, a NV5 limitation, a non ISR one, etc.??
I just shut down 10.1.3.2 and sho ip route shows 10.1.2.1 routes, then when I brought 10.1.3.2 back up, the table switches back to the 10.1.3.1 route, and the 10.1.2.1 route is gone. Any thoughts? I'm hoping this is a snaffu in the software that NV6 is going to fix???
thanks,
James
I had to fudge the network build in ch 6 as NetVis 5 doesn't have the requisite routers. So I built a network of 6 2600's, with 2 of them playing Corp with a FE connection between them.
I just finished the EIGRP setup, and am NOT getting load balancing across 10.1.2.0 and 10.1.3.0 to my Corp A (initially I had R1 split between my Corp A and B, and so I moved it to try the next step with the bundling)
After getting s0/0 setup as 10.1.3.1, it's the only EIGRP route in my routing table. 10.1.2.2 isn't showing up as an option. They both have the same clock rate, so any thoughts on why this isn't working?
Also, when I try to bundle, I get an error that 10.1.2.0 overlaps with s0/1 and it won't allow me to make them both in the same subnet. Is this a 2600 limitation, a NV5 limitation, a non ISR one, etc.??
I just shut down 10.1.3.2 and sho ip route shows 10.1.2.1 routes, then when I brought 10.1.3.2 back up, the table switches back to the 10.1.3.1 route, and the 10.1.2.1 route is gone. Any thoughts? I'm hoping this is a snaffu in the software that NV6 is going to fix???
thanks,
James