255.255.254.0 subnet mask vs 255.255.255.0 subnet mask -- MIDRANGE-L

Subject: 255.255.254.0 subnet mask vs 255.255.255.0 subnet mask
From: Rob Berendt <rob@xxxxxxxxx>
Date: Thu, 3 Jan 2019 14:37:38 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Network guy had me set up our DMZ based LPARs with a 255.255.254.0 mask.
Now he wants me to change it to a 255.255.255.0 subnet mask.
I told him that it would have to wait until our next scheduled downtime.
Which is in March.

I am trying to figure out why. I can't get an explanation from him that I
can understand. Knowing why might help me to determine what I should test
to see what it broke. For example, since he discovered this by analyzing
traffic I am assuming that something is using this.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: 255.255.254.0 subnet mask vs 255.255.255.0 subnet mask , Clay Carley
Re: 255.255.254.0 subnet mask vs 255.255.255.0 subnet mask , David Gibbs
Re: 255.255.254.0 subnet mask vs 255.255.255.0 subnet mask , DrFranken

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.