LISTSERV - HP3000-L Archives

HP3000-L Archives

August 2012, Week 4

HP3000-L@RAVEN.UTC.EDU

	LISTSERV Archives
	HP3000-L Home
	HP3000-L August 2012, Week 4

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	Re: Configuration of Class C Subnet with 10. Prefix
From:	Mark Ranft <[log in to unmask]>
Reply To:	Mark Ranft <[log in to unmask]>
Date:	Thu, 23 Aug 2012 17:06:03 -0500
Content-Type:	text/plain
Parts/Attachments:	text/plain (33 lines)

The 10.xx.yy.zz address you are using can be sliced up into one class A or a bunch of class B's or a whole lot of Class C addresses.  The way this is done is by setting a subnet mask.  

For example....
10.1.2.2 could be the HP3000.  
With a Class C subnet mask of 255.255.255.0 all the network devices with 10.1.2.x (where x = 1 to 255) would be on the same subnet.  A total of 255 devices can be on class C subnet.
With a Class B subnet mask of 255.255.0.0 all the network devices with 10.1.x.x (where both x's = 1 to 255) would be on the same subnet.  That is 255 times 255 devices.
A Class A subnet mask would be 255.0.0.0.  

Assuming a Class C subnet, if the HP3000 on 10.1.2.2 needs to talk to a computer on another network (or subnet) then a default gateway would be configured.  A gateway must be in the same subnet as the HP3000 (or it couldn't reach it.)  
An example gateway in this scenario might be  10.1.2.200

I would suggest you ask your network expert what the "subnet mask" and "gateway" should be for your HP3000.  If you need further help, the list is here.


Mark Ranft
Pro 3K

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Mark Sprowls
Sent: Thursday, August 23, 2012 4:20 PM
To: [log in to unmask]
Subject: [HP3000-L] Configuration of Class C Subnet with 10. Prefix

When we moved our datacenter a few years ago, servers at that location were put into a class C subnet that starts with "10.", and our A-class seemed to work fine.  Now it needs to access a mail server in a different "10." subnet, but we are having difficulties.  It appears that "10." is or at some time was intended for class A subnets, and NMMGR forces the server's IP address to class A by putting the A in front of the IP address and moving the space between the first two numbers.  The result is that this server thinks the other "10." server is on the same subnet, and broadcasts locally instead of using the default gateway.  Is there some way in NMMGR to force the address to be class C?  Any other ideas?  I tried creating a static route to the other subnet, but MPE doesn't seem to even want to route.  

We are running version C.75.04.  I don't claim to be a networking expert, so please excuse any inconsistencies.  Any help would be much appreciated!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2

RAVEN.UTC.EDU