If B and C can talk to each other, you probably have everything working inside the box. Do you have a dynamic routing protocol (such as RIP or OSPF) runnning on B, and are the network routers between B and A listening to updates from B?
The machines like A need to know that C can be reached via B. This can be announced via a dynamic routing protocol or by placing static routes in the network between A and B. The best solution is to enable dynamic routing on B and allow it to announce routing information to the network for C. Talk with your networking people and see which they would prefer. -- db David Boyes Sine Nomine Associates > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Alex Leyva > Sent: Thursday, March 13, 2003 11:35 AM > To: [EMAIL PROTECTED] > Subject: OSA mode and lost packets > > > Hi all, im again here with problems... > > i've configured a linux with the OSA-Express dedicated to it, > using the > qdio mode, and its running ok, i've defined a virtual nic to the same > linux, and created a guest lan, then, i brought up another > linux, defined > a virtual nic in the same guest lan, both linux can see each other, > everything its ok, and it look like this: > > host_A----host_B----host_C > > host_A is outside the z800, is a pc, connected at the same > switch that the > OSA. > host_B is the linux that owns the OSA and have a virtual nic > host_C is another linux that have a virtual nic, connected to the same > guest lan that host_B. > > ping from host_B to host_A is ok. > ping from host_B to host_C is ok. > ping from hots_A to host_C is NOT ok. > > i have ip_forward enable, routes are ok, with tcpdump in > host_A i can see > that the echo request came from host_C and that host_A send the echo > reply, in host_B i can see the echo requet going trough the OSA, but i > cant see the echo reply, i have this OAT in the OSA: > > > ************************************************************** > ********** > *** Start of OSA address table for CHPID 00 > *** > > ************************************************************** > ********** > * UA(Dev) Mode Port Entry specific information > Entry Valid > > ************************************************************** > ********** > LP 2 (ZVM ) > 00(2000) MPC N/A HALLOLE (QDIO control) > SIU ALL > 01(2001) MPC N/A HALLOLE (QDIO control) > SIU ALL > 02(2002) MPC 00 No HALLOLE (QDIO data) > SIU ALL > FE80::2:5500:39A:B703 > ::A01:460C > 03(2003) N/A > N/A CSS > 04(2004) N/A > N/A CSS > 05(2005) N/A > N/A CSS > > |...+....1....+....2....+....3....+....4....+....5....+....6.. > ..+....7.. > 06(2006) N/A > N/A CSS > 07(2007) N/A > N/A CSS > 08(2008) N/A > N/A CSS > 09(2009) N/A > N/A CSS > 0A(200A) N/A > N/A CSS > 0B(200B) N/A > N/A CSS > 0C(200C) N/A > N/A CSS > 0D(200D) N/A > N/A CSS > 0E(200E) N/A > N/A CSS > > > i have some questions about this osa: > why the name is HALLOLE? i dont know where it cames from > i dont know why i have two UA's with QDIO control > i dont know why the address appears like > FE80::2:5500:39A:B703::A01:460C, > i think that it must be an ip address right? > > i think that i must define the linux like the PRIMARY, > instead of having > NO, maybe thats the problem with the traffic? > if so, how i can do that? > > thanks > > -- > Alejandro Leyva Rabinovich. > Jefe de la Unidad Departamental de Soporte Ticnico > (Administracisn de Mainframe). > Direccisn General de Informatica. > Secretarma de Finanzas. > Gobierno del Distrito Federal. >
