Description
The modules below have a fixed factory-set MAC address.

• S7-300 and S7-400 Industrial Ethernet CPs
• S7-300 and S7-400 CPUs with integrated PROFINET interface
• Network components like SCALANCE X, SCALANCE W, SCALANCE S, PN/PN coupler
• Gateways like IE/PB Link, IWLAN/PB Link and IE/AS-Interface Link
• Interface modules of ET 200M, ET 200pro and ET 200S
• ET 200eco PN

The first 3 bytes of the MAC address describe the manufacturer ID, also known as the OUI (Organizationally Unique Identifier).
Up to now these modules above have been delivered with a MAC address in which the first three bytes have always been 08-00-06.

The manufacturer ID of the MAC addresses is administered by the IEEE (Institute of Electrical and Electronics Engineers). At the link below you can see which manufacturer ID or OUI the first three bytes of a MAC address describe.

IEEE-Standards Association

SIEMENS AG uses the following manufacturer IDs or OUIs for the MAC addresses of the above-mentioned network-compatible devices.

• 08-00-06 (hex)
  SIEMENS AG
  Siemens IT Solutions and Services, SIS GO QM O
  Siemensstraße 2-4
  POB 2353 Fürth 90713
  GERMANY
• 00-0E-8C (hex)
  Siemens AG A&D ET
  Siemensstraße 10
  Regensburg 93055
  GERMANY
• 00-1B-1B (hex)
  Siemens AG
  I IA SC EWK PU1, Östliche Rheinbrückenstraße 50
  76181 Karlsruhe, Baden Württemberg
  GERMANY

Confusion may arise in the following situations:

• A network engineer uses a new module whose factory-set MAC address has the manufacturer ID 00-0E-8C or 00-1B-1B. From older modules he is used to factory-set MAC addresses having the manufacturer ID 08-00-06. Therefore he will look for a MAC address 08-00-06-xx-yy-zz which, however, he will not find.
• Spare parts scenario: A module with a factory-set MAC address of 08-00-06-xx-yy-zz is defective and has to be replaced with a new module. It might be that the factory-set MAC address of the new module has the manufacturer ID 00-0E-8C or 00-1B-1B.

Configuration Notes
With CIDR, there is no fixed assignment of an IP address to a network class and possible subnetting in other networks or supernetting of several networks in a class. There is only one network mask that splits the IP address into a network part and a host part.

The CIDR function (Classless Inter Domain Routing) thus includes subnetting and supernetting.

The following Industrial Ethernet CPs support the subnetting and supernetting functions:

• 6GK7343-1EX21-0XE0 as from FW V1.2
• 6GK7343-1EX30-0XE0
• 6GK7343-1GX21-0XE0 as from FW V1.1
• 6GK7343-1GX30-0XE0
• 6GK7343-1GX31-0XE0
• 6GK7343-1CX10-0XE0
• 6GK7343-1FX00-0XE0
• 6FL4343-1CX10-0XE0
• 6GK7443-1EX20-0XE0
• 6GK7443-1EX30-0XE0
• 6GK7443-1EX40-0XE0 as from FW V2.4
• 6GK7443-1EX41-0XE0
• 6GK7443-1GX20-0XE0
• 6GK7443-1GX30-0XE0

The following CPUs with integrated PROFINET interface support the subnetting and supernetting functions:

• IM151-8(F) PN/DP CPU
• IM154-8(F) CPU
• CPU314C-2 PN/DP
• CPU315(F)-2 PN/DP as from FW V2.3
• CPU317(F)-2 PN/DP as from FW V2.3
• CPU319(F)-3 PN/DP
• CPU412-2 PN
• CPU414(F)-3 PN/DP
• CPU416(F)-3 PN/DP
• CPU412-5H PN/DP
• CPU414-5H PN/DP
• CPU416-5H PN/DP
• CPU417-5H PN/DP
• S7-1200 CPUs as from FW V1.0

The following Industrial Ethernet PC modules support the subnetting and supernetting functions:

