Browse Community
Help
Log In
Responses(4)
Solutions(0)
admingirl
2 Intern
•
614 Posts
0
September 6th, 2016 10:00
Server Side
root@efsdzadmclient0101:~# rpcinfo -u localhost rpcbind
program 100000 version 2 ready and waiting
program 100000 version 3 ready and waiting
program 100000 version 4 ready and waiting
root@efsdzadmclient0101:~# rpcinfo -u localhost mountd
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting
root@efsdzadmclient0101:~# rpcinfo -u localhost nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
root@efsdzadmclient0101:~#
Client Side
export list for 10.129.171.110:
/DB_Backup/backup (everyone)
/export/oesinstall/IPS-repos (everyone)
root@efsdzadmclient0201:~#
10.129.171.110
root@efsdzadmclient0201:~# rpcinfo -u 10.129.171.110 mountd
root@efsdzadmclient0201:~# rpcinfo -u 10.129.171.110 rpcbind
efsdzadmclient0101 acting as client for the 10.129.226.16 server (THIS IS THE ARRAY VNX DATA MOVER)
root@efsdzadmclient0101:~# rpcinfo -u 10.129.226.16 mountd
rpcinfo: RPC: Timed out
program 100005 version 0 is not available
root@efsdzadmclient0101:~# rpcinfo -u 10.129.226.16 rpcbind
rpcinfo: RPC: Program not registered
program 100000 version 3 is not available
September 7th, 2016 08:00
I believe it is a T5-8
zhaos2
643 Posts
Is your Super Cluster M7? below is the network diagram might be help:
Has anyone in this group done this before??
We were able to validate that network and VNX side traffic are fine.
Yet the Oracle Team cannot mount this file system.
Dell Support Resources
View All
Top
admingirl
2 Intern
•
614 Posts
0
September 6th, 2016 10:00
Server Side
root@efsdzadmclient0101:~# rpcinfo -u localhost rpcbind
program 100000 version 2 ready and waiting
program 100000 version 3 ready and waiting
program 100000 version 4 ready and waiting
root@efsdzadmclient0101:~# rpcinfo -u localhost mountd
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting
root@efsdzadmclient0101:~# rpcinfo -u localhost nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
root@efsdzadmclient0101:~#
Client Side
export list for 10.129.171.110:
/DB_Backup/backup (everyone)
/export/oesinstall/IPS-repos (everyone)
root@efsdzadmclient0201:~#
10.129.171.110
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
root@efsdzadmclient0201:~# rpcinfo -u 10.129.171.110 mountd
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting
root@efsdzadmclient0201:~# rpcinfo -u 10.129.171.110 rpcbind
program 100000 version 2 ready and waiting
program 100000 version 3 ready and waiting
program 100000 version 4 ready and waiting
root@efsdzadmclient0201:~#
efsdzadmclient0101 acting as client for the 10.129.226.16 server (THIS IS THE ARRAY VNX DATA MOVER)
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
root@efsdzadmclient0101:~# rpcinfo -u 10.129.226.16 mountd
rpcinfo: RPC: Timed out
program 100005 version 0 is not available
root@efsdzadmclient0101:~# rpcinfo -u 10.129.226.16 rpcbind
program 100000 version 2 ready and waiting
rpcinfo: RPC: Program not registered
program 100000 version 3 is not available
root@efsdzadmclient0101:~#
admingirl
2 Intern
•
614 Posts
0
September 7th, 2016 08:00
I believe it is a T5-8
zhaos2
2 Intern
•
643 Posts
0
September 7th, 2016 08:00
Is your Super Cluster M7? below is the network diagram might be help:
admingirl
2 Intern
•
614 Posts
0
September 7th, 2016 08:00
Has anyone in this group done this before??
We were able to validate that network and VNX side traffic are fine.
Yet the Oracle Team cannot mount this file system.