Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

multiple vlans for 10Gb Ethernet ports on Netbackup 5220 appliance

Created: 18 Feb 2013 • Updated: 06 May 2013 | 14 comments
This issue has been solved. See solution.

All,

I have a NetBackup 5220 appliance. It has 2 x 10Gb Ethernet Ports. Can I add these to multiple VLANs for backup?

My network has many VLANs. 3 for Storage and 10 for actual Server access.

My thinking here is trunk the 10Gb Ethernet Ports and put into multiple VLANs.

The NetBackup Appliance is Suse Linux which does support multiple VLANs on single NICs but does NetBackup support this?

Best Regards,

Kevin.

Discussion Filed Under:

Comments 14 CommentsJump to latest comment

Nicolai's picture

I don't know if Symantec will support the use of 802.1Q VLAN tagging on the 5220. But I have run 802.1Q for years on SUSE 10 master server. Work really good and stable.

Seen from the Netrbackup side there isn't really much to say. It's just a host with many "network cards".  Being in control of routing and DNS names of each interface is paramount.

We usally apply a VLAN number to each NIC (VLAN). E.g. if master server is called server.acme.com - we will call the interfaces connected to VLAN 111 server-VLAN111.acme.com.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Galtryn's picture

Hi Ksmith169,

Did you get anywhere with this? we are considering using the same approach on one of our platforms and have been looking for info with regards to this.

Ksmith169's picture

Hi Galtryn,

No unfortunately. VLAN tagging is not supported by the NetBackup Appliance. A big shame in particular when there are 10Gb Ethernet ports.

I am now going to seperate things out have have 2 x 10Gb E for storage and 4 x 1 Gb E for other VLANs. I will define each with its own IP address / VLAN. This way I can ensure backup traffic flows correctly.

K.

Andrew Madsen's picture

This is how we have our 5220 configured:

vlan64    Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.16.30.1  Bcast:172.16.30.255  Mask:255.255.255.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:128382295 errors:0 dropped:0 overruns:0 frame:0
          TX packets:91954918 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:598348447684 (570629.5 Mb)  TX bytes:11774552196 (11229.0 Mb)

vlan101   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.16.101.22  Bcast:172.16.101.255  Mask:255.255.255.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24351 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1120146 (1.0 Mb)  TX bytes:3307 (3.2 Kb)

vlan102   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.16.102.129  Bcast:172.16.102.255  Mask:255.255.255.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5119084641 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3883168458 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:27892095246860 (26599974.8 Mb)  TX bytes:256289356280 (244416.5 Mb)

vlan165   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.17.65.78  Bcast:172.17.65.255  Mask:255.255.255.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2294915 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:251933417 (240.2 Mb)  TX bytes:4315 (4.2 Kb)

vlan167   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.17.8.28  Bcast:172.17.15.255  Mask:255.255.248.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16095472 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1698043591 (1619.3 Mb)  TX bytes:3307 (3.2 Kb)

vlan701   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.17.68.17  Bcast:172.17.71.255  Mask:255.255.252.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:413553 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1023 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:28336269 (27.0 Mb)  TX bytes:72877 (71.1 Kb)

vlan702   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.17.72.27  Bcast:172.17.75.255  Mask:255.255.252.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:510522 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:73510892 (70.1 Mb)  TX bytes:532 (532.0 b)

vlan703   Link encap:Ethernet  HWaddr 90:E2:BA:16:DD:A8 
          inet addr:172.17.76.32  Bcast:172.17.79.255  Mask:255.255.252.0
          inet6 addr: fe80::92e2:baff:fe16:dda8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:246656 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:38458360 (36.6 Mb)  TX bytes:532 (532.0 b)

lines 51-120/120 (END)

The above comments are not to be construed as an official stance of the company I work for; hell half the time they are not even an official stance for me.

SOLUTION
Ksmith169's picture

Hi Wolfsbane,

Wow! This looks good. So you have multiple VLANs on single physical interface. Does it work ok? I was told by resller and in another discussion that VLAN tagging not supported on NetApp 5220 Appliance.

Have you got backup data flowing across these VLANs? Any further detail much appreciated.

