- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve Stack
Switches, Hubs, and Modems
1752574
Members
5003
Online
108788
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
12-01-2010 04:35 AM
12-01-2010 04:35 AM
Re: Procurve Stack
Sorry,
but the documentation mentionned the following point:
"The Commander is the only device in the stack that must have an IP address if you want to access it through the network."
And this one:
"Members (or Candidates) do not require an IP address, but they can have one."
So if i understand correctly, i have one commander, whit four member, each switch has his own ip, but the admnistration is doing by the ip of the commander?
Am i right?
but the documentation mentionned the following point:
"The Commander is the only device in the stack that must have an IP address if you want to access it through the network."
And this one:
"Members (or Candidates) do not require an IP address, but they can have one."
So if i understand correctly, i have one commander, whit four member, each switch has his own ip, but the admnistration is doing by the ip of the commander?
Am i right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2010 06:44 AM
12-01-2010 06:44 AM
Re: Procurve Stack
>>> if you want to access it through the network."<<<
It's exactly as it says (but no more).
- TO the stack you only need one ip-adress to manage all stack members.
- FROM the stack member to the outside, above does not count and each member needs it's own address (ntp, sylog).
If a stack member does not have it's own address then, from the stack commander you can enable /disable ports, create vlans, create port trunks etc etc.
You can manually set time on the stack member from the commander interface.
But a stack member does not use the commander for ntp queries!
It does this all by itself and hence needs an ip-adresss (in a tcp/ip environment).
It's exactly as it says (but no more).
- TO the stack you only need one ip-adress to manage all stack members.
- FROM the stack member to the outside, above does not count and each member needs it's own address (ntp, sylog).
If a stack member does not have it's own address then, from the stack commander you can enable /disable ports, create vlans, create port trunks etc etc.
You can manually set time on the stack member from the commander interface.
But a stack member does not use the commander for ntp queries!
It does this all by itself and hence needs an ip-adresss (in a tcp/ip environment).
- « Previous
-
- 1
- 2
- Next »
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