Re: [c-nsp] NCS IOS-XR rant (was:Re: Internet border router recommendations and experiences)

[Steve Mikulasik via cisco-nsp]

Cisco's method for rolling out updates (basically stuck in the 90s) is becoming 
more and more of a liability. When evaluating vendors I have started to place 
high importance in how they handle updates as there is less and less tolerance 
for leaving anything in a unpatched state for very long. Patch management 
software should be part of the product, it shouldn't be something I need to pay 
extra to do in an efficient manner, nor should it be expected you'd build out 
some scripting solution that accounts for all the annoying oddities a vendors 
platform should have. Cisco and other vendors need to really do better to 
ensure that their customers can easily patch so their boxes are not viewed as 
security liabilities.


-Original Message-
From: cisco-nsp  On Behalf Of Mark Tinka via 
cisco-nsp
Sent: Sunday, February 26, 2023 7:55 AM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] NCS IOS-XR rant (was:Re: Internet border router 
recommendations and experiences)

CAUTION: This email originated from outside of Civeo.
Do not click links or open attachments unless you recognize the sender and know 
the content is safe.


On 2/26/23 16:44, Tarko Tikan via cisco-nsp wrote:

> Well, not so in practice.
>
> You can't issue install from http:// or any other remote URL.
>
> You have to sit around and issue "install apply" after "install
> replace" is finished. Replace is async so you have to sit around and
> poll the process.
>
> After reboot you have to reconnect to device and issue "install commit".
>
> In some cases direct upgrades from version X to Y fail so you have to
> go through this whole process twice (X to Z to Y) that takes around 2
> hours on NCS540.
>
> In some other X to Y cases there is not sufficient diskspace to
> complete "install replace".
>
> We personally have automated the whole install process via netconf and
> can workaround the quirks relevant for our platforms and versions.
> Many people can't do that or can't justify the expense (when they have
> small number of devices).
>
> Some other issues have been solved by Cisco in latest releases, I
> belive install replace can now be sync operation, maybe not on NCS540
> but on larger platforms (IOS-XR consistency between platforms is an
> issue itself).
>
> So I totally get what Mark and Gert are saying. IOS-XR is currently
> worst NOS operational experience from all large NOSes out there.

Oh gosh - it's such a shame that it's 2023 and we still have to put up with 
shoddy software maintenance processes, just because a vendor insists that their 
next generation OS core is worth the daily-use pain.

I could be okay with doing for this for about 10 - 20 nodes in the core.
But even with some level of automation (because you have to baby-sit the 
automation, especially when the vendor changes things in a bid to "improve" 
life with their OS), trying to manage this on 100's - 1,000's of nodes in the 
Metro (or anywhere, really) is just too much of a nightmare.

So you either end up with network gear running very old code because operators 
can't be asked to spend 2hrs on upgrading a single device, or simply tying up 
too many engineer hours at the expense of other projects.

Mark.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-nsp=05%7C01%7Csteve.mikulasik%40civeo.com%7C6026c96b2aa84683fd4508db1809a7f5%7C19af17147411493892e842145780331d%7C0%7C0%7C638130201987637854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oZ6pox81KyUj2bwtn9pbmXdYK3x1Jf5k4194wD0JXR4%3D=0
archive at 
https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpuck.nether.net%2Fpipermail%2Fcisco-nsp%2F=05%7C01%7Csteve.mikulasik%40civeo.com%7C6026c96b2aa84683fd4508db1809a7f5%7C19af17147411493892e842145780331d%7C0%7C0%7C638130201987637854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=arChJnDgaJLcdrhPSrW269c9GcKc3xrWMsqVhlD7C4k%3D=0

 
___
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] Experience with 9500-16X ?

[Steve Mikulasik via cisco-nsp]

--- Begin Message ---
We run the 16x and 40X. I honestly wouldn't buy them again since the other 9500 
models use the UADP 3.0 ASIC and have better buffers. The UADP 2.0 9500 
switches  split the 32MB buffer into two 16MB buffers per core, well the UADP 
3.0 9500 switches have 36M shared between both cores. I have heard that pricing 
between the 2.0 and 3.0 9500s is pretty close. I don't know why Cisco has ASICs 
that work different in the same switch series, just makes it hard to know what 
switch you are really getting.

https://www.cisco.com/c/dam/en/us/products/collateral/switches/catalyst-9500-series-switches/white-paper-c11-741484.pdf



From: cisco-nsp  On Behalf Of Michael 
Malitsky
Sent: Wednesday, September 25, 2019 9:54 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Experience with 9500-16X ?

CAUTION: This email originated from outside of Civeo.
Do not click links or open attachments unless you recognize the sender and know 
the content is safe.

Does anyone have personal experience with the Catalyst 9500 series 
(specifically interested in 16X)? Impressions, caveats?


Sincerely,
Michael Malitsky

___
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/
--- End Message ---
___
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] Has there been a Cisco network device with GE management port while other ports are FE or lower?

[Steve Mikulasik]

In my experience G0 is always a management interface.



From: cisco-nsp  On Behalf Of Martin T
Sent: Wednesday, October 24, 2018 10:27 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Has there been a Cisco network device with GE management port 
while other ports are FE or lower?

Hi,

I need to know, if GigabitEthernet0(returned by SNMP
ifDescr)/Gi0(returned by ifName) is a Management Ethernet interface or
not. My assumption is that Cisco has never made a network device,
where Management Ethernet is a 1GigE port while non-management port(s)
are Ethernet or Fast Ethernet ports. In other words, if device has any
other Gi ports besides GigabitEthernet0, then GigabitEthernet0 is
always a Management Ethernet port?


thanks,
Martin
___
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] 3750 Stack Auto Upgrade

[Steve Mikulasik]

I have had issues using auto-upgrade on 3750 switches. The 16M of flash is 
pretty low and auto-upgrade can fail if there is a bunch of stuff on flash that 
isn't image related. The latest IOS is a lot larger than the image shipped on 
most 3750 switches, so storage is a lot tighter than what some may have 
experienced in the past.

