Martin, The token ring resides inside the CISCO is not propagated outside the router itself. So in terms of their statement they are correct unless you have tokenring adapters on the cisco router.
The virtual adapters defined for the TN3270 servers and the corresponding CSNA statements act like a ring and talk to the mainframe VTAM via the CIP. Those token ring adapters act as a endpoint for XCA/SWN definitions. IBM has a migration paper for converting CISCO TN3270 definition to OSA. You could get that at the following URL ftp://ftp.software.ibm.com/software/network/commserver/whitepapers/TN3270_Migration.pdf The Cisco IOS Bridging and IBM Networking Configuration Guide, Release 12.4 at url http://www.cisco.com/en/US/docs/ios/bridging/configuration/guide/12_4/br_12_4_book.html explains in detail of the configurations of CSNA and corresponding TN3270 servers. Thanks Natarajan >>> "Kline, Martin" <martin.kl...@yrcw.com> 9/17/2009 6:17 AM >>> Chris: >In the diagram for "Ethernet-Attached SNA Nodes", does your logical >configuration correspond to the top part of the diagram which does *not* >involve having a DLSw node or the bottom part which does? No. You are oversimplifying. This Cisco router has three ethernet ports connected to (maybe switches???) and one ESCON channel port connected to an ESCON director which was used to connect it to multiple mainframes. The multiple OnePrint servers use both ethernet and SNA. None of them is directly connected to the Cisco router. Instead, they are connected to (maybe switches again????) However, I am assured by our network team that one of the router ports and all of the OnePrint servers must be on the same subnet <RANT>(There's that word again!!! Assumed to be fully understood, but never defined. It's a LAN. It's a network. It's part of a network. What defines the boundaries of a subnet????? I've asked many, many times, and gotten no answer. How can I know if a device is on a particular subnet when no one can define a subnet in meaningful terms to me? We have thousands of in-house devices on our network. They are all on our LAN. Most are inside the firewall. To me, that means they are all on the same subnet - 255.255.0.0:10.0.0.0)</RANT>. You speak of having DLSws as if they are devices, but when I look up the definition, I find it is a protocol. Isn't that like saying I have UDPs and SNAs? Returning to the primary goal, which is to remove the Cisco router as a connection to the mainframe, the OnePrint servers are only part of the issue, though they are the most difficult to understand. That router is the only IP connection to that mainframe system. The router itself supports TN3270 and presents these devices as remote SNA devices to the mainframe. People who use TN3270 connect to this router, and do not specify the mainframe's IP address or network name. It currently handles thousands of these connections. It also handles all other TCPIP traffic to this mainframe - SMTP, FTP, some CA product communications, EE, etc. Both TCPIP and VTAM on the mainframe access this router through the same single channel interface. I may be able to test parts of this new configuration in my sandbox, but when I unplug the router, all of this traffic must continue to work flawlessly. That's what I mean when I say it must work the first time. I do not have a test Cisco router, and I cannot disconnect this router from production so I can play with it in the sandbox. I already know how to configure the TCPIP traffic and the TN3270 traffic to use an OSA port and TN3270 on z/OS. Hmmmm. (long pause here, but of course you can't see that.) I shouldn't do my thinking out loud, but perhaps I can utilize one OSA port (OSA express GBE SX) to handle all traffic except the OnePrint servers, then tackle OnePrint alone using a separate OSA port (OSA Express 2 1000 BASE T Ethernet) configured as OSE. Cheryl Meehan has some suggestions on the OnePrint implementation that may prove fruitful. For now, I'll follow that track. >Needing canonical and non-canonical forms of the MAC address is what you >need to bear in mind when a token ring LAN segment is "bridged" to an >Ethernet LAN segment - if I remember this topic correctly. For what it's worth, the network team (a regrettably unreliable source) that pseudo-supports the switches and little else (definitely, if 'mainframe' is mentioned, then they do not support it), insists we absolutely do not have and do not support token ring protocol. Yet, I am looking at a printout of the Cisco CIP configuration, and see "lan TokenRing 1; source-bridge 300 1 333; . . ." This is the same team that believes a 30-minute outage to a main switch is 'pretty much' non-impacting, even though it disables over 100 servers, all mainframe connectivity including system consoles, and so forth. In other words, my confidence in the reliability of what they say is extremely low. ---------------------------------------------------------------------- For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L NOTICE OF CONFIDENTIALITY The information contained in this communication, including but not limited to any accompanying document(s) and/or attachment(s), is privileged and confidential and is intended solely for the above-named individual(s). If you are not the intended recipient, please be advised that any distribution, copying, disclosure, and/or use of the information contained herein is strictly prohibited. If you received this communication in error, please destroy all copies of the communication, whether in electronic or hard copy format, and immediately contact the Security Office at EdFund at (916) 526-7539 or securityoff...@edfund.org. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
