• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3517
  • Last Modified:

Nortel Avaya Switch 4548GT-PWR Vlans and DHCP

I'm new to this but have used Cisco before:

I have some old Cisco 3500 Switches and I'm trying to replace them with a Nortel Avaya Switch 4548GT-PWR switch.

I have setup the VLANs just like the Cisco switch so bascially its mirroring the cisco switch that used to be in place, However when I plug into it, its not grabbing a DHCP license.

I have a windows server 2003 as my AD and DNS and DHCP and the VLAN Scopes are in the DHCP server.

I have enabled DHCP on the switch as well ( I think )

Does anybody have any experience with these Switches? Here is my setup below:

I have a Cisco 6506 switch that is the Switch Engine (it holds all the VLANS) VLAN 172 is for access to my switches via hyperterminal or putty, VLAN 162 is my printers.

Now before the Cisco 6506 switch just had 1 ethernet cord up to the Gigabyte port on the old Cisco 3500, I'm assuming that port was 172, than on the rest of the ports they were 162

So on the Avaya switch I made Port 1 as 172 and then the rest on 162. So I was thinking I could just unplug that ethernet cord from the 3500 switch and put it into Port 1 on the Avaya switch and then plug in the rest of the ethernet cords that go to the printers in the rest of the ports on the Avaya switch.

So far its not obtaining an IP address, however if I change my laptop to a static IP of 162 it shows it connected. My printers all have static IP address however when I try to print to one of them its not working.

What am I doing wrong here, please help
  • 4
  • 4
1 Solution
If several VLANs are going outside your Cisco 6506, apparently VLANs 172 & 162, you have to tag the port 1 of your Avaya so that it can handle the two VLANs at the same time.

* If you can, check the configuration on the Cisco 6506, of the port connected to the Avaya. It must be a trunk port, see all the VLANs that are associated with it. Normally, at least 162 and 172.

* On your 4548GT, configure the port 1 connected to the Cisco 6505, as a "trunk port". (which mean: able to carry several VLANs, as an opposite to "Access port")

* If asked, you can set the PVID of the port to the management VLAN 172, but there's no big deal in your configuration with the PVID.

* More important: set the port 1 in all VLANs that you've seen on the Cisco other side port, at least 162 & 172.

* All the other port of your Avaya must be "Access port", in VLAN 162 if it's printer, that should be already done.

* There's no specific configuration for DHCP, you don't have to enable anything.

* To test: try to ping the Gateway (your Cisco) from the VLAN 162, plug your Laptop in a printer port and configure it with a printer ip address.
You must be able to ping the gateway of each VLAN to be sure that your VLAN configuration is ok, and that the link between Cisco & Avaya is ok.
Neogeo147Author Commented:
Thank you for responding, I'll try that and get back to you on it. The VLANs that the 6506 has in it are:

VLAN1 = = access to switchs
VLAN5 = = vpn
VLAN155 = = voip
VLAN160 = = All users
VLAN162 = = Printers
VLAN165 = = PT to PT
VLAN200 = = Servers

So the ethernet cords go from the 6506 into each cisco 3500.

So currently I have 5 cisco switches that are VLAN 160 that I am replacing with the Ayava 4548GT-PWR and doing 4 in a stack for VLAN160

Then I have another Avaya 4548GT-PWR that I'm going to use as the Printer switch on VLAN162 and I have another switch I'm going to use for VLAN155 and VLAN165

I hope that better explains my configuration I currently have and what I'm trying to replace with, Also do I need to make them seperate or can I just put them all in 1 stack and just configure certain ports as which VLAN is which. Can you see an easier way of doing this.

Thanks for your help
* For the stack vs separate switch: There are no obligation, your configuration is possible in both case, there are only pro/cons.

Stack will be more easier to configure, as you'll get less connection to your Cisco, and you only need to access to the stack to configure a lot of ports.
But it's also a problem in case of failure, you loose the whole stack if you loose the uplink.
So to avoid that you could think about an MLT (cable from different unit going to your Cisco), to double attach your stack to your Cisco, but it's more configuration.

And if you need to make an upgrade, with only one stack, you temporarily paralyse everybody.

Try not to make big stacks, and maybe to load balance your users depending the "function" (user/server) or the criticity.

So it's more up to you...

* For the configuration, here is the philosophy:
- On the Cisco 6506, add a VLAN on a port only if needed. Don't put all the VLANs on all ports if there are no use. You'll avoid problems and errors on the switches.

- For each connection between the router and a switch, you must have the same VLANs on the ports on both side.

- Your ports on Cisco and Avaya uplink must be trunked, to carry several VLANs.

- On Avaya:
-- uplink port with PVID 1 (not 172 as I said before, we talk about the VLAN id here), and configure it with all the VLANs that you need on the switch/stack, must be the number of VLANs as the opposite Cisco port.

-- all the other ports are access, with the VLAN you need.
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Neogeo147Author Commented:
So if I just configure 1 4548 switch at a time:

for instance: The printer switch, I just need to create 1 port as the uplink port for Vlans 162 but if I wanted to add say 165 on that switch I would need to add that Vlan to that port as well and so on and so forth for others if I wanted,

However if I just add 162 vlan on there and then on another switch I just do vlan160, will they be able to talk to each other, Like my Users when they print will the job see that 162 switch?

All the interVlans connection is made by the router, the Cisco 6506.

Each device in his VLAN must be able to talk to its gateway, the x.x.x.1
After it's up to the cisco to route to packet to the corresponding vlan and port.

No worries with the fact that the switch are separate or not.
Think about VLAN like pipes that can be extended everywhere, and the Cisco is the pipe master.

(Wouahou pipe master, think I have to go to bed right now ...)
Neogeo147Author Commented:
How do you trunk them, I'm using the Web Interface to configure it, any ideas?

When I first boot it up it I used the CLI and it says Inbound IP address: so I gave it
default gateway: (thats the way it was setup on the previous cisco switch 3500)

then once that is set I can use the web login

So once in the web interface, it has a vlan section:

It shows VLAN#1 / 1-48 port members, stgid 1, routing false, iPaddress

So it will allow me to insert another VLAN in there, is this where I add the VLAN 162 and what would be the IP address, Then what ports do I select all but port 1?

Then how do I trunk and what do I trunk?? I see a section in there that says MLT/LACP and has Multilink Trunks, it shows Trunk#1 and portmembers, here is where I can select Port 1 vlanid 1 (which is the am I doing this correctly?
I'm very scared when you say "What ports do I select all but port 1" !
It's been three times I'm explaining you that your uplink port must be trunked and configured with ALL the VLANs that your switch will need.

Erase your MLT config.
No ip address for other VLAN than your Management ( is ok)

For a "Printer" and "Users" switch for example, in command line :
If you have a stack, replace the following port number by Unit/Port number: 1/1, 2/1 …

Command line:
> enable
# config
(config) # vlan port 1 tagging enable
(config) # vlan members remove 1 ALL
(config) # vlan members add 1 1
(config) # vlan create 160 name "Users" type port
(config) # vlan members add 160 1-23
(config) # vlan create 162 name "Printers" type port
(config) # vlan members add 162 1,24-48
(config) # vlan mgmt 1
Neogeo147Author Commented:
Its hard to follow when you don't know what tagging and things are, so maybe just a better breakdown on those configs would help someone follow it eaiser..

Thanks for all your help though, its working

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now