Another failure scenario I have run into is when you have one switch with a 
lower license level than the other switches in the stack (1 LANBase switch in a 
stack of IP Services). The switch will need the image for LAN Base, but all the 
other switches will have the image for IP Services, so the auto upgrade won't 
work. 


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Harry 
Hambi - Atos
Sent: Friday, March 3, 2017 2:58 AM
To: 'cisco-nsp@puck.nether.net' 
Subject: [c-nsp] 3750 Stack Auto Upgrade

Hi Everyone,
Has anyone one successfully upgraded stacks with the auto upgrade feature?. If 
a member of a stack failed it would be nice if when replacing the failed unit 
it would be automatically upgraded from the master. When I say upgraded I mean 
the IOS and the configuration, is this possible. Any advice appreciated.


Rgds
Harry

Harry Hambi BEng(Hons)  MIET  Rsgb






http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal 
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on 
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

-
___
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] Ode to the old days

[Steve Mikulasik]

That reminds me of this comic http://i.imgur.com/FEiAgxh.gif




-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Gert 
Doering
Sent: Thursday, December 8, 2016 2:36 PM
To: Nick Cutting 
Cc: cisco-nsp 
Subject: Re: [c-nsp] Ode to the old days

Hi,

On Thu, Dec 08, 2016 at 09:29:01PM +, Nick Cutting wrote:
> The day I got my hands on a 3550, when I was new to networking - and I 
> thought we will never ever need routers again ! Removed all our 
> routers living on sticks

Yeah, the 3750 we bought "because it can do v6!".  

And then I discovered that it can neither do v6, nor netflow, nor counters on 
SVIs.  Spent the rest of its life as too-expensive L2 switch, and fortunately 
died a few years later (after a much shorter lifespan than normal Cisco gear, 
so it wasn't even built properly).

gert
--
USENET is *not* the non-clickable part of WWW!
   
http:www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025g...@net.informatik.tu-muenchen.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/

Re: [c-nsp] Ode to the old days

[Steve Mikulasik]

Make sure you tell all the young techs "They don't make 'em like they used to!"


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Mattias 
Gyllenvarg
Sent: Thursday, December 8, 2016 4:46 AM
To: cisco-nsp 
Subject: [c-nsp] Ode to the old days

Dear All

10year 4weeks 6days and about 11hours ago I was working for my first ISP (ispA).

On that day I put a 3560-24TS into production as a device to terminate to a 
Metronet running OSPF/BGP och public IP space.

A few years later I started consulting for ispB who later split into and became 
ispC for whom I worked for several years.

After this I ventured into a smaller ISP (ispD) that was acquiring ispA.

During that time that 3560 has been working without issue or power 
interruptions.
Today, that it was replaced to add MPLS capabilities to the node boasting an 
up-time of 10 years 4 weeks 6 days and 11 hours.

I fear I will never beat this record in my career.

To the old gear!
___
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] DHCP Snooping on Cat3850

[Steve Mikulasik]

I have had a lot of issues with DHCP snooping on the 3.7 train. Never got it to 
work, but since it wasn't necessary for the deploy I never got around to 
figuring it out. 

___
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] ISR4431-AX/K9

[Steve Mikulasik]

I believe NBAR 2 is in the AVX bundle, but there is normal NBAR support in the 
other bundles.


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Adam 
Greene
Sent: Tuesday, July 12, 2016 10:50 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] ISR4431-AX/K9

Hey guys,

 

If I need a router that can do application based bandwidth throttling
(NBAR2) at 500M-1G aggregate throughput, ISR4431-AX/K9 should do the trick, 
right? It seems to provide the features and throughput. Please tell me if I'm 
wrong (other services enabled on the router will be limited to BGP and OSPF).

 

Thanks,

Adam

___
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] VRF IP Helper

[Steve Mikulasik]

I am trying to setup ip helper on a 3750G 12.2(55)SE10. The SVIs are on the 
"GUEST" vrf and the DHCP server is in global. With "ip helper-address global 
1.1.1.14" set on the SVI the switch seems to be forwarding using the SVI's IP 
rather than an IP in global. This behavior is different on my 3850s where an 
interface in global is used to forward the DHCP request.

Is there a way to set the source address for ip helper or some other method to 
make this work?

Here is the debug

000122: 14:36:51: DHCPD: DHCPINFORM received from client 0174.d435.b7c9.bc 
(172.20.1.51).
000123: 14:36:51: DHCPD: Finding a relay for client 0174.d435.b7c9.bc on 
interface Vlan101.
000124: 14:36:51: DHCPD: Looking up binding using address 172.20.1.1
000125: 14:36:51: DHCPD: setting giaddr to 172.20.1.1.
000126: 14:36:51: DHCPD: BOOTREQUEST from 0174.d435.b7c9.bc forwarded to 
1.1.1.14.
000127: 14:36:54: DHCPD: Reload workspace interface Vlan101 tableid 1.
000128: 14:36:54: DHCPD: tableid for 172.20.1.1 on Vlan101 is 1
000129: 14:36:54: DHCPD: client's VPN is GUEST.
___
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] Strange X2 Temperature Flaps

[Steve Mikulasik]

Are they 3rd party optics? Maybe you got a bad batch that had a fault temp 
diode.



-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Robert 
Williams
Sent: Thursday, March 17, 2016 9:37 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Strange X2 Temperature Flaps

Hi,

Within 48 hours we have had three very strange issues with three different X2 
modules, installed in 2 different chassis (both in 6708-10G/Sup720/6509E). In 
each case, the module's temperature reading has jumped and then oscillated from 
+127C to -127C over the course of the next 5 hours.

Each time it completes a loop it jumps from -127 to +127 - at _that_ moment we 
get a short burst of CRC errors in the ASR9k which is connected to the other 
end of the link. In two of the cases so far, the errors were enough to trip OAM 
on the ASR9k into err-disable on the port due to >3 seconds of symbol errors.

