blob: b7a49b5b9946442c6781aba8e874c6c67a404417 [file] [log] [blame]
Wei-Yu Chen0f12b9c2019-04-18 11:12:59 -07001{{- /*
2# Copyright 2018-present Open Networking Foundation
3# Copyright 2018 Intel Corporation
4#
5# Licensed under the Apache License, Version 2.0 (the "License");
6# you may not use this file except in compliance with the License.
7# You may obtain a copy of the License at
8#
9# http://www.apache.org/licenses/LICENSE-2.0
10#
11# Unless required by applicable law or agreed to in writing, software
12# distributed under the License is distributed on an "AS IS" BASIS,
13# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14# See the License for the specific language governing permissions and
15# limitations under the License.
16*/ -}}
17
18This is the instruction to configure your eNodeB to work with ONF M-CORD. You can find architecture illustration in assets/mcord-architecture.png.
19
201. Check the eNodeB is operating in following information:
21 eNodeB Address: {{ .Values.enb.host }}
22 eNodeB S1 port: {{ .Values.enb.port }}
23
242. Configure eNodeB with the correct MME information, get MME IP by following commands:
25 export MMEIP=$(kubectl get --namespace {{ .Release.Namespace }} -o jsonpath="{.status.podIP}" pods mme-0
26 export MMEPORT="36412"
27
28 MMEPORT is fixed in templates/mme.yaml.
29
303. Make sure UE's SIM card information is configured in hss.yaml.
31
324. Attach UE to M-CORD.