Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
implementing vipa on AIX
- Thread starter raylin
- Start date
I didn't try VIPA but found on IBM it quite nice described:
VIPA and routing protocols
The gated daemon was modified for VIPA so that it would not add the interface route or send advertisements over virtual interfaces.
VIPA and routing protocols
The gated daemon was modified for VIPA so that it would not add the interface route or send advertisements over virtual interfaces.
- Thread starter
- #3
I had already found this info and I based my test configuration from this info.
But now how can I define a default route ?
On the VIPA network interface you can not define a default route.
Is it the role of the gated daemon ? If yes how can I configure this daemon ?
I found no more than this doc , no redbook.
root@bssp161:/etc>lsattr -El vi0
alias4 TRAILER Link-Level Encapsulation True
alias6 Internet Address True
interface_names en1,en2 N/A True
netaddr 10.48.12.161 N/A True
netaddr6 Maximum IP Packet Size for REMOTE Networks True
netmask 255.255.255.0 Maximum IP Packet Size for This Device True
prefixlen Current Interface Status True
state up Standard Ethernet Network Interface True
root@bssp161:/etc>ifconfig vi0
vi0: flags=84000041<UP,RUNNING,64BIT>
inet 10.48.12.161 netmask 0xffffff00
iflist : en1 en2
root@bssp161:/etc>netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2 (Internet):
10.48.12.0 10.48.12.162 UHSb 0 0 en1 - - - =>
10.48.12.0 10.48.12.163 UHSb 0 0 en2 - - - =>
10.48.12/24 10.48.12.162 U 4 77 en1 - - - =>
10.48.12/24 10.48.12.163 U 0 0 en2 - - -
10.48.12.161 127.0.0.1 UH 0 0 lo0 - - -
10.48.12.162 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.163 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.255 10.48.12.162 UHSb 1 0 en1 - - - =>
10.48.12.255 10.48.12.163 UHSb 0 0 en2 - - -
10.48.50.0 10.48.50.161 UHSb 0 0 en0 - - - =>
10.48.50/24 10.48.50.161 U 7 49564683 en0 - - -
10.48.50.255 10.48.50.161 UHSb 0 0 en0 - - -
127.0.0.1 127.0.0.1 UH 2 231 lo0 - - -
Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 7 lo0 16896 - -
But now how can I define a default route ?
On the VIPA network interface you can not define a default route.
Is it the role of the gated daemon ? If yes how can I configure this daemon ?
I found no more than this doc , no redbook.
root@bssp161:/etc>lsattr -El vi0
alias4 TRAILER Link-Level Encapsulation True
alias6 Internet Address True
interface_names en1,en2 N/A True
netaddr 10.48.12.161 N/A True
netaddr6 Maximum IP Packet Size for REMOTE Networks True
netmask 255.255.255.0 Maximum IP Packet Size for This Device True
prefixlen Current Interface Status True
state up Standard Ethernet Network Interface True
root@bssp161:/etc>ifconfig vi0
vi0: flags=84000041<UP,RUNNING,64BIT>
inet 10.48.12.161 netmask 0xffffff00
iflist : en1 en2
root@bssp161:/etc>netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2 (Internet):
10.48.12.0 10.48.12.162 UHSb 0 0 en1 - - - =>
10.48.12.0 10.48.12.163 UHSb 0 0 en2 - - - =>
10.48.12/24 10.48.12.162 U 4 77 en1 - - - =>
10.48.12/24 10.48.12.163 U 0 0 en2 - - -
10.48.12.161 127.0.0.1 UH 0 0 lo0 - - -
10.48.12.162 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.163 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.255 10.48.12.162 UHSb 1 0 en1 - - - =>
10.48.12.255 10.48.12.163 UHSb 0 0 en2 - - -
10.48.50.0 10.48.50.161 UHSb 0 0 en0 - - - =>
10.48.50/24 10.48.50.161 U 7 49564683 en0 - - -
10.48.50.255 10.48.50.161 UHSb 0 0 en0 - - -
127.0.0.1 127.0.0.1 UH 2 231 lo0 - - -
Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 7 lo0 16896 - -
In the sample given on the site is said:
Sample VIPA environment in AIX® 5.2
The following sample VIPA environment with Ethernet connections involves a system with a virtual IP address and two physical connections.
A system has a virtual IP address, vi0, of 10.68.6.1 and two physical connections, en1 with IP address 10.68.1.1 and en5, with IP address 10.68.5.1. In this example, both physical connections are Ethernet, but any mixture of IP interfaces, such as token-ring or FDDI, would be supported as long as the subnets were ultimately attached to the larger corporate network and were known to the corporate routers.
Running the lsattr -El vi0 command produces the following results:
netaddr 10.68.6.1 N/A True
state up Standard Ethernet Network Interface True
netmask 255.255.255.0 Maximum IP Packet Size for This Device True
netaddr6 Maximum IP Packet Size for REMOTE Networks True
alias6 Internet Address True
prefixlen Current Interface Status True
alias4 TRAILER Link-Level Encapsulation True
interface_names en1,en5 Interfaces using the Virtual Address True Running the ifconfig vi0 command produces the following results:
vi0: flags=84000041<UP,RUNNING,64BIT>
inet 10.68.6.1 netmask 0xffffff00
iflist : en1 en5 Running the netstat -rn command produces the following results:
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2 (Internet):
default 10.68.1.2 UG 3 1055 en1 - -
10.68.1/24 10.68.1.1 U 0 665 en1 - -
10.68.5/24 10.68.5.1 U 0 1216 en5 - -
127/8 127.0.0.1 U 4 236 lo0 - -
10.68.6.1 127.0.0.1 UH 0 0 lo0 - - The outgoing packets that do not have a source address set and that are routed via interfaces en1 and en5 will have the source address set to the virtual address (10.68.6.1). Incoming packets are routed to the VIPA address (10.68.6.1) advertised on the network. Because vi0 is virtual (that is, not associated with any device) there should be no entries for it in the system-wide routing table displayed using the netstat -rn command. This means no interface route is added when the interface is configured in SMIT.
If one of the physical interfaces, a network attachment, or a network path fails, the network protocols route to the other physical interface on the same system. If a remote system telnets to the vi0 address, packets to vi0 can arrive using either en1 or en5. If en1 is down, for example, packets can still arrive on en5. Note that routing protocols might take time to propagate the routes.
When using the VIPA, the end systems and intervening routers must be able to route the packets destined for VIPA (vi0) to one of the physical interfaces (en1 or en5).
----------
Shouldn't you have set the default router you would have for physical interface(s)?
Sample VIPA environment in AIX® 5.2
The following sample VIPA environment with Ethernet connections involves a system with a virtual IP address and two physical connections.
A system has a virtual IP address, vi0, of 10.68.6.1 and two physical connections, en1 with IP address 10.68.1.1 and en5, with IP address 10.68.5.1. In this example, both physical connections are Ethernet, but any mixture of IP interfaces, such as token-ring or FDDI, would be supported as long as the subnets were ultimately attached to the larger corporate network and were known to the corporate routers.
Running the lsattr -El vi0 command produces the following results:
netaddr 10.68.6.1 N/A True
state up Standard Ethernet Network Interface True
netmask 255.255.255.0 Maximum IP Packet Size for This Device True
netaddr6 Maximum IP Packet Size for REMOTE Networks True
alias6 Internet Address True
prefixlen Current Interface Status True
alias4 TRAILER Link-Level Encapsulation True
interface_names en1,en5 Interfaces using the Virtual Address True Running the ifconfig vi0 command produces the following results:
vi0: flags=84000041<UP,RUNNING,64BIT>
inet 10.68.6.1 netmask 0xffffff00
iflist : en1 en5 Running the netstat -rn command produces the following results:
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2 (Internet):
default 10.68.1.2 UG 3 1055 en1 - -
10.68.1/24 10.68.1.1 U 0 665 en1 - -
10.68.5/24 10.68.5.1 U 0 1216 en5 - -
127/8 127.0.0.1 U 4 236 lo0 - -
10.68.6.1 127.0.0.1 UH 0 0 lo0 - - The outgoing packets that do not have a source address set and that are routed via interfaces en1 and en5 will have the source address set to the virtual address (10.68.6.1). Incoming packets are routed to the VIPA address (10.68.6.1) advertised on the network. Because vi0 is virtual (that is, not associated with any device) there should be no entries for it in the system-wide routing table displayed using the netstat -rn command. This means no interface route is added when the interface is configured in SMIT.
If one of the physical interfaces, a network attachment, or a network path fails, the network protocols route to the other physical interface on the same system. If a remote system telnets to the vi0 address, packets to vi0 can arrive using either en1 or en5. If en1 is down, for example, packets can still arrive on en5. Note that routing protocols might take time to propagate the routes.
When using the VIPA, the end systems and intervening routers must be able to route the packets destined for VIPA (vi0) to one of the physical interfaces (en1 or en5).
----------
Shouldn't you have set the default router you would have for physical interface(s)?
- Thread starter
- #5
I entered a default gateway on the 2 physical network interface en1 and en2.
I can now ping the vipa from outside.
I unplugged one interface and could still ping from outside the dns hostname (=vipa address)
I plugged again the unplugged interface and unplugged the other interface and from now on no more ping possible.
It seems that the default gateway has disappeared :
root@bssp161:/etc>netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2 (Internet):
10.48.12.0 10.48.12.163 UHSb 0 0 en2 - - - =>
10.48.12/24 10.48.12.163 U 0 0 en2 - - -
10.48.12.161 127.0.0.1 UH 0 0 lo0 - - -
10.48.12.162 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.163 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.255 10.48.12.162 UHSb 0 0 en1 - - - =>
10.48.12.255 10.48.12.163 UHSb 1 0 en2 - - -
10.48.50.0 10.48.50.161 UHSb 0 0 en0 - - - =>
10.48.50/24 10.48.50.161 U 7 49571721 en0 - - -
10.48.50.255 10.48.50.161 UHSb 0 0 en0 - - -
127.0.0.1 127.0.0.1 UH 4 1235 lo0 - - -
Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 7 lo0 16896 - -
replugged the interface but no more ping possible
errorlog :
root@bssp161:/etc>errpt
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
D5528AE6 1107140007 T H ent1 PROBLEM RESOLVED
499B30CC 1107134607 T H ent1 ETHERNET DOWN
D5528AE6 1107134607 T H ent2 PROBLEM RESOLVED
499B30CC 1107134007 T H ent2 ETHERNET DOWN
I can now ping the vipa from outside.
I unplugged one interface and could still ping from outside the dns hostname (=vipa address)
I plugged again the unplugged interface and unplugged the other interface and from now on no more ping possible.
It seems that the default gateway has disappeared :
root@bssp161:/etc>netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2 (Internet):
10.48.12.0 10.48.12.163 UHSb 0 0 en2 - - - =>
10.48.12/24 10.48.12.163 U 0 0 en2 - - -
10.48.12.161 127.0.0.1 UH 0 0 lo0 - - -
10.48.12.162 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.163 127.0.0.1 UGHS 0 2 lo0 - - -
10.48.12.255 10.48.12.162 UHSb 0 0 en1 - - - =>
10.48.12.255 10.48.12.163 UHSb 1 0 en2 - - -
10.48.50.0 10.48.50.161 UHSb 0 0 en0 - - - =>
10.48.50/24 10.48.50.161 U 7 49571721 en0 - - -
10.48.50.255 10.48.50.161 UHSb 0 0 en0 - - -
127.0.0.1 127.0.0.1 UH 4 1235 lo0 - - -
Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 7 lo0 16896 - -
replugged the interface but no more ping possible
errorlog :
root@bssp161:/etc>errpt
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
D5528AE6 1107140007 T H ent1 PROBLEM RESOLVED
499B30CC 1107134607 T H ent1 ETHERNET DOWN
D5528AE6 1107134607 T H ent2 PROBLEM RESOLVED
499B30CC 1107134007 T H ent2 ETHERNET DOWN
did you configure your default interface for permanent - in ODM?
do you see any gw on "lsattr -El inet0" output?
if not, try to add the default gw once again using "smitty chinet" command or "chdev -l inet0 -a addroute=...".
example for the chdev command:
chdev -l inet0 -a addroute="net,-hopcount,0,,0,XX.XX.XX.XX"
where XX.XX.XX.XX is your gw IP address.
do you see any gw on "lsattr -El inet0" output?
if not, try to add the default gw once again using "smitty chinet" command or "chdev -l inet0 -a addroute=...".
example for the chdev command:
chdev -l inet0 -a addroute="net,-hopcount,0,,0,XX.XX.XX.XX"
where XX.XX.XX.XX is your gw IP address.
- Thread starter
- #7
after TCP/IP - Minimum Configuration & Startup on one physical interface , the default gateway was again there and ping from outside was possible.
I do not want to add static routes.
I think the gated daemon config file must be configurated (etc/gated.conf) and not only starting the daemon with startsrc -s gated ...
found following topic :
I do not want to add static routes.
I think the gated daemon config file must be configurated (etc/gated.conf) and not only starting the daemon with startsrc -s gated ...
found following topic :
- Status
Similar threads
- Locked
- Question