HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- ethernet id problem
Operating System - Tru64 Unix
1828820
Members
2337
Online
109985
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
12-08-2006 01:31 AM
12-08-2006 01:31 AM
ethernet id problem
dear all
im having a problem with my ethernet ports id on the es45 tru64
the case is i have two cards one quad and one dual which i need their ids to be from ee0 to ee5 but their ids are ee0 ee1 ee5 ee6 ee8 ee9 .... so they are not consecutive which is causing me a big problem
can anybody help?
im having a problem with my ethernet ports id on the es45 tru64
the case is i have two cards one quad and one dual which i need their ids to be from ee0 to ee5 but their ids are ee0 ee1 ee5 ee6 ee8 ee9 .... so they are not consecutive which is causing me a big problem
can anybody help?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2006 04:03 AM
12-08-2006 04:03 AM
Re: ethernet id problem
Hi,
In Tru64 UNIX, component names are designed to be unique. Some hardware components derive their unique names based on their physical location. In particular, most buses and controllers derive their system-wide unique name from their physical location in the system. If you move such a component from one physical location in the system to another, it might appear as a new device, with a new name, when you subsequently reboot the system.
Component is assigned a persistence type
and persistence location based on its physical location. The persistence type can be a network controller or a peripheral component interconnect (PCI) bus providing a series of slots. The persistence location of a component can be the logical address of a particular slot on a bus, such as
slot 2 on PCI bus 1 or a main bus location.
Use #/sbin/hwmgr show name command to see the component and its physical locations, you can rename if you want using #/sbin/hwmgr remove name -entry ee0, but
HP recommends that you let your system dynamically assign component names.
After reboot, the persistent names are recreated. The new names are assigned in the order in which the hardware is probed.
For example, ee0 is assigned to the first NIC discovered during hardware probe, ee1 is assigned to the next, and so on until all the components are discovered.
Archunan
In Tru64 UNIX, component names are designed to be unique. Some hardware components derive their unique names based on their physical location. In particular, most buses and controllers derive their system-wide unique name from their physical location in the system. If you move such a component from one physical location in the system to another, it might appear as a new device, with a new name, when you subsequently reboot the system.
Component is assigned a persistence type
and persistence location based on its physical location. The persistence type can be a network controller or a peripheral component interconnect (PCI) bus providing a series of slots. The persistence location of a component can be the logical address of a particular slot on a bus, such as
slot 2 on PCI bus 1 or a main bus location.
Use #/sbin/hwmgr show name command to see the component and its physical locations, you can rename if you want using #/sbin/hwmgr remove name -entry ee0, but
HP recommends that you let your system dynamically assign component names.
After reboot, the persistent names are recreated. The new names are assigned in the order in which the hardware is probed.
For example, ee0 is assigned to the first NIC discovered during hardware probe, ee1 is assigned to the next, and so on until all the components are discovered.
Archunan
Regards
Archie
Archie
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