×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

vlan problems on an SF 300-24P

Unanswered Question
Nov 30th, 2011
User Badges:

I have a stack of SGE2010P switches with 3 vlans (1, 10 and 255) on it. Connected to it via a trunk port, I have a SF300-24P.


On the trunk ports, I have vlan 1 untagged, vlans 10 and 255 tagged (on both sides, obviously).


On the SGE2010 stack, I can set a ports primary vlan id to vlan 10, and workstations work correctly.


On the SF300, if I set a port to type general, and the ports default vlan to 10  (on the port to vlan page), I cannot get any communication to work.


This is my first time with a non-CLI switch, and am having real problems figuring out how to troubleshoot this problem.


Any pointers would be appreciated.


Thanks


Mike

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
David Hornstein Wed, 11/30/2011 - 22:21
User Badges:
  • Gold, 750 points or more

Hi mike


With the SF300 switch, why not leave the switch port in trunk  mode .


step 1.  verify and if needed upgrade to firmware version 1.1.2.0 as of yesterday,.  but 1.1.1.8 will give you CLI


step 2. put the ports back into trunk mode, the default setting.


Step 3, you have already created the vlan, but i went through the process below..


vlan.jpg



Step 4.  The ports are all in the default TRUNK  mode allowing one untagged vlan and multiple tagged vlans per port.



vlan1.jpg



Step 5.  I selected VLAN 10  from the drop down and then clicked Go.


vlan2.jpg



step 6. Below I selected ports 5 to 7 as untagged in vlan 10  and my trunk port 28 tagged in vlan 10 then clicked apply.


(port 28 will now transmit untagged ethernet frames belonging to the default vlan and also tagged frames for vlan 10.)


vlan3.jpg


In the following screen capture,  I verified that ports 5 to 7  were now excluded from the default vlan.



vlan4.jpg



That's it. hopefully pretty easy to duplicate.



Below is the CLI created via the GUI, but to access the CLI interface  via the  telnet,  you must  first enable telnet service  as seen by the following screen capture.





switch4cf17c#sh run

interface  gi28

spanning-tree link-type point-to-point

exit

vlan database

vlan 10,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 snmp-server server

ip telnet server

interface gigabitethernet5

switchport trunk native vlan 10

exit

interface gigabitethernet6

switchport trunk native vlan 10

exit

interface gigabitethernet7

switchport trunk native vlan 10

exit

interface gigabitethernet28

switchport trunk allowed vlan add 10

exit

interface vlan 10

name blue

exit

switch4cf17c#


Hope this helps


regards Dave

Actions

This Discussion