Thanks,

 

Kevin.

Andrew Madsen's picture

We have data flowing from each subnet to the 5220 with no issue.

The above comments are not to be construed as an official stance of the company I work for; hell half the time they are not even an official stance for me.

Galtryn's picture

Hi Wolfsbane,

Have you had any issues logging support cases with Symantec or applying updates  to the appliance.

Thanks

Nick

Ryan-4SL's picture

VLAN tagging is not configurable from the appliance's menu driven interface. It is something you will have to switch into the maintenance shell to configure, which Symantec don't want you to do.

Therefore, although it is configurable from a SuSE perspective, I guess Symantec will view it as a non-standard configuration and will provide limited, if any, configuration or troubleshooting support for the feature.

I doubt it will invalidate support on the appliance as a whole, or for your NetBackup configuration - it may only cause an issue if VLAN tagging is suspected to be contributing to an issue you are experiencing.

Andrew Madsen's picture

Actually, they do not look at it as that. We just finished a health check and an upgrade to 2.5.1 with this configuration and both passed. The only caution they have given us was to copy the route tables prior to a major upgrade so we do not have to go through the same thing if it was to get blown out and we have no issue with that.  

 

Yes we had to break into the maintainance shell to configure the VLAN settings.

The above comments are not to be construed as an official stance of the company I work for; hell half the time they are not even an official stance for me.

Ksmith169's picture

Thanks All, Especially Wolfsbane.

I found the following document "DedupAppSW_Admin_Guide.pdf" at this link http://www.symantec.com/business/support/index?pag.... I have also attached it here.

All of chapter 6 is about VLAN support so I can only assume based on this and Wolfsbane comments re:health check that it is supported.

I am going to implement this. I will post back any major findings.

Best Regards,

Kevin.

AttachmentSize
DedupAppSW_Admin_Guide.pdf 2.12 MB
CRZ's picture

Kevin and all, please be aware that you are linking a 5000/5020 Appliance Guide and not a 5200/5220 Appliance Guide.  Not all Appliances are equal!

As I write this response, this is still not a supported configuration on a 5220.


bit.ly/76LBN | APPLBN | 75LBN

Andrew Madsen's picture

Chris,

 

The message then needs to get out to ALL of Symantec not just a few in the know. We had a two week engagement for a helath check and using VLANS was not mentioned as a bad thing. In fact we were told it is fine but be sure to save the configuration because future upgrades may wipe it out.  So either it is or it is not a supported feature.

The above comments are not to be construed as an official stance of the company I work for; hell half the time they are not even an official stance for me.

CRZ's picture

I'm not sure how to be more clear.  It is not supported now and has not been supported.  I won't speculate on future plans but I can tell you for sure that RIGHT NOW if you call Support with 5220 VLAN problems, we will tell you that unfortunately we can't help.

I try to be very careful when I'm speaking as an employee of Symantec - lots of things may be possible, but I can only speak to the stuff that is supported.

If you don't mind, Wolfsbane, could you please drop me a private message letting me know who told you it was fine so I can try to make sure they know it is not?


bit.ly/76LBN | APPLBN | 75LBN

Ksmith169's picture

Hi Chris,

Thanks for clarity but this does contradict Wolfsbanes experience and health check results. It also a serious limitation on the new NetBackup Appliance especially considering it is Suse Linux.

How are customers to get the best use out of 10Gb Ethernet ports if they cannot get connected to multiple VLANs? This just makes no sense. All customers of any reasonable size are going to have multiple vlans that require backup traffic to flow to and from.

How does Symantec suggest customers solve this problem without support for VLANs?

The only way I can see is to create a single backup VLAN and change ALL clients to have interfaces on that VLAN. This may not always be possible depending on clients OS and installed network cards. It can also pose security threats. It also means all clients must change compared to single device change of VLANs supported on appliance.

If a customer installed there own NetBackup Server (hardware and OS) they could configure VLANs. It is the sensible thing to do.

If we create VLANs will all other aspects of set-up be supported apart from any VLAN issues. To be frank VLANs tend to work and in general any issues are at the network stack.

Best Regards,

Kevin.