Network design
Hi Experts
have a brand new firewall and six 24 ports L3 capable HP switches ; existing network is small (<150 wks) ; currently running over L2 switches and little hubs !
Trying to get some good benefits from all these new equipments . so , my thought is like this :
Let's say we will have 2 VLANs : VLAN 1 and VLAN2
VLAN 1 : 10.10.1.0/24
VLAN 2: 10.10.2.0/24
Intra-VLAN routing should be enabled so that devices can talk to each other.
so , as far as I know , I have to create VLANs on the core switch ; dedicate interfaces to them and assign IP addresses on respective VLAN :
e.g :
VLAN 1
Interface GigaEthernet 0/1 / IP address :10.0.1.1/24
VLAN 2
Interface GigaEthernet 0/2 / IP address :10.0.2.1/24
let's imagine IP routing is enabled on this switch . so these 2 VLANs can talk to each other . also ; probably I can define another interface and set static routs to send Internet traffic toward edge firewall.
Let's also imagine 5 other switches are connected (using 1 GB connections) and ports are
assigned to different VLANs, I think one GB trunking port should be considered on each of these five switches.
My dummy questions for now :
How physically I connect remaining 5 switches to core switch ? should I expect 5 trunk connections to core switch ? how interfaces on core switch will talk to trunk links ?
have a brand new firewall and six 24 ports L3 capable HP switches ; existing network is small (<150 wks) ; currently running over L2 switches and little hubs !
Trying to get some good benefits from all these new equipments . so , my thought is like this :
Let's say we will have 2 VLANs : VLAN 1 and VLAN2
VLAN 1 : 10.10.1.0/24
VLAN 2: 10.10.2.0/24
Intra-VLAN routing should be enabled so that devices can talk to each other.
so , as far as I know , I have to create VLANs on the core switch ; dedicate interfaces to them and assign IP addresses on respective VLAN :
e.g :
VLAN 1
Interface GigaEthernet 0/1 / IP address :10.0.1.1/24
VLAN 2
Interface GigaEthernet 0/2 / IP address :10.0.2.1/24
let's imagine IP routing is enabled on this switch . so these 2 VLANs can talk to each other . also ; probably I can define another interface and set static routs to send Internet traffic toward edge firewall.
Let's also imagine 5 other switches are connected (using 1 GB connections) and ports are
assigned to different VLANs, I think one GB trunking port should be considered on each of these five switches.
My dummy questions for now :
How physically I connect remaining 5 switches to core switch ? should I expect 5 trunk connections to core switch ? how interfaces on core switch will talk to trunk links ?
best way would be to connect 5 switches with trunks but also us lacp to aggregate (group) ports - use 2 for each switch - you will have to use 10 ports on main switch but it is well worth it.
1 if one link fails you always have second one to given port
2 you gaining internal bandwidth - 2Gbps from each switch to core switch - server wise it does speed up everything. - end devices can pull much more data on shorter periods of time (shared folders or networked drives)
JAN MA CCNA
1 if one link fails you always have second one to given port
2 you gaining internal bandwidth - 2Gbps from each switch to core switch - server wise it does speed up everything. - end devices can pull much more data on shorter periods of time (shared folders or networked drives)
JAN MA CCNA
ASKER
yeah , but how we physically connect them to core ?
star connection - 2 cables from each switch to core
ASKER
1- okay so .. let say we connect two ports from a given switch to core ; what specific configuration on the core switch is needed ? where I set the IPs ? and on what interface ?
2- what happens to rest of unused ports on core switch ? are they wasted ?
2- what happens to rest of unused ports on core switch ? are they wasted ?
what type of hp switches do you have?
@1 you set up ips and subnetmasks on ethercahnnels groups of ports (lacp agregation) - not on physical interface ports
you also enable trunking on etherchannels groups.
@2 core server connects to your firewall and if possible put all your servers on it (if cpu of switch is powerful enough - you should be able to monitor it)
@1 you set up ips and subnetmasks on ethercahnnels groups of ports (lacp agregation) - not on physical interface ports
you also enable trunking on etherchannels groups.
@2 core server connects to your firewall and if possible put all your servers on it (if cpu of switch is powerful enough - you should be able to monitor it)
ASKER
HP 3800 switches .
1-I still don't get it . lets say we have two VLANs ; 10.10.1.0 and 10.10.2.0 ;
we also have two cables (in a group coming from each access switch to core)
So I have 5 pairs coming to core switch with trunk enabled , getting 10 ports in total .
so that I will have 5 grouped interfaces on my switch . Where do I set up IP addresses of two VLANs to become the default gateway ?
2- so can I have my serevrs connected to let's say VLAN 3 on core switch talking to rest of VLANs ?
1-I still don't get it . lets say we have two VLANs ; 10.10.1.0 and 10.10.2.0 ;
we also have two cables (in a group coming from each access switch to core)
So I have 5 pairs coming to core switch with trunk enabled , getting 10 ports in total .
so that I will have 5 grouped interfaces on my switch . Where do I set up IP addresses of two VLANs to become the default gateway ?
2- so can I have my serevrs connected to let's say VLAN 3 on core switch talking to rest of VLANs ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Dot1q Trunk will negotiate connection between switches.