Re: [c-nsp] asr920 tag translation 1-to-2 unsupported?
Yep - that absolutely works, thank you! On 4/20/20 6:29 PM, Tan Shao Yi wrote: > Hi Mike, > > Would this work for you? > > bridge-domain X > > interface A > service instance 1 ethernet > encapsulation dot1q 131 > rewrite ingress tag pop 1 symmetric > bridge-domain X > > interface B > service instance 1 ethernet > encapsulation dot1q 313 second-dot1q 10 > rewrite ingress tag pop 2 symmetric > bridge-domain X > > Hope this helps. > > Regards, > ShaoYi Tan > > On 21/4/20, 3:51 AM, "cisco-nsp on behalf of Mike" > mike+li...@yourtownonline.com> wrote: > > Hello, > > I have an ASR920 and I am trying to translate input dog1q tag > '131' to dual-tagged '313,10'. My intention is to the bridge this over > to another port that expects these frames on 313,10. But when I try > configuring the translation, I get the following: > > Router(config)#interface gi0/0/0 > Router(config-if)#service instance 1 ethernet > Router(config-if-srv)#encapsulation dot1q 131 > Router(config-if-srv)#rewrite ingress tag translate 1-to-2 dot1q 313 > second-dot1q 10 symmetric > 1_TO_2 not supported on EFP > This rewrite ingress on ServInst 1(Gi0/0/0) is not allowed by platform > or other components. > > > Can anyone tell me how to get this done or is this just not possible > on asr920? > > ___ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] asr920 tag translation 1-to-2 unsupported?
Hi Mike, Would this work for you? bridge-domain X interface A service instance 1 ethernet encapsulation dot1q 131 rewrite ingress tag pop 1 symmetric bridge-domain X interface B service instance 1 ethernet encapsulation dot1q 313 second-dot1q 10 rewrite ingress tag pop 2 symmetric bridge-domain X Hope this helps. Regards, ShaoYi Tan On 21/4/20, 3:51 AM, "cisco-nsp on behalf of Mike" wrote: Hello, I have an ASR920 and I am trying to translate input dog1q tag '131' to dual-tagged '313,10'. My intention is to the bridge this over to another port that expects these frames on 313,10. But when I try configuring the translation, I get the following: Router(config)#interface gi0/0/0 Router(config-if)#service instance 1 ethernet Router(config-if-srv)#encapsulation dot1q 131 Router(config-if-srv)#rewrite ingress tag translate 1-to-2 dot1q 313 second-dot1q 10 symmetric 1_TO_2 not supported on EFP This rewrite ingress on ServInst 1(Gi0/0/0) is not allowed by platform or other components. Can anyone tell me how to get this done or is this just not possible on asr920? ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Default Route recalculated every 60 seconds.
Hi, On Mon, Apr 20, 2020 at 08:54:27PM +, Bradley Ordner wrote: > Thanks Gert, I will now ask them to do packet capture on their side and see > if they are advertising this default to any other customer every 60 seconds. > > Something else I noticed, we only accept routes less than or equal to /18. I > noticed that many updates come in, for different prefixes. I can???t see how > the Internet could be that unstable unless there is something wrong with > their network. Wonder what is the norm when seeing so many prefixes change. The Internet is huge - 70.000 networks(!) connected together. Things are rebuilt and changed all over the place all the time, and links and devices fail and get repaired all over the time. So yes, there's a constant stream of BGP updates. Google for Geoff Huston. He's done a number of very good presentation on the dynamics of BGP updates over time. gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Default Route recalculated every 60 seconds.
Thanks Gert, I will now ask them to do packet capture on their side and see if they are advertising this default to any other customer every 60 seconds. Something else I noticed, we only accept routes less than or equal to /18. I noticed that many updates come in, for different prefixes. I can’t see how the Internet could be that unstable unless there is something wrong with their network. Wonder what is the norm when seeing so many prefixes change. Brad Sent from my iPhone > On 20 Apr 2020, at 7:55 pm, Gert Doering wrote: > > Hi, > >> On Mon, Apr 20, 2020 at 09:36:55AM +, Bradley Ordner wrote: >> They have told me they have no other issues with other customers and same >> config, but this could be a bug between different IOS versions because I am >> running IOS-XE and they may be running XR as they have a ASR9K. > > Strictly speaking, there is no "issue", except that the counter for > "how old is the route?" on your side is being reset every minute. > > Packet forwarding works, routing is stable, no CPU churn. > > WRT "bugs between different IOS versions" - please read what I wrote > before: frequent reannouncements of a single route *can not* be triggered > by anything on your side. There is nothing in the BGP protocol which > would enable this. (If it happens for *all* routes, it could be a > soft reconfig request going awry, but this not what you see) > > gert > > -- > "If was one thing all people took for granted, was conviction that if you > feed honest figures into a computer, honest figures come out. Never doubted > it myself till I met a computer with a sense of humor." > Robert A. Heinlein, The Moon is a Harsh Mistress > > Gert Doering - Munich, Germany g...@greenie.muc.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] asr920 tag translation 1-to-2 unsupported?
Hello, I have an ASR920 and I am trying to translate input dog1q tag '131' to dual-tagged '313,10'. My intention is to the bridge this over to another port that expects these frames on 313,10. But when I try configuring the translation, I get the following: Router(config)#interface gi0/0/0 Router(config-if)#service instance 1 ethernet Router(config-if-srv)#encapsulation dot1q 131 Router(config-if-srv)#rewrite ingress tag translate 1-to-2 dot1q 313 second-dot1q 10 symmetric 1_TO_2 not supported on EFP This rewrite ingress on ServInst 1(Gi0/0/0) is not allowed by platform or other components. Can anyone tell me how to get this done or is this just not possible on asr920? ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Default Route recalculated every 60 seconds.
Hi, On Mon, Apr 20, 2020 at 09:36:55AM +, Bradley Ordner wrote: > They have told me they have no other issues with other customers and same > config, but this could be a bug between different IOS versions because I am > running IOS-XE and they may be running XR as they have a ASR9K. Strictly speaking, there is no "issue", except that the counter for "how old is the route?" on your side is being reset every minute. Packet forwarding works, routing is stable, no CPU churn. WRT "bugs between different IOS versions" - please read what I wrote before: frequent reannouncements of a single route *can not* be triggered by anything on your side. There is nothing in the BGP protocol which would enable this. (If it happens for *all* routes, it could be a soft reconfig request going awry, but this not what you see) gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Default Route recalculated every 60 seconds.
Hi James, Interesting you mention this, as someone else on Cisco Community Page was interested in the IOS version. Possibly once this design is finished the default may come from somewhere else, but I don't think I will be there when it happens. They have told me they have no other issues with other customers and same config, but this could be a bug between different IOS versions because I am running IOS-XE and they may be running XR as they have a ASR9K. I am going to ask the question and see what happens. Thanks for the info. Brad From: James Bensley Sent: Monday, 20 April 2020 6:30 PM To: Bradley Ordner ; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Default Route recalculated every 60 seconds. On Sat, 18 Apr 2020 at 07:11, Bradley Ordner wrote: > > I am about to leave an Enterprise environment due to Pre Covid-19 redundancy > and I just need to find the root cause of this issue before I leave. > > We recently built a Layer 2 Circuit over a Providers SDN Backbone so we could > get a 2Gb Internet link. We peered with this neighbor and filtered a partial > table, so we get about 3 routes. For some reason, every 30 seconds the > default route uptime resets to 00:00 in the routing table. I spoke with > Carrier, they made a few changes and one was the BGP advertisement timer. It > is now set to 60 seconds and now the default route resets every 60 seconds. > > The carrier, keeps blaming my side so I opened a Cisco TAC case and they > haven't got around to looking at it yet, probably because it really sounds > like it is the carrier side. I took some packet captures and indeed every 60 > seconds an update with the default is sent. Our router constantly accepts > this, recalculates and enters it into the routing table. > > I can't seem to figure out if this is some type of bug or not. The router has > been rebooted and is due for IOS upgrade shortly, but wanted to see if anyone > has seen this or point me in the right direction. > > Thanks > > Brad Hi Brad, Do you know if your provider uses IOS-XR on their PE? There was a bug a couple of years ago in XR (I've searched on cisco.com but can't find the BugID right now) in which XR was re-advertising the default route every 30 or 60 seconds. We had it, and if I recall correctly it wasn't being withdrawn, just a new BGP UPDATE was sent to supersede the existing route, so as other posters have said, packet capture the BGP TCP packets with your provider or use some "debug bgp" commands to see whats really going on. Also, maybe reconsider if need them to advertise a default route if you're getting a partial table from them. Cheers, James. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Default Route recalculated every 60 seconds.
On Sat, 18 Apr 2020 at 07:11, Bradley Ordner wrote: > > I am about to leave an Enterprise environment due to Pre Covid-19 redundancy > and I just need to find the root cause of this issue before I leave. > > We recently built a Layer 2 Circuit over a Providers SDN Backbone so we could > get a 2Gb Internet link. We peered with this neighbor and filtered a partial > table, so we get about 3 routes. For some reason, every 30 seconds the > default route uptime resets to 00:00 in the routing table. I spoke with > Carrier, they made a few changes and one was the BGP advertisement timer. It > is now set to 60 seconds and now the default route resets every 60 seconds. > > The carrier, keeps blaming my side so I opened a Cisco TAC case and they > haven't got around to looking at it yet, probably because it really sounds > like it is the carrier side. I took some packet captures and indeed every 60 > seconds an update with the default is sent. Our router constantly accepts > this, recalculates and enters it into the routing table. > > I can't seem to figure out if this is some type of bug or not. The router has > been rebooted and is due for IOS upgrade shortly, but wanted to see if anyone > has seen this or point me in the right direction. > > Thanks > > Brad Hi Brad, Do you know if your provider uses IOS-XR on their PE? There was a bug a couple of years ago in XR (I've searched on cisco.com but can't find the BugID right now) in which XR was re-advertising the default route every 30 or 60 seconds. We had it, and if I recall correctly it wasn't being withdrawn, just a new BGP UPDATE was sent to supersede the existing route, so as other posters have said, packet capture the BGP TCP packets with your provider or use some "debug bgp" commands to see whats really going on. Also, maybe reconsider if need them to advertise a default route if you're getting a partial table from them. Cheers, James. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
