This post is more than 5 years old
2 Intern
•
261 Posts
0
2113
February 9th, 2011 11:00
Management NIC card for celerra NAS
Can i put a management NIC card ( 172.18.48.XX) in one of our NAS blade servers ( D M) in order to interact with another network?
This is what the scenario is . We recently bought NS480 whose gate way IP( 172.18.16.81) is "customer 1 " 's aplication network (172.18.16.XX). i want to bring that to "customer 1" 's management network ( which is 172.18.48.0 255.255.240.0 network).
The whole purpose of doing this is to bring this Data mover gateway to talk to the backup server 67.204.92.X( customer 2)
My network guy made me understand that inorder to talk to customer2 my blade server ( NAS DM ) should have a management NIC card in 172.18.48.(which is customer 1 management network).
If i have this card in place i can easily talk to customer 2, other wise i can't.
My question how can i put NAS box in that network .Do i 've a set up for NIC.If yes, can I not reprovision an existing NIC for a Management connection?
Please suggest.
umichklewis_ac7b91
300 Posts
0
February 10th, 2011 04:00
Excellent - so you should be able to get your networking group to add 67.204.92.X to a Gigabit port, then connect it to cge2 or cge3. Once the port is connected, you'll have to make an interface with the server_ifconfig command or from the GUI. You can associate the new interface with Customer 2's CIFS server and allow access on that network. If you anticipate more customers with their own networks on your NAS, you should really consider asking the network group about VLAN tagging. Otherwise, you'll need to buy more network interfaces for your Celerra.
Thanks!
Karl
dynamox
9 Legend
•
20.4K Posts
0
February 9th, 2011 12:00
i am confused
..what do you mean by management network ? Are backups going over AUX connections ?
umichklewis_ac7b91
300 Posts
1
February 9th, 2011 12:00
Let's try this - how many physical interfaces and virtual interfaces do you have? server_sysconfig server_2 -pci will show you which network interfaces you have, then server_sysconfig server_2 -virtual will show you which virtual interfaces you've created:
[nasadmin@NS80-CS0 ~]$ server_sysconfig server_2 -pci
server_2 : PCI DEVICES:
On Board:
PLX PCI-Express Switch Controller
0: Port9 - Unused IRQ: 10
Neterion 10 Gigabit Ethernet Controller
0: fxg0 IRQ: 18
txflowctl=enable rxflowctl=enable
Slot: 1
Agilent QX4 Fibre Channel Controller
0: fcp-0 IRQ: 28 addr: 5006016039a04326
1: fcp-1 IRQ: 29 addr: 5006016139a04326
2: fcp-2 IRQ: 30 addr: 5006016239a04326
3: fcp-3 IRQ: 31 addr: 5006016339a04326
Slot: 4
Broadcom Gigabit Ethernet Controller
1: cge0 IRQ: 27
speed=1000 duplex=full txflowctl=disable rxflowctl=disable
On Board:
Broadcom Gigabit Ethernet Controller
0: cge1 IRQ: 21
speed=1000 duplex=full txflowctl=disable rxflowctl=disable
0: cge2 IRQ: 23
speed=1000 duplex=full txflowctl=disable rxflowctl=disable
Slot: 4
Broadcom Gigabit Ethernet Controller
0: cge3 IRQ: 26
speed=1000 duplex=full txflowctl=disable rxflowctl=disable
On Board:
Broadcom Gigabit Ethernet Controller
0: cge4 IRQ: 20
speed=1000 duplex=full txflowctl=disable rxflowctl=disable
0: cge5 IRQ: 22
speed=1000 duplex=full txflowctl=disable rxflowctl=disable
Slot: 3
Broadcom Gigabit Ethernet Controller
1: fge0 IRQ: 25
linkneg=enable txflowctl=disable rxflowctl=disable
0: fge1 IRQ: 24
linkneg=enable txflowctl=disable rxflowctl=disable
[nasadmin@NS80-CS0 ~]$ server_sysconfig server_2 -virtual
server_2 :
Virtual devices:
DM2_FS1 active=fxg0 primary=fxg0 standby=DM2_LA1
DM2_LA1 devices=cge0 cge1 :protocol=lacp
fsn failsafe nic devices : DM2_FS1
trk trunking devices : DM2_LA1
In my case, I have physical interfaces cge0-5 and fxg0 on server_2. We created a virtual interface DM2_LA1, consisting of cge0 and cge1, then made a virtual interface consisting of fxg0 (10Gb Ethernet) and DM2_LA1 (2x 1Gb). This leaves cge2 through cge5 available for other purposes - they could be used for other purposes or put on other networks. If you have unused physical interfaces, this could be what you need to do. Of course, if you've already used all of your physical interfaces already, you have to either A) destroy and recreate virtual interfaces or B) add another UltraFlex module to your Celerra NS480 to get more physical interaces.
I'm a little fuzzy on why you can't get IP 172.18.16.81 to talk to 67.204.92.X - do they have a routing rule or block that prevents traffic between those two networks? A firewall rule, perhaps?
Finally, is VLAN tagging an option? If your network group can provide VLAN tagging at the switch level, you might be able to use VLAN tagging to put the right traffic on the right network.
deeppat
2 Intern
•
261 Posts
0
February 9th, 2011 12:00
Hi Dynamox,
This Customer 1 has two networks in different subnets- application network / management network
Customer 1- application network , 172.18.16.81 , this has a certain range and 172.18.16.81 falls in it.
Customer 1 - Managment Network , 172.18.48.0/20, 172.18.8.0/21 , range for this network.
Now , the network guy is saying-Every server in this location to date has a Management NIC in the 172.18.48.XX.if I put the NAS box in that network I will be able to perform backups of all the customer servers without the box sitting in the customer Application network
67.204.92.x network can talk to 172.18.48.0 network
67.204.92.X network can't talk to 172.18.16.0
67.204.92.x--master server
and most probably we will have backups going from AUX ports.But. at this point , my DM cannot talk to the Backup server at all because of this diff network configuration.
Please let me know if i am clear this time..
deeppat
2 Intern
•
261 Posts
0
February 9th, 2011 12:00
Hi Karl,
"I'm a little fuzzy on why you can't get IP 172.18.16.81 to talk to 67.204.92.X - do they have a routing rule or block that prevents traffic between those two networks? A firewall rule, perhaps?"
Its the firewall ,the reason is, the network people 're not allowing customer 1 ( 172.18.16.81) interaction with customer 2 (67.204.92.X) for the security reasons. said , this set up cannot be changed.
from your explanation on top, if i 've free physical interface available , i can use them to have a NIC inserted. Please correct me if i am wrong.
I 'll try the steps you recommended and see how it goes. Thanks a lot! ..Karl
dynamox
9 Legend
•
20.4K Posts
1
February 9th, 2011 14:00
will they allow VLAN tagging ? If yes, then i would simply setup tagging on one of the interfaces so that it has access to both networks. When you assign ip addresses to interfaces you get to specify VLAN number they should be part off. This way you can drive your "meta data" traffic through that interface and all data traffic will go over your AUX ports.
deeppat
2 Intern
•
261 Posts
0
February 10th, 2011 04:00
Hello Karl,,
This is what i see -
server_sysconfig server_2 -pci
server_2 : PCI DEVICES:
On Board:
PLX PCI-Express Switch Controller
0: PLX PEX8516 IRQ: 11
Slot: 1
Agilent QX4 Fibre Channel Controller
0: fcp-0 IRQ: 24 addr: 5006016041e11b23
1: fcp-1 IRQ: 25 addr: 5006016141e11b23
2: fcp-2 IRQ: 26 addr: 5006016241e11b23
3: fcp-3 IRQ: 27 addr: 5006016341e11b23
Slot: 3
Broadcom Gigabit Ethernet Controller
0: cge0 IRQ: 22
speed=auto duplex=auto txflowctl=disable rxflowctl=disable
1: cge1 IRQ: 23
speed=auto duplex=auto txflowctl=disable rxflowctl=disable
Slot: 2
Broadcom Gigabit Ethernet Controller
0: cge2 IRQ: 20
speed=auto duplex=auto txflowctl=disable rxflowctl=disable
1: cge3 IRQ: 21
speed=auto duplex=auto txflowctl=disable rxflowctl=disable
server_sysconfig server_2 -v
server_2 :
Virtual devices:
fsn0 active=cge0 primary=cge0 standby=cge1
fsn failsafe nic devices : fsn0
trk trunking devices :
so i 've cge 2 and cge 3 as free ports , and i don't see trunking enabled. It's just the FSN configured