Re: Any HMC Gurus out there?
Doug: Thanks. I think you have the answer. I logged onto the HMC and viewed the console log. I was able to see regular messages indicating a time synchronization between the HMC and the z9 on a regular basis up to the time when someone logged on locally and fooled around with the IP addresses. I queried the client and found that they were messing around at that time and also fooled with the cabling. They will go and check things tomorrow morning and then we may be back on the air. I'll let you know. Mike On 10/08/2011 08:42 PM, Doug Fuerst wrote: Hardware Management Console and support element wiring options A local Hardware Management Console must be connected to its support Elements using Local Area Network (LAN) wiring. The Hardware Management Console and the support Elements both come with Dual Ethernet LAN adapters. The communication protocol (TCP/IP) used in Support Element to Hardware Management Console communication is defined for both adapters in the support elements. v Ethernet only - one path wiring scenario This Ethernet only wiring scenario is intended for enterprises who currently have Ethernet installed and who do not want Token Ring wiring introduced into their environment. This wiring scenario requires that a second Ethernet be specified with the support Elements. The Ethernet features assume the use of 10/100 Mbit Ethernet facilities, requiring the use of CAT-5 Ethernet cabling. Since the Support Element Ethernet only feature includes two Ethernet adapters, there will be two Ethernet connections available. For this scenario, only the Ethernet cable connected to the Ethernet in the first (top) PCMCIA slot of the support Elements will be used. The TCP/IP protocol used in Support Element to Hardware Management Console communication is defined for both adapters in the PCMCIA slots of the support Elements. It will be necessary to connect the top Ethernet adapter cable to a customer supplied local hub capable of 10/100 Mbit Ethernet rates. It will be necessary to connect the Ethernet from the Hardware Management Console to either the same hub as the support Elements, or to a hub that connects to the Support Element hub. Chapter 6. Hardware Management Console and support element communications 55 GC28-6875-03 Doug -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Roger Lowe Sent: Saturday, October 08, 2011 7:15 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Any HMC Gurus out there? Mike, Is there a Firewall in place? When you VPN in, is your IP address being NAT'd to the IP address (sub net) that the z9 network is on? Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Any HMC Gurus out there?
I am looking for some help with an HMC problem on a z9 system. I am helping install a z9 at a client who is about two hours away. I had gone to the client's previously and had set up the HMC and was creating an IOCDS for it, so the HMC and SEs were communicating. I set up a userid for myself with most powers so I could access the HMC remotely. The client's people subsequently went about configuring the network to allow me to access the HMC through a VPN. That works, but now the communication between the HMC and the z9 doesn't work. The z9's name (serial #) still shows under defined CPCs, but the icon is greyed out and when any attempt is made to access it (like single object operations), it indicates that the CPC is not communicating. I have tried to PING the SEs from the HMC (not working - times out). I have tried to PING the HMC from the primary SE (also times out). The HMC has one IP address that should correctly set it on the LAN with the SEs - 192.168.4.100 - the other IP address is the one I access the HMC from the Net. There must be something that I am missing, but I can't think of what it might be. Anyone have any suggestions? Mike Myers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Any HMC Gurus out there?
Check to see if any cabling changed. Doug Fuerst -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mike Myers Sent: Saturday, October 08, 2011 10:49 AM To: IBM-MAIN@bama.ua.edu Subject: Any HMC Gurus out there? I am looking for some help with an HMC problem on a z9 system. I am helping install a z9 at a client who is about two hours away. I had gone to the client's previously and had set up the HMC and was creating an IOCDS for it, so the HMC and SEs were communicating. I set up a userid for myself with most powers so I could access the HMC remotely. The client's people subsequently went about configuring the network to allow me to access the HMC through a VPN. That works, but now the communication between the HMC and the z9 doesn't work. The z9's name (serial #) still shows under defined CPCs, but the icon is greyed out and when any attempt is made to access it (like single object operations), it indicates that the CPC is not communicating. I have tried to PING the SEs from the HMC (not working - times out). I have tried to PING the HMC from the primary SE (also times out). The HMC has one IP address that should correctly set it on the LAN with the SEs - 192.168.4.100 - the other IP address is the one I access the HMC from the Net. There must be something that I am missing, but I can't think of what it might be. Anyone have any suggestions? Mike Myers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Any HMC Gurus out there?
My 2 cents here. Probably the machine is in service mode from se/hmc or machine is still allocated to whatever action client's people were taking. Rajesh -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Doug Fuerst Sent: Saturday, October 08, 2011 5:30 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Any HMC Gurus out there? Check to see if any cabling changed. Doug Fuerst -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mike Myers Sent: Saturday, October 08, 2011 10:49 AM To: IBM-MAIN@bama.ua.edu Subject: Any HMC Gurus out there? I am looking for some help with an HMC problem on a z9 system. I am helping install a z9 at a client who is about two hours away. I had gone to the client's previously and had set up the HMC and was creating an IOCDS for it, so the HMC and SEs were communicating. I set up a userid for myself with most powers so I could access the HMC remotely. The client's people subsequently went about configuring the network to allow me to access the HMC through a VPN. That works, but now the communication between the HMC and the z9 doesn't work. The z9's name (serial #) still shows under defined CPCs, but the icon is greyed out and when any attempt is made to access it (like single object operations), it indicates that the CPC is not communicating. I have tried to PING the SEs from the HMC (not working - times out). I have tried to PING the HMC from the primary SE (also times out). The HMC has one IP address that should correctly set it on the LAN with the SEs - 192.168.4.100 - the other IP address is the one I access the HMC from the Net. There must be something that I am missing, but I can't think of what it might be. Anyone have any suggestions? Mike Myers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Please visit our website at http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html for important disclosures and information about our e-mail policies. For your protection, please do not transmit orders or instructions by e-mail or include account numbers, Social Security numbers, credit card numbers, passwords, or other personal information. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Any HMC Gurus out there?
Mike, Is there a Firewall in place? When you VPN in, is your IP address being NAT'd to the IP address (sub net) that the z9 network is on? Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Any HMC Gurus out there?
Hardware Management Console and support element wiring options A local Hardware Management Console must be connected to its support Elements using Local Area Network (LAN) wiring. The Hardware Management Console and the support Elements both come with Dual Ethernet LAN adapters. The communication protocol (TCP/IP) used in Support Element to Hardware Management Console communication is defined for both adapters in the support elements. v Ethernet only - one path wiring scenario This Ethernet only wiring scenario is intended for enterprises who currently have Ethernet installed and who do not want Token Ring wiring introduced into their environment. This wiring scenario requires that a second Ethernet be specified with the support Elements. The Ethernet features assume the use of 10/100 Mbit Ethernet facilities, requiring the use of CAT-5 Ethernet cabling. Since the Support Element Ethernet only feature includes two Ethernet adapters, there will be two Ethernet connections available. For this scenario, only the Ethernet cable connected to the Ethernet in the first (top) PCMCIA slot of the support Elements will be used. The TCP/IP protocol used in Support Element to Hardware Management Console communication is defined for both adapters in the PCMCIA slots of the support Elements. It will be necessary to connect the top Ethernet adapter cable to a customer supplied local hub capable of 10/100 Mbit Ethernet rates. It will be necessary to connect the Ethernet from the Hardware Management Console to either the same hub as the support Elements, or to a hub that connects to the Support Element hub. Chapter 6. Hardware Management Console and support element communications 55 GC28-6875-03 Doug -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Roger Lowe Sent: Saturday, October 08, 2011 7:15 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Any HMC Gurus out there? Mike, Is there a Firewall in place? When you VPN in, is your IP address being NAT'd to the IP address (sub net) that the z9 network is on? Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
