- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- bc2000 chassis problem
ProLiant Servers - Netservers
1752807
Members
6015
Online
108789
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
тАО11-27-2008 07:45 AM
тАО11-27-2008 07:45 AM
I have a chassis for bc2000 blades and can no longer connect to the web server on it. The IP address no longer pings as well. I have tried rebooting the chassis several times but with no success.
The chassis was originally configured by someone else so I have no documentation or original initial configuration/install documents.
Can anyone help?
The chassis was originally configured by someone else so I have no documentation or original initial configuration/install documents.
Can anyone help?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2008 08:31 PM
тАО11-27-2008 08:31 PM
Solution
Hi Edward,
For documentation, try this URL: http://search.hp.com/query.html?charset=iso-8859-1&lk=1&la=en&nh=10&rf=0&qs=&hpvc=sitewide&uf=0&st=1&qt=%2Bbladesystem+%22integrated+administrator%22+%2Bmanual
As for the best way to check the chassis configuration without affecting it would be to connect to the console (DB9 Serial) port on the rear of the unit with hyperterm, log in and enter "show network" minus the quotes. This will show you how its network interface is configured, its' IP address, and if the web interface is enabled.
For documentation, try this URL: http://search.hp.com/query.html?charset=iso-8859-1&lk=1&la=en&nh=10&rf=0&qs=&hpvc=sitewide&uf=0&st=1&qt=%2Bbladesystem+%22integrated+administrator%22+%2Bmanual
As for the best way to check the chassis configuration without affecting it would be to connect to the console (DB9 Serial) port on the rear of the unit with hyperterm, log in and enter "show network" minus the quotes. This will show you how its network interface is configured, its' IP address, and if the web interface is enabled.
---------------------------------------------
I work for HP, but my posts and replies are my own.
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2008 11:54 AM
тАО12-01-2008 11:54 AM
Re: bc2000 chassis problem
Thanks Dennis, that's what I needed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2009 06:21 PM
тАО03-03-2009 06:21 PM
Re: bc2000 chassis problem
We also had this issue. The chassis (and the integrated switch) would drop their static IP's after about 24hours.
The solution was to disable the Cisco PVST compatability. ONLY do this if you don't use Cisco products. We use 3com 4400's and 5500's and found that the 2 different spanning tree protocols were conflicting.
PVST interoperability.
The PVST Interoperability feature is only intended for use with Cisco based networks running Per VLAN Spanning Tree and no more than three active VLANs on each PC Blade Switch. Optionally, a third VLAN may be added to support Out-of-Band manageability. See section on ???Configuring Out-of-band Management??? below for more information.
When connecting to Cisco based networks that use MST (IEEE 802.1s) or any other switch vendor that follows IEEE Industry Standardized methods for Spanning Tree usage such as ProCurve, Nortel, or 3Com the recommended practice is to disable the PVST Interoperability feature and configure the PC Blade Switch to interoperate with the network using IEEE standards.
Run these commands to disable the PVST Interoperability feature, which will leave the switch operating with pure MSTP or IEEE 802.1s Multi-Instance Spanning Tree. Note: Be sure this is what the network you are connecting to is running or else you will need to run additional commands to configure the switch appropriately.
console> enable
console# configure
console(config)# no spanning-tree mst mstp-rstp
console(config)# spanning-tree mst configuration
console(config-mst)# instance 15 remove vlan 3-4093
console(config-mst)# exit
console(config)# end
Note:
Be sure to save the switches configuration.
This is the only solution that worked for us. Hope it helps you. but please make sure you want to do it first!
The solution was to disable the Cisco PVST compatability. ONLY do this if you don't use Cisco products. We use 3com 4400's and 5500's and found that the 2 different spanning tree protocols were conflicting.
PVST interoperability.
The PVST Interoperability feature is only intended for use with Cisco based networks running Per VLAN Spanning Tree and no more than three active VLANs on each PC Blade Switch. Optionally, a third VLAN may be added to support Out-of-Band manageability. See section on ???Configuring Out-of-band Management??? below for more information.
When connecting to Cisco based networks that use MST (IEEE 802.1s) or any other switch vendor that follows IEEE Industry Standardized methods for Spanning Tree usage such as ProCurve, Nortel, or 3Com the recommended practice is to disable the PVST Interoperability feature and configure the PC Blade Switch to interoperate with the network using IEEE standards.
Run these commands to disable the PVST Interoperability feature, which will leave the switch operating with pure MSTP or IEEE 802.1s Multi-Instance Spanning Tree. Note: Be sure this is what the network you are connecting to is running or else you will need to run additional commands to configure the switch appropriately.
console> enable
console# configure
console(config)# no spanning-tree mst mstp-rstp
console(config)# spanning-tree mst configuration
console(config-mst)# instance 15 remove vlan 3-4093
console(config-mst)# exit
console(config)# end
Note:
Be sure to save the switches configuration.
This is the only solution that worked for us. Hope it helps you. but please make sure you want to do it first!
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