RE: Pegasus in-built SLP not stable

Venkateswara R Puvvada <[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <OF0CE334D9.4DF8BAD3-ON652576C0.003E382D-652576C0.003F7796@in.ibm.com> 
Biswapratap,

I don't  think there is limitation for SLP advertisements  on Windows. 
slp_attrreq works on windows without any problems in my test environment. 
It may also depends on UDP packet fragmentation. Verify if  registered 
profiles  are causing the problem when you see no output. As other SLP 
Template attributes are mostly constant, if  there are more  registered 
profiles, chances are that it may cross MTU .

Venkat




<[email protected]> 
04/02/2010 16:40

To
Venkateswara R Puvvada/India/IBM@IBMIN
cc
<[email protected]>, <[email protected]>, 
<[email protected]>, <[email protected]>, 
<[email protected]>
Subject
RE: Pegasus in-built SLP not stable






Hi Venkateswara,
 
Thanks a lot for your reply. I have already encountered the same issue you 
are talking about, in linux pegasus (whose MTU size is much lower), and I 
was also able to get the attributes explicitly using slp_attrreq command.
 
The issue I mentioned in my previous mail, is in windows pegasus and 
slp_attrreq is also not working in this case, though the same 
implementation works fine for linux pegasus using slp_attrreq command.
 
Is there any special limitation with windows pegasus in case when the 
advertisement length exceeds its MTU size or something like that? means, 
its not like I am never able to receive the advertisements, its like 
inconsistent behaviour, sometimes I am able to get the full advertisement, 
sometimes only the service and sometimes nothing at all (not even the 
service).
 
Regards,
Biswapratap,
Wipro Technologies.
 

From: Venkateswara R Puvvada [mailto:[email protected]] 
Sent: Thursday, February 04, 2010 4:17 PM
To: Biswapratap Chatterjee (WT01 - Semi Conductor and Peripheral IPG)
Cc: Partha Protim porel (WT01 - Semi Conductor and Peripheral IPG); 
[email protected]; Sijo Cherian Kappen (WT01 - Semi Conductor and 
Peripheral IPG); Souvik Roy (WT01 - Semi Conductor and Peripheral IPG); 
[email protected]
Subject: Re: Pegasus in-built SLP not stable


> 
>Even if everything goes fine without any error anywhere, why is - 
"slp_query --type=service:wbem" command giving inconsistent results? that 
is, sometimes I >am not able to get any output, sometimes I am able to get 
only the service as the output without any attributes and sometime I get 
correct output i.e. with all >attributes. 
> 

URLs may not be advertised immediately  after CIMServer startup because it 
may take a while to start the internal SLP service listener. If URLs are 
advertised without attributes, it means that total interface specific 
advertisement length exceeds MTU (Pegasus default 4096). In this case 
attributes can be get with explicit request using slp_attreq command. 


Venkat



<[email protected]> 
02/02/2010 20:59 


To
<[email protected]>, <[email protected]> 
cc
<[email protected]>, <[email protected]>, <[email protected]> 
Subject
Pegasus in-built SLP not stable








Hi all, 
  
I was debugging pegasus's in-built SLP implementation as it was behaving 
abruptly. The following is my understanding - 
 

  
The issueSLPRegistrations method calls the populateSLPRegistrations method 
which then calls the populateRegistrationData method. The 
populateRegistrationData method takes the following input from the 
populateSLPRegistrations method - 
  
1. first instance of all instances (class PG_ObjectManager) in 
root/PG_InterOp namespace, and 
2. each instance of all instances (class 
CIM_ObjectManagerCommunicationMechanism) in root/PG_InterOp namespace. (as 
many CIMXML communication types http, https etc) 
  
that means, if there are are 'n' number of communicationMechansims for the 
ObjectManager than 'n' Registration data will be advertised through SLP. 
  
If the RegistrationData (service) obtained in populateRegistrationData 
method is successfully registered with the service agent, then the method 
will return true else false. Based on the truth value, the 
populateSLPRegistrations method will count the number of successful 
registrations and return the total number of successful registrations to 
the issueSLPRegistration method. In issueSLPRegistration method, if the 
total number of successful registrations with the service agent is more 
than zero, than it starts the service agent's listener. 
  
I have the following outputs at various stages - 
  
I have 2 CIM-XML communication mechanisms - http://10.141.46.190:5988, 
https://10.141.46.190:5989 
  
1. populateRegistrationData 
  
TEST_REG: ServiceId service:wbem:http://10.141.46.190:5988 
  
serviceName: wbem 
  
TEMPLATE = 
(template-url-syntax=http://10.141.46.190:5988),(service-id=PG:126502
3706542-127-0-0-1),(service-hi-name=Pegasus),(service-hi-description=Pegasus 
CIM
Server Version 
2.9.1),(template-type=wbem),(template-version=1.0),(template-des
cription=This template describes the attributes used for advertising 
Pegasus CIM
Servers.),(InteropSchemaNamespace=root/PG_InterOp),(FunctionalProfilesSupported
=Basic Read,Basic Write,Schema Manipulation,Instance 
Manipulation,Association Tr
aversal,Qualifier 
Declaration,Indications),(MultipleOperationsSupported=FALSE),(
AuthenticationMechanismsSupported=Basic),(AuthenticationMechanismDescriptions=Ba
sic),(CommunicationMechanism=CIM-XML),(ProtocolVersion=1.0),(Namespace=root/PG_I
nterOp,root/PG_Internal,root/pmc/maxRAID/smi_14,root/cimv2,root),(RegisteredProf
ilesSupported=SNIA:Server,SNIA:Host Hardware RAID Controller,SNIA:Host 
Hardware
RAID Controller:Software,SNIA:Host Hardware RAID 
Controller:Battery,DMTF:Physica
l Asset,SNIA:Host Hardware RAID Controller:JobControl,SNIA:Host Hardware 
RAID Co
ntroller:Extent Composition,DMTF:Battery,SNIA:Host Hardware RAID 
Controller:SAS
Initiator Ports,SNIA:Host Hardware RAID Controller:Disk Drive 
Lite,SNIA:Host Har
dware RAID Controller:Physical Asset,DMTF:Physical Asset:Host Hardware 
RAID Cont
roller,DMTF:Profile Registration,SNIA:Host Hardware RAID Controller:Block 
Servic
es,SNIA:Host Hardware RAID Controller:Disk Sparing,SNIA:Host Hardware RAID 
Contr
oller:Indication,SNIA:Server:Indication,SNIA:Host Hardware RAID 
Controller:Devic
eCredentials,DMTF:Battery:Host Hardware RAID Controller,SNIA:Host Hardware 
RAID
Controller:DA Target Ports,SNIA:Profile 
Registration,SNIA:Server:Software,SNIA:S
MI-S,SNIA:Base Server) 
  
SUCCESS --> Registered Instance internally Good 
  
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

  
TEST_REG: ServiceId service:wbem:https://10.141.46.190:5989 
  
serviceName: wbem 
  
TEMPLATE = 
(template-url-syntax=https://10.141.46.190:5989),(service-id=PG:12650
23706542-127-0-0-1),(service-hi-name=Pegasus),(service-hi-description=Pegasus 
CI
M Server Version 
2.9.1),(template-type=wbem),(template-version=1.0),(template-de
scription=This template describes the attributes used for advertising 
Pegasus CI
M 
Servers.),(InteropSchemaNamespace=root/PG_InterOp),(FunctionalProfilesSupporte
d=),(MultipleOperationsSupported=FALSE),(AuthenticationMechanismsSupported=None)
,(CommunicationMechanism=CIM-XML),(ProtocolVersion=1.0),(Namespace=root/PG_Inter
Op,root/PG_Internal,root/pmc/maxRAID/smi_14,root/cimv2,root),(RegisteredProfiles
Supported=SNIA:Server,SNIA:Host Hardware RAID Controller,SNIA:Host 
Hardware RAID
Controller:Software,SNIA:Host Hardware RAID 
Controller:Battery,DMTF:Physical As
set,SNIA:Host Hardware RAID Controller:JobControl,SNIA:Host Hardware RAID 
Contro
ller:Extent Composition,DMTF:Battery,SNIA:Host Hardware RAID 
Controller:SAS Init
iator Ports,SNIA:Host Hardware RAID Controller:Disk Drive Lite,SNIA:Host 
Hardwar
e RAID Controller:Physical Asset,DMTF:Physical Asset:Host Hardware RAID 
Controll
er,DMTF:Profile Registration,SNIA:Host Hardware RAID Controller:Block 
Services,S
NIA:Host Hardware RAID Controller:Disk Sparing,SNIA:Host Hardware RAID 
Controlle
r:Indication,SNIA:Server:Indication,SNIA:Host Hardware RAID 
Controller:DeviceCre
dentials,DMTF:Battery:Host Hardware RAID Controller,SNIA:Host Hardware 
RAID Cont
roller:DA Target Ports,SNIA:Profile 
Registration,SNIA:Server:Software,SNIA:SMI-S
,SNIA:Base Server) 
  
SUCCESS --> Registered Instance internally Good 
  
2. populateSLPRegistrations 
  
itemsRegistered till now = 1 (for Communication Mechanism - 
http://10.141.46.190:5988) 
  
itemsRegistered till now = 2 (for Communication Mechanism - 
https://10.141.46.190:5989) 
  
Total number of itemsRegistered = 2 
  
3. issueSLPRegistrations 
  
slp_agent.start_listener() ........ 
  
Inside start_listener thread !!!! 
  
<! ------------- After 10 secs --------------> 
  
********* SUCCESS ********** 
  
QUERY 
  
Even if everything goes fine without any error anywhere, why is - 
"slp_query --type=service:wbem" command giving inconsistent results? that 
is, sometimes I am not able to get any output, sometimes I am able to get 
only the service as the output without any attributes and sometime I get 
correct output i.e. with all attributes. 
  
No output 
 
  
Only Service without attributes 
  
0
2
38
URL: service:wbem:http://10.141.46.190:5988
URL: service:wbem:http://10.141.46.190:5988 
  

0
2
38
URL: service:wbem:http://10.141.46.190:5988
URL: service:wbem:http://10.141.46.190:5988 
  
With Service and all attributes 
  
0
2
38
URL: service:wbem:http://10.141.46.190:5988
ATTR: 
(template-url-syntax=http://10.141.46.190:5988),(service-id=PG:1265006013157-127-0-0-1),(service-hi-name=Pegasus),(service-hi-description=Pegasus 
CIM Server Version 
2.9.1),(template-type=wbem),(template-version=1.0),(template-description=This 
template describes the attributes used for advertising Pegasus CIM 
Servers.),(InteropSchemaNamespace=root/PG_InterOp),(FunctionalProfilesSupported=),(MultipleOperationsSupported=FALSE),(AuthenticationMechanismsSupported=None),(CommunicationMechanism=CIM-XML),(ProtocolVersion=1.0),(Namespace=root/PG_InterOp,root/PG_Internal,root/pmc/maxRAID/smi_14,root/cimv2,root),(RegisteredProfilesSupported=SNIA:Server,SNIA:Host 
Hardware RAID Controller,SNIA:Host Hardware RAID 
Controller:Software,SNIA:Host Hardware RAID 
Controller:Battery,DMTF:Physical Asset,SNIA:Host Hardware RAID 
Controller:JobControl,SNIA:Host Hardware RAID Controller:Extent 
Composition,DMTF:Battery,SNIA:Host Hardware RAID Controller:SAS Initiator 
Ports,SNIA:Host Hardware RAID Controller:Disk Drive Lite,SNIA:Host 
Hardware RAID Controller:Physical Asset,DMTF:Physical Asset:Host Hardware 
RAID Controller,DMTF:Profile Registration,SNIA:Host Hardware RAID 
Controller:Block Services,SNIA:Host Hardware RAID Controller:Disk 
Sparing,SNIA:Host Hardware RAID 
Controller:Indication,SNIA:Server:Indication,SNIA:Host Hardware RAID 
Controller:DeviceCredentials,DMTF:Battery:Host Hardware RAID 
Controller,SNIA:Host Hardware RAID Controller:DA Target Ports,SNIA:Profile 
Registration,SNIA:Server:Software)
URL: service:wbem:https://10.141.46.190:5989
ATTR: 
(template-url-syntax=https://10.141.46.190:5989),(service-id=PG:1265006013157-127-0-0-1),(service-hi-name=Pegasus),(service-hi-description=Pegasus 
CIM Server Version 
2.9.1),(template-type=wbem),(template-version=1.0),(template-description=This 
template describes the attributes used for advertising Pegasus CIM 
Servers.),(InteropSchemaNamespace=root/PG_InterOp),(FunctionalProfilesSupported=),(MultipleOperationsSupported=FALSE),(AuthenticationMechanismsSupported=None),(CommunicationMechanism=CIM-XML),(ProtocolVersion=1.0),(Namespace=root/PG_InterOp,root/PG_Internal,root/pmc/maxRAID/smi_14,root/cimv2,root),(RegisteredProfilesSupported=SNIA:Server,SNIA:Host 
Hardware RAID Controller,SNIA:Host Hardware RAID 
Controller:Software,SNIA:Host Hardware RAID 
Controller:Battery,DMTF:Physical Asset,SNIA:Host Hardware RAID 
Controller:JobControl,SNIA:Host Hardware RAID Controller:Extent 
Composition,DMTF:Battery,SNIA:Host Hardware RAID Controller:SAS Initiator 
Ports,SNIA:Host Hardware RAID Controller:Disk Drive Lite,SNIA:Host 
Hardware RAID Controller:Physical Asset,DMTF:Physical Asset:Host Hardware 
RAID Controller,DMTF:Profile Registration,SNIA:Host Hardware RAID 
Controller:Block Services,SNIA:Host Hardware RAID Controller:Disk 
Sparing,SNIA:Host Hardware RAID 
Controller:Indication,SNIA:Server:Indication,SNIA:Host Hardware RAID 
Controller:DeviceCredentials,DMTF:Battery:Host Hardware RAID 
Controller,SNIA:Host Hardware RAID Controller:DA Target Ports,SNIA:Profile 
Registration,SNIA:Server:Software) 
Regards, 
Biswapratap, 
Wipro Technologies. 
 
Please do not print this email unless it is absolutely necessary. 
The information contained in this electronic message and any attachments 
to this message are intended for the exclusive use of the addressee(s) and 
may contain proprietary, confidential or privileged information. If you 
are not the intended recipient, you should not disseminate, distribute or 
copy this e-mail. Please notify the sender immediately and destroy all 
copies of this message and any attachments. 
WARNING: Computer viruses can be transmitted via email. The recipient 
should check this email and any attachments for the presence of viruses. 
The company accepts no liability for any damage caused by any virus 
transmitted by this email. 
www.wipro.com 
Please do not print this email unless it is absolutely necessary. 
The information contained in this electronic message and any attachments 
to this message are intended for the exclusive use of the addressee(s) and 
may contain proprietary, confidential or privileged information. If you 
are not the intended recipient, you should not disseminate, distribute or 
copy this e-mail. Please notify the sender immediately and destroy all 
copies of this message and any attachments. 
WARNING: Computer viruses can be transmitted via email. The recipient 
should check this email and any attachments for the presence of viruses. 
The company accepts no liability for any damage caused by any virus 
transmitted by this email. 
www.wipro.com
(unnamed) (image/jpeg, 36.5 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.