- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: can't connect to NW
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
Forums
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
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
01-24-2005 04:26 PM
01-24-2005 04:26 PM
can't connect to NW
we have a problem.we have 2 server L class that can't to network.if we delete the degault gateway with run "route delete default 10.x.x.x" and run commnad "/sbin/init.d/net stop && /sbin/init.d/net start", we can connect to network and can ping to gateway.but it can't connect to network again after a few minutes.
please,give me solutions!!!
thx,
piyut
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2005 04:33 PM
01-24-2005 04:33 PM
Re: can't connect to NW
Looks like you have duplicate ip addresses in your environment. Do you have nettl running ?
nettl -status ?
If not start it with
nettl -start
your commands again then check to see whats happening
netfmt -t 30 /var/adm/nettl.LOG00 > /tmp/netfmt.out
HTH
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2005 04:39 PM
01-24-2005 04:39 PM
Re: can't connect to NW
seems like duplicate ipaddress in the network.
we were having same problem.it was due to the host router/switch ipaddress was given to another host in the network.
regds,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2005 04:56 PM
01-24-2005 04:56 PM
Re: can't connect to NW
Looks like you have duplicate IP address, check for the same
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2005 05:47 PM
01-24-2005 05:47 PM
Re: can't connect to NW
# nettl -status
Logging Information:
Log Filename: /var/adm/nettl.LOG0*
Max Log file size(Kbytes): 1000 Console Logging: On
User's ID: 0 Buffer Size: 8192
Messages Dropped: 0 Messages Queued: 0
Subsystem Name: Log Class:
NS_LS_LOGGING ERROR DISASTER
NS_LS_NFT ERROR DISASTER
NS_LS_LOOPBACK ERROR DISASTER
NS_LS_NI ERROR DISASTER
NS_LS_IPC ERROR DISASTER
NS_LS_SOCKREGD ERROR DISASTER
NS_LS_TCP ERROR DISASTER
NS_LS_PXP ERROR DISASTER
NS_LS_UDP ERROR DISASTER
NS_LS_IP ERROR DISASTER
NS_LS_PROBE ERROR DISASTER
NS_LS_DRIVER ERROR DISASTER
NS_LS_RLBD ERROR DISASTER
NS_LS_BUFS ERROR DISASTER
NS_LS_CASE21 ERROR DISASTER
NS_LS_ROUTER21 ERROR DISASTER
NS_LS_NFS ERROR DISASTER
NS_LS_NETISR ERROR DISASTER
NS_LS_NSE ERROR DISASTER
NS_LS_STRLOG ERROR DISASTER
NS_LS_TIRDWR ERROR DISASTER
NS_LS_TIMOD ERROR DISASTER
NS_LS_ICMP ERROR DISASTER
FILTER ERROR DISASTER
NAME ERROR DISASTER
NS_LS_IGMP ERROR DISASTER
FC ERROR DISASTER
FORMATTER ERROR DISASTER
STREAMS ERROR DISASTER
BASE100 ERROR DISASTER
SPP100BT ERROR DISASTER
Tracing Information:
Trace Filename:
Max Trace file size(Kbytes): 0
No Subsystems Active
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2005 06:07 PM
01-24-2005 06:07 PM
Re: can't connect to NW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2005 02:07 AM
01-25-2005 02:07 AM
Re: can't connect to NW
ndd -get /dev/ip ip_ire_gw_probe
if that comes back 1 then you need to turn it off with:
ndd -set /dev/ip ip_ire_gw_probe 0
Then remove and re-add your default gateway. (The mechanism that re-enables the gateways is turned off too so you need to wake it up.)
To make it stick during a reboot you need to edit /etc/r.config.d/nddconf to add:
TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe
NDD_VALUE[0]=0
Use the next higher integer in the brackets if you already have entries in nddconf.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2005 01:06 PM
01-25-2005 01:06 PM
Re: can't connect to NW
the gateway does not respond for ping command because of closed.than i open so gateway can respond for ping command.
thank you.