- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- rp7410 GSP weirdness
HPE 9000 and HPE e3000 Servers
1748282
Members
3966
Online
108761
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2004 11:19 PM
тАО05-17-2004 11:19 PM
It's been a while since I visited the GSP on the rp7410 at our site. In the past it has been used for LAN Console connectivity.
However I recently encountered a snag with it.
The LAN interface pings but does not respond to telnet requests.
However partition manager displays the following error;
"The service processor could not be located. This probably due to a cabinet with a non-unique cabinet ID. Either move the service processor to another cabinet in the complex or modify the cabinet numbering so that each cabinet is unique."
I accessed the MP Console with a tip session from a PowerBook and had a look around.
LC displayed the following;
Current configuration of MP LAN interface
MAC address : 00:30:6e:38:82:a9
IP address :
Hostname :
Subnet mask :
Gateway :
Status :
AutoNegotiate : Enabled
Data Rate : 100 Mb/s
Duplex : Half
Error Count : 3898
Last Error : rx FIFO overflow
Which indicated the former IP/netmask and gateway details lost (though why the interface pings is a mystery).
So I re-entered the parameters, noting that I was being prompted for the very same parameters(?);
Current IP Address is: 10.114.10.144
Do you want to modify it? (Y/[N]) y
Enter new IP Address : 10.114.10.144
New IP Address will be: 10.114.10.144
Please confirm (Y/[N]) y
-> IP Address will be updated.
etc. etc.
-> Parameters have been updated.
Then checked again;
MP:CM> lc
This command modifies the LAN parameters.
Current configuration of MP LAN interface
MAC address : 00:30:6e:38:82:a9
IP address :
Hostname :
Subnet mask :
Gateway :
Status :
AutoNegotiate : Enabled
Data Rate : 100 Mb/s
Duplex : Half
Error Count : 3898
Last Error : rx FIFO overflow
Which looks like they weren't written.
However the IP is detailed for the interface;
MP:CM> if
This command displays information about the network interface.
Do you want a brief or verbose report ? ([B]/V) y
=== Host table ===
hostname inet address aliases
-------- ------------ -------
localhost 127.0.0.1
host 15.11.130.190
gsp0 10.114.10.144
and telnet access is enabled. Still no response though to telnet requests.
Anyone any thoughts as to the cause of the partition manager error and the seeming unwillingness to record LAN details in LC?
Its been a while since I configured GSP, but I'm sure I've run through the basic settings.
Many thanks
Brendan
I
However I recently encountered a snag with it.
The LAN interface pings but does not respond to telnet requests.
However partition manager displays the following error;
"The service processor could not be located. This probably due to a cabinet with a non-unique cabinet ID. Either move the service processor to another cabinet in the complex or modify the cabinet numbering so that each cabinet is unique."
I accessed the MP Console with a tip session from a PowerBook and had a look around.
LC displayed the following;
Current configuration of MP LAN interface
MAC address : 00:30:6e:38:82:a9
IP address :
Hostname :
Subnet mask :
Gateway :
Status :
AutoNegotiate : Enabled
Data Rate : 100 Mb/s
Duplex : Half
Error Count : 3898
Last Error : rx FIFO overflow
Which indicated the former IP/netmask and gateway details lost (though why the interface pings is a mystery).
So I re-entered the parameters, noting that I was being prompted for the very same parameters(?);
Current IP Address is: 10.114.10.144
Do you want to modify it? (Y/[N]) y
Enter new IP Address : 10.114.10.144
New IP Address will be: 10.114.10.144
Please confirm (Y/[N]) y
-> IP Address will be updated.
etc. etc.
-> Parameters have been updated.
Then checked again;
MP:CM> lc
This command modifies the LAN parameters.
Current configuration of MP LAN interface
MAC address : 00:30:6e:38:82:a9
IP address :
Hostname :
Subnet mask :
Gateway :
Status :
AutoNegotiate : Enabled
Data Rate : 100 Mb/s
Duplex : Half
Error Count : 3898
Last Error : rx FIFO overflow
Which looks like they weren't written.
However the IP is detailed for the interface;
MP:CM> if
This command displays information about the network interface.
Do you want a brief or verbose report ? ([B]/V) y
=== Host table ===
hostname inet address aliases
-------- ------------ -------
localhost 127.0.0.1
host 15.11.130.190
gsp0 10.114.10.144
and telnet access is enabled. Still no response though to telnet requests.
Anyone any thoughts as to the cause of the partition manager error and the seeming unwillingness to record LAN details in LC?
Its been a while since I configured GSP, but I'm sure I've run through the basic settings.
Many thanks
Brendan
I
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2004 11:53 PM
тАО05-17-2004 11:53 PM
Solution
Hi Brendan,
That error:
"The service processor could not be located. This probably due to a cabinet with a non-unique cabinet ID. Either move the service processor to another cabinet in the complex or modify the cabinet numbering so that each cabinet is unique."
usually indicates a need for a GSP and PDC. PDC firmware upgrades here -
http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CKEYMAT0602&context=firmware:cpu
and here -
http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CKEYMAT0603&context=firmware:cpu
GSP FW upgrades can be obtained via ftp from HP as I don't see it in the patch list. They have to be installed from a system on the GSP subnet via local ftp.
HTH,
Jeff
That error:
"The service processor could not be located. This probably due to a cabinet with a non-unique cabinet ID. Either move the service processor to another cabinet in the complex or modify the cabinet numbering so that each cabinet is unique."
usually indicates a need for a GSP and PDC. PDC firmware upgrades here -
http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CKEYMAT0602&context=firmware:cpu
and here -
http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CKEYMAT0603&context=firmware:cpu
GSP FW upgrades can be obtained via ftp from HP as I don't see it in the patch list. They have to be installed from a system on the GSP subnet via local ftp.
HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2004 12:23 AM
тАО05-18-2004 12:23 AM
Re: rp7410 GSP weirdness
Thanks Jeff.
I was hoping that a solution wouldn't involve patching, seeing as the server has run uninterrupted for 18 months, but I guess its downtime period is coming soon.
Bren
I was hoping that a solution wouldn't involve patching, seeing as the server has run uninterrupted for 18 months, but I guess its downtime period is coming soon.
Bren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2004 02:09 AM
тАО05-18-2004 02:09 AM
Re: rp7410 GSP weirdness
Hi (again) Brendan,
Yea - what usually happens is that patch levels of utils like Diags & STM start to outpace the FW levels & start causing this type "weirdness".
Besides these updates always containf fixes of some sort or another & cell-based systems are still rather new - so you need to stay up-to-date - certainly no more than 3 revisions old I'd say.
Rgds,
Jeff
Yea - what usually happens is that patch levels of utils like Diags & STM start to outpace the FW levels & start causing this type "weirdness".
Besides these updates always containf fixes of some sort or another & cell-based systems are still rather new - so you need to stay up-to-date - certainly no more than 3 revisions old I'd say.
Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP