Sponsored Content
Operating Systems HP-UX Help needed HP UX 11.11i new install on C8000 Desktop messaging system error CAN'T FIX Post 302929804 by C8000 on Friday 26th of December 2014 06:07:31 PM
Old 12-26-2014
ok set up network using final stage of os install , all text based, answered no to DHCP set up manually, ip address entered 192.168.1.18, gateway 192.168.1.1 subnet mask 255.255.255.0

named system c80001
didnt enter any NIS settings or any other network settings

this allows boot to CDE desktop without Desktop messaging error

ok to start your questions
boot to command line (?)
ping 192.168.1.1 to ping gateway
got good result
ping 192.168.1.18 to ping my system
got good result
assume subnet mask at 255.255.255.0 is ok, checked in router manual settings etc
do the speed of lan ports match (????)

do nslookup unix.com
get output of

Using /etc/hosts on: c80001
looking up FILES
*** no address information available for "unix.com"
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

The Desktop Messaging System Could Not Be Started HP-UX

Hi People! I've just got a HP-UX system dumped on me. I've started it, followed all the install/setup questions, and everything was going ok, right upto when going into the desktop enviroment I got the message "The Desktop Messaging System Could Not Be Started". Now I've checked the... (8 Replies)
Discussion started by: cpiuk
8 Replies

2. UNIX for Dummies Questions & Answers

sudo install on HP UX 11i(basic question)

Hello folks, had a question. I was trying to install sudotool on HP -UX 11i. I downloaded gzip file from sudo site and unzipped to /tmp folder on HP box how do i install it?? do i need to run "swinstall" menu and then choose from there? THanks! karthik (1 Reply)
Discussion started by: karthikosu
1 Replies

3. HP-UX

11i install error

Hi Experts I have a C3000 workstation onto which I am trying to install 11i however I am running into the following error. ENTRY_INIT failed, status = -4: Unrecoverable hardware error (followed by a hex dump) I have re-tried many times and on one occasion successfully got through to CD... (4 Replies)
Discussion started by: C3000
4 Replies

4. HP-UX

HP UX 11i and HP C8000

Hey, i want install HP UX 11i on HP C8000. When i start the C8000 i get a prompt. On this Prompt i write BOot P1 P1 is my DVD-ROM (IDE). I get the Message "ERROR: Not a boot path". When i write SEArch the Prompt said: P0 scsiA.6 HP73.4MAT3073NP P1 ide.1 ... (2 Replies)
Discussion started by: numx
2 Replies

5. UNIX for Advanced & Expert Users

The DT messaging system could not be started

Hello All, I am getting " The DT messaging system could not be started" message when wants to login as root on a box running on tru64 5.1A. /etc/hosts is ok. when i see in .dt/errorlog it shows message server could not be started. Thanks for help. Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies

6. Solaris

how to install iplanet messaging server 5.2 on solaris 10

hi all, I want to install iplanet messaging service in solaris 10. if it is possible plz send the procedure for installation.its urgent plz regards spandan (2 Replies)
Discussion started by: spandhan
2 Replies

7. HP-UX

RX2620 11i V3 install halts at load ram disk

Hi there, hope you can help since I'm a novice and playing with this machine to maybe one day use it with our non-profit art project (plantage9.de). I have the proper media for itanium and everything seems okay, loads the DVD etc., until it halts without any progress for hours (see also image... (1 Reply)
Discussion started by: plantage
1 Replies

8. Red Hat

RPM Install error: libc.so.6 is needed by

I have an application rpm which when installed is failing to get installed with error error: Failed dependencies: libc.so.6 is needed by testSam-4.7.x86_64 libc.so.6(GLIBC_2.0) is needed by testSam-4.7.x86_64 libc.so.6(GLIBC_2.1) is needed by testSam-4.7.x86_64 ... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

9. Shell Programming and Scripting

The DT messaging system could not be started.

Good Morning, Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 04:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy