My supervisor instructed me to go to the server room and join a bunch of servers to the Division community so they’re accessible from workplace PCs. Within the server room we’ve got 7 servers, a few wall jacks and a few switches. I solely use one wall jack.
Very first thing I attempted was utilizing a easy D-Hyperlink DGS 105 change by connecting one in every of its ports to the wall jack and related two servers to 2 different ports. Each the servers obtained IP tackle and issues appeared to be working positive. However There are 7 servers every having at the very least 5 interfaces in order that 5 port D-Hyperlink change is just not going to suffice. In addition to, there are these shiny lovely Aruba switches (2530 and 2930F) which can be simply sitting there so I figured I’d use these. The target is so as to add my servers to the identical LAN phase because the default gateway and be capable to talk with them straight utilizing the PC’s within the workplaces.
I did the identical factor with one Aruba change. I related port 1 to the wall, and the 2 servers to ports 3 and 5 all on vlan 1 all untagged. Here’s what occurs: When IP tackle setting is ready to bootp/dhcp on vlan 1, the change SVI obtains and IP tackle however not one of the servers do. I’ve mirrored port 1 site visitors and captured DHCP frames, the broadcasts are being despatched out of port 1 into the wall however no reply or provide comes again in. Once I disable IP tackle and IP routing on the change, one of many servers is ready to receive an IP tackle however the different(s) do not. They maintain broadcasting DHCP discovers however no reply comes again. The default gateway tackle is on a special subnet from the DHCP server tackle which I noticed in DHCP ACKs so I feel the default gateway behind the wall already has dhcp-relay enabled. By the way in which, all outbound Ethernet frames of port 1 have the VLAN tag with VID = 1 however no Inbound site visitors has VLAN tags neither the DHCP replies (when it really works for one server) nor the DHCP broadcasts of different units behind the wall.
DHCP-snooping is disabled on the change.
I’ve checked the MAC tackle desk of the change and all the pieces appears to be right. There are many totally different entries for interface 1 and the right server MAC addresses for port 3 and 5.
My Query: Why is the behaviour totally different with the Aruba change? How can I simply join my servers to the identical LAN phase because the D-Hyperlink change appears to be doing? Does it have one thing to do with port safety? If that’s the case why is not the D-Hyperlink change having any points? Am I heading in the right direction? Is the fundamental setup I’m on the lookout for even doable?
Sadly I haven’t got entry to no matter is behind the wall, like DHCP server logs, as that’s managed by division IT.
output of present config:
hostname "Aruba-2930F-48G-4SFPP"
module 1 sort jl254a
mirror 1 port 2
no dhcp-relay
no ip icmp redirects
ip route 0.0.0.0 0.0.0.0 10.172.156.1 metric 250
interface 1
monitor all each mirror 1
exit
snmp-server group "public" unrestricted
vlan 1
identify "DEFAULT_VLAN"
no untagged 2
untagged 1,3-52
no ip tackle
ip helper-address 10.59.232.5
exit
vlan 2
identify "MONITOR"
untagged 2
no ip tackle
exit
vlan 1 information:
VLAN ID : 1
Identify : DEFAULT_VLAN
Standing : Port-based
Voice : No
Jumbo : No
Personal VLAN : none
Related Major VID : none
Related Secondary VIDs : none
Port Data Mode Unknown VLAN Standing
---------------- -------- ------------ ----------
1 Untagged Study Up
3 Untagged Study Up
4 Untagged Study Down
5 Untagged Study Up
6 Untagged Study Down
7 Untagged Study Down
8 Untagged Study Down
9 Untagged Study Down
10 Untagged Study Down