OOB on the C classe cisco server

Started by icecream-guy, June 09, 2015, 11:10:28 AM

Previous topic - Next topic

icecream-guy

so I have setup OOB access to the console port on a Cisco C220M3,  the other side of the connection is connected to a HWIC-16A. in a 3925, the line connections are standard.   So when I reboot my server, there are a number of function key options across the top of the screen while booting, seems that none of my function keys are working via OOB so I can't get into any. Press <F2> Setup, <F6> Boot Menu, <F7> Diagnostics, <F8> CIMC Config, <F12> Network Boot

is there a way to get the function keys working via the terminal server?  works just fine when consoled in locally.

:professorcat:

My Moral Fibers have been cut.

icecream-guy

maybe it something with my terminal program secureCRT where I can remap a key?
:professorcat:

My Moral Fibers have been cut.

icecream-guy

I'm getting bounce back from the customer,  doesn't want me to configure CIMC, "we haven't used it in three years. why do we need it now"......... under my breath,  (yeah, you haven't used it, because you haven't upgraded in three years)... :wall: :wall:
:professorcat:

My Moral Fibers have been cut.

deanwebb

A remap *should* work, but now your issue is managerial, not technical.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

icecream-guy

CIMC's lack of two factor authentication, even though AD and LDAP integration is supported, killed the project.
:professorcat:

My Moral Fibers have been cut.

NetworkGroover

Quote from: ristau5741 on June 11, 2015, 02:22:52 PM
CIMC's lack of two factor authentication, even though AD and LDAP integration is supported, killed the project.

The dreaded 2FA....
Engineer by day, DJ by night, family first always

wintermute000

why the heck would you need two factor? Surely the OOB network should be secured (if necessary, with two factor there)? Or is this some military type spec

NetworkGroover

Quote from: wintermute000 on June 11, 2015, 07:02:00 PM
why the heck would you need two factor? Surely the OOB network should be secured (if necessary, with two factor there)? Or is this some military type spec

Guessing DoD.
Engineer by day, DJ by night, family first always

icecream-guy

Quote from: wintermute000 on June 11, 2015, 07:02:00 PM
why the heck would you need two factor? Surely the OOB network should be secured (if necessary, with two factor there)? Or is this some military type spec

government mandate. :(

so if your server is running ACS on top of the server as the application, and if you could configure 2-factor on the CIMC to authenticate into the OOB CIMC management interface, surely you are not going to use the same ACS server as your authentication point...

Does ACS support two-factor authentication for administration of the ACS server, or must one use a local account.  Where would you point for your external authentication server?????  I suppose one would point to another HA pair of ACS servers that are a separate entity,  then on those one would configure an external authentication server that points back to the first set of ACS servers for two-factor authentication there.

:professorcat:

My Moral Fibers have been cut.