• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't ping a chassis over a T1 bundle.

jlazzaro

Golden Member
heres the scenario:

3845 ------- ( t1 multilink bundle ) ------- 2811 ------- 4506 -- 75 Remote PC's

3845 / 2811 both have static routes. 4506 is just acting as a switch with a basic config, vlan1 has an ip.

as of now, i can ping the 2811 and all the remote computers from the 3845 and vice versa. however, i cannot ping or telnet the 4506 from the 3845. i can ping and telnet the 4506 from the 2811 just fine.

what am i missing here?!?


 
Originally posted by: jlazzaro
heres the scenario:

3845 ------- ( t1 multilink bundle ) ------- 2811 ------- 4506 -- 75 Remote PC's

3845 / 2811 both have static routes. 4506 is just acting as a switch with a basic config, vlan1 has an ip.

as of now, i can ping the 2811 and all the remote computers from the 3845 and vice versa. however, i cannot ping or telnet the 4506 from the 3845. i can ping and telnet the 4506 from the 2811 just fine.

what am i missing here?!?

If you can provide sanitized configs of all three, I'm sure I'll spot it within a minute or two of reception. PM if necessary.
 
Originally posted by: spidey07
Default gateway on 4500?
had a default-gateway on the 4506 for the 2811 fa0/0 interface (76.1).

once i added a static route to the 4506 for that address, it seemed to start working.

is this because ip routing is enabled by default therefore it disregards the default gateway command?
 
Originally posted by: jlazzaro
Originally posted by: spidey07
Default gateway on 4500?
had a default-gateway on the 4506 for the 2811 fa0/0 interface (76.1).

once i added a static route to the 4506 for that address, it seemed to start working.

is this because ip routing is enabled by default therefore it disregards the default gateway command?

bingo. If you're doing routing you need a true default route 0/0.
 
Originally posted by: spidey07
Originally posted by: jlazzaro
had a default-gateway on the 4506 for the 2811 fa0/0 interface (76.1).

once i added a static route to the 4506 for that address, it seemed to start working.

is this because ip routing is enabled by default therefore it disregards the default gateway command?

bingo. If you're doing routing you need a true default route 0/0.

I'll second that. Caught myself in one of those many years ago when working on an AS from remote -- thank god for reload in 5. 😉
 
Back
Top