transport input cli only applies to a specific line of the router, aux or
console ports are out-of-bands, and are definitely not an async/tty line,
INMHO
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=35015t=34996
--
FAQ,
Does anyone know the affect of entering 'transport input none' on the
console line? Many of the IPExpert labs show it in their answer keys, but
niether they, not Cisco really explains why. (That I can find.) Cisco shows
it in many of their show run examples everywhere - with no explanation.
transport input none prevents any protocol selection on the line. This
makes the port unusable by incoming connections
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=34997t=34996
--
FAQ, list archives, and subscription info:
That makes it sound like I would make the console port useable, but that it
not what happens. I know that it will stop all traffic when applied to the
async lines, but I don't see any effect on the console port or the aux port.
somera cecilia wrote in message
[EMAIL PROTECTED]">news:[EMAIL
4 matches
Mail list logo