[Example image of temperature Vs. time is attached.]

So far this has hit us on:

 - 3 different X2 modules
 - in 2 different line cards
 - in 2 different chassis
 - within a 48 hour window

Chassis are at the same geographic site but several racks apart. Modules are 
10G-LR SM optics, mixed brands. Chassis are 6509-E running 15.1(2)SY5 with 
around 260 days uptime each.

So apart from being powered on for a similar amount of days, I can find 
absolutely nothing related which may be causing this.

If you login to the chassis and repeatedly read the temperature from the 
transceiver (sh int te2/8 trans) you get a slightly different (+/- 5 degrees) 
value each time, but always tracking the same steady decrease (until -127, then 
it jumps again).

In many years of operating this type of hardware I’ve never seen this happen 
before. Anyone have any ideas or advice?

Any input most welcome!

Cheers,



Robert Williams
Custodian Data Centre
Email: rob...@custodiandc.com
http://www.CustodianDC.com

___
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] NCS-5001 - sweet...got one in the lab

[Steve Mikulasik]

In the future when kids are complaining that the multi Tbps wifi is slow we 
will tell them that back in our day we had 100Gbe and we liked it!


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Aaron
Sent: Monday, February 01, 2016 3:24 PM
To: 'Justin M. Streiner' ; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] NCS-5001 - sweet...got one in the lab

Some of y'all might be used to these really fat interfaces, not in my little 
ol' world... hundred gige was surprising!  That's all I was saying...

Thanks Justin

Aaron

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Justin 
M. Streiner
Sent: Monday, February 1, 2016 11:12 AM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] NCS-5001 - sweet...got one in the lab

On Mon, 1 Feb 2016, Aaron wrote:

> wow, check out the interface names at the bottom of the list, yeah the 
> names that start with "H" !!

Kind of surprising.  Thinking of the Nexus world, all Ethernet interfaces are 
named "Ethernet." regardless of speed.  It seems like other vendors are 
moving in this direction as well, such as Juniper with 100G interfaces on MX 
platforms.

jms

> RP/0/RP0/CPU0:eng-lab-5001-1#sh ip int br Mon Feb 1 15:37:16.489 CST
>
> Interface IP-Address Status Protocol Vrf-Name
> Loopback0 10.101.12.244 Up Up default
> TenGigE0/0/0/0 unassigned Shutdown Down default
> TenGigE0/0/0/1 unassigned Shutdown Down default
> TenGigE0/0/0/2 unassigned Shutdown Down default
> TenGigE0/0/0/3 unassigned Shutdown Down default
> TenGigE0/0/0/4 unassigned Shutdown Down default
> TenGigE0/0/0/5 unassigned Shutdown Down default
> TenGigE0/0/0/6 unassigned Shutdown Down default
> TenGigE0/0/0/7 unassigned Shutdown Down default
> TenGigE0/0/0/8 unassigned Shutdown Down default
> TenGigE0/0/0/9 unassigned Shutdown Down default
> TenGigE0/0/0/10 unassigned Shutdown Down default
> TenGigE0/0/0/11 unassigned Shutdown Down default
> TenGigE0/0/0/12 unassigned Shutdown Down default
> TenGigE0/0/0/13 unassigned Shutdown Down default
> TenGigE0/0/0/14 unassigned Shutdown Down default
> TenGigE0/0/0/15 unassigned Shutdown Down default
> TenGigE0/0/0/16 10.101.14.50 Up Up default
> TenGigE0/0/0/17 unassigned Shutdown Down default
> TenGigE0/0/0/18 unassigned Shutdown Down default
> TenGigE0/0/0/19 unassigned Shutdown Down default
> TenGigE0/0/0/20 unassigned Shutdown Down default
> TenGigE0/0/0/21 unassigned Shutdown Down default
> TenGigE0/0/0/22 unassigned Shutdown Down default
> TenGigE0/0/0/23 unassigned Shutdown Down default
> TenGigE0/0/0/24 unassigned Shutdown Down default
> TenGigE0/0/0/25 unassigned Shutdown Down default
> TenGigE0/0/0/26 unassigned Shutdown Down default
> TenGigE0/0/0/27 unassigned Shutdown Down default
> TenGigE0/0/0/28 unassigned Shutdown Down default
> TenGigE0/0/0/29 unassigned Shutdown Down default
> TenGigE0/0/0/30 unassigned Shutdown Down default
> TenGigE0/0/0/31 unassigned Shutdown Down default
> TenGigE0/0/0/32 unassigned Shutdown Down default
> TenGigE0/0/0/33 unassigned Shutdown Down default
> TenGigE0/0/0/34 unassigned Shutdown Down default
> TenGigE0/0/0/35 unassigned Shutdown Down default
> TenGigE0/0/0/36 unassigned Shutdown Down default
> TenGigE0/0/0/37 unassigned Shutdown Down default
> TenGigE0/0/0/38 unassigned Shutdown Down default
> TenGigE0/0/0/39 unassigned Shutdown Down default
> HundredGigE0/0/1/0 unassigned Shutdown Down default
> HundredGigE0/0/1/1 unassigned Shutdown Down default
> HundredGigE0/0/1/2 unassigned Shutdown Down default
> HundredGigE0/0/1/3 unassigned Shutdown Down default
> MgmtEth0/RP0/CPU0/0 unassigned Shutdown Down default
> MgmtEth0/RP0/CPU0/1 unassigned Shutdown Down default
>
>
>
> ___
> 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/

___
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] switch for SAN

[Steve Mikulasik]

The 3850 will perform better as it has larger buffers than the 3750X. 3850 is 
an upgrade in everyway. 

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Adam 
Greene
Sent: Friday, January 08, 2016 7:44 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] switch for SAN

Hi all,

 

I know running Catalyst switches for SAN backbone fabric is not the best idea, 
due to limited buffers. 

 

