Routing

Hi Guys

     I just did a lab about vlan-ccc with quite simple topology  R1（1.1.1.1/30）--R2（vlan-ccc）--R3（1.1.1.2/30）. I can't ping myself IP 1.1.1.1 and remote 1.1.1.2. Seems like layer3 interface never been configured. Pls refer to file attached for the configuration. Appreciate your opinion if any.

Attachment(s)

Vlan-ccc.txt   2 KB 1 version

Hello,

It appears you are doing CCC on older HW - what is the exact router model and JUNOS version?

Also, it appears you are doing that in logical-systems because without "vlan-tagging" under physical interface, _BUT_ with "vlan-id" under unit, such config does not commit. Please post the interfaces config from master LS.

Lastly, "encapsulation vlan-ccc" must be repeated on physical interface as well so your complete CCC interface config must look like below. If you are using LS, "encapsulation vlan-ccc" and "vlan-tagging" must be present in master LS under [edit interfaces]:

R2 {
    interfaces {
        fe-0/3/2 {
        encapsulation vlan-ccc;
        vlan-tagging;
            unit 0 {
                encapsulation vlan-ccc;
                vlan-id 1102;
                family ccc;
            }       
        }
        fe-0/3/1 {
        encapsulation vlan-ccc;
        vlan-tagging;
            unit 0 {
                encapsulation vlan-ccc;
                vlan-id 1102;
                family ccc;
            }
        }
    }

 HTH

Thanks

Alex

Hi Alex

    Exaclty , I am using logical system , I performed vlan-tagging and encapsulation vlan-ccc also. Below is my global configuration for all of interfaces. This is M7i running with unos 10.0r3.

lab@M7i# show interfaces
so-0/0/0 {
no-keepalives;
encapsulation frame-relay;
}
so-0/1/0 {
no-keepalives;
encapsulation frame-relay;
}
fe-0/3/0 {
vlan-tagging;
}
fe-0/3/1 {
vlan-tagging;
encapsulation vlan-ccc;
}
fe-0/3/2 {
vlan-tagging;
encapsulation vlan-ccc;
}
fe-0/3/3 {
vlan-tagging;
}

Few question 

1. If you connection is showing up for you ?

you can check it cli:

show connections

2. If you are having physical connectivity between fe-0/3/0 --- fe-0/3/1 and between fe-0/3/2 --- fe-0/3/3 ?

Regards

Gaurav Goel

Hi Gaurav

      Thanks for your reply on the issue, I checked the status that you mentioned.

1. I can't see any connection when I "show connections"

2.Double confirmed, physical connections are correct. fe-0/3/0 to fe-0/3/1, fe-0/3/2 to fe-0/3/3.

I just curious , as I know vlan-ccc just provides cross circuit in this ordinary case ,  like a router with a vlan pass-through. Is that correct? If it is, I have no idea why it does not work.  Any incorrect configuration? Thanks for your reply.

Hi Gaurav

     I made a mistake when I was showing connections, it should implement under logical system hierarchy. The status is down and NP（Not present）, sorry about that!

lab@M7i# run show connections logical-system R2
CCC and TCC connections [Link Monitoring On]
Legend for status (St) Legend for connection types
UN -- uninitialized if-sw: interface switching
NP -- not present rmt-if: remote interface switching
WE -- wrong encapsulation lsp-sw: LSP switching
DS -- disabled tx-p2mp-sw: transmit P2MP switching
Dn -- down rx-p2mp-sw: receive P2MP switching
-> -- only outbound conn is up
<- -- only inbound conn is up Legend for circuit types
Up -- operational intf -- interface
RmtDn -- remote CCC down tlsp -- transmit LSP
Restart -- restarting rlsp -- receive LSP

Connection/Circuit Type St Time last up # Up trans
l2sw if-sw Dn ----- 0
fe-0/3/1.0 intf NP
fe-0/3/2.0 intf NP

Hello,

And what happens if you use CCC vlan-id between 512 and 1024, say, 600?

Please could you test and report back.

Thanks

Alex

Hi Alex

    Instead of  vlan-id1102, It works after I changed vlan-id to 777 . Do you have any document mentioned about this? Thanks a lot!

lab@M7i# run show interfaces terse
Interface Admin Link Proto Local Remote
so-0/0/0 up up
so-0/1/0 up up
fe-0/3/0 up up
fe-0/3/0.777 up up inet 1.1.1.1/30
fe-0/3/0.32767 up up
fe-0/3/1 up up
fe-0/3/1.0 up up ccc
fe-0/3/1.32767 up up
fe-0/3/2 up up
fe-0/3/2.0 up up ccc
fe-0/3/2.32767 up up
fe-0/3/3 up up
fe-0/3/3.777 up up inet 1.1.1.2/30

==============================================================================

lab@M7i# show groups ccc logical-systems R2
interfaces {
fe-0/3/2 {
unit 0 {
encapsulation vlan-ccc;
vlan-id 777;
}
}
fe-0/3/1 {
unit 0 {
encapsulation vlan-ccc;
vlan-id 777;
}
}
}
protocols {
mpls {
interface fe-0/3/1.0;
interface fe-0/3/2.0;
}
connections {
interface-switch l2sw {
interface fe-0/3/1.0;
interface fe-0/3/2.0;
}
}
}

Hi Chen,

                As per you output since connection are not showing up in cli so you will not able to ping as basic ccc is not up.

The connections may be down generally because it might be your ports are down . Can you please check out you basic interfaces are show up properly or not. 

1. show interfaces fe-0/3/1 extensive

2. show interfaces fe-0/3/2 extensive

3. if it is still proper, Can you check basic plane ip connectivity comes up with these interfaces? 

Regards

Gaurav goel

JNCIP-SP

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

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !

Hi Gaurav

   After I did what Alex suggested. It works after I change the vlan into 777 （512~1024）, but don't know why.Thanks for your help. 

   I just found a document mentions about vlan range when using vlan-ccc with 4-port Fast Ethernet Interfaces.

Ethernet interfaces in VLAN mode can have multiple logical interfaces. In CCC and VPLS modes, VLAN IDs from 1 through 511 are reserved for normal VLANs, and VLAN IDs 512 through 4094 are reserved for CCC or VPLS VLANs. For 4-port Fast Ethernet interfaces, you can use VLAN IDs 512 through 1024 for CCC or VPLS VLANs

http://www.juniper.net/techpubs/en_US/junos9.5/information-products/topic-collections/config-guide-network-interfaces/interfaces-configuring-vlan-encapsulation.htm