Re: [c-nsp] BGP routes disappearing

2024-06-10 Thread Hank Nussbacher via cisco-nsp
but I also want a record of every attempt someone tried to reach one of these null0 routes. Think of something like: https://www.team-cymru.com/ty/cisco-router-traditional-bogons So I want an ACL like: ipv4 access-list log-traffic 10 permit ipv4 any any log But an ACL can't be placed

Re: [c-nsp] BGP routes disappearing

2024-06-10 Thread Brian Turnbow via cisco-nsp
alle ore 10:09 Hank Nussbacher via cisco-nsp < cisco-nsp@puck.nether.net> ha scritto: > I have a simple iBGP peer defined as follows: > > neighbor 128.139.197.146 >remote-as 378 >update-source Loopback0 >address-family ipv4 unicast > > > I ha

Re: [c-nsp] BGP routes disappearing

2024-06-10 Thread Hank Nussbacher via cisco-nsp
then the routes disappear as well after having made it into the routing table. I am obviously missing something very simple.  Clue-bat welcome. Thanks, Hank ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman

Re: [c-nsp] BGP routes disappearing

2024-06-10 Thread Gert Doering via cisco-nsp
Hi, On Mon, Jun 10, 2024 at 11:05:18AM +0300, Hank Nussbacher via cisco-nsp wrote: > If the feed sets the IP to 192.0.2.2 then the BGP routes appear in the > routing table.  If I then change the IP address on interface > GigabitEthernet0/0/0/43.1 to 192.0.2.2 then the routes disappea

Re: [c-nsp] BGP routes disappearing

2024-06-10 Thread Saku Ytti via cisco-nsp
to the BGP session over the BGP session. On Mon, 10 Jun 2024 at 11:09, Hank Nussbacher via cisco-nsp wrote: > > I have a simple iBGP peer defined as follows: > > neighbor 128.139.197.146 >remote-as 378 >update-source Loopback0 >address-family ipv4 unicast > >

[c-nsp] BGP routes disappearing

2024-06-10 Thread Hank Nussbacher via 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/

[c-nsp] MPLS TE FRR - IOS XR

2024-06-09 Thread Mohammad Khalil via cisco-nsp
/0/2:30 tt1:PopReady Is there anything missing? Note : MPLS LDP is enabled globally to ensure LFIB population. Appreciated. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive

Re: [c-nsp] vs route leaking

2024-06-08 Thread Saku Ytti via cisco-nsp
wrote: > > On Sat, 8 Jun 2024 at 18:26, Arne Larsen via cisco-nsp > > wrote: > > > >> Yes, it'd with route-target I'm trying to get it to work, and what I'm > >> trying to get rid off is the default route from the IOT vrf to be > >> imported into th

Re: [c-nsp] vs route leaking

2024-06-08 Thread Arne Larsen via cisco-nsp
Sort off, I need the default route from the vrf with the import target 64515:112, that's our leak for the shared vrf to the internet /Arne On 08/06/2024 17.31, Saku Ytti wrote: On Sat, 8 Jun 2024 at 18:26, Arne Larsen via cisco-nsp wrote: Yes, it'd with route-target I'm trying to get

Re: [c-nsp] vs route leaking

2024-06-08 Thread Saku Ytti via cisco-nsp
On Sat, 8 Jun 2024 at 18:26, Arne Larsen via cisco-nsp wrote: > Yes, it'd with route-target I'm trying to get it to work, and what I'm > trying to get rid off is the default route from the IOT vrf to be > imported into the SHARED vrf. Ok so the problem is not sharing routes between VRF

Re: [c-nsp] vs route leaking

2024-06-08 Thread Arne Larsen via cisco-nsp
if you can show what you have tried already. Cheers, James. Ursprüngliche Nachricht Am 08.06.24 08:04 um Arne Larsen via cisco-nsp schrieb : Hi all I’m struggling with an 9606 Cisco router and route leaking between vrf’s. I have 2 vrf’s with a default route

[c-nsp] vs route leaking

2024-06-08 Thread Arne Larsen via cisco-nsp
Hi all I’m struggling with an 9606 Cisco router and route leaking between vrf’s. I have 2 vrf’s with a default route that needs to imported into a 3. The default route from the one vrf’s is direct connected on the box, andthe other is via mBGP. I’ve tried several forms for import maps base

Re: [c-nsp] Cisco ASA5516-x DATAPATH-0-1648 and DATAPATH-0-1648 CPU hog

