• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

Configuration HP Procurve switch 2910

Hi


3Com layer3 switch already installed and i want to configure hp procurve 2910 with 3com. before configuration i want to verify configuration.
could you please suggest me am i right or wrong ? becuase i will live configuration at client end  that's why i'm asking and sharing my pre-configuation plan.

Please find attached 3 Com switch configuation and HP Procurve configuration.
core.txt
ProCurve-Switch-2910.docx
0
lahoria79
Asked:
lahoria79
  • 5
  • 5
4 Solutions
 
jburgaardCommented:
The way I would do this is on the L2-sw is more simple.
You already have set up IP-addesses to vlans on your L3-sw and also setup dgw., so with dgw on clients equal  to IP of vlan and same netmask, clients can communicate both within vlan, between vlans and via dgw of L3-sw hopefully to internet.
To make the 2910 able to communicate it only needs one IP in one vlan and a L2-default-gateway, just like a PC.

conf term
IP DEFAULT-GATEWAY  10.1.10.1
vlan 1
IP ADDRESS 10.1.10.2  255.255.255.0
exit
exit
wr mem

HTH
0
 
lahoria79Author Commented:
achually, we need maximum 5 vlans more that's why i have to configure more vlans could you please guide me regarding this.
0
 
lahoria79Author Commented:
could you please tell me intervlan routing command ...? i have already configured "ip routing " command. but vlan's can not communite with core switch and each other.
0
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

 
jburgaardCommented:
To be clear, I assume on L2 switch:
NO IP ROUTING

on L3-switch: all vlans present with IP asigned
IP ROUTING (making inter-vlan routing happen)

on link between L3 and L2
L3-side: port trunk permit vlan all
L2-side the port should be tagged on all relevant vlans , perhaps Untagged in vlan 1

HTH
0
 
jburgaardCommented:
Could you please forward output from the CLI-command SHOW RUNNING  on 2910.

Also tell witch switchport  on 3com is connected to witch switchport on HP.

Where is a PC connected? with IP=?,netmask=? and dgw=? what do you try to ping? and what do you get??

From here we have common ground and can make some more tests and eventually make changes.
0
 
lahoria79Author Commented:
Dear expert,

Client requirement is to increase vlan ports which would be same with 3COM Core Switches.
HP Procurve 2910 perform just like layer 2 switch and vlans must b configure without ip address and these vlan just a member of Core Switches vlans.
i have to configure is as following:

Vlan 1 (Ports 21-24 tagged)
Vlan 20 (Ports 1-5 tagged, Port 16 untagged)
Vlan 21 (Ports 6-9 tagged, Port 17 untagged)
Vlan 22 (Ports 10-12 tagged, Port 18 untagged)
Vlan 23 (Ports 13-15 tagged, Port 19 untagged)

These Vlan ports must be trunk ports because all access switch will connect with this switch.  and all vlan must be communicate with each other. Please help me.
0
 
jburgaardCommented:
This is what you ask for, but I am not sure this is what you want.

conf term
vlan 1
tag 21-24
exit

vlan 20
name Admin-20
untag 16
tag 1-5
exit

vlan 21
name Mgmt_dept_21
untag 17
tag 6-9
exit

vlan 22
name Mgmt_Lab_22
untag 18
tag 10-12
exit

vlan 23
name Btad_lab_23
untag 19
tag 13-15
exit

exit
write mem

Witch switchport  on 3com is connected to witch switchport on HP?
This port should have all vlans
0
 
lahoria79Author Commented:
vlan1 directly connected from hp vlan1 and management ip is 10.1.10.1.
0
 
lahoria79Author Commented:
Dear Experts,
 
3Com layer3 switch already installed and i want to configure hp procurve 2910 with 3com.
 
Client requirement is to increase vlan ports which would be same with 3COM Core Switches.
HP Procurve 2910 perform just like layer 2 switch and vlans must b configure without ip address and these vlan just a member of Core Switches vlans.
 
Basic Configurations are:

Vlan 1 (Ports 21-24 tagged)
Vlan 20 (Ports 1-5 tagged, Port 16 untagged)
Vlan 21 (Ports 6-9 tagged, Port 17 untagged)
Vlan 22 (Ports 10-12 tagged, Port 18 untagged)
Vlan 23 (Ports 13-15 tagged, Port 19 untagged)
-------------------------------------------------------------------------------
ProCurve Switch 2910-24G# conf t
ProCurve Switch 2910-24G(config)# vlan 20
ProCurve Switch 2910-24G(vlan-20)# name Admin-20
ProCurve Switch 2910-24G(vlan-20)# tagged 1-5
ProCurve Switch 2910-24G(vlan-20)# untagged  16-17
ProCurve Switch 2910-24G(vlan-20)# exit

ve Switch 2910-24G# conf t
ProCurve Switch 2910-24G(config)# vlan 21
ProCurve Switch 2910-24G(vlan-21)# name Mgmt_dept_21
ProCurve Switch 2910-24G(vlan-21)# tagged 6-9
ProCurve Switch 2910-24G(vlan-21)# untagged  16-17
ProCurve Switch 2910-24G(vlan-21)# exit

ProCurve Switch 2910-24G# conf t
ProCurve Switch 2910-24G(config)# vlan 22
ProCurve Switch 2910-24G(vlan-22)# name Mgmt_Lab_22
ProCurve Switch 2910-24G(vlan-22)# tagged 10-12
ProCurve Switch 2910-24G(vlan-22)# untagged  16-17
ProCurve Switch 2910-24G(vlan-22)# exit


ProCurve Switch 2910-24G# conf t
ProCurve Switch 2910-24G(config)# vlan 23
ProCurve Switch 2910-24G(vlan-23)# name Btad_lab_23
ProCurve Switch 2910-24G(vlan-23)# untagged 13-15
ProCurve Switch 2910-24G(vlan-23)# untagged  16-17
ProCurve Switch 2910-24G(vlan-23)# exit

ProCurve Switch 2910-24G# conf t
ProCurve Switch 2910-24G(config)# vlan 1
 Porcurve Switch 2019-24 (vlan-1)# ip address 10.0.20.2 255.255.255.0
ProCurve Switch 2910-24G(vlan-1)# tagged 21-24
ProCurve Switch 2910-24G(vlan-1)# untagged  16-17
ProCurve Switch 2910-24G(vlan-1)# exit
------------------------------------------------------------------------------------------------------
 
These Vlan ports must be trunk ports because all access switch will connect with this switch.  and all vlan must be communicate with each other. Please help me.
 
it's my exactly requirement ... got my point ?
0
 
jburgaardCommented:
The port connecting to 3com should be tagged in all vlans.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now