Deployed Magma v1.5 - NMS credentials are not working

278 views
Skip to first unread message

Robin George

unread,
Jun 9, 2021, 9:54:21 AM6/9/21
to magma-dev
Hi,
I have deployed on AGW on ubuntu and orchestrator on ubuntu following the documentation. This is deployed successfully. Now i am trying to integrate the AGW with orchestrator.

I am unable to login to NMS, please could you guide me in resolution for this.

~# kubectl -n magma get services
NAME                            TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)                                                    AGE
fluentd                         LoadBalancer   10.233.9.248    10.53.213.90   24224:30666/TCP                                            4d16h
nginx-proxy                     LoadBalancer   10.233.62.182   10.53.213.93   443:32074/TCP                                              4d16h
orc8r-bootstrap-legacy          LoadBalancer   10.233.26.196   10.53.213.92   80:31320/TCP,443:30266/TCP,8444:31532/TCP                  4d16h
orc8r-clientcert-nginx          LoadBalancer   10.233.2.68     10.53.213.94   80:31085/TCP,443:31875/TCP,8443:32088/TCP                  4d16h
orc8r-nginx-proxy               LoadBalancer   10.233.27.92    10.53.213.91   80:32196/TCP,8443:30168/TCP,8444:30083/TCP,443:31495/TCP   4d16h

I do have entry in windows  /driver/hosts as
 10.53.213.93 master.nms.magma330.local

On logging on to the NMS https://10.53.213.93/user/login?invalid=true&to=%2F i getam unable to login and on checking the pod of nms i see  error of Invalid organization!

Login was already created using the command
kubectl exec -it ${NMS_POD} -- yarn setAdminPassword master xxx xxxx

In the pods during NMS login i see below error
kubectl -n magma logs -f nms-magmalte-f46488596-6wwqf

{"message":"::ffff:10.233.111.15 - - [08/Jun/2021:13:34:28 +0000] \"GET /nms/static/images/favicon.png HTTP/1.0\" - - \"https://10.53.213.93/user/login?to=%2F\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-08T13:34:28.861Z"}
{"message":"::ffff:10.233.111.15 - - [08/Jun/2021:13:35:08 +0000] \"GET /nms/static/images/favicon.png HTTP/1.0\" - - \"https://10.53.213.93/user/login?to=%2F\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-08T13:35:08.440Z"}
{"message":"::ffff:10.233.111.15 - - [08/Jun/2021:13:39:09 +0000] \"POST /user/login HTTP/1.0\" 302 114 \"https://10.53.213.93/user/login?to=%2F\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-08T13:39:09.139Z"}
{"level":"error","message":"Error getting organization Invalid organization!","stack":"Error: Invalid organization!\n    at getOrganization (/usr/src/node_modules/@fbcnms/express-middleware/organizationMiddleware.js:44:9)","label":"auth/express.js","timestamp":"2021-06-08T13:39:09.160Z"}
{"message":"::ffff:10.233.111.15 - - [08/Jun/2021:13:39:09 +0000] \"GET /user/login?invalid=true&to=%2F HTTP/1.0\" 200 - \"https://10.53.213.93/user/login?to=%2F\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-08T13:39:09.167Z"}
{"message":"::ffff:10.233.111.15 - - [08/Jun/2021:13:39:09 +0000] \"GET /nms/static/dist/vendor.d4f8252eb2e49a31d879.chunk.js HTTP/1.0\" 304 - \"https://10.53.213.93/user/login?invalid=true&to=%2F\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-08T13:39:09.232Z"}
{"message":"::ffff:10.233.111.15 - - [08/Jun/2021:13:39:09 +0000] \"GET /nms/static/dist/login.db1151080950de40be58.js HTTP/1.0\" 304 - \"https://10.53.213.93/user/login?invalid=true&to=%2F\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-08T13:39:09.240Z"}
(node:27) UnhandledPromiseRejectionWarning: Error: Invalid organization!
    at getOrganization (/usr/src/node_modules/@fbcnms/express-middleware/organizationMiddleware.js:44:9)
