Using ADAC on ERS stack with IP routing enabled

[Stefan Herbst]

Hello,

I am wondering if ADAC can be utilized on a ERS4548 stack functioning as a router. As the voice VLAN is routed on this stack their is no "uplink" where the voice VLAN is tagged.

Just wondering if anyone has leveraged ADAC in this type of config, or if it would even be possible.

Thanks,
Stefan

[Jon Hurtt]

Don't see any problem using ADAC and L3... but i would look into LLDP-MED, might prove to be a easier implementation.


This guide might help.

Avaya IP Telephony Deployment Technical Configuration Guide
https://support.avaya.com/css/P8/documents/100123695

[aGeftwGER]

Hi, u can post your ADAC config, maybe there is something wrong?


Hi, also poste mal die ADAC config, ich hatte mal ähnliche Probleme bei mir. Ich geh jetzt von deinem Namen davon aus, dass du aus Deutschland kommst...

[Michael McNamara]

Hi Stefan and welcome to the forums!

Your question gives me pause... and I don't believe it will work (as you've hinted to) depending on your configuration. It's similar to using the ADAC/LLDP-MED on an switch when that switch is also a distribution switch with uplinks/downlinks (this specific issue was just addressed in the latest release of software - see http://blog.michaelfmcnamara.com/2011/09/avaya-ethernet-routing-switches-and-non-adac-vlans/).

Are you trying to route the VOICE VLAN on the ERS5520 itself? Or will you bridge it to your core and route it there?

If you are bridging the VOICE VLAN while routing the DATA VLAN then it should work fine. If you are trying to route the VOICE VLAN on the ERS 5520 then I would probably need to consult with Avaya. The issue is that you cannot create the VOICE VLAN, the switch creates it automagically when you issue the command "adac voice vlan 50". So can you then create a IP interface and enable routing on that VLAN? I'm not sure, never done it myself... you'd need to test. Also it might appear to work initially but it might break if you rebooted the switch (I have ADAC/LLDP-MED do that to me dozens of times).

Shouldn't be hard to test but you should probably get some acknowledgement from Avaya that this configuration is supported.

Cheers!

[Stefan Herbst]

Hi Michael,
The scenario I was working through was to have the switch stack do routing for both data and voice networks (for a very small branch office for example). The idea being wanting to standardize on the network/telephony edge compared to large sites where these switches would bridge to the core (and ADAC works well in this case).

I did some testing on a ERS4548 running 5.3.3 and it led me to a scenario where you could get the switch to the point where this would work. However, this would not be something I would deploy due to the nuances around ADAC in this use case, not to mention if it would be supported (which my guess would be no).

Here some points I was able to clarify in my testing:
1. The VLAN you configure under ADAC cannot already exist on the switch (error will not take command).
2. You cannot create/configure an IP address for a VLAN if it does not exist.
3. You have to specify an uplink/call server port (adac enable will not work with out this parameter configured).
4. The Uplink/Call server port is automatically changed to a TagALL port config. Although this can be changed after, enable/disable of ADAC or switch reboot will force this port back to TagALL.
5. Globally enable/disable of ADAC removes the IP address configured on the VLAN.

These were the steps to end up with ERS4548 stack with IP routing enabled for voice/data networks using ADAC for detection.
1. Assume switch is pre-configured with data vlan, IP interface for data vlan and IP routing enabled. All edge ports are in data vlan as access ports.
2. Configure configure ADAC tagging mode, configure ADAC voice vlan-id
3. Configure ADAC uplink port (as their would be no bridged uplink port I sacrificed a port that would not be used).
4. Enable ADAC
5. Configure IP address/mask for voice VLAN and enable routing.
6. Enable ADAC on edge ports.

The risk to reward does not make sense in this case (in my opinion). It would be nice if ADAC was more flexible in this use case, perhaps accepting an IP address instead of an uplink port (from a logical point of view).

Thanks,
Stefan

[Michael McNamara]

Thanks for the follow-up Stefan!

I believe some of the issues you pointed out above have been resolved in 5.4 software for the ERS 4000 series.

The latest version of software available is actually 5.6 (as of this writing);
http://blog.michaelfmcnamara.com/2011/12/ethernet-routing-switch-4000-software-release-v5-6/

I would agree though, not sure if Avaya would support that configuration or that it wouldn't break down the road.

Cheers!