HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: NIC not connected was the most problem
Operating System - OpenVMS
1832585
Members
3396
Online
110043
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-27-2004 07:04 PM
04-27-2004 07:04 PM
NIC not connected was the most problem
@All
The most problem was that the Interfaces, that i tried to configure in the Failoverset wasn't connected to the LAN.
And it seems that they will not be added, if they aren't connected.
I tried it with the connected EWA0 (a unsupported DE500) and it appears immediately after reboot!!!
So i'm continuing to configure it.
Thx at all for help.
Bye, Kuddel
The most problem was that the Interfaces, that i tried to configure in the Failoverset wasn't connected to the LAN.
And it seems that they will not be added, if they aren't connected.
I tried it with the connected EWA0 (a unsupported DE500) and it appears immediately after reboot!!!
So i'm continuing to configure it.
Thx at all for help.
Bye, Kuddel
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2004 02:55 AM
04-29-2004 02:55 AM
Re: NIC not connected was the most problem
I'm glad you got it working.
And I know it's far too easy to click on the "New Message" button in ITRC Forums when you really meant the "Reply" button. :-)
And I know it's far too easy to click on the "New Message" button in ITRC Forums when you really meant the "Reply" button. :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2004 03:30 AM
04-29-2004 03:30 AM
Re: NIC not connected was the most problem
Ah, that is good to know - thanks for the info. Sometime it is an easy cause - 'did you plug it in?'.
I guess it is a good idea to implement a check of the failover setup at least after system boot. Otherwise a single failure gets unnoticed due to redundancy.
Does anybody know if it is possible to get at this information via $GETDVI? I have taken a short look at the arguments of F$GETDVI, but I did not see anything useful.
I guess it is a good idea to implement a check of the failover setup at least after system boot. Otherwise a single failure gets unnoticed due to redundancy.
Does anybody know if it is possible to get at this information via $GETDVI? I have taken a short look at the arguments of F$GETDVI, but I did not see anything useful.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2004 08:50 PM
10-06-2004 08:50 PM
Re: NIC not connected was the most problem
closed
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