2024-06-07 Thread Lee Starnes via cisco-nsp
usage before falling off in a 10 second period. vpn-gw# sh proc cpu-usage non-zero Hardware: ASA5516 Cisco Adaptive Security Appliance Software Version 9.16(4)57 ASLR enabled, text region 56474105f000-564744cef285 PC Thread 5Sec 1Min 5Min Process 0x564743c1c050

Re: [c-nsp] Cisco ASA5516-x DATAPATH-0-1648 and DATAPATH-0-1648 CPU hog

2024-06-04 Thread harbor235 via cisco-nsp
4 at 6:53 PM Lee Starnes via cisco-nsp < > cisco-nsp@puck.nether.net> wrote: > >> Hello Everyone, >> >> I have an odd issue trying to track down. We are seeing issue whereby >> traffic just "pauses" through the ASA for about 2-4 seconds before >>

Re: [c-nsp] Cisco ASA5516-x DATAPATH-0-1648 and DATAPATH-0-1648 CPU hog

2024-06-04 Thread harbor235 via cisco-nsp
What features do you have enabled? NGFW and/or NGIPS? These features can limit the box to 450Mbps. Mike On Tue, Jun 4, 2024 at 6:53 PM Lee Starnes via cisco-nsp < cisco-nsp@puck.nether.net> wrote: > Hello Everyone, > > I have an odd issue trying to track down. We are seein

[c-nsp] Cisco ASA5516-x DATAPATH-0-1648 and DATAPATH-0-1648 CPU hog

2024-06-04 Thread Lee Starnes via cisco-nsp
2d2067bff5 0x7f2d1f88416f I did disable logging flash-bufferwrap to stop it from writing to flash. The logging process stopped using 29% CPU, but still the issue persists. Anyone got any Ideas on what the cause is and how to resolve it? Best, -Lee ___ cisco-n

Re: [c-nsp] STP over Port-channel issue

2024-05-06 Thread james list via cisco-nsp
Thanks good point on LACP Fast, we'll test it. RSTP should be in any case slower than 3 seconds with LACP FAST. Cheers James Il giorno lun 6 mag 2024 alle ore 15:22 Saku Ytti ha scritto: > On Mon, 6 May 2024 at 15:53, james list via cisco-nsp > wrote: > > > The questio

Re: [c-nsp] STP over Port-channel issue

2024-05-06 Thread Saku Ytti via cisco-nsp
On Mon, 6 May 2024 at 15:53, james list via cisco-nsp wrote: > The question: since the PO remains up, why we see this behaviour ? > are BDPU sent just over one link (ie the higher interfac e) ? Correct. > how can we solve this issue keeping this scenario ? > moving to RSTP

[c-nsp] STP over Port-channel issue

2024-05-06 Thread james list via cisco-nsp
dear experts a customer of mine has a legacy environment with 4 x Cisco 9500 (IOS XE 17.09.03) connected in a square mode with 2 links (2 per each connection) and each couple of links is considered a single virtual port (port-channel). Loops are managed with PVSTP. Two x C9500 are in DC1 while

Re: [c-nsp] vPC members use identical virtual addresses without HSRP

2024-04-24 Thread Nathan Lannine via cisco-nsp
nodes/roles. You can implement this same configuration for Nexus following the configuration documentation for VXLAN anycast gateway. Thank you, Nathan On Sun, Apr 21, 2024 at 8:55 PM Chen Jiang via cisco-nsp < cisco-nsp@puck.nether.net> wrote: > Hi! Michael > > Thanks for your

Re: [c-nsp] vPC members use identical virtual addresses without HSRP

2024-04-21 Thread Chen Jiang via cisco-nsp
Hi! Michael Thanks for your advice, I mean could 2*cisco devices support just use only one identical address? ... interface Vlan100 vrf v101 ip address virtual 192.168.100.254/24 interface Vlan101 vrf v101 ip address virtual 192.168.101.254/24 On Sun, Apr 21, 2024 at 3:24 PM

Re: [c-nsp] vPC members use identical virtual addresses without HSRP

2024-04-21 Thread Michael Lee via cisco-nsp
Cisco support VRRP as well. Sent from my iPhone > On Apr 18, 2024, at 10:08 PM, Chen Jiang via cisco-nsp > wrote: > > Hi! Experts > > I wonder if Cisco support vPC members use identical virtual addresses as > host's layer 3 gateway? > > Just like Arista or Junip

[c-nsp] vPC members use identical virtual addresses without HSRP

2024-04-18 Thread Chen Jiang via cisco-nsp
Hi! Experts I wonder if Cisco support vPC members use identical virtual addresses as host's layer 3 gateway? Just like Arista or Juniper, Arista for example: ... interface Vlan100 vrf v101 ip address virtual 192.168.100.254/24 interface Vlan101 vrf v101 ip address virtual

