UNSOLVED
S
saranraj456
1 Rookie
•
108 Posts
0
998
August 15th, 2015 05:00
How the Virtual interface in Celerra works
Hi Folks,
Generally, we use to create a multiple logical interface on top of the physical interface. Virtual interface IP would be on same Subnet & also we have a unique MAC addr for all this interface. I am wondering , how it does really filter the traffic to each and every virtual interface.
Ex: Below three interfaces are from same physical interface called CGE1-2 with same MAC addr. However each interface belongs to different CIFS servers and user groups.
1a protocol=IP device=cge-1-2
inet=10.218.100.10 netmask=255.255.255.0 broadcast=10.218.100.255
UP, Ethernet, mtu=1500, vlan=0, macaddr=0:60:48:1f:a9:d2
1b protocol=IP device=cge-1-2
inet=10.218.100.11 netmask=255.255.255.0 broadcast=10.218.100.255
UP, Ethernet, mtu=1500, vlan=0, macaddr=0:60:48:1f:a9:d2
1c protocol=IP device=cge-1-2
inet=10.218.100.12 netmask=255.255.255.0 broadcast=10.218.100.255
UP, Ethernet, mtu=1500, vlan=0, macaddr=0:60:48:1f:a9:d2
Still scratching my head ,how the Celerra will be able differentiate the traffic
Thanks
Saran
361
0
Posted December 21st, 2015 11:00
Normally just wonder about the basics of Trunk port concept, why the VLAN tagging can be used on trunk port not on access port or single port ?
Thanks
Saran
361
0
Posted December 21st, 2015 15:00
Hi,
you need to differentiate between devices and interfaces.
Physical ports and trunks / FSNs are devices (Layer 2)
Each device can VLAN tagging with 803.1q
Of course you can also use VLAN tagging on a single NIC port
Interfaces are layer 3 (IP address) – they can be in a VLAN (or default 0)
See server_sysconfig vs. server_ifconfig
More details are in the two Celerra/VNX networking manuals available on support.emc.com
Rainer_EMC
6 Operator
•
8645 Posts
361
1
Posted August 17th, 2015 01:00
Hi,
not sure what you mean.
As a server the VNX mostly gets inbound traffic or send replies back according to inbound traffic.
For CIFS an interface is bound to a CIFS server – if you send CIFS requests to that CIFS servers IP it will be received in that context and sent out with its IP as src using the underlying physical interface.
By default we also have packet reflect active – which sends a reply back through the same interface that the request for it came in.
For other unsolicited traffic – if there are multiple interfaces for the same subnet the VNX uses the first interface in the routing table.
Rainer