However, we have been doing just that with a 3750X and Dell Equallogic 
6100/4100s for quite some time, with no issues.

 

We are putting in a NetApp FAS3160 and need to add a switch. I see 3750X is EOL 
and Cisco positions the 3850 as its replacement. 3850 is even slightly less 
expensive than 3750X.

 

Questions:

-  Should we expect the 3850 to perform as well or better than the
3750X for this application?

-  Is there any other switch we should be looking at which is not
humongously more expensive? Maybe Nexus 3k could work, but it's a lot more 
expensive. Maybe 4948E? Seems up there price-wise, too .

 

Thanks,

Adam

 

___
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] 4500X Roadmap

[Steve Mikulasik]

Seems like it. I have a very small datacenter I am specing out, need are not 
very high, but 10gb is a requirement. 4500X would be a perfect fit if it had 
40Gbe, although it still isn't out of the question. 


-Original Message-
From: CiscoNSP List [mailto:cisconsp_l...@hotmail.com] 
Sent: Monday, October 19, 2015 2:55 PM
To: Steve Mikulasik <steve.mikula...@civeo.com>; cisco-nsp@puck.nether.net
Subject: Re: 4500X Roadmap


We run some 4500X's, but were told by our Cisco AM last year that it(4500X 
platform) is not seen as a "long term" propositionpotential new model?





From: cisco-nsp <cisco-nsp-boun...@puck.nether.net> on behalf of Steve 
Mikulasik <steve.mikula...@civeo.com>
Sent: Tuesday, 20 October 2015 4:59 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] 4500X Roadmap

The 3850 recently got updated to have models that support 40Ggbe uplinks. Is 
there any word on the street about the 4500X getting 40Gbe modules? Seems weird 
this switch does not have the capability, but the lower end unit does.



___
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] 4500X Roadmap

[Steve Mikulasik]

You are right, nice catch :) I'll look at the 6840-X as well. 


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Tom Hill
Sent: Monday, October 19, 2015 3:10 PM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] 4500X Roadmap

On 19/10/15 22:05, Steve Mikulasik wrote:
> L3 is needed as well. L2TP support is a big plus too. 

Would the 6840-X not make a better fit? I can't see reference to the 4500-X 
doing L2TP at all.

(L2PT, yes, but that's *totally* different.)

--
Tom
___
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] 4500X Roadmap

[Steve Mikulasik]

L3 is needed as well. L2TP support is a big plus too. 


-Original Message-
From: CiscoNSP List [mailto:cisconsp_l...@hotmail.com] 
Sent: Monday, October 19, 2015 3:03 PM
To: Steve Mikulasik <steve.mikula...@civeo.com>; cisco-nsp@puck.nether.net
Subject: Re: 4500X Roadmap


Do you only need L2?

Nexus 9K might fit your needsnot overly expensive, and you can run VPC (If 
you needed to vs VSS on 4500X)




From: Steve Mikulasik <steve.mikula...@civeo.com>
Sent: Tuesday, 20 October 2015 7:57 AM
To: CiscoNSP List; cisco-nsp@puck.nether.net
Subject: RE: 4500X Roadmap

Seems like it. I have a very small datacenter I am specing out, need are not 
very high, but 10gb is a requirement. 4500X would be a perfect fit if it had 
40Gbe, although it still isn't out of the question.


-Original Message-
From: CiscoNSP List [mailto:cisconsp_l...@hotmail.com]
Sent: Monday, October 19, 2015 2:55 PM
To: Steve Mikulasik <steve.mikula...@civeo.com>; cisco-nsp@puck.nether.net
Subject: Re: 4500X Roadmap


We run some 4500X's, but were told by our Cisco AM last year that it(4500X 
platform) is not seen as a "long term" propositionpotential new model?





From: cisco-nsp <cisco-nsp-boun...@puck.nether.net> on behalf of Steve 
Mikulasik <steve.mikula...@civeo.com>
Sent: Tuesday, 20 October 2015 4:59 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] 4500X Roadmap

The 3850 recently got updated to have models that support 40Ggbe uplinks. Is 
there any word on the street about the 4500X getting 40Gbe modules? Seems weird 
this switch does not have the capability, but the lower end unit does.



___
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] 4500X Roadmap

[Steve Mikulasik]

The 3850 recently got updated to have models that support 40Ggbe uplinks. Is 
there any word on the street about the 4500X getting 40Gbe modules? Seems weird 
this switch does not have the capability, but the lower end unit does.



___
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] CRC errors on multiple ports of WS-C2950T-48-SI switch

[Steve Mikulasik]

When it boots up check to see if the switch passes the startup tests. 


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Martin T
Sent: Wednesday, October 14, 2015 9:15 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] CRC errors on multiple ports of WS-C2950T-48-SI switch

Hi,

I had two WS-C2950T-48-SI switches in the network which all of the sudden 
started to show large amount of CRC errors on about dozen ports. Those two 
incidents are not related to each other, i.e those two incidents did not happen 
at the same time or in the same location.
I simply received those switches now from remote sites. Unfortunately this is 
all the information I have about the incidents. My first thought was that maybe 
it has to do with the fact that switch has 48 ports and there was increased 
bandwidth between the ports behind different ASICs. I made a following physical 
setup:

Fa0/1 <-> Fa0/48
Fa0/2 <-> Fa0/47
Fa0/3 <-> Fa0/46
...
Fa0/24 <-> Fa0/25

Image of the setup can be seen here:
http://s15.postimg.org/fmsj753qz/WS_C2950_T_48_SI_test_setup.png


VLANs were configured like this:

WS-C2950T-48-SI#sh int status

