HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- S340net start route errors
Operating System - HP-UX
1833319
Members
2941
Online
110051
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
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
02-21-2006 12:25 PM
02-21-2006 12:25 PM
S340net start route errors
After a reboot of our server we are receiving errors in rc,log from /sbin/rc2.d/S340net:
ERROR: Failed to add route entry because its interface is not yet initialized. May need to add this route entry with a route commad after the interface is up : netmask: bad value
I can do a manual route add after the server is back up and routes add ok.
What could be causing it not to work on startup ??
ERROR: Failed to add route entry because its interface is not yet initialized. May need to add this route entry with a route commad after the interface is up : netmask: bad value
I can do a manual route add after the server is back up and routes add ok.
What could be causing it not to work on startup ??
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2006 05:29 PM
02-21-2006 05:29 PM
Re: S340net start route errors
Mike
Yes you can add the routes after the system is up with the route add command.
The cause of the problem could be a switch port(bad or not configured correctly)or a cable or maybe a gateway that is not correctly configured.
Was that lan working prior to the reboot or is this a new configuration
Louis
Yes you can add the routes after the system is up with the route add command.
The cause of the problem could be a switch port(bad or not configured correctly)or a cable or maybe a gateway that is not correctly configured.
Was that lan working prior to the reboot or is this a new configuration
Louis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2006 05:38 PM
02-21-2006 05:38 PM
Re: S340net start route errors
Hi,
DO a
#netstat -in
and
#ifconfig
to check if the network interfaces instances are UP and IP config is correct.
latter you kay try to add the statis route manually using
#route add
and confirm the route by
#netstate -r
if this is OK and you are able to reach the other network,then you may add this statis route entry in any rc script so that during every reboot the route is getting added.
Regards,
Siva.
DO a
#netstat -in
and
#ifconfig
to check if the network interfaces instances are UP and IP config is correct.
latter you kay try to add the statis route manually using
#route add
and confirm the route by
#netstate -r
if this is OK and you are able to reach the other network,then you may add this statis route entry in any rc script so that during every reboot the route is getting added.
Regards,
Siva.
Nothing is Impossible !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2006 05:46 PM
02-21-2006 05:46 PM
Re: S340net start route errors
check /etc/rc.config.d/netconf file. I hope there is some problem that route settings there but not the interface informations.
--
Muthu
--
Muthu
Easy to suggest when don't know about the problem!
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