New switch Trunking

[jwc1972]

Hello

We have an 2910Al Switch, if we add another HP 2910 Switch Do I mirror the same config as switch 1, Could I add Trunk Port 1 & 2 then tag the traffic on both switches ? or do i buy a Module to connect both switches e.i Port 48

Switch 1

vlan 1
   name "DEFAULT_VLAN"
   untagged 1-40
   ip address dhcp-bootp
   no untagged 40-48
   exit

vlan 200
name "EASYNET"
untagged 40
no ip address
exit
vlan 201
   name "ADSL1"
   untagged 41 
   no ip address
   exit
vlan 202
   name "ADSL2"
   untagged 43 
      no ip address
   exit

[showneek]

Hi,

you can do that. All of its ports are 1Gbs so it doesn't matter which ports you want to use to make interconnection. The last four ports are dual personality copper or optics mixed. You have to use module/transceiver only if you want to connect these switches through fibre optics.... or if you want more throughput between switches you can create trunk (link aggregation) on front ports or buy 10Gb module in the slot on the back side.

Regards

Jan

[peyushzach]

YOu can either use module or Gig ports, Mirror the same config and tagg them all to the trunk you are creating . I recomend if its just 2 swicthes create trunk group (trk1) with the interface you wanted in it and tagg the VLANs into trunk.
Thanks

[jwc1972]

Hello

About the late reponse I have been away. Doubling checking somethime On Switch A I want to put all the client machine could i say Vlan 1

Name default vlan

Untagged 1-45

ip address dchp-bootp

tagged trk 1

exit

then on switch B leavbe as servers and adsl config

vlan 1
   name "DEFAULT_VLAN"
   untagged 1-34,36-39,45-47,Trk1
   ip address dhcp-bootp
   no untagged 35,40-41,43-44,Trk2
   exit
vlan 201
   name "ADSL1"
   untagged 41
   tagged Trk2
   no ip address
   exit
vlan 202
   name "ADSL2"
   untagged 43
   tagged Trk2
   no ip address
   exit
vlan 300
   name "supplier"
   untagged 35
   tagged Trk2
   no ip address
   exit

Then Tagged the traffic on Port 48 Trunk 1, So the client use swicth A and the server use switch B, At the monent I have a netgear unmagged connect to port 2 on the HP 2910 switch to pass traffic

[jwc1972]

Morning

I have insatlled a new HP 2910 Switch to replace an old netgear with the following config. A few user have compliant the network has become slow ca n i test for that? Plus on the Firbe link between the two switchs do i need to tag trunk 1 & 2 or just tag trunk 1?

Switch A

module 1 type J9147A
interface 24
   speed-duplex 100-half
exit
interface 42
   name "WAN "
exit
interface 48
   name "Fibre"
exit
trunk 42 Trk2 Trunk
trunk 48 Trk1 Trunk
ip default-gateway 192.168.1.3
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-34,36-39,44-47,Trk1
   ip address dhcp-bootp
   no untagged 35,40-41,43,Trk2
   exit
vlan 201
   name "ADSL1"
   untagged 41
   tagged Trk2
   no ip address
   exit
vlan 202
   name "ADSL2"
   untagged 43
   tagged Trk2
   no ip address
   exit
vlan 300
   name "ISP"
   untagged 35
   tagged Trk2
   no ip address
   exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
snmp-server community "public" unrestricted
snmp-server location "Masta Office"
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4

On Switch B

module 1 type J9147A
trunk 48 Trk1 Trunk
ip default-gateway 192.168.1.3
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-47,Trk1
   ip address dhcp-bootp
   exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
snmp-server community "public" unrestricted
snmp-server location "Masta Warehouse"
spanning-tree
spanning-tree Trk1 priority 4
no autorun
password manager
password operator