Re: [IBMTCP-L] Replacing CIP with OSA-Express in SNA mode
Jim Mollmann
Jim
On Mon, 15 Feb 2010, VANDER WOUDE, PETER wrote:
> The XCA for the CIP has medium of RING
>
> Thanks,
> Peter
>
> CONFIDENTIALITY NOTICE: This e-mail message and all attachments may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, any reading, dissemination, distribution, copying, or other use of this message or its attachments is prohibited. If you have received this communication in error, please notify the sender immediately by telephone (704/844-4331), and delete this message and all copies and backups thereof. Thank you.
>
>
> -----Original Message-----
> From: IBM TCP/IP List [mailto:IBMT...@VM.MARIST.EDU] On Behalf Of William Hecox
> Sent: Monday, February 15, 2010 4:56 PM
> To: IBMT...@VM.MARIST.EDU
> Subject: Replacing CIP with OSA-Express in SNA mode
>
> actually, you can define T/R, FDDI, or Ethernet LANs
> on the CISCO CIP.
>
> So if the 4000 MAC-ADDR on the CIP is for a
> T/R Lan then defining the OSA as 0200 MAC should work
>
> If the 4000 MAC-ADDR on the CIP is for a
> Ethernet Lan, you have a problem. In that case
> you will still have to define the 0200 MAC on the
> OSA and the remote Ethernet devices will have
> to modify there configurations.
>
> Do you have the CISCO CIP definitions or the
> VTAM XCA definitions to look at?
> The XCA member will include a MEDIUM parm value.
> What is it?
>
> Bill
>
> ----- Original Message -----
> From: "William Hecox" <whe...@myfairpoint.net>
> To: "IBM TCP/IP List" <IBMT...@vm.marist.edu>
> Sent: Monday, February 15, 2010 4:43 PM
> Subject: Re: [IBMTCP-L] Replacing CIP with OSA-Express in SNA mode
>
>
>> We had a T/R OSA-2 years ago and we did configure
>> it with a 4000- MAC ADDR.
>>
>> I believe the original OSA Express had a T/R model.
>> I do not believe the OSAE2 and OSAE3 have a T/R model
>> available.
>>
>> So you are right you will have to code 0200- as the MAC-ADDR.
>> on the Ethernet OSA. It should work.
>>
>> If the CIP definition is a 4000- MAC-ADDR, the 0200- MAC-ADDR
>> on the OSA is correct.
>>
>>
>> ----- Original Message -----
>> From: "VANDER WOUDE, PETER" <pwo...@harristeeter.com>
>> Newsgroups: bit.listserv.ibmtcp-l
>> To: <IBMT...@vm.marist.edu>
>> Sent: Monday, February 15, 2010 4:14 PM
>> Subject: Re: [IBMTCP-L] Replacing CIP with OSA-Express in SNA mode
>>
>>
>>> Bill,
>>>
>>> The crux of the problem is that it does not appear that I can configure
>>> the OSA to use the 4000 Mac address. The OSA is a 1000BaseT card.
>>> Unless I'm mistaken, I can't configure it to use a token ring mac
>>> address, can I? If there's a way to do that, then I'll try that.
>>> Otherwise, I've asked our telecom guy I've been working with to look at
>>> the tranparent bridge.
>>>
>>> Thanks,
>>> Peter
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This e-mail message and all attachments may
>>> contain legally privileged and confidential information intended solely
>>> for the use of the addressee. If the reader of this message is not the
>>> intended recipient, any reading, dissemination, distribution, copying, or
>>> other use of this message or its attachments is prohibited. If you have
>>> received this communication in error, please notify the sender
>>> immediately by telephone (704/844-4331), and delete this message and all
>>> copies and backups thereof. Thank you.
>>>
>>>
>>> -----Original Message-----
>>> From: IBM TCP/IP List [mailto:IBMT...@VM.MARIST.EDU] On Behalf Of
>>> William Hecox
>>> Sent: Monday, February 15, 2010 4:06 PM
>>> To: IBMT...@VM.MARIST.EDU
>>> Subject: Re: Replacing CIP with OSA-Express in SNA mode
>>>
>>> Actually, I find that interesting.
>>>
>>> I would have thought the remotes that are on Ethernet
>>> would specify the canonical format (0200). (That is what we
>>> specify in our remote devices to reach the M/F).
>>> We use SNASW on our local CISCO Router.
>>>
>>> The transparent bridge on the remote CISCO router would
>>> convert the destination MAC-ADDR specified on Ethernet devices
>>> from canonical to standard T/R format 4000-
>>>
>>> The transparent bridge on the local CISCO router would convert
>>> the destination MAC-ADDR back to canonical to send frames over ethernet.
>>>
>>> You may have to try both formats on the OSA Device to see
>>> which works.
>>>
>>> Bill
>>>
>>>
>>>
>>> ----- Original Message -----
>>> From: "VANDER WOUDE, PETER" <pwo...@harristeeter.com>
>>> Newsgroups: bit.listserv.ibmtcp-l
>>> To: <IBMT...@vm.marist.edu>
>>> Sent: Monday, February 15, 2010 2:57 PM
>>> Subject: Re: [IBMTCP-L] Replacing CIP with OSA-Express in SNA mode
>>>
>>>
>>>> Bill,
>>>>
>>>> The remotes use the 4000 mac address.
>>>>
>>>> Thanks,
>>>> Peter I. Vander Woude
>>>> Systems Administrator III
>>>>
>>>>
>>>> CONFIDENTIALITY NOTICE: This e-mail message and all attachments may
>>>> contain legally privileged and confidential information intended solely
>>>> for the use of the addressee. If the reader of this message is not the
>>>> intended recipient, any reading, dissemination, distribution, copying,
>>>> or
>>>> other use of this message or its attachments is prohibited. If you have
>>>> received this communication in error, please notify the sender
>>>> immediately
>>>> by telephone (704/844-4331), and delete this message and all copies and
>>>> backups thereof. Thank you.
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: IBM TCP/IP List [mailto:IBMT...@VM.MARIST.EDU] On Behalf Of
>>>> William
>>>> Hecox
>>>> Sent: Monday, February 15, 2010 2:56 PM
>>>> To: IBMT...@VM.MARIST.EDU
>>>> Subject: Re: Replacing CIP with OSA-Express in SNA mode
>>>>
>>>> Peter,
>>>>
>>>> What MAC-ADDR do the remotes specify now to reach the
>>>> M/F through the CIP?
>>>>
>>>> Bill
>>>>
>>>> ----- Original Message -----
>>>> From: "VANDER WOUDE, PETER" <pwo...@harristeeter.com>
>>>> Newsgroups: bit.listserv.ibmtcp-l
>>>> To: <IBMT...@vm.marist.edu>
>>>> Sent: Monday, February 15, 2010 1:55 PM
>>>> Subject: Re: [IBMTCP-L] Replacing CIP with OSA-Express in SNA mode
>>>>
>>>>
>>>>> Alan,
>>>>>
>>>>> Our remote sites are running Ethernet. They are using SNA over
>>>>> ethernet
>>>>> to connect to a mac address, being hosted by the CIP (which was used to
>>>>> replace the old 3745, which had token ring). Thus the CIP is
>>>>> presenting
>>>>> a
>>>>> Token Ring mac address, even though we only have Ethernet.
>>>>>
>>>>> I'm wanting to replace it with the SNA via OSA, and am just trying to
>>>>> figure out how to map the token ring mac to actually go to the 0200 mac
>>>>> address loaded into our osa (which is the canonical version of the 4000
>>>>> mac address).
>>>>>
>>>>> Thanks,
>>>>> Peter
>>>>>
>>>>>
>>>>> CONFIDENTIALITY NOTICE: This e-mail message and all attachments may
>>>>> contain legally privileged and confidential information intended solely
>>>>> for the use of the addressee. If the reader of this message is not the
>>>>> intended recipient, any reading, dissemination, distribution, copying,
>>>>> or
>>>>> other use of this message or its attachments is prohibited. If you have
>>>>> received this communication in error, please notify the sender
>>>>> immediately
>>>>> by telephone (704/844-4331), and delete this message and all copies and
>>>>> backups thereof. Thank you.
>>>>>
>>>>> -----Original Message-----
>>>>> From: IBM TCP/IP List [mailto:IBMT...@VM.MARIST.EDU] On Behalf Of
>>>>> A.Watthey
>>>>> Sent: Saturday, February 13, 2010 1:22 AM
>>>>> To: IBMT...@VM.MARIST.EDU
>>>>> Subject: Re: Replacing CIP with OSA-Express in SNA mode
>>>>>
>>>>> Peter,
>>>>>
>>>>> The MAC address is 0200 for ethernet and 4000 for token ring. If your
>>>>> remote sites are token ring then they specify 4000 as the destination
>>>>> (I
>>>>> presume this is what they do already from what you imply - or maybe I
>>>>> infer). If the remote sites were ethernet then they would specify 0200
>>>>> already. The transparent bridge does the conversion from canonical to
>>>>> non-canonical and vice versa. You don't change the remote sites.
>>>>>
>>>>> As for the Cisco statements (which you asked for in another posting).
>>>>> You
>>>>> do not wish/choose to use SnaSw so it makes it very basic (it's good
>>>>> but
>>>>> expensive). You just create a transparent bridge to which you connect
>>>>> both
>>>>> DLSw and the ethernet interface.
>>>>>
>>>>> Does this help?
>>>>> http://www.cisco.com/en/US/tech/tk331/tk336/technologies_configuration_examp
>>>>> le09186a0080093ecd.shtml
>>>>>
>>>>> I'd also always advise restricting the MAC addresses and SAPs sent
>>>>> across
>>>>> DLSw to cut down on unwanted traffic if you don't already.
>>>>>
>>>>> https://www.cisco.com/en/US/tech/tk331/tk336/technologies_configuration_exam
>>>>> ple09186a0080094135.shtml
>>>>>
>>>>> The Cisco site is very extensive but the issue is always finding what
>>>>> you
>>>>> want.
>>>>>
>>>>> Regards,
>>>>> Alan.
>>>>>
>>>>> -----Original Message-----
>>>>> From: IBM TCP/IP List [mailto:IBMT...@VM.MARIST.EDU] On Behalf Of
>>>>> VANDER
>>>>> WOUDE, PETER
>>>>> Sent: 12 February 2010 21:37
>>>>> To: IBMT...@VM.MARIST.EDU
>>>>> Subject: Replacing CIP with OSA-Express in SNA mode
>>>>>
>>>>> Please excuse me if this is the wrong forum, but we are currently using
>>>>> a
>>>>> Cisco CIP card to handle SNA traffic coming into our mainframe. remote
>>>>> locations connect over our network via the DLSW+ process.
>>>>>
>>>>> We would like to move this over to using the OSA-Express port on the
>>>>> mainframe, but I'm running into a "minor" hickup in the process. On
>>>>> our
>>>>> CIP, the MAC address they are using (site override), starts with 4000.
>>>>> Now
>>>>> on the OSA, I can't define the MAC with the 4000 mac address, but must
>>>>> convert it to the canonical format, thus it starts with 0200.
>>>>>
>>>>> Is there a way, on the cisco side, that we can have the cisco router,
>>>>> handling the dlsw traffic, to map the 4000 mac address to the 0200 mac
>>>>> address, and thus not require significant changes on the remote
>>>>> systems?
>>>>>
>>>>> Thanks,
>>>>> Peter
>>>>>
>>>>> CONFIDENTIALITY NOTICE: This e-mail message and all attachments may
>>>>> contain
>>>>> legally privileged and confidential information intended solely for the
>>>>> use
>>>>> of the addressee. If the reader of this message is not the intended
>>>>> recipient, any reading, dissemination, distribution, copying, or other
>>>>> use
>>>>> of this message or its attachments is prohibited. If you have received
>>>>> this
>>>>> communication in error, please notify the sender immediately by
>>>>> telephone
>>>>> at
>>>>> 704.844.3100 and delete this message and all copies and backups
>>>>> thereof.
>>>>> Thank you.
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>>
>>>> ----------------------------------------------------------------------
>>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>>
>>>
>>> ----------------------------------------------------------------------
>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>
>>> ----------------------------------------------------------------------
>>> For IBMTCP-L subscribe / signoff / archive access instructions,
>>> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>>>
>>
>
> ----------------------------------------------------------------------
> For IBMTCP-L subscribe / signoff / archive access instructions,
> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>
> ----------------------------------------------------------------------
> For IBMTCP-L subscribe / signoff / archive access instructions,
> send email to LIST...@VM.MARIST.EDU with the message: INFO IBMTCP-L
>