Routing

last person joined: 4 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.

  • 1.  Please help explain this to me..

    Posted 04-30-2014 02:02

    In a QoS situation running BFD, Why would Drops in QoS cause BFD to trigger and drop the circuit? IS this possible? I didnt think it was...

     

    This is the only thing I can find, No LEC issues, No router issues, No nothing other than seeing drops in QoS..

     

    The circuit is as configured..

     

    Interface Config:
    interfaces ae0 description "AGG: IPVPNEXT: XXX1.SAC1-PO4-GE (INTRAHUB, XXXYYY)"
    interfaces ae0 enable
    interfaces ae0 vlan-tagging
    interfaces ae0 mtu 9134
    interfaces ae0 encapsulation flexible-ethernet-services
    interfaces ae0 aggregated-ether-options minimum-links 1
    interfaces ae0 aggregated-ether-options link-speed 1g
    interfaces ae0 aggregated-ether-options lacp active
    interfaces ae0 unit 932 description "CUSTOMER: VPN-XXXYYY-1: XXXXXXXXX Insurance Reno (829: XXXYYY16429, EON: 800/4, XXXYYY043982VRP)"
    interfaces ae0 unit 932 vlan-id 932
    interfaces ae0 unit 932 family inet mtu 1500
    interfaces ae0 unit 932 family inet no-redirects
    interfaces ae0 unit 932 family inet filter input ae0.932-inet-i
    interfaces ae0 unit 932 family inet policer input ae0.932-in
    interfaces ae0 unit 932 family inet address 172.25.0.5/30

    Aggregated Ethernet Constituents:
    interfaces ge-2/2/0 description "TRUNK: IPVPNEXT: XXX1.SAC1-GE3/9-GE (INTRAHUB, XXXYYY)"
    interfaces ge-2/2/0 gigether-options 802.3ad ae0
    interfaces ge-4/1/0 description "TRUNK: IPVPNEXT: XXX1.SAC1-GE3/3-GE (INTRAHUB, XXXYYY)"
    interfaces ge-4/1/0 gigether-options 802.3ad ae0

    Input Filter:
    firewall family inet filter ae0.932-inet-i term EF_DSCP from dscp 46
    firewall family inet filter ae0.932-inet-i term EF_DSCP then policer ae0.932.EF-i
    firewall family inet filter ae0.932-inet-i term EF_DSCP then count EF.rx-ae0.932-inet-i
    firewall family inet filter ae0.932-inet-i term EF_DSCP then loss-priority low
    firewall family inet filter ae0.932-inet-i term EF_DSCP then forwarding-class EF
    firewall family inet filter ae0.932-inet-i term AF_DSCP from dscp 26
    firewall family inet filter ae0.932-inet-i term AF_DSCP then policer ae0.932.AF-i
    firewall family inet filter ae0.932-inet-i term AF_DSCP then count AF.rx-ae0.932-inet-i
    firewall family inet filter ae0.932-inet-i term AF_DSCP then loss-priority low
    firewall family inet filter ae0.932-inet-i term AF_DSCP then forwarding-class AF
    firewall family inet filter ae0.932-inet-i term BE then count BE.rx-ae0.932-inet-i
    firewall family inet filter ae0.932-inet-i term BE then loss-priority high
    firewall family inet filter ae0.932-inet-i term BE then forwarding-class VPN-BE

    Input Policer:
    firewall policer ae0.932-in logical-interface-policer
    firewall policer ae0.932-in if-exceeding bandwidth-limit 100m
    firewall policer ae0.932-in if-exceeding burst-size-limit 3750000
    firewall policer ae0.932-in then discard

    Policer ae0.932.EF-i
    firewall policer ae0.932.EF-i filter-specific
    firewall policer ae0.932.EF-i if-exceeding bandwidth-limit 10m
    firewall policer ae0.932.EF-i if-exceeding burst-size-limit 375k
    firewall policer ae0.932.EF-i then discard

    Policer ae0.932.AF-i
    firewall policer ae0.932.AF-i filter-specific
    firewall policer ae0.932.AF-i if-exceeding bandwidth-limit 60m
    firewall policer ae0.932.AF-i if-exceeding burst-size-limit 2250000
    firewall policer ae0.932.AF-i then loss-priority high
    firewall policer ae0.932.AF-i then forwarding-class VPN-BE

    Remaining Config:
    policy-options policy-statement XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-export term DEFAULT then default-action reject
    policy-options policy-statement XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-export term L3VPN then community add XXXYYY-1-XXXXXXXXX-2005111119-L3VPN-mesh
    policy-options policy-statement XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-export term L3VPN then default-action accept
    policy-options policy-statement XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-import term L3VPN from community XXXYYY-1-XXXXXXXXX-203319-L3VPN-mesh
    policy-options policy-statement XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-import term L3VPN then accept
    policy-options policy-statement XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-import term final then reject
    policy-options community XXXYYY-1-XXXXXXXXX-2222361111111119-L3VPN-mesh members target:6745:1100XXXYYY
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN instance-type vrf
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN interface ae0.859
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN interface ae0.932
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN interface lo0.XXXYYY
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN route-distinguisher 67.17.97.61:XXXYYY
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN vrf-import [ VPN-import XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-import ]
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN vrf-export [ VPN-export XXXYYY-1-XXXXXXXXX-2005036519-L3VPN-export ]
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN vrf-table-label
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN routing-options maximum-prefixes 5000 threshold 95
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN routing-options router-id 172.16.4.87
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN routing-options auto-export
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp path-selection always-compare-med
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp family inet any
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYtype external
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYlog-updown
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYimport BGP-import
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYfamily inet any prefix-limit maximum 2000
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYexport [ BGP-export XXXYYY-1-San_Francisco-20000000-export ]
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYpeer-as 65105
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYas-override
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYneighbor 172.25.0.18 bfd-liveness-detection minimum-interval 999
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group San_Francisco-XXXYYYneighbor 172.25.0.18 bfd-liveness-detection multiplier 5
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY type external
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY log-updown
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY import BGP-import
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY family inet any prefix-limit maximum 2000
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY export [ BGP-export XXXYYY-1-Reno-20050411111111-export ]
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY peer-as 65101
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY as-override
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY neighbor 172.25.0.6 bfd-liveness-detection minimum-interval 1999
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY neighbor 172.25.0.6 bfd-liveness-detection multiplier 6

    BGP Config:
    routing-instances 13877-1-CustomerExperienceLab-L3VPN protocols bgp group SOHO-Phoenix_BACKUP-20051 neighbor 172.25.0.6 hold-time 64800
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY neighbor 172.25.0.6 bfd-liveness-detection minimum-interval 1999
    routing-instances XXXYYY-1-XXXXXXXXX-2005036519-L3VPN protocols bgp group Reno-XXXYYY neighbor 172.25.0.6 bfd-liveness-detection multiplier 6



  • 2.  RE: Please help explain this to me..

    Posted 04-30-2014 02:22

    I finally was able to find this in our Syslog server

     

    Apr 29 05:01:39 pr4.sac1 bfdd[1355]: BFDD_TRAP_SHOP_STATE_DOWN: local discriminator: 2086, new state: down, interface: ae0.932, peer addr: 172.25.0.6
    Apr 29 05:01:39 pr4.sac1 rpd[1892]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 172.25.0.6 (External AS 65101) changed state from Established to Idle (event BfdDown)
    Apr 29 05:02:16 pr4.sac1 rpd[1892]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 172.25.0.6 (External AS 65101) changed state from OpenConfirm to Established (event RecvKeepAlive)

     

    This definition is soooo generic to me I have no idea what it means..

     

    BFDD_TRAP_SHOP_STATE_DOWN

    System Log Message

    local discriminator: session-id, new state: state, interface: pip-interface, peer addr: remote-peer

    Description

    The state changed to 'down' or 'admin down' for the indicated Bidirectional Forwarding Detection process (bfdd) session.

    Type

    Event: This message reports an event, not an error



  • 3.  RE: Please help explain this to me..
    Best Answer

    Posted 04-30-2014 04:22

    I figured it out...

     

    The explanaiton was soo generic it took me forever..

     

    But what you do it set a trace option to look for PPM-PACKET 

     

    When BFD flaps,check the BFD traceoptions file and look for messages similar to the following:


    Apr 29 22:01:25 PPM Trace: BFD neighbor discr 0x2d (IFL 137) timeout
    Apr 29 22:01:25 PPM Trace: BFD neighbor discr 0x26 (IFL 123) timeout

     

    Here we see that the BFD neighbor on various interfaces has timed out. This means that a BFD hello was not received  from the neighbor