Comments for CCIE, the beginning! http://cciethebeginning.wordpress.com Mon, 26 Oct 2009 07:40:46 +0000 http://wordpress.com/ hourly 1 Comment on Manual IPv6 GRE tunnel over IPv4 by honor http://cciethebeginning.wordpress.com/2008/07/03/manual-ipv6-gre-tunnel-over-ipv4/#comment-172 honor Mon, 26 Oct 2009 07:40:46 +0000 http://cciethebeginning.wordpress.com/2008/07/03/manual-ipv6-gre-tunnel-over-ipv4/#comment-172 I welcome warmly. Whether at you it is possible to put the ipv 6 tunnel on, if this way very much I asked it. I would like to establish a few addresses on IRCnet, if it's possible. I am greeting and I am waiting for the write-off. I welcome warmly. Whether at you it is possible to put the ipv 6 tunnel on, if this way very much I asked it. I would like to establish a few addresses on IRCnet, if it’s possible. I am greeting and I am waiting for the write-off.

]]> Comment on GRE (Generic Routing Encapsulation) : Point-to-point & multipoint GRE by shivlu jain http://cciethebeginning.wordpress.com/2008/06/29/gre-generic-routing-encapsulation-point-to-point-multipoint-gre/#comment-171 shivlu jain Fri, 25 Sep 2009 15:18:48 +0000 http://cciethebeginning.wordpress.com/2008/06/29/gre-generic-routing-encapsulation-point-to-point-multipoint-gre/#comment-171 The explanation is really wonderful. The explanation is really wonderful.

]]> Comment on About by Jim http://cciethebeginning.wordpress.com/about/#comment-170 Jim Wed, 26 Aug 2009 01:15:33 +0000 #comment-170 Excellent write-ups, this is the same concept of how I achieved my CCIE but I did my write-ups in word. Good luck. Excellent write-ups, this is the same concept of how I achieved my CCIE but I did my write-ups in word. Good luck.

]]> Comment on Multicast over FR NBMA part3 – (PIM-NBMA mode and Auto-RP) by cciethebeginning http://cciethebeginning.wordpress.com/2008/07/31/multicast-over-fr-nbma-part3-%e2%80%93-pim-nbma-mode-and-auto-rp/#comment-161 cciethebeginning Thu, 30 Jul 2009 02:19:01 +0000 http://cciethebeginning.wordpress.com/2008/07/31/multicast-over-fr-nbma-part3-%e2%80%93-pim-nbma-mode-and-auto-rp/#comment-161 Hi Anh, As mentioned in the article "Multicast over FR NBMA part1" multicast has issues with NBMA, and even with workarounds such "pseudo-broadcast" & "PIM-NBMA mode" a couple of conditions are required for multicast to work. The HUB point-toMultipoint interface doesn't forward multicast traffic spoke-to-spoke only between HUB-to-spoke or spoke-to-HUB, that's why we need to make sure that all multicast traffic flow between the HUB site and spokes. Are you using Static RP? if PIM-Sparse-Dense, where your Multicast Agent is configured? Hi Anh,

As mentioned in the article “Multicast over FR NBMA part1″ multicast has issues with NBMA, and even with workarounds such “pseudo-broadcast” & “PIM-NBMA mode” a couple of conditions are required for multicast to work.
The HUB point-toMultipoint interface doesn’t forward multicast traffic spoke-to-spoke only between HUB-to-spoke or spoke-to-HUB, that’s why we need to make sure that all multicast traffic flow between the HUB site and spokes.

Are you using Static RP? if PIM-Sparse-Dense, where your Multicast Agent is configured?

]]> Comment on Multicast over FR NBMA part3 – (PIM-NBMA mode and Auto-RP) by Anh http://cciethebeginning.wordpress.com/2008/07/31/multicast-over-fr-nbma-part3-%e2%80%93-pim-nbma-mode-and-auto-rp/#comment-160 Anh Wed, 29 Jul 2009 13:18:11 +0000 http://cciethebeginning.wordpress.com/2008/07/31/multicast-over-fr-nbma-part3-%e2%80%93-pim-nbma-mode-and-auto-rp/#comment-160 Hi I am currently doing some tests with similar setup but have some problem :) What if the source is connected to Spoke B and client to Spoke A? At spoke A the RP is B. A (*,G) mapping from A will try to contact RP B, which also is RPF neighbor if the hub is multipoint and RP has IP address of spoke B frame-relay interface (listed in show ip mroute). Showing the ip pim neighbor at A, no neighbor B is listed (because they are not directly connected) => Spoke A cant send out join pim message to establish RPT to the RP ( spoke B). => Fail to connect RPT and source SPT at B In the setup RP mapping is to physical interface of Spoke B not any loopback. What can be wrong here? Thanks Hi

I am currently doing some tests with similar setup but have some problem :)

What if the source is connected to Spoke B and client to Spoke A?

At spoke A the RP is B. A (*,G) mapping from A will try to contact RP B, which also is RPF neighbor if the hub is multipoint and RP has IP address of spoke B frame-relay interface (listed in show ip mroute).