Port  Name   Status   Vlan   Duplex  Speed Type
Fa0/1connected1  a-full  a-100 10/100BaseTX
Fa0/2connected2  a-full  a-100 10/100BaseTX
Fa0/3connected3  a-full  a-100 10/100BaseTX
Fa0/4connected4  a-full  a-100 10/100BaseTX
Fa0/5connected5  a-full  a-100 10/100BaseTX
Fa0/6connected6  a-full  a-100 10/100BaseTX
Fa0/7connected7  a-full  a-100 10/100BaseTX
Fa0/8connected8  a-full  a-100 10/100BaseTX
Fa0/9connected9  a-full  a-100 10/100BaseTX
Fa0/10   connected10 a-full  a-100 10/100BaseTX
Fa0/11   connected11 a-full  a-100 10/100BaseTX
Fa0/12   connected12 a-full  a-100 10/100BaseTX
Fa0/13   connected13 a-full  a-100 10/100BaseTX
Fa0/14   connected14 a-full  a-100 10/100BaseTX
Fa0/15   connected15 a-full  a-100 10/100BaseTX
Fa0/16   connected16 a-full  a-100 10/100BaseTX
Fa0/17   connected17 a-full  a-100 10/100BaseTX
Fa0/18   connected18 a-full  a-100 10/100BaseTX
Fa0/19   connected19 a-full  a-100 10/100BaseTX
Fa0/20   connected20 a-full  a-100 10/100BaseTX
Fa0/21   connected21 a-full  a-100 10/100BaseTX
Fa0/22   connected22 a-full  a-100 10/100BaseTX
Fa0/23   connected23 a-full  a-100 10/100BaseTX
Fa0/24   connected24 a-full  a-100 10/100BaseTX
Fa0/25   connected25 a-full  a-100 10/100BaseTX
Fa0/26   connected24 a-full  a-100 10/100BaseTX
Fa0/27   connected23 a-full  a-100 10/100BaseTX
Fa0/28   connected22 a-full  a-100 10/100BaseTX
Fa0/29   connected21 a-full  a-100 10/100BaseTX
Fa0/30   connected20 a-full  a-100 10/100BaseTX
Fa0/31   connected19 a-full  a-100 10/100BaseTX
Fa0/32   connected18 a-full  a-100 10/100BaseTX
Fa0/33   connected17 a-full  a-100 10/100BaseTX
Fa0/34   connected16 a-full  a-100 10/100BaseTX
Fa0/35   connected15 a-full  a-100 10/100BaseTX
Fa0/36   connected14 a-full  a-100 10/100BaseTX
Fa0/37   connected13 a-full  a-100 10/100BaseTX
Fa0/38   connected12 a-full  a-100 10/100BaseTX
Fa0/39   connected11 a-full  a-100 10/100BaseTX
Fa0/40   connected10 a-full  a-100 10/100BaseTX
Fa0/41   connected9  a-full  a-100 10/100BaseTX
Fa0/42   connected8  a-full  a-100 10/100BaseTX
Fa0/43   connected7  a-full  a-100 10/100BaseTX
Fa0/44   connected6  a-full  a-100 10/100BaseTX
Fa0/45   connected5  a-full  a-100 10/100BaseTX
Fa0/46   connected4  a-full  a-100 10/100BaseTX
Fa0/47   connected3  a-full  a-100 

Re: [c-nsp] Cisco WS2960-X - Are these switches lemons or is there a stable release?

[Steve Mikulasik]

I think that was a bug in 15.0.2EX5. 15.0.2aEX5 has been working fine for me 
since it came out in Feb.  


-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Hagen 
AMEN
Sent: Monday, October 12, 2015 11:29 AM
To: Nick Cutting 
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Cisco WS2960-X - Are these switches lemons or is there a 
stable release?

Indeed, not only do they stop forwarding on the copper SFPs, the SFP tends to 
drop off entirely (just generates that lovely HULC error when you query the 
ethernet-controller phy detail).

And, for extra fun, some iterations of the hardware will also (when the SFP
fails) start generating:

"%ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured by 
Cisco or with Cisco's authorization..."

Which causes the switch to stop forwarding all traffic. Requires a full power 
cycle to restore.


On Mon, Oct 12, 2015 at 10:20 AM, Nick Cutting 
wrote:

> I've never got over the bug that plagues copper SFP's in this model of 
> switch.  They just stop forwarding traffic randomly.
>
> They keep promising a fix - I still haven't seen anything rock solid.
>
> -Original Message-
> From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf 
> Of Ian Hiddleston
> Sent: 12 October 2015 17:29
> To: cisco-nsp@puck.nether.net
> Subject: [c-nsp] Cisco WS2960-X - Are these switches lemons or is 
> there a stable release?
>
> Hi guys,
>
> For reasons best left alone, I’ve ended up with a pair of Cisco 
> 2960-X’s (WS-C2960X-48TD-L to be precise). I’ve had nothing but 
> trouble with them so far, hence asking the list. Does anyone know if 
> there is a stable software image for them that doesn’t crash when you 
> SSH to it or drop the stack module offline and split brain for fun?
>
> Thanks,
> Ian
>
>
> Ian Hiddleston | Senior Network Analyst | Civica UK Limited
> Tel: 0845 055 2323
> e-mail: ian.hiddles...@civica.co.uk | 
> http://www.civica.co.uk<
> http://www.civica.co.uk/>
>
>
> ■ Civica commits to the next generation by joining The 5% Club.. more< 
> https://www.civica.co.uk/articles/816-Civica-commits-to-the-next-generation-by-joining-The-5-Club
> >
> ■ The Great British Cloud-off... more< 
> https://www.civica.co.uk/articles/813-The-Great-British-Cloud-off>
> ■ Bristol City Council selects Civica’s Housing Cx system to transform 
> tenant services... more< 
> https://www.civica.co.uk/articles/809-Bristol-City-Council-selects-Civicas-Housing-Cx-system-to-transform-tenant-services
> >
>
> Civica UK Limited
>
> --
> -
>
> This e-mail is sent for and on behalf of Civica UK Limited company 
> number 01628868,
>
> Civica Services Limited company number 02374268, or Civica Group 
> Limited company number 04968437.
>
> All companies are registered in England and Wales and each has its 
> registered office at 2 Burston Road, Putney, London, SW15 6AR.
>
> Confidentiality: This e-mail and its attachments are intended for the 
> above named only and may be confidential. If they have come to you in 
> error you must take no action based on them, nor must you copy or show 
> them to anyone. If you have received this in error please advise the 
> sender by replying to this e-mail immediately highlighting the error 
> and deleting it from your system.
>
>
>
> ___
> 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/
>



