Hi Tony,
Have you tried to apply a route-map through the ip local policy
route-map route-map command? This command should apply the route-map
to all your locally generated traffic. I don't know wether this also
works for your ES20+ card and ARP traffic. It's worth the try.
If this doesn't work
On 30/05/2014 01:37, Shane Heupel wrote:
Hoping someone can help with a configuration I'm having trouble with.
Trying to pass untagged traffic from cust-site-A to cust-site-B.
Thought the configuration would be straight forward but traffic is not
passing between host. I'm sure I'm missing
I originally had it configured that way but changed it so I could do some
troubleshooting because they were unable to pass any traffic. I plan to put it
back once we get traffic going. I guess my question is how does the interfaces
between the ASR901 and 9010 need to be configured. I had TAC
From what I've read, the netflow export is the only thing you can't do on
the management port. Everything else (ntp, tacacs, snmp, syslog, ssh, file
copy, whatever) should work. Granted you need to put it in a VRF, but
that's trivial since it's local.
Chuck
-Original Message-
From:
This would be simple with mpls:
asr901:
int gi0/5
xconnect ip.of.asr9010 encapsulation mpls
asr9010:
int gi0/0/0/0
l2transport
l2vpn
xconnect group cust-vpws
p2p vpws-cust-a
interface GigabitEthernet0/0/0/0
neighbor ipv4 ip.of.asr901 pw-id
If you're using a tagged port at
Hi Gert,
On 26.05.2014 10:06 AM, Gert Doering wrote:
There is a bit of BGP churn on this router, but all BGP peers are up
(so no updates to some members of an update-group are stuck) and all
BGP table versions in show ip b su are much higher than 681600139 -
OTOH, one or the other peer is
There are a couple of bugs.
Not sure of the bug ID but there is one that only happens if you have a shut
down peer.
It causes a memory leak.
Mack McBride | Network Architect | ViaWest, Inc.
O: 720.891.2502 | mack.mcbr...@viawest.com | www.viawest.com | LinkedIn |
Twitter | YouTube
Hi,
On Fri, May 30, 2014 at 06:08:08PM +, Mack McBride wrote:
There are a couple of bugs.
Not sure of the bug ID but there is one that only happens if you have a shut
down peer.
It causes a memory leak.
Yeah, this one I know. Very funny. (But supposedly fixed quite a while
ago in all
That sounds like the bug I mentioned.
Eliminating the shutdown peer fixes the issue in the bug I mentioned.
Mack McBride | Network Architect | ViaWest, Inc.
O: 720.891.2502 | mack.mcbr...@viawest.com | www.viawest.com | LinkedIn |
Twitter | YouTube
-Original Message-
From: Gert
Hi,
On Fri, May 30, 2014 at 07:57:11PM +, Mack McBride wrote:
That sounds like the bug I mentioned.
Eliminating the shutdown peer fixes the issue in the bug I mentioned.
Yeah, but that bug (the memory leak if peers are down) has long been
fixed - so *this* is a new one :-)
gert
--
USENET
I ran into this same issue. In my case the carrier only took CS0 and
CS6. No issues with ARP (CS6) but it turned out IPv6 neighbour
discovery is marked CS7. I am still without a solution...
On 29/May/2014 11:37 p.m., Ryan West wrote:
First thing, that's a bad carrier. Second, they are
11 matches
Mail list logo
