Table of Contents
Advertisement
GFK-2573AD
Restriction/Open Issues
Page function not available
Response to invalid command
entry
telnetd command response
log details command response
term command response
Operational Notes
Operational Note
Storing updated media
redundancy protocol (MRP)
configurations to large
operating MRP ring networks
with fast IO update rates
configured can result in
PROFINET I/O device Loss/Add
faults
Description
The output paging function, as described in the shConfig command, is not
currently functioning.
The error message displayed in response to an invalid show port help command
does not provide useful information. Example: show port fdp help is an invalid
command.
To see a list of valid parameters for the show port command, type show port ?
The CLI does not echo the new number of max connections in its response to
the telnetd <maxconnections> command. However, the command still functions
properly and updates the maximum number of telnet connections.
When displaying numerous local log table entries using the log details
command, sometimes erroneous blank characters appear within the display.
Use the log details <log entry number> command to view the disrupted log table
entry. Example: log details 99.
Occasionally, the CLI does not respond to the term command. To recover,
restart the terminal emulation program.
Description
When storing Media Redundancy Protocol (MRP) configuration updates to an
operating MRP ring network, users may infrequently observe one or more pairs of
Loss of Device and subsequent Addition of Device faults regarding PROFINET I/O
Device faults on the network. This is expected behavior and is more likely to occur
on ring networks with a large number of PROFINET I/O Devices acting as MRCs
with very fast I/O Update Rates configured.
Because changing MRP configuration settings require each MRC to break and
reconnect its connections to the ring network, IP packets on the network may be
lost as this flurry of connection breaks/ reconnects occur on the network. Since a
PROFINET I/O Device is considered lost if it misses three consecutive I/O data
transactions if three consecutive I/O data packets from a particular PROFINET I/O
Device are lost due to network reconfiguration, the device will appear to be lost to
the PNC001 and a Loss of I/O Device is logged. When the network stabilizes, the
PNC001 will be able to re-establish connection with the lost IO Device and an
Addition of I/O Device fault will be logged.
May 2023
20
Advertisement
Table of Contents
