- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Alpha 4100 and DEGXA-TB
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-16-2008 01:19 PM
тАО03-16-2008 01:19 PM
Alpha 4100 and DEGXA-TB
The device shows up but won't configure in TCPIP.
The LANCP characteristics are as follows:
Device Characteristics EWA0:
Value Characteristic
----- --------------
1500 Device buffer size
Normal Controller mode
External Internal loopback mode
FF-FF-FF-FF-FF-FF 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
No Full duplex operational
FF-FF-FF-FF-FF-FF MAC address (Current LAN address)
TwistedPair Line media type
1000 Line speed (mbps)
Enabled Auto-negotiation
Enabled Flow control
Disabled Jumbo frames
Disabled/No Failset Logical LAN state
0 Failover priority
Link Down Link state
Thanks in advance for any suggestions (even if it's "futile, forget it."--Guy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2008 02:32 PM
тАО03-16-2008 02:32 PM
Re: Alpha 4100 and DEGXA-TB
> TCPIP.
This means what, exactly? That is, what,
exactly, did you do, and what, exactly,
happened when you did it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2008 05:08 PM
тАО03-16-2008 05:08 PM
Re: Alpha 4100 and DEGXA-TB
tcpip> define communication_controller (or some such) and tcpip> list communication_controller (or some such), to add and to list the device to those recognized by tcp/ip services. That's how you can get ucx to accept the controller, iirc. (It's been a while since I've tried this particular sequence, and I don't have a ucx box handy.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 05:05 AM
тАО03-17-2008 05:05 AM
Re: Alpha 4100 and DEGXA-TB
Device EWA0:, device type DEGXA, is online, network device, error logging is
enabled, device is a template only.
Error count 0 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size 512
Current preferred CPU Id 0 Fastpath 1
The communication controller shows up as a defined device:
Controller: EW Internet Interface: W
Description: PCI bus Ethernet Adapter
Type: CLUSTER ETHERNET
When I do a TCPIP SET INTERFACE WE0, I get the following:
TCPIP> set inter we0
%TCPIP-E-INVINTER, error defining interface: WE0
-TCPIP-I-DRIVERQIO, interface operation from internet driver QIO failed
-TCPIP-E-INVNETFLAG, invalid interface flags
ioctl failed: status = 908
ifconfig: no such interface: WE0
%SYSTEM-W-NOSUCHDEV, no such device available
which kicks me out of TCPIP.--Guy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2008 08:18 AM
тАО03-17-2008 08:18 AM
Re: Alpha 4100 and DEGXA-TB
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1195112
thread?
Which version of TCP/IP Services? (Current?)
Per the support matrix, the Tigon III DEGXA is not supported on the AlphaServer 4100, and the previous and current reports do not bode well.
If work is to continue here toward an unsupported configuration, what do the TCPIP> LIST and DEFINE COMMUNICATION_CONTROLLER commands present to you? (The "no such device" error in TCP/IP implies it's either not in the communications controller list that is used by TCP/IP Services to find and identify NICs, or that the DEGXA is being expressly excluded for some reason.)
As for an alternative, try the DEGPA GbE NIC, which is listed as supported on this box. Or pick up a fully-loaded and gently-used AlphaServer DS20e for USD$1500 a year ago, like I did for a customer. I'd expect the system prices have subsequently dropped, too.
Stephen Hoffman
HoffmanLabs LLC