Beruflich Dokumente
Kultur Dokumente
KnowBase 57174
Purpose
This document includes practical information that may or may not be included in other documentation. With time, some of the information may be included in formal publications. Likewise, a previously not widely understood topic may become widely know and can be deleted from this document. Changes, additions & deletions, are made over time. If you have an EtherNet/IP topic that should be described but is not already covered elsewhere, contact Dan Zaniewski.
Outline
References Topologies Connectivity Segmentation Performance Availability Manageability Troubleshooting Scalability Security Switches Media Some list prices (2008) General topics Whats new in v18 Appendix
3
References
www.odva.org/Home/ODVATECHNOLOGIES/EtherNetIP/EtherNetIPLibrar y/tabid/76/Default.aspx www.rockwellautomation.com/knowledgebase/?OpenForm samplecode.rockwellautomation.com/idc/groups/public/documents/webasse ts/sc_home_page.hcst Product: Network Communications Technology: Faceplates Title: Ethernet www.ab.com/networks/site-index.html www.ab.com/networks/architectures.html
Rockwell/Cisco reference archtictures, Design & Implementation Guide
Publication ENET-UM001G-EN-P Provides connection and packet rate specs for modules
Topologies
What topologies are there?
Line Ring (cable redundancy) Star Double star (distribution switch redundancy) Combinations
Linear topology
Switch1 Switch2 Switch3 Switch4
Advantages
Architecturally, a drop-in replacement for RIO.
Disadvantage
Some traffic may traverse multiple switches (Fewer switches in the path is better)
Linear topology
How many switches can I have in a line? ANSWER:
That depends on several factors:
Single point of failure consideration
Clients tolerance for delay (e.g. timeout)
Switchs capacity (e.g. wire-speed on all ports, switching fabric) The amount of traffic (uni, multi, broadcast) queued in front of a message under test. Troubleshooting a longer line is more difficult to find the problem
Connectivity
Methods for connecting IP networks: Isolated
Not connected to any other network
Restricted
By protocol, IP address, MAC, etc.
Segmentation
How many nodes can I put on a network?
Fewer is better (see notes) because:
Broadcast storm size and duration is less Protection against defective device behavior Spanning tree event (re-convergence) reduced exposure Losing a few nodes to a malfuncton is better than more nodes
Why do I segment?
Performance and security
Best approach
Performance
System performance requires: - characterizing each component in the system
- combining the components for end-end result
Availability
Switches Media CLGX redundancy inc ENBT/EN2x
11
Manageability
Manage device/sys changes, inc reconfig Monitor (determine if we are within specs) Baseline (take a snapshot of good system) Troubleshoot (fix a customer anomaly) Management tools
12
Troubleshooting - Basics
13
15
Troubleshooting - common
One common anomaly.duplex mismatch
Autonegotiation is out-of-the-box easy to use and reliable. But, if your company policy is to force the duplex and speed, this is legitimate. However, if you force, remember to force both the switch port and the corresponding end-device. Other wise, there will be a mismatch and communications problems will occur.
Depending on the timing of who-transmits-when, the problem may not be obvious or may be very obvious. Examine both the switch port and the end-device (e.g. 1756-ENBT) for Ethernet errors. Signature errors for duplex mismatch include: - Late collisions - FCS/CRC errors - Alignment errors
16
Troubleshooting S8000
If you cycle power, the date/time changes to
Feb 28 1993 This is how the product was designed by Cisco. There is no battery to retain the date/time. CompactFlash retains the switch configuration but not the date/time.
17
Troubleshooting S8000
To gather switch data quickly, especially with multiple switches, use Cisco Network Assistant to look at the Monitor tab:
1. 2. 3. Reports tab Port Statistics Views Topology shows all the switches. System Messages This info is close, if not identical, to the switch log file.
18
Troubleshooting S8000
What do I look at first with a Stratix 8000?
(How do I know if the switch is happy?)
Troubleshooting - Basics
Provide the required files describe in this document. If you open a tech support case but do not provide all the files, analysis will take longer and waste everybodys time. Do NOT use Wireshark without first discussing with Tech Support. Any customer anomaly needs to have a tech support case opened. You can call Commercial Engineering to discuss a situation but they will not work on a post sale event unless you have a tech support case open AND tech support has requested help (case was escalated). Wireshark trace analysis generally takes time to analyze and create a user-friendly report. There is no such thing as a quick look.
20
Troubleshooting - General
Files we need:
Network drawing (all switches, routers, copper/fiber converters, wireless, etc.) IP address of the nodes and also the types of devices Switch operating status including errors, duplex, forced/auto (CLI or web browser) Relevant Logix acd file(s) Configuration file for each switch Firmware versions
If you use HTTrack software, this will be provided by the software.
Search the Knowledgebase for any known anomalies associated with the products in your system If 1794-AENT/A is involved, then verify if ground clip helps Module screen captures (use HTtrack Website Copier, www.httrack.com)
HTtrack software is free and easy to use. It copies all the pages quickly.
Examples: Home, Diagnostics Overview, Ethernet statistics, I/O connections
Troubleshooting - General
Get a description of the anomaly
What is the problem the customer sees? (simple description)
Example: The I/O tree in RSLogix5000 has a yellow triangle on a Flex I/O module. Only a single device is being lost?
Example: Only a single device, a 1794-IB16 module, has a yellow triangle
Was it ever operating correctly or did this start recently? How often does it happen? (constantly, once per hour, once per week?) For how long does the anomaly last? (3 seconds, forever?) How do you recover? (cycle power to device?, recovers by itself?) What additional steps, if any, did you already take to troubleshoot? E.g. hardware changes
22
Troubleshooting - General
At some point, you might be asked for a network capture
Install Wireshark (free at www.wireshark.org) Configure port mirroring in a switch (see next pages for details) In your report, specify which device was port mirrored. Send a short (e.g. 5-10 seconds) trace to immediately for review
To verify that port mirroring is configured correctly.
Identify the IP addresses that are having a problem and all others in capture Dont configure any capture filters (we need to see all the frames)
Multiple file capture (circular buffer, see next pages for detail) If the event cannot be easily put into 1 file, configure Wireshark for multiple files.
The number of files is dependent on how many are needed to insure that you stop the trace before the circular buffer event is overwritten.
NOTE: If port mirroring functionality is not available (device is not a managed switch), you need to work around it.
23
24
All three of the above are the same in that the firmware cant associate a received packet with an active CIP connection ---- it's rejected . 26
Provide a list of all IP addresses Provide network drawing Provide a simple description of the anomaly
Example: CLGX 1.2.3.4 loses its connection to Point I/O 1.2.3.5 once a week.
27
Troubleshoot Wireshark
CIP connections
CIP connections are bi-directional. During trace analysis, packets in both directions need to be identified by their connection identifiers. The identifiers are provided in the forward open reply. So, when pursuing a class 1 (produce tag or I/O) connection anomaly, the trace must contain a forward open and then, of course the subsequent anomaly. The anomaly could be some packet loss or loss of the connection.
See the next 2 slides for more information.
28
Troubleshoot Wireshark
CIP connections
If produce tag or I/O connections are being lost and recovered frequently, then a Wireshark trace should include these without any additional work on your part. However, if connection losses occur infrequenently, you will need to make a forwardOpen (makes a connection) happen. Again, the forwardOpen includes connection identifiers for both directions (O->T and T-> O).
29
Troubleshoot Wireshark
CIP connections
If class 1 connections are being lost infrequently, you will need to do something to make sure there is a forwardOpen in the trace (in addition to the anomaly). You can make this happen several ways at either of the 2 Ethernet modules involved in the CIP connection: - Remove/reconnect the Ethernet cable - Inhibit the connection and reenable (RSLogix5000) - Cycle power
30
If the switch is managed, see switch documentation for directions to configure port-mirroring
Common methods: - web browser (Internet Explorer) - serial cable - customer application
4.
33
If the event happens infrequently, you will need to configure Wireshark to run continuously, filling multiple files in a circular buffer. See the next slide for more information. NOTE: You must manually stop the trace after the event BEFORE the event is overwritten in the circular buffer.
34
Specify enough files to insure that you have time to stop the capture before the event is overwritten.
35
36
Scalability/Flexibility
Allow for reserve switch port capacity Moving devices Adding devices IP address scheme Allow for reserve performance capacity
37
Security
Level1 Level2 Level3 DMZ How to (ACL, Firewall) secure
38
Stratix Switches
Family members -- 8000, managed, RA/Cisco, 6-26 ports
Released Summer 2008
Reset-to-factory-default procedure Express Setup Password recovery procedure Switch replacement (use compact flash) IOS upgrade Troubleshooting using switch diagnostics RSLinx, RSNetWorx, faceplates switch access Hardware: 2 power supply connectors, compactFlash
41
S8K Reset-to-factory-default
Cycle power and insert paper clip immediately Keep paper clip in until 3 LEDs turn solid red EIP Mode LED EIP Net LED Setup LED Remove paper clip and wait until Setup LED is solid green Both config.txt and VLAN.dat files were both deleted You are all done.
42
43
8. Select Submit.
44
45
Config Recommendations
Recommended system configuration
Avoid mixed spanning tree protocols
A loop will allow a broadcast storm. A single protocol is the best approach. Multiple protocols may prevent loops but verification testing is needed.
IGMP Affect of multiple queriers Affect of mixing versions (v1-v3) VLAN Consider use of VLANs as a default Configure trunks to carry only needed VLANs
46
48
L3 switches
- Create VLANs - Create IP address for each VLAN (gateway address)
49
Switch/router access
Q: Can I reconfigure any switch or router without knowing the passwords? A: Yes. For many/most devices, given physical access, there is a backdoor procedure, vendor specific.
50
51
52
DHCP Description
Present
The affects of Persistence, Reserved Only, DHCP Snooping The affects of local and remote servers. What to avoid.
NOTE: The Stratix8000 Software Manual describes DHCP.
53
-Reserved Only
- DHCP Snooping (release 4)
54
DHCP Description
Describe DHCP including persistence and Reserved Only.
Connected to FA1/1
Local switch
Connected to FA1/2
A pool of 10 addresses has been created. Only 1 of these addresses has been assigned (persistence on FA1/1).
55
Two DHCP requests are received by the local switch FA1/1 and FA1/2 and are broadcast out all ports, including G1/1. Both will get DHCP offers from local Stratix8000 Any device may accept the first offering or a subsequent offering.
56
DHCP Description
Case 2 - pool w persist but w/o Reserved Only
(no remote DHCP server)
The DHCP request is received by the local switch and broadcast out all ports, including G1/1. There are no remote DHCP servers active in this example. An IP address has been assigned (persistence) to FA1/1 by local switch. The device on FA1/1 may accept the local offer.
The device on FA1/2 will get an offer from the local switch because there are 9 available addresses from the DHCP pool.
Any device may accept the first offering or a subsequent offering.
57
DHCP Description
Case 3 - pool with persistence and with Reserved Only (no remote
DHCP server)
The DHCP request is received by the local switch and broadcast out all ports, including G1/1. There are no remote DHCP servers active in this example. The device connected to port FA1/1 is requesting DHCP. This port is in the persistence table. The device on FA1/1 may accept the local offer. The device connected to port FA1/2, is requesting DHCP, but is not in persistence table. The device on FA1/2 will NOT get an offer from the local switch because Reserved Only is selected (even though there are 9 available addresses from the DHCP pool).
58
DHCP Description
Describe DHCP including persistence and Reserved Only.
Connected to FA1/1
Local switch
Connected to FA1/2
DHCP server(s)
Connected to G1/1
A pool of 10 addresses has been created. Only 1 of these addresses has been assigned (persistence on FA1/1). Remote server(s) included
59
DHCP Description
Case 4 DHCP pool w/o persist and w/o Reserved Only
Devices connected to the local switch issuing DHCP requests will get DHCP offers locally and remotely (assuming remote servers). The device may accept the local offering or may accept the remote offering, if any. The device may accept the first offering or a subsequent offering.
60
DHCP Description
Case 5 - pool w persist but w/o Reserved Only
An IP address has been assigned (persistence) to FA1/1 by local switch. The device on FA1/1 may accept the local offering or may accept a remote offering, if any. The device on FA1/2 will get an offer from the local switch IF there is an available address (not in the persistence table). FA1/2 will also get an offer from a remote server. The device may accept the first offering or a subsequent offering.
61
DHCP Description
Case 6 - pool with persist and with Reserved Only
Remote DHCP servers are active in this example and are connected via local switch G1/1 Automation device is connected to port FA1/1 and is requesting DHCP, is in persistence table. Automation device is connected to port FA1/2, is requesting DHCP, is not in persistence table.
62
DHCP Description
Case 6 (continued)
Remote DHCP servers are active in this example and are connected via local switch G1/1 The DHCP pool consists of 10 addresses on the local switch. Only port FA1/1 has been assigned an address from the local pool. FA1/2 is requesting an address but is NOT assigned in persist table.
63
DHCP Description
1. 2. 3. 4.
NOTE: If remote servers are Stratix8000, and they have Reserved Only, they will not DHCP offer.
64
65
Media
Copper types for EIP
Category 5e, category 6 recommended by ODVA
Mode
Speed
1783-SFP100FX 1783-SFP100LX 1783-SFP1GSX 1783-SFP1GLX (100mbps (100mbps single (1000mbps (1000mbps single multimode) mode) Connector type multimode) mode) LC LC LC X X X X X X X X
up to 2 (optional) based on SFP type based on SFP type up to 2 (optional) based on SFP type based on SFP type 8 Multimode (FX) 100mbps
1 (optional)
1000mbps
LC
1 1
100mbps 100mbps
LC LC
1783-fiberETAP everything the same as EN2F above. Stratix6000, See above. Also, autonegotiation not supported.
Stratix8000 (uplinks) See above. Also, autonegotiation not supported. Stratix8000 (expansion) See above. Also, autonegotiation not supported.
67
Media
Slip rings
Two basic types: optical, mechanical
Media, slip-rings
Example of how one customer is using
70
71
72
Monitor
Reports, IOS inventory for all switches Views, topology for all switches Views, health
Configure
73
General topics
74
76
QoS prioritization
QoS can help smooth out the peak loads and make sure that the important traffic has priority. However, the most important thing is to make sure you have enough bandwidth to begin with QoS = quality of service Refers to mechanism that provides precedence to applications. Mechanisms include ToS and CoS. TOS = type of service (layer 3) Byte in IP header 6 bits, Differentiated Services Code Point. Of the 6 bits, 3 bits of precedence. CoS = Class of service (layer 2) 3 bit field in Ethernet frame Priority 0-7
77
Additionally the EN2T/EN2F will include the QoS Object but will only be marking the CIP Motion and CIP Sync packets with the default DSCP values. The other traffic, including regular I/O, produce tags etc. will have 0 for DSCP
78
79
81
82
Spanning-tree protocols
Question: What are the spanning-tree protocols?
RSTP (2 sec)
MSTP (2 sec)
RSTP(2 sec)
REP (50ms)
DLR (1 ms)
84
Etherchannel - resiliency
Example: No ring, 0ms link loss recovery
Switch_1 P P Switch_2
P Switch_1
Switch_2
85
Resiliency
Rapid spanning-tree
Etherchannel REP DLR
86
Ping Web server (in each Ethernet module) Logix Controller task monitor Network management software
Example: IntraVue
Packet capture
Examples: Ethereal, Sniffer
CIP Connections
Most devices use 1 CIP connection A few devices use more than 1 connection
1756-DNB uses 2 (status, data) RSLinx opens as many as 5
Produce tag
The controller that produces a tag uses connections as follows:
1 + #consumers.
Note that with 125 tags produced (with only 1 consumer each), a CLGX would be out of connections.
Sending emails
Sending emails
CPX, CLGX, FlexLogix Ethernet modules can initiate emails (ENET-UM001, KBase 30937, 32295) EWEB modules can also be used to send emails
89
Intrinsically safe
Are there intrinsically safe products on EIP? Answer: Not directly on EIP. However, you can use intrinsically safe RA I/O products and put an EIP adapter outside the hazardous area by using 1797-BIC and CEC.
Reference:
http://www.odva.org/tabid/154/ctl/Detail/mid/520/xmid/18469/xmfid/8/Default.aspx 90
Multicast
- Used for one-to-many communications. - Uses IP addressing class D. - Always is UDP (at least for EtherNet/IP) - Video (which is not EIP protocol) and EIP I/O are 2 examples.
Broadcast
Used for one-to-all communications. Can be either OSI layer 2 (ARP) or OSI layer 3 (AB_ETHIP driver.)
91
Multicast considerations
What are considerations for multicast? Answer:
EIP uses multicast for I/O and produce tag IGMP recommended (Internet Group Management Protocol) TTL (time-to-live)
If the producer and the consumer are in the same network, TTL is not a factor. (TTL is a Internet Protocol parameter). Also, if in the same network, multicast routing is not needed.
92
IGMP Snooping
Recommendations
Select IGMP Snooping on all switches Enable IGMP querier on all switches Verify operation with Wireshark --- look for multicast flooding Troubleshooting an IGMP Leave message is an indicator See KnowledgeBase, IGMP Leave 55266
Note: With version 2, all the switches will negotiate and the lowest IP address will be the IGMP querier. IGMP v1 enabled queriers will not negotiate.
93
Case 2: Two controllers consuming same tag thru same ENBx At the consumer Logix chassis, if there are 2 consumer controllers for the same tag and both are consuming thru the same ENBT module, then that ENBT will send a Leave for that multicast group when both Logix controllers no longer want to consume that group. A Logix controller will not consume under the following conditions:
consumed tag is inhibited or deleted I/O connection is inhibited or deleted 95
96
97
99
ISP
internet VPN concentrator E.g. Cisco, Checkpoint. (Hardware or software.) server Internal network
- First, purchase VPN concentrator and then purchase recommended VPN client software.
Appendix
101
104
Note: Although document 22644 calls this a TCP inactivity timeout, it is actually a CIP inactivity timeout. However, no matter how you call it, it closes a TCP connection.
106
107
108
The EN3TR will expand the number of axis supported from (6-256)
109
110
VLANs
Add pix to show single switch with red and blue ports (2 VLANs with no L3 connectivity) under construction Add pix to show single switch with router on a stick (red and blue VLANs) Add pix to show multiple switches connected to router and connected via VLAN trunking
111
112
Q&A
How do I clear the configuration of a switch
Answer: Use the CLI commands as follows: - write erase (deletes startup config file) - reload (uses the non-existing config file) Note that the vlan.dat file is not deleted.
113
More Q & A
What are Network Considerations for CLGX redundancy?
Answer: A. CLGX Primary and Secondary must be in same L2 and L3 network to make IP swapping work No additional information to add. B. If source device (e.g. HMI) is in same L2 and L3 network as CLGX redundancy system (target device) No additional information to add. C. If source device is in different L2 or L3 network as CLGX redundancy system The routers must update their ARP caches in a timely fashion to allow IP swapping to operate in a timely fashion.
114
More Q & A
How do I configure a S8K switch Smartport when connecting to a DLR?
Answer: Select None in the Smartport pull-down menu.
115
Tips
116
Passwords (out-of-box)
Stratix8000
When running the web browser for the first time, you will be running Express Setup. The password you need to enter will be switch. No username is needed.
Stratix6000
The default password is PASSWORD (all upper case). You can change this to whatever you want.
118
Stratix6000
Remove the plastic clip from the rear of the switch and you will see a small reset button. Remove power from the switch. Then, hold the small reset button and then apply power. Keep hold the reset button for 30 seconds. Cycle power to complete the reset. The IP address is now 192.168.1.1. User = (no username), pw = PASSWORD
(when upgrading, user = uploader, pw = PASSWORD)
119
Questions?
120