console-relay: Checking VTY access:

[pedrosanmartin]

On a switch model C9300L-48UXG-4X with Firmware version 17.03.03. When looking at the log, 8 messages appear every second with the title "[console-relay] Checking VTY access:" 

I have searched the internet and I didn't found a reference to this type of message. Can someone tell me what it means?

Thanks in advance,

PSB

[balaji.bandi]

you see some logs like, how is you logging config

You do see some message like below :

[console-relay] Checking VTY access: addr(0xAC142C40) tableid(0) liin_tableid(266)

post output :

show logging

[pedrosanmartin]

The message that appears is similar to that:

120101: Nov 22 12:23:44.021 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120102: Nov 22 12:23:44.022 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120103: Nov 22 12:26:44.071 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120104: Nov 22 12:26:44.072 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120105: Nov 22 12:29:44.118 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120106: Nov 22 12:29:44.119 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120107: Nov 22 12:32:44.170 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120108: Nov 22 12:32:44.172 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)

What it means?

[pedrosanmartin]

The message that appears is similar to that:

120101: Nov 22 12:23:44.021 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120102: Nov 22 12:23:44.022 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120103: Nov 22 12:26:44.071 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120104: Nov 22 12:26:44.072 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120105: Nov 22 12:29:44.118 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120106: Nov 22 12:29:44.119 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120107: Nov 22 12:32:44.170 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)
120108: Nov 22 12:32:44.172 UTC: [console-relay] Checking VTY access: addr(0xA140108) tableid(0) liin_tableid(266)

What it means?

[balaji.bandi]

this is related to your VTY login

[pedrosanmartin]

But what does addr(0xA140108) tableid(0) liin_tableid(266) mean?
Or how can I locate the device that is generating these connection attempts?

[MHM Cisco World]

161.68.16.8= addr(0xA140108) <<- are you use this public IP ??

[pedrosanmartin]

No, I have never seen that IP
How did you convert the number (0xA140108) to the IP?

[MHM Cisco World]

this hexa I first convert it to binary and then divide binary to parts 
each parts have 8 bits 
then convert bits to decimal.

but if you connect via console why VTY log appear? 

[balaji.bandi · Accepted solution]

what @MHM Cisco World  provided information correct -addr(0xAC142C40) - this my proviate IP address where i try to login to device .

in your case 10.20.1.8  ( find out the IP try to login)

use below tool to convert :

https://www.browserling.com/tools/hex-to-ip

[diptiranjan]

Hi, please check if debugging is enabled by entering 'show debug'. If you find it enabled, please execute either 'undebug all' or 'no debug platform software console-relay' commands to disable it.

[pedrosanmartin]

@balaji.bandi and @MHM Cisco World  Thank you for your help and answers

[MHM Cisco World]

You are so so welcome friend

[Rich R]

Old thread but I just encountered this issue so updating with the answer - it's a bug https://bst.cisco.com/bugsearch/bug/CSCvx78163 which Cisco are clearly not in a hurry to fix because it's been open for 3 years even though there are 19 customer cases attached to it!
The "workaround" is "undebug all" every time it happens <smile>