Questions on setup my SG-300-10MP switch

hi Everyone,
Thank you very much for your help in advanced. I never been in this community before.
I just got the new SG-300 switches. My manager 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.
Anyway, I have a 3750 switch configured already in a new site. It has two vlans, one is vlan 11 for PC, and one is for VOIP vlan 320. It has auto qos running as well. I just setup a trunk for the new SG-300 switch.
Now on the new small switch SG 300...I have some questions:
1.) I also created two vlans, one is VLAN11 (for PC), and one is VLAN 320. For this one I go to the Web-GUI and assign the 320 to the VOICE Vlan. I also changed the CoS to 5 (from 6). Are these ok?
2.) On the port number 9, it is trunk by default, so I add both 11 and 320 to the trunk and leave the rest settings default. It is ok too right?
3.) On a Access port #1, which will have a IP phone attached with a PC plug in. What I did is to change the Interface Vlan mode to "GENERAL". Is that right? I also "CHECK" the Auto Voice VLAN Membership box. And the Voice VLAN QoS mode leaves it as Telephony Source MAC ADDRESS. Did I do all these right?
4.) Finally, for the QoS part...I leave them all default untouch - which is the Basic QoS defualt... I am not sure if this will be fine. I know the enterprise switch can assign an Auto-QOS command and it would do all the config itself. Or may you mind if you would share your QoS config settings?
I am more concerned about the QoS settings here. Hope you can help.
Thank you very much.
Takami Chiro

Hi Chiro-san,
See my answer below:
I just got the new SG-300 switches. My manager 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. Thank you for your business, a supported CLI interface is coming out with the next version of firmware. (so i have been told)
1.) I also created two vlans, one is VLAN11 (for PC), and one is VLAN 320. For this one I go to the Web-GUI and assign the 320 to the VOICE Vlan. I also changed the CoS to 5 (from 6). Are these ok?
Yes, but it makes no difference in my instance as the COS to queue tab shows that both CoS 5 and 6 are set within the same egress queue.
2.) On the port number 9, it is trunk by default, so I add both 11 and 320 to the trunk and leave the rest settings default. It is ok too right?
Yes, on switch port #9, VLAN1 traffic will be untagged, while Ethernet traffic for vlan11 and vlan 320 must have all incoming traffic Tagged. Outgoing Ethernet frames will also be tagged for Vlan11 and 320.
So IP phone will have to be set to run tagged Ethernet frames for one of those two vlans. But the switch also supports LLDP-MED, which depending on your phone system might help to auto-configure the phone on a particular VLAN.
3.) On a Access port #1, which will have a IP phone attached with a PC plug in. What I did is to change the Interface Vlan mode to "GENERAL". Is that right?
I personally do not use General mode, and it's usage seems quite unique.
When I went to VLAN Management > Interface Settings, I then selected the help option at the top right of the GUI.
This then brings up specific help for that displayed options. It says for general mode "General—The interface can support all functions as defined in the IEEE 802.1q specification. The interface can be a tagged or untagged member of one or more VLANs"
I personally prefer trunk mode, as General mode might allow two vlans to be untagged on switch port #1. I don't think that is what you want, but General mode still does allow multiple tagged VLANs to be associated with Switch port #1. So it's really not a problem. Having the port in trunk mode allows for one untagged vlan (default VLAN1) and one or more tagged VLANs.
I.
I also "CHECK" the Auto Voice VLAN Membership box. And the Voice VLAN QoS mode leaves it as Telephony Source MAC ADDRESS. Did I do all these right? yes
4.) Finally, for the QoS part...I leave them all default untouch - which is the Basic QoS defualt... I am not sure if this will be fine. I know the enterprise switch can assign an Auto-QOS command and it would do all the config itself. Or may you mind if you would share your QoS config settings?
The default settings set on my SG300-10P ( order p/n SRW2008P-K9) is shown below. Notice I could have the option to trust DSCP or COS settings coming into the switch.
I am more concerned about the QoS settings here. Hope you can help.
Thank you very much.

Similar Messages

300 Series Switch VLAN Setup

