Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We have an ASR1001X running BGP over an ethernet link to our MPLS provider. We have had occasional outages where BGP bounces and we believe this is being caused by micro-bursts (historical logs don't show pattern of over-utilization).
The only drop...
According to the BGP Best Path Selection Algorithm:
Paths from an external BGP (eBGP) neighbor if the local autonomous system (AS) appears in the AS_PATH. Such paths are denied upon ingress into the router and are not even installed in the BGP Routin...
I'm going to be making some BGP changes soon configuring adding the BGP neighbor "send-community both" as well as the "ip bgp-community new-format". I've tried looking in the documentation but I cannot find whether or not these changes would affect t...
I have a BGP route, being learned from a Route-Reflector-Client, that should be advertised into OSPF but it is not. It shows redistributing via ospf, but I'm unable to see it in the OSPF database and when I go the next-hop router it is not being lear...
One one of our Cisco 6509s I've globally enabled QoS and set a port to "trust cos". However when I look at the queueing for that interface, I notice that the receive queue thresholds have not changed to the default. I'm kind of new to QoS so I'm not ...
Yes, that was my understanding as well. I thought I saw the traffic between endpoints as CS0, but upon further investigation it was ICMP traffic used during troubleshooting at the time of the BGP flap. The BGP traffic doesn't show up in Netflow at al...
I think I would need to use replace-as to supress the fake-as, since that is the one overlapping. I'm going to throw it in the lab tomorrow and I may have a better explanation.
The situation that I'm facing is occurring with an MPLS migration. We already had unique ASN for each site with Carrier A. We've started turning up Carrier B sites, but they assigned a new (and overlapping) ASN for all the sites. To accommodate this ...
I think I may have found an issue...I had configured trust dscp and trust cos on different interfaces on the same ASIC. When I went back and removed the trust dscp from interfaces on that ASIC, my default rcv-queue thresholds were there.
