HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Server Management (Insight Manager 7)
- >
- Re: "The device status has changed..." -- "Ping St...
Server Management (Insight Manager 7)
1833750
Members
2456
Online
110063
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
Forums
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
11-19-2003 11:02 AM
11-19-2003 11:02 AM
We've got 4 identically configured Proliant ML350's, all of which are acting as file servers, all of which have Insight Manager and only one is reporting these errors.
So just for testing, I pinged two of them manually:
The one with the error reports:
Packets: Sent = 3575, Received = 3557, Lost = 18 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 14ms, Average = 0ms
The other:
Packets: Sent = 3655, Received = 3655, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
They're both connected to the same switch, with about the same workload. In fact, I believe this box was having this issue before it went live, but only occasionally. It seems to be getting more frequent.
Any ideas would be greatly appreciated.
Justin
So just for testing, I pinged two of them manually:
The one with the error reports:
Packets: Sent = 3575, Received = 3557, Lost = 18 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 14ms, Average = 0ms
The other:
Packets: Sent = 3655, Received = 3655, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
They're both connected to the same switch, with about the same workload. In fact, I believe this box was having this issue before it went live, but only occasionally. It seems to be getting more frequent.
Any ideas would be greatly appreciated.
Justin
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2003 01:43 AM
11-20-2003 01:43 AM
Solution
Justin -
This soudns liek mor elike a network issue. here are a couple things that you can do.
1. check the switch port that the server is connected to and make sure that the speed and duplex settings match. Typically you should set your NICs to 100/full or 1000/full
2. Check your cabling. You may have a bad cable somewhere. You should switch your network cable from the server to the patch panel and so on.
This is not an IM7 issue.
This soudns liek mor elike a network issue. here are a couple things that you can do.
1. check the switch port that the server is connected to and make sure that the speed and duplex settings match. Typically you should set your NICs to 100/full or 1000/full
2. Check your cabling. You may have a bad cable somewhere. You should switch your network cable from the server to the patch panel and so on.
This is not an IM7 issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2003 11:03 AM
11-23-2003 11:03 AM
Re: "The device status has changed..." -- "Ping Status Polling"
As Jadrice has mentioned this is typically Network related.
I've had similar issues with Servers over WANs and some on a slower switch.
You can Set IM to be slight more forgiving of LAN/WAN errors, under Settings, Automatic Discovery, I've upped the retries to 2.
I've had similar issues with Servers over WANs and some on a slower switch.
You can Set IM to be slight more forgiving of LAN/WAN errors, under Settings, Automatic Discovery, I've upped the retries to 2.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP