Log In. Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community.

Author:Dokasa Tole
Language:English (Spanish)
Published (Last):27 March 2007
PDF File Size:19.63 Mb
ePub File Size:4.95 Mb
Price:Free* [*Free Regsitration Required]

June 04, , PM. Home Help Search Login Register. Welcome, Guest. Please login or register. Registration is free. Did you miss your activation email? Member Posts: But if I take the Devices and plug them into the Core Switch which is stacked , I won't respond to any of my ping commands.

I instead had to build a Cluster when I used 2 Switches to function as a Core. So to fix this issue, I had to break the Stack. I instead had the Core Switch to be a Standalone Switch and not to be stacked. Any feedback will be highly appreciated. Johan Witters Sr. We work with the ERS quite a lot, also as "core" systems with our smaller customers. Until now we have not yet had this kind of issues with the series. Unless there is a software issue somewhere in the release you're running, it should not make any difference whether you use individual units, or a stack.

The problem sounds like the stack is not operating in L3 mode: the command "ip routing" has not been executed. In that case it will not be possible to communicate between clients in different vlans, and you will only be able to ping the stack on the address configured for the vlan you attached to with your client. Any chance to post the configuration? Hi Johan, Have you actually tested with a Core as being a Stack? I definitely had "ip routing" enabled.

I know because I had 2 Laptops on different Subnets terminating on 2 different Access Switches and I could ping the 2 Laptops just fine. However, when I put the laptops on the Core, I cannot ping the Laptops. And I was consoled into the Core and yet I couldn't even ping it's own interface configured on it. So strange. The minute I broke the Stack, it worked. That sounds more like something in the port settings on the stack, but then again it should persist when breaking the stack Routing seems fine as you are able to ping from the access switch.

Which agent release are the switches running on? I believe v5. I tried to upgrade the Switches but I was having tons of issues. It wouldn't upgrade. Always giving me an "invalid image" or "not reading the image from USB" and so on.

I wasn't so sure if I had to upgrade the Agent Software image first before the Diagnostic and Boot image. But that's a different story all together. Quote from: eosuorah on November 26, , PM. We've been helping network engineers, system administrators and technology professionals since June If you've found this site useful or helpful, please help me spread the word.

Link to us in your blog or homepage - Thanks! SMF 2. Expo by DzinerStudio.


Need Help?

Your cart is empty, why not try searching for products? The product specifications provided below are only related to the types of upgrades and accessories available for this system. This product is not for sale. It is shown here for configuration purposes only.


Avaya Switches Ethernet Routing Switch 4548gt-pwr Al4500a 14-e6

This Forum is provided solely for the use and convenience of Avaya customers and partners. No other use is permitted. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason. Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin. You expressly understand and agree that you assume all risks associated with use or reliance on this content.


Avaya 4548GT-PWR Ethernet Routing Switch Managed 48-Ports PoE


Related Articles