(node:27) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 39)

proxy_ssl.conf has right entry. 

server {
  listen 443;
  ssl on;
  ssl_certificate /etc/nginx/conf.d/cert.pem;
  ssl_certificate_key /etc/nginx/conf.d/key.pem;
  location / {
     proxy_pass http://magmalte:8081;
     proxy_set_header Host $http_host;
  }
}


Karthik Subraveti

unread,
Jun 9, 2021, 10:28:32 AM6/9/21
to Robin George, magma-dev
Yes. This error is expected. The master portal or other tenants are expected to be accessed via domain name and not through IP address. 
So you might want to login through master.nms.<orc8r_domain_name> or <org>.nms.<orc8r_domain_name>

--
You received this message because you are subscribed to the Google Groups "magma-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to magma-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/magma-dev/746ea187-6b2d-474e-bb9f-459a5ecdf023n%40googlegroups.com.

Robin George

unread,
Jun 10, 2021, 5:47:57 PM6/10/21
to Karthik Subraveti, magma-dev
Karthik Hi,

Thanks, i got this resolved and am able to login to https://master.nms.magma330.local
with login as admin to master.nms i donot see a create network icon as stated in https://docs.magmacore.org/docs/lte/deploy_config_agw
 on fresh Orchestrator install, you will be prompted to create your first network. Otherwise, select "Create Network" from the network selection icon at the bottom of the left sidebar.

Do i need to login to https://magma-test.nms.magma330.local or create a new organization and then create a network ?

Kindly could you guide me

Regards,
 Robin

Karthik Subraveti

unread,
Jun 10, 2021, 6:13:44 PM6/10/21
to Robin George, magma-dev

On Thu, Jun 10, 2021 at 2:47 PM Robin George <robin...@gmail.com> wrote:
Karthik Hi,

Thanks, i got this resolved and am able to login to https://master.nms.magma330.local
with login as admin to master.nms i donot see a create network icon as stated in https://docs.magmacore.org/docs/lte/deploy_config_agw
 on fresh Orchestrator install, you will be prompted to create your first network. Otherwise, select "Create Network" from the network selection icon at the bottom of the left sidebar.

Do i need to login to https://magma-test.nms.magma330.local or create a new organization and then create a network ?
Great. Yes.  

Robin George

unread,
Jun 14, 2021, 3:42:31 PM6/14/21
to Karthik Subraveti, magma-dev
Hi,

I have logged into https://master.nms.<doamin_name>  created an organization named magma330org with Accessible tab= NMS and Enable all Network=checked.
On logging in to https://magma330.nms.<domain_name> , I donot see a Create network icon.
 
 If this is a fresh Orchestrator install, you will be prompted to create your first network. Otherwise, select "Create Network" from the network selection icon at the bottom of the left sidebar.

I wanted to register the  Access Gateway as mentioned below.
Navigate to "Equipment" on the NMS via the left navigation bar, hit "Add Gateway" on the upper right, and fill out the multi-step modal form. Use the secrets from above for the "Hardware UUID" and "Challenge Key" fields.

Jun 14 19:33:46 fbf1-agw magmad[767079]: ERROR:root:GetChallenge error! [StatusCode.NOT_FOUND] Gateway with hwid 6c282341-79f9-468f-87a2-56072bc85062 is not registered: Not found
Jun 14 19:33:46 fbf1-agw magmad[767079]: INFO:root:Retrying bootstrap in 30 seconds
Jun 14 19:33:50 fbf1-agw smsd[767228]: INFO:root:mme non_eps_service_config is not SMS_ORC8R, sleeping.
Jun 14 19:33:51 fbf1-agw control_proxy[767287]: 2021-06-14T19:33:51.170Z [127.0.0.1 -> subscriberdb-controller.magma330.local,8443] "POST /magma.lte.SubscriberDBCloud/ListSubscribers HTTP/2" 400 238bytes 0.001s
Jun 14 19:33:51 fbf1-agw subscriberdb[767128]: ERROR:root:Fetch subscribers error! [StatusCode.INTERNAL] Received http2 header with status: 400
Jun 14 19:33:55 fbf1-agw smsd[767228]: INFO:root:mme non_eps_service_config is not SMS_ORC8R, sleeping.

