- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: NIC/Physical address problem
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-28-2007 11:55 PM
тАО03-28-2007 11:55 PM
Re: NIC/Physical address problem
I came to work this morning and saw MAC address of that node in the MAC address table (switch).
Confused....I tried to ping the node but didnt recieved an echo. Then I typed command ucx sh int/full to check for any send/recieve packages and nothing. After I looked at NIC and LINK led was blinking. I first tought there might be a duplicated MAC address on the LAN but no.
Yeah the problem was on Physical or Data layer for sure...after I did the command that Andy suggested (mc lancp sh dev /char) and it showed the speed "100". I compared it with other nodes on the LAN and they were set to communicate on 10Mbit/s. Heureka!
-------------------------------------
So once again thanks Andy and everybody I learned some useful stuff here.
Still lot to learn so I might come back with more stupid questions. Thanks!
...and yeah...my boss is satisfied now :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2007 12:07 AM
тАО03-29-2007 12:07 AM
Re: NIC/Physical address problem
Also thx, for the links I will read them for sure. Especialy for DECnet.
This SRM(>>>)...what is it exacly? Something like BIOS or...?
I was typing some stuff at that prompt before VMS installation...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2007 12:25 AM
тАО03-29-2007 12:25 AM
Re: NIC/Physical address problem
welcome to the OpenVMS ITRC forum and the world of OpenVMS from me, too.
There are two types of firmware on Alpha systems: SRM (Systems Reference Manual) and ARC (Advanced Risc Console).
Firmware is loosely synonymous with the BIOS software on PC systems.
By the way, what company are you working for (I am also from Croatia)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2007 01:56 AM
тАО03-29-2007 01:56 AM
Re: NIC/Physical address problem
from me also:
Dobro dosli to the VMS Forum.
As you already found out, on matters related to DecNet Colin really _IS_ a guru (and Steven is guru in so many fields that is incorrect to call him just a network guru).
>>>
and sry 4 bad Englsih. :)
<<<
No need.
To begin with, we have seen much wors.
The only thing you should be sorry about, is for _NOT_ asking questions that others in this forum could answer!!
No excuse necessary for lack of specific knowledge: NOBODY can know everything, and even the greatest gurus also have started as beginners!
Na zdravje
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2007 02:12 AM
тАО03-29-2007 02:12 AM
Re: NIC/Physical address problem
Its useful information to keep.
In that information you should see the setting for the NIC card that it will star at. Determines the speed and duplex. I would suggest checking that value next time the system is down.
Usually "show ewa0*" - like ewa0_mode.
And welcome to the forum.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2007 08:22 AM
тАО03-29-2007 08:22 AM
Re: NIC/Physical address problem
Croatia, Zagreb-Croatian Post! :)
I just wonder how many VMS admins/systems are here in Croatia. :)
------------------------------------
@Jan van den Ende
I guess now I know where you spend your hollydays... :)
Hehehe...I'm suprised!
Takodjer, na zdravlje!
------------------------------------
@Peter Zeiszle
Yes I studied help pages for a while...especialy in VMS, I found them even more user friendly then linux manuals!
Only directory structure is a bit confusing at first...it still is. :)
-------------------------------------
Ohhh yeah...I was messing with file security options.
Problem is, I started Anonymous FTP server on that node and once I connect to it I can't download files/directories because of security violations.
I typed command something like
I cheked with
Any tips on how to solve this issue?
And how can I set on SRM promt to automaticly boot dka0 device on power-on and is it possible if booting of dkao fails that it tries to boot second device dka100?
Once again thank you for support. I tought that days will pass since I get first respond. :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2007 08:45 AM
тАО03-29-2007 08:45 AM
Re: NIC/Physical address problem
I cheked with
You might want to provide some details on your goals, as there may be other ways to resolve this. If you're trying to create a wide-open anonymous FTP directory (which is itself quite hazardous if this box is accessible on a network, as various nefarious-minded folks are actively looking for these directories) then there is the anonymous logical name that needs to be set up, and the directory and file protections and ownerships need to be set.
As for tracking the specific NOPRIV error, if it's not the logical name or ownerships... Enable file access failure auditing via SET AUDIT (and you can view the current auditing settings via SHOW AUDIT) and use ANALYZE/AUDIT command to see what object is returning the failure. If this is a "real" NOPRIV error, full details will then get logged. And you can then see exactly why the failure is occurring.
As for setting up anonymous FTP, there's a section on this topic in the TCP/IP Services manuals (in the management manual), and the TCP/IP manuals (and others) are available in the left navigation at http://www.hp.com/go/openvms/doc/
>>>And how can I set on SRM promt to automaticly boot dka0 device on power-on...<<<
SET AUTO_ACTION RESTART
SET BOOTDEF_DEV DKA0
There's a HELP command at the console, too.
>>>...and is it possible if booting of dkao fails that it tries to boot second device dka100? <<<
The usual approach is to resolve the problem with the device. There's not a particular concept of a sequence for bootstrap devices in SRM, as there's a general assumption that the primary boot device will work -- save for cases of serious hardware failures.
- « Previous
-
- 1
- 2
- Next »