1751691 Members
4853 Online
108781 Solutions
New Discussion

Re: stack 4500G

 
Michael15
New Member

stack 4500G

Hello, i'm Michael15 a student from France



I am in a company internship and I am configuring 3com switch 4500G.



The switch OS is the s03q05_01_03s56.app



My problem concern the stackable option who's not recognized :



I'm looking the Conf_guide that explain different stack options as stack ip-pool , stack role master, stack port ...



without telling any pre-requits



in the CLI there isn't any stack command possible it is equal with device manager no stack option ! !



examples :



stack ip-pool 192.168.1.1 24



^ unrecognized command



stack ?



^ unrecognized command



?



all commands display but no stack



 



So I was thinking it's possible to configure it.



Thanks to answer me.



Michael15



2 REPLIES 2
Fred_Mancen_1
Super Advisor

Re: stack 4500G

Hi Michael. The Device Manager does not support the 4500G stacking feature; you can manage the stack through the web console only.



The config guide is poor when explaining the stack feature implementation, and you need to perform some actions beyond the commands you already have entered.



The 4500G stack is a "cluster like" stack, with one master switch and slave switches. Through the master you will have access to the others, using the command "stack switch-id to <id_of_the_slave>". The stack does not work as a single entity, as in the 5500G-EI and 4800G stack feature.



The additional actions are:



In the VLAN interface 1 on the master switch, assign an IP address of any class you want. The slave switches will obtain IP addresses by DHCP from the master, after you finish the settings. You can define the IP addresses in the slaves if you prefer.



In the stack ports, you need to setup the ports as trunk ports, with all VLANs allowed, and using the PVID of a VLAN interface that you are using in the local network. I suggest to use different VLANs than the VLAN 1. Use RSTP in all ports.



Note that the slave switches does not maintain always the same ID, when rebooting the slave switches or all the stack, the first slave switch that came up will receive the first free ID of the stack, and so on.



The advantages in this feature is the faster convergence and the bandwidth in the switches connections (10G), but even simple features as distributed link-aggregation does not work in this kind of stack.



HTH.



Regards,
Fred Mancen
Michael15
New Member

Re: stack 4500G

Hello Fred_Mancen,



thank you for having responded this will help me.



So I'll see what can I do with cluster as you advised me.



I'll ask if  still need advice.



:)



Michael