Hi Deepak,

You shouldn’t configure both for L3… you need to configure L2 between the 2 switches so they can share VLANs (unless you are going to stack them) and then only one of them will act as the L3 between VLANs.

Now there are switches you can use from Cicso (vPC) and Extreme (formerly Avaya) (IST) and others that allow you to run 2 switches under a single dataplane but that’s for enterprise HA and redundancy in conjunction with protocols such as HSRP and VRRP.
Cheers!

If the provider supports Q-in-Q you could just tag 802.1Q taffic across your providers network. If they don’t support Q-in-Q you would need to either route (Layer 3) or you could do some type of GRE tunnel with a Cisco or Juniper router.

Cheers!

Thanks!

Hi Muhammad,

Unfortunately the commands are not the same across manufacturers. That’s not to say that a great many manufacturers are trying to emulate the Cisco CLI these days. While the commands are similar for the majority of vendors they are not identical. I’m sure for a time the other manufacturers worried about Cisco taking them to court similar to how Apple took Microsoft to court over Windows 3.1.

Good Luck!

What’s the difference between basic and advanced “Loadbalance(Mode)”?

Thanks!

-b

i wanna create 3 vlan, 2 vlan data and 1 vlan voice.
in my Office a Switch connected to IP telephones before connect to PC.
how to untagged 2 vlans (voice and data) in one port? please give me some syntax/command for Nortel switch. I have done it in cisco and procurve, but i dont similiar with nortel switch.
help me please.

Thanks

If I want to put a trunk from a nortel to a non nortel switch with only vlan 100 passing the trunk is this config correct?
________________________________________
vlan port 10-12 tagging tagall
vlan members add 1 10-12
vlan members add 100 10-12
vlan 10-12 pvid 1
_______________________________________

in the last line:
why would i need pvid 1 instead of pvid 100, in which vlan 100 is the only vlan that i want from the other switch?

You will not see any route in the routing table until that VLAN is active. In order for the VLAN to be active you need to have at least 1 port that is a member of that VLAN up (link) and running. Now with that said there is a bug in some specific versions of software where the VLAN will not become active, you can test this case by just rebooting the switch and see if that clears the problem. If so then upgrade to the latest software release to resolve the problem.

Cheers!

Problem comes when I set a pair of new VLANs. It is done correctly but I cant ping the ip address assigned to the VLAN either to route anything.

I have noticed that no new LOCAL route appear when I set the IP address of the new VLANS so, whats is happening? why is not any route appearing when I set the IP address of VLANS?

global ip routing is active, and there are VLANs working… Do you have a clue of what should be the problem?

I have follow the step than you have defined to create the new VLANs , IPs and dhcp relay, also I did it using the web interface. After 5 tries I am a bit lost.

Could you help me please?

Alberto.

While it’s technically possible using the QoS filters it’s really not practical.

Hi McAdams,

You probably want to look at this post entitled, 802.1Q VLAN Tagging on a Cisco Catalyst 3750-E.

Good Luck!

This is a nice post you have here but I have a question. I made vlans on a nortel 3510-24t switch just like in your previous post. they are working, I have a cisco switch 3550 that I want to configure some of the vlans like on the nortel switch. How can i create a trank between the cisco and the nortel switch? so that their will not be any communication problem between them?

Thanks.

Hi Joe,

The PVID is the default VLAN for that port. With access ports as in UnTagAll ports the PVID should be set to the same VLAN ID as the VLAN assigned to that port. For example, if port 10 was a member of VLAN 200 the PVID for port 10 would be 200. In the case of a trunk port (802.1q) with UnTagPVIDOnly the PVID is the VLAN that will be sent untagged across the link. In the case of a traditional trunk port (802.1q) the PVID should usually be set to the management VLAN, with discard-untagged-frames enable to prevent any accidental configuration issues.

If you wanted ports 10-15 in VLAN 61 you would issue the following commands;

vlan port 10-15 tagging UnTagAll
vlan members remove 1 10-15
vlan members add 61 10-15
vlan port 10-15 pvid 1

You do need to check and make sure that Spanning Tree is enabled after making any VLAN changes

inter fastEthernet 10-15
spanning-tree learning fast

You can refer to this blog post for a best practice configuration of an ERS 5520 switch.

http://blog.michaelfmcnamara.com/2007/10/nortel-ers-5520-pwr-switch/

Good Luck!

I am only using VLAN 1 for management of the switches, nothing else. I think I will be ok there.

I apologize as I dont know what PVID means in this context, its not required in HP networking. This is for a hotel wireless/wired guest room network.

VLAN 1 = switch management
VLAN 61 = public IP addresses (facing outside)
VLAN 71 = wireless AP management network
VLAN 91 = guest facing network.

On my HP switches, uplink/fiber ports between switches obviously have all VLAN’s tagged. In the HP switches, a wired guest room port would be “VLAN 91 untag”. A wireless AP would be “VLAN 71 untag” and “VLAN 91 tagged”

Can you help me accomplish this with minimal pain? HAHA. Most of the Nortel switches will only have wired guestroom network ports, so besides the uplinks I don’t have a lot of VLAN modifications to do.

Hi Jon,

It’s not hard to understand Avaya (formerly Nortel) switches they behave by the same principles but have slightly different terminology.