Re: [c-nsp] Serious Bug in Cisco's 6500 & 6800 Platforms

2024-04-09 Thread Mark Tinka via 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] Serious Bug in Cisco's 6500 & 6800 Platforms

2024-04-09 Thread Gert Doering via cisco-nsp
hi, On Tue, Apr 09, 2024 at 03:20:15PM +0200, Mark Tinka via cisco-nsp wrote: > https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ios-dos-Hq4d3tZG I'm so glad our single box with SUP-2T has been retired many years ago... (We still do have one (1) Sup720-

[c-nsp] Serious Bug in Cisco's 6500 & 6800 Platforms

2024-04-09 Thread Mark Tinka via cisco-nsp
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ios-dos-Hq4d3tZG Mark. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net

[c-nsp] CFM Configuration

2024-04-01 Thread Mohammad Khalil via cisco-nsp
-points remote PE2# PE2#ping ethernet mpid 170 domain SPCOR_DOMAIN service EVC_SRVC % No RMEP entry found in for mpid 170 at domain SPCOR_DOMAIN service EVC_SRVC, evc EVC1. Any lights would be appreciated. ___ cisco-nsp mailing list cisco-nsp

Re: [c-nsp] Firepower Threat Defense Geolocation DB

2024-03-27 Thread Justin Krejci via cisco-nsp
Also it doesn't hurt to otherwise advertise your 8805 geofeed as per: https://datatracker.ietf.org/doc/html/rfc9092 -Original Message- From: Hank Nussbacher via cisco-nsp mailto:hank%20nussbacher%20via%20cisco-nsp%20%3ccisco-...@puck.nether.net%3e>> Reply-To: Hank Nuss

Re: [c-nsp] Firepower Threat Defense Geolocation DB

2024-03-27 Thread Hank Nussbacher via cisco-nsp
On 26/03/2024 17:29, Jon Lewis via cisco-nsp wrote: Find out from Cisco where you can publish your geo-location data as per: https://www.rfc-editor.org/rfc/rfc8805.html If it is Google related, report the issue here: https://support.google.com/websearch/workflow/9308722?hl=en or define your geo

[c-nsp] Firepower Threat Defense Geolocation DB

2024-03-26 Thread Jon Lewis via cisco-nsp
I've been going back and forth with cisco support for 2 weeks on this and gotten nowhere. Does anyone know of a way to verify (and update if needed) Cisco's IP Geo data for the FTD platform? I've been trying to get support to let me download the DB files from https://software.cisco.com

[c-nsp] Teo En Ming's Notes on Basic Configuration of Cisco ASA 5516-X Firewall - Version 1

2024-03-20 Thread Turritopsis Dohrnii Teo En Ming via cisco-nsp
Subject: Teo En Ming's Notes on Basic Configuration of Cisco ASA 5516-X Firewall - Version 1 Good day from Singapore, Author: Mr. Turritopsis Dohrnii Teo En Ming Country: Singapore Date of Publication: 20 March 2024 Wednesday Document Version: 1 I have bought this refurbished/second hand/used

[c-nsp] Cisco ASA 5516-X Firewall (Open Source) Console Bootup Messages and Show Version

2024-03-18 Thread Turritopsis Dohrnii Teo En Ming via cisco-nsp
Subject: Cisco ASA 5516-X Firewall (Open Source) Console Bootup Messages and Show Version Good day from Singapore, I have bought this refurbished/second hand/used Cisco ASA 5516-X firewall with FirePOWER Services for SGD$100 at Bukit Panjang Ring Road on 17 Mar 2024 Sunday at about 8.30 PM

[c-nsp] Login Alarms

