- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: making Persisten Disaled ports enabled
HPE EVA Storage
1757572
Members
2889
Online
108862
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
тАО08-04-2009 12:29 AM
тАО08-04-2009 12:29 AM
Re: making Persisten Disaled ports enabled
Thanks,
Further any one could let me know why i get to see
Unknown1 license
Unknown2 license
after licenseshow command issued.
One reason that I know is "Unknown license results when a license from previous OS is no longer valid"
any other reasons and solutions?
Thanks Again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2009 12:46 AM
тАО08-04-2009 12:46 AM
Re: making Persisten Disaled ports enabled
License Unknown is of 6.x firmware which includes by default the previous lic's .( mentioned now as unknown).
no problem for that.
no problem for that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2009 03:51 AM
тАО08-10-2009 03:51 AM
Re: making Persisten Disaled ports enabled
Hi All,
To further add....we are using c7000 Blade Chassis Brocade FC Switch ( 4 in number)
now i have to help onsite guy locate the FC Mezz card to reset it on.
My guesses locating the card.
1.Its Blade Chassis that has all 4 switches (and may be other Linux servers) -
2.I would beacon all the switches..and ask the onsite guy to verify the connectivity.
Any suggestions to improve further.?
Many thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2009 05:47 AM
тАО08-10-2009 05:47 AM
Re: making Persisten Disaled ports enabled
For the c-class SAN switches there are a minimum of 3 things required to allow a blade to log into the internal SAN switch port:
1. The blade must be powered on (which means there is a blade in the given bay)
2. The blade must have a FC HBA installed in the correct mezzanine slot (dependent on SAN switch interconnect bay location).
3. A local OS must be installed with the correct QLogic or Emulex driver or the FC HBA card is configured for a BfS (Boot from SAN).
If any of the above is not correct, the given internal SAN switch port will remain permanently disabled - you cannot manually enable it.
Getting a blade to successfully log into an internal interconnect SAN switch port is not dependent on SAN switch zoning.
1. The blade must be powered on (which means there is a blade in the given bay)
2. The blade must have a FC HBA installed in the correct mezzanine slot (dependent on SAN switch interconnect bay location).
3. A local OS must be installed with the correct QLogic or Emulex driver or the FC HBA card is configured for a BfS (Boot from SAN).
If any of the above is not correct, the given internal SAN switch port will remain permanently disabled - you cannot manually enable it.
Getting a blade to successfully log into an internal interconnect SAN switch port is not dependent on SAN switch zoning.
- « 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