Comments on: Implementing VLAN trunking

By: Switch konfigürasyonu içindeki şu komutların aralarında ki farklar/ve neye yaradıkları hk. yardım

Fri, 02 Sep 2011 00:53:36 +0000

[...] VLAN'ları trunk kanaldan geçirmeye yarar. Aşağıdaki linke bakarsan daha iyi anlayabilirsin. Implementing VLAN trunking | Technology for Mortals switchport trunk allow vlan 1-3 diyerek o trunk kanal içerisinden 1 ve 3 vlan'larına izin [...]

By: bharat

bharat — Fri, 19 Aug 2011 16:57:44 +0000

good one

By: Mike

Mike — Fri, 22 Jul 2011 18:01:03 +0000

I have an issue where ive a 1900 series router and the isp has configured a L2 link to hq.
there are 3 vlans on the one port that they have presented to me.

normally id just do suinterfaces on router port and then configure those interfaces wiith vlan tag and encapsulation dot1.q. however the isp say that they just need the vlan numbers an no encapsulation. i dont know how to do this short of just connecting a switch.

i have to use the router as the client has bought it.
i have a wic 4esw
i must route subnets, any ideas?

By: Kysersosai

Kysersosai — Thu, 27 Jan 2011 20:44:24 +0000

does anyone know where i can get the proset drivers for x64

thanks

By: lsf

lsf — Mon, 20 Dec 2010 20:32:31 +0000

@xtropx That is why you have vlan acess ports. A access port adds the vlan tag on packets entering that port and strips the vlan tag on packets leaving the same port.

By: xtropx

xtropx — Sun, 12 Dec 2010 19:25:01 +0000

So wait? If the NICs on your PCs do not support adding the VLAN tag, VLAN’s do not work? Seems kind of pointless to have that extra configuration step….

By: Mark Levy

Mark Levy — Thu, 28 Oct 2010 20:22:41 +0000

You wrote:
On the IOS UI, you would need to enter each interface for all 48 ports and apply 96 individual commands vs. one command on the CatOS!

Actually, on IOS switches, that’s not correct: For example, if you wanted to set all 48 ports on a 2960S to access ports for vlan 120 (or as many common commands for all interfaces that you wanted), you would simply enter a range like this:

config t
int range gi1/0/1 – 48
switchport mode access
switchport access vlan 120
exit

But thanks so much for your articles!

By: Ed Spencer

Ed Spencer — Thu, 26 Aug 2010 15:41:45 +0000

Actually, the data passed to the phones via DHCP varies from manufacturer to manufacturer and how they implement various settings.

Here’s a fairly complete list:
http://www.networksorcery.com/enp/protocol/bootp/options.htm

By: كمك در مورد vlan بندي

كمك در مورد vlan بندي — Sat, 21 Aug 2010 06:21:16 +0000

[...] VLAN های مختلف قابل استفاده باشد !! جهت کامل تر شدن بحث Implementing VLAN trunking | Technology for Mortals …Life is too short to wake up with regrets. Love the people who treat you right Forget about [...]

By: Andy Raven

Andy Raven — Sun, 15 Aug 2010 00:55:48 +0000

@NetEng
Please read my comment, otherwise my finger exercise is wasted. Option 176 seems to only apply to Avaya phones. Option 191 works for Nortel, Polycom, Cisco etc..
However, if you use this configuration on your “enterprise network” then it really is badly organised. You miss the whole point of using this option, which is basically because you are using switches that can’t do CDP or LLDP.
Using these options pollutes the arp cache, the phones temporarily are handed data IP addresses, these MAC-Address translations are stored in the router for a set period of time and any incoming NAT relies on this DB. For many devices to “temporarily” gain data IP addresses means you have to decrease the ARP refresh on the router, which uses up vital CPU power, this has happened on a number of voip installations we have performed where the customer thought they were being clever and it has taken days for us to diagnose the issue.
For any “enterprise network”, CDP is the preferred way, when you state you have PoE cisco switches then you would have to be completely stupid to not use the default CDP config on the switch, or am i missing something? If your IP phones do not support CDP then you should have waiting longer to upgrade.

I beg people to ignore the above comments and not use these data DHCP options, they are crude, primitive, and designed for companies with a lacking switch infrastructure or simply do not understand networks.
Andy