- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Not Linked | Loop Detected
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
Discussions
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
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
12-04-2017 01:19 AM
12-04-2017 01:19 AM
Not Linked | Loop Detected
Guys !
Need help on this particular issue.
Randomly (have happened twice already in last week ) we see the following error message -
"Not lInked / Loop Detected "
The above is shown on Virtual Connect GUI, resulting in all NIC's at ESX showing disconnected.
We fixed this by resetting the server port loop option from the Virtual Connect GUI.
As per VMWARE support case , ESXi host would not create any loop for the HP Virtual Connect uplinks - so it needs to be checked with HP and probably get more details (Mac address, NIC) where the loop was detected.
Can someone point out where to start this troubleshooting ?
As I read somewhere - it is by design that Flex10D would disconnect/disable downlink ports to servers if it finds a loop in its uplink connections ? Am I getting this right ? which means that there is a loop getting generated on TOR/Cisco switches propagating down here ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 03:36 AM
01-03-2018 03:36 AM
Re: Not Linked | Loop Detected
Hi Theantz
The recommendation to issue about the loop protect in the virtual connect is associated with the driver and firmware of the network card.
So I recommend you check:
Check if you have latest drivers and firmware of the Network Card
Check if you have latest firmware of the Virtual Connect (use the maximum the 4.50 do not aplly in this momment the most recent release).
Below link of HPE Adivisorys abut this issue:
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c02623029
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00005422en_us