2024-02-27 Thread Mohammad Khalil via cisco-nsp
Greetings Do Cisco has similar feature to :https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/login-alarms-edit-system.html Appreciated. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-12 Thread Shawn L via cisco-nsp
at 3:24 AM Saku Ytti via cisco-nsp < cisco-nsp@puck.nether.net> wrote: > On Mon, 12 Feb 2024 at 09:44, james list wrote: > > > I'd like to test with LACP slow, then can see if physical interface > still flaps... > > I don't think that's good idea, like what would we kn

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-12 Thread Saku Ytti via cisco-nsp
e have confidence? I would suggest - turn on debugging, to see cisco emitting LACP PDU, and juniper receiving LACP PDU - do packet capture, if at all reasonable, ideally tap, but in absence of tap mirror - turn off LACP distributed handling on junos - ping on the link, ideally 0.2-0.5s interval, to

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
ated to lacp ? > > 16:39:35.813 Juniper reports LACP timeout (so problem started at > 16:39:32, (was traffic passing at 32, 33, 34 seconds?)) > 16:39:36.xxx Cisco reports interface down, long after problem has > already started > > Why Cisco reports physical interface down, I'm no

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
On Sun, 11 Feb 2024 at 17:52, james list wrote: > - why physical interface flaps in DC1 if it is related to lacp ? 16:39:35.813 Juniper reports LACP timeout (so problem started at 16:39:32, (was traffic passing at 32, 33, 34 seconds?)) 16:39:36.xxx Cisco reports interface down, long af

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
tate: CURRENT > > Ok so problem always starts by Juniper seeing 3seconds without LACP > PDU, i.e. missing 3 consecutive LACP PDU. It would be good to ping > while this problem is happening, to see if ping stops at 3s before the > syslog lines, or at the same time as syslog lines. > I

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
ng while this problem is happening, to see if ping stops at 3s before the syslog lines, or at the same time as syslog lines. If ping stops 3s before, it's link problem from cisco to juniper. If ping stops at syslog time (my guess), it's software problem. There is unfortunately log of bug surface

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
On Cisco I see physical goes down (initializing), what does that mean? While on Juniper when the issue happens I always see: show log messages | last 440 | match LACPD_TIMEOUT Jan 25 21:32:27.948 2024 MX1 lacpd[31632]: LACPD_TIMEOUT: et-0/1/5: lacp current while timer expired current Receive

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
of events here, due to no subsecond precision enabled on Cisco end. But if failure would start from interface down, it would take 3seconds for Juniper to realise LACP failure. However we can see that it happens in less than 1s, so we can determine the interface was not down first, the first

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
Hi 1) cable has been replaced with a brand new one, they said that to check an MPO 100 Gbs cable is not that easy 3) no errors reported on both side 2) here the output of cisco and juniper NEXUS1# sh interface eth1/44 transceiver details Ethernet1/44 transceiver is present type is QSFP

Re: [c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
Hi there are no errors on both interfaces (Cisco and Juniper). here following logs of one event on both side, config and LACP stats. LOGS of one event time 16:39: CISCO 2024 Feb 9 16:39:36 NEXUS1 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel101 is down (No operational

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
> > juniper-nsp mailing list juniper-...@puck.nether.net > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > -- > ++ytti -- ++ytti ___ 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] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
o the >same on the Nexus boxes. > > Regards, > > - Håvard > ___ > juniper-nsp mailing list juniper-...@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp -- ++ytti ___ cisco-nsp mailing list cisco-n

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Havard Eidnes via cisco-nsp
gards, - Håvard ___ 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] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
On Sun, 11 Feb 2024 at 13:51, james list via juniper-nsp wrote: > One think I've omit to say is that BGP is over a LACP with currently just > one interface 100 Gbs. > > I see that the issue is triggered on Cisco when eth interface seems to go > in Initializing state: Ok, so we

