From: Yurchenko, Michael (michael.yurchenko@xxxxxxxxxxx)
Date: Mon Dec 25 2000 - 01:02:41 GMT-3
Hello,
I also add
service timestamps log date ms
service timestamps deb date ms
no logging console
-----Original Message-----
From: Facundo Musante
To: Chuck Larrieu; CCIE_Lab Groupstudy List
Sent: 12/24/00 12:48 AM
Subject: RE: Lab Practice - habits for success
Hi Chuck,
Thanks for your input. I use a script of standards commands very
similar to
what you described. I also include "logging synch" under line con 0
(probably is a good idea to put it on every line).
Rgds,
FM
PS:For those of you who are not familiar with this command, this is the
command description from the CD
logging synchronous
To synchronize unsolicited messages and debug output with solicited
Cisco
IOS software output and prompts for a specific console port line,
auxiliary
port line, or
virtual terminal line, use the logging synchronous line configuration
command. Use the no form of this command to disable synchronization of
unsolicited messages
and debug output.
logging synchronous [level severity-level | all] [limit
number-of-buffers]
no logging synchronous [level severity-level | all] [limit
number-of-buffers]
Syntax Description
level severity-level
(Optional) Specifies the message severity level.
Messages with a severity level equal to or higher than this value are
printed
asynchronously. Low numbers indicate greater
severity and high numbers indicate lesser severity. The default value is
2.
all
(Optional) Specifies that all messages are
printed
asynchronously, regardless of the severity level.
limit number-of-buffers
(Optional) Specifies the number of buffers to be
queued for the terminal after which new messages are dropped. The
default
value
is 20.
Defaults
This feature is turned off by default.
If you do not specify a severity level, the default value of 2 is
assumed.
If you do not specify the maximum number of buffers to be queued, the
default value of 20 is assumed.
Command Modes
Line configuration
Command History
Release
Modification
10.0
This command was introduced.
Usage Guidelines
When synchronous logging of unsolicited messages and debug output is
turned
on, unsolicited Cisco IOS software output is displayed on the console or
printed after
solicited Cisco IOS software output is displayed or printed. Unsolicited
messages and debug output is displayed on the console after the prompt
for
user input is
returned. This is to keep unsolicited messages and debug output from
being
interspersed with solicited software output and prompts. After the
unsolicited messages
are displayed, the console displays the user prompt again.
When specifying a severity level number, consider that for the logging
system, low numbers indicate greater severity and high numbers indicate
lesser severity.
When a message-queue limit of a terminal line is reached, new messages
are
dropped from the line, although these messages might be displayed on
other
lines. If
messages are dropped, the notice "%SYS-3-MSGLOST number-of-messages due
to
overflow" follows any messages that are displayed. This notice is
displayed
only on the terminal that lost the messages. It is not sent to any other
lines, any logging servers, or the logging buffer.
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Chuck Larrieu
> Sent: Saturday, December 23, 2000 11:24 PM
> To: CCIE_Lab Groupstudy List
> Subject: Lab Practice - habits for success
>
>
> Having spoken to several CCIE's about the lab, having collected a
> number of
> e-mails containing lab strategy from CCIE's, I am convinced that one
major
> component of the CCIE Lab is time management. It is about putting
first
> things first, leaving one room to research what one doesn't
immediately
> know.
>
> That said, one important part of my study and practice is my
> routine. These
> are things I do every time I sit down to do anything that involves the
> actual configuration of routers.
>
> 1) Write a short note about the work to be done. What I hope to
> show. What I
> am investigating. This will come in handy for later review.
>
> 2) Draw a diagram. Lay out the logical network diagram in a manner
that
> facilitates all of the following steps.
>
> 3) On the diagram, label all interfaces. Note which serial interfaces
are
> DCE, if applicable. It continues to surprise me how easily I overlook
> something as simple as applying the clockrate appropriately.
>
> 4) Fill in the IP addressing scheme for each interface
>
> 5) Note the routing protocol to be involved
>
> 6) Note extra virtual interfaces, such as tunnels, to one side. Use a
> notation that facilitates quick visuals and pneumonics to associate
those
> virtual interfaces with their physical counterparts
>
> 7) Open notepad, and create the file containing the standard commands
that
> will appear on all routers. Refer to the separate note below.
>
> 8) When all of this has been completed, only then attach to the
> routers and
> begin the work. This should be true for quick and dirty checks of
> things as
> well as for complex exercises.
>
> 9) Always, one should follow a predictable pattern of work. For me,
this
> means cutting and pasting the standard commands into each router, and
then
> going through my documentation / configuration matrix and configuring
all
> layer two, and layer three address, along with the basic routing
process
> configurations.
>
> 10) Check the show run, and the IP routing table at this point
>
> 11) Move on to the next router, and repeat steps 8,9, and 10
>
>
> At this point in time, I have the following as my standard
> commands. I type
> from scratch in notepad, and cut and paste into each router. I watch
> carefully for indications of types. If I see an error, I check, and
then
> rewrite the notepad configuration where necessary.
>
> no ip domain-lookup
> ip subnet-zero
> ip classless
> ip tcp synwait-time 7 ( the no ip domain-lookup probably renders this
one
> unnecessary, but it can't hurt! )
> line con 0
> exec-timeout 0 0
> privilege level 15
> line vty 0 4
> password [whatever my chosen password is]
> login
> exec-timeout 0 0
> privilege level 15
> line aux 0 ( may be unnecessary on all lines,
but
> again, it can't hurt )
> exec-timeout 0 0
> privilege level 15
> exit
> hostname
>
> at this point I can enter an appropriate hostname, and get on
> with my layer
> two and layer three configurations
>
> I'm offering this as one way of augmenting one's practice. Comments
are
> certainly welcome.
>
> Chuck
> ----------------------
> I am Locutus, a CCIE Lab Proctor. Xx_Brain_dumps_xX are futile.
> Your life as
> it has been is over ( if you hope to pass ) From this time
> forward, you will
> study US!
> ( apologies to the folks at Star Trek TNG )
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:10 GMT-3