Network configuration means providing a clear network device naming and unique identity within the corporate network. You need to design the network configuration standard within your global organization for an easy identification and management. Network configuration can include the unique identity such as:
1. Naming network components and objects
Network configuration by giving universal naming standard within your corporation is required for all relevant network components and objects. It is a requirement that network entities such as file servers, shared printers, routers, switches, users, groups and email messaging systems have a consistent and unique global naming standard. This is essential to ensure that your corporate resources can be easily identified and located throughout the global network.
If your corporation has many business units globally, a unique Company ID code is required to provide a global naming prefix. Each business unit ID (Company ID) shall be unique.
Back to our previous computer network scenario, the corporate has 3 business units, Guinea Gold; US Gold and Brazil Gold, the following are good examples of company prefix:
GUI identifies Guinea USA identifies US Gold BRA identifies Brazil GoldFor company with multiple large business subsidiaries, a company prefix followed by a unique subsidiary prefix can be used to identify the subsidiary, for example:
GUISML identifies Guinea Smelters Ltd. GUIFRG identifies Guinea Freight.This will form the basis of the name prefix used to universally define various network components and objects throughout the corporate directory and network.
The computer name of each server shall be comprised of the Company ID, the site ID (if required), the server role and a unique sequence number (if required):
<CompanyID><Site><Role><Sequence number>
The role of the server maybe defined as:
| Role | Server (Primary) Function |
| DC | Domain controller |
| SQL | SQL Database Server |
| MAIL or EXCH | Mail or Exchange server |
| FS | File and Print server |
The <Site> defines the location of the device. This may be required to assist with the network support and management of the network. If a server is functioning under multiple roles, the primary role must be defined in the server name. Any Domain Controllers must be identified using the DC role-prefix.
For example:
GUISMLDC01 (Guinea Smelter Domain Controller #01)
The other network configuration regarding naming is Network Device Naming such as Routers and Switches; this is required to provide consistent identification throughout the corporate group.
Switch naming standard – network configuration
The syntax used is as follows:
< CompanyID>-< Location>-<Device-Type><Sequence Number>
The Location should be a maximum of 8 characters (guideline only) and used to define a unique and descriptive locality. This is to be based on <town/street:building number:floor level>.
S is the device-type used to indicate a LAN Switch CS is the device-type used to indicate a core LAN Switch.For example,
The 2nd core LAN switch located at Guinea Smelter on the 1st floor (level 1) should be called.
GUISML-L1-CS2
Router naming standard – network configuration
The hostname of each router must be comprised of the Company ID, the location, router type and a unique sequence number (if required):
< CompanyID>- Location>-<Device-Type><SequenceNumber >
R is used to indicate a device-type of Router.
CR is used to indicate a device-type of a core Router. This router interconnects into the corporate Wide Area Network core (Interlink).
2. Network configuration – IP address
If a device wants to communicate using TCP/IP, it needs an IP address. Further article will discuss more detail about this IP addressing. Back to the previous scenario about connecting the network, let’s have a look a simple core network diagram below that connect the HR and Mining buildings.
See that the network configuration in Mining Office (MO) has its own file server (GUISML-MO-FS01) because this server will only be accessed by Geologist users in the MO. Placing often accessed resources such as servers in close proximity to clients will improve network response times.
Network Configuration Diagram
Deploying IP addresses regarding Network configuration for Servers and switches, they must have fix IP addresses. What you need to have is a proper documentation – register of the Fix IP addresses something like the table below before applying to the devices.
Guinea Smelter – IP Addresses Register
| IP Address | Device ID | Description |
| 192.168.100.254 | GUISML-HR-R01 | E0 Core Router HR building to WAN Connection |
| 192.168.100.253 | GUISML-HR-DC01 | Domain controller #1 at HR building |
| 192.168.100.252 | GUISML-HR-DC02 | Domain controller #2 at HR building |
| 192.168.100.251 | GUISML-HR-FS03 | File server #3 at HR building |
| 192.168.100.250 | GUISML-HR-Cs1 | Core switch #1 at HR building |
| ….. | ||
| ….. | ||
| 192.168.100.1 to
192.168.100.220 |
DHCP IP pool | Reserve IP for DHCP IP address pool |
Starting the deployment of network configuration will be easier if you have everything in a well documentation with standard network configuration across the global business. This will help assessing the risk security of the networking environment.
Now you can start deploy network configuration by setting-up the devices names and IP addressing with well naming standard.
By Ki Grinsing
See also:
- WAN Technologies – types of WAN services
- LAN topologies – the basic concept
- Spanning tree protocol – high performance LAN
- VLAN tutorial – the basic concept of VLAN
- Business firewall – endpoint protection
Recent Comments