Hi networking mavens!
[ http://www.m-w.com/dictionary/maven
Function: noun
Etymology: Yiddish meyvn, from Late Hebrew mEbhIn
: one who is experienced or knowledgeable : EXPERT; also : FREAK 4a ]
(Freak??????)
It looks like I am FINALLY, REALLY doing it! The traffic over
our 2216 will be moved to two OSAs - SNA traffic to an OSE
and TCP traffic to an OSD.
We have 2 2216s in the following setup (please use monospace font):
10.0.0.0/16 ---+---------------------------+----------
| |
| 10.0.0.8/16 |
[2216-P] |
10.1.2.1/24 | |
| 10.1.2.2/24 | 10.0.0.12/16
VSE-IM VM-P
10.0.0.0/16 ---+----------------------------+----------
| |
| 10.0.0.9/16 |
[-------2216-T-------] |
10.1.4.1/24 | |10.1.5.1/24 |
| | |
| 10.1.4.2/24 |10.1.5.2/24 | 10.0.0.7/16
VSE-TM +-----------VM-T
10.1.4.2/24 | | 10.1.5.2/24
+----------VCTC--------------+
2216-P is on lan 10.0 as 10.0.0.8, and is the gateway
for traffic to VSE-IM at 10.1.2.2
2216-T on the same lan is 10.0.0.9, and is the gateway to
VM-T 10.1.5.2 and also to VSE-TM at 10.1.4.2
VM-T has a VCTC connection to VSE-TM
using the same IP numbers as they use to the 2216:
10.1.5.2 to 10.1.4.2 (/24)
The Network-Guy (tm) has shown me a bit of his routing info:
ip route vrf MOFET 10.1.2.0 255.255.255.0 10.0.0.8
ip route vrf MOFET 10.1.4.0 255.255.255.0 10.0.0.9
ip route vrf MOFET 10.1.5.0 255.255.255.0 10.0.0.9
My VM definitions in VM-T include:
HOME
10.0.0.7 LAN10 ; OSA QDIO TO LAN 10.0.0.0/16
10.1.5.2 T2216 ; LAN ADAPTER 2216-T (10.1.5.1)
10.1.5.2 VSET ; TM (10.1.4.2)
Known gateways:
NetAddress FirstHop Flgs PktSz Subnet Mask Subnet Value Link
---------- -------- ---- ----- ----------- ------------ ------
Default 10.1.5.1 UGS 1500 <none> T2216
10.0.0.0 <direct> US 1500 0.255.0.0 0.0.0.0 LAN10
10.1.4.2 <direct> UHS 4096 HOST VSET
10.1.5.1 <direct> UHS 1500 HOST T2216
As far I understand, in order for traffic to VSE-IM,
VSE-TM, and VM-T to bypass the 2216s, I will need
to perform the following steps:
First, the default gateway needs to change from 10.1.5.1
(the 2216) back to the 10.0.0.0/16 lan.
for VM-T:
1) change the VM-T's HOME list from:
HOME
10.0.0.7 LAN10
10.1.5.2 T2216
10.1.5.2 VSET
to:
HOME
10.0.0.7 LAN10
10.1.5.2 LAN10
10.1.5.2 VSET
2) have the Network-Guy change the route of 10.1.5.0
to be 10.0.0.7
This seems to be all, making it the easiest conversion.
For VSE-TM:
1) The N-G needs to route 10.1.4.0 to 10.0.0.7 (VM-T)
2) VM needs to act as a virtual router and send all 10.1.4.2
traffic over the VCTC to VSE. Also, returning traffic from VSE
must go out over 10.0.0.7.
(Unfortunately, our VSE TCPIP seems incapable of talking to
a virtual switch, so VM must act as a router to it).
Is there anything special I need to do in VM to get it
to route to VSE and back, or are my current definitions enough?
For VSE-IM:
1) Same as for TM, the N-G needs to route 10.1.2.0 to
10.0.0.12 .
2) Here I need to set up a new VSE-I link in VM-P,
which does not yet have a VCTC to IM.
3) Once I have the CTC, VM routing should be implemented
just like between VM-T and VSE-TM.
Do I have any gross (or other) mistakes here?
Do you have any advice/hints/tips?
This is an old level, we are still using VM TCPIP
from z/VM 4.3.0, until I hopefully go to 5.3 this summer.
(I have 4.4 here also, but it never went production. It could
if necessary).
Thanks for your help!
Shimon
--
************************************************************************
Shimon Lebowitz mailto:[EMAIL PROTECTED]
VM System Programmer .
Israel Police National HQ. http://www.poboxes.com/shimonpgp
Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
************************************************************************
