This is a sad story.
We have purchased a Cisco 877 (SEC k9) with IOS 12.4, with the intention of experimenting in a little IPv6 sandbox, for development of some comms software.
I have spent the whole day today establishing that although the 877 appears to support IPv6 (as per the Cisco website), the Cisco SDM doesn't AT ALL.
Putting to one side the wisdom of shipping a device that purports to support IPv6 but has no way of configuring that support, and having banged my head against the wall repeatedly and sworn to never, ever purchase any Cisco product ever again, I'm now left with my only recourse being the IOS console. Yes, in order to work with the latest and greatest in internet protocols, I have to descend into the stygian gloom of the technological dark ages... the serial interface. Lucky me that my PC even HAS one of these things.
So after much searching, I see that I need to issue the command
ipv6 unicast-routing
to this dinosaur of a device, at a very minimum. So I grab a copy of Hypertrm from an old XP machine and fire it up. Bear in mind this is a router already configured by SDM. It is not connected to anything other than my two test machines, and it's definitely not connected either to the corporate net or the Internet (we only bought a DSL router so it could get repurposed later once I've finished playing with it).
I can log in using the username and password I configured earlier on SDM... but then I get dropped at a
yourname#
prompt, with no idea what might be a valid input. This prompt is tangentially mentioned in the Cisco startup guide, as appearing once you've entered the enable command :
yourname> enable yourname#
but I can't enter ANYTHING that the router will recognise - it appears to be trying to resolve anything I enter as a machine name. But since this router isn't connected to anything resembling a DNS server, that isn't likely to succeed. Any attempt to enter a command produces an "invalid input" error. I tried ipv6, I even tried enable.... nothing works.
Doesanyone have a clue what's going on here? Or how I might reverse out of this ghastly situation ?
-- Bob Moore