Is it possible to use a VLAN on an aggregated NIC to merge existing separate networks to the new Interface?
We are running NBU 6.5.4 on a Solaris Sparc configuration.
Currently we use two separate networks to perform backups, 1 is 4 NICs aggregated (aggr1) and the other is a single NIC (e1000g3) with a shared default gateway. In order to increase performance of the backups on the single NIC we want to merge them onto the aggregated one and add the single to the aggregation.
We have been reading about how we can setup a VLAN under an aggregated NIC to allow us to advertise 2 IP's under the same logical NIC (aggr1). We are planning to perform some testing, but before we do, I thought I should check with the Admin Gods!!
Our plan is as follows:
1) Stop NBU
2) Down e1000g3
3) Create a VLAN using the IP Address from the e1000g3 NIC
4) Start NBU
5) test communication and then backup to the servers within that segment
So our questions are as follows:
1) Will NBU be able to direct the VLAN to the Prime IP (aggr1)?
2) Do we have to make any other changes to the configuration of the Master Server?
3) Do we still have to look at making changes to the network configuration? (lets hope that this is not yes)
Thanks in Advance,
Kind Regards,
Trevor
Comments
Try it and let us know
It seems like you are planning to create a trunk interface that will accept traffic from 2 different VLAN's. The network switch that the server is connecting to will also need a trunk configured to pass VLAN traffic to the server.
NetBackup doesn't direct VLAN traffic. This will be the job of the OS. It would be interesting if it works.
Why not use 3 NICs for AGG-1 and 2 NICs for AGG-2 and keep the same network config. This way the traffic between the two VLAN's is still separated and double the bandwidth for AGG-2.
Another idea is to use Jumbo frames to decrease TCP overhead.
Hi Reagan, We have
Hi Reagan,
We have implemented our VLAN's and this is what we have found so far:
After creating the VLANs we initially needed to perform a 'reboot -- -r' to configure them properly. However, after the reboot the VLAN's would not work. We took the Aggregated NIC down and bought it back online again and hey presto, they started working.
However, since using the aggregated NIC's original IPAddress as one of the VLAN addresses we have been unable to make NOM work correctly.
If I were to implement the solution from scratch I would do the following:
1) Create a backup VLAN
2) Assign Master IP Address to the Aggregated NIC, Install the clients using DNS so that the million and one host files do not require changing.
3) Each new network / set of clients would have their own VLAN and specific IP
4) Install NOM on the Master server to the Aggr1 IP address
I think right now we are getting network problems that are stopping our existing NOM server from talking over the VLAN that the backup server is now a member of, so I will be talking with our networks team to resolve this.
Thanks for your time.
Trevor
Thanks for the feedback
Hi Trevor
Very interesting. If possible, install NOM on a seperate server (Windows, or Sparc Solaris). Installing NOM on the Master server works, but it creates an additional CPU load that could affect performance on the master server.
Reagan
Dhammica De Silva
"It's better to keep my mouth shut and be thought a fool rather than open it and remove all doubt." (Margaret Thatcher 1975)
NOM is Installed on a separate server...
The NOM issue with being unable to connect to the master server is starting to make the Network team hate me...
I am convinced that this is an issue with the network, as we can ping the master server from the NOM server and visa versa. Both with name and IP Address.
Does anyone know how the NOMWebsvr commiunicates with the NBU Master to add the server into the list?
is it TCP 13786? I see this in the log files...
Thanks
Trevor
Netbackup using VLAN's
Its official, you can configure VLANs over an aggregated NIC to increase throughput and save having the security issue of dual honed NICs.
Thanks Sun for a simple way of doing this, albeit hidden inside a 400 page document.... ;-)
We've got 8 NICs (well 11
We've got 8 NICs (well 11 actually) in each of 4 media servers. Each media server has one quad card on one LAN switch, and another quad card on the another LAN switch. Other NICs are for management etc. We use IPMP over both aggregates for failover, thus max of 4 Gb per media server, but I like the idea of dual active quad NIC aggregates.
Trevor, are you willing to post a link to the Sun doc that you found? Would I be asking too much for the page number too? :) Please?
VLAN Link Aggregation
@sdw303
Here is the simple way to create the VLAN link aggregation:
Modify your switch ports for the aggregation to include dot1q tagging and then configure your NICs as below:
ifconfig aggr[VLANID][Aggregation number] IPAddress/subnet plumb up
Create a hosname file in /etc containing the same IPaddress/subnet
For instance:
VLANID = 700
AGGREGATION = 1
IPADDRESS = 10.231.10.7
SUBNET = 27
(use 001 for Link Aggr1)
ifconfig aggr700001 10.231.10.7/27 plumb up
create a file called /etc/hostname.aggr700001 and put 10.231.10.7/27 inside.
This step has been found to be necessary as there is an issue with the e1000g driver we are currently using, so it may not be required, but it is suggested.
ifconfig aggr1 down
ifconfig aggr1 up
You should now be able to communicate with the VLAN 700 IPAddresses ;-)
Or of course, you this link... (http://docs.sun.com/app/docs/doc/816-4554/gifot?l=en&a=view&q=vlan+over+aggr)
Kind Regards,
Trevor
Thanks very much Trevor.
Thanks very much Trevor.
Your welcome
Your welcome
Would you like to reply?
Login or Register to post your comment.