• CP1616 as from V2.0
• CP1604 as from V2.0
• CP1613 (A2) as from SW V7.1
• CP1623
• CP1628
• CP1612 and IE General

For the remaining Industrial Ethernet PC modules like CP1613 (A2) < SW V7.1, CP1604 V1, CP1616 V1 and CP1512 it is only possible to configure the "Subnetting" function. It is not possible to configure the "Supernetting" function for these modules in STEP 7 / NCM PC. This is prevented in STEP 7 / NCM PC by an error message (see Fig. 05).

In these modules that support the TCP/IP protocol it is possible to set both the IP address and the associated subnet mask in the hardware configuration of STEP 7. The IP address and associated subnet mask are entered in the Properties window of the CP's or CPU's Ethernet interface. After inserting the Industrial Ethernet CP or CPU with integrated PN interface in the hardware configuration, you are offered the following default settings (see Fig. 01) in the Properties window of the CP's or CPU's Ethernet interface.

• IP Address: 192.168.0.1
• Subnet mask: 255.255.255.0

Fig. 01: Properties window of a CP's Ethernet interface

If you wish to change these default settings for the IP address and subnet mask, you need information about the connection between classes of IP addresses and subnet masks. The following demonstrates the connection between classes of IP addresses and subnet masks.

Connection between class of the IP address and subnet mask
In principle there are 5 classes of IP addresses. These are the classes A to E. Each class has its own subnet mask. The connections are given in the table below.
 

Class	Class bits	IP address range	Subnet mask	Network share	Node share
A	0xxxxxxx	0.x.x.x - 127.x.x.x	255.0.0.0	1 byte	3 bytes
B	10xxxxxx	128.0.x.x - 191.255.x.x	255.255.0.0	2 bytes	2 bytes
C	110xxxxx	192.0.0.x - 223.255.255.x	255.255.255.0	3 bytes	1 byte
D	1110xxxx	224.0.0.0 - 239.255.255.255	---	Multicast addresses
E	1111xxxx	240.0.0.0 - 255.255.255.255	---	Reserved addresses (for future purposes)

Class A network
IP addresses from Class A begin with the bit sequence 0-...; for example, the IP address range lies between 0.x.x.x and 127.x.x.x.
The subnet mask identifies the range that includes the address information for identifying the subnet. In Class A networks the first byte, that is to say the first 8 bits, corresponds to the IP address of the subnet address. Thus Class A networks are defined by the following subnet mask: 255.0.0.0 = 1111 1111 0000 0000 0000 0000 0000 0000. The last three bytes (24 bits) of the IP address identify a node in this subnet.

The total number of Class A networks can be calculated as follows:

• 2^8-1-2 = 2⁷-2 = 126 networks (since the IP address always begins with the bit sequence 0-..., 0.0.0.0 and 127.0.0.0 are not permitted)

The number of computers in a Class A network can be calculated as follows:

• 2²⁴-2 = 16 777 214 computers (x.0.0.0 -> network address and x.255.255.255 -> broadcast address are not permitted)

Fig. 02: Class A network

Class B network
IP addresses from Class B begin with the bit sequence 1-0-... and the address range lies between 128.0.x.x and 191.255.x.x. In Class B networks the first two bytes, that is to say the first 16 bits correspond to the IP address of the subnet address. Thus Class B networks are defined by the following subnet mask: 255.255.0.0 = 1111 1111 1111 1111 0000 0000 0000 0000. The last two bytes (16 bits) identify a node in this subnet.

The total number of Class B networks can be calculated as follows:

• 2^16-2 = 2¹⁴ = 16384 networks (since the IP address always begins with the bit sequence 1-0...)

The number of computers in a Class B network can be calculated as follows:

• 2¹⁶-2 = 65534 computers (x.x.0.0 -> network address and x.x.255.255 -> broadcast address are not permitted)

Fig. 03: Class B network

