nanog mailing list archives
Re: interesting troubleshooting
From: Saku Ytti <saku () ytti fi>
Date: Sun, 22 Mar 2020 11:26:19 +0200
Hey Tassos, On Sat, 21 Mar 2020 at 22:51, Tassos Chatzithomaoglou <achatz () forthnet gr> wrote:
Yep, the RFC gives this option. Does Juniper MX/ACX series support it? I know for sure Cisco doesn't.
I only run bidir, which Cisco do you mean? ASR9k allows you to configure it. both Insert/Discard Flow label on transmit/recceive code Flow label TLV code receive Discard Flow label on receive transmit Insert Flow label on transmit JunOS as well: flow-label-receive Advertise capability to pop Flow Label in receive direction to remote PE flow-label-receive-static Pop Flow Label from PW packets received from remote PE flow-label-transmit Advertise capability to push Flow Label in transmit direction to remote PE flow-label-transmit-static Push Flow Label on PW packets sent to remote PE RP/0/RP0/CPU0:r14.labxtx01.us.(config-l2vpn-pwc-mpls)#do show l2vpn xconnect interface Te0/2/0/3/7.1000 detail .. PW: neighbor 204.42.110.29, PW ID 1290, state is up ( established ) PW class ethernet-ccc, XC ID 0xa0000025 Encapsulation MPLS, protocol LDP Source address 204.42.110.15 PW type Ethernet, control word disabled, interworking none PW backup disable delay 0 sec Sequencing not set LSP : Up Load Balance Hashing: src-dst-ip Flow Label flags configured (Tx=1,Rx=0), negotiated (Tx=1,Rx=0) .... ytti () r28 labxtx01 us bb# run show l2circuit connections interface et-0/0/54:3.0 ... Neighbor: 204.42.110.15 Interface Type St Time last up # Up trans et-0/0/54:3.0(vc 1290) rmt Up Mar 20 04:06:45 2020 7 Remote PE: 204.42.110.15, Negotiated control-word: No Incoming label: 585, Outgoing label: 24003 Negotiated PW status TLV: No Local interface: et-0/0/54:3.0, Status: Up, Encapsulation: ETHERNET Description: BD: wmccall ixia 1-1 Flow Label Transmit: No, Flow Label Receive: Yes ... I didn't push bits, but at least I can signal unidir between ASR9k and PTX1k. -- ++ytti
Current thread:
- Re: interesting troubleshooting, (continued)
- Re: interesting troubleshooting Saku Ytti (Mar 21)
- Re: interesting troubleshooting Mark Tinka (Mar 22)
- Re: interesting troubleshooting Saku Ytti (Mar 22)
- Re: interesting troubleshooting Mark Tinka (Mar 22)
- Re: interesting troubleshooting Saku Ytti (Mar 22)
- Re: interesting troubleshooting Mark Tinka (Mar 22)
- RE: interesting troubleshooting adamv0025 (Mar 23)
- Re: interesting troubleshooting Tassos Chatzithomaoglou (Mar 21)
- Re: interesting troubleshooting Saku Ytti (Mar 21)
- Re: interesting troubleshooting Tassos Chatzithomaoglou (Mar 21)
- Re: interesting troubleshooting Saku Ytti (Mar 22)
- Re: interesting troubleshooting Mark Tinka (Mar 22)