my comments on Bridging and Switching

I browsed the Bridging and Switching part today and I liked what I saw.

The Bridging and Switching would probably catchup with the more verbose explanation style the EIGRP and RIP

sections have, right?.

I have some remarks (after checking what has been made already so not to have redundant remarks)

page 29 Configuration SW2 - I was expecting "switchport nonegotiate" since this is a trunk to a router port

pages 40-43 I see a lot of the same configurations on a individual range of port. I was expecting the "interface range" command.

Next I will actually do the Bridging and Switching tasks.

This thursday I will browse the Frame-Relay Part and do it this Saturday/Sunday

I will be back. 

Comments

  • <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">





    The Briding & Switching section isn't complete, neither is Frame
    Relay. Both will have very detailed breakdowns like IP Routing, RIP,
    and EIGRP.



    > page 29 Configuration SW2 - I was expecting "switchport
    nonegotiate" since this is a trunk to a router port



    You can disable DTP but you don't 100% have to.  The router doesn't
    understand the DTP frames so it will just drop them anyways.  There are
    some production designs, like when you a trunking to a server, that you
    would want to disable DTP to make sure that it doesn't cause a
    negotiation failure.



    > pages 40-43 I see a lot of the same configurations on a individual
    range of port. I was expecting the "interface range" command.



    The configuration is all the same but the verification is not.  The
    solution comes from the show run output, so they're listed individually
    instead of in an interface range.  When you actually configure it the
    easiest way to do it is in a range though.





    HTH,
    Brian McGahan, CCIE #8593 (R&S/SP/Security)
    [email protected]

    Internetwork Expert, Inc.
    http://www.InternetworkExpert.com
    Toll Free: 877-224-8987 x 705
    Outside US: 775-826-4344 x 705
    24/7 Support: http://forum.internetworkexpert.com
    Live Chat: http://www.internetworkexpert.com/chat/



    aza wrote:

    I browsed the Bridging and Switching part today and I liked what I
    saw.

    The Bridging and Switching would probably catchup with the more
    verbose explanation style the EIGRP and RIP

    sections have, right?.

    I have some remarks (after checking what has been made already so
    not to have redundant remarks)

    page 29 Configuration SW2 - I was expecting "switchport
    nonegotiate" since this is a trunk to a router port

    pages 40-43 I see a lot of the same configurations on a individual
    range of port. I was expecting the "interface range" command.

    Next I will actually do the Bridging and Switching tasks.

    This thursday I will browse the Frame-Relay Part and do it this
    Saturday/Sunday

    I will be back. 







    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • Thank you, this certainly helps.

    Now on to the Bridging and Switching tasks :)


    2008/7/14 Brian McGahan :
    > The Briding & Switching section isn't complete, neither is Frame Relay. Both
    > will have very detailed breakdowns like IP Routing, RIP, and EIGRP.
    >
    >> page 29 Configuration SW2 - I was expecting "switchport nonegotiate" since
    >> this is a trunk to a router port
    >
    > You can disable DTP but you don't 100% have to. The router doesn't
    > understand the DTP frames so it will just drop them anyways. There are some
    > production designs, like when you a trunking to a server, that you would
    > want to disable DTP to make sure that it doesn't cause a negotiation
    > failure.
    >
    >> pages 40-43 I see a lot of the same configurations on a individual range
    >> of port. I was expecting the "interface range" command.
    >
    > The configuration is all the same but the verification is not. The solution
    > comes from the show run output, so they're listed individually instead of in
    > an interface range. When you actually configure it the easiest way to do it
    > is in a range though.
    >
    >
    > HTH,
    >
    > Brian McGahan, CCIE #8593 (R&S/SP/Security)
    > [email protected]
    >
    > Internetwork Expert, Inc.
    > http://www.InternetworkExpert.com
    > Toll Free: 877-224-8987 x 705
    > Outside US: 775-826-4344 x 705
    > 24/7 Support: http://forum.internetworkexpert.com
    > Live Chat: http://www.internetworkexpert.com/chat/
    >
    > aza wrote:
    >
    > I browsed the Bridging and Switching part today and I liked what I saw.
    >
    > The Bridging and Switching would probably catchup with the more verbose
    > explanation style the EIGRP and RIP
    >
    > sections have, right?.
    >
    > I have some remarks (after checking what has been made already so not to
    > have redundant remarks)
    >
    > page 29 Configuration SW2 - I was expecting "switchport nonegotiate" since
    > this is a trunk to a router port
    >
    > pages 40-43 I see a lot of the same configurations on a individual range of
    > port. I was expecting the "interface range" command.
    >
    > Next I will actually do the Bridging and Switching tasks.
    >
    > This thursday I will browse the Frame-Relay Part and do it this
    > Saturday/Sunday
    >
    > I will be back.
    >
    >
    > Internetwork Expert - The Industry Leader in CCIE Preparation
    > http://www.internetworkexpert.com
    >
    > Subscription information may be found at:
    > http://www.ieoc.com/forums/ForumSubscriptions.aspx
    >
    >
    >
    > Internetwork Expert - The Industry Leader in CCIE Preparation
    > http://www.internetworkexpert.com
    >
    > Subscription information may be found at:
    > http://www.ieoc.com/forums/ForumSubscriptions.aspx
    >
  • Hi brain

    When will be the complete version available for IE-WB-1 (v-5) ?

    Regards

    Amit Chopra

     

  • I just finished 1.17. These are my comments till now. I will finish the rest by this weekend.

    Bridging and Switching

    Task 1.8 Bullet 5
     "Configure necessary VLAN definitions on SW4 using.." has to be on SW2 for it is the VTP server.

    Task 1.9 bullet 2
    The following is a minor glitch; It is just something temporarily.
     Since "ie.rs.v5.00.hardware.specification" is not yet available a conversion has to be made from ethernet to
     fastethernet when looking at "ie.rs.v4.10.hardware.specification" and "IEWB-RS-VOL-I-V5.Diagrams.1.00" together.
     When "ie.rs.v5.00.hardware.specification" is available both will be referencing to fastethernet interfaces and no
     mental conversion will be necesarry.

    There is 1 part which is not clear to me in Task 1.8 Bullet 2.
     I would expect the following VLANs to be created on SW1: 7,58,67,79,146.
     In the Solution part I also see VLAN 43 created, I don't see why this VLAN needs to be created on SW1.

    Task 1.13, this is more of a note
    For this to work the port channels has to be recreated. If I change the channel mode on the fly from "on" to
    "desirable" the status of the channel will remain "on" and will not change to "desirable". This is at least on
    3750's.

    Task 1.16 802.1q tunneling
    In order for this to work VLAN100 has to be created on SW2 and SW3. Although implied in the output this can be
    made more clear.

    Task 1.17 Etherchannel over 802.1q Tunneling
    Bullet 1; "remove the previous trunking and tunneling configuration"
     This also includes removing Vlan 100 from SW1 and SW4 and removing the subinterface configurations on R1 and R4.
     Probably it would be better to start over with a new initial configuration.

    Regards,

    aza

  • ok, I have just finished up to 1.32

    Here is my feedback

    Task 1.19 STP Load Balancing with Port Cost
        Both bullets; "Sw2 and SW4" this must be "SW2 and SW1"

    Task 1.20 STP Load Balancing with Port Priority
    Port Priority is only checked if the upstream consists of different link to the same BID.
    This prerequisite is not met for SW4 has 3 links with SW3 and 3 links with SW2. These links
    where made during task 1.18 bullet 1 (SW2 & SW4 and SW3 & SW4).
    To make this task work the upstream links from SW4 to SW2 has to be disabled.

    Task 1.25
    If on Rack1SW2 I do "show spanning-tree vlan 10" my root port will be fa1/0/14 and not fa0/21
    as showed in the task solution. I will leave this task for later on for this confuses me.

    Task 1.31
    When rootguard is enabled on the interfaces and loopguard is enabled globally than this will not be
    applied on the interfaces. When the loopguard is enabled on the interfaces directly the rootguard
    applied on the interfaces will be removed and the loopguard will be applied on the interfaces.
    So eventhough the loopguard command can be applied from global mode it will not have effect in this
    particular case. Only the interface command will make loopguard applied to the ports.

     

    Regards,

    aza

  • <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">





    aza,



        I'm posting an update to the document tonight with a lot more
    detailed breakdown information.  I'll go through your questions in
    detail shortly and see if they are resolved by this update.  A note
    will be posted when the new file is available.



    Thanks,



    Brian McGahan, CCIE #8593
    (R&S/SP/Security)

    [email protected]



    Internetwork Expert, Inc.

    http://www.InternetworkExpert.com

    Toll Free: 877-224-8987 x 705

    Outside US: 775-826-4344 x 705

    Online Community: http://www.IEOC.com

    CCIE Blog: http://blog.internetworkexpert.com






    amit chopra wrote:

    Good Update , aza







    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • I have just completed up to task 1.44 and this is my feedback

    Task 1.41
    Bullet 4. Configure SW1 to receive traffic from the RSPAN VLAN..."
    The interface fas1/0/24 (or fas0/24) is already used in another span session (task 1.40).
    The configuration from task 1.40, especially the monitor session NN destination" has to
    be removed in order to be able to complete Task 1.41

    Regards,

    aza

  • To make things easier I have updated the list and leave the opening questions/remarks

    Bridging and Switching

    The physical interface connection table is for 4.1 using ethernet0/0 whilst the new diagram is using fastethernet.

    Task 1.13, this is more of a note
    For this to work the port channels has to be recreated. If I change the channel mode on the fly from "on" to
    "desirable" the status of the channel will remain "on" and will not change to "desirable". This is at least on
    3750's.

    >>> This is not something to fix but could be  clarified a bit more, see my comments

    Task 1.17 Etherchannel over 802.1q Tunneling
    Bullet 1; "remove the previous trunking and tunneling configuration"
     This also includes removing Vlan 100 from SW1 and SW4 and removing the subinterface configurations on R1 and R4.
     Probably it would be better to start over with a new initial configuration.

    >>> This is not something to fix. It would be easier just to erase the configs and start new again.

    Task 1.19 STP Load Balancing with Port Cost
        Both bullets; "Sw2 and SW4" this must be "SW2 and SW1"

    >>> I will check this out again to see if I missed something (probably)

    Task 1.20 STP Load Balancing with Port Priority
    Port Priority is only checked if the upstream consists of different link to the same BID.
    This prerequisite is not met for SW4 has 3 links with SW3 and 3 links with SW2. These links
    where made during task 1.18 bullet 1 (SW2 & SW4 and SW3 & SW4).
    To make this task work the upstream links from SW4 to SW2 has to be disabled.

    >>> I will check this out again to see if I missed something (probably)

    Task 1.31
    When rootguard is enabled on the interfaces and loopguard is enabled globally than this will not be
    applied on the interfaces. When the loopguard is enabled on the interfaces directly the rootguard
    applied on the interfaces will be removed and the loopguard will be applied on the interfaces.
    So eventhough the loopguard command can be applied from global mode it will not have effect in this
    particular case. Only the interface command will make loopguard applied to the ports.

    >>> This is not something to fix but could be  clarified a bit more, see my comments

    Task 1.41
    Bullet 4. Configure SW1 to receive traffic from the RSPAN VLAN..."
    The interface fas1/0/24 (or fas0/24) is already used in another span session (task 1.40).
    The configuration from task 1.40, especially the monitor session NN destination" has to
    be removed in order to be able to complete Task 1.41

    >>> I will check this out again to see if I missed something (probably)

  • It would also be nice to see an example for QinQ with native vlan tagging together with an explanation why, when, what for  this should be used ...

Sign In or Register to comment.