Class C network
IP addresses from Class C begin with the bit sequence 1-1-0... and the address range lies between 192.0.0.x and 223.255.255.x. In Class C networks the first three bytes, that is to say the first 24 bits correspond to the IP address of the subnet address. Thus Class C networks are defined by the following subnet mask: 255.255.255.0 = 1111 1111 1111 1111 1111 1111 0000 0000. The last byte (8 bits) identifies a node in this subnet.

The total number of Class C networks can be calculated as follows:

• 2^24-3 = 2²¹ = 2 097 152 networks (since the IP address always begins with the bit sequence 1-1-0...)

The number of computers in a Class C network can be calculated as follows:

• 2⁸-2 = 254 computers (x.x.x.0 -> network address and x.x.x.255 -> broadcast address are not permitted)

Fig. 04: Class C network

Class D subnetwork
The class D subnetwork consists of special addresses that are used for multicast addressing.

Summary
The splitting up of IP addresses in network share and node share leads to the following conclusions:

• A Class A network is larger than a Class C network, because there is a greater address area available for addressing the computers.

• There are much less Class A networks than Class C networks because the address area of the subnets is smaller.

Reserved addresses

• The Class A network address 127.x.x.x is reserved for the Loopback function of all computers, which means that
  all IP addresses that have the value 127 in the first byte may only be used for internal tests of computers.

• The value 255 in the last byte (Byte 4) is reserved asBroadcast Address. Thus, for example, the address 140.80.255.255 is a broadcast address to all nodes in the Class B network 140.80.0.0.

• The following ranges are reserved for private networks. All IP addresses from these ranges are not routed in the Internet.
  10.0.0.0 - 10.255.255.255
  172.16.0.0 - 172.31.255.255
  192.168.0.0 - 192.168.255.255

Until now, the connection between the class of the IP address and subnet mask has been explained. Furthermore, it is possible to extend the subnet mask with the so-called "subnetting" procedure.

Subnetting
Subnetting can be implemented in a Class A network, for example. It is possible to divide the computers of this Class A network into further logical units (subnets). We will observe the Class A network 86.x.x.x as an example. The subnet mask of this Class A network is 255.0.0.0 (1111 1111 0000 0000 0000 0000 0000 0000). The address area can be divided further into logical subnets by extending the subnet mask by 1 bit. The subnet mask is then 255.128.0.0 (1111 1111 1000 0000 0000 0000 0000 0000).

This means the following for addressing:

• Only the addresses 86.0.0.1 to 86.127.255.254 can communicate directly with each other, that is without router, because these computers have the same value (in this case "0") in the first bit after the subnet mask.

• Only the addresses 86.128.0.1 to 86.255.255.254 can communicate directly with each other, that is without router, because these computers have the same value (in this case "1") in the first bit after the subnet mask.

• The address area of the computers in this Class A network has been divided into two subnets.

Conclusion
By extending the subnet mask you can divide the address area of the computers into more logical units (subnets). The address area has been divided into two subnets in the example. By adding more bits you can quickly multiply the number of subnets.

Supernetting
Supernetting is the grouping together of multiple networks with partially the same network share in one subnet. The underlying technology is the opposite to subnetting and in principle means a procedure for addressing a large number of nodes within one subnet. With supernetting the node share of a network class is increased. Thus the network share of this network class is decreased.
We will observe the Class C network 192.168.178.0 as an example. The subnet mask of this Class C network is 255.255.255.0 (1111 1111 1111 1111 1111 1111 0000 0000). Now 2 bits are added to the node share. The subnet mask is then 255.255.252.0 (1111 1111 1111 1111 1111 1100 0000 0000).

• The lowest IP address of the network to be assigned is
  192.168.176.1 (1111 1111.1111 1111. 1011 0000. 0000 0001)

• The highest IP address of the network to be assigned is
  192.168.179.254 (1111 1111.1111 1111. 1011 0011. 1111 1110)

• The addresses 192.168.176.1 to 192.168.179.254 can communicate directly with each other, this means without router.

Requirement
The use of "Supernetting" requires that the modules in the network support the "Classless Inter Domain Routing" (CIDR) function.

