- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- PROBLEM WITH AUTONEGOTIATE NIC ON IA64 RX2620
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
Discussions
Discussions
Forums
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
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
тАО03-07-2007 11:44 AM
тАО03-07-2007 11:44 AM
I have a problem with setting the authonegotiate off on a nic on a Integrity machine rx2620.
LANCP> SHO DEV EIA0:/CHAR
Device Characteristics EIA0:
Value Characteristic
----- --------------
1500 Device buffer size
Normal Controller mode
External Internal loopback mode
00-16-35-3E-AD-88 Default MAC address
(Hardware LAN address)
Multicast address list
Ethernet Communication medium
FF-FF-FF-FF-FF-FF MAC address (Current LAN
address)
128 Minimum receive buffers
256 Maximum receive buffers
Yes Full duplex enable
Yes Full duplex operational
AA-00-04-00-0B-04 MAC address (Current LAN
address)
TwistedPair Line media type
100 Line speed (mbps)
Disabled Auto-negotiation
Enabled Flow control
Disabled Jumbo frames
0 Failover priority
Link Up Link state
Via mc lancp, I configured the
LANCP>SET DEV EIA0:/SPEED=100
/MEDIA=TWISTEDPAIR
/NOAUTONEGOTIATE
/FULL_DUPLEX
/PERMANENT
When the server is not rebooted the autonegotiate has been disabled. When the server is rebooted the autonegotiate is back enabled which causes large delays in transfering files from the itanium server to an alpha server (autonegotiate on alpha is disabled).
So the /permanent qualifier is not that permanent as I thought.
On alpha man can disable autonegotiate at the srm console and after every reboot it stays disabled. Can someone tell me how I can permanently disable autonegotiate on my integrity machine.
Thank you in advance
Mario Dhaenens
Volvo Cars Gent
Belgium
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 12:00 PM
тАО03-07-2007 12:00 PM
Re: PROBLEM WITH AUTONEGOTIATE NIC ON IA64 RX2620
As per above given command u did /permanent qualifier
give same command after above command with /permanent_database qualifier.
both are required.
Thanks ,
Atul sardana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 12:53 PM
тАО03-07-2007 12:53 PM
SolutionLANCP> SET DEVICE . . . sets the current configuration.
LANCP> DEFINE DEVICE . . . sets the permanent configuration.
From LANCP HELP:
/PERMANENT_DATABASE
Updates the device entries in the LAN volatile device database with any data currently set in the permanent database. This allows you to update the volatile database after changing data in the permanent database, rather than repeating the commands for each updated entry to apply the changes to the volatile database.
Andy
San Diego, California
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 01:20 PM
тАО03-07-2007 01:20 PM
Re: PROBLEM WITH AUTONEGOTIATE NIC ON IA64 RX2620
I carried out the define command /
LANCP> DEFINE DEVICE EIA0:/SPEED=100/MEDIA=TWISTEDPAIR/NOAUTONEGOTIATE/FULL_DUPL
EX/PERMANENT_DATABASE
%LANCP-E-CONVERT, Database entry format not current, please convert database usi
ng the CONVERT command
-LANCP-E-FERRDEV, Error accessing LAN$DEVICE_DATABASE file
LANCP>
Mario
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 01:31 PM
тАО03-07-2007 01:31 PM
Re: PROBLEM WITH AUTONEGOTIATE NIC ON IA64 RX2620
in LANCP, do HELP CONVERT (as the message is trying
to advise you) to see the format of the CONVERT
command.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 01:34 PM
тАО03-07-2007 01:34 PM
Re: PROBLEM WITH AUTONEGOTIATE NIC ON IA64 RX2620
LANCP>SET DEV EIA0:/SPEED=100
/MEDIA=TWISTEDPAIR
/NOAUTONEGOTIATE
/FULL_DUPLEX
/PERMANENT/UPDATE
thenafter use
LANCP>SET DEV EIA0:/SPEED=100
/MEDIA=TWISTEDPAIR
/NOAUTONEGOTIATE
/FULL_DUPLEX
/PERMANENT_DATABSE
and it will make permanent entry in volatile databse
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 01:45 PM
тАО03-07-2007 01:45 PM
Re: PROBLEM WITH AUTONEGOTIATE NIC ON IA64 RX2620
LANCP> DEFINE DEVICE EIA0:/SPEED=100/MEDIA=TWISTEDPAIR/NOAUTONEGOTIATE/FULL_DUPL
EX/PERMANENT_DATABASE
%LANCP-E-CONVERT, Database entry format not current, please convert database usi
ng the CONVERT command
-LANCP-E-FERRDEV, Error accessing LAN$DEVICE_DATABASE file
LANCP>
I had to do some additional work to taccle this problem : I found the following procedure
1.9.7 Converting the LANCP Device Database After Upgrading V8.2
When you upgrade to OpenVMS Alpha Version 8.2, you might also need to convert
the LAN device database to the Version 8.2 format if this is not automatically
done by LANACP when LANACP is first run after the upgrade.
To convert the database, issue the following LANCP commands to convert the
device database and then to stop LANACP so it can be restarted to use the new
database:
$ LANCP
LANCP> CONVERT DEVICE_DATABASE
LANCP> SET ACP/STOP
LANCP> EXIT
$ @SYS$STARTUP:LAN$STARTUP
%RUN-S-PROC_ID, identification of created process is 0000043B
SYS_NVK$ MC LANCP
LANCP> DEFINE device EIA0:/SPEED=100/MEDIA=TWISTEDPAIR/NOAUTONEGOTIATE/FULL_DUPL
EX/PERMANENT_DATABASE
LANCP> EXIT
SYS_NVK$
After reboot I got the requested items I wanted, thank you guys
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 01:50 PM
тАО03-07-2007 01:50 PM