Re: VLAN-based EoMPLS

From: Marko Milivojevic <markom_at_ipexpert.com>
Date: Thu, 28 Oct 2010 12:11:15 +0000

Well, then something is wrong, but ... the information you're
providing doesn't make up for much troubleshooting fodder.

One question though - are you sure you can do xconnect from SVI on
3750? Perhaps you need to do it from a subinterface, as is the case
with 6500/7600 with LAN line cards.

--
Marko Milivojevic - CCIE #18427
Senior Technical Instructor - IPexpert
FREE CCIE training: http://bit.ly/vLecture
Mailto: markom_at_ipexpert.com
Telephone: +1.810.326.1444
Web: http://www.ipexpert.com/
On Thu, Oct 28, 2010 at 11:39, Manaf Al Oqlah <manafo_at_hotmail.com> wrote:
> no ma addresses and no arp are being learned!
>
> --------------------------------------------------
> From: "Marko Milivojevic" <markom_at_ipexpert.com>
> Sent: Thursday, October 28, 2010 2:01 PM
> To: "Manaf Al Oqlah" <manafo_at_hotmail.com>
> Cc: "karthik thatikonda" <get2explore_at_gmail.com>; "Shaughn Smith"
> <maniac.smg_at_gmail.com>; "srinivas pv" <vsrinivas.paturi_at_gmail.com>; "Elias
> Chari" <elias.chari_at_gmail.com>; "Group Study" <ccielab_at_groupstudy.com>
> Subject: Re: VLAN-based EoMPLS
>
>> Manaf - how are your ARP entries? Are MAC addresses being learned?
>>
>> --
>> Marko Milivojevic - CCIE #18427
>> Senior Technical Instructor - IPexpert
>>
>> FREE CCIE training: http://bit.ly/vLecture
>>
>> Mailto: markom_at_ipexpert.com
>> Telephone: +1.810.326.1444
>> Web: http://www.ipexpert.com/
>>
>> On Thu, Oct 28, 2010 at 06:25, Manaf Al Oqlah <manafo_at_hotmail.com> wrote:
>>>
>>> B 1 B * B * B *
>>>
>>>
>>> From: karthik thatikonda
>>> Sent: Wednesday, October 27, 2010 6:28 PM
>>> To: Shaughn Smith
>>> Cc: Manaf Al Oqlah ; srinivas pv ; Elias Chari ; Group Study
>>> Subject: Re: VLAN-based EoMPLS
>>>
>>>
>>> Can you do a traceroute on CE01 and see where it is stopping?.
>>>
>>>
>>> Regards,
>>>
>>>
>>> Karthik.
>>>
>>>
>>> On Wed, Oct 27, 2010 at 7:39 AM, Shaughn Smith <maniac.smg_at_gmail.com>
>>> wrote:
>>>
>>> B Did you reload the devices. Had the same issue once and a reload sorted
>>> it.
>>>
>>> B CCIE # 23962 (SP)
>>>
>>> B Sent from my iPhone 4
>>>
>>>
>>> B On 27 Oct 2010, at 4:17 PM, "Manaf Al Oqlah" <manafo_at_hotmail.com>
>>> wrote:
>>>
>>> B > yes received this debugging messages after putting deb ip icmp or deb
>>> ip
>>> packets
>>> B >
>>> B > CE01#debug ip icmp
>>> B > CE01#debug ip packet
>>> B > CE01#ping 192.168.0.2
>>> B >
>>> B > Type escape sequence to abort.
>>> B > Sending 5, 100-byte ICMP Echos to 192.168.0.2, timeout is 2 seconds:
>>> B >
>>> B > *Mar B 2 01:50:02.690: IP: tableid=0, s=192.168.0.1 (local),
>>> d=192.168.0.2
>>> (Vlan100), routed via RIB
>>> B > *Mar B 2 01:50:02.690: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, sending
>>> B > *Mar B 2 01:50:02.690: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, output feature, Check hwidb(63), rtype 1, forus FALSE, sendself
>>> FALSE, mtu 0
>>> B > *Mar B 2 01:50:02.699: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, encapsulation failed.
>>> B > *Mar B 2 01:50:04.695: IP: tableid=0, s=192.168.0.1 (local),
>>> d=192.168.0.2
>>> (Vlan100), routed via RIB
>>> B > *Mar B 2 01:50:04.695: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, sending
>>> B > *Mar B 2 01:50:04.695: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, output feature, Check hwidb(63), rtype 1, forus FALSE, sendself
>>> FALSE, mtu 0
>>> B > *Mar B 2 01:50:04.695: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, encapsulation failed.
>>> B > *Mar B 2 01:50:06.700: IP: tableid=0, s=192.168.0.1 (local),
>>> d=192.168.0.2
>>> (Vlan100), routed via RIB
>>> B > *Mar B 2 01:50:06.700: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, sending
>>> B > *Mar B 2 01:50:06.700: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, output feature, Check hwidb(63), rtype 1, forus FALSE, sendself
>>> FALSE, mtu 0
>>> B > *Mar B 2 01:50:06.700: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, encapsulation failed.
>>> B > *Mar B 2 01:50:08.705: IP: tableid=0, s=192.168.0.1 (local),
>>> d=192.168.0.2
>>> (Vlan100), routed via RIB
>>> B > *Mar B 2 01:50:08.705: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, sending
>>> B > *Mar B 2 01:50:08.705: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, output feature, Check hwidb(63), rtype 1, forus FALSE, sendself
>>> FALSE, mtu 0
>>> B > *Mar B 2 01:50:08.705: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, encapsulation failed.
>>> B > *Mar B 2 01:50:10.710: IP: tableid=0, s=192.168.0.1 (local),
>>> d=192.168.0.2
>>> (Vlan100), routed via RIB
>>> B > *Mar B 2 01:50:10.710: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, sending
>>> B > *Mar B 2 01:50:10.710: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, output feature, Check hwidb(63), rtype 1, forus FALSE, sendself
>>> FALSE, mtu 0
>>> B > *Mar B 2 01:50:10.710: IP: s=192.168.0.1 (local), d=192.168.0.2
>>> (Vlan100),
>>> len 100, encapsulation failed.
>>> B > Success rate is 0 percent (0/5)
>>> B > CE01#
>>> B >
>>> B > --------------------------------------------------
>>> B > From: "srinivas pv" <vsrinivas.paturi_at_gmail.com>
>>> B > Sent: Wednesday, October 27, 2010 5:11 PM
>>> B > To: "Manaf Al Oqlah" <manafo_at_hotmail.com>
>>> B > Cc: "Elias Chari" <elias.chari_at_gmail.com>; "Group Study"
>>> <ccielab_at_groupstudy.com>
>>> B > Subject: Re: VLAN-based EoMPLS
>>> B >
>>> B >> These outputs looks fine.
>>> B >>
>>> B >> Did you get 'deb ip icmp' and 'deb ip pack' on both CEs?
>>> B >>
>>> B >> This may give some idea.
>>> B >>
>>> B >> Thanks,
>>> B >> Srinivas
>>> B >>
>>> B >> On Wed, Oct 27, 2010 at 7:36 PM, Manaf Al Oqlah <manafo_at_hotmail.com>
>>> wrote:
>>> B >>
>>> B >>> here you go:
>>> B >>>
>>> B >>> PE01#sh mpls forwarding-table
>>> B >>> Local B Outgoing B B B B B Prefix B B B B B B B B B B B Bytes Label B
>>> Outgoing B B Next
>>> Hop
>>> B >>>
>>> B >>> Label B Label or VC B B or Tunnel Id B B B B B Switched B B B B B
>>> interface
>>> B >>>
>>> B >>> 17 B B B B Pop Label B B B B 2.2.2.2/32 B B B B B B B 0 B B B B B B B B B B B
>>> Gi1/1/1
>>> B >>> 10.0.0.2
>>> B >>> 18 B B B B No Label B B B B B l2ckt(100) B B B B B B B 0 B B B B B B B B B B B
>>> Vl100 point2point
>>> B >>>
>>> B >>>
>>> B >>> PE01#sh mpls forwarding-table detail
>>> B >>> Local B Outgoing B B B B B Prefix B B B B B B B B B B B Bytes Label B
>>> Outgoing B B Next
>>> Hop
>>> B >>>
>>> B >>> Label B Label or VC B B or Tunnel Id B B B B B Switched B B B B B
>>> interface
>>> B >>>
>>> B >>> 17 B B B B Pop Label B B B B 2.2.2.2/32 B B B B B B B 0 B B B B B B B B B B B
>>> Gi1/1/1
>>> B >>> 10.0.0.2
>>> B >>> B B B B B B B MAC/Encaps=14/14, MRU=1504, Label Stack{}
>>> B >>> B B B B B B B 002334947D42001DE63D1F428847
>>> B >>> B B B B B B B No output feature configured
>>> B >>> 18 B B B B No Label B B B B B l2ckt(100) B B B B B B B 0 B B B B B B B B B B B
>>> Vl100 point2point
>>> B >>>
>>> B >>> B B B B B B B MAC/Encaps=0/0, MRU=0, Label Stack{}
>>> B >>> B B B B B B B No output feature configured
>>> B >>>
>>> B >>> *From:* Elias Chari <elias.chari_at_gmail.com>
>>> B >>> *Sent:* Wednesday, October 27, 2010 5:05 PM
>>> B >>> *To:* srinivas pv <vsrinivas.paturi_at_gmail.com>
>>> B >>> *Cc:* Manaf Al Oqlah <manafo_at_hotmail.com> ; Group
>>> Study<ccielab_at_groupstudy.com>
>>> B >>> *Subject:* Re: VLAN-based EoMPLS
>>> B >>>
>>> B >>> you are probably right and it looks right based on the fact that
>>> PEs
>>> are
>>> B >>> connected back to back. But I am curious about the fact that on a
>>> 7200
>>> B >>> platform the command also displays the Tunnel label: imp-null, see
>>> output
>>> B >>> below, whilst on the ME3750 it does not. I wonder, is this because
>>> this
>>> is
>>> B >>> how the me3750 displays the output of the command or is it because
>>> the
>>> B >>> implicit-null is not there?
>>> B >>>
>>> B >>> Manaf, I would apprecuate it if you send the output of: sh mpls
>>> B >>> forwarding-table, it will help me understand a bit better the
>>> me3750.
>>> B >>>
>>> B >>> This is what you get on the 7200
>>> B >>>
>>> B >>> Rack1R1#sh mpls forwarding-table
>>> B >>> Local B Outgoing B B B B B Prefix B B B B B B B B B B B Bytes Label B
>>> Outgoing B B Next
>>> Hop
>>> B >>> Label B Label or VC B B or Tunnel Id B B B B B Switched B B B B B
>>> interface
>>> B >>> 19 B B B B Pop Label B B B B 2.2.2.2/32 B B B B B B B 0 B B B B B B B B B B B
>>> Se2/2
>>> B >>> point2point
>>> B >>> 23 B B B B No Label B B B B B l2ckt(111) B B B B B B B 860 B B B B B B B B B
>>> none point2point
>>> B >>>
>>> B >>> Rack1R1#sh mpls l2transport vc detail
>>> B >>> Local interface: Fa0/0 up, line protocol up, Ethernet up
>>> B >>> B Destination address: 2.2.2.2, VC ID: 111, VC status: up
>>> B >>> B B B Output interface: Se2/2, imposed label stack {23}
>>> B >>> B B B Preferred path: not configured
>>> B >>> B B B Default path: active
>>> B >>> B B B Tunnel label: imp-null, next hop point2point
>>> B >>> B Create time: 00:19:56, last status change time: 00:19:05
>>> B >>> B Signaling protocol: LDP, peer 2.2.2.2:0 up
>>> B >>> B B B MPLS VC labels: local 23, remote 23
>>> B >>> B B B Group ID: local 0, remote 0
>>> B >>> B B B MTU: local 1500, remote 1500
>>> B >>> B B B Remote interface description:
>>> B >>> B Sequencing: receive disabled, send disabled
>>> B >>> B VC statistics:
>>> B >>> B B B packet totals: receive 26, send 25
>>> B >>> B B B byte totals: B B receive 7206, send 7144
>>> B >>> B B B packet drops: B receive 0, send 0
>>> B >>>
>>> B >>>
>>> B >>> On 27 October 2010 14:20, srinivas pv <vsrinivas.paturi_at_gmail.com>
>>> wrote:
>>> B >>>
>>> B >>>> Since PEs are connected back-to-back, I do not think any issues
>>> with
>>> LDP
>>> B >>>> here.
>>> B >>>>
>>> B >>>> Also VC labels are setup properly.
>>> B >>>>
>>> B >>>> On PE1:
>>> B >>>> > B B B packet totals: receive 0, send 5 B <<<<< receive counters
>>> not
>>> B >>>> incrementing
>>> B >>>>
>>> B >>>> > B B B byte totals: B B receive 0, send 630
>>> B >>>> > B B B packet drops: B receive 0, send 0
>>> B >>>>
>>> B >>>> On PE2:
>>> B >>>> > B VC statistics:
>>> B >>>> > B B B packet totals: receive 5, send 0 B <<<<< send counters not
>>> B >>>> incrementing
>>> B >>>>
>>> B >>>> > B B B byte totals: B B receive 540, send 0
>>> B >>>> > B B B packet drops: B receive 0, send 0
>>> B >>>>
>>> B >>>> You may need to enable 'deb ip icmp' and 'deb ip pack' on CEs and
>>> may
>>> get
>>> B >>>> some ideas.
>>> B >>>>
>>> B >>>> Thanks,
>>> B >>>> Srinivas
>>> B >>>>
>>> B >>>> On Wed, Oct 27, 2010 at 6:42 PM, Elias Chari
>>> <elias.chari_at_gmail.com>wrote:
>>> B >>>>
>>> B >>>>> check to make sure LDP (not targeted) works ok and that you have
>>> a
>>> label
>>> B >>>>> to
>>> B >>>>> reach the remote PE loopback address.
>>> B >>>>>
>>> B >>>>> On 27 October 2010 13:24, Manaf Al Oqlah <manafo_at_hotmail.com>
>>> wrote:
>>> B >>>>>
>>> B >>>>> > ########### PE01 ###########
>>> B >>>>> >
>>> B >>>>> > PE01#sh mpls l2transport vc detail
>>> B >>>>> > Local interface: Vl100 up, line protocol up, Eth VLAN 100 up
>>> B >>>>> > B Interworking type is Ethernet
>>> B >>>>> > B Destination address: 2.2.2.2, VC ID: 100, VC status: up
>>> B >>>>> > B B B Output interface: Gi1/1/1, imposed label stack {18}
>>> B >>>>> > B B B Preferred path: not configured
>>> B >>>>> > B B B Default path: active
>>> B >>>>> > B B B Next hop: 10.0.0.2
>>> B >>>>> > B Create time: 00:22:03, last status change time: 00:07:53
>>> B >>>>> > B Signaling protocol: LDP, peer 2.2.2.2:0 up
>>> B >>>>> > B B B Targeted Hello: 1.1.1.1(LDP Id) -> 2.2.2.2
>>> B >>>>> > B B B Status TLV support (local/remote) B B : enabled/not
>>> supported
>>> B >>>>> > B B B B B Label/status state machine B B B B B B B : established,
>>> LruRru
>>> B >>>>> > B B B B B Last local dataplane B B status rcvd: no fault
>>> B >>>>> > B B B B B Last local SSS circuit status rcvd: no fault
>>> B >>>>> > B B B B B Last local SSS circuit status sent: no fault
>>> B >>>>> > B B B B B Last local B LDP TLV B B B status sent: no fault
>>> B >>>>> > B B B B B Last remote LDP TLV B B B status rcvd: not sent
>>> B >>>>> > B B B MPLS VC labels: local 20, remote 18
>>> B >>>>> > B B B Group ID: local 0, remote 0
>>> B >>>>> > B B B MTU: local 1900, remote 1900
>>> B >>>>> > B B B Remote interface description:
>>> B >>>>> > B Sequencing: receive disabled, send disabled
>>> B >>>>> > B VC statistics:
>>> B >>>>> > B B B packet totals: receive 0, send 5
>>> B >>>>> > B B B byte totals: B B receive 0, send 630
>>> B >>>>> > B B B packet drops: B receive 0, send 0
>>> B >>>>> >
>>> B >>>>> > PE01#sh run int g1/1/2
>>> B >>>>> > Building configuration...
>>> B >>>>> >
>>> B >>>>> > Current configuration : 128 bytes
>>> B >>>>> > !
>>> B >>>>> > interface GigabitEthernet1/1/2
>>> B >>>>> > B description To CE01
>>> B >>>>> > B switchport access vlan 100
>>> B >>>>> > B switchport mode access
>>> B >>>>> > B speed auto 1000
>>> B >>>>> > end
>>> B >>>>> >
>>> B >>>>> > ###### PE02 ############
>>> B >>>>> >
>>> B >>>>> > PE02#sh mpls l2transport vc detail
>>> B >>>>> > Local interface: Vl100 up, line protocol up, Eth VLAN 100 up
>>> B >>>>> > B Interworking type is Ethernet
>>> B >>>>> > B Destination address: 1.1.1.1, VC ID: 100, VC status: up
>>> B >>>>> > B B B Output interface: Gi1/1/1, imposed label stack {20}
>>> B >>>>> > B B B Preferred path: not configured
>>> B >>>>> > B B B Default path: active
>>> B >>>>> > B B B Next hop: 10.0.0.1
>>> B >>>>> > B Create time: 00:21:35, last status change time: 00:09:38
>>> B >>>>> > B Signaling protocol: LDP, peer 1.1.1.1:0 up
>>> B >>>>> > B B B Targeted Hello: 2.2.2.2(LDP Id) -> 1.1.1.1
>>> B >>>>> > B B B Status TLV support (local/remote) B B : enabled/not
>>> supported
>>> B >>>>> > B B B B B Label/status state machine B B B B B B B : established,
>>> LruRru
>>> B >>>>> > B B B B B Last local dataplane B B status rcvd: no fault
>>> B >>>>> > B B B B B Last local SSS circuit status rcvd: no fault
>>> B >>>>> > B B B B B Last local SSS circuit status sent: no fault
>>> B >>>>> > B B B B B Last local B LDP TLV B B B status sent: no fault
>>> B >>>>> > B B B B B Last remote LDP TLV B B B status rcvd: not sent
>>> B >>>>> > B B B MPLS VC labels: local 18, remote 20
>>> B >>>>> > B B B Group ID: local 0, remote 0
>>> B >>>>> > B B B MTU: local 1900, remote 1900
>>> B >>>>> > B B B Remote interface description:
>>> B >>>>> > B Sequencing: receive disabled, send disabled
>>> B >>>>> > B VC statistics:
>>> B >>>>> > B B B packet totals: receive 5, send 0
>>> B >>>>> > B B B byte totals: B B receive 540, send 0
>>> B >>>>> > B B B packet drops: B receive 0, send 0
>>> B >>>>> >
>>> B >>>>> > PE02#sh run int g1/1/2
>>> B >>>>> > Building configuration...
>>> B >>>>> >
>>> B >>>>> > Current configuration : 128 bytes
>>> B >>>>> > !
>>> B >>>>> > interface GigabitEthernet1/1/2
>>> B >>>>> > B description to CE01
>>> B >>>>> > B switchport access vlan 100
>>> B >>>>> > B switchport mode access
>>> B >>>>> > B speed auto 1000
>>> B >>>>> > end
>>> B >>>>> >
>>> B >>>>> > ########### CE01 ############
>>> B >>>>> >
>>> B >>>>> > CE01#sh run int g1/0/25
>>> B >>>>> > interface GigabitEthernet1/0/25
>>> B >>>>> > B description to PE01
>>> B >>>>> > B switchport access vlan 100
>>> B >>>>> > B switchport mode access
>>> B >>>>> > end
>>> B >>>>> > !
>>> B >>>>> > CE01#sh run int vlan 100
>>> B >>>>> > interface Vlan100
>>> B >>>>> > B ip address 192.168.0.1 255.255.255.0
>>> B >>>>> >
>>> B >>>>> > ######### CE02 ###########
>>> B >>>>> >
>>> B >>>>> > CE02#sh run int g1/1/1
>>> B >>>>> > interface GigabitEthernet1/1/1
>>> B >>>>> > B description to PE02
>>> B >>>>> > B switchport access vlan 100
>>> B >>>>> > B switchport mode access
>>> B >>>>> > B speed auto 1000
>>> B >>>>> > end
>>> B >>>>> >
>>> B >>>>> > CE02#sh run int vlan 100
>>> B >>>>> > interface Vlan100
>>> B >>>>> > B ip address 192.168.0.2 255.255.255.0
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > From: srinivas pv
>>> B >>>>> > Sent: Wednesday, October 27, 2010 2:42 PM
>>> B >>>>> > To: Manaf Al Oqlah
>>> B >>>>> > Cc: Group Study
>>> B >>>>> > Subject: Re: VLAN-based EoMPLS
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > Hi,
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > Could you give following details
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > On both PEs:
>>> B >>>>> > show mpls l2 vc detail
>>> B >>>>> > sh run int <int connected to CE>
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > On both CEs:
>>> B >>>>> > sh run int <int connected to PE>
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > Thanks,
>>> B >>>>> > Srinivas
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > On Wed, Oct 27, 2010 at 5:00 PM, Manaf Al Oqlah
>>> <manafo_at_hotmail.com>
>>> B >>>>> > wrote:
>>> B >>>>> >
>>> B >>>>> > B Hi,
>>> B >>>>> >
>>> B >>>>> > B I have established an EoMPLS circuit on ME3750 switches as
>>> below.
>>> B >>>>> > everything
>>> B >>>>> > B seems to be working fine as my virtual circuit is UP
>>> B >>>>> > B but my problem is that I cant ping IP address CE02 from CE01
>>> B >>>>> >
>>> B >>>>> > B PC01---CE01---PE01---PE02---CE02---PC02
>>> B >>>>> >
>>> B >>>>> > B I have applied the following configuration on PE01 & PE02 ES
>>> ports
>>> B >>>>> >
>>> B >>>>> > B interface loopback 0
>>> B >>>>> > B ip address 1.1.1.1 255.255.255.255
>>> B >>>>> > B !
>>> B >>>>> > B interface GigabitEthernet1/1/1
>>> B >>>>> > B description to PE02
>>> B >>>>> > B B ip address 10.0.0.1 255.255.255.252
>>> B >>>>> > B B mpls ip
>>> B >>>>> > B !
>>> B >>>>> > B interface GigabitEthernet1/1/2
>>> B >>>>> > B description to CE01
>>> B >>>>> > B switchport mode access
>>> B >>>>> > B switchport access vlan 100
>>> B >>>>> > B !
>>> B >>>>> > B vlan 100
>>> B >>>>> > B !
>>> B >>>>> > B interface vlan 100
>>> B >>>>> > B xconnect 2.2.2.2 100 encapsulation mpls
>>> B >>>>> >
>>> B >>>>> > B where could me my problem!
>>> B >>>>> >
>>> B >>>>> > B Regards,
>>> B >>>>> > B Manaf Al Oqlah
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > B Blogs and organic groups at http://www.ccie.net
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>>
>>> _______________________________________________________________________
>>> B >>>>> > B Subscription information may be found at:
>>> B >>>>> > B http://www.groupstudy.com/list/CCIELab.html
>>> B >>>>> >
>>> B >>>>> >
>>> B >>>>> > Blogs and organic groups at http://www.ccie.net
>>> B >>>>> >
>>> B >>>>> >
>>> _______________________________________________________________________
>>> B >>>>> > Subscription information may be found at:
>>> B >>>>> > http://www.groupstudy.com/list/CCIELab.html
>>> B >>>>>
>>> B >>>>>
>>> B >>>>> Blogs and organic groups at http://www.ccie.net
>>> B >>>>>
>>> B >>>>>
>>> _______________________________________________________________________
>>> B >>>>> Subscription information may be found at:
>>> B >>>>> http://www.groupstudy.com/list/CCIELab.html
>>> B >>>>>
>>> B >>>>>
>>> B >>>>>
>>> B >>>>>
>>> B >>>>>
>>> B >>>>>
>>> B >>>>>
>>> B >>>>>
>>> B >>>>
>>> B >>>
>>> B >>>
>>> B >>> --
>>> B >>> Regards,
>>> B >>> Elias
>>> B >>> CCIE#17354
>>> B >>> Tel: +44 794 386 6320
>>> B >>
>>> B >>
>>> B >> Blogs and organic groups at http://www.ccie.net
>>> B >>
>>> B >>
>>> _______________________________________________________________________
>>> B >> Subscription information may be found at:
>>> B >> http://www.groupstudy.com/list/CCIELab.html
>>> B >
>>> B >
>>> B > Blogs and organic groups at http://www.ccie.net
>>> B >
>>> B >
>>> _______________________________________________________________________
>>> B > Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> B Blogs and organic groups at http://www.ccie.net
>>>
>>> B _______________________________________________________________________
>>> B Subscription information may be found at:
>>> B http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Oct 28 2010 - 12:11:15 ART

This archive was generated by hypermail 2.2.0 : Mon Nov 01 2010 - 06:42:06 ART