10-08-2010
hostname.bge0 failing after creating bge0:1 and rebooting
Hello,
I've got a puzzler here but it might be quick solution for some of you.
I'm trying to add a second IP address to a network adapter on a Solaris 10 box. I've created a hostname.bge0:1 file and put in the new name, e.g. new.mycom.com. I've added the new IP and the name to hosts. I've done:
Ifconfig bge0:1 plumb
Ifconfig bge0:1 xxx.xx.xx.xxx
Ifconfig bge0:1 up
There are really two problems.
1. My new.mycom.com is resolving to old.mycom.com. I probably need to do something like set Listen xxx.xx.xx.xxx:80 in the httpd.conf for the old IP so the new IP can go to the new.mycom.com?
2. After I get things set up and do a normal reboot, I cannot get to old.mycom.com. The page will not load in the browser. I can SSH to server. The only thingy that doesn't work is the WWW, I cannot get the index.html or any other page. Then when I remove the new hostname.bge0:1 and reboot, everything is fine and functioning as normal. Do I need to ifconfig hostname.bge0 up maybe? I've taken a look at ifconfig -a and it looks fine.
Any ideas? Please educate me.
Thank you,
Friedrich
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I do a hard reboot, the system recognizes both the ttya and the ttyb, but when I do a hard reboot, it only doesn't recognize the ttyb. Is there a way I can fix this???
Thanks!:confused: (5 Replies)
Discussion started by: nattie_h
5 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I am new to Solaris.
I am using stand alone Solaris 10.0 for test/study purpose and connecting to internet via an ADSL modem which has DHCP server. My Solaris is working on VMWare within winXP. My WinXP and Solaris connects to internet by the same ADSL modem via its DHCP at the same... (1 Reply)
Discussion started by: XNOR
1 Replies
3. Solaris
Hi,
Server --Dell Poweredge 2550.
OS--Solaris 10
Network switch --cisco --port setting- 1000Mbps full duplex
The network LED goes off when the solaris console screen comes up but prior to that(while booting is in progess) it is green.
The system is not able to come on network,ping to switch... (3 Replies)
Discussion started by: anilzoc
3 Replies
4. AIX
Anyone faced this?
I rebooted the HMC through command line after patch installation (hmcshutdown -t now -r)
The strange thing happened was the hmc never rebooted, I was not able to connect it through graphical view or through ssh, but the session through which i issued the command was still... (4 Replies)
Discussion started by: balaji_prk
4 Replies
5. Solaris
Deall All,
I have facing some problem. I have a Sun 4500 Server at the customer place. Now the server is not booting mean's once the server is coming up it is automatically rebooting. As this is the critical server for the customer that is use for production .
Can this be solved by... (10 Replies)
Discussion started by: sudhansu
10 Replies
6. Solaris
Hi people,
I have a solaris OS system. I configured its interfaces. They are UP but not in RUNNING status except loopback interface. I made the interfaces DOWN and UP again. The other side of the interfaces (switch ports) are UP. Does anyone have any idea? What may cause this problem, How can... (8 Replies)
Discussion started by: hubatuwang
8 Replies
7. Emergency UNIX and Linux Support
Hi All,
So we added a new HP-UX 11.31 machine. Copied OS via Ignite-UX (DVD)over from this machine called machine_a. It was supposed to be named machine_c. And it is when you log in...however when I'm in the ILO console before logging in, it says:
It should say:
What gives? And how do... (4 Replies)
Discussion started by: zixzix01
4 Replies
8. AIX
Hi,
I would like to know wheather rebooting HMC will impact on Management Systems or Lpar inside it is showing?
or I have to shutdown LPAR then only reboot HMC. (7 Replies)
Discussion started by: manoj.solaris
7 Replies
9. What is on Your Mind?
Apologies if this is not the correct place to post this.
I used to have a job supporting several custom applications that ran on Unix platforms. I used shell scripting, sed, awk, and SQL, but all on a pretty basic level. I also performed non-technical tasks like helping with project management,... (4 Replies)
Discussion started by: intranslation
4 Replies
10. UNIX for Advanced & Expert Users
deleted (0 Replies)
Discussion started by: hce
0 Replies
AGR(4) BSD Kernel Interfaces Manual AGR(4)
NAME
agr -- link aggregation pseudo network interface driver
SYNOPSIS
pseudo-device agr
DESCRIPTION
The agr driver provides link aggregation functionality (a.k.a. L2 trunking or bonding).
It supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol.
The agr driver supports the following link specific flags for ifconfig(8):
link0 Use the round-robin distribution algorithm. Don't use it unless you're really sure, because it violates the frame ordering rule.
-link0 Use the default distribution algorithm, which is based on the hash of DA/SA, TCI, and, if available, some upper layer protocol infor-
mation like ip(4) DA/SA.
link1 Disable LACP. Prevents any LACP or Marker messaging which leaves the ports in the default static configuration. Set this prior to
adding ports.
EXAMPLES
Create an agr interface, agr0, and attach re0 and re1 to it. In other words, aggregate re0 and re1 so that they can be used as a single
interface, agr0. The physical interfaces which are attached to the agr interface must not have any IP addresses, neither IPv4 nor IPv6.
ifconfig re0 inet xxx.xxx.xxx.xxx delete
ifconfig re0 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig re1 inet xxx.xxx.xxx.xxx delete
ifconfig re1 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig agr0 create
ifconfig agr0 agrport re0
ifconfig agr0 agrport re1
Destroy an interface created in the above example.
ifconfig agr0 -agrport re0
ifconfig agr0 -agrport re1
ifconfig agr0 destroy
SEE ALSO
ifconfig(8)
STANDARDS
IEEE 802.3ad Aggregation of Multiple Link Segments
HISTORY
The agr driver first appeared in NetBSD 4.0.
AUTHORS
The agr driver was written by YAMAMOTO Takashi.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation of the agr
driver always performs active-mode LACP and uses 0x8000 as system and port priorities.
The agr driver uses the MAC address of the first-added physical interface as the MAC address of the agr interface itself. Thus, removing the
physical interface and using it for another purpose can result in non-unique MAC addresses.
The current implementation of the agr driver doesn't prevent unsafe operations like some ioctls against underlying physical interfaces. Such
operations can result in unexpected behaviors, and are strongly discouraged.
There is no way to configure agr interfaces without attaching physical interfaces.
Physical interfaces being added to the agr interface shouldn't have any addresses except for link level address. Otherwise, the attempt will
fail with EBUSY. Note that it includes an automatically assigned IPv6 link-local address.
BSD
February 23, 2010 BSD