cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
171
Views
1
Helpful
3
Replies

cbs350 logging mismatch vlan eating cpu ?

samuellsk
Level 1
Level 1

Hellou

hopefully i selected the right board...

Have a strange question, as this does seems kinda odd to think...
We were connecting 2 switches , one is ours, the others is customers.
Customer is using his own vlans and we are using our own vlans.

So in order to get internet to our solution and not chaning half of things on our side we setup access port with a vlan for our "wan side". The vlan is used in the virtual router as "wan"...etc.. everything works.

So it came a bit surprasing when some global senior of cyber defense from the customer spew out that
having native vlan mismatch (that is not really relevant cause port is in the access not trunk and he failed to setup his side...) is eating up resources cause its logging (yeah it logs , every 3 minutes)... that there is mismatch...

So either i am totaly dumb thinking that it is eating, at least 1percent , casue i dont really see any sort of utilization, switch always chills around 2 - 4% of cpu utilisation according to monitoring or is he just simply hostile ?

Thank you.

1 Accepted Solution

Accepted Solutions

balaji.bandi
Hall of Fame
Hall of Fame

i dont think these model support log suppress, until you fix the issue disable log or offload to syslog.

https://www.cisco.com/c/en/us/td/docs/switches/lan/csbms/CBS_250_350/Administration-Guide/cbs-350/administration.html#ID-00001228

as long as its not effecting performance 2-4% is ok.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

View solution in original post

3 Replies 3

balaji.bandi
Hall of Fame
Hall of Fame

i dont think these model support log suppress, until you fix the issue disable log or offload to syslog.

https://www.cisco.com/c/en/us/td/docs/switches/lan/csbms/CBS_250_350/Administration-Guide/cbs-350/administration.html#ID-00001228

as long as its not effecting performance 2-4% is ok.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

samuellsk
Level 1
Level 1

i think the observer 2 - 4 is normal behaviour regardelss the logging issue.
he is presenting it like thats the problem, that causes it...

to put it into more context
our guys are connecting to the w365 instances from eu to usa, thats 100+ ms just there, on the top of that customer is running some packet analyzer between w365 and site where we need to connect, so another 40

and the whole issue started cause he request tcpdump from our solution (running robots across the warehouse) while not even having the access point on side but in the server room locked in the metal rack... and he sees packet retrasmits..etc..

i just think he trolls with everything what is "wrong" but actualy is not related to any performance issue,

But wanted to at least have some sort of confirmation if it can cause a problem (never belived that, he throws tanrtrums like this all the time...) but better check

Thank you
that would be all.

Joseph W. Doherty
Hall of Fame
Hall of Fame

Presuming the customer's switch is flagging the VLAN logging mismatch because of CDP, then customer can simply deactivate CDP on their interface.  (Which might be considered a good practice between ASs, something you might consider too.)

2-4% CPU utilization, to me, seem rather high for logging one interface's CDP VLAN mismatch every 3 minutes.  However, regardless, generally any switch's "heavy lifting" (i.e. data plane - frame forwarding) is usually performed by dedicated hardware and CPU load is thereby often not too relevant.  CPU load can be very relevant to its control plane (management), but even there, CPU processing is usually prioritized such that more critical tasks get CPU cycles first.  I.e. even if CPU is running continuously at 100%, it may not be impactful to critical tasks.

Cannot say what's the motivation of your customer.  Perhaps it's not hostility, but something like ignorance; they don't truly understand how switch hardware works and are alarmed by anything that appears to cause something to happen, which may, they believe, degrade performance, like the additional logging.