--
Hagen Amen : Multco Network : 503-988-5227 
___
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] Cisco WS2960-X - Are these switches lemons or is there a stable release?

[Steve Mikulasik]

My recent experiences with TAC suggested releases has not been good when it 
comes to switches. I have been doing a lot more reading into the release notes 
to figure out the most suitable release.



From: Hagen AMEN [mailto:hagen.a.a...@multco.us]
Sent: Tuesday, October 13, 2015 8:38 AM
To: Steve Mikulasik <steve.mikula...@civeo.com>
Cc: Nick Cutting <ncutt...@edgetg.co.uk>; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Cisco WS2960-X - Are these switches lemons or is there a 
stable release?

Certainly, we saw the issue happen running 15.0(2)EX5, but we've also seen it 
happen on 15.2(2)E, 15.2(2a)E1, as well as ES releases from TAC (which were 
supposed to fix the issue).

We're running 15.2(3)E1, for the last couple of months (July timeframe). So 
far, no recurrence.

On Tue, Oct 13, 2015 at 6:57 AM, Steve Mikulasik 
<steve.mikula...@civeo.com<mailto:steve.mikula...@civeo.com>> wrote:
I think that was a bug in 15.0.2EX5. 15.0.2aEX5 has been working fine for me 
since it came out in Feb.


-Original Message-
From: cisco-nsp 
[mailto:cisco-nsp-boun...@puck.nether.net<mailto:cisco-nsp-boun...@puck.nether.net>]
 On Behalf Of Hagen AMEN
Sent: Monday, October 12, 2015 11:29 AM
To: Nick Cutting <ncutt...@edgetg.co.uk<mailto:ncutt...@edgetg.co.uk>>
Cc: cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net>
Subject: Re: [c-nsp] Cisco WS2960-X - Are these switches lemons or is there a 
stable release?

Indeed, not only do they stop forwarding on the copper SFPs, the SFP tends to 
drop off entirely (just generates that lovely HULC error when you query the 
ethernet-controller phy detail).

And, for extra fun, some iterations of the hardware will also (when the SFP
fails) start generating:

"%ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured by 
Cisco or with Cisco's authorization..."

Which causes the switch to stop forwarding all traffic. Requires a full power 
cycle to restore.


On Mon, Oct 12, 2015 at 10:20 AM, Nick Cutting 
<ncutt...@edgetg.co.uk<mailto:ncutt...@edgetg.co.uk>>
wrote:

> I've never got over the bug that plagues copper SFP's in this model of
> switch.  They just stop forwarding traffic randomly.
>
> They keep promising a fix - I still haven't seen anything rock solid.
>
> -Original Message-
> From: cisco-nsp 
> [mailto:cisco-nsp-boun...@puck.nether.net<mailto:cisco-nsp-boun...@puck.nether.net>]
>  On Behalf
> Of Ian Hiddleston
> Sent: 12 October 2015 17:29
> To: cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net>
> Subject: [c-nsp] Cisco WS2960-X - Are these switches lemons or is
> there a stable release?
>
> Hi guys,
>
> For reasons best left alone, I’ve ended up with a pair of Cisco
> 2960-X’s (WS-C2960X-48TD-L to be precise). I’ve had nothing but
> trouble with them so far, hence asking the list. Does anyone know if
> there is a stable software image for them that doesn’t crash when you
> SSH to it or drop the stack module offline and split brain for fun?
>
> Thanks,
> Ian
___
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] CSRv & VXLAN

[Steve Mikulasik]

Yeah after some further reading I think you are right. I'll extend the question 
to include OTV on the CSRv platform. Any experiences would be greatly 
appreciated. 


-Original Message-
From: Luis Anzola [mailto:anzo...@gmail.com] 
Sent: Thursday, September 24, 2015 11:22 AM
To: Steve Mikulasik <steve.mikula...@civeo.com>
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] CSRv & VXLAN

I would look at OTV instead. It's a technology developed specifically for DCI 
implementations and brings very important benefits with it.

Luis 

Sent from my iPhone

> On Sep 24, 2015, at 12:56 PM, Steve Mikulasik <steve.mikula...@civeo.com> 
> wrote:
> 
> Anyone have any experience with VXLAN on the CSRv? I need to span L2 traffic 
> across hosted datacetners (can't use a physical device unless it installs on 
> x86 hardware) and was wondering if this is the way to go on this platform.
> 
> 
> 
> ___
> 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] CSRv & VXLAN

[Steve Mikulasik]

Anyone have any experience with VXLAN on the CSRv? I need to span L2 traffic 
across hosted datacetners (can't use a physical device unless it installs on 
x86 hardware) and was wondering if this is the way to go on this platform.



___
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] CSRv & VXLAN

[Steve Mikulasik]

I haven't heard of other vendors using it, but there is a IETF draft. A lot of 
vendors seem to be pushing OTV-like tech or VXLAN. 

https://tools.ietf.org/html/draft-hasmit-otv-04

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Luan 
Nguyen
Sent: Thursday, September 24, 2015 12:57 PM
To: Luis Anzola <anzo...@gmail.com>
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] CSRv & VXLAN

While we are on this...
Is OTV still Cisco Proprietary? And still ASR1K and Nexus 7K support from Cisco 
side?
Wouldn't it better to use L2TPv3 - and MACSEC if need to?

On Thu, Sep 24, 2015 at 2:40 PM, Luis Anzola <anzo...@gmail.com> wrote:

