- Community Home
- >
- Software
- >
- Software - General
- >
- The Network Should Know Before We Do
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
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
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
Sunday
Sunday
The Network Should Know Before We Do
A chess master can see moves before they appear on the board.
An architect sees the building before it is built.
A musician hears the melody before the audience.
A chess master sees the move before it is played.
What if our networks could do the same?
Today, network operations are often reactive:
Something breaks → User complains → Ticket opens → Engineer investigates → Engineer fixes it.
But the network often had signals long before the ticket arrived.
A port started behaving differently.
Authentication began failing.
A configuration changed.
A loop started forming.
DHCP stopped responding as expected.
User experience began degrading.
The signals were there.
The network just needed to connect the dots.
That is the promise of self-driving networking.Instead of simply telling us:
“Something is wrong.”
Imagine the network saying:
“Something is changing.”
“Here is why.”
“Here is who could be affected.”
“Here is the safest action.”
“I took the action within your policy.”
“And I verified that it worked.”
That's the journey:
Observe → Understand → Predict → Act → Verify → Learn
Self-driving doesn't mean removing network engineers.
It means removing repetitive work from network engineers.
Less time searching logs.
Less time connecting symptoms.
Less time solving the same problems again and again.
More time designing, securing and improving the network.
The real goal isn't more AI. It's fewer problems.The best self-driving network may be the one users barely notice.
Because the problem was understood before they reported it.
The risk was contained before it spread.
And eventually, some problems may be corrected before they become incidents.
A chef tastes ahead.
An architect sees ahead.
A musician hears ahead.
That, to me, is the future of self-driving networking.
Thank you.
Yash Nagaraju,
Director, Technical Marketing Engineering,
Campus and Branch, HPE Networking
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
Tuesday
Re: The Network Should Know Before We Do
Thanks for sharing that informative topic. It is very useful.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]