SF 300 24p Firmware

Hi guys,
I recently upgraded the firmware of an SF 300 24p PoE switch using the GUI.
But I was wondering if the same task could be done using the CLI so the task could be scripted for bulk operations.
So far, it doesn't seem to support deleting files from flash memory properly (squeeze doesn't seem to exist), as well as other things.
Am I simply missing something or is it something that just can't be done?
Thanks in advance.

Hi Wim, if your switches are running the original firmware 1.0.0.27, there is not a faster way to manage this.
I haven't played with this aspect in a while but the file names are very simple If my memory served me correctly you can't just delete the images or boot code.
As example the firmware images are labeled as image1 or image2, boot is called boot.
Here's the CLI guide
http://www.cisco.com/en/US/docs/switches/lan/csbms/sf30x_sg30x/administration_guide/CLI_300_1_2_5.pdf
You can find the syntax for copy operations around page 146/147.
If you're already on the 1.2.7.76 firmware you may also use SCP
Here's the admin guide
http://www.cisco.com/en/US/docs/switches/lan/csbms/sf30x_sg30x/administration_guide/78-19308-01.pdf
The SCP option requires a SCP server. I'm not sure if that's a good option for you.
-Tom
Please mark answered for helpful posts

Similar Messages

SF 300-24P uplink problem

Dear Team,
We bought a cisco POE Switch (Cisco SF 300-24P) from a reseller before two months, and we are facing a problem when we connect just an uplink on Telephone network and it is a standalone network and there is no Vlans connected to this network, the other two switches on this network are LINKSYS SRW224P (Old Product), and the problem is when we dial from POE phones like Linksys SPA922; the tone gone and we can’t hear the one who we are calling and he don’t hear us, but when we disconnect this uplink cable from the Switch above every things come back normal.
Please advise.
Many thanks

it would be good to see a topology of your network to help troubleshooting.
is the uplink between your switches? if so, you could have a loop in your network,
do all the activity lights light up on your switches whan you plug in the uplink?
Verify all the cables between the switches and make sure you don't have a loop,
virtual server hosts with multiple nics, unmanaged switches and hubs can also cause this.
You can also look in the logs to see if there are spanning tree errors, or
look at spanning tree status to see if there are ports that have a 'blocked' state, that would indicate spanning tree has shut down a port,
if the uplink is to the telephone network... is this an analog line?
you say standalone network, so I assume it's not an ethernet cable...

Mounting Brackets (SG 200-26P & SF 300-24P)

Looking for mounting brackets for the SG 200-26P & SF 300-24P. Lost the originals and can't seem to find a new set anywhere online.

I don't think this could be ordered as a spare.
Look if you could find something similar in a local market, following are the measurements:

Differences between SF 300-24P and SF 300-24MP??

Hello all,
First post here, very excited!
On to my question as I cannot seem to find specifics on this.
Besides the MP having support for PoE+, does the 24P have a full 24-port PoE budget or only 12 ports at a time?
What other differences between the two.
I currently have 10 APs plugged into a SF 300-24P and want to add 10 more. PoE consumption is around 3500mW for each AP.
Thanks,
Pasquale

Hi and welcome to the forum.
According to the data sheet, all 24 ports support POE.
have a look at table-1 in this link (under power over Ethernet) section:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps10898/data_sheet_c78-610061.html
Also, here is a link to compare models:
http://www.cisco.com/cisco/web/solutions/small_business/products/routers_switches/300_series_switches/index.html-tab-Models
HTH

SG500X-24P firmware 1.2.0.83

I recently got an old SG500X-24P switch with an active firmware 1.2.0.81. I can't seem to update it. I ran an update to 1.2.0.9, reboot, the firmware still shows 1.2.0.81. I can update the non-active firmware, but can't switch to it. Whatever I do it still shows 1.2.0.81. This device doesn't have Cisco support. Does anyone have firmware 1.2.0.83? Maybe, doing it sequentially will work? Thanks.
This topic first appeared in the Spiceworks Community

Suggestion: Make sure you reboot your RV when you think it should be working and everything matches.
Wasted an hour on my RV320 the other night because it had hung up somehow. Changes were not taking effect and a reboot fixed it.

Upgrading SF200-24P firmware questions

I have an SF200-24P running FW 1.2.7.76 and boot 1.1.0.6. I wanted to update the firmware in hopes it would help with a weird problem I'm having with a UC320 phone system so I downloaded from Cisco Sx200_FW_Boot_1.4.0.88.zip.
The instructions say if I'm upgrading from something earlier than 1.3.5, I first need to upgrade the device image to "to image 1.3.5 or 1.3.7 and the latest boot file (1.4.0.x)."
In the ZIP file I downloaded from Cisco are two files:
sx200_boot-13506.rfb
sx200_fw-14088.ros
Are they just saying I first need to load the sx200_boot-13506.rfb, then load the
sx200_fw-14088.ros file?
Or do I need to download a previous copy of the firmware? If that is the case, do I just download 1.3.5.58 and install the .ros file in that archive, wait for the switch to become ready, and load the .ros file from the 1.4.0.88 archive?
I'm unclear on the process of getting my switch with old firmware updated to the newest firmware. So any tips would be appreciated.

Hi,
First upgrade to version sx200_fw_1.3.7.18.ros and Boot code sx200_boot-13506.rfb.After that upgrade to latest firmware sx200_fw-14088.ros .Not required to upgrade the boot code .since boot code is same for both version firmware.
regards
Moorthy

SF 300-24P 24-Port 10/100 PoE - Video is not working smoothly

Hi,
We installed SF-300 24 ports that connected to our network and we connected 20 IP cameras to it. In the Giga ports we connected Video Server.
In the same Vlan but on another switch we connected 2 PC's that can monitor all the 20 IP cameras. Everything worked fine until we had electricity outage.
After that break the monitoring working very bad. The video streaming is not working smooth and it is working with some breaks. I reloaded the switch and everything was back to normal. Can someone send me any suggestions how to configure cameras and how to configure the servers on the port switch? Do I need to enable the smartport option?
Thanks,
Reuven

Hi Reuven, If everything was working as expected and then you had a network event such as a power failure where new symptoms arised, I do not believe this is a configuration issue unless you lost configuration settings. Is that the case? The switch lost configuration?
Having power issues has a funny way of making things have problems. One thing you may want to try to do is isolate your problem to every camera. Do all 20 cameras have an issue or just a few? Is there any symptoms if you disconnect the cameras one at a time?
If all 20 cameras have a problem, I'd recommend to make a back up of your switch and then factory reset the unit as it is possible the power issue caused some sort of corruption in the software.
-Tom
Please mark answered for helpful posts

CK-300 new firmware

Hi
Finally wanted to update my CK-300 in my car while having the glovebox out to change the pollen filter.
On the website they claim that the newest version is 1.5 but the software fetched 1.6 and installed it.
Does anyone know if nokia has some sort of changelog from version to version ?
It's super easy to upgrade the CK-300 with the software and the simple homemade USB cable i use.
Xsatquest

Hi redsri
Unfortunately no clues as to what device you intend using CK-300 with but if you use a Nokia Device compatible with CarMenu .sis available here:http://europe.nokia.com/support/product-support/nokia-ck-300/application-software then it appears under "Settings" menu on device. Dependent upon how old stock is your HF-21W may be running v1.400, whereas the latest available using Nokia Carkit Updater application is v1.600. Although software changelog is not in the public domain it does address some Bluetooth connectivity issues amongst others, although a recent poster wished it had been left on previous v1.500 and not updated with their particular usage.
Happy to have helped forum in a small way with a Support Ratio = 37.0

Trouble with SF 300-24P 24-Port 10/100 PoE