unTagAll – access port with a single VLAN associated
TagAll – trunk port with all VLANs getting 802.1q tag headers
unTagPVIDonly – trunk port with the PVID VLAN untagged all other VLANs getting 802.1q tag headers

In an unTagAll configuration the PVID of the port should be set the only VLAN assigned to the port. In a TagAll configuration the PVID is best set to the management VLAN of the network.

It’s highly advisable to NOT use VLAN 1 (the default VLAN on all factory reset switches) as a best practice if at all possible.

If you have additional questions this post might help, http://blog.michaelfmcnamara.com/2012/02/untagall-vs-tagall-on-avaya-ethernet-routing-switches/

Good Luck!

Your posts are very informative. I find myself in the unique situation of having to take over a Network of Nortel switches, having not used Nortel before. My core switches in the configuration are HP, and there are Nortel and HP switches co-mingled througout the network. We already deployed our new network configuration across my core HP switches. We are going to take over the Nortel switches. I do not think I need to start from scratch (factory default) on the Nortels. I think it should be as easy as adding my VLANs to the Nortel switches (I am lucky I picked VLAN numbers that did not already exist in Nortel) and then tagging/untagging ports. I know all VLANs need to be added to the fiber ports for network communication (and I can use your commands above for that). I need help with the following commands if you don’t mind?

VLAN 1 is my management VLAN, and the only thing that needs an IP address, but I do need to change/remove the gateway. My switches are on the same IP scheme as the Nortels, but the gateway will cause issues.

1) Remove the password from a Nortel switch
2) Remove the gateway from VLAN 1
2) remove existing tag/untag from ports
3) in the above posts, I see no mention of “untag”. We use “untag” a lot in HP switches. How do I “untag” ports in Nortel?

My other “thought” is that I could use the existing VLAN’s on the Nortel switches and run a patch cable from my VLAN on my switch, to one of the ports on the existing Nortel VLAN and bridge the communication that way without changing VLANS. I am not sure if I am off base or not.

Hi David,

What version of software in on the RES 4548GT-PWR? If you have software release 5.4 or later you should have the command “ip routing” which will enable the Layer 3 routing functionality in the switch. Assuming this is the only router in your environment you just need to set the devices in VLAN 10 and 20 with their respective default gateways of 192.168.10.1 and 192.168.20.1 and you should be good to go.

You’d probably benefit from reading this blog post, http://blog.michaelfmcnamara.com/2011/01/vlans-ip-routing-ethernet-routing-switch/

Good Luck!

I have a switch 4548GT-PWR, I need comunicate two vlans, I saw your blog but I did the same that your examples and I can not comunicate the vlans this is my configuration, Can you help me please.

vlan create 10 name ITCJ type port
vlan members remove 1 1-5
vlan members add 10 1-5
vlan port 1-5 pvid 10

vlan create 20 name CTTI type port
vlan members remove 1 5-8
vlan members add 20 5-8
vlan port 1-5 pvid 20

interface vlan 10
ip address 192.168.10.1 255.255.255.0 1

interface vlan 20
ip address 192.168.20.1 255.255.255.0 2

so how can I comunicate these vlans, i do not have a router

You need a default route for the switch to respond to any packets outside of the management VLAN. While you might have a route to the switch in your desktop/laptop the switch doesn’t know where to send the reply packets for the 192.168.53.0/192 network.

Look at the routes in my lab switch;

4548GT-PWR>show ip route
===============================================================================
                                        Ip Route
===============================================================================
DST             MASK            NEXT            COST    VLAN PORT PROT TYPE PRF
-------------------------------------------------------------------------------
0.0.0.0         0.0.0.0         192.168.1.1     1        1    1     S  IB     5
192.168.1.0     255.255.255.0   192.168.1.25    1        1    ----  C  DB     0
Total Routes: 2
-------------------------------------------------------------------------------
TYPE Legend:
I=Indirect Route, D=Direct Route, A=Alternative Route, B=Best Route, E=Ecmp Route, U=Unresolved Route, N=Not in HW

The management VLAN by default is VLAN 1, in this case I’ve configured the switch IP address as 192.168.1.0. I’ve also added a default route to 192.168.1.1 which is the primary router in my lab.

4548GT-PWR(config)# ip route 0.0.0.0 0.0.0.0 192.168.1.1 1

If you only have this single ERS 3500 series switch then you must enable Layer 3 (routing) in order to be able to ping the management VLAN. That’s the difference between a Layer 2 switch and Layer 3 switch. With a Layer 2 switch you need a router to connect the different networks and subnets.

Good Luck!

But When I send a ping to switch in vlan 240 I don´t have a reply, I just can ping to switch in users vlan 192.168.53.62, checking Avaya routing manage i found that I need a management route to do what I want, but in manual I can see that router is member of management vlan and I have my router in users vlan. is there a way to solve my problem without change my router to management vlan?

Bye

Hi Jhon,

1) What model of switch? Not every model support CLIP or Loopback interfaces, for those switches it’s either an IP interface associated with a VLAN or the management IP address.

2) You can either route or bridge between your switches (actually you can do both but lets ignore that fact right now). If you bridge using an 802.1q trunk then you should be able to communicate so long as you have the proper route table entries.

3) Yes.

4) No, your learning.

Cheers!