Hi,
I can only agree to Dave. I don't like checking the conf registers and the IOS version. Shouldn't be a big problem. PL has such cool features. So, the basics should work too.

Cheers
Simon

Am 08.06.2009 um 18:29 schrieb ccie_security- [email protected]:

Send CCIE_Security mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://onlinestudylist.com/mailman/listinfo/ccie_security
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CCIE_Security digest..."


Today's Topics:

  1. Re: Lab 1B (Dave Craddock)
  2. Re: CCIE_Security Digest, Vol 36, Issue 9 (Paul Stewart)


----------------------------------------------------------------------

Message: 1
Date: Mon, 8 Jun 2009 17:14:22 +0100
From: "Dave Craddock" <[email protected]>
Subject: Re: [OSL | CCIE_Security] Lab 1B
To: "Stuart Hare" <[email protected]>, "Johan Bornman"
        <[email protected]>
Cc: OSL Lab Exam <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Hi Stu

As part of the init config can?t you add the correct flash file and then either get the script to reload it or as part of the process have the client reload before they start.



It?s got to be better to have the systems setup correctly so that time can be spent on study not trying to figure out what IOS it should load for what rack.



Just my 2 cent



Dave







From: [email protected] [mailto:[email protected] ] On Behalf Of Stuart Hare
Sent: 08 June 2009 17:20
To: Johan Bornman
Cc: OSL Lab Exam
Subject: Re: [OSL | CCIE_Security] Lab 1B



Do a dir flash on the device usually on proctorlabs there are are 2 code versions 12.4 22 T and 12.4 3T.



Check your config register to ensure it's set correctly the issue the boot system flash <image filename> and then reload the device.



As rack 1 is shared between the r&s and security pods it's pot luck with who used it last I suppose.



Generally it's worth a quick check prior to loading the cfgs.



Stu

Sent from my iPhone


On 8 Jun 2009, at 17:02, "Johan Bornman" <[email protected]> wrote:

        Checked 1st router and I am on Version 12.4(13r)T

        2nd Router Version 12.4(1r) [hqluong 1r]

        3rd Router Version 12.4(1r) [hqluong 1r]

How do I get the correct code if that is the problem? I don?t think I have control over that.

        

I was hoping that the initial uploads will be fine so that I can spend maximum time working through the labs.

Having to check that the devices have uploaded correctly is very frustrating as I wouldn?t know what is right and wrong.

        

        From: Stuart Hare [mailto:[email protected]]
        Sent: 08 June 2009 17:15
        To: Brandon Carroll
        Cc: Johan Bornman; OSL Lab Exam
        Subject: Re: [OSL | CCIE_Security] Lab 1B

        

The main issue with the load configs is the dual code versions on the routers so to provide r&s and sec support. Have u made sure your on 12.4 22 T code on the routers.

        

My issues with initial configs have always been down to the wrong ios running.

        

Even if you do use load cfgs always make sure the first thing u do is confirm l2 / l3 is all correct, all vlans exist ips are reachable etc.

        
        Sent from my iPhone

        
On 8 Jun 2009, at 16:02, Brandon Carroll <[email protected]> wrote:

                Did you load the initial configs?

On Mon, Jun 8, 2009 at 7:53 AM, Johan Bornman <[email protected]> wrote:

                I am busy with Lab1B.

                

I am following the proctor guide, every command as per the guide. The results of the commands in the proctor guide compared to what I have running on the devices are very different. Is this an initial upload problem, is the guide not up to date? I have reverted the pod 2 times now and reloaded the initial config 3 times.

                

                1 Example

                On page 51 of the proctor guide I am running:

                My result:

                Sw3(config-if)#do sh int trunk

                

Port Mode Encapsulation Status Native vlan

                Fa0/5       on               802.1q         trunking      1

                Fa0/10      on               802.1q         trunking      24

                Fa0/23      on               802.1q         trunking      1

                Fa0/24      on               802.1q         trunking      1

                

                Port        Vlans allowed on trunk

                Fa0/5       2,10

                Fa0/10      1-4094

                Fa0/23      1-4094

                Fa0/24      1-4094

                

                Port        Vlans allowed and active in management domain

                Fa0/5       2

                Fa0/10      1-2,24,99

                Fa0/23      1-2,24,99

                Fa0/24      1-2,24,99

                

                Port        Vlans in spanning tree forwarding state and not 
