Hi Radius help,

I would suggest you start by reading the fine manual… then review the technical configuration guides. When that’s all done you can review the posts on the discussion forums.

Good Luck!

since version 6.0.0.5 diag 6.0.0.6 I not enter x.x.x.0 for my problem

Hi Simonelli,

I would guess that it’s a bug in the software… it’s very unusual to have a .0 address on anything. I actually know of a number of devices that choke when you try to use a last octet of 127 (example; 10.1.0.127).

I just tested it myself and even with a valid network mask of say 255.255.240.0 (/20) I was unable to assign an IP address of 10.1.17.0 (network comprised of 10.1.16.0 – 10.1.31.255).

I would guess that you’ll probably just need to avoid utilizing the .0 address for any of your switch interfaces. You could certainly report the problem to Avaya but I don’t they’ll have any quick fix for you.

Good Luck!

Since update 6.2.1.003, I have a big problem any ip address finish by 0 example 10.60.x.0 the message is “ERROR : Reserved IP address cannot set as Switch IP address” I erase config and retest same problem

have you got one solution

many thanks

Don’t know if the 5500 will get vrf functionality. But I know that the 5500 and Routing needs some work being addressed. Avaya is aware of it and putting many resources on it.

Still troubleshooting is childish on a 5×00 compaired to a 8600. So it needs some more time I guess…

For as it comes down to routing, late 5.1.x code is pretty good. But as it is not really supported anymore, you should take care when you install this device a larger environment.

Michael McNamara:

I’m not sure the ERS 5000 series will ever get VRF capabilities… have you heard different?
Thanks for the post!

I once read this in the Nortel ERS 5000 FAQ:

Does the ERS 5000 Series support advanced Layer 3 Routing features such as IPv6 Routing and Virtual Routing & Forwarding..?
An IPv6 Management capability was added in v6.0, and the ERS 5600 Hardware is IPv6 ready. However, neither IPv6 Routing nor VRF capabilities are currently supported on the ERS 5000 Series. The development roadmap for the ERS 5000 Series is currently being updated and both of these features are under consideration.

So I remembered it as being under consideration :-), never heard anything more of it though. It would allow us to extend our different central routing domains in a very elegant way to our remote sites.

Hi Bylie,

We’re actually using the ERS 5530 switch as a replacement for the ERS 1648 switch acting as a L3 router for a large number of our remote offices where we have between 100-500 devices. The ERS 5530 acts as our core/distribution switch connecting the WAN (dark fiber, metro Ethernet) with the building LAN made up of edge/closet switches/stacks. We utilize the Advanced Routing License to provide OSPF routing on the platform. I will tell you that we are still running 5.1.x for the most part and haven’t upgraded any of our L3 deployments to 6.2.x.

I’m not sure the ERS 5000 series will ever get VRF capabilities… have you heard different?

Thanks for the post!

Is it just me or are they really having a hard time getting the 5000 series to behave nicely when using them for routing? Mind you, we only have a couple of 5510’s which are only doing standard forwarding tasks, nothing fancy. They haven’t let us down in that department but reading about all the issues in the release notes one might start thinking twice before using these as L3 components in their network.

I’m also still waiting for VRF capabilities on the 5000 series which would make them more suitable as backbone switch/router for our remote sites.