[j-nsp] vpls remote mac learning on M20 on Junos 9.1?
Marlon Duksa
mduksa at gmail.com
Wed Jul 30 23:42:43 EDT 2008
Yes, no tp hardware in the chassis, this is why I'm using no-tunnel
-services cmd.
Is there any workaround? Or at least the documentation mentioning that VPLS
PE is not supported on certain FPCs...
Thanks,
Marlon
admin at m20-nemo> show chassis hardware detail
Hardware inventory:
Item Version Part number Serial number Description
Chassis 21700 M20
Backplane REV 07 710-001517 AL2602 M20 Backplane
Power Supply A REV 03 740-001465 001250 AC Power Supply
Power Supply B REV 03 740-001465 001111 AC Power Supply
Display REV 04 710-001519 AF3167 M20 FPM Board
Routing Engine 0 b900000749e24801 RE-2.0
ad0 3847 MB CF CARD 4GB CF 4GB 0000B064 Compact Flash
ad1 11513 MB IBM-DARA-212000 AH0AHGC9395 Hard Disk
SSB 0 REV 01 710-001951 AH5619 Internet Processor
IIv1
SSRAM bank 0 REV 02 710-001385 214894 2 Mbytes
SSRAM bank 1 REV 02 710-001385 510731 2 Mbytes
SSRAM bank 2 REV 02 710-001385 215301 2 Mbytes
SSRAM bank 3 REV 02 710-001385 214879 2 Mbytes
FPC 0 REV 01 710-001292 AL5231 FPC
SSRAM REV 03 710-000077 V07963 1 Mbyte
SDRAM bank 0 REV 04 710-000099 334802 64 Mbytes
SDRAM bank 1 REV 04 710-000099 334803 64 Mbytes
PIC 0 REV 02 750-002785 AN3275 1x G/E, 1000
BASE-SX
PIC 1 REV 02 750-002785 AJ1733 1x G/E, 1000
BASE-SX
PIC 2 REV 02 750-002785 AM3054 1x G/E, 1000
BASE-SX
PIC 3 REV 07 750-002303 AK5668 4x F/E, 100 BASE-TX
Fan Tray 0 Front Upper Fan
Tray
Fan Tray 1 Front Middle Fan
Tray
Fan Tray 2 Front Bottom Fan
Tray
Fan Tray 3 Rear Fan Tray
On Wed, Jul 30, 2008 at 5:03 PM, Harry Reynolds <harry at juniper.net> wrote:
> What type fpc is in that M20? I believe a B2/efpc is needed for lsi
> type interfaces, such as needed for no-tunnel services config. In the
> past I have seen this blackhole vpls traffic coming in from the core.
>
> I assume you have no tp hardware? If you did worth loosing the
> no-tunnel.
>
> Send OP of a show chassis hardware....
>
> HTHs
>
>
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Marlon Duksa
> Sent: Wednesday, July 30, 2008 4:52 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] vpls remote mac learning on M20 on Junos 9.1?
>
> Does anyone know why M20 would not learn remote (comming from a PE) MAC
> addresses? I'm on Junos 9.1.
> It is learning ce mac addresses. Also it is forwarding traffic in the
> ce->pe direction, but everything coming from the pe side is not getting
> out on the ce side.
> I even put the sniffer between MX and M20 and see traffic comming from
> the MX (pe side) with the proper demultiplexer label (there is no
> transport label as routers are connected back to back). Transport is
> ldp.
>
>
> On the other side I have an MX as PE and the MX is forwarding traffic
> just fine in both directions. Is there any additional config that needs
> to be enabled on the M20?
> Thanks
>
> Here is the M20 config and some show commands that show VPLS as UP.
>
> routing-instances {
> vpls {
> instance-type vpls;
> interface ge-0/1/0.0;
> interface ge-0/1/0.1;
> interface ge-0/3/0.0;
> route-distinguisher 100:100;
> vrf-target target:200:200;
> protocols {
> vpls {
> site-range 10;
> mac-table-size {
> 65000;
> }
> interface-mac-limit {
> 65000;
> }
> mac-table-aging-time 10000;
> no-tunnel-services;
> site green {
> site-identifier 3;
> interface ge-0/1/0.0;
> interface ge-0/1/0.1;
> interface ge-0/3/0.0;
> }
> }
> }
> }
> }
>
>
> admin at m20-nemo# show interfaces
> ge-0/0/0 {
> unit 0 {
> family inet {
> address 10.0.0.2/24;
> }
> family mpls;
> }
> }
> ge-0/1/0 {
> vlan-tagging;
> encapsulation extended-vlan-vpls;
> unit 0 {
> vlan-id 1;
> }
> unit 1 {
> vlan-id 2;
> }
> }
> ge-0/2/0 {
> unit 0 {
> family inet {
> address 10.0.1.2/24;
> }
> family mpls;
> }
> }
> ge-0/3/0 {
> encapsulation ethernet-vpls;
> unit 0;
> }
> lo0 {
> unit 0 {
> family inet {
> address 3.3.3.3/32;
> }
> }
> }
>
>
> admin at m20-nemo# run show vpls connections extensive
> Layer-2 VPN connections:
>
> Legend for connection status (St)
> EI -- encapsulation invalid NC -- interface encapsulation not
> CCC/TCC/VPLS
> EM -- encapsulation mismatch WE -- interface and instance encaps not
> same
> VC-Dn -- Virtual circuit down NP -- interface hardware not present
> CM -- control-word mismatch -> -- only outbound connection is up
> CN -- circuit not provisioned <- -- only inbound connection is up
> OR -- out of range Up -- operational
> OL -- no outgoing label Dn -- down
> LD -- local site signaled down CF -- call admission control failure
> RD -- remote site signaled down SC -- local and remote site ID
> collision LN -- local site not designated LM -- local site ID not
> minimum designated RN -- remote site not designated RM -- remote site ID
> not minimum designated XX -- unknown connection status IL -- no
> incoming label
> MM -- MTU mismatch MI -- Mesh-Group ID not availble
>
> Legend for interface status
> Up -- operational
> Dn -- down
>
> Instance: vpls
> Local site: green (3)
> Number of local interfaces: 3
> Number of local interfaces up: 2
> IRB interface present: no
> ge-0/1/0.0
> ge-0/1/0.1
> ge-0/3/0.0
> Interface flags: VC-Down
> lsi.1048576 1 Intf - vpls vpls local site 3 remote
> site
> 1
> lsi.1048577 2 Intf - vpls vpls local site 3 remote
> site
> 2
> 262145 1 8 100
> status-vector: 3F
> connection-site Type St Time last up # Up
> trans
> 1 rmt Up Jul 30 23:41:09 2008
> 1
> Local interface: lsi.1048576, Status: Up, Encapsulation: VPLS
> Description: Intf - vpls vpls local site 3 remote site 1
> Remote PE: 1.1.1.1, Negotiated control-word: No
> Incoming label: 262145, Outgoing label: 262147
>
> Connection History:
> Jul 30 23:41:09 2008 status update timer
> Jul 30 23:41:09 2008 PE route changed
> Jul 30 23:41:09 2008 Out lbl Update 262147
> Jul 30 23:41:09 2008 In lbl Update 262145
> Jul 30 23:41:09 2008 loc intf up lsi.1048576
> 2 rmt Up Jul 30 23:41:28 2008
> 1
> Local interface: lsi.1048577, Status: Up, Encapsulation: VPLS
> Description: Intf - vpls vpls local site 3 remote site 2
> Remote PE: 2.2.2.2, Negotiated control-word: No
> Incoming label: 262146, Outgoing label: 262147
>
> Connection History:
> Jul 30 23:41:28 2008 status update timer
> Jul 30 23:41:28 2008 PE route changed
> Jul 30 23:41:28 2008 Out lbl Update 262147
> Jul 30 23:41:28 2008 In lbl Update 262146
> Jul 30 23:41:28 2008 loc intf up lsi.1048577
>
> [edit]
> admin at m20-nemo#
>
>
>
>
> admin at m20-nemo# run show route forwarding-table family vpls Routing
> table: vpls.vpls
> VPLS:
> Destination Type RtRef Next hop Type Index NhRef Netif
> default perm 0 rjct 536 1
> ge-0/1/0.0 user 0 comp 557 3
> ge-0/1/0.1 user 0 comp 557 3
> lsi.1048576 user 0 comp 566 3
> lsi.1048577 user 0 comp 566 3
> 00:00:c0:00:00:3d/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:3e/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:3f/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:40/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:41/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:42/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:43/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:44/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:45/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> 00:00:c0:00:00:46/48
> dynm 0 ucst 552 12
> ge-0/1/0.0
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list