NIM w/ two network interfaces


Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
# 1  
Question NIM w/ two network interfaces

Hi all, this is my first post on this forum. My main problem is this:

I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing. I have made a few mistakes doing this. I want to force all 10.x.x.x traffic over the Admin VLAN and everything else can go over the interface. That way all of the other AIX boxes and admins can come in on en4 and SUMA and all other packets go to the en8. I used route add and when i rebooted I lost all of my routing, I know that it isn't persistent now! I have used smitty to do a lot of the changes the problem w/ that is that it puts multiple entries into the ODM. Not good messes up the routing table. Here is what I have right now:

Route Tree for Protocol Family 2 (Internet):
10/8 10.156.40.1 UG 5 3660 en4 - -
10.155.40.0 10.155.40.16 UHSb 0 0 en8 - - =>
10.155.40/24 10.155.40.16 U 0 1 en8 - -
10.155.40.16 127.0.0.1 UGHS 0 1 lo0 - -
10.155.40.255 10.155.40.16 UHSb 0 4 en8 - -
10.156.40/24 10.156.40.20 U 1 107459 en4 - -
10.156.40.20 127.0.0.1 UGHS 5 77 lo0 - -
10.156.40.255 10.156.40.20 UHSb 0 4 en4 - -
127/8 127.0.0.1 U 13 171177 lo0 - -

I just need to force all 10.x.x.x over the internal en4 interface, shouldn't be that hard right? Yet I need both interfaces to know where their default gateways are... Maybe I am just missing a step, that is what I am thinking. Any help would be great.
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #56
Difficulty: Easy
A flip-flop circuit stores 1 bit of data.
True or False?

10 More Discussions You Might Find Interesting

1. Linux

Network interfaces error

I just ran sudo service networking start on Ubuntu 16.00 and came out with error message Job for networking service failed because control process exited with error code see systemctl status networking.service I tried to also run this command systemctl status networking.service I also got an... (4 Replies)
Discussion started by: DOkuwa
4 Replies

2. UNIX for Dummies Questions & Answers

/etc/network/interfaces

i need a one liner command that writes in /var/log/net.log the date when i connect to the network and when i disconect ..i know that i need to write somethin in /etc/network/interfaces but idk what ! please help (1 Reply)
Discussion started by: g0dlik3
1 Replies

3. UNIX for Advanced & Expert Users

How to bond network interfaces

All, I have a quad NIC on a V880 running Solaris 9. I've heard you can bond interfaces together and get better throughput. I found this link that seems to describe the process well. However, the command mentioned (dladm) is missing. Is there some package I need to install to get this command? Thx.... (2 Replies)
Discussion started by: agcodba
2 Replies

4. Debian

/etc/network/interfaces problem

Hello i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address then i save it wq! then i restart the networking , /etc/init.d/networking restart . but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address... (5 Replies)
Discussion started by: learn82
5 Replies

5. UNIX for Dummies Questions & Answers

using wget on selected network interfaces

Hi there, I have a Linux Debian server with 2 network cards each connected through a different gateway : auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.224 netmask 255.255.255.0 gateway 192.168.1.1 auto eth1 iface eth1 inet... (5 Replies)
Discussion started by: chebarbudo
5 Replies

6. Solaris

Network Interfaces

I got second IOU in my M5000 but not able bring internal network interfcae .. ike i don't get link on those 2 interfaces .. and the same network cable plugged in PCI network card it works like a charm Is there any special way to enable the internal IOU interfaces or i have bad nics ? (8 Replies)
Discussion started by: fugitive
8 Replies

7. AIX

NIM w/ two network interfaces

Hi all, this is my first post on this forum. My main problem is this: I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (1 Reply)
Discussion started by: snakernetb
1 Replies

8. SCO

Network interfaces problem

Hi, I have problems with my SCO unix network interfaces. Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot. Installed driver using SCO Software manager - successfully Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies

9. IP Networking

Network interfaces problem

Hi, I have problems with my SCO unix network interfaces. Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot. Installed driver using SCO Software manager - successfully Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies

10. Solaris

HOW-TO Retrieve all network interfaces??!

Yes. But just wait a bit. How to do it via system calls? I'm just a newbie in Unix\Linux\Solaris e.t.c. programming. Can anyone help me? I need an advice probably how to do it or may be what API to read... :) Please, help... (2 Replies)
Discussion started by: LocalStorm
2 Replies
FIPVLAN(8)							  Open-FCoE Tools							FIPVLAN(8)

NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery SYNOPSIS
fipvlan [-c|--create] [-s|--start] [-m|--mode fabric|vn2vn] interfaces fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-m|--mode fabric|vn2vn] [-l|--link-retry count] fipvlan -h|--help fipvlan -v|--version DESCRIPTION
The fipvlan command performs Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) VLAN Discovery over Ethernet interfaces. fipvlan can be used as a diagnostic tool to determine which VLANs have FCoE services available on a network, prior to configuring VLAN interfaces and the Open-FCoE initiator. fipvlan can also be used to create VLAN interfaces as they are discovered, and to start the Open-FCoE initiator. The --create and --start options are primarily intended to be used as part of an Open-FCoE boot solution. FCoE instances started in this way cannot be destroyed or reset by fcoeadm. fipvlan takes a list of network interface names to run the VLAN discovery protocol over, or the --auto option to use all available Ethernet interfaces. fipvlan will enable any interface which is found disabled. If no response is received on that interface it will be shutdown again when fipvlan terminates. OPTIONS
-a, --auto Use all Ethernet interfaces currently available -c, --create Create network interfaces for discovered FCoE VLANs. If a VLAN device already exists for a discovered VLAN, a new VLAN device will not be created. -d, --debug Enable debugging output -s, --start Start the Open-FCoE initiator on discovered FCoE VLANs -m, --mode fabric|vn2vn Specify whether VLAN discovery is performed in the default fabric mode, or in VN2VN mode. -f, --suffix suffix Append the specified string suffix to VLAN interface names. -l, --link-retry count Retry check for link up to count times. The link state is checked every 500 ms. The default number of retries is 20. -h, --help Display a help message with basic usage instructions -v, --version Display the fipvlan version string VLAN NAMING CONVENTIONS
If a new VLAN device is created, it will have the name dev.vlan; where dev is the name of the Ethernet parent device and vlan is the discovered VLAN ID number. An optional suffix may be appended to this with the the -f command line option. EXAMPLES
Display all discoverable VLANs with FCoE services fipvlan --auto Discover FCoE VLANs on interface eth2, create VLAN devices and start the Open-FCoE initiator fipvlan --create --start eth2 In this example if FCoE services were available on VLAN 101 of network interface eth2, then a VLAN interface eth2.101 would be created and used as the parent device for the initiator. SEE ALSO
fcoeadm(8) fcoemon(8) SUPPORT
fipvlan is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found at the Open-FCoE website http://open-fcoe.org/ Open-FCoE 03/18/2013 FIPVLAN(8)

Featured Tech Videos