Good day.
I connect to switch Access Point, configure port on switch which vlan work on this port. But after reboot AP my config for this port delete and have other config where vlan 1 untagged, and allow all other vlan. But in my cinfig allow 3vlan: untagged 100, and tagged 113, 999.
How to solve this problem?

hi Igor, you need to save the running config to the start up config, otherwise a reboot will drop any changes made to the switch.
When you make a change to the switch, on the top right of your browser there is a blinking button to save, click this and save the run config to start up.
-Tom
Please mark answered for helpful posts

SF300-24P - SNMP question

Hi,
I've a script that does the check of port status asking OIDs
.1.3.6.1.2.1.17.4.3.1.2
.1.3.6.1.2.1.17.4.3.1.1
.1.3.6.1.2.1.2.2.1.8
after a firmware upgrade, all these OIDs are not available.
for example:
snmpwalk -v 2c -c public 192.168.1.197 .1.3.6.1.2.1.17.4.3.1.2iso.3.6.1.2.1.17.4.3.1.2 = No Such Instance currently exists at this OID
I also tried to follows procedures like:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801c9199.shtml
using the community string indexing (I don't think that it applies to small business switches) but for desperation...
Have you any suggestion?
Thank you very much in advance,
and sorry if it's an already asked question, I've tried the search button, but without finding a definitive answer.
Best Regards,
Franceco

Hi Tom,
thanks for your answer,
on my first switch (firmware 1.0.0.27)
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 iso.3.6.1.4.1.9.6.1.101.53.4.1.5.1iso.3.6.1.4.1.9.6.1.101.53.4.1.5.1 = STRING: "1.0.0.27"francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 iso.3.6.1.4.1.9.6.1.101.53.4.1.6.1iso.3.6.1.4.1.9.6.1.101.53.4.1.6.1 = STRING: "SF 300-24P"francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.17.4.3.1.1iso.3.6.1.2.1.17.4.3.1.1.0.1.108.10.28.67 = Hex-STRING: 00 01 6C xx xx xxiso.3.6.1.2.1.17.4.3.1.1.0.5.51.63.126.18 = Hex-STRING: 00 05 33 xx xx xx...iso.3.6.1.2.1.17.4.3.1.1.228.31.19.196.116.24 = Hex-STRING: E4 1F 13 xx xx xxiso.3.6.1.2.1.17.4.3.1.1.228.31.19.196.116.26 = Hex-STRING: E4 1F 13 xx xx xxfrancesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.17.4.3.1.2iso.3.6.1.2.1.17.4.3.1.2.0.1.108.10.28.67 = INTEGER: 1000iso.3.6.1.2.1.17.4.3.1.2.0.5.51.63.126.18 = INTEGER: 1000...iso.3.6.1.2.1.17.4.3.1.2.228.31.19.196.116.24 = INTEGER: 1000iso.3.6.1.2.1.17.4.3.1.2.228.31.19.196.116.26 = INTEGER: 1000francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.2.2.1.8iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2...iso.3.6.1.2.1.2.2.1.8.100000 = INTEGER: 1iso.3.6.1.2.1.2.2.1.8.300000 = INTEGER: 1
On firmware 1.1.1.8 same output.
If you need somthing else, please let me know.
Best Regards,
Francesco

Creative Zen Style 300 - charging

Hi,?i have a big problem. I bought mp4 about 2 weeks ago. I listened to it from time to time. Yesterday, my mp4 warned me that the battery is very low. So i connected USB to my mp4 and to the charger and put it in to the socket. My mp4 is charging for about 0 seconds and it turned on autobmatically. And it won't charge! I thought that maybe it only charges when it has to be on. So i put it like that for a night. In the morning it was in the same condition like the last night! I downloaded ?Creative ZEN Style 300/00 Firmware .03.04 and?Creative ZEN Style Starter Pack .8.03?but it didn't help. Please, what do i have to do?

Hi,
It looks like something is wrong with the player. Did you purchase this from your local electronics store or direct from Creative? Please contact the place of purchase for repair/replacement.

SG-300 28P switches problem with VLAN Data and Voice, working all the time as Voice VLAN

Hi Everyone,
Thank you very much for your help in advance. I’m pulling my hair to fix the problem.
I just got the new SG-300 28P switches. My Bios ordered for me. I did not know how it runs until now... not an IOS based. I really do not know how to configure it.
I have 2 VLAN are Data and Voice.
-          Data VLAN ID is 2 IP 192.168.2.X/255.255.255.0
-          Voice VLAN ID is 200 IP 192.168.22.X/255.255.255.0
-          I created two vlans, in switch, Data and Voice.
-          On the port number 28, it is trunk by default, so I add Data vlan ID 2 tagged.
-          On the port number 26, it is trunk by default, so I add Voice vlan ID 200 tagged.
-          On the port number 27, I add Data vlan ID 2 tagged for Data vlan out.
-          Port settings No.1
I set it up as Trunk with Data vlan 2 untagged, and 200 Tagged (voice vlan). I plugged in a phone with a pc attached. But the PC will get to the vlan 200 to get the DHCP address, but no from vlan 2. The Phone works with correct vlan ip.
-          Port settings No.2
Trunk with vlan 1UP, 2T, and 200T. The phone is even worse. Would never pick up any IP from DHCP.
-          Port settings No.3
Access with 200U...of course the phone will work... and the PC could not get to its own vlan. Instead, the PC got an ip from the voice vlan. Not from VLAN 2.
I have Linksys phone I’m not sure if this help.
For more information I setup in switch,
            - enable voice vlan
- set the port on auto voice vlan
- enable LLDP-MED globally
- create a network policy to assign VLAN 200
- assign this network policy to the port the phone is connected to.
I hope this information help to help me to setup Data and Voice vlans, to plug the phone to work with vlan Voice 200 (IP rang 192.168.22.X), from phone to Pc and pc work as Data vlan 2 (IP rang 192.168.2.X).

I just got done setting up voice VLANs on an SF 300-24P and verified working. This was working with Cisco 7900 series phones connected to a Cisco UC setup.
Here's my sample config.
Note that I edited this by hand before posting, so doing a flat out tftp restore probably won't work. However, this should give you a clue. Also, don't take this as 100% accurate or correct. I've only been working with these things for about a week, though I've worked with the older Linksys SRW switches for a couple of years. I'm a CCNP/CCDP.
VLAN 199 is my management VLAN and is the native VLAN on 802.1q trunks.
VLAN 149 is the data/computer VLAN here.
VLAN 111 is the voice/phone VLAN here.
VLAN 107 does nothing.
interface range ethernet e(1-24)
port storm-control broadcast enable
exit
interface ethernet e1
port storm-control include-multicast
exit
interface ethernet e2
port storm-control include-multicast
exit
interface ethernet e3
port storm-control include-multicast
exit
interface ethernet e4
port storm-control include-multicast
exit
interface ethernet e5
port storm-control include-multicast
exit
interface ethernet e6
port storm-control include-multicast
exit
interface ethernet e7
port storm-control include-multicast
exit
interface ethernet e8
port storm-control include-multicast
exit
interface ethernet e9
port storm-control include-multicast
exit
interface ethernet e10
port storm-control include-multicast
exit
interface ethernet e11
port storm-control include-multicast
exit
interface ethernet e12
port storm-control include-multicast
exit
interface ethernet e13
port storm-control include-multicast
exit
interface ethernet e14
port storm-control include-multicast
exit
interface ethernet e15
port storm-control include-multicast
exit
interface ethernet e16
port storm-control include-multicast
exit
interface ethernet e17
port storm-control include-multicast
exit
interface ethernet e18
port storm-control include-multicast
exit
interface ethernet e19
port storm-control include-multicast
exit
interface ethernet e20
port storm-control include-multicast
exit
interface ethernet e21
port storm-control include-multicast
exit
interface ethernet e22
port storm-control include-multicast
exit
interface ethernet e23
port storm-control include-multicast
exit
interface ethernet e24
port storm-control include-multicast
exit
interface range ethernet g(1-4)
description "Uplink trunk"
exit
interface range ethernet g(1-4)
switchport default-vlan tagged
exit
interface range ethernet e(21-24)
switchport mode access
exit
vlan database
vlan 107,111,149,199
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 107
exit
interface range ethernet e(21-24)
switchport access vlan 111
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 111
exit
interface range ethernet e(1-20)
switchport trunk native vlan 149
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 149
exit
interface range ethernet g(1-4)
switchport trunk native vlan 199
exit
voice vlan aging-timeout 5
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
voice vlan oui-table add 108ccf MyCiscoIPPhones1
voice vlan oui-table add 40f4ec MyCiscoIPPhones2
voice vlan oui-table add 8cb64f MyCiscoIPPhones3
voice vlan id 111
voice vlan cos 6 remark
interface ethernet e1
voice vlan enable
exit
interface ethernet e1
voice vlan cos mode all
exit
interface ethernet e2
voice vlan enable
exit
interface ethernet e2
voice vlan cos mode all
exit
interface ethernet e3
voice vlan enable
exit
interface ethernet e3
voice vlan cos mode all
exit
interface ethernet e4
voice vlan enable
exit
interface ethernet e4
voice vlan cos mode all
exit
interface ethernet e5
voice vlan enable
exit
interface ethernet e5
voice vlan cos mode all
exit
interface ethernet e6
voice vlan enable
exit
interface ethernet e6
voice vlan cos mode all
exit
interface ethernet e7
voice vlan enable
exit
interface ethernet e7
voice vlan cos mode all
exit
interface ethernet e8
voice vlan enable
exit
interface ethernet e8
voice vlan cos mode all
exit
interface ethernet e9
voice vlan enable
exit
interface ethernet e9
voice vlan cos mode all
exit
interface ethernet e10
voice vlan enable
exit
interface ethernet e10
voice vlan cos mode all
exit
interface ethernet e11
voice vlan enable
exit
interface ethernet e11
voice vlan cos mode all
exit
interface ethernet e12
voice vlan enable
exit
interface ethernet e12
voice vlan cos mode all
exit
interface ethernet e13
voice vlan enable
exit
interface ethernet e13
voice vlan cos mode all
exit
interface ethernet e14
voice vlan enable
exit
interface ethernet e14
voice vlan cos mode all
exit
interface ethernet e15
voice vlan enable
exit
interface ethernet e15
voice vlan cos mode all
exit
interface ethernet e16
voice vlan enable
exit
interface ethernet e16
voice vlan cos mode all
exit
interface ethernet e17
voice vlan enable
exit
interface ethernet e17
voice vlan cos mode all
exit
interface ethernet e18
voice vlan enable
exit
interface ethernet e18
voice vlan cos mode all
exit
interface ethernet e19
voice vlan enable
exit
interface ethernet e19
voice vlan cos mode all
exit
interface ethernet e20
voice vlan enable
exit
interface ethernet e20
voice vlan cos mode all
exit
interface ethernet e1
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e2
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e3
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e4
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e5
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e6
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e7
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e8
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e9
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e10
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e11
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e12
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e13
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e14
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e15
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e16
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e17
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e18
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e19
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e20
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e21
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e22
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e23
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e24
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g1
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g2
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g3
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g4
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e1
lldp med notifications topology-change enable
exit
interface ethernet e2
lldp med notifications topology-change enable
exit
interface ethernet e3
lldp med notifications topology-change enable
exit
interface ethernet e4
lldp med notifications topology-change enable
exit
interface ethernet e5
lldp med notifications topology-change enable
exit
interface ethernet e6
lldp med notifications topology-change enable
exit
interface ethernet e7
lldp med notifications topology-change enable
exit
interface ethernet e8
lldp med notifications topology-change enable
exit
interface ethernet e9
lldp med notifications topology-change enable
exit
interface ethernet e10
lldp med notifications topology-change enable
exit
interface ethernet e11
lldp med notifications topology-change enable
exit
interface ethernet e12
lldp med notifications topology-change enable
exit
interface ethernet e13
lldp med notifications topology-change enable
exit
interface ethernet e14
lldp med notifications topology-change enable
exit
interface ethernet e15
lldp med notifications topology-change enable
exit
interface ethernet e16
lldp med notifications topology-change enable
exit
interface ethernet e17
lldp med notifications topology-change enable
exit
interface ethernet e18
lldp med notifications topology-change enable
exit
interface ethernet e19
lldp med notifications topology-change enable
exit
interface ethernet e20
lldp med notifications topology-change enable
exit
interface ethernet e21
lldp med notifications topology-change enable
exit
interface ethernet e22
lldp med notifications topology-change enable
exit
interface ethernet e1
lldp med enable network-policy poe-pse
exit
interface ethernet e2
lldp med enable network-policy poe-pse
exit
interface ethernet e3
lldp med enable network-policy poe-pse
exit
interface ethernet e4
lldp med enable network-policy poe-pse
exit
interface ethernet e5
lldp med enable network-policy poe-pse
exit
interface ethernet e6
lldp med enable network-policy poe-pse
exit
interface ethernet e7
lldp med enable network-policy poe-pse
exit
interface ethernet e8
lldp med enable network-policy poe-pse
exit
interface ethernet e9
lldp med enable network-policy poe-pse
exit
interface ethernet e10
lldp med enable network-policy poe-pse
exit
interface ethernet e11
lldp med enable network-policy poe-pse
exit
interface ethernet e12
lldp med enable network-policy poe-pse
exit
interface ethernet e13
lldp med enable network-policy poe-pse
exit
interface ethernet e14
lldp med enable network-policy poe-pse
exit
interface ethernet e15
lldp med enable network-policy poe-pse
exit
interface ethernet e16
lldp med enable network-policy poe-pse
exit
interface ethernet e17
lldp med enable network-policy poe-pse
exit
interface ethernet e18
lldp med enable network-policy poe-pse
exit
interface ethernet e19
lldp med enable network-policy poe-pse
exit
interface ethernet e20
lldp med enable network-policy poe-pse
exit
interface ethernet e21
lldp med enable network-policy poe-pse
exit
interface ethernet e22
lldp med enable network-policy poe-pse
exit
lldp med network-policy 1 voice vlan 111 vlan-type tagged
interface range ethernet e(1-22)
lldp med network-policy add 1
exit
interface vlan 199
ip address 199.16.30.77 255.255.255.0
exit
ip default-gateway 199.16.30.3
interface vlan 1
no ip address dhcp
exit
no bonjour enable
bonjour service enable csco-sb
bonjour service enable http
bonjour service enable https
bonjour service enable ssh
bonjour service enable telnet
hostname psw1
line console
exec-timeout 30
exit
line ssh
exec-timeout 30
exit
line telnet
exec-timeout 30
exit
management access-list Management1
permit ip-source 10.22.5.5 mask 255.255.255.0
exit
logging 199.16.31.33 severity debugging description mysysloghost
aaa authentication enable Console local
aaa authentication enable SSH tacacs local
aaa authentication enable Telnet local
ip http authentication tacacs local
ip https authentication tacacs local
aaa authentication login Console local
aaa authentication login SSH tacacs local
aaa authentication login Telnet local
line telnet
login authentication Telnet
enable authentication Telnet
password admin
exit
line ssh
login authentication SSH
enable authentication SSH
password admin
exit
line console
login authentication Console
enable authentication Console
password admin
exit
username admin password admin level 15
power inline usage-threshold 90
power inline traps enable
ip ssh server
snmp-server location in-the-closet
snmp-server contact [email protected]
ip http exec-timeout 30
ip https server
ip https exec-timeout 30
tacacs-server host 1.2.3.4 key spaceballz timeout 3 priority 10
clock timezone -7
clock source sntp
sntp unicast client enable
sntp unicast client poll
sntp server 199.16.30.1
sntp server 199.16.30.2
ip domain-name mydomain.com
ip name-server 199.16.5.12 199.16.5.13
ip telnet server

SF300-24P VLAN CONFIG QUESTION

Hi please excuse my ignorance and lack of knowledge in this field as I am a complete newbie when it comes to Cisco switches and VLANS etc. but trying to learn.
I have a Cisco 300-24P and need to create two separate networks (private and public) ports 1 - 10 for Private and ports 11 - 20 for Public. I then to need ports 21 - 24 for access points and that can access both private and public.
I am assuming that would need to create two vlans (e.g. VLAN100 for private and VLAN200 for public). After reading a little I think I need to set ports 1- 20 to "access" and ports 21- G4 to "trunk".
I have attempted this but don't think I have things quite right. Would it be possible for someone to either point me in the right direction or even send me a saved config that I could load and examine.
Many thanks in advance for your help.

Hello,
I think I can clarify a few things for you:
1- The ports that are going to connect directly to end stations will need to be configured as access ports with the respective VLAN as untagged.
2- The ports that are going to be connected to the AP's will need to be configured as trunks with VLAN 100 un-tagged and 200 tagged. The AP should be able to understand VLAN's, they should be configured with and IP address on VLAN 100.
3- By default, the un-tagged VLAN is the same PVID.
Notes:
A few things to keep in mind:
1- I see you already have a router on the network, this is the one that will determine if the VLAN's can talk to each other based on the Inter VLAN configuration. In general terms, if inter VLAN is enabled on the router then Public and Private will be able to share traffic, otherwise they wont.
2- When creating VLAN's on the SG300 make sure that you are not assigning IP addresses to any other VLAN than your management VLAN, otherwise you could have issues with the routing.
3- To make sure the connectivity between the VLANs is working as you expect, make sure to do all the testing from the hardwired PC's first, that way you will know if the issue is on the router or the switch.
I hope this was helpful.

SF 300 Series rack mount brackets

I have misplaced the rack mount brackets for a SF 300-24P switch. I have searched online to try and find replacements. Anyone have a clue as to were I could find some?

Dave,
Please open a case with Cisco Support and they will be able to help you.
Thanks,
Ivor

ESW-520-24P - New GUI?

We're testing out the ESW series to replace the existing small business series for many of our customers. I was disappointed to see it run the same GUI as the SFE and SGE series switches! It's so clumsy and takes 10x as long to configure. And yes, we modify the clumsy config file offline but it's not that straight forward and always results in some type of error.
Anybody know when the ESW series switches will run the new GUI that the SF 300-24P new small business series runs? I gotta say, I'm very impressed with that GUI as it seem to collapse all the best features of all 3 previous GUI's together.
For now, we will plan on sticking with the SF 300 series until the ESW has the updated GUI.
Thanks
-robert

Hi Robert,
I also really like the new look and feel of the new 300 series.
We are trying to use a standard look and feel for the GUI on the small business products.
So the Small Business Routers, WAPs.Switches, Security appliances that are coming online and are online for sale at the moment, all have the same look and feel. I think the ESW switch, because it is really only used on UC5XX will stay the way it is, I have heard no mention of upgrading it's GUI.
Anyway currently, the ESW family of switches has an advantage of being managed by Cisco Configuration Assistant (CCA).
Robert, for other folks that look at this posting, I will include a link below to the newer 300 series product comparison pages.
As you will have noticed already, the 300 series is generations ahead of the older SRW series switches, even allows for Layer 3 routing between VLANs.
But for consistency of changeover from old part to new part , if you ordered in the past a part number SRW224G4, the 300 series replacement is now SRW224G4-K9-XX (where XX can be UK NA EU.......... country code of some kind.)
http://www.cisco.com/en/US/products/ps10898/prod_models_comparison.html
regards Dave

SF 300 24p Firmware

Similar Messages

Maybe you are looking for