Hello,
I am trying to setup vlans on sf 302 switch and been unsuccesful. My idea is having 2 separate networks and both connecting to internet
192.168.2.0/24 Gaming Network
192.168.3.0/24 Work Network
Router ( Linkys) connected to port 8 on the switch - 192.168.4.1
I have attached the serial cable and made the following changes
Creating VLAN's
Created Vlan 20 for gaming network
#config t
#vlan database vlan 20
exit
Created Vlan 30 for work
#config t
# vlan database vlan 30
#exit
Asigned ports to VLAN's
#config t
# int fa2
# switchport mode access
# switchport access vlan 20
#exit
#config t
#int fa3
# switchport mode access
# switchport access vlan 30
#exit
Assigning IP address to VLAN
#conf t
#int vlan 20
# ip address 192.168.2.1 255.255.255.0
#end
#conf t
#int vlan 30
# ip address 192.168.3.1 255.255.255.0
#end
I am stuck after this. Now i want to connect vlan 20 and vlan 30 on to router attached to port8 on switch so that computers on both vlans have access to internet. The IP address of router is
192.168.4.1.
Please explain what needs to be done to acomplish this.
Thanks
Maakri

Hello Randy,
The switch is already set to router mode.
I have attached a belkin router on port 8 of the switch. The LAN IP of router is 192.168.4.2
On the switch I have configured port 8 as follows
#int fa8
#ip address 192.168.4.1
# switchport mode trunk
#switchport trunk allowed vlan add vlan 20
#switchport trunk allowed vlan add vlan 30
#no shutdown
#exit
#ip routing
From PC connected to vlan 20 and VLAN30 I can ping 192.168.4.1 but not 192.168.4.2. I want to access internet from my PC's on Vlan20 and VLAN30
I can ping PC in vlan30 from my pc in Vlan20 but cant access the router IP and so no internet. What am I missing? Please let me know
Thank you
Maakri

Firmware upgrade question for 300 series switches

Hi-
I have a customer that is investigating a strategy and solution for centralized firmware management of the 300 series switches. They have found an issue in the lab where they were trying to roll back the firmware to a previous version They can not roll back to the previous firmware version, which is desirable in the case of finding an issue in the new firmware that causes them to have need to rollback to a known working version.
We have read in the cisco 300 switch admin guide that there are two images (active and inactive) and that a new downloaded firmware always replaces the inactive image and is active until explicitly set. The admin guide does not mention inability to make an older firmware image as active image when the switch has previously run on a new release firmware image. My customer's engineers testing have informed me that an older image can not be made active after a newer image has booted. Can you please verify if this if a fallback is supposed to work as it is causing a lot of concern-
Thanks-
Jena

Jena,
The release notes -
http://www.cisco.com/en/US/docs/switches/lan/csbms/sf30x_sg30x/release_notes/Sx200-Sx300_R1.1.2.x.pdf
What firmware is the switches currently on?
Major Changes and Defects Corrected
• Hardware version 1.0 devices that were upgraded to software version 1.1
can now be downgraded to software version 1.0. You must delete the
startup configuration file before rebooting the device to software version
1.0. Otherwise the device may have problems when booting up. You may
backup your running configuration before the reboot, and re-import the
configuration afterward. Major Changes and Defects Corrected
• Hardware version 1.0 devices that were upgraded to software version 1.1
can now be downgraded to software version 1.0. You must delete the
startup configuration file before rebooting the device to software version
1.0. Otherwise the device may have problems when booting up. You may
backup your running configuration before the reboot, and re-import the
configuration afterward.
Please read full release notes for other work arounds
Hope this helps,
Jasbryan

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

Multiple vlans configuration issue with RV016 router and SG 300-10MP witch

Hi,
I have to configure multiple vlans served with a unique DCHP server . As first step, I just will The DHCP server to serve 2 vlans. The following is the hardware and configuration that I implemented :
Router (RV016 10/100 16-Port VPN Router) as gateway mode:
IP : 172.16.0.1/24
DHCP Server :
IP : 172.16.0.2/24 GW: 172.16.0.1
2 subnets :
172.16.1.0/24 GW: 172.16.1.1 to serve vlan 1
172.16.2.0/24 GW:172.16.2.1 to serve vlan 2
Switch (SG 300-10MP 10-Port Gigabit PoE Managed Switch) as layer 3 mode:
IP 172.16.0.254 (vlan 8 default)
Vlan 1 : 172.16.1.1
Vlan 2 : 172.16.2.1
1 device connected on each vlan
a workstation on the vlan 1
a laptop on the vlan 2
In this scenario (see the attached pdf file) the DHCP server is connected on a router, hosts on vlans dont receive any IP address.
But If I connect the DHCP server on a trunked switch port and adapt the DHCP server gateway 172.16.0.1 to 172.16.0.254, hosts receive ip address properly.
I have to connect the DHCP server directly to the router. How can I do that, what is wrong in the configuration ?
I hope the explanations are clear enough and my English too
Any help will be highly appreciated,
Zoubeir

Hi Eric, the small business group doesn't support the ASA config, but I can help with the switch.
A couple things I notice in your description-
48 port (192.168.1.254) and the other 24P (192.168.1.253) we have a second vlan 20 set up on the 24P switch (192.168.2.253) we have ports 1-12 set for vlan20 (untagged and trunk), the remaining ports on on the default vlan 1.
The connection between the switches, is it 1u, 2t?
The link between the switches should be 1u, 2t, the switches support the trunking and vlan tagging, meaning all communication will work fine.
We have the 24p and 48p switches connect using GE1 and GE1. We are unable to ping a device on vlan 20 ( on the 24p switch
The 24p switch should be in layer 2 mode, if you have the 48 port l3 switch upstream. Additionally, you need to have the default gateway set on the 24p switch.
We have a static route set on the 24p switch (0.0.0.0 192.168.1.0).
Between the switches, it shouldn't require any static routes, assuming you correctly trunk / tag your ge1 ports, with both switches operating in l3, the ip route table dynamically builds the connected routes, therefore a static route is redundant.
-Tom
Please rate helpful posts

Cisco 300 series switches

hi all
Ive looked through some of the online content but dont see a definitive answer to my question about the physical size of the switches, are they all 19" rack mountable or desktop?
I look forward to a confirmation..

LJ,
P = PoE capable. On the 300 series, half of the ports can provide 15.4W, or all can provide half that.
PoE+ is NOT SUPPORTED.
MP = Maximum Power. This means that all ports can provide up to 15.4W. PoE+ is supported on some models only.
PP = PoE Plus. Can provide up to 30W on a single port. Note the maximum PoE budget for each switch. Also,
half of the ports can provide 15.4W, or all can provide half that - any extra power used by PoE+
MPP = Maximum Power and PoE Plus. This means that all ports can provide up to 15.4W - any extra power used by PoE+
According to the Data Sheet:
"Switches support 802.3at PoE+, 802.3af, and Cisco pre-standard (legacy) PoE. Maximum power of 30.0W to any 10/100 or Gigabit Ethernet port for PoE+ supported devices and 15.4W for PoE supported devices, until the PoE budget for the switch is reached"
The PoE+ models are brand new and are not widey available yet. I did a web search for SG300-28PP and found that at least a few online resellers have it in stock.
- Marty
Message was edited by: Martin Pyhala

CCA for 100 + 300 series switches?

Is it in the roadmap to provide CCA control over 300 series switches? We have a lot of SRW2008's put in before the 8-port ESW existed...and we have PITA vlan consistency issues out there too that I think CCA would help fix.
While I understand the "don't pre-announce products", I need a level of design intent around CCA - is it a tool for configuring UC series pieces primarily and all else is secondary? Or is it the multi-device config tool for all SBCS pieces?

Nothing to do with the UC - primary concern is standalone networks.
Real life case:
2 ESW switches in control room hooked up to SA540
Closet switches are SRW2008's
Port no more than two devices are supposed to go now has 4, add an SRW2008 to the desk location.
Now, it turns out that there is a badly behaved device at the desk - a video player that spews all sorts of traffic when it's playing that doesn't play nice with others. So I now need to set-up a VLAN crossing those two switches. Oh, and it turns out the customer decided to unplug an access point and plug it into that switch too which ended up causing a loop when the PC plugged into ethernet someplace else attached to the PC.
Tasks:
Ensure that the 2 SRW2008's have proper vlan assignments to setup a port vlan for that video server.
Issues:
Make sure you assign proper configs to both ends of each link
Make sure not to confuse one SRW2008 with another
If new vlan, make sure all other ports that need to see it can still see it.
Applications for CCA:
Visualize all VLANS
Document port assignments (i.e. where is the video server vs. printer on that last leg 2008)
More easily see port statistics across multiple switches
So after I did that work, I realized that the SA540 wasn't really up to being an aggregation switch too and made the ESW-540-48 into the aggregation switch which required some more changes - however CCA made it easy...
At another job, I have SA540 + AP541ns (upgraded from RVL200 + WAP54GP's) but if I had 300 series in CCA, I'd upgrade the SRW2024's and SRW2008's but without easy management tools, the labor cost will be too high to make their networks really managed.....CCA makes that layer of management cheaper.

Cisco 300 series switches with 802.3at standard

I'm a bit confused as to which of the 300 series switches supports the 802.3at standard. According to the website, the SG300-28P supports it. But in the quick start guide for the 300 series, only the MP models (excluding the SF302-08MP and SG300-10MP) including the SG300-52P has it. Can someone give me a difinitive answer to this? Thanks!

LJ,
P = PoE capable. On the 300 series, half of the ports can provide 15.4W, or all can provide half that.
PoE+ is NOT SUPPORTED.
MP = Maximum Power. This means that all ports can provide up to 15.4W. PoE+ is supported on some models only.
PP = PoE Plus. Can provide up to 30W on a single port. Note the maximum PoE budget for each switch. Also,
half of the ports can provide 15.4W, or all can provide half that - any extra power used by PoE+
MPP = Maximum Power and PoE Plus. This means that all ports can provide up to 15.4W - any extra power used by PoE+
According to the Data Sheet:
"Switches support 802.3at PoE+, 802.3af, and Cisco pre-standard (legacy) PoE. Maximum power of 30.0W to any 10/100 or Gigabit Ethernet port for PoE+ supported devices and 15.4W for PoE supported devices, until the PoE budget for the switch is reached"
The PoE+ models are brand new and are not widey available yet. I did a web search for SG300-28PP and found that at least a few online resellers have it in stock.
- Marty
Message was edited by: Martin Pyhala

Using TACACS+ With ACS 5.6 on 300 Series Switches v1.4

I was wondering if anyone could give me instructions on how to set up ACS for TACACS+ on a 300 series switch using Authorization? I can get it to work to authenticate, but the authorization doesn't seem to work like a catalyst switch. Thanks in advance for any help!

Brandon, thanks for the link, but this is for the older software before they included authorization (the v1.4). I've looked through a bunch of manuals and tried to find examples online, but it doesn't seem like anyone has anything out there I can find.

TACACS+ Authorization on 300 Series Switches

I was wondering if anyone could give me instructions on how to set up ACS for TACACS+ on a 300 series switch using Authorization? I can get it to work to authenticate, but the authorization doesn't seem to work like a catalyst switch. Thanks in advance for any help!

Brandon, thanks for the link, but this is for the older software before they included authorization (the v1.4). I've looked through a bunch of manuals and tried to find examples online, but it doesn't seem like anyone has anything out there I can find.

Are 300 Series switches compatible with pre-standard PoE detection in old Cisco phones?

Are 300 Series switches compatible with pre-standard PoE detection in old Cisco phones? They don't seem to be (a 7902G won't power on when connected to an SF302-08MP with firmware version 1.1). Is any special configuration needed on the switch to enable this detection?

Please note that the 200 and 300 Series switches now support Cisco Legacy POE as of September 2011, allowing it to deliver power to 7960, 7940, and other pre-standard phones and APs. Details provided at the following link:
https://supportforums.cisco.com/docs/DOC-18337

Small configure help please? I have 3 300-28 switches, I want to connect them and avoid stp (stp setup)

HI!
I have a small network. I have 3 300-28 cisco switches. I already connected my 3 servers and clients with the switch 1 and now I want to add more clients and I need to add my other two switches in the network. Please guide me with the simple configuration So I can connect them all and avoid loop (stp). Thanks

Hi Nagaraja Thanthry!
Thanks for your reply. I am implementing it tomorrow. By just conecting the switches together at trunk ports will there be no loop? I don't want my network chowk. I hope it will work well. I might need further help, please reply.
1. I will do setting on all switches. Assign IP addresses to switches (to Vlan 1 default).
2. Set one port (e.g 28) as trunk and all others as Access on all three switches.
3. Then I will connect the switches with each other at trunk ports. Hope there will be no loop in this setting.
4. Do I need to set any setting for stp in switches ?
Please reply one by one thanks.
I am using 192.168.0.1 255.255.255.0 IP range.
Best Regards,

SG-300 series switches - Network loop / broadcast storm question

So the SG300's have STP on them and prevent network loops when other switches on the network also support STP too. However, if someone plugs in a non-managed switch that doesn't support STP with a network loop, is there anything within the SG300 switches to help isloate and/or prevent that from happening?
(I currently have port mirroring turned on for one port and a network sniffer attached awaiting the incident to happen again).
Thanks,
Chris

Hi Chris, the lowest cost path connection will go to a discard state on the interface of the SG300 switch. So, even if the unmanage switch has 2 physical connections, the spanning tree will shut down one port to prevent this loop.
-Tom
Please rate helpful posts

Cisco switch sg-300-10mp

I am able to log in via web gui but not all text is visible .
did reset several times .
any ideas ?

Hi Oran,
Please check this link may help you on this issue :
https://supportforums.cisco.com/discussion/12358601/sg200-50p-web-interface-problems
Please rate this post or marked as answer to help other Cisco customer
Thanks
Mehdi

SG 300-28 Switch - Jumbo Frames Problem.

I just got the SG 300-28 28 port switch tonight and got it up and running however, i've encountered a problem regarding jumbo frames. In the documentation and product brochures, it states the SG 300 switches supports jumbo frames up to 10k. When I first setup the switch and enabled jumbo frames, i was getting very slow speeds in my network transfers (800kb/s !!!). All the workstations are running Intel PCIE nic cards with jumbo frames enabled at 9014 bytes. After some troubleshooting, i lowered the frame size to 4088 bytes and everything returned to normal with fast speeds.
I had a suspicion that it might be the switch that is causing the network slowdown with 9k frames; I went ahead and enabled the 9k jumbo frame settings on my NICs again and started to ping other workstations on the network using the "don't fragment" flag. It turns out, the largest packet that i can send out is 8972 bytes. This is a little far from 10k frames that is stated in the documentation and brochures. Please correct me if i'm wrong, but it seems that i've stumbled into a bug in switch.
Time for a firmware update?

Hi Dickson C,
Interesting query.. TCP, UDP and ICMP packet overhead are fairly negligible according to the information below i would think about 94 bytes for ethernet plus tcp overhead.
The switch would internally label the ethernet frame to identify what VLAN the frame is in (even Vlan 1), so an extra 4 bytes would be used within the switch for that.
Ethernet frame format:
6 byte dest MAC addr
6 byte src MAC addr
[4 byte optional 802.1q VLAN Tag]
2 byte length/type
46-9014 byte data (payload)
4 byte CRC
Ethernet overhead bytes:
12 byte intergap + 8 preamble + 14 header + 4 trailer = 18 bytes/packet w/o 802.1q
12 byte intergap + 8 preamble + 18 header + 4 trailer = 22 bytes/packet with 802.1q
TCP encapsulated in Ethernet:
Assuming no header compression (e.g. not PPP)
Add 20 IPv4 header or 40 IPv6 header (no options)
Add 20 TCP header
Add 12 bytes optional TCP timestamps
TCP overhead can be 52 bytes
Ethernet + TCP overhead around 52+22 bytes = 74 bytes
Your Intel ethernet NIC supports around 9500-byte, so the datasheets from intel suggest for a jumbo frame , but you have it enabled at 9014 bytes.
So your NIC enabled at 9014 bytes - 74 bytes for Ethernet and TCP packet overhead= approximately 8940 bytes of data.
You say you are getting packet data throughput around 8972 bytes.
Check my maths, I have made a few assumptions. What you reckon, worth a call to the Small Business Support center to double check, please open a case and report back with the results. I really may be way off in some of my assumptions.
regards Dave
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html

Questions on setup my SG-300-10MP switch

Similar Messages

Maybe you are looking for