Note
If the module configured in STEP 7 does not support the subnetting function or the supernetting function, then use of these functions is prevented by the following error message in STEP 7

Fig. 05: STEP 7 error message

The STEP 7 Online Help indicates that the subnet mask in the incorrect format as follows.

Fig. 06: STEP 7 Online Help

Description
This entry provides an overview of the connectors and cables that can be ordered for the distributed IO systems ET 200eco, ET 200eco PN and ET 200pro.

Connectors and cables for the distributed IO system ET 200eco and ET 200eco PN
The table below gives an overview of the connectors and cables you can order for the distributed IO system ET 200eco and ET 200eco PN.
 

Module	Connectors and cables
ET 200eco	cable_and_connector_for_ET200eco_en.pdf ( 149 KB )
ET 200eco PN	cable_and_connector_for_ET200ecoPN_en.pdf ( 260 KB )

Connectors and cables for the connection modules of the distributed IO system ET 200pro
The table below gives an overview of the connectors and cables you can order for the various connection modules of the distributed IO system ET 200pro.
 

Connection modules for	Connectors and cables
IM154-1 / IM154-2	cable_and_connector_for_IM154-1_and_IM154-2_en.pdf ( 69 KB )
IM154-4	cable_and_connector_for_IM154-4_en.pdf ( 64 KB )
IM154-6	cable_and_connector_for_IM154-6_en.pdf ( 57 KB )
IM154-8	cable_and_connector_for_IM154-8_en.pdf ( 84 KB )
EM	cable_and_connector_for_EMs_en.pdf ( 203 KB )
PM-E	cable_and_connector_for_PM-E_en.pdf ( 31 KB )
PM-O	cable_and_connector_for_PM-O_en.pdf ( 22 KB )
Communication module RF170C	cable_and_connector_for_RFID_en.pdf ( 29 KB )

Connectors and cables for the motor starters, special modules, frequency converters and F switch of the distributed IO system ET 200pro
The table below gives an overview of the connectors and cables you can order for the motor starters, special modules, frequency converters and F switch of the distributed IO system ET 200pro.
 

Module	Connectors and cables
Motor starter	cable_and_connector_for_MS_en.pdf ( 28 KB )
Special modules - ASM - RSM - F-RSM	cable_and_connector_for_ASM_RSM_F-RSM_en.pdf ( 24 KB )
Frequency converter	cable_and_connector_for_FC_and_F-FC_en.pdf ( 75 KB )
F switch	cable_and_connector_for_F-Switch_en.pdf ( 22 KB )

Description
This entry gives you an overview of the PROFINET IO controllers and IO devices that support the PROFINET functions below:

• Isochronous real-time communication (IRT)
• Prioritized startup
• Medium redundancy protocol (MRP)
• PROFIenergy
• Shared device
• I device
• Clock-synchronized mode for process data

The PROFINET IO controllers below support the above-mentioned PROFINET functions.

IO-Controller_PROFINET_functions_en.pdf ( 47 KB )

The PROFINET IO devices below support the above-mentioned PROFINET functions.

IO-Device_PROFINET_functions_en.pdf ( 47 KB )

Description
The Entry ID 49311792 gives you an overview of the PROFINET IO controllers and IO devices of SIMOTION and SINAMICS that support the PROFINET functions above.

Isochronous real-time communication (IRT)
Synchronized transmission procedure for cyclic exchange of IRT data between PROFINET devices. There is a bandwidth reserved for the IRT data in the transmitter clock. The reserved bandwidth guarantees that the IRT data can be transmitted at reserved, clock-synchronized intervals even when the network is otherwise heavily loaded (with TCP/IP communication or additional real-time communication, for example).

Prioritized startup
Prioritized startup is the PROFINET functionality for accelerating the startup of an IO device in a PROFINET IO system with RT and IRT communication.

The function cuts the time needed by the appropriately configured IO devices to get back into the cyclic user data communication in the cases below:

• After return of power supply
• After station return
• After IO device enabling

