[IRX frm1]-------[Nynex]----DLCI 17 [pm2er] (works great)
[ ] [ ]----DLCI 18 [ascend] (works great)
[ ] [ ]----DLCI 19 [ascend] (works great)
[ sub-if] [ ]----DLCI 28 [cisco]---DLCI 16--Nynex (no
communications)
>The IRX and the Cisco are each part of different Frame Relay
networks, but
we had the other end include us in their network by giving us DLCI 28 and
having us make a sub-interface, so that makes the IRX part of both
networks.
What does this mean? If both ends of the DLCI are on different
frame networks (I take this to mean 2 different frame relay
providers), then the 2 networks need a NNI between them.
>The key is that both routers have DLCI 16 has their local FR
interface, though each DLCI 16 is on a different FR network for the IRX.
DLCI's are only locally significant, meaning that DLCI numbers only
matter between the end device (router/frad) and the frame relay
switch it terminates into. Another frame relay link can have the
same DLCI on the other end, because PVC's are mapped from an
interface/dlci to another interface/dlci.
>Is this causing the problem, or is the Cisco the problem, or is the
network design the problem? Maybe it will work afterall and it's a Nynex
problem?
I don't know. What concerns me is the fact that you you have 2
networks but no mention of a link between them. I need some more
information.
>I've tried messing with the DLCI-ipnumber static mappings but to
no avail.
That's kinda pointless unless you have the provider on the line to
tell you what is coming in from the device.
We also stopped receiving DLCI 28 from the LMI information coming
from the
switch, which means it might be a nynex problem. But if it's a Nynex
problem, we have to be lucky and catch a clueful person which hasnt
happened yet.
Now this sounds like dlci 28 is no longer active or configured in
the network.
Kyle Platts
CSS-Tech
!NTERPRISE Networking Services