> Find below a very handy guide for the CSR1Kv and OTV:
>
>
> http://www.cisco.com/c/en/us/td/docs/solutions/Hybrid_Cloud/DRaaS/CSR/CSR/CSR5.html
>
>
>
> On Thu, Sep 24, 2015 at 2:22 PM, Mohammad Khalil 
> <eng_m...@hotmail.com>
> wrote:
>
> > Hi
> > I have simulated this on gns3
> > http://eng-mssk.blogspot.com/2015/09/otv-example.html?m=1
> >
> > It might give you a hint
> >
> > BR,
> > Mohammad
> >
> >
> > Sent from Samsung Mobile
> >
> >
> >  Original message 
> > From: Steve Mikulasik <steve.mikula...@civeo.com>
> > Date:24/09/2015 20:45 (GMT+02:00)
> > To: Luis Anzola <anzo...@gmail.com>
> > Cc: cisco-nsp@puck.nether.net
> > Subject: Re: [c-nsp] CSRv & VXLAN
> >
> > Yeah after some further reading I think you are right. I'll extend 
> > the question to include OTV on the CSRv platform. Any experiences 
> > would be greatly appreciated.
> >
> >
> > -Original Message-
> > From: Luis Anzola [mailto:anzo...@gmail.com <anzo...@gmail.com>]
> > Sent: Thursday, September 24, 2015 11:22 AM
> > To: Steve Mikulasik <steve.mikula...@civeo.com>
> > Cc: cisco-nsp@puck.nether.net
> > Subject: Re: [c-nsp] CSRv & VXLAN
> >
> > I would look at OTV instead. It's a technology developed 
> > specifically for DCI implementations and brings very important benefits 
> > with it.
> >
> > Luis
> >
> > Sent from my iPhone
> >
> > > On Sep 24, 2015, at 12:56 PM, Steve Mikulasik <
> steve.mikula...@civeo.com>
> > wrote:
> > >
> > > Anyone have any experience with VXLAN on the CSRv? I need to span 
> > > L2
> > traffic across hosted datacetners (can't use a physical device 
> > unless it installs on x86 hardware) and was wondering if this is the 
> > way to go on this platform.
> > >
> > >
> > >
> > > ___
> > > 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/
> >
> ___
> 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/

___
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] NATPort block alloc fail

[Steve Mikulasik]

I am trying to confirm what Port block alloc fail means when displaying sh 
ip nat stat. Is it the failure of the router to NAT connections due to 
exhausting the port range of available IPs? My google-fu is failing me today 
and I can't find any references to this.

sh ip nat stat
Total active translations: 43980 (0 static, 43980 dynamic; 43980 extended)
Outside interfaces:
GigabitEthernet0/0/0
Inside interfaces:
GigabitEthernet0/0/2
Hits: 126626681380 Misses: 930651476
Expired translations: 978336005
Dynamic mappings:
-- Inside Source
[Id: 1] access-list 10 interface GigabitEthernet0/0/0 refcount 43926
nat-limit statistics:
max entry: max allowed 50, used 43979, missed 0
In-to-out drops: 498115 Out-to-in drops: 584950318
Pool stats drop: 0 Mapping stats drop: 0
Port block alloc fail: 41366
IP alias add fail: 0
Limit entry add fail: 0


Steve Mikulasik




___
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] Mixing 2960S and X in stack

[Steve Mikulasik]

And here I was thinking about adding a 2960X to 2960S stack. Thanks for helping 
me dodge a bullet! It is the simple stuff that is the hardest. 

Stephen Mikulasik

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Alan 
Buxey
Sent: Sunday, May 31, 2015 3:34 PM
To: Garry; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Mixing 2960S and X in stack

Gert has given the answer.  Yes,  you can mix them but there are so many 
caveats... I've advised our team to just not think about mixing them ever.  
Better to swap out 2960s elsewhere with a 2960x to get a 2960s stack member!  ;)

alan
___
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] Cisco 3850 Stable Release

[Steve Mikulasik]

What is the most stable release for the 3850 platform? The TAC recommended 
3.3.5SE is total trash. Has a wonderful bug when you write mem the switch stack 
reloads.

https://tools.cisco.com/bugsearch/bug/CSCur26193/?referring_site=bugquickviewredir

Stephen Mikulasik

___
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] DAI Scale

[Steve Mikulasik]

I have some 2960+ running WAPs. Each 2960 will probably have 100-200 clients at 
peak (low bandwidth use) and I am thinking of turning on DAI on each 2960. I 
don't know how DAI functions on the hardware, so how well does it scale up on 
this platform? Will I run into issues doing this on 2960 switches since they 
are a low end platform?

Stephen Mikulasik

___
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] 3850 DHCP Database Locked

[Steve Mikulasik]

Anyone ever received the error % The DHCP database could not be locked. Please 
retry the command later. It pops up when doing any sort of show dhcp command. 
I can find reference to it as a bug for 7206, but can't seem to find anything 
for 3850.

I am running 3.03.05SE. Figured I would try this group before running around 
with TAC.


Stephen Mikulasik

___
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] Question for TAC

[Steve Mikulasik]

I have noticed this as well. Maybe Cisco should develop a system where people 
going on vacation in 1-2 weeks don't get certain types of tickets. 

Stephen Mikulasik

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Eric 
Van Tol
Sent: Thursday, April 30, 2015 8:44 AM
To: David White, Jr. (dwhitejr)
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Question for TAC

First, thank you for responding.

 I know your original post was a rant, but I wanted to respond 
 because as someone who lives, eats and breathes my customer's problems 
 (just like my fellow TAC engineers) it hits hard when I hear about 
 something like this.  As others have mentioned, there are escalation 
 paths within and outside of TAC to assist you when you do not feel 
 your problem is getting the attention it needs.  But I don't think 
 that really addresses your rant.  All I can say is that engineers do 
 need to take time off occasionally (whether sickness, travel or 
 vacation), but it should not be something that you would experience regularly.

