- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual connect Community string
BladeSystem - General
1752293
Members
4648
Online
108786
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
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-2010 04:31 AM
тАО05-17-2010 04:31 AM
Virtual connect Community string
When configuring the SNMP Read community string in the virtual connect I'm able to use small and capital letters. When configuring the TRAP destination Community String I'm not able to use capital letters (not possible to click "OK" in flash window.
This causes some problem with the monitoring because all servers use a capital community string. Is it possible this is a bug?
This causes some problem with the monitoring because all servers use a capital community string. Is it possible this is a bug?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 07:25 AM
тАО05-17-2010 07:25 AM
Re: Virtual connect Community string
what version of VC firmware?
seems to work OK in 2.32
seems to work OK in 2.32
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 11:03 PM
тАО05-17-2010 11:03 PM
Re: Virtual connect Community string
I'm currently using version HP VC Flex-10 Enet Module 2.31.
I will try to upgrade and see if the problem is solved.
I will try to upgrade and see if the problem is solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 11:31 PM
тАО05-17-2010 11:31 PM
Re: Virtual connect Community string
Bug is fixed in version 2.32:
From the HP site a found the following problems fixed in 2.32:
├в ┬в Resolved an issue when un-initialized server(s) was installed and continuously attempted to PXE boot. Each server was generating multiple Ethernet port state events which could result in sluggish VCM GUI responses.
├в ┬в Resolved an issue for VCM GUI which would not allow using upper case letters to define SNMP Community Strings.
├в ┬в Resolved an issue where user├в s GUI interface would appear not responsive during the Checkpoint Operation time period, which can be up to 40 seconds. Checkpoint Operation is initiated whenever a profile configuration is being updated.
├в ┬в Resolved an issue where RDP operations would fail when VC unexpectedly updated UUID and SN to an internal data structure. This update occurs whenever a server POST COMPLETE event is detected.
├в ┬в Resolved an issue where VC CLI SHOW operations would occur in minutes instead of seconds with large network configurations.
The second fixed problem is the one I had.
I thought I was using the latest version.
Case closed :-)
From the HP site a found the following problems fixed in 2.32:
├в ┬в Resolved an issue when un-initialized server(s) was installed and continuously attempted to PXE boot. Each server was generating multiple Ethernet port state events which could result in sluggish VCM GUI responses.
├в ┬в Resolved an issue for VCM GUI which would not allow using upper case letters to define SNMP Community Strings.
├в ┬в Resolved an issue where user├в s GUI interface would appear not responsive during the Checkpoint Operation time period, which can be up to 40 seconds. Checkpoint Operation is initiated whenever a profile configuration is being updated.
├в ┬в Resolved an issue where RDP operations would fail when VC unexpectedly updated UUID and SN to an internal data structure. This update occurs whenever a server POST COMPLETE event is detected.
├в ┬в Resolved an issue where VC CLI SHOW operations would occur in minutes instead of seconds with large network configurations.
The second fixed problem is the one I had.
I thought I was using the latest version.
Case closed :-)
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