Description This entry describes how to set the "Port Mirroring" function in the Industrial Ethernet switch SCALANCE X in order to monitor data transfer from a SCALANCE X port.
In this example we monitor the data transfer at Port 3 of a SCALANCE X 208. Using a network protocol recording you can monitor the messages sent and received by an S7-1200 CPU connected to Port 3. You can use the Wireshark tool installed on a SIMATIC Field PG to do the network protocol recordings. In order to be able to analyze the data traffic at Port 3 of the SCALANCE X 208 using network protocol recording, you connect the SIMATIC Field PG also to the SCALANCE X 208, at Port 8, for example, and mirror the data traffic at Port 3 at Port 8 (Port Mirroring).
Fig. 01
To set the "Port Mirroring" function you open the "Switch" menu in the Web Based Management of the SCALANCE X.
Enable the "Monitoring Enable" function.
For "Mirrored Port" you specify the port to be monitored: Port 3, for example, to which the S7-1200 CPU is connected.
For "Monitor Port" you specify the port to be used for monitoring: Port 8, for example, to which the SIMATIC Field PG is connected.
Fig. 02
Note A ring port cannot be used as Monitor Port.
After setting the "Port Mirroring" function in the SCALANCE X you can use the Wireshark to do network protocol recording.
Further Information
Detailed information about the SCALANCE X Industrial Ethernet switches is available in the manuals below.
Which manufacturer ID, in other words OUI (Organizationally Unique Identifier), does SIEMENS AG use for the MAC addresses of network-compatible devices?
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.
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.
Where can you find information on the topic of PROFINET?
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:
Description:
Power over Ethernet (PoE) is a power supply procedure for network components in compliance with IEEE 802.3af and 802.3at. With PoE, power and data are transferred together via the Ethernet cables used which connect the network components. This eliminates the need for addition power lines and thus saves investment and maintenance costs. PoE can be used with all network components that consume little power (max. 12.95 Watt).
In compliance with standard IEEE 802.af, with 10Base-T and 100Base-TX two wire pairs of the Ethernet cable are used for power supply.
In compliance with standard IEEE 802.at, with 100Base-T all four wire pairs of the Ethernet cable are used for power supply.
There are two ways of supplying power with PoE:
Method 1: Redundant wires With Fast Ethernet, the wire pairs 1, 2 and 3, 6 are for data transfer. In this case, wire pairs 4, 5 and 7, 8 are used for power supply. If there are only 4 wires in the Ethernet cable, the power supply is modulated onto wires 1, 2 and 3, 6 (see "phantom power supply").
This method supplies the power via two wire pairs of the Ethernet cable in compliance with IEEE 802.3af.
Method 2: Phantom power supply
In the case of phantom power supply the power is supplied via the wire pairs via which the data is also transferred, i.e. the power is modulated onto the data cable. In the case of Gigabits, all eight wires of the Ethernet cable are used for data transfer and power supply in compliance with IEEE 802.3at. In the case of 10/100 Mbit/s, four wires of the Ethernet cable are used for data transfer and power supply in compliance with IEEE 802.3af.
In the case of PoE, there is a power generator (Power Source Equipment, PSE) and power consumers (Power Devices, PD).
A power consumer (PD) must support both Method 1 and phantom power supply via redundant wires.
A power generator (PSE) can supply power to power consumers (PD) via
Redundant wires or
Phantom power supply or
Redundant wires and phantom power supply.
Fig. 01
Power consumers (PD) are the following, for example:
SCALANCE W-700 Access Points and Client Modules as well as IP cameras, e.g. CFMC1513 and CCMS1315 They support power supply from Power-over-Ethernet (PoE), i.e. they are power consumers (PD) as PoE-compatible terminals. The SCALANCE W-700 Access Points and Client Modules are authorized as PD in compliance with IEEE 802.3af. The SCALANCE W Access Points can be supplied by PSE in compliance with IEEE 802.3at, because the standard IEEE 802.3at is downwards compatible to IEEE 802.3af.
Power generators (PSE) are, for example:
SCALANCE X Industrial Ethernet Switches X108 PoE, XR324-4M PoE and X308-2M PoE
They permit supply of terminals via Ethernet cables via Power-over-Ethernet (PoE) in compliance with IEEE 802.3at, i.e. they generate the power as power generators.
Note: The SIMATIC NET SCALANCE W700 configuration manual, section 5.2 gives an overview of the SCALANCE W components that support the "Power over Ethernet" function after the hardware redesign. The configuration manual is available in Entry ID: 42784493.
Which PROFINET nodes support the extended PN diagnostics and what do you have to configure?
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:
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
ANSWER:
A MIB (Management Information Base) is a standardized data
structure from various SNMP variables that are written in a
language independent from the target system.
Figure 1: Overview of MIB
With the manufacturer spanning standardization of MIBs and
access mechanisms, a heterogenous network with components made by
various manufacturers can be monitored and controlled. Today, the
following MIB standards are valid:
MIB2
Bridge-MIB
RMON-MIB
MAU-MIB
If component specific, non-standardized data is required for
network monitoring, they can be written into so-called private MIBs
by the manufacturers. Thus, also values that are not included in
the in the standard MIBs can be queried.
The information available for each private MIB can be obtained from
the manufacturers.
The RFC1213 determines the MIB II which is supported by all
SNMP-compliant devices. The RFC1213 is available for download
through this link:
The OSM/ESM with network management supports the following
MIBs:
RFC1213: MIB II
RFC 2233: Interface MIB
RFC1286, RFC1493: Bridge–MIB
RFC1757: RMON–MIB
The private MIB for SIMATIC NET network components is available
on the delivered CD. The private MIB file can also be loaded
directly with a Web browser via OSM/ESM.
http://<IP–adress of OSM/ESM>/snOSM.mib
A MIB describes the entirety of all SNMP objects (SNMP
variables) which are available in the network. The MIB information
is structured similar to the Windows registry.
The OID (Object Indentifier) describes the address of the MIB
object. For standardized MIB ojects, the address is fixed. Private
MIB objects are always stored in the "Enterprise" directory. The
addresses within this structure are set by the manufacturer. Only
the manufacturer number has to be registered. The following
internet page lists the registered manufacturers that provide
privateSNMP/MIB objects.
The standard object "sysdescr" (address of object
0.1.3.6.1.2.1.1.1) contains a description of SNMP components. For
the OSM TP62, the string "OSM TP62" is issued. To make private,
non-standardized information readable, these private MIBs have to
registered with a management station (e.g. SNMP OPC Server),
otherwise they cannot be addressed. To make MIB objects directly
readable and writable, so-called MIB browsers are used. MIB
browsers are often included in the standard delivery package of
network management applications.
To enable MIBs for integration in the system, so-called MIB
compilers have to be used. STEP 7 / NCM PC includes a MIB compiler
for configuring the SNMP/OPC server.
With the MIB Compiler from SIMATIC NET, any external device as well
as new SIMATIC NET devices can be linked.
However, this requires a MIB description for this device.
While the MIB administers various system aspects - like
information regarding nods or statistical information about the
throughput of packages, connections established, error messages
etc. - , the SMI represents the framework for the MIB which
describes exactly the kind of representation of objects and
exchange through the protocol with the help of "Structure of
Managed Information". Today, MIBs according to SMIv1 and SMIv2 are
available. For MIB Compilers for SIMATIC NET, those MIBs have to
conform to SMI v1. The SMI v2 format is not supported, but for most
SNMP components, both MIB formats are available.
QUESTION:
Do switch times (Store and Forward) affect the bus cycle times?
ANSWER:
In the case of SCALANCE X switches, except for the SCALANCE X-200
IRT switch, the Store and Forward principle is applied to RT data.
The switch receives the complete data package and stores it in a
buffer. There the package is then checked by various filters and
processed. Only then is the package forwarded to the target
port.
Advantages:
Defective data packages can thus be sorted out beforehand. You can
work at different data rates (10, 100 or 1000 Mbit/s) on different
connections.
Disadvantages:
Storage and testing of data packages causes delays. For the
maximum package size of approx. 1.5 kbytes these are approx. 120µs
per switch cycle. This means that a PROFINET message can be delayed
correspondingly.
