[j-nsp] Question about l2circuits

[Peering]

I was trying to migrate some customers off of a Newbridge FR/ATM switch
and onto a couple of Juniper M-20s running 7.3R6.  The T1 in Colorado
Springs is an NNI that has 6 of the 7 remote sites for a customer in
Vegas.  The two T1s in Vegas are the hub site for the frame and one of
the remotes.  Here's the config I used on two of the routers, to give
you an idea.  I got the L2circuits up, but only one-way traffic would
pass for the sites that were built between the two routers.  For the
sites that are in the same router, traffic passed both ways.  Any ideas
of what's going on?  

Also, if anyone has a config for MLFR (hub and multiple spoke config) on
the old (non-IQ) link-services PIC, please send it to me off-list.  I
can't find anything on the Juniper website that doesn't involve the AS
PIC (I swear they're conspiring to make me buy one).

mylogin at CLSPCO-03> show configuration interfaces t1-2/0/0:28 
apply-groups-except default-t1/ds0;
description "NNI circuit to a vendor";
dce;
encapsulation extended-frame-relay-ccc;
lmi {
    lmi-type ansi;
}
unit 0 {
    description "site A";
    encapsulation frame-relay-ccc;
    dlci 77;
    inverse-arp;
}
unit 1 {
    description "site B";
    encapsulation frame-relay-ccc;
    dlci 79;
    inverse-arp;
}
unit 2 {
    description "site C";
    encapsulation frame-relay-ccc;
    dlci 24;        
    inverse-arp;
}
unit 3 {
    description "site D";
    encapsulation frame-relay-ccc;
    dlci 25;
    inverse-arp;
}
unit 4 {
    description "site E";
    encapsulation frame-relay-ccc;
    dlci 26;
    inverse-arp;
}
unit 5 {
    description "site F";
    encapsulation frame-relay-ccc;
    dlci 40;
    inverse-arp;
}

mylogin at CLSPCO-03> show configuration protocols l2circuit neighbor
x.x.x.x
interface t1-2/0/0:28.0 {
    virtual-circuit-id 40;
    description "Customer A";
}
interface t1-2/0/0:28.1 {
    virtual-circuit-id 41;
    description "Customer B";
}
interface t1-2/0/0:28.2 {
    virtual-circuit-id 42;
    description "Customer C";
}
interface t1-2/0/0:28.3 {
    virtual-circuit-id 43;
    description "Customer D";
}
interface t1-2/0/0:28.4 {
    virtual-circuit-id 44;
    description "Customer E";
}
interface t1-2/0/0:28.5 {
    virtual-circuit-id 45;
    description "Customer F";
}                   

mylogin at LSVGNV-01> show configuration interfaces | find 2/2/0:27 
 t1-2/2/0:27 {
    apply-groups-except default-t1/ds0;
    description "Sites A-G's hub site";
    dce;
    encapsulation extended-frame-relay-ccc;
    lmi {
        lmi-type ansi;
    }
    unit 0 {
        description "Site G";
        encapsulation frame-relay-ccc;
        dlci 16;
        inverse-arp;
    }
    unit 1 {
        description "Site C";
        encapsulation frame-relay-ccc;
        dlci 24;
        inverse-arp;
    }
    unit 2 {
        description "Site E";
        encapsulation frame-relay-ccc;
        dlci 26;
        inverse-arp;
    }
    unit 3 {
        description "Site D";
        encapsulation frame-relay-ccc;
        dlci 39;
        inverse-arp;
    }
    unit 4 {
        description "Site F";
        encapsulation frame-relay-ccc;
        dlci 40;
        inverse-arp;
    }
    unit 5 {
        description "Site A";
        encapsulation frame-relay-ccc;
        dlci 77;
        inverse-arp;
    }
    unit 6 {        
        description "Site B";
        encapsulation frame-relay-ccc;
        dlci 79;
        inverse-arp;
    }
}
t1-2/2/0:28 {
    apply-groups-except default-t1/ds0;
    description "site G";
    dce;
    encapsulation extended-frame-relay-ccc;
    lmi {
        lmi-type ansi;
    }
    unit 0 {
        description "Connection to hub, t1-2/2/0:27.0";
        encapsulation frame-relay-ccc;
        dlci 16;
        inverse-arp;
    }
}

mylogin at LSVGNV-01> show config protocols l2circuit 
neighbor x.x.x.y
interface t1-2/2/0:27.1 {
    virtual-circuit-id 42;
    description "Site C";
}
interface t1-2/2/0:27.2 {
    virtual-circuit-id 44;
    description "site E";
}
interface t1-2/2/0:27.3 {
    virtual-circuit-id 43;
    description "site D";
}
interface t1-2/2/0:27.4 {
    virtual-circuit-id 45;
    description "Site F";
}
interface t1-2/2/0:27.5 {
    virtual-circuit-id 40;
    description "Site A";
}
interface t1-2/2/0:27.6 {
    virtual-circuit-id 41;
    description "Site B";
}
local-switching {
    interface t1-2/2/0:27.0 {
        end-interface {
            interface t1-2/2/0:28.0;
        }
        description "Site G to hub connection";
    }
}

Diane Turley
Sr. Network Engineer
Xspedius Communications Co.
636-625-7178