Query Regarding NAS Network Ports Profile
Radek Novacek
rnovacek at redhat.com
Mon Oct 7 11:22:35 UTC 2013
On Mon 07 of Oct 2013 16:46:38 sunil kumar wrote:
> On Mon, Oct 7, 2013 at 1:31 PM, Radek Novacek <rnovacek at redhat.com> wrote:
> > On Mon 07 of Oct 2013 11:28:26 sunil kumar wrote:
> > > Hi,
> > >
> > > We are implementing "NAS Networt Ports profile", Starting with
> > >
> > > ProtocolEndpoint class. i have some query according to DMTF standards
> > > NFS
> > > port is 4200,
> >
> > Where did you find that NFS is on port 4200? Do you mean value 4200 (=
> > NFS) of
> > property ProtocolIFType from CIM_ProtocolEndpoint class? That's not a port
> > number, it's just internal value that specify that given
> > CIM_ProtocolEndpoint
> > is a NFS.
> >
> > > But when i check "netstat -ntlp" command i got rpcbind is
> > > running on port 111, rpc.mountd runnig on port 20048 etc.
> > >
> > > tcp 0 0 0.0.0.0:875 0.0.0.0:* LISTEN 3318/rpc.rquotad
> > > tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 818/rpcbind
> > > tcp 0 0 0.0.0.0:20048 0.0.0.0:* LISTEN 3320/rpc.mountd
> > >
> > > my question is even if i write code (LMI_ProtocolEndpoint) how it will
> > > detect?
> > >
> > > Do we have to set protocolIFtype 4200 to a network adapter(p7p1,
> >
> > eth0...) ?
> >
> > > Do we have to implement "ProtocolIFType" property in association
> > > (LMI_DeviceSAPImplementation) between LMI_ProtocolEndpoint and
> > > LMI_NetworkPort. Or we have to simply define ProtocolIFType = 4200 in
> > > LMI_ProtocolEndpoint?
> >
> > I think you should subclass CIM_ProtocolEndpoint and make one instance for
> > each NFS share on the given system. Then subclass
> > CIM_DeviceSAPImplementation
> > to associate these ProtocolEndpoints to existing LMI_NetworkPorts.
>
> is LMI_NetworkPorts is already implemented ? or we need to create and
> then associate?
OpenLMI-Networking implements LMI_EthernetPort class, that is inherited from
CIM_EthernetPort and that one is inherited from CIM_NetworkPort.
So no, you don't need to implement it, you just need to implement the
association.
Radek Novacek
More information about the openlmi-devel
mailing list