topic Re: vfiler setup issue in ONTAP Discussions

vfiler setup issue

SKC64750 — Thu, 05 Jun 2025 06:25:25 GMT

Hii, There is a node fdlr whose ip starts with 172.31 serving to JD domain..and I have to setup a new vfiler to serve data for another domain called Nor domain (192.168).

There is an existing vif1 (where e0a is up, e0a is down) which is used as filer interface. So I have created a vlan 400 serving for vfiler, so I created vlan, ipspace,assigned vif1-400 to ipspace, created vfiler, assigned the vfiler ip to vlan 400 by ifconfig and then did default route from vfiler to the gateway of switch.

After the above creation process, vfiler was able to talk to Nor-domain switch or gateway, filer wasnt able to talk to JD domain switch, and the server team were not able to access there CIFS shares from the filer before I want to setup cifs for vfiler.

So was wondering what might be the issue. Hope anyone assists me on this

Vif1– original ip of the fdlr filer (JD domain)

Vif1-400- vfiler vlan (Nor-domain)

Thanks,

Karthik

Re: vfiler setup issue

scottgelb — Fri, 08 Jun 2012 17:06:53 GMT

Are you on ONTAP 8? Prior to ONTAP 8 if you have a VLAN you can't assign an ip to the base interface...that changed with 8.x though. If you are on 8.x then some troubleshooting with netstat -rn on vfiler0 and the vfiler.

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 17:14:16 GMT

Yes I m on 8.0.2 P3 only. So what should I change in netstat –rn to make filer talk with JD domain (172.31) and vfiler talk to Nor domain..is it default route..if so can you help me what needs to be changed exactly.

Thanks,

Karthik

Re: vfiler setup issue

scottgelb — Fri, 08 Jun 2012 17:23:53 GMT

Make sure your vfiler0 interface is up and has a route

Sent from my iPhone 4S

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 17:50:19 GMT

The vfiler0 is up and running I hope as per below, when I give vif status, it shows me that e0a is up but e0a is down. Does this have anything to do with it.

Also, do we need to add the route in netstat –rn for vfiler fdvnor to nor domain gateway also.

fdlr1> netstat -rn

Routing tables

Internet:

Destination Gateway Flags Refs Use Interface

default 172.31.180.1 UGS 4610 526433 vif1

Thanks,

Karthik

Re: vfiler setup issue

scottgelb — Fri, 08 Jun 2012 17:53:19 GMT

Not sure what the issue is if up and down. Switch side? Your default route is there do that looks ok. Can the switch handle a tagged and utagged interface or is it configured on handle it?

Sent from my iPhone 4S

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 18:13:09 GMT

I think the interface is up, and has a default route. The switch supports vlan tagging in our envi. Also, there is a native vlan 300 on the switch itseems which supports fldrn filer. So they are asking do we need to configure this vlan 300 on filer ??

Thanks,

Karthik

Re: vfiler setup issue

scottgelb — Fri, 08 Jun 2012 18:47:24 GMT

Depends. It worked before you added the vlan. Sounds suspicious that it stops working untagged when you add a tagged vlan.

Sent from my iPhone 4S

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 19:12:01 GMT

This is the port configurations on our switch right now:

interface GigabitEthernet2/13

description FDLRNAS01_PortGroup#1.1

switchport

switchport trunk encapsulation dot1q

switchport trunk native vlan 300

switchport trunk allowed vlan 300,339,340,413

switchport mode trunk

no ip address

speed 1000

duplex full

no cdp enable

As you can see above that there is native vlan 300. Do we need to setup on the filer fdlrn??. Actually i tried doing it, but had a doubt since it dint work that way too.

vif1 originally has 172.31.190.21 (During this time the users were able to access cifs shares)..Took downtime, I created vif1-300 and then assigned 172.31.190.37 (some address in the vlan 300 subnet) to vif1 and 172.31.190.21 (which is actual filer ip for communication) to vif1-300 and it did not allowed any communication to happen from the switch when pining or users were not able to see any cifs shares. Later, we backed off and put back to original where users were able to see cifs shares. Then I thought it dint worked since I dint added vif1-300 default route to gateway in the routing table So, creating vlan 300 on filer is right?? and would adding vif1-300 also in the routing table will able to allow users to see cifs shares??

fdlrn> netstat -rn

Routing tables

Internet:

Destination Gateway Flags Refs Use Interface

default 172.31.190.1 UGS 5710 523433 vif1

Thanks,

Karthik

Re: vfiler setup issue

VKALVEMULA — Fri, 08 Jun 2012 19:42:16 GMT

can you paste the /etc/rc file info

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 19:52:16 GMT

#Regenerated by registry Fri Oct 07 06:59:17 CDT 2011

#Auto-generated by cifs setup Mon Apr 25 11:01:24 CDT 2011