I know people need to take time off.  It just seems like the I'm going to be 
on vacation line happens a lot more than one would expect it should.  Clearly, 
I'm not the only one who has experienced this.

 This much I know is true, working in TAC isn't so much of a job as a 
 life choice.  We are here because we want to help people (our 
 customers) and we like solving complex challenging problems.  Our 
 customers come first (often at the expense of many other parts of our life).

I do not doubt that 99% of TAC wants to help, as that's why they're in TAC.  
It's why I do what I do, too.  We're in the same boat, that respect.  My rant 
was not at all about TAC's willingness to help, or their competency, but rather 
the frustratingly high number of incidents where engineers take cases and 
immediately go on vacation.  I just wanted to see if this was common and I 
think I got my answer.

Thanks,
evt

P.S. TAC management is doing something right because the quality of TAC 
engineers has improved greatly, in my experience, over the past few years.  
Others may disagree, but that's my take.
___
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] Slightly off-topic - Network Monitoring software

[Steve Mikulasik]

Anyone ever try Nedi? http://www.nedi.ch/

Stephen Mikulasik

___
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] Inline Fan Controllers?

[Steve Mikulasik]

I have used those before, it should decrease the voltage, forcing the fan spin 
slower. It should work in theory on any device using a 3pin connector. Possibly 
a defective or junky fan controller. You could put a volt meter on the end of 
it to see if turning the knob has any affect. 

Stephen 

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of chris
Sent: Wednesday, December 17, 2014 10:02 AM
To: cisco-nsp@pu ck.nether.net
Subject: [c-nsp] Inline Fan Controllers?

Hello,

Has anyone on the list ever messed putting in a fan controller in a switch so 
its inline between the motherboard and fan? I had one of these ( 
http://www.quietpc.com/images/products/gel-fan-controller.jpg ) laying around 
and plugged into a spare 2950g and 3560g I have kicking around and the fan 
powers up and the fan works like normal and turning the knob has no effect. I 
thought it would be like a standard 3 wire computer fan and that this would be 
easy way to lower rpm on a stock fan with replacing the fan.

This is only to minimize noise when labbing, we arent lookinng to do this to 
any production equipment. Anyone ever tried anything like this and had any 
success? I was hoping it would work because the controllers are only a few 
dollars and it would be cheaper and more flexible as we could move the 
controllers around from box to box as needed

If you have any experience with anything that worked, I would be interested to 
hear about it

chris
___
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] Inline Fan Controllers?

[Steve Mikulasik]

It was a Zalman, cheapo unit 
http://www.newegg.com/Product/Product.aspx?Item=N82E16835118217

I have used a few others over the years, but they were usually for 3.5” and 
5.25” bays on desktops, might be a bit bigger than what you want.

Stephen

From: chris [mailto:tknch...@gmail.com]
Sent: Wednesday, December 17, 2014 10:54 AM
To: Steve Mikulasik
Cc: cisco-nsp@pu ck.nether.net
Subject: Re: [c-nsp] Inline Fan Controllers?

I had 2 of the same exact fan controllers both do the same thing so I'm 
counting out that both are defective but guessing that most likely theres 
something they arent doing right. The controllers I have say they control any 
12V fan, and the fan on the 2950g im playing with says its 12V 0.46A so i think 
it should work. You don't happen to remember a model or part # of one you 
used that worked?

chris

On Wed, Dec 17, 2014 at 12:35 PM, Steve Mikulasik 
steve.mikula...@civeo.commailto:steve.mikula...@civeo.com wrote:
I have used those before, it should decrease the voltage, forcing the fan spin 
slower. It should work in theory on any device using a 3pin connector. Possibly 
a defective or junky fan controller. You could put a volt meter on the end of 
it to see if turning the knob has any affect.

Stephen

-Original Message-
From: cisco-nsp 
[mailto:cisco-nsp-boun...@puck.nether.netmailto:cisco-nsp-boun...@puck.nether.net]
 On Behalf Of chris
Sent: Wednesday, December 17, 2014 10:02 AM
To: cisco-nsp@pu ck.nether.nethttp://ck.nether.net
Subject: [c-nsp] Inline Fan Controllers?

Hello,

Has anyone on the list ever messed putting in a fan controller in a switch so 
its inline between the motherboard and fan? I had one of these ( 
http://www.quietpc.com/images/products/gel-fan-controller.jpg ) laying around 
and plugged into a spare 2950g and 3560g I have kicking around and the fan 
powers up and the fan works like normal and turning the knob has no effect. I 
thought it would be like a standard 3 wire computer fan and that this would be 
easy way to lower rpm on a stock fan with replacing the fan.

This is only to minimize noise when labbing, we arent lookinng to do this to 
any production equipment. Anyone ever tried anything like this and had any 
success? I was hoping it would work because the controllers are only a few 
dollars and it would be cheaper and more flexible as we could move the 
controllers around from box to box as needed

If you have any experience with anything that worked, I would be interested to 
hear about it

chris
___
cisco-nsp mailing list  
cisco-nsp@puck.nether.netmailto: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] 4500X help

[Steve Mikulasik]

I agree, in my 4500X deploys I haven't noticed a difference. Only thing would 
be VSS setup if you are planning on doing stacking. From my understanding Cisco 
has made it easier in later IOS releases.  

Steve

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Mark 
Tinka
Sent: Thursday, December 11, 2014 8:53 AM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] 4500X help

On Thursday, December 11, 2014 05:06:19 PM Howard, Christopher wrote:

 I've not seen any differences with ours either.  I expect you could 
 probably take the 3560 config and just paste it in and not get any 
 errors. You should be fine if you're comfortable with IOS.

The most notable engineering changes to IOS XE compared to IOS are under the 
hood, i.e., you don't see them as the operator.

The main changes the operator sees for IOS XE are in the platform commands, 
since IOS XE is typically running only on hardware-based boxes (with the 
exception of CSR1000v, which still uses the platform command too).

So for me, IOS and IOS XE are 100% identical from a CLI perspective.

Mark.



___
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/