pruned

                Fa0/5       2

                

                Port        Vlans in spanning tree forwarding state and not 
pruned

                Fa0/10      1-2,24,99

                Fa0/23      1-2,24,99

                Fa0/24      none

                

                The above is different from what is on page 51.

                

None of the tasks/verifications/ping commands in this lab has the same result as per the proctor guide.

                

                Can somebody from IPExpert assist?

                

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://onlinestudylist.com/pipermail/ccie_security/attachments/20090608/85739125/attachment-0001.htm

------------------------------

Message: 2
Date: Mon, 8 Jun 2009 12:29:27 -0400
From: Paul Stewart <[email protected]>
Subject: Re: [OSL | CCIE_Security] CCIE_Security Digest, Vol 36, Issue
        9
To: "[email protected]"
        <[email protected]>
Cc: "[email protected]"
        <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain;       charset=us-ascii;       format=flowed;  
delsp=yes

Do a show flash.  Then use the boot command to point to the correct
version and reboot.  If there is a boot system command that points to
the wrong one remove it.  I agree it is frustrating, but good to check
since it could happen in the real lab.

Sent from my iPhone



On Jun 8, 2009, at 12:20 PM, [email protected]
wrote:

Send CCIE_Security mailing list submissions to
  [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
  http://onlinestudylist.com/mailman/listinfo/ccie_security
or, via email, send a message with subject or body 'help' to
  [email protected]

You can reach the person managing the list at
  [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CCIE_Security digest..."


Today's Topics:

 1. Re: Lab 1B (Johan Bornman)
 2. Re: Lab 1B (Stuart Hare)


----------------------------------------------------------------------

Message: 1
Date: Mon, 8 Jun 2009 18:02:48 +0200
From: "Johan Bornman" <[email protected]>
Subject: Re: [OSL | CCIE_Security] Lab 1B
To: "'Stuart Hare'" <[email protected]>,    "'Brandon
Carroll'"
  <[email protected]>
Cc: 'OSL Lab Exam' <[email protected]>
Message-ID:
  <!&!
AAAAAAAAAAAYAAAAAAAAALwmcazjsqxKumHgdhyllRfCgAAAEAAAADaHRHGtnlhEllxTuG +
[email protected]>

Content-Type: text/plain; charset="us-ascii"

Checked 1st router and I am on Version 12.4(13r)T

2nd Router Version 12.4(1r) [hqluong 1r]

3rd Router Version 12.4(1r) [hqluong 1r]

How do I get the correct code if that is the problem? I don't think
I have
control over that.



I was hoping that the initial uploads will be fine so that I can spend
maximum time working through the labs.

Having to check that the devices have uploaded correctly is very
frustrating
as I wouldn't know what is right and wrong.



From: Stuart Hare [mailto:[email protected]]
Sent: 08 June 2009 17:15
To: Brandon Carroll
Cc: Johan Bornman; OSL Lab Exam
Subject: Re: [OSL | CCIE_Security] Lab 1B



The main issue with the load configs is the dual code versions on the
routers so to provide r&s and sec support. Have u made sure your on
12.4 22
T code on the routers.



My issues with initial configs have always been down to the wrong ios
running.



Even if you do use load cfgs always make sure the first thing u do is
confirm l2 / l3 is all correct, all vlans exist ips are reachable etc.


Sent from my iPhone


On 8 Jun 2009, at 16:02, Brandon Carroll <[email protected]>
wrote:

Did you load the initial configs?

On Mon, Jun 8, 2009 at 7:53 AM, Johan Bornman <[email protected]> wrote:

I am busy with Lab1B.



I am following the proctor guide, every command as per the guide. The
results of the commands in the proctor guide compared to what I have
running
on the devices are very different. Is this an initial upload
problem, is the
guide not up to date? I have reverted the pod 2 times now and
reloaded the
initial config 3 times.



1 Example

On page 51 of the proctor guide I am running:

My result:

Sw3(config-if)#do sh int trunk



Port        Mode             Encapsulation  Status        Native vlan

Fa0/5       on               802.1q         trunking      1

Fa0/10      on               802.1q         trunking      24

Fa0/23      on               802.1q         trunking      1

Fa0/24      on               802.1q         trunking      1



Port        Vlans allowed on trunk

Fa0/5       2,10

Fa0/10      1-4094

Fa0/23      1-4094

Fa0/24      1-4094



Port        Vlans allowed and active in management domain

Fa0/5       2

Fa0/10      1-2,24,99

Fa0/23      1-2,24,99

Fa0/24      1-2,24,99



Port        Vlans in spanning tree forwarding state and not pruned

Fa0/5       2



Port        Vlans in spanning tree forwarding state and not pruned

Fa0/10      1-2,24,99

Fa0/23      1-2,24,99

Fa0/24      none



The above is different from what is on page 51.



None of the tasks/verifications/ping commands in this lab has the same
result as per the proctor guide.



Can somebody from IPExpert assist?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://onlinestudylist.com/pipermail/ccie_security/attachments/20090608/8e44762a/attachment-0001.htm

------------------------------

Message: 2
Date: Mon, 8 Jun 2009 17:19:47 +0100
From: Stuart Hare <[email protected]>
Subject: Re: [OSL | CCIE_Security] Lab 1B
To: Johan Bornman <[email protected]>
Cc: OSL Lab Exam <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Do a dir flash on the device usually on proctorlabs there are are 2
code versions 12.4 22 T and 12.4 3T.

Check your config register to ensure it's set correctly the issue the
boot system flash <image filename> and then reload the device.

As rack 1 is shared between the r&s and security pods it's pot luck
with who used it last I suppose.

Generally it's worth a quick check prior to loading the cfgs.

Stu

Sent from my iPhone

On 8 Jun 2009, at 17:02, "Johan Bornman" <[email protected]> wrote:

Checked 1st router and I am on Version 12.4(13r)T

2nd Router Version 12.4(1r) [hqluong 1r]

3rd Router Version 12.4(1r) [hqluong 1r]

How do I get the correct code if that is the problem? I don?t think
I have control over that.



I was hoping that the initial uploads will be fine so that I can
spend maximum time working through the labs.

Having to check that the devices have uploaded correctly is very
frustrating as I wouldn?t know what is right and wrong.



From: Stuart Hare [mailto:[email protected]]
Sent: 08 June 2009 17:15
To: Brandon Carroll
Cc: Johan Bornman; OSL Lab Exam
Subject: Re: [OSL | CCIE_Security] Lab 1B



The main issue with the load configs is the dual code versions on
the routers so to provide r&s and sec support. Have u made sure your
on 12.4 22 T code on the routers.



My issues with initial configs have always been down to the wrong
ios running.



Even if you do use load cfgs always make sure the first thing u do
is confirm l2 / l3 is all correct, all vlans exist ips are reachable
etc.


Sent from my iPhone


On 8 Jun 2009, at 16:02, Brandon Carroll
<[email protected]> wrote:

Did you load the initial configs?

On Mon, Jun 8, 2009 at 7:53 AM, Johan Bornman <[email protected]>
wrote:

I am busy with Lab1B.



I am following the proctor guide, every command as per the guide.
The results of the commands in the proctor guide compared to what I
have running on the devices are very different. Is this an initial
upload problem, is the guide not up to date? I have reverted the pod
2 times now and reloaded the initial config 3 times.



1 Example

On page 51 of the proctor guide I am running:

My result:

Sw3(config-if)#do sh int trunk



Port Mode Encapsulation Status Native vlan

Fa0/5       on               802.1q         trunking      1

Fa0/10      on               802.1q         trunking      24

Fa0/23      on               802.1q         trunking      1

Fa0/24      on               802.1q         trunking      1



Port        Vlans allowed on trunk

Fa0/5       2,10

Fa0/10      1-4094

Fa0/23      1-4094

Fa0/24      1-4094



Port        Vlans allowed and active in management domain

Fa0/5       2

Fa0/10      1-2,24,99

Fa0/23      1-2,24,99

Fa0/24      1-2,24,99



Port        Vlans in spanning tree forwarding state and not pruned

Fa0/5       2



Port        Vlans in spanning tree forwarding state and not pruned

Fa0/10      1-2,24,99

Fa0/23      1-2,24,99

Fa0/24      none



The above is different from what is on page 51.



None of the tasks/verifications/ping commands in this lab has the
same result as per the proctor guide.



Can somebody from IPExpert assist?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://onlinestudylist.com/pipermail/ccie_security/attachments/20090608/b38ad99c/attachment.htm

End of CCIE_Security Digest, Vol 36, Issue 9
********************************************


End of CCIE_Security Digest, Vol 36, Issue 10
*********************************************

Reply via email to