kubectl -n magma logs -f nms-magmalte-f46488596-6wwqf

{"message":"::ffff:10.233.111.15 - - [14/Jun/2021:19:39:43 +0000] \"GET /nms/static/images/favicon.png HTTP/1.0\" 200 - \"https://magma330org.nms.magma330.local/admin/audit_log\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.101 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-14T19:39:43.609Z"}
{"message":"::ffff:10.233.111.15 - - [14/Jun/2021:19:39:48 +0000] \"GET /nms/static/images/favicon.png HTTP/1.0\" 200 - \"https://magma330org.nms.magma330.local/nms\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.101 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-14T19:39:48.740Z"}
{"message":"::ffff:10.233.111.15 - - [14/Jun/2021:19:39:48 +0000] \"GET /nms/apicontroller/magma/v1/networks HTTP/1.0\" 503 32 \"https://magma330org.nms.magma330.local/nms\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.101 Safari/537.36\"\n","level":"info","label":"express-middleware/appMiddleware.js","timestamp":"2021-06-14T19:39:48.763Z"}

Please could you guide me if i am making any mistake in the steps to register the Gateway.
attached is screen shot of the NMS page.

Regards,
 Robin
MagmaNMS-1.PNG

Karthik Subraveti

unread,
Jun 14, 2021, 3:51:37 PM6/14/21
to Robin George, magma-dev
Can you share your screenshots of https://master.nms.<domain_name>/organizations page ?

Robin George

unread,
Jun 14, 2021, 3:56:23 PM6/14/21
to Karthik Subraveti, magma-dev
Hi,

Please see attached.

Regards,

MagmaNMS-2.PNG

Karthik Subraveti

unread,
Jun 14, 2021, 4:02:54 PM6/14/21
to Robin George, magma-dev
How did you create the user for the magma330 org ? Is the user a superuser ?

Robin George

unread,
Jun 14, 2021, 4:24:42 PM6/14/21
to Karthik Subraveti, magma-dev
Hi,

Yes i used the command "kubectl - exec -it nms-magmalte-f46488596-6wwqf -- yarn setAdminPassword magma330org admin admin"

Regards,
MagmaNMS-3.PNG

Robin George

unread,
Jun 14, 2021, 7:26:03 PM6/14/21
to Karthik Subraveti, magma-dev
Hi,

please could you guide the issue here.
any specific log files are needed.

appreciate your help

Regards,

Karthik Subraveti

unread,
Jun 15, 2021, 7:09:50 AM6/15/21
to Robin George, magma-dev
Can you attach screenshots of the this page https://magma330org.nms.<domain>/admin/networks
Also typically username is expected to be of email format  i.e admin@xxxx

Additionally also attach magmalte logs for triaging this further.
Debugging over email is hard. Please open a github issue or a discussion around this topic with
above mentioned information and we can take it from there.

..
Thanks
Karthik


Robin George

unread,
Jun 15, 2021, 3:37:34 PM6/15/21
to Karthik Subraveti, magma-dev
Hi,

I have created a discussion item with below details and attached the screenshot.
Kindly could you assist in verifying this and guide the next steps.

Registering and Configuring Your Access Gateway through NMS issues - Unable to add H/Wid #7574


Regards,


Joey Padden

unread,
Jun 16, 2021, 11:36:51 AM6/16/21
to Robin George, Karthik Subraveti, magma-dev
+1 for the subject of this thread. 

We deployed 1.5.1 orc8r and NMS last night. 

We are seeing login issues for some tenants and some users. 

Karthik I know Vitalii has sync’d with you. Want to join the thread here. 

We have had to reset a passwords for a number of users/tenants after the update. 

-Joey

Reply all
Reply to author
Forward
0 new messages