##BAS1 (running-config)
interface Vlan10
ip address 10.2.255.252 255.255.0.0
ip helper-address 10.0.2.22
standby version 2
standby 10 ip 10.2.255.254
!
interface Vlan20
ip address 10.1.127.252 255.255.128.0
ip helper-address 10.0.2.22
standby version 2
standby 20 ip 10.1.127.254
!
interface Vlan100
ip address 10.100.127.252 255.255.128.0
ip helper-address 10.0.2.22
standby version 2
standby 100 ip 10.100.127.254
##BAS2 (running-config)
interface Vlan10
ip address 10.2.255.253 255.255.0.0
ip helper-address 10.0.2.22
standby version 2
standby 10 ip 10.2.255.254
!
interface Vlan20
ip address 10.1.127.253 255.255.128.0
ip helper-address 10.0.2.22
standby version 2
standby 20 ip 10.1.127.254
!
interface Vlan100
ip address 10.100.127.253 255.255.128.0
ip helper-address 10.0.2.22
standby version 2
standby 100 ip 10.100.127.254
Both multilayer switch configurations listed above are HSRP group members for three separate HSRP groups. The group numbers refer to the VLAN that the HSRP group is associated with. The last three IP addresses of their respective networks have been used for the HSRP virtual IP address as well as the VLAN interface address. The same configuration above is used on Building B multilayer switches, however alternative IP addressing is used as our DHCP pools have been segregated.
The next step in our project in order to get full connectivity is to configure two routers, connected to the two central multilayer switches in the following configuration:
My current issue with this configuration is finding a solution to allow load balancing with exiting to the "ISP". In our project, ISP would be the main campus network where we would get internet from, however BGP could be configured in order to represent what an ISP configure could be like.
*Note: This configuration may change in order to better represent what we want to do for the final design.
