fuck cisco

[rmd]

so, i put a new card in a 2600. all goes well. i reboot, and a PREVIOUSLY EXISTING AND PROPERLY OPERATING interface loses its ip address and decides to come up in dhcp mode.

GAH! what a stupid fucking failure mode.

i've never seen that before. it took me a while to notice what was going on. it kept looking like some sort of fucked up routing thing on the far end of the WAN link.

it's fixed now. stupid cisco router.

Comments

Wow!

[lyricae.livejournal.com]

I'll show my ignorance by saying that I have no idea what any of that meant...
Sounds bad though. I'm glad you got it solved though. And btw... How the heck are you?! I've been slacking on my journal, so I've not been keeping up with friends the way I should be.

[bikergeek.livejournal.com]

is anyone else thinking about the irony of calling a router a "2600"?

[spazzkat.livejournal.com]

NO SPACE INVADERS FOR YOU!

patronize the competition

[kjc.livejournal.com]

If you can afford it, switch to Juniper.

I could rhapsodize on & on about them, but suffice it to say that they rule! And have none of the failure modes and general pain that you get with Cisco.

(Of course, without Cisco there would be no Juniper, since much of Juniper's philosophy is derived from lessons learned via Cisco's mistakes. But who are we to refuse the bounty of these lessons?)

[rmd.livejournal.com]

yeah, that would be wicked overkill for what we have here. i mean, i'm surrounded by 2600's. they're so cute! tiny little 1U routers!

it's very quaint. :-)

otoh, i love juniper's onboard docs and the 'examine interface' command. very cool.

[loopback.livejournal.com]

What you REALLY need is an F5 Networks Link Controller.