Showing the ip pim neighbor at A, no neighbor B is listed (because they are not directly connected) => Spoke A cant send out join pim message to establish RPT to the RP ( spoke B). => Fail to connect RPT and source SPT at B

In the setup RP mapping is to physical interface of Spoke B not any loopback.
What can be wrong here?

Thanks

]]> Comment on OSPF loopback network type by safdar http://cciethebeginning.wordpress.com/2009/02/27/ospf-loopback-network-type/#comment-156 safdar Wed, 15 Jul 2009 06:27:46 +0000 http://cciethebeginning.wordpress.com/2009/02/27/ospf-loopback-network-type/#comment-156 ccie notes ccie notes

]]> Comment on OSPF loopback network type by Raju Mor http://cciethebeginning.wordpress.com/2009/02/27/ospf-loopback-network-type/#comment-153 Raju Mor Thu, 28 May 2009 18:55:52 +0000 http://cciethebeginning.wordpress.com/2009/02/27/ospf-loopback-network-type/#comment-153 Awesome forum. I can't explain it in words, this site ROCKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!! Awesome forum. I can’t explain it in words, this site ROCKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!

]]> Comment on Differences between PVST and PVST+ by Pavel Devecka http://cciethebeginning.wordpress.com/2008/10/15/differences-between-pvst-and-pvst/#comment-152 Pavel Devecka Fri, 22 May 2009 13:51:48 +0000 http://cciethebeginning.wordpress.com/2008/10/15/differences-between-pvst-and-pvst/#comment-152 Again some comments from me. :) From article: 1. Untagged, if PVST+ native VLAN=VLAN 1. (figure1) 2. Tagged (coded with TLV, containing VLAN ID), if native VLAN other than VLAN 1. (figure2) My comment: According to my research in books and on the Internet, native VLAN should be always untagged in this case, which is also logical. According to point 2, if native VLAN wouldn't be VLAN 1, then VLAN ID would be carried in 802.1q and also in TLV for all VLANs. That would mean, that receiving switch wouldn't have any way how to figure out which VLAN is the native one on the other side of trunk. But if native VLAN would be always untagged, then receiving switch would be able to check what is the VLAN ID in TLV field of frame received without 802.1q tag and it would know, which VLAN is the native one. From article: 1) – PVST+ native VLAN BPDUs are transported (merged) in IEEE native VLAN (CST) My comment: I could spot information, that it's always VLAN 1, which is mapped to the CST. Again some comments from me. :)

From article:
1. Untagged, if PVST+ native VLAN=VLAN 1. (figure1)
2. Tagged (coded with TLV, containing VLAN ID), if native VLAN other than VLAN 1. (figure2)

My comment:
According to my research in books and on the Internet, native VLAN should be always untagged in this case, which is also logical. According to point 2, if native VLAN wouldn’t be VLAN 1, then VLAN ID would be carried in 802.1q and also in TLV for all VLANs. That would mean, that receiving switch wouldn’t have any way how to figure out which VLAN is the native one on the other side of trunk. But if native VLAN would be always untagged, then receiving switch would be able to check what is the VLAN ID in TLV field of frame received without 802.1q tag and it would know, which VLAN is the native one.

From article:
1) – PVST+ native VLAN BPDUs are transported (merged) in IEEE native VLAN (CST)

My comment:
I could spot information, that it’s always VLAN 1, which is mapped to the CST.

]]> Comment on Differences between PVST and PVST+ by cciethebeginning http://cciethebeginning.wordpress.com/2008/10/15/differences-between-pvst-and-pvst/#comment-151 cciethebeginning Wed, 20 May 2009 04:09:25 +0000 http://cciethebeginning.wordpress.com/2008/10/15/differences-between-pvst-and-pvst/#comment-151 You are absolutely right Pavel, The BPDUs on the native VLAN of the trunk are sent 1st time to the reserved IEEE 802.1D spanning tree multicast MAC address (01-80-C2-00-00-00) and a second time to the reserved SSTP multicast MAC address (01-00-0c-cc-cc-cd). I fixed it in the post, thank you for the correction. You are absolutely right Pavel,

The BPDUs on the native VLAN of the trunk are sent 1st time to the reserved IEEE 802.1D spanning tree multicast MAC address (01-80-C2-00-00-00) and a second time to the reserved SSTP multicast MAC address (01-00-0c-cc-cc-cd).

I fixed it in the post, thank you for the correction.

]]> Comment on Differences between PVST and PVST+ by Pavel Devecka http://cciethebeginning.wordpress.com/2008/10/15/differences-between-pvst-and-pvst/#comment-150 Pavel Devecka Tue, 19 May 2009 13:30:27 +0000 http://cciethebeginning.wordpress.com/2008/10/15/differences-between-pvst-and-pvst/#comment-150 Extract from article: PVST+ native VLAN BPDUs are transported (merged) in IEEE native VLAN (CST) untagged using IEEE STP MAC 0180.0CCC.CCCD. My comment: Shouldn't there be 0180.C200.0000 instead? Extract from article:
PVST+ native VLAN BPDUs are transported (merged) in IEEE native VLAN (CST) untagged using IEEE STP MAC 0180.0CCC.CCCD.

My comment:
Shouldn’t there be 0180.C200.0000 instead?

]]>