Re: [c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
f your interfaces on DC1 > links do not go down > > On Sun, Feb 11, 2024, 21:16 Igor Sukhomlinov via cisco-nsp < > cisco-nsp@puck.nether.net> wrote: > >> Hi James, >> >> Do you happen to run the same software on all nexuses and all MXes? >> Do the DC1 and DC2 bgp

Re: [c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
he DC1 and DC2 bgp session exchange the same amount of routing updates > across the links? > > > On Sun, Feb 11, 2024, 21:09 james list via cisco-nsp < > cisco-nsp@puck.nether.net> wrote: > >> Dear experts >> we have a couple of BGP peers over a 100 Gbs interconnec

Re: [c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
Hi One think I've omit to say is that BGP is over a LACP with currently just one interface 100 Gbs. I see that the issue is triggered on Cisco when eth interface seems to go in Initializing state: 2024 Feb 9 16:39:36 NEXUS1 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port

Re: [c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread nivalMcNd d via cisco-nsp
Can it be DC1 is connecting links over an intermediary patch panel and you face fibre disturbance? That may be eliminated if your interfaces on DC1 links do not go down On Sun, Feb 11, 2024, 21:16 Igor Sukhomlinov via cisco-nsp < cisco-nsp@puck.nether.net> wrote: > Hi James, > >

Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Saku Ytti via cisco-nsp
dropping at reliable probability BGP packets from the wire. On Sun, 11 Feb 2024 at 12:09, james list via juniper-nsp wrote: > > Dear experts > we have a couple of BGP peers over a 100 Gbs interconnection between > Juniper (MX10003) and Cisco (Nexus N9K-C9364C) in two different datace

Re: [c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread Igor Sukhomlinov via cisco-nsp
Hi James, Do you happen to run the same software on all nexuses and all MXes? Do the DC1 and DC2 bgp session exchange the same amount of routing updates across the links? On Sun, Feb 11, 2024, 21:09 james list via cisco-nsp < cisco-nsp@puck.nether.net> wrote: > Dear experts > we h

[c-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

2024-02-11 Thread james list via cisco-nsp
Dear experts we have a couple of BGP peers over a 100 Gbs interconnection between Juniper (MX10003) and Cisco (Nexus N9K-C9364C) in two different datacenters like this: DC1 MX1 -- bgp -- NEXUS1 MX2 -- bgp -- NEXUS2 DC2 MX3 -- bgp -- NEXUS3 MX4 -- bgp -- NEXUS4 The issue we see

Re: [c-nsp] [External] Re: Support for CFP2

2024-02-02 Thread Ted Pelas Johansson via cisco-nsp
Hi Rob, Sorry for the delay, yes, SO use Cisco Acacia QDD Bright 400ZR+ and DCP-404 also seems to support Cisco Acacia 100G QDD DWDM pluggable. I'm unsure about the 100G QDD DWDM spec and price, but Bright 400ZR+ can definitely cover that distance at 200G and 100G within 50 GHz. Best Regards

Re: [c-nsp] [External] Re: Support for CFP2

2024-02-02 Thread Nick Hilliard via cisco-nsp
Rob Evans via cisco-nsp wrote on 24/01/2024 23:27: Yeah, as I mentioned, there may be alternatives. Noting that the OP wanted a range of 800km+, do SO also offer a suitable pluggable for the line-side? The ones I could see from a cursory glance appear to be dispersion limited to 450km at 50GHz

Re: [c-nsp] Local switching on EVPN port

2024-02-02 Thread Mihai via cisco-nsp
*From:* cisco-nsp on behalf of Mihai via cisco-nsp *Sent:* Friday, February 2, 2024 1:05:12 PM *To:* cisco-nsp@puck.nether.net *Subject:* [c-nsp] Local switching on EVPN port Hi, On Cisco NCS I can configure local switching between two subinterfaces

Re: [c-nsp] Local switching on EVPN port

2024-02-02 Thread Catalin Dominte via cisco-nsp
Are you trying to migrate to EVPN? What are you trying to achieve? :) Catalin From: cisco-nsp on behalf of Mihai via cisco-nsp Sent: Friday, February 2, 2024 1:05:12 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Local switching on EVPN port Hi, On Cisco

[c-nsp] Local switching on EVPN port

2024-02-02 Thread Mihai via cisco-nsp
Hi, On Cisco NCS I can configure local switching between two subinterfaces/vlans by adding them to a bridge domain as below: l2vpn bridge group X bridge-domain X interface Bundle-Ether1.10 l2vpn bridge group X bridge-domain X interface Bundle-Ether1.20 Once I enable EVPN on the physical

Re: [c-nsp] Acceptable port configurations for ASR 9902 (gripe)

2024-01-31 Thread Nick Hilliard via cisco-nsp
the ASR 9902 is actually doing - it's just an example of how gearbox implementations can lead to unexpected outcomes. Nick ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http

Re: [c-nsp] Acceptable port configurations for ASR 9902 (gripe)

2024-01-31 Thread Drew Weaver via cisco-nsp
one port from each slice for each 'service'. That is just my opinion though. Thanks, -Drew -Original Message- From: Nick Hilliard Sent: Wednesday, January 31, 2024 9:06 AM To: Drew Weaver Cc: 'cisco-nsp@puck.nether.net' Subject: Re: [c-nsp] Acceptable port configurations for ASR

Re: [c-nsp] Acceptable port configurations for ASR 9902 (gripe)

2024-01-31 Thread Nick Hilliard via cisco-nsp
Drew Weaver via cisco-nsp wrote on 31/01/2024 14:00: So having a 1x100GE,1x100GE,4x25GE,10x10GE option and not a 1x100GE,1x100GE,1x100GE,10x10GE option is just... laziness I guess is how I would describe it. 4x25G is not the same as 1x100G - sounds like there's some weird gearbox stuff going

Re: [c-nsp] Acceptable port configurations for ASR 9902 (gripe)

2024-01-31 Thread Drew Weaver via cisco-nsp
up to me I would've made all of the ports on the ASR9902 available for use but bandwidth not to exceed 800Gbps total. But that is just me. -Original Message- From: cisco-nsp On Behalf Of Hank Nussbacher via cisco-nsp Sent: Saturday, January 27, 2024 2:57 PM To: cisco-nsp@puck.nether.net

Re: [c-nsp] Acceptable port configurations for ASR 9902 (gripe)

2024-01-27 Thread Hank Nussbacher via cisco-nsp
On 26/01/2024 15:49, Drew Weaver via cisco-nsp wrote: Hello, I just have a general gripe that I want to share regarding the ASR9902 and since there is nobody to talk to at Cisco about any of this anymore, I figured I would just share it here. This is an acceptable configuration: 1x100GE

[c-nsp] Acceptable port configurations for ASR 9902 (gripe)

2024-01-26 Thread Drew Weaver via cisco-nsp
Hello, I just have a general gripe that I want to share regarding the ASR9902 and since there is nobody to talk to at Cisco about any of this anymore, I figured I would just share it here. This is an acceptable configuration: 1x100GE, 1x100GE, 4x25GE, 10x10GE But this is not: 1x100GE

Re: [c-nsp] [External] Re: Support for CFP2

2024-01-24 Thread Rob Evans via cisco-nsp
lso offer a suitable pluggable for the line-side? The ones I could see from a cursory glance appear to be dispersion limited to 450km at 50GHz, or need 100GHz. Cheers, Rob _______ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.ne

Re: [c-nsp] [External] Re: Support for CFP2

2024-01-24 Thread Shawn L via cisco-nsp
e and power for the > > DSPs, and it has been difficult to cram that into QSFP28s (coherent > > optics requires a lot of signal processing). As you've already noted, > > there are products in the pipeline, but I'm not aware of any that are > > widely supported yet.

Re: [c-nsp] [External] Re: Support for CFP2

2024-01-24 Thread Rob Evans via cisco-nsp
d, > there are products in the pipeline, but I'm not aware of any that are > widely supported yet. Cisco do seem to suggest there is a QSFP-DD > using QPSK for 100G, but I've not looked too closely at it (and note > that QSFP-DD is different to QSFP28, having about three times the > ele

Re: [c-nsp] [External] Re: Support for CFP2

2024-01-24 Thread Rob Evans via cisco-nsp
(coherent optics requires a lot of signal processing). As you've already noted, there are products in the pipeline, but I'm not aware of any that are widely supported yet. Cisco do seem to suggest there is a QSFP-DD using QPSK for 100G, but I've not looked too closely at it (and note that QSFP-DD

Re: [c-nsp] [External] Re: Support for CFP2

2024-01-23 Thread Shawn L via cisco-nsp
Jockey > VBH M-1C > +1 256 824 5331 > > Office of Information Technology > The University of Alabama in Huntsville > Network Engineering > > On Fri, Jan 19, 2024 at 9:07 AM Nick Hilliard via cisco-nsp > wrote: > > > > Shawn L via cisco-nsp wrote on 19/01/2024 14:58:

Re: [c-nsp] IOS-XR unsuppressed map BGP

2024-01-21 Thread Mohammad Khalil via cisco-nsp
8.64.0 10.1.45.50 0 5 i *> 192.168.64.0/23 10.1.45.5 0 5 i *> 192.168.65.0 10.1.45.50 0 5 i ____ From: cisco-nsp on behalf of Harold Ritter (hritter) via cisco-nsp

Re: [c-nsp] IOS-XR unsuppressed map BGP

2024-01-21 Thread Harold Ritter (hritter) via cisco-nsp
, Harold De : cisco-nsp de la part de Toje TJ via cisco-nsp Date : samedi, 20 janvier 2024 à 08:28 À : cisco-nsp@puck.nether.net Objet : [c-nsp] IOS-XR unsuppressed map BGP Good day,. Apologize if I ask the wrong question or anything, I just wondering how to configure an unsuppressed map

Re: [c-nsp] ASR9000 QoS counters on LAG

2024-01-20 Thread Saku Ytti via cisco-nsp
raffic to drop during fabric congestion. -- ++ytti ___ 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] ASR9000 QoS counters on LAG

2024-01-20 Thread Ross Halliday via cisco-nsp
Moving to qos-group for egress classes got me the result I was looking for. Thank you very much! Cheers Ross -Original Message- From: cisco-nsp On Behalf Of Ross Halliday via cisco-nsp Sent: Saturday, January 20, 2024 4:44 PM To: Saku Ytti Cc: cisco-nsp@puck.nether.net Subject: Re

Re: [c-nsp] ASR9000 QoS counters on LAG

2024-01-20 Thread Ross Halliday via cisco-nsp
estigate the use of "qos-group". Thanks Ross ___ 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] IOS-XR unsuppressed map BGP

2024-01-20 Thread Toje TJ via cisco-nsp
this question. Regards. TP ___ 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] C2C ASR9K

2024-01-19 Thread Mohammad Khalil via cisco-nsp
Thanks, Harold, for the great insight , actually I missed configuring the /32 route : ) My bad. From: Harold Ritter (hritter) Sent: Friday, January 19, 2024 6:51 PM To: Mohammad Khalil ; cisco-nsp@puck.nether.net Subject: Re: C2C ASR9K Hi Mohammad, XR

Re: [c-nsp] [External] Re: Support for CFP2

2024-01-19 Thread Hunter Fuller via cisco-nsp
d then use a transponder closer to the DWDM gear, as Nick suggested. -- Hunter Fuller (they) Router Jockey VBH M-1C +1 256 824 5331 Office of Information Technology The University of Alabama in Huntsville Network Engineering On Fri, Jan 19, 2024 at 9:07 AM Nick Hilliard via cisco-nsp wrote: >

Re: [c-nsp] C2C ASR9K

2024-01-19 Thread Harold Ritter (hritter) via cisco-nsp
the update-source on both CE2 and CE7. For instance on CE2: neighbor 10.1.100.7 update-source lo0 Regards, Harold De : cisco-nsp de la part de Mohammad Khalil via cisco-nsp Date : vendredi, 19 janvier 2024 à 06:00 À : cisco-nsp@puck.nether.net Objet : [c-nsp] C2C ASR9K Greetings I am trying

Re: [c-nsp] Support for CFP2

2024-01-19 Thread Nick Hilliard via cisco-nsp
Shawn L via cisco-nsp wrote on 19/01/2024 14:58: The pluggable optic must be DWDM 1530 to 1563 nm with QPSK modulation that fits 50Ghz (~31 to 35Gbaud) and a launch power of ZR+ 0dBm. The customer channel should have Rx: Max <-10 dBm/Ch and Tx: Min: >–5 dBm/Ch to Max: <+ 6.5dBm/Ch

Re: [c-nsp] Support for CFP2

2024-01-19 Thread Nick Hilliard via cisco-nsp
Shawn L via cisco-nsp wrote on 19/01/2024 14:35: At $dayjob we're working on turning up a 100G connection with a provider. At this point, it looks like the only optic that's meets their criteria is a CFP2. sounds like metro 100G connectivity. What sort of distances are involved

Re: [c-nsp] Support for CFP2

2024-01-19 Thread Shawn L via cisco-nsp
t; that QSFP-100G-ER4L-S may be compatible with what you are looking for. > > Regards, > Nathan > _______ 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] Support for CFP2

2024-01-19 Thread Nathan Lannine via cisco-nsp
In particular, the page I linked (and I may just not be understanding correctly) seems to be saying that QSFP-100G-ER4L-S may be compatible with what you are looking for. Regards, Nathan ___________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.

[c-nsp] Support for CFP2

2024-01-19 Thread Shawn L via cisco-nsp
can use to convert it somehow. Thanks Shawn ___ 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] C2C ASR9K

