The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] RE: Frame based MPLS between an Unisphere ERX and a CISCO 7507
Panos, Enabling LDP on the ERX lets it exchange label mappings with all of it's LDP peers for all of it's routing entries, but does not actually create LSP's to each prefix. The "topology-driven-lsp" command specifies which destinations (ingress and egress) the ERX should establish LSP's to. This allows you a more granular control over which destinations you create LSPs for. Thanks, Chris Young Network Support Engineer Unisphere Certified Technical Expert Juniper Networks JTAC Westford, MA USA support: 978.589.9000 direct: 978.589.0170 cell: 978.973.0574 -----Original Message----- From: panos@noc.uoa.gr [mailto:panos@noc.uoa.gr] Sent: Thursday, September 26, 2002 7:38 PM To: mpls-ops@mplsrc.com Subject: [MPLS-OPS]: Frame based MPLS between an Unisphere ERX and a CISCO 7507 Hi to all, Some minutes ago i found out that the mpls topology-driven-lsp command should be augmented with the following two commands: mpls topology-driven-lsp ip-interfaces egress access-list test mpls topology-driven-lsp ip-interfaces ingress access-list test where : access-list test permit ip any any It seems that the ERX does not forward labeled packets as an ingress or as an egress if these two commands are not in place. Any better explanation will be greatly appreciated. Thank you, Panos Kolyvas Network Operations Center University of Athens Greece. ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml |
|