- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve Stack
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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-29-2010 07:38 AM
тАО11-29-2010 07:38 AM
Procurve Stack
i have some procurve 2810, in a "stack" configuration.
However, only the commander has the good time with sntp, and only the commander is using the syslog.
How can i do, to have correct time with sntp on the other member of the stack, and how can i do for the other members use the syslog server?
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2010 12:08 AM
тАО11-30-2010 12:08 AM
Re: Procurve Stack
commander dose not copy any config, only the password
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2010 12:13 AM
тАО11-30-2010 12:13 AM
Re: Procurve Stack
thanks for your response.
All the member of the stack are correctly configured, with the following command:
sntp server xx.xx.xx.xx
timesync sntp
sntp unicast
sntp 300
logging facility local1
logging xx.xx.xx.xx
However, all the logs are local to the switch, they are not deported.
All the member are not to the right time:
CA-A-2# show time
Sun Mar 4 21:22:47 1990
I don't understand, how the memeber of the stakc can have the right time with sntp without an ip, The same question for the log.
Maybe, i'm wrong with my configuration?
Is ther any solution?
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 01:18 AM
тАО12-01-2010 01:18 AM
Re: Procurve Stack
timezone must be taken into account.
so compare time in UTC format at both ends.
You must manually set time within some limits of the time source.
After that ntp can sync, or when still large difference exists, slowly adjust time until synced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 01:30 AM
тАО12-01-2010 01:30 AM
Re: Procurve Stack
See Advanced Trafic Management guide:
All switches in a particular stack must be in the same IP subnet (broadcast domain). A stack cannot cross a router.
that is : each switch DO needs it's own ip-adress to communicate with the commander.
only thing is, for management you do not need to know all separate adresses, but only access the commander switch to manage all stack members.
See Advanced Trafic Management guide:
The Commander switch serves as the in-band entry point for access to the Member switches. For example, the Commander├в s IP address becomes the path to all stack Members and the Commander├в s Manager password controls access to all stack Members.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 01:39 AM
тАО12-01-2010 01:39 AM
Re: Procurve Stack
>>>that is : each switch DO needs it's own ip-adress to communicate with the commander.
<<<
There are other networking protocols that are not tcp/ip-based.
those do not need an ip-adress to communicate, but may need only the MAC-adress to communicate.
>>> All switches in a particular stack must be in the same IP subnet (broadcast domain). A stack cannot cross a router.<<
is neccessary just because a non-tcp/ip protocol is used, so a router cannot route stack-traffic to another subnet/broadcast-domain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 01:53 AM
тАО12-01-2010 01:53 AM
Re: Procurve Stack
Only the commander has an ip in the management vlan.
I do not have to set time manually to each member of the stack. Sntp exist for that.
I want too, that all the member send her logs to my syslog server.
If i understand, i must affect an ip to each switch, int he management vlan, to have sntp access and syslog server access?
But if i read good the documentation, it says, that only the commander must have an ip.
Im' a bit confused.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 02:37 AM
тАО12-01-2010 02:37 AM
Re: Procurve Stack
For opertional task from a member switch, that switch needs its own ip-adres for outgoing connections such as sntp or syslog.
>>> Stacking is an optional feature (enabled in the default configuration) and can easily be disabled. Stacking has no effect on the normal operation of the switch in your network.<<<
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 02:59 AM
тАО12-01-2010 02:59 AM
Re: Procurve Stack
i administer the commander in the management-vlan.
Only the management-vlan can access the syslog and the ntp server.
So, you say that the member of the stack can access my server?
So bad.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 03:48 AM
тАО12-01-2010 03:48 AM
Re: Procurve Stack
Each member switch needs it's own ip-adress in the management vlan.
Then it can access (on ip-level) your syslogserver and ntp server.
It does NOT use the command-switch for this.