HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS server or router up and down?
Operating System - HP-UX
1834675
Members
2853
Online
110069
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
04-16-2003 06:11 PM
04-16-2003 06:11 PM
NIS server or router up and down?
hi all,
Currently my NIS server or my router up and down. The NIS(HPUX11.0) server connect through the BAY router through ATM card.
Every half an hour, I can't ping the ATM card and the router for about 2,3 minutes, then it recover itself. At the same time, I also experience it when I ping the machine in different subnet.
I got some error from the ATM card, it saids"(ELA) Connection to the ELAN failed during LECS Connect Phase". I also get some error message from the router, there are some checksum failure.
My whole network just up and down every half an hour.
Is there anyone experience this or anyone can tell me how to identify whether it is the router's fault.
Thanks a lot
Currently my NIS server or my router up and down. The NIS(HPUX11.0) server connect through the BAY router through ATM card.
Every half an hour, I can't ping the ATM card and the router for about 2,3 minutes, then it recover itself. At the same time, I also experience it when I ping the machine in different subnet.
I got some error from the ATM card, it saids"(ELA) Connection to the ELAN failed during LECS Connect Phase". I also get some error message from the router, there are some checksum failure.
My whole network just up and down every half an hour.
Is there anyone experience this or anyone can tell me how to identify whether it is the router's fault.
Thanks a lot
wang & wang
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2003 06:25 AM
04-17-2003 06:25 AM
Re: NIS server or router up and down?
I'm not sure I understand your network.
I assume you have something like this and that every thing used to work and that you have not made any changes recently:
A -- B -- C -- D
Where A is a host attached to the router B which is attached to C (the NIS Server)via an ATM circuit. D is a host on the different subnet you speak about which connects to the NIS server
If you are at A and you can't ping the router's interface on the AB LAN then the router is probably rebooting which is usually a software error but could be a hardware problem. The problem with not being able to ping the CD interface of the NIS Server could be explained by the route to CD from A going through the router.
If you are at D when you try to ping the router and you can't ping either of the interfaces on C then C has rebooted or has some other problem. I would look in syslog for problems. Could also be a duplex mismatch to the switch and the switch periodically resetting the bad port.
Finally you report checksum errors and LECS connection problems which could be a problem with the ATM link between the B and C. Replace the cable if that's all there is between them. IF you have a telco in between then that could be the source of your errors and I would call in a trouble and have the line tested.
I would think the router would log any problems with the circuit and would also tell you if it had rebooted. Ciscos do but I don't know much about Bays other than that you use a fancy GUI to talk to them.
Ron
I assume you have something like this and that every thing used to work and that you have not made any changes recently:
A -- B -- C -- D
Where A is a host attached to the router B which is attached to C (the NIS Server)via an ATM circuit. D is a host on the different subnet you speak about which connects to the NIS server
If you are at A and you can't ping the router's interface on the AB LAN then the router is probably rebooting which is usually a software error but could be a hardware problem. The problem with not being able to ping the CD interface of the NIS Server could be explained by the route to CD from A going through the router.
If you are at D when you try to ping the router and you can't ping either of the interfaces on C then C has rebooted or has some other problem. I would look in syslog for problems. Could also be a duplex mismatch to the switch and the switch periodically resetting the bad port.
Finally you report checksum errors and LECS connection problems which could be a problem with the ATM link between the B and C. Replace the cable if that's all there is between them. IF you have a telco in between then that could be the source of your errors and I would call in a trouble and have the line tested.
I would think the router would log any problems with the circuit and would also tell you if it had rebooted. Ciscos do but I don't know much about Bays other than that you use a fancy GUI to talk to them.
Ron
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