|
Comm trace, ran on the old server GDISYS01, didn't seem to show any hits between the two animals. In fact when I ran the report I saw only one hit for 10.10.1.237 and it was: *...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2 Record Data Record Controller Destination Source Frame Number Number Poll/ Number S/R Length Timer Name MAC Address MAC Address Format Command Sent Received Final ------ --- ------ --------------- ---------- ------------ ------------ ------ ------- ------ -------- ----- 12 R 46 14:14:03.955439 FFFFFFFFFFFF 020000E00800 ETHV2 Type: 0806 Frame Type : ARP Src Addr: 10.10.1.141 Dest Addr: 10.10.1.237 Operation: REQU ARP Header : 0001080006040001020000E008000A0A018D0000000000000A0A01ED Data . . . . . : 0000000000000000 0000000000000000 0000 *.................. But that's the wrong src address. 10.10.1.141 should be for Internet Host Address Name 10.10.1.130 GDISYS01.DEKKO.COM GDISYS01 10.10.1.141 INTERNOTES 10.10.1.237 INTERNOTES02 INTERNOTES02.dekko-1 INTERNOTES02.DEKKO.COM 10.10.1.141, or INTERNOTES, is a Domino partition on an iseries that is totally independent of the other two iSeries being used in this problem. INTERNOTES and INTERNOTES02 are in a cluster. Frankly I don't understand why traffic between 10.10.1.141 and 10.10.1.237 would even show on this comm trace. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.