How do I disable console messages?

[49merc]

I know I saw this command documented somewhere but I haven't been able to find it after scouring my books.

When I'm sitting at the console doing configs and I don't want to see all the messages that keep bubbling up because they really screw up my syntax.

What is the command to disable console messages? I know I read it in the Sybex CCNA book but it was just a sidebar and can't find it even when I search through the PDF.

thanks,
-AR

 

[SoyGalesa]

conf t
no logging console

that should do it.

 

[tbilan]

I think I have a better solution for you. If you're on the console and all those darn messages keep screwing up your typing use the logging sync command on console line. This will keep those commands from screwing up what you're typing. I think it should be on by default.

line con 0
logging synchronous

Tom Bilan
TJBA, Inc.
CCNP, CCDP, MCSE & CNE

 

[BuckWeet]

agreed, i always do that myself.. if not turn off loggin all together..


BuckWeet

 

[49merc]

Thanks to all. This is exactly what I was looking for.

AR
CCNA, MSCE

 

[Normskin]

Hi...I couldn't help interpreting your email as asking how you stopped mesage appearing on you console. The best to do that...without having to stop logging is :-

Terminal no monitor.

Even if messages are generated you shouldn't see them.

Normskin..

 

[tbilan]

You can't 'term no mon' the console port, only a vty port. It will give you an error if you try.
Tom Bilan
TJBA, Inc.
CCNP, CCDP, MCSE & CNE

 

[Normskin]

Hi tbilan ..Yes you can..

BlackCisco#term no mon
BlackCisco#term no monitor
BlackCisco#sh u
Line User Host(s) Idle Location
* 0 con 0 idle 00:00:00

Interface User Mode Idle Peer Address

BlackCisco#

Practice a bit more..

Normskin.

 

[ChrisAC]

I think the point is that "term no monitor" is for turning off logging to the VTY lines. The original question was about the console port, hence "no logging console".

Chris.
**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[tbilan]

I practiced a bit more and to my amazement term no mon still doesn't stop the console messages. It may take the command but it doesn't stop logging to the console. No logging console does stop this, as suggested earlier in the thread.

Here's my practicing:

MOR02#term no mon
4w3d: BGP: Performing BGP general scanning
4w3d: BGP(0): scanning IPv4 Unicast routing tables
4w3d: BGP(IPv4 Unicast): Performing BGP Nexthop scanning for general scan
4w3d: BGP(1): scanning IPv6 Unicast routing tables
4w3d: BGP(IPv6 Unicast): Performing BGP Nexthop scanning for general scan
4w3d: BGP(2): scanning VPNv4 Unicast routing tables
4w3d: BGP(VPNv4 Unicast): Performing BGP Nexthop scanning for general scan
4w3d: BGP(3): scanning IPv4 Multicast routing tables
4w3d: BGP(IPv4 Multicast): Performing BGP Nexthop scanning for general scan
MOR02#show u
Line User Host(s) Idle Location
* 0 con 0 idle 00:00:00

Interface User Mode Idle Peer Address

MOR02#
4w3d: BGP: Import timer expired. Walking from 1 to 1
4w3d: BGP: Import timer expired. Walking from 1 to 1
4w3d: BGP: Import timer expired. Walking from 1 to 1

I guess this is enough practicing for now.

Tom Bilan
TJBA, Inc.
CCNP, CCDP, MCSE & CNE

 

[tbilan]

I was wrong about the error message though, it gives you that error when you 'term mon' saying '% Console already monitors'.

Tom Bilan
TJBA, Inc.
CCNP, CCDP, MCSE & CNE

 

[Normskin]

Your NOT wrong....but you were half right...Practice helped me as well..

Normskin.

 

[vammu]

Try,

router(config)#no logging console ?
<0-7> Logging severity level
alerts Immediate action needed (severity=1)
critical Critical conditions (severity=2)
debugging Debugging messages (severity=7)
emergencies System is unusable (severity=0)
errors Error conditions (severity=3)
guaranteed Guarantee console messages
informational Informational messages (severity=6)
notifications Normal but significant conditions (severity=5)
warnings Warning conditions (severity=4)
<cr>