Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Although not a problem, I've noted that on my CBS-350 the port speeds that are identified and published are 100Mbps, 1000Mbps and 10Gbps when interfaces to the SFP+ ports are being used. This is the case when the attached device is running at 2.5Gbp...
Hi folks,I need some help assessing what is going on with my CBS350 switch on the latest firmware. It's my understanding that the events I am seeing is for port 1 of this switch. Please note that there is nothing plugged into this port so I am wond...
I inadvertently pulled the AC power cord on my CBS350 on f/w 3.2.0.89 knocking my network down. I plugged it back in and the front panel System LED is flashing on and off continually. From reading the manual, the flashing green indicator means that...
Hi all,I am a beginner when it comes to managed switches and the CBS350 is my first foray into this arena. I currently have a home network with my cable modem feeding an ASUS router and a QNAP QSW-1208-8C unmanaged switch followed by several inexpen...
Thanks Kris K. I will try that route next time. What I did to correct my issue in the interim was to modify the tiny little text file slightly, uploaded it via the file system and execute if as I had done previously when going from DHCP to STATIC t...
Apologies for raising this thread from the dead. I am having a similar issue in that I have a current static IP address set to 192.168.1.x and want to change it to 192.168.1.y.I messed things up and did a complete factory reset of the switch that se...
I was unable to initiate a TAC case because I am not a business and don't have a business that Cisco has in their database. Maybe a lowly consumer end-user like me should stay away from Cisco?
Hello balaji.bandi. I will manually shut the unused ports and check. Also, I am at the latest firmware level Cisco is providing which is 43.4.0.17.Edit: Manually shutting down the port via the Administrative Status radio button eliminates the mess...
