[f-nsp] Show processes on a FESX

[Kennedy, Joseph]

The FES and FESX switches aren't based on the same hardware so you can't always rely on them to have the same issues.

I haven't found high CPU conditions in the FESX line using switch code that weren't due to some traffic anomaly, SNMP, sFlow, or misreporting of the actual usage.

It also depends on what you mean by high.  There is an old issue in the FESX line where CPU seems to increase when sFlow is enabled irrespective of the sampling rate.  I've seen it in different releases going way back.

--JK

-----Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Niels Bakker
Sent: Thursday, April 17, 2014 1:00 PM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Show processes on a FESX

* Joseph.Kennedy at purchase.edu (Kennedy, Joseph) [Thu 17 Apr 2014, 18:50 CEST]:
>"show proc cpu" is limited to router code as far as I am aware. It's 
>like that in the FES code as well. You could alter your config to allow 
>management and load router code to see which process is causing the 
>issue, but in some cases the process causing the issue may not be in 
>the list(like if it is related to management processes).

Don't do that without console access.  The configuration statement style for setting the switch's management IP address in switch software is not accepted as valid in the router software.

Chances are a reload will clear this up anyway.  FES/FESX in my experience can run into problems much like this near the 1,000 days uptime mark. :)


	-- Niels.

--
_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp