SG300-28P Voice VLAN issue

Hi,
I was running firmware 1.1.2.0 and everything was working fine on 2 of these switches, connected via fiber. I tried upgrading to the latest firmware (1.3.5.58) and had no luck. Our phones which are Avaya 9650 VOIP handsets could not find the router, would not find DHCP, and were waiting for LLDP. The update was only applied on the further away switch from the PBX, yet it still messed up the other switch. I put the firmware back to the original active version and everything started working again.
Nothing else changed except when I rolled back from the firmware version It left any phones plugged in to ports, it changed their tagging to untagged. I put this back and everything worked fine.
Is there an incompatiblity with this firmware with my phones, or what else could be the problem?

https://supportforums.cisco.com/search.jspa?peopleEnabled=true&userID=&containerType=14&container=2141&spotlight=true&q=1.2.7.76+xml
If you want to dig through some posts.
I'm sure could find some. It looks like the 1.2.7.76 release notes were removed off the download page even.
-Tom
Please mark answered for helpful posts

Similar Messages

302-08MP Voice Vlan issue

Hi,
I have a 302-08Mp attached to my network, it is plugged directly into a C3560G, however when i plug a phone into this switch i get a 'configuring ip' message up on the phone. The voice vlan is set identical to the 3560 but in the logs i get an error message stating
%CDP-W-VOICE_VLAN_MISMATCH: voice VLAN mismatch detected on interface gi1.
Can anyone help me solve this issue?
Thanks in advance

Tom,
Sorry for teh delay i needed to get someone at the remote location i could trust to reboot the unit. The voice vlan is 20 and the rest run on vlan 1
the 302 is set as
interface gigabitethernet1
macro description "switch | no_switch | switch | no_switch | switch | no_switch
| switch | no_switch | switch | no_switch | switch | no_switch"
exit
macro auto disabled
macro auto processing type host enabled
macro auto built-in parameters ip_phone_desktop $max_hosts 10 $native_vlan 1
and runs sw version 1.1.2.0
the 3560 is set
interface GigabitEthernet0/3
description Link to SW3
power inline never
switchport trunk encapsulation dot1q
switchport mode trunk
switchport voice vlan 20
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust interface GigabitEthernet0/3
description Link to SW3
power inline never
switchport trunk encapsulation dot1q
switchport mode trunk
switchport voice vlan 20
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
Thanks

About SRW224G4P Voice vlan issue

Hi,
I've configured the SRW as many vlan, use vlan 212 for voice, 348 for data and connect with cisco IP Phone.
vlan database
vlan 210-216,345-348
exit
voice vlan id 212
interface fastethernet1
storm-control broadcast enable
storm-control broadcast level 10
storm-control include-multicast
port security max 10
port security mode max-addresses
port security discard trap 60
spanning-tree portfast
switchport trunk allowed vlan add 212
switchport trunk native vlan 348
macro description ip_phone_desktop
!next command is internal.
macro auto smartport dynamic_type ip_phone_desktop
but when I show voice vlan,
it shows:
=====================================
1ASW01#show voice vlan
Administrate Voice VLAN state is auto-triggered
Operational Voice VLAN state is auto-enabled
Best Local Voice VLAN-ID is 212
Best Local VPT is 5 (default)
Best Local DSCP is 46 (default)
Agreed Voice VLAN is received from switch 34:62:88:73:05:c9
Agreed Voice VLAN priority is 0 (active static source)
Agreed Voice VLAN-ID is 216
Agreed VPT is 5
Agreed DSCP is 46
Agreed Voice VLAN Last Change is 03-May-13 05:06:31
=====================================
I don't know why vlan 216 become the voice vlan ?
I've tried the modified the macro build-in parameters,
macro auto built-in parameters ip_phone $native_vlan 348
macro auto built-in parameters ip_phone_desktop $native_vlan 348
but system could not modify $voice_vlan value.
how to fix it ?

Hi Skywings,
So I am guessing the above output is after the change, right? If this is true it looks like something went wrong during the configuration process. Auto Voice VLAN process has two main phases where the first one is related to communication between switches and other Cisco infrastructure devices and synchronizing the Voice VLAN ID. The second phase is related to identifying the end device as phone. What I can see in your case that the first phase is failing somehow since the voice VLAN ID is different than locally configured. Can you share with me your running and also startup config plus CDP neighbours? You may use private message.
Regards,
Aleksandra

SG300-28P L3 vlan Question

Hi,
I am struggling for last 20 days to figure out how to change IP on my switch. When the switch came up 1st time, it grabbed a DHCP address from my server. I changed configuration to L3 config instead of default L2. After that point it doesn't give me an option to change the static IP. I changed to static IP but it lets me change the mask only.
My need is to change the vlan1 interface IP to be the default gateway of .1. So far I am unable to do this. Attached screenshot shows the IP address field is not modifyable.
Any ideas?

I will have to buy that USB/Serial cable now. I could never get the telnet or SSH to work on this switch. Even I opened up whole rulebase. See attached screenshot.
Off topic:
I am surprised why Cisco didn't choose to implement CDP on these switches. There is a MIB loaded but no option to turn up CDP.

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

SG300-28P - POE not correctly supported on all ports - possible firmware or hardware issue

So, I spent some time this weekend troubleshooting the issues I've had with the new SG300-28P switch and POE to many of my devices in the office. As a recap, I cannot utilize all of the 24 POE ports on the switch for POE purposes. Really only every other port [with a few odd combinations thrown in between]. In addition, the SG300-28P switch, on occasion, is sending POE to non-POE devices [e.g. my Ruckus Zone Director 1106].
Here are my POE devices [all 802.3 af-compliant]:
3 Ruckus 7982 access points
1 Pakedge access point
2 home-automation controllers
2 Polycom voip phones
I called Cisco support several times in regards to this problem, and they figured it was a hardware issue - a faulty switch. So, Cisco sent me a replacement SG300-28P, which I hooked up today. The exact problem still occurs. Default configuration [fresh out of the box]. No way I can land, for example, the 3 Ruckus 7982 AP's on ports 1, 2, and 3 [or ports 1,13, and 2]. I have to put them on ports 1, 3, and 5 in order for them to power up. In addition, I can't plug any other POE devices on the ports either between or below them.   I had to skip another port bay. This is very odd behavior!!   Two Cisco SG300-28P's in a row with the same problem.
However, I also had one of the new Cisco SG300-10P switches in my possession for a recent project of ours. I decided to hook up the same POE devices to this switch. ALL POE devices were recognized and worked! No need to skip a port. And it didn't matter what device was plugged in first or not. I am now convinced that it is either a hardware issue [bad power supply/transformer?] inside all of the SG300-28P switches, or a firmware issue.
Both of the SG300-28P switches were running firmware 1.1.2 [the latest on Cisco's website]. So, I decided to install an older firmware version on the SG300-28P switch that I'm returning [installed 1.1.1.8].   Here's what I found out. I could then plug 2 POE devices [e.g. two Ruckus AP's] in adjacent horizontal ports, but not three in a row. In addition, not all adjacent ports. It's funky. For example, I could plug an access point in ports 20 and 21, but not in 21 and 22. No rhyme or reason in how it worked. And I still couldn't plug an access point in adjacent vertical ports [e.g. ports 1 and 13]. BUT...
It's interesting that the same exact switch that would not initially allow 2 horizontally-adjacent POE ports to be utilized WOULD allow 2 horizontally-adjacent POE ports to be utilized when running a different firmware version.   It's also interesting to note that when plugged into a "non-working" POE port, the SG300-28P would actually make a small whining noise. Very subtle noise; I could hear it when approx. 1ft away from the switch.   The noise was not noticeable when ports were skipped [and POE actually worked]. Therefore, I believe that Cisco has some SG300-28P firmware bugs [at least in the last two versions of firmware] that is not truly allowing all 24 ports to utilize POE correctly. This problem does not exist with the SG300-10P switch.
I'm really interested to hear what Cisco's reply and findings on this matter would be. And would welcome a reply from one of their senior support team members/managers who could actually experiment with this, too.   In addition, I'd like to know when they think a solution could be created if it's firmware-related. If hardware-related, I don't think I'll be recommending any 28P switches in our projects. Perhaps just the regular SG300-28 with a separate SG300-10P. It's a shame because the SG300-28P is more of a bargain when compared to the two separate components.

show power inline
Port based power-limit mode
Unit Power Nominal Power   Consumed Power   Usage Threshold   Traps
1     On      180 Watts     13 Watts (7%)          95         Disable
Port      Powered Device         State          Status    Priority   Class
gi1                               Auto            On      critical class0
gi2                              Never           Off        low     class0
gi3                               Auto        Searching   critical class0
gi4                              Never           Off        low     class0
gi5                               Auto            On      critical class0
gi6                              Never           Off        low     class0
gi7                               Auto            On      critical class2
gi8                               Auto        Searching     low     class0
gi9                               Auto        Searching     low     class0
gi10                              Auto        Searching     low     class0
gi11                              Auto        Searching     low     class0
gi12                             Never           Off        low     class0
gi13                             Never           Off        low     class0
gi14                             Never           Off        low     class0
gi15                             Never           Off        low     class0
gi16                             Never           Off        low     class0
gi17                             Never           Off        low     class0
gi18                             Never           Off        low     class0
gi19                             Never           Off        low     class0
gi20                              Auto        Searching     low     class0
gi21                             Never           Off        low     class0
gi22                              Auto        Searching     low     class0
[0mMore: , Quit: q or CTRL+Z, One line:                                                          gi23                              Auto        Searching     low     class0
gi24                              Auto        Searching     low     class0
show power inline gigabitethernet xx (for each device plugged in)
Port      Powered Device         State          Status    Priority   Class
gi1                               Auto            On      critical class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is on - valid resistor detected
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            3
Invalid Signature Counter: 17583
Port      Powered Device         State          Status    Priority   Class
gi2                              Never           Off        low     class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is off - user setting
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            0
Invalid Signature Counter: 0
Port      Powered Device         State          Status    Priority   Class
gi3                               Auto        Searching   critical class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is off - detection is in process
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            2
Invalid Signature Counter: 1
Port      Powered Device         State          Status    Priority   Class
gi4                              Never           Off        low     class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is off - user setting
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            0
Invalid Signature Counter: 0
Port      Powered Device         State          Status    Priority   Class
gi5                               Auto            On      critical class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is on - valid resistor detected
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            0
Invalid Signature Counter: 0
Port      Powered Device         State          Status    Priority   Class
gi7                               Auto            On      critical class2
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is on - valid resistor detected
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            0
Invalid Signature Counter: 0
Port      Powered Device         State          Status    Priority   Class
gi13                             Never           Off        low     class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is off - user setting
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            1
Invalid Signature Counter: 0
Port      Powered Device         State          Status    Priority   Class
gi14                             Never           Off        low     class0
Power limit (for port power-limit mode): 15.400W
Port Status:               Port is off - user setting
Overload Counter:          0
Short Counter:             0
Denied Counter:            0
Absent Counter:            0
Invalid Signature Counter: 0
show interfaces advertise gigabitethernet xx (for what ports are of interest)
Port: gi9
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
                                  1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement    yes    no     yes   yes   yes yes
Oper Local link Advertisement     -      -      -     -     -    -
Oper Remote link Advertisement    -      -      -     -     -    -
Priority Resolution               -      -      -     -     -    -
Port: gi10
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
                                  1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement    yes    no     yes   yes   yes yes
Oper Local link Advertisement     -      -      -     -     -    -
Oper Remote link Advertisement    -      -      -     -     -    -
Priority Resolution               -      -      -     -     -    -
Port: gi11
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
                                  1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement    yes    no     yes   yes   yes yes
Oper Local link Advertisement     -      -      -     -     -    -
Oper Remote link Advertisement    -      -      -     -     -    -
Priority Resolution               -      -      -     -     -    -
Port: gi21
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
                                  1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement    yes    no     yes   yes   yes yes
Oper Local link Advertisement     -      -      -     -     -    -
Oper Remote link Advertisement    -      -      -     -     -    -
Priority Resolution               -      -      -     -     -    -
Port: gi22
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
                                  1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement    yes    no     yes   yes   yes yes
Oper Local link Advertisement     -      -      -     -     -    -
Oper Remote link Advertisement    -      -      -     -     -    -
Priority Resolution               -      -      -     -     -    -
Port: gi23
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
                                  1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement    yes    no     yes   yes   yes yes
Oper Local link Advertisement     -      -      -     -     -    -
Oper Remote link Advertisement    -      -      -     -     -    -
Priority Resolution               -      -      -     -     -    -

VLAN communication between 2 SG300-28P using one LAG

Hi,
I have 2 SG300-28P without a router used for back-end network usage.
The switches are configured in L2.
I would like to configure on both switches:
The default VLAN with Id 90
One VLAN with Id 80 to access the databases
One VLAN with Id 70 to access the backup server
One agregate with ports 25/26/27/28
Ports 1 to 8, 13 to 20 with VLAN 80 (90UP/80T)
Ports 9 to 12, 21 to 24 with VLAN 70 (70UP)
Computers connecting in VLAN 70 will only talk to VLAN 70.
I would like to use the access mode for ports in VLAN 70.
Computers connecting in VLAN 80 will only talk to VLAN 80.
It seems that the servers on VLAN 80 on switch 1 can communicate with servers on VLAN 80 on switch 2.
My problem is that the servers on VLAN 70 on switch 1 don't access the servers on VLAN 70 on switch 2.
I suppose that this is due to the LAG 25/26/27/28 configured 90UP.
Any idea to resolve this problem?

The LAG is like any other link. It is configurable. You should be able to log the cli
config t
int po1
switchport mode trunk
switchport trunk native vlan 90
switchport trunk allowed vlan add 70,80
-Tom
Please rate helpful posts

SG300 voice vlan problem with UC520

Hi Forumers'
My problem statement:
- refere to attached topology.png, this is how my network structure look like
- the IP phone after boot cannot get connected, so it can't download the XML config file from UC520. suspicious switching problem.
- my configuration shown at topology.png and my vlan voice config show as voice vlan setting.png
- My requirement is SG300 switch single switchport to carry vlan data and vlan voice.
- what is the trunking mode for voice VLAN siwth a IP phone+data should i configure? is it switchport voice vlan vvid, switchport voice vlan dot1p, switchport voice vlan untagged or switchport voice vlan none to suite above requirement?
thanks
Noel

Hello Noel,
Sorry for the late reply, things have been quite hectic around here lately
1. Why use trunk? the UC520 only have vlan voice (vlan 20)
Do you mean that the data VLAN is handled by another device ? Still I would leave it as a trunk in order to be able manage the UC through the data VLAN. (Unless for security or other reasons you would choose otherwise of course)
2. The UC520 got CUE (voice messaging), how should i design the service module uplink to the core switch?
Nothing in particular has to be done for this, CUE is handled and routed inside the UC520, the CUE vlan (default ID =90) is only used if you have another CUE in the network
1. i guess i did this: swithcport tagged vlan 20, untagged vlan 10. is it ok for this setting?
If the Voice Vlan on the switch and on the UC520 has been defined as VLAN 20 (default = VLAN 100) this is perfect. Verify if both on the UC and on the switch, the voice VLAN ID is set to 20.
1. so if i just point the phone to vlan 20 (vlan voice), should i create the LLDP network policy?
If you are ready to configure the VLAN manually on the phone, you don't need the LLDP policy, that is correct.
The LLDP policy is being used for having the phones automatically choose the VLAN you defined, so you don't need to set it manually.
Hope this answers your questions ?
Best regards,
Nico Muselle
Sr. Network Engineer - CCNA

Multilpe Voice Vlans in SG300

Dear Team
I am using sg300 for voip. i have created 5 voice vlans for different departments in my office.
but my voip is not working. only 1 voice vlan is working out of 5 voice vlans. The voice vlan working is agreed voice vlan in sh voice vlan commad
Kindly suggest
Regards
ABHINAV

Hi Ankur, this switch only supports 1 voice vlan. If you genuinely require 5 different voice vlan then you should manually set the ports or create LLDP policies for each voice VLAN you need.

Cisco sg200 voice vlan dhcp issue

i have cisco sg200 50p connected to cisco 3750 switch. i just wanted to separate voice (vlan2) and data (vlan1) VLANS. I created vlan 2 as my voice VLAN and separate dhcp server for vlan 2 to give ip addresses to phones. however the ip phone connected to my voice vlan (vlan 2) is not receiving ip address from my dhcp server in vlan 2.
the dhcp server is connected to 3750 switch with an access port (vlan2-voice)
two switches are connected via trunk ports and allowed vlan 1&2
ip phone is connected to sg200 via access port (vlan 2) -
note - there is no pc connected to ip phone
I really appreciate if anyone can help me with this issue

Hi Tom
Thank you for the support. The phone is now getting the IP from the DHCP on its own VLAN (vlan2 ) according to your configuration. However i need to configure the auto voice VLAN based on OUI feature which is in SG200 switch.
The problem is, the switch not allowed me to configure auto voice vlan feature when the port connected to IP phone is in ACCESS mode (it has to be a trunk). I know according to cisco catlyst guidelines this is totally incorrect bcz they say "Voice VLAN is only supported on access ports and not on trunk ports, even though the configuration is allowed"
I think its not valid for Small business switches . Anyway, when i make the said port TRUNK it works (by assigning 1U & 2T- automatically).But the phone does not get an IP address from my DHCP server then.
Can you help me with this if I am missing some configuration. Thank you once again

SG300-28P QoS Question

Hello, I have SG300-28Ps as the PSE's for my IP telephone system. The phones are tagging their voice packets as DSCP 46 as directed by auto voice vlan. The QoS settings on the switch are at default - Basic Mode, Trust DSCP, strict priority, etc.
On the PBX itself, DB programming allows me to program the 'Type of Service' for the voice packets. The recommended value in the manual was 184 which makes sense, as this decimal value for ToS corresponds to DSCP 46, CoS 5, etc.
The question comes though, do I need to change the trust mode on the switch? I'm not real clear on the differences between them.
Regards,
-Brayton

Hi Brayton,the trust mode doesn't need to be changed. 802.1p specifies a 3 bit field called a PCP within the etherner frame header when using tagged vlan frames. This will contain a class of service priority.
The CoS is able to map to DSCP values. The DSCP has a 6 bit field called diffserv (differentiated service). CoS values are able to be mapped to DSCP values. Video is generally CoS 4 while voice is generally CoS 5. Within the SX300 you are able to manually set the mapping to any value you'd like. With trust mode, the switch will basically accept and agree with whatever the tagged ethernet frame contains. Without trust mode, the switch will remark the packet based on the PCP and DiffServ value to fit in to the different categories.
-Tom
Please mark answered for helpful posts

TCAM Utilization on SG300 28P

Hi There,
I was wondering if you could help me aviod a situation where the limit of 100IP's is reach on my client new site using 3 x SG300 28P switches.
I have 1 x SG300 28P in Layer 3 mode which is the default gateway for all the IP phones that will be installed. The PC's ont he network will use the existing default gateway which is another router. I will have another 2 x SG300 28P devices in layer 2 mode which are connected to the Layer 3 SG300 28P.
My question - Are the IP's that registered against the TCAM limit only the devies which physically plug into the SG300 28P switches ? I assume other computers on the network which are plugged into another switch and don't use the default gateway of the SG300 (its only for voice) they then wouldn't be registered in the TCAM ?
The site has around 65 computers currently and obviously plugging in 65 IP phones we're going to hit a limit of over 100 IP's. My thoughts were to potentially keep the computers and Phones seperate on a couple of the switches to keep the IP's in the TCAM to a minimum.. Is this possible?
Any advice would be welcomed!
Brett

Hi Thomas,
Thanks for the quick reply.
Just to confirm though, I want to be sure that the Layer 3 SG300 28P will have have all the IP phones from the other Layer switches using it as the default gateway for the voice VLAN - Obviously this will then register 60 + IP addresses. If I have the computers plugged into the back of the Phones (which is then into the SG300 switches) this will then register another 60 IP's correct? If I don't patch these computers into the phones and have them in a seperate switch then the TCAM address list doesn't care about these computer IP's? I do believe we'll have traffic routing from the computer to the phones even if they are on a different switch so would that then add these addresses to the TCAM?
The reason I ask this to be clear is that I read someone else going over the 100 limit and causing the network to slow down which with voice traffic I want to avoid...
Brett

Voice VLAN Help Please

My customer has 2 SG300-52P and 5 SG300-28P. We installed a VoIP phone system earlier this year. At the time of install we placed the phone system on the native VLAN 1. Now they want to move the phone system to a new VLAN because their class C subnet is running out of addresses. DHCP is handled by their Active Directory and their router/firewall is an Untangle Box. The SG300 switches have a basic configuration only.
To move the phone system to a new VLAN I created VLAN 20 on every switch. I then turned Auto Voice VLAN on. I have every port on every switch set to trunk. Computers are plugged into back of phones. I then created a virtual interface on the Untangle Box for VLAN 20. The Untangle Box is also handling DHCP for the new VLAN. Active Directory is still handling DHCP for native VLAN.
From each switch I can ping the gateway of the new VLAN. From each computer I can ping the gateway and the phone system on the new VLAN. However, the phones will not grab an address on the VLAN and when they are set to static, they cannot communicate with other devices on the VLAN.
Any help would be highly appreciated. I am not sure what I am overlooking.

Here is an example of part of a working switch config with Zultys phones where voice VLAN is 100 and data VLAN is 10:
vlan database
vlan 10,20,100
exit
voice vlan id 100
interface fastethernet1
description "RCP and Voice"
switchport trunk allowed vlan add 100
switchport trunk native vlan 10
interface fastethernet2
description "RCP and Voice"
switchport trunk allowed vlan add 100
switchport trunk native vlan 10
In your case you need a trunk port with VLAN 20 tagged on your firewall (or an access port to a separate physical port on VLAN 20. The default gateway served to the phone (or put there statically) should be the interface on the IP. Then you may also want to allow inter-vlan routing for admin access or MXIE if you are using it.
One thing to note on Zultys is by default I think the device profile disables LLDP, but on the phones it is enabled out of the box. So the first time a phone downloads its config from the Zultys it may turn of LLDP unless you checked the box to keep it on.

Voice VLAN with SRW224G4P

Hi all,
I have been trying to config a voice vlan into this switchs for the last 3 hours and for me this is impossible... I know how to do in a IOS switch but with this switchs is a nightmare...
I have this topology,
PC ---- IP phone ----- SW1 SRW224G4P -------- SWCORE SRW2024 --------- Router 2921 CME
I have this config in my router,
interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
interface GigabitEthernet0/0.1
description LAN
encapsulation dot1Q 1 native
ip address 192.168.5.95 255.255.255.0
ip virtual-reassembly in
interface GigabitEthernet0/0.100
description Voice VLAN
encapsulation dot1Q 100
ip address 192.168.251.1 255.255.255.0
ip virtual-reassembly in
SW1 has created the VLAN 100 and enabled as VOICE VLAN
The first 3 octes of the mac of my phone is inserted into Telephony OUI Table
The Auto Voice VLAN Membership is enabled in the port where phone is attached.
The port that is conected to SWCORE has the vlan 100 configured as tagged.
SWCORE has created the VLAN 100 and enabled as VOICE VLAN
The port that is conected to SW1 has the vlan 100 configured as tagged.
The port that is conected to router CME has the vlan 100 configured as tagged.
If I config other port into SWCORE with VLAN 100 tagged I can ping from CME to that host.
Could be the problem a vlan propagation error?
Somebody could help me? I am desperate...
Thank you in advance.

Hi David,
Thank you for the purchase of the switch.
.Like anything, even riding a bike, the switch is actually very easy to configure, if you have a little bit of practice on it..
You mentioned you are using the " Telephony OUI Table" i guess you have a SF300-24P or ordering p/n SRW224G4P-K9-NA. Please be specific with the switch models you are using.
Are you using the older SRW series or the refreshed SRWxxx-K9 (300 series) switch in the core?
Firstly, make sure you are using version 1.1.0.73 of the switch firmware. Do that change now or verify that 1.1.0.73 is the active image on the switch.
The switch has two areas for storing firmware images. It stores the new firmware in the unused image area. Check the administration guide for how to upgrade firmware and select new firmware for the next reboot.
CDP is enabled on the switch when you use the new software, it was not there with older firmware, hence my insistance at upgrading firmware.
( Personally i would prefer you to have a catalyst switch for your ISRG2 CME application, for tech support purposes. But this is the land of the free..)
I found the following when I added my SG300-28P to a VLAN aware UC500.
The UC500 was advertising vlan100 as a voice vlan, configured that by Cisco Configuration Assistant, you might try CCP on your ISR.
I had a IP phone plugged into switch port G7 and a uplink to my UC500 via port Gig27.
The following in blue is a screen copy from my 300 series switch CLI interface.
You will note the switch automatically populated both VLAN and port information, the only command I added was "no passwords complexity enable," and some usernames, which removed from the screen capture below.
the switch basically configured itself.
------------------ show system ------------------
System Description:                       28-port Gigabit PoE Managed Switch
System Up Time (days,hour:min:sec):       00,00:12:04
System Contact:
System Name:                              switch4cf17c
System Location:
System MAC Address:                       d0:d0:fd:4c:f1:7c
System Object ID:                         1.3.6.1.4.1.9.6.1.83.28.2
Fans Status:                              OK
------------------ show version ------------------
SW version   1.1.0.73 ( date 19-Jun-2011 time 18:10:49 )
Boot version 1.0.0.4 ( date 08-Apr-2010 time 16:37:57 )
HW version    V01
Gateway IP Address        Activity status       Type
192.168.10.1            Active                  dhcp
    IP Address         I/F       Type       Status
192.168.10.17/24    vlan 1    DHCP        Valid
------------------ show ipv6 interface ------------------
IPv6 is disabled on all interfaces
------------------ show running-config ------------------
interface gigabitethernet7
storm-control broadcast level 10
exit
interface gigabitethernet7
storm-control include-multicast
exit
interface gi27
spanning-tree link-type point-to-point
exit
vlan database
vlan 100
exit
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______________
hostname switch4cf17c
no passwords complexity enable
no snmp-server server
interface gigabitethernet7
macro description ip_phone_desktop
exit
interface gigabitethernet27
macro description "switch | no_switch | switch"
exit
interface gigabitethernet7
!next command is internal.
macro auto smartport dynamic_type ip_phone_desktop
switchport trunk allowed vlan add 100
exit
interface gigabitethernet27
!next command is internal.
macro auto smartport dynamic_type switch
switchport trunk allowed vlan add 100
exit
switch4cf17c#sh cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - VoIP Phone
                  M - Remotely-Managed Device, C - CAST Phone Port,
                  W - Two-Port MAC Relay
Device ID        Local      Adv Time To Capability   Platform     Port ID
                   Interface Ver. Live
SEP503De50F133A      gi7      2     158      H P     CISCO IP        eth0
                                                     Phone
                                                     SPA525G2
68bdab0fdcfd        gi27      2     169      S I     Cisco SG         gi9
                                                     300-10P
                                                                                           (PID:SRW2008P-K9)-VSD
switch4cf17c#sh vlan
Vlan       Name                   Ports                Type     Authorization
1           1                gi1-28,Po1-8           Default      Required
100         100                 gi7,gi27            permanent    Required
Switch automatically figures which ports should be tagged into VLAN 100.
I did not tell the switch it was connected to VLAN100. I did not add vlan100 to the VLAN database.
So get the ISR router to advertise VLAN100 as a voice vlan.
regards Dave

Problem with switch SG300-28P Poe and Avaya 1408 telephone

Hi Team
We have a model SG300-28P Switch 28-Port Gigabit PoE Managed Switch, in every port we are allowing the voice VLAN and data VLAN (trunk), happens to be off this type of phone, we reconnect the cable and port the switch is dropped, so that the voice vlan phone is lost and no longer work.
Thanks for your comments.
Regards

Hi Yesenia, did you contact Avaya support? Did you configure the phone for a voice and data vlan?
I'm trying to dig through the Avaya website and looking at the fact sheet and user guide it has no mention of VLAN.
Is the switch supported for the usage of Avaya Aura Communication Manager call processing system?
-Tom
Please mark answered for helpful posts

SG300-28P Voice VLAN issue

Similar Messages

Maybe you are looking for