If there's an OAT loaded, perhaps it's not set up to use the device addresses that Billy has coded in his IOCP. That's more of a longshot, but coding the whole device range in the IOCP will certainly determine which devices (if any) come available.

Correct, an OAT is not required, but even when using a non-shared, TCP/IP only configuration on the OSA/2 an OAT was helpful (even suggested) to provide IP address filtering.

On 01/26/2010 12:37 PM, Kris Buelens wrote:
On 9672's, using an OAT was not always required. IIRC it was not needed when using only TCP/IP and not wanting to share it between LPARs. But, given that that MP2000 is "most probably" used in the past, there might be some OAT you can't see and that defines other unitaddresses than your IOCP. You could try to get information from the HMC (did that exist on an MP2000?), or fully reset the OSA. Such things are possible on a z800 I know. Or, you could create an IOCP with unitaddresses 00-FE and see what VM then reports. This won't help if the unknown but loaded OAT defines addresses ofr an LPAR you no longer have....

2010/1/26 Billy Bingham <[email protected] <mailto:[email protected]>>

    I don't have the OSA/SF service machines.It looks like I didn't
    restore all the volumes from the old VM system and I'm also not
    sure if we have all the old volumes.


    Billy



--
Rich Smrcina
Phone: 414-491-6001
http://www.linkedin.com/in/richsmrcina

Catch the WAVV! http://www.wavv.org
WAVV 2010 - Apr 9-13, 2010 Covington, KY

Reply via email to