2024-01-19 Thread Mohammad Khalil via cisco-nsp
ipv4 vrf CUST redistribute static exit-address-family Nothing on the C except for a default route , is there anything I am missing? LDP is functioning well along the path. Appreciated. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https

Re: [c-nsp] ASR9000 QoS counters on LAG

2024-01-19 Thread Saku Ytti via cisco-nsp
On Fri, 19 Jan 2024 at 05:10, Ross Halliday via cisco-nsp wrote: > We've inherited some older ASR9000 systems that we're trying to support > in-place. The software version on this one router is fairly old at 6.1.4. > Driving it are a pair of RSP440-SE. The line cards are A9K-

[c-nsp] ASR9000 QoS counters on LAG

2024-01-18 Thread Ross Halliday via cisco-nsp
-action drop ! ! class DSCP-Management priority level 3 police rate 200 mbps conform-action transmit exceed-action drop ! ! class class-default ! end-policy-map ! ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https

Re: [c-nsp] Pnet XRV 6.6.2

2023-12-27 Thread Mohammad Khalil via cisco-nsp
It was interface mapping issue , G0/0/0/0 is actually G0/0/0/2 Thanks everyone. From: cisco-nsp on behalf of Mohammad Khalil via cisco-nsp Sent: Wednesday, December 27, 2023 3:42 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Pnet XRV 6.6.2 Greetings I have

