ty, Brian. OSA2LAN is defined in the 1st Level Dircectory profile of my 2d Level machine.
There is an OSALAN on the 1st Level machine and a VSWITCH as well. As you noted in a previous email, I could just NICDEF from 2nd Level to the 1st Level VSWITCH, but I was not clear how I would distinguish my IP address between the 2 levels if I did that. My first Level IP is 10.13.13.18 My second Level IP is 10.13.13.26 I have no problem teleneting to 1st level, but how do I get to 2nd level from there. Alternatively you indicated in the previous email, I could just mirror everything, OSALAN, VSWITCH at 2nd Level, instead of NICDEFing 2d Level to 1st Level. I was not clear how to handle the different IP addresses if I had 2d Level go through 1st Level, so I chose the second approach, to keep them separate.. But, please explain how I navigate from 1st to 2nd Level and I will go ahead and COUPLE the 2d Level to the 1st Level as you suggest. Brian Nielsen <bniel...@sco.idaho.gov> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 10/13/2010 10:48 AM Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Cannot TELNET to Level 2 I think the you are probably issuing the COUPLE command from the wrong place. You need to issue it from your 2nd level guest userid as a comman d to your 1st level system to COUPLE to an OSA2LAN defined in your 1st leve l system. The best time to do this is after you logon to your 2nd level guest userid before you IPL it. Keep in mind that COUPLE is a class G command, so your "couple 9012" commands failed because the userid you are doing it from does not have a virtual 9012 device. It's also hard to tell from your narrative whether OSA2LAN was defined on your 1st level system (where it should be) or in your 2nd level system. You might benefit from drawing yourself a picture of your 1st & 2nd l evel systems showing what structures & addresses exist where in the hierar chy. This will help you correlate what commands need to be issued with where hey need to be issued. Brian Nielsen On Wed, 13 Oct 2010 10:15:34 -0400, George Henke/NYLIC <george_he...@newyorklife.com> wrote: >I have defined the OSA2LAN as Dave Jones suggested, though probably not >how: > >I defined a SPECIAL in the profile of the Level 2 machine and also in th e >profile of TCPIP Level 2: > >SPECIAL 9012 QDIO 3 SYSTEM OSA2LAN > >But I still get a failure at TCPIP startup: > >09:45:12 DTCQDI001I QDIO device OSA9012 device number 9012: >09:45:12 DTCQDI007I Enabled for QDIO data transfers >09:45:12 DTCOSD223E OSD device OSA9012: Return code E080 from STRTLAN fo r >IPv4 >09:45:12 DTCOSD305I Waiting for adapter-initiated Start Lan > >I also have defined a VSWITCH in TCPIP Level 2: > >SPECIAL 9112 QDIO 3 SYSTEM LNX2VSW1 > >and also in CF1 SYSTEM CONFIG: > >define vswitch lnx2vsw1 portname lnx2vsw1 rdev 9112 > >And it is there: > >q lan >09:32:30 VSWITCH SYSTEM LNX2VSW1 Type: VSWITCH Connected: 0 Maxconn: >INFINITE >09:32:30 PERSISTENT RESTRICTED NONROUTER Accountin g: >OFF >09:32:30 VLAN Unaware >09:32:30 MAC address: 02-00-00-00-00-01 >09:32:30 State: Defined >09:32:30 IPTimeout: 5 QueueStorage: 8 > >But OSA is not there now that I defined the OSA2LAN with the SPECIALS. T he >ATTACHES of 9012-9014 in TCPIP PROFILE EXEC fail at TCPIP startup becaus e >the devices are already defined in the OSA2LAN SPECIAL: > >Q OSA >09:35:07 An active OSA was not found. > >Yet, 9012-9014 are there as OSA devices: > >q 9012-9014 >09:36:35 OSA 9012 FREE , OSA 9013 FREE , OSA 9014 FREE > >But I cannot COUPLE them to the VSWITCH or LAN: > >couple 9012 system vlnx2sw1 >09:39:27 HCPCPL040E Device 9012 does not exist >Ready(00040); T=0.01/0.01 09:39:27 >q 9012 >09:39:40 OSA 9012 FREE >Ready; T=0.01/0.01 09:39:40 >couple 9012 system osa2lan >09:40:00 HCPCPL040E Device 9012 does not exist > >I added the dynamic parms in MPROUTE per Marcy: > >INTERFACE NAME=VIRLNK1 > IP_ADDRESS=10.13.13.26 > SUBNET_MASK=255.255.255.252 > MTU=1492; >RIP_INTERFACE NAME=OSA9012LNK > IP_ADDRESS=172.28.3.140 > SUBNET_MASK=255.255.255.192 > RIPV2=YES > RECEIVE_RIP=YES > RECEIVE_DYNAMIC_NETS=YES > RECEIVE_DYNAMIC_SUBNETS=YES > RECEIVE_DYNAMIC_HOSTS=YES > MTU=1492; >RIP_INTERFACE NAME=OSA9112LNK > IP_ADDRESS=172.28.3.240 > SUBNET_MASK=255.255.255.192 > RIPV2=YES > RECEIVE_RIP=YES > RECEIVE_DYNAMIC_NETS=YES > > >But I still cannot find the Gateway Router. > >Here is the MPROUTE log: > >EZZ7838I Using configuration file: MPROUTE CONFIG >EZZ7883I Processing interface from stack, address 10.13.13.26, name >VIRLNK1, ind >ex 1, flags 4041 >EZZ7871I No matching interface statements for 10.13.13.26 (VIRLNK1) >EZZ7883I Processing interface from stack, address 172.28.3.140, name >OSA9012LNK, > index 2, flags 62 >EZZ7871I No matching interface statements for 172.28.3.140 (OSA9012LNK) >EZZ8023I The RIP routing protocol is Enabled >EZZ8036I The IPv6 RIP routing protocol is Disabled >EZZ7937I The IPv4 OSPF routing protocol is Disabled >EZZ7937I The IPv6 OSPF routing protocol is Disabled >EZZ7875I No IPv4 default route installed >EZZ7898I MPROUTE Initialization Complete > >Another anomaly: When I use a valid "slash notation" in TCPIP PROFILE, > >10.13.13.26/30 VIRLNK1 > >MPROUTE does not like the subnet mask and it and abnormally ends: > >10:01:29 DTCPDO087I Dynamic Routing active; ICMP redirects will be ignor ed > >10:01:29 DTCPDO151E Subnet mask supplied by MPRoute (255.0.0.0) for link >VIRLNK1 > does not match subnet mask specified on the HOME st >atement (255.255.255.252). > >Without the "slash notation" it is just fine. > >Sorry, if this is all overwhelming, but if anyone who has a working mode l >or more ideas on how to configure things it would be greatly appreciated . > > > > >Marcy Cortes <marcy.d.cor...@wellsfargo.com> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >10/12/2010 09:01 PM >Please respond to >The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > >To >IBMVM@LISTSERV.UARK.EDU >cc > >Subject >Re: Cannot TELNET to Level 2 > > > > > > >You're going to have to put the RIPV2=YES >> RECEIVE_RIP=YES >> RECEIVE_DYNAMIC_NETS=YES >> RECEIVE_DYNAMIC_SUBNETS=YES >> RECEIVE_DYNAMIC_HOSTS=YES >On 2nd level def for the interface just like you did for the first I >think. > > > >Marcy > > >From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On >Behalf Of George Henke/NYLIC >Sent: Tuesday, October 12, 2010 4:35 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: [IBMVM] Cannot TELNET to Level 2 > > >It's all virtual, Level 2. > >So I guest I just put a SPECIAL in the directory entry for the Level 2 >machine. > >In the meantime I have noticed that MPROUTE is coming up with OSPF >protocol and all I have is RIP INTERFACE statements. > >Do you know how I specify RIP instead of OSPF protocol when MPROUTE come s >up? > >MPROUTE does not stay up and that is another problem. > > > >Dave Jones <d...@vsoft-software.com> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >10/12/2010 07:19 PM >Please respond to >The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > >To >IBMVM@LISTSERV.UARK.EDU >cc > >Subject >Re: Cannot TELNET to Level 2 > > > > > > > >Yes, that's the problem, George. Here's what the error code E080 means: > >E080 > A LAN connection could not be made, possibly for one of the >following reasons: > > * The cable might not be present. > > * The LAN might not be functioning. > > * The port might have been disabled. > >Which one of these might apply to your situation....? > >DJ > >On 10/12/2010 04:47 PM, George Henke/NYLIC wrote: >> Also getting the following error on TCPIP startup. >> >> Perhaps it is the problem. >> >> E080 says the OSA has no connectionto the LAN. >> >> >> 17:43:34 DTCQDI001I QDIO device OSA9012 device number 9012: >> 17:43:34 DTCQDI007I Enabled for QDIO data transfers >> 17:43:34 DTCOSD223E OSD device OSA9012: Return code E080 from STRTLAN >for >> IPv4 >> 17:43:34 DTCOSD305I Waiting for adapter-initiated Start Lan >> >> >> ----- Forwarded by George Henke/NYLIC on 10/12/2010 05:44 PM ----- >> >> George Henke/NYLIC >> 10/12/2010 05:17 PM >> >> To >> IBMVM@LISTSERV.UARK.EDU >> cc >> >> Subject >> Cannot TELNET to Level 2 >> >> >> >> >> >> Level 2 OSA cannot find a Gateway router: >> >> NETSTAT GATE >> VM TCP/IP Netstat Level 540 TCP/IP Server Name: TCPIP >> >> Path MTU Discovery Aging Interval: 10 Minutes >> >> Known IPv4 gateways: None >> >> Known IPv6 gateways: None >> >> Ready; T=0.01/0.01 16:35:44 >> >> Level 1 has no problem finding the Gateway router: >> >> VM TCP/IP Netstat Level 540 TCP/IP Server Name: TCPIP >> >> Path MTU Discovery Aging Interval: 10 Minutes >> >> Known IPv4 gateways: >> >> Subnet Address Subnet Mask FirstHop Flgs PktSz Metric Lin k > >> -------------- ----------- -------- ---- ----- ------ >------ >> >> Default <none> 172.28.3.129 UG 1492 7 OSA9000L NK > >> 172.28.3.128 255.255.255.192 <direct> U 1492 1 OSA9000L NK > >> 172.28.3.192 255.255.255.192 <direct> U 1492 1 OSA9100L NK > >> >> Known IPv6 gateways: None >> >> Ready; T=0.01/0.01 16:39:25 >> >> >> Except for the home and OSA IP addresses the PROFILE TCPIP is exactly >the >> same. >> >> Except for HOSTNAME TCPIP DATA is the same. >> >> There is no default GATEWAY defined in PROFILE TCPIP for L1 or L2. >> >> In Level 2, I attach the OSA addresses in the TCPIP PROFILE EXEC: >> >> ATT 9012 TCPIP 9012 >> ATT 9013 TCPIP 9013 >> ATT 9014 TCPIP 9014 >> >> And they come up fine: >> >> q osa >> 17:06:17 OSA 9012 ATTACHED TO TCPIP 9012 DEVTYPE OSA CHPID >D2 >> OSD >> 17:06:17 OSA 9013 ATTACHED TO TCPIP 9013 DEVTYPE OSA CHPID >D2 >> OSD >> 17:06:17 OSA 9014 ATTACHED TO TCPIP 9014 DEVTYPE OSA CHPID >D2 >> OSD >> Ready; T=0.01/0.01 17:06:17 >> >> But I cannot TELNET to the Level 2 home address: 10.13.13.26. >> >> TRACERTE indicates it find the gateway router. >> >> MPROUTE is the same for both except for the IP addresses. >> >> How do I advertise TCPIP L2 to the Gateway, RIP routers, or point it t o >a >> Gateway Router? >> >> Sorry for all this data, but here are the relevant details of my confi g >> for Level 1 and Level 2: >> >> >> Level 1 Parms: >> >> 10.13.13.18/30 VIRLNK1 >> 172.28.3.131 OSA9000LNK >> 172.28.3.195 OSA9100LNK >> 172.28.3.31 OSA9210LNK >> 10.13.13.162 OSA9108LNK >> >> DEVICE VIRDEV1 VIRTUAL 0 >> LINK VIRLNK1 VIRTUAL 0 VIRDEV1 >> DEVICE VIRDEV2 VIRTUAL 0 >> LINK VIRLNK2 VIRTUAL 0 VIRDEV2 >> DEVICE OSA9000 OSD 9000 PORTNAME OSA9000 NONROUTER AUTORESTART >> LINK OSA9000LNK QDIOETHERNET OSA9000 >> DEVICE OSA9100 OSD 9100 PORTNAME OSA2 NONROUTER AUTORESTART >> LINK OSA9100LNK QDIOETHERNET OSA9100 >> DEVICE OSA9108 OSD 9108 PORTNAME OSALAN NONROUTER AUTORESTART >> LINK OSA9108LNK QDIOETHERNET OSA9108 MTU 1492 >> DEVICE OSA9210 OSD 9210 PORTNAME OSA9020 PRIROUTER AUTORESTART >> LINK OSA9210LNK QDIOETHERNET OSA9210 >> DEVICE OSA9313 OSD 9313 PORTNAME OSA9060 PRIROUTER AUTORESTART >> LINK OSA9313LNK QDIOETHERNET OSA9313 >> >> INTERFACE NAME=VIRLNK1 >> IP_ADDRESS=10.13.13.18 >> SUBNET_MASK=255.255.255.252 >> MTU=1492; >> INTERFACE NAME=VIRLNK2 >> IP_ADDRESS=10.13.13.22 >> SUBNET_MASK=255.255.255.252 >> MTU=1492; >> RIP_INTERFACE NAME=OSA9000LNK >> IP_ADDRESS=172.28.3.131 >> SUBNET_MASK=255.255.255.192 >> RIPV2=YES >> RECEIVE_RIP=YES >> RECEIVE_DYNAMIC_NETS=YES >> RECEIVE_DYNAMIC_SUBNETS=YES >> RECEIVE_DYNAMIC_HOSTS=YES >> MTU=1492; >> RIP_INTERFACE NAME=OSA9100LNK >> IP_ADDRESS=172.28.3.195 >> SUBNET_MASK=255.255.255.192 >> RIPV2=YES >> RECEIVE_RIP=YES >> RECEIVE_DYNAMIC_NETS=YES >> RECEIVE_DYNAMIC_SUBNETS=YES >> RECEIVE_DYNAMIC_HOSTS=YES >> MTU=1492; >> RIP_INTERFACE NAME=OSA9104LNK >> IP_ADDRESS=10.13.13.161/27 >> RIPV2=YES >> RECEIVE_RIP=YES >> RECEIVE_DYNAMIC_NETS=YES >> RECEIVE_DYNAMIC_SUBNETS=YES >> RECEIVE_DYNAMIC_HOSTS=YES >> MTU=1492; >> RIP_INTERFACE NAME=OSA9210LNK >> IP_ADDRESS=172.28.3.31 >> SUBNET_MASK=255.255.255.192 >> RIPV2=YES >> RECEIVE_RIP=YES >> RECEIVE_DYNAMIC_NETS=YES >> RECEIVE_DYNAMIC_SUBNETS=YES >> RECEIVE_DYNAMIC_HOSTS=YES >> MTU=1492; >> RIP_INTERFACE NAME=OSA9313LNK >> IP_ADDRESS=10.13.13.162 >> SUBNET_MASK=255.255.255.224 >> RIPV2=YES >> RECEIVE_RIP=YES >> RECEIVE_DYNAMIC_NETS=YES >> RECEIVE_DYNAMIC_SUBNETS=YES >> RECEIVE_DYNAMIC_HOSTS=YES >> MTU=1492; >> >> Level 2 Parms: >> >> 10.13.13.26 VIRLNK1 >> 172.28.3.140 OSA9012LNK >> >> DEVICE VIRDEV1 VIRTUAL 0 >> LINK VIRLNK1 VIRTUAL 0 VIRDEV1 >> DEVICE OSA9012 OSD 9012 PORTNAME OSA1 NONROUTER AUTORESTART >> LINK OSA9012LNK QDIOETHERNET OSA9012 >> >> INTERFACE NAME=VIRLNK1 >> IP_ADDRESS=10.13.13.26 >> SUBNET_MASK=255.255.255.252 >> MTU=1492; >> RIP_INTERFACE NAME=OSA9012LNK >> IP_ADDRESS=172.28.3.140 >> SUBNET_MASK=255.255.255.192 >> RIPV2=YES >> MTU=1492; >> >> > >-- >Dave Jones >V/Soft Software >www.vsoft-software.com >Houston, TX >281.578.7544 > >
