NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
setting up two switches on same subnet
have servers with two 10g nic, have two xs716e switches
since this will be an intranet, set both switched to not be dhcp, and will give servers static IP addresses
when I try to Apply the "default gateway" as blank, I get error "IP address: of this switch must be in the same subnet as the gateway."
(making one of the switches' ip addr .240, so the other stays default .239 and both accessible via web browser)
should I make both switches default gateway the same? something like 192.168.0.254
or should they each have their own default gateway? (and unsure if stupid question, but should the gateway be the switches' own ip address?)
4 Replies
Whatever an Intranet is for you - even an iSCSI storage network needs the ability to manage or monitor switches and SAN/NAS, so how else you want to do the job without some router/firewall. In absence, it's a good policy to reserve either the highest or the lowest IP from the IPv4 subnet for a gateway at lest, and configure the address as a default gateway.
Last but not least, I'm not sure how smart it is to use one of these well-known often default LAN IP subnets like 192.168.0.0/24 or 192.168.1.0/24 for such an "Intranet".
Needless to say, a "network" (more appropriately a "broadcast domain") and IPv4 subnet can be created using one or more switches, multiple broadcast domains and IP subnets can be configured on one or multiple swiches using VLANs.
using Microsoft S2D, so actually better to do two different subnets
because setup as one subnet, was getting failoverClustering events about partitioned network when setup as same /23; i.e. both switches set to subnet mask 255.255.254.0 and default gateway 192.168.0.1, where I put the second switch with default 192.168.1.239, and all it's attached nic as 192.168.1.x--could have gone for /24; guessing you're saying creating a vlan was the way to go, but regardless, s2d doesn't want same subnet on the cluster only networks
so moot question now; the first switch setup dhcp disable, left self ip addr as default 192.168.0.139, subnet mask 255.255.255.0, and default gateway 192.168.0.1, and the second switch setup basically the same, but 1.239 self ip, and 1.1 default gateway; no vlan setup (and no failoverClustering events)
my next problem is how to get into knowing port flow control (vs global pause) and QoS, is it RDMA capable; I think I bought a cheap switch, doesn't have much in the way of settings; will have to do testing between servers to confirm traffic is what I want (not really easy conversation in this community; would be more windows powershell community question)
and using well know local/intranet subnet not an issue for me (no one can access it, so not like they can hack it)
and more importantly, thank you for replying (always discouraging when you have a question that no one is willing to even touch!)
hunter3740 wrote:using Microsoft S2D, so actually better to do two different subnets
Ways beyond of the Netgear community scope however I'd say.
Show us the layout intended. Indeed there are different subnets required - but i would keep the network management VLAN connected and accessibe direct. This is what the primay IP config is for.
The subnets (VLAN if you want to share the bandwidth) you run for connecting the vNIC for host management (RDP, AD and so on - GbE is sufficient, could be alos the switch management VLAN), plus two vNIC connctions for Storage (S2D, SMB, Live-Migration - I guess this is where you intend to use these two 10G switches).
Last but not least, stay far away using these common IP subnets like 192.168.0.x/24 or 192.168.1.x/24 or 10.0.0.x/24 as these are often default on many simple routers. Choose something meaningful. it's not about hacking or security - it's about logic...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
