Alert mgetty: cannot get TIO: Input/output error
after the installation of CUCM 7.1(3) RTMT starts logging the following error from the Publisher node:
At Tue Nov 24 12:27:18 CET 2009 on node x.x.x.x; the following SyslogSeverityMatchFound events generated: SeverityMatch - Alert mgetty: cannot get TIO: Input/output error SeverityMatch - Alert mgetty: cannot get TIO: Input/output error
Re: Alert mgetty: cannot get TIO: Input/output error
mgetty is a application that allows you to connect a console to a serial port and get a login prompt.
This error could be considered as cosmetic, and does not affect the operation of the CUCM.
Possible options for the error:
1. There is a device that should not be connected to the serial port
-> Disconnect that device
2.There is a serial port in the server and it is disabled in the BIOS
-> Enable the serial port in the BIOS
3. There is no serial port in the server and it is enabled in the BIOS
-> Disable the serial port in the BIOS
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...