Medium redundancy protocol (MRP)
Medium redundancy is a function for ensuring that availability of networks and plants. Redundant transmission paths (ring topology) ensure that when one transmission path fails an alternative path is made available.

PROFIenergy
Function for saving power in the process, during idle times, for example, through temporary switch-off of the encoder and load supply in the potential group via standard PROFIenergy commands.

More information about PROFIenergy is available in the manuals ready for downloading in the Entry IDs below.
 

Manual	Description	Entry ID
SIMATIC PROFINET System description	General information about PROFIenergy	19292127
SIMATIC S7-300 with PROFINET interface	PROFINET IO Controller or IO Device with PROFIenergy	12996906
System and Standard Functions for S7-300/400 Volume 1 and Volume 2	Send and receive (PROFIenergy) data records With SFB73 "RCVREC" you receive the (PROFIenergy) data records in the I device of the higher-level IO controller. With SFB74 "PRVREC" you make the (PROFIenergy) data records in the I device available to the higher-level IO controller.	44240604
SIMATIC HMI Comfort Panels	Control of the backlight of the operator panel with PROFIenergy	49313233
SIMATIC ET 200S: Power module PM-E	Switch-off of the potential group by means of PROFIenergy	43582121
SIMATIC ET 200S: Motor starter ET 200S HF	Switch-off of the motor and measurement of the current motor current with PROFIenergy	6008567
SENTRON PAC3200 / PAC4200	Incorporation of the SENTRON PAC multifunctional measuring device in PROFINET and PROFIenergy with the SENTRON SWITCHED ETHERNET PROFINET module	26504372
SIRIUS motor starter M200D for PROFIBUS / PROFINET	PROFIenergy with motor starter M200D	38823402
ET 200S motor starter, fail-safe motor starter, safety engineering	PROFIenergy with DPV1 starter	6008567
ET 200pro motor starter	PROFIenergy with motor starter ET 200pro	22332388

Shared device
IO device that makes its data available to multiple IO controllers.

I device
Using the I device function you can use an IO controller also as IO device and thus establish a separate lower-level PROFINET IO subnetwork.
An I device can also be used as a shared device.

Clock-synchronized mode for process data
Process data, transmission cycle via PROFINET IO and user program are synchronized with each other to achieve the highest deterministics. The input and output data of distributed IOs in the plant is captured and output simultaneously. The equidistant PROFINET IO cycle is the clock for this.

Description:
IO devices that support the "Replace device without interchangeable medium" function can be replaced without the need for an interchangeable medium (Micro Memory Card, for example) with saved device name being slotted.
The replacement IO device no longer receives the device name from the interchangeable medium, but from the IO controller.

For this, the IO controller and the neighboring PROFINET devices of the replaced IO device must also support the "Replace device without interchangeable medium" function.

The IO controller uses the topology configured in STEP 7 to assign the device name and the neighbor relationships of the IO devices.

The IO controllers below support the "Replace device without interchangeable medium" function:

36752540_PROFINET_IO_Controller_list_en.pdf ( 19 KB )

The following IO devices support the "Replace device without interchangeable medium" function:

36752540_PROFINET_IO_Device_list_en.pdf ( 17 KB )

Configuration Notes:
With the extended PROFINET diagnostics it is possible to have functions like the diagnostics and parameterization of integrated Ethernet interfaces (e.g. fiber-optic diagnostics and topology configuration). The PROFINET IO-Devices that support extended PROFINET diagnostics are configured in the Hardware Configuration in STEP 7. They are available in the hardware catalog and have additional ports e.g. interface modules as subslots in Slot 0. 

Example:
ET200S with and without PROFINET diagnostics

Fig. 01

The following IO-Controllers support the extended PROFINET-Diagnostics:
   

Module	Firmware	MLFB
PC CPs
CP1616	from V2.0	6GK1 161-6AA00
CP1604	from V2.0	6GK1 160-4AA00
SIMATIC NET PC-Software
SOFTNET PROFINET IO	from V7.1 (Edition 2008)	6GK1704-1HW71-3AA0
Embedded and PC-based Automation
WinAC RTX 2008	from V4.4	6ES7 671-0RC06-0YA0
S7-mEC, EC31-RTX	from V4.4	6ES7 677-1DD00-0BB0
S7-400 CPUs
CPU 414-3 PN/DP	-	6ES7 414-3EM05-0AB0
CPU 416-3 PN/DP	-	6ES7 416-3ER05-0AB0
CPU 416F-3 PN/DP	-	6ES7 416-3FR05-0AB0
S7-300 CPUs
CPU 315-2 PN/DP	from V2.5	-
CPU 315F-2PN/DP	from V2.5	-
CPU 317-2 PN/DP	from V2.5	-
CPU 317F-2PN/DP	from V2.5	-
CPU 319-3 PN/DP	from V2.5	6ES7318-3EL00-0AB0
CPU 319F-3 PN/DP	from V2.5	6ES7318-3FL00-0AB0
Industrial Ethernet CPs
CP343-1 Standard	from V2.0	6GK7343-1EX30-0XE0
CP343-1 Advanced	from V1.0	6GK7343-1GX30-0XE0
CP443-1 Standard	from V1.0	6GK7443-1EX20-0XE0
CP443-1 Advanced	from V2.0	6GK7443-1GX20-0XE0
ET 200S
IM151-8 PN/DP CPU	from V2.7	6ES7 151-8AB00-0AB0
IM151-8F PN/DP CPU	from V2.7	6ES7 151-8FB00-0AB0
ET 200pro
IM154-8 CPU	from V2.5	6ES7 154-8AB00-0AB0

The following IO-Devices can use the extended PROFINET-Diagnostics:
 

Module	Firmware	MLFB
PC CPs
CP1616	from V2.0	6GK1 161-6AA00
CP1604	from V2.0	6GK1 160-4AA00
Industrial Ethernet CPs
CP343-1 Advanced	from V1.0	6GK7343-1GX30-0XE0
ET 200S modules
IM151-3PN FO	from V4.0	from 6ES7 151-3BB21-0AB0
IM151-3PN ST	from V4.0	from 6ES7 151-3AA20-0AB0
IM151-3PN HF	from V4.0	from 6ES7 151-3BA20-0AB0
IM151-3PN HS	-	from 6ES7 151-3BA50-0AB0
ET 200M modules
IM 153-4PN	-	6ES7 153-4AA00-0XB0
ET 200pro modules
IM154-4PN HF	-	from 6ES7 154-4AB00-0AB0
ET 200eco PN	-	6ES7 141-6Bx00-0AB0 6ES7 142-6Bx00-0AB0 6ES7 142-6Bx50-0AB0
Network components
PN/PN coupler	-	6ES7 158-3AD00-0XA0
SCALANCE X20x IRT products	from V2.1	-
SCALANCE X200 products	from V2.1	- see Entry ID: 25472849
SCALANCE X300 products	-	-
SCALANCE X414-3 E	from V2.1.1	- see Entry ID: 25355654
SCALANCE X408-2	-	-
Gateways
IE/AS Interface Link PN/IO	from V2.0	Single AS-i master: 6GK1 411-2AB10 Double AS-i master: 6GK1 411-2AB20

The PROFINET IO devices that support the extended PROFINET diagnostics can only be operated on PROFINET IO controllers that likewise support the extended PROFINET diagnostics.

There is a migration GSDML file for some of the PROFINET IO devices listed above for operating the PROFINET IO device on a PROFINET IO controller that does not support the extended PROFINET diagnostics.

Example:
PN/PN coupler

Fig. 02

Note:
The following applications provide a detailed description, including sample program, of the diagnostics options available in a PROFINET IO system.

• "Diagnostic Methods for PROFINET Network Components (PROFINET IO, SNMP, WBM)" in Entry ID: 21566216
• "PROFINET IO – Diagnostics Processing in the User Program"
  in Entry ID: 24000238