[c-nsp] Pnet XRV 6.6.2

2023-12-27 Thread Mohammad Khalil via cisco-nsp
ShutdownDown default Is there anything I should do to resolve this? Appreciated. ___ 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] ASR9901 licensing configuration

2023-12-22 Thread Shawn L via cisco-nsp
an interface / default route (router isn't in production yet, need to get all the little things resolved first) was the key. I'm not sure if it was because it's slow at Cisco right before Christmas or what, but I have to say this was one of the fastest tickets I've ever seen. On Fri, Dec 22, 2023 at 11

Re: [c-nsp] ASR9901 licensing configuration

2023-12-22 Thread Drew Weaver via cisco-nsp
Good luck is the right response. They insist that our ASR9902 is an ASR9903 at TAC every time I open a ticket. It's getting old. -Original Message- From: cisco-nsp On Behalf Of Hank Nussbacher via cisco-nsp Sent: Friday, December 22, 2023 2:11 AM To: cisco-nsp@puck.nether.net Subject

Re: [c-nsp] ASR9901 licensing configuration

2023-12-21 Thread Hank Nussbacher via cisco-nsp
On 21/12/2023 22:35, Shawn L via cisco-nsp wrote: Running on IOS-XR 7.5.2 I get: RP/0/RSP0/CPU0:GP1#license smart ? deregister De-register Device from Cisco Cloud mfg Factory license reservation feature registerRegister Device With Cisco Cloud renew Renewal Message

[c-nsp] ASR9901 licensing configuration

2023-12-21 Thread Shawn L via cisco-nsp
I have a new ASR9901 and this is my first foray into Cisco's smart licensing. Can anyone point me in the right direction? I've found numerous cisco docs for configuring it, but the commands don't seem to be present on my router. For example, the ASR9k documentation (I cannot seem to find 9901

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-21 Thread Drew Weaver via cisco-nsp
I might just be using the quirkiest products in their lineup but if you have to upgrade fpd and reload line cards 8 times to get the firmware to upgrade it seems like the support better be pristine. -Original Message- From: cisco-nsp On Behalf Of Aaron1 via cisco-nsp Sent: Thursday

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-21 Thread Aaron1 via cisco-nsp
Agreed, often I’ve started a TAC case and also started an email thread with NANOG, juniper nsp or cisco nsp mail lists…. Often the community comes back faster than TACs. …and without needing RSI or show tech… just a pointed response to the issue. Love it Aaron > On Dec 21, 2023, at 1:21

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-20 Thread Saku Ytti via cisco-nsp
On Thu, 21 Dec 2023 at 09:21, Hank Nussbacher via cisco-nsp wrote: > It used to be TAC was a main selling card of Cisco vs competitors. Not > any longer :-( Don't remember them ever being relatively or absolutely good. Having one support channel for all requests doesn't work, becau

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-20 Thread Hank Nussbacher via cisco-nsp
On 20/12/2023 17:31, Drew Weaver via cisco-nsp wrote: Only a week? I have found this list far more helpful than TAC, which usually takes 2-3 weeks to request all the necessary logs, with commands that don't work. It used to be TAC was a main selling card of Cisco vs competitors. Not any

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-20 Thread Drew Weaver via cisco-nsp
, -Drew -Original Message- From: cisco-nsp On Behalf Of Drew Weaver via cisco-nsp Sent: Wednesday, December 20, 2023 11:02 AM To: 'Mouniri Mdahoma' Cc: 'cisco-nsp@puck.nether.net' Subject: Re: [c-nsp] ASR9902 fpd upgrade admin show alarms brief Wed Dec 20 11:08:22.652 EST % No entries

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-20 Thread Drew Weaver via cisco-nsp
admin show alarms brief Wed Dec 20 11:08:22.652 EST % No entries found. From: Mouniri Mdahoma Sent: Wednesday, December 20, 2023 10:59 AM To: Drew Weaver Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] ASR9902 fpd upgrade Hello What is the output of the following command #admin show alarms

Re: [c-nsp] ASR9902 fpd upgrade

2023-12-20 Thread Mouniri Mdahoma via cisco-nsp
Hello What is the output of the following command #admin show alarms brief Le mer. 20 déc. 2023, 16:32, Drew Weaver via cisco-nsp < cisco-nsp@puck.nether.net> a écrit : > Hello, > > I've had a TAC case open on this for more than a week but after we > upgraded an ASR9902

  1   2   3   4   5   6   7   8   9   10   >