[c-nsp] router suggestion for backup link
Hi, Can anyone provide suggestion outside cisco ASR/ISR router model that can handle 2.5gb throughput and also able to scale to 5gb? Currently this router will perform static routes but we may switch to BGP down the path to accept default route(s). Both ASR/ISR seem to be little pricey/feature rich for what we need for our backup 2gb link. Any feedback will be appreciated. -- sky ___ 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] LACP Nexus vpc down after server reboot
We have had some issues with VPC over non networking hw. Works great towards our Juniper switches but is a pain to all things EMC more or less. Its hit and miss towards some IBM AIX machines. It gets broken quite often when they patch the AIX machines. I would be abit careful running VPC to non networking hw and test a lot not just initialization of the channel but also failover, redundancy tests and so on. //Gustav -Ursprungligt meddelande- Från: cisco-nsp För Satish Patel Skickat: den 9 juli 2018 18:44 Till: Cisco Network Service Providers Ämne: [c-nsp] LACP Nexus vpc down after server reboot I have Nexus 3064 with vPC configuration and some strange issue going on, I have configured LACP 802.3ad bonding with my Linux server everything was good and working great but as soon as i reboot server i found on Nexus switch vpc is down N3K(config-if)# sh vpc 137 vPC status -- id Port Status Consistency Reason Active vlans -- -- --- -- 137 Po137 down* success success- But as soon as i do "shut/no shut" on po137 interface it works and vpc brought up. is this normal behavior on Cisco Nexus switches? I am using many IOS switch in same config and it works but with vpc i am having issue. This is my switch config, i am running nexus 7.0.x NX-OS interface port-channel137 switchport mode trunk switchport trunk native vlan 40 switchport trunk allowed vlan 10,20,30,100 speed 1 vpc 137 on Linux side i have following config. BONDING_OPTS="mode=4 miimon=500 downdelay=1000 lacp_rate=1" ___ 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/
[c-nsp] LACP Nexus vpc down after server reboot
I have Nexus 3064 with vPC configuration and some strange issue going on, I have configured LACP 802.3ad bonding with my Linux server everything was good and working great but as soon as i reboot server i found on Nexus switch vpc is down N3K(config-if)# sh vpc 137 vPC status -- id Port Status Consistency Reason Active vlans -- -- --- -- 137 Po137 down* success success- But as soon as i do "shut/no shut" on po137 interface it works and vpc brought up. is this normal behavior on Cisco Nexus switches? I am using many IOS switch in same config and it works but with vpc i am having issue. This is my switch config, i am running nexus 7.0.x NX-OS interface port-channel137 switchport mode trunk switchport trunk native vlan 40 switchport trunk allowed vlan 10,20,30,100 speed 1 vpc 137 on Linux side i have following config. BONDING_OPTS="mode=4 miimon=500 downdelay=1000 lacp_rate=1" ___ 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] NAT logging ASR1k
You wanna see the juniper configs for your ASR1006? Not sure why we didn't use netflow. I guess because syslog worked and that's where the docs led me Aaron > On Jul 9, 2018, at 2:52 AM, Ring Bit wrote: > > Hi Aaron, > > Could you post the nat configs? > > Why not use Netflow? > > Thanks. > T. > >> Sent: Sunday, July 08, 2018 at 10:14 PM >> From: "Aaron Gould" >> To: ring...@mail.com >> Cc: cisco-nsp@puck.nether.net >> Subject: Re: [c-nsp] NAT logging ASR1k >> >> Bulk logging and port block allocation (PBA)? >> >> https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/xe-3s/nat-xe-3s-book/iadnat-bpa.html >> >> I do PBA in groups of 100 ports on my CGNAT deployment (juniper) and use >> syslog to log. Using port block allocation caused the syslogging to slow >> down significantly >> >> Aaron >> >>> On Jul 8, 2018, at 10:12 AM, ring...@mail.com wrote: >>> >>> Hi everybody, >>> >>> Have an ASR 1006 doing NAT translations, it is having around 300k+ and >>> wanted to ask for a recommendation about logging those NAT translations. >>> >>> Tried it with a collector via Netflow v9 with the export command "ip nat >>> log translationsflow-export v9 udp destination" command the CPU spiked to >>> 100%. >>> >>> Is there a recommendation as a workaround or have alternative solution >>> which is easy on resources to those massive NAT translations? >>> >>> Thanks, >>> T. >>> ___ >>> 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] NAT logging ASR1k
Hi Patrick, I'm interested about the config you are using. T. > Sent: Monday, July 09, 2018 at 12:46 AM > From: "Patrick Cole" > To: ring...@mail.com > Cc: cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] NAT logging ASR1k > > T, > > We are having around 200-300k non-CGNAT translations on ASR1001-X and using > Netflow Event > Logging. The CPU on average is less than 20%. > > Regards, > > Patrick > > Sun, Jul 08, 2018 at 05:12:29PM +0200, ring...@mail.com wrote: > > > Hi everybody, > > > > Have an ASR 1006 doing NAT translations, it is having around 300k+ and > > wanted to ask for a recommendation about logging those NAT translations. > > > > Tried it with a collector via Netflow v9 with the export command "ip nat > > log translationsflow-export v9 udp destination" command the CPU spiked to > > 100%. > > > > Is there a recommendation as a workaround or have alternative solution > > which is easy on resources to those massive NAT translations? > > > > Thanks, > > T. > > ___ > > 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] NAT logging ASR1k
Hi Aaron, Could you post the nat configs? Why not use Netflow? Thanks. T. > Sent: Sunday, July 08, 2018 at 10:14 PM > From: "Aaron Gould" > To: ring...@mail.com > Cc: cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] NAT logging ASR1k > > Bulk logging and port block allocation (PBA)? > > https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/xe-3s/nat-xe-3s-book/iadnat-bpa.html > > I do PBA in groups of 100 ports on my CGNAT deployment (juniper) and use > syslog to log. Using port block allocation caused the syslogging to slow > down significantly > > Aaron > > > On Jul 8, 2018, at 10:12 AM, ring...@mail.com wrote: > > > > Hi everybody, > > > > Have an ASR 1006 doing NAT translations, it is having around 300k+ and > > wanted to ask for a recommendation about logging those NAT translations. > > > > Tried it with a collector via Netflow v9 with the export command "ip nat > > log translationsflow-export v9 udp destination" command the CPU spiked to > > 100%. > > > > Is there a recommendation as a workaround or have alternative solution > > which is easy on resources to those massive NAT translations? > > > > Thanks, > > T. > > ___ > > 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/
