This should work fine in a conducted RF setup. One thought.. are you using the same IMSI for both UEs?
--
You received this message because you are subscribed to the Google Groups "Powder Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to powder-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/f0cf43df-8f4c-4e36-9938-a2dbe0b3c85an%40googlegroups.com.
On Jun 7, 2023, at 11:18 AM, Dustin Maas <dusti...@gmail.com> wrote:
You received this message because you are subscribed to a topic in the Google Groups "Powder Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/powder-users/TlaDCcPLzW8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to powder-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/CAD91B33-DFEA-4C2A-AAF9-E5894A06B0F6%40gmail.com.
I wouldn’t suspect the release if everything else appears to be working properly. I think we’ll need logs in order to help here though.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/8240FD2F-F4BE-483D-B63D-B3FC2BB0CE7E%40posteo.net.
These look like I’d expect. Please share logs for srsepc
and srsenb
, as well as the command line arguments you used when running srsenb
.
These look like logs for an instance where a single UE is attached via ZMQ. I thought we were talking about a 2-UE scenario with a conducted RF setup.
--
You received this message because you are subscribed to the Google Groups "Powder Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to powder-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/ecf33d2a-35d9-44e7-b6f0-0e61082a99aen%40googlegroups.com.
On Jun 8, 2023, at 2:24 PM, Dustin Maas <dusti...@gmail.com> wrote:
You received this message because you are subscribed to a topic in the Google Groups "Powder Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/powder-users/TlaDCcPLzW8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to powder-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/DCAB6C68-51E0-4F5C-A2D6-FE97E5FE1EB3%40gmail.com.
These logs confirm what I noticed today, which is that I see the slicer methods that get run when a UE attaches printing logs to stdout, but I’m not seeing any of the logging I expect to see when a UE gets bound to a slice, slice share gets updated, etc. I’ll try to reproduce here with the same O-RAN release.
-Dustin
On 8 Jun 2023, at 11:30, Nisha Adhikari wrote:
The commands to run the srsenb are at the top of enblog.txt. Thanks
On Thursday, 8 June 2023 at 11:05:20 UTC-5 Dustin Maas wrote:These look like I’d expect. Please share logs for
srsepc
andsrsenb
, as well as the command line arguments you used when runningsrsenb
.
--
You received this message because you are subscribed to the Google Groups "Powder Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to powder-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/1bb30f31-edd8-47a3-9dcc-612184ea9787n%40googlegroups.com.
I wasn’t able to reproduce this, but it may be a RIC or RMR bug.. please try the following "fix":
kubectl -n ricplt rollout restart \
deployments/deployment-ricplt-e2term-alpha \
deployments/deployment-ricplt-e2mgr \
deployments/deployment-ricplt-submgr \
deployments/deployment-ricplt-rtmgr \
deployments/deployment-ricplt-appmgr \
statefulsets/statefulset-ricplt-dbaas-server