#Auto-generated by setup Wed Apr 13 16:03:47 CDT 2011

hostname fdlrnas01

vif create single vif1 e0b e0a

ifconfig vif1 `hostname`-vif1 mediatype auto netmask 255.255.254.0 partner vif1

ifconfig e0M `hostname`-e0M netmask 255.255.255.0 mtusize 1500 -wins flowcontrol full

ifconfig e0P `hostname`-e0P netmask 255.255.252.0 mtusize 1500 -wins flowcontrol full

ifconfig e0M 192.168.83.188

route add default 172.31.190.1 1

route add 204.53.19.105 192.168.83.254 2

routed on

options dns.enable on

options nis.enable off

savecore

Thanks,

Karthik

Re: vfiler setup issue

scottgelb — Fri, 08 Jun 2012 20:03:05 GMT

Where is the vlan? You ran manually an not in rc?

Sent from my iPhone 4S

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 20:06:05 GMT

Yes I ran it manually and I did not do failover so I dint updated in rc file yet.

Re: vfiler setup issue

scottgelb — Fri, 08 Jun 2012 20:25:55 GMT

Can you post ifconfig -a , Ifgrp status, vlan status, vfiler status -a an vfiler run * netstat -rn

Sent from my iPhone 4S

Re: vfiler setup issue

SKC64750 — Fri, 08 Jun 2012 20:34:56 GMT

I have posted the vlan stat of fdlrn02, as vlan got removed on fdlrnas01 by itself, don’t know whats the reason??

fdlrn01> ifconfig -a

e0a: flags=0xaf4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

ether 02:a0:98:14:a3:92 (auto-1000t-fd-up) flowcontrol full

trunked vif1

e0b: flags=0xaf4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

ether 02:a0:98:14:a3:92 (auto-1000t-fd-up) flowcontrol full

trunked vif1

c0a: flags=0x174c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000 PRIVATE

inet 192.168.1.173 netmask 0xffffff00 broadcast 192.168.1.255

ether 00:a0:98:14:a3:94 (auto-unknown-enabling) flowcontrol full

c0b: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000 PRIVATE

inet 192.168.2.176 netmask 0xffffff00 broadcast 192.168.2.255

ether 00:a0:98:14:a3:95 (auto-10g_kr-fd-up) flowcontrol full

e0M: flags=0x6b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500

inet 192.168.83.188 netmask 0xffffff00 broadcast 192.168.83.255

ether 00:a0:98:14:a3:96 (auto-100tx-fd-up) flowcontrol full

e0P: flags=0x6b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500

inet 192.168.0.155 netmask 0xfffffc00 broadcast 192.168.3.255

ether 00:a0:98:14:a3:97 (auto-100tx-fd-up) flowcontrol full

lo: flags=0x1b48049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160

inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1

ether 00:00:00:00:00:00 (RNIC Provider)

losk: flags=0x40a400c9<UP,LOOPBACK,RUNNING> mtu 9188

inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1

vif1: flags=0x22f4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

inet 172.31.190.21 netmask 0xfffffe00 broadcast 172.31.191.255

partner vif1 (not in use)

ether 02:a0:98:14:a3:92 (Enabled interface groups)

fdlrn01> ifgrp status

default: transmit 'IP Load balancing', Ifgrp Type 'multi_mode', fail 'log'

vif1: 1 link, transmit 'none', Ifgrp Type 'single_mode' fail 'default'

Ifgrp Status Up Addr_set

up:

e0a: state up, since 08Jun2012 00:12:41 (15:14:50)

mediatype: auto-1000t-fd-up

flags: enabled

input packets 141635613, input bytes 46181889738

output packets 159014098, output bytes 81899071833

output probe packets 9148, input probe packets 9148

strike count: 0 of 10

up indications 1, broken indications 0

drops (if) 0, drops (link) 0

indication: up at 08Jun2012 00:12:41

consecutive 54887, transitions 1

down:

e0b: state down, since 08Jun2012 00:12:41 (15:14:50)

mediatype: auto-1000t-fd-up

flags: enabled

input packets 160953, input bytes 13059671

output packets 9148, output bytes 384216

output probe packets 9148, input probe packets 9148

strike count: 0 of 10

up indications 1, broken indications 0

drops (if) 0, drops (link) 0

indication: up at 08Jun2012 00:12:41

consecutive 54887, transitions 1

fdlrnas01> vfiler status -a

vfiler0 running

ipspace: default-ipspace

IP address: 172.31.190.21

IP address: 192.168.83.188

IP address: 192.168.0.155

Path: /

UUID: 00000000-0000-0000-0000-000000000000

Protocols allowed: 7

Allowed: proto=rsh

Allowed: proto=ssh

Allowed: proto=nfs

Allowed: proto=cifs

Allowed: proto=iscsi

Allowed: proto=ftp

Allowed: proto=http

Protocols disallowed: 0

fdvnor1 running

ipspace: fdvnor1_ipspace

IP address: 192.168.45.251

Path: /vol/fdvnor1_root

UUID: 5986bc64-a517-11e1-adf1-00a09814a392

Protocols allowed: 7

Allowed: proto=rsh

Allowed: proto=ssh

Allowed: proto=nfs

Allowed: proto=cifs

Allowed: proto=iscsi

Allowed: proto=ftp

Allowed: proto=http

Protocols disallowed: 0

fdlrn01> netstat -rn

Routing tables

Internet:

Destination Gateway Flags Refs Use Interface

default 172.31.190.1 UGS 6016 811949 vif1

127 127.0.0.1 UGS 0 0 lo

127.0.0.1 127.0.0.1 UH 3 13 lo

127.0.10.1 127.0.20.1 UHS 2 52 losk

127.0.20.1 127.0.20.1 UH 0 0 losk

172.31.190/23 link#10 UC 0 0 vif1

172.31.190.1 0:19:a9:3e:d4:0 UHL 1 0 vif1

172.31.190.9 0:18:fe:71:41:cd UHL 1 127 vif1

172.31.190.10 d4:85:64:cb:84:1c UHL 1 28 vif1

172.31.190.11 d8:d3:85:b0:7d:54 UHL 1 68 vif1

172.31.190.12 d4:85:64:cb:92:7c UHL 1 32 vif1

172.31.190.13 0:50:56:9f:e:f9 UHL 0 96 vif1

172.31.190.24 0:1e:b:74:e4:4a UHL 0 0 vif1

172.31.190.26 d8:d3:85:5c:5c:2c UHL 1 0 vif1

172.31.190.27 b4:99:ba:aa:7a:c2 UHL 0 0 vif1

172.31.190.29 18:a9:5:6f:e2:8e UHL 1 0 vif1

172.31.190.31 d8:d3:85:5f:b9:38 UHL 1 20 vif1

172.31.190.34 0:50:56:a3:32:39 UHL 3 0 vif1

172.31.190.70 0:1b:78:9b:b1:ca UHL 0 30 vif1

172.31.190.127 0:50:56:bd:69:38 UHL 0 9 vif1

172.31.190.164 0:50:56:bd:55:ec UHL 0 0 vif1

172.31.190.180 0:16:35:6c:bc:a9 UHL 2 316 vif1

172.31.190.181 0:50:56:bd:67:f7 UHL 6 26 vif1

172.31.190.200 0:21:5a:cf:53:36 UHL 0 2 vif1

172.31.191.255 ff:ff:ff:ff:ff:ff UHL 0 85 vif1

192.168/22 link#6 UC 0 0 e0P

192.168.3.255 ff:ff:ff:ff:ff:ff UHL 0 85 e0P

192.168.83 link#5 UC 0 0 e0M

192.168.83.187 0:a0:98:14:a8:30 UHL 0 1 e0M

192.168.83.188 0:a0:98:14:a3:96 UHL 0 180 lo

192.168.83.252 0:26:98:20:f5:c2 UHL 0 0 e0M

192.168.83.253 0:26:98:1c:f4:42 UHL 0 0 e0M

192.168.83.254 0:0:c:7:ac:16 UHL 1 0 e0M

192.168.83.255 ff:ff:ff:ff:ff:ff UHL 0 85 e0M

204.53.19.105 192.168.83.254 UGHS 0 72117 e0M

fdlrn02> vlan stat

Vlan Physical Interface: vif1 () --

Vlan IDs: 413

GVRP: disabled

RECEIVE STATISTICS

Total frames: 425m | Total bytes: 146g | Multi/broadcast: 7052k

Untag drops: 0 | Vlan tag drops: 45996

TRANSMIT STATISTICS

Total frames: 460m | Total bytes: 226g

Vlan Interface: vif1-413 () --

ID: 413

MAC Address: 02:a0:98:14:a8:2a

RECEIVE STATISTICS

Total frames: 85084 | Total bytes: 6098k | Multi/broadcast: 0

TRANSMIT STATISTICS

Total frames: 0 | Total bytes: 0 | Multi/broadcast: 0

Queue overflows: 0

fdlrnas01> vfiler run fdvnor1 netstat -rn

===== fdvnor1

Routing tables

Internet:

Destination Gateway Flags Refs Use Interface

Thanks,

Karthik

Re: vfiler setup issue

VKALVEMULA — Fri, 08 Jun 2012 21:51:15 GMT

in your rc file .. second vif is missing.. update that..

also keep your routed as off..

Re: vfiler setup issue

SKC64750 — Sat, 09 Jun 2012 00:20:15 GMT

Did you mean vif1-413..if so i already said vlan 413 got vanished after reboot..it is on fdlrnas02.