The Nokia out-of-band management (OOBM) gateway must be configured to transport management traffic to the Network Operations Center (NOC) via dedicated circuit, Multiprotocol Label Switching/Virtual Private Network (MPLS/VPN) service, or IPsec tunnel.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-283829 | NOKI-RT-000110 | SV-283829r1203736_rule | CCI-001097 | medium |
| Description | ||||
| Using dedicated paths, the OOBM backbone connects the OOBM gateway routers located at the edge of the managed network and at the NOC. Dedicated links can be deployed using provisioned circuits or MPLS layer 2 and layer 3 VPN services or implementing a secured path with gateway-to-gateway IPsec tunnels. The tunnel mode ensures the management traffic will be logically separated from any other traffic traversing the same path. | ||||
| STIG | Date | |||
| Nokia Service Router OS 25.x Router Security Technical Implementation Guide | 2026-06-15 | |||
Details
Check Text (C-283829r1203736_chk)
This requirement is not applicable for the DODIN Backbone.
Review the network topology diagram to determine connectivity between the managed network and the NOC.
Review the OOBM gateway router configuration to validate the path and interface that the management traffic traverses.
Verify that only the routes and interfaces belonging to the management VPRN are present, as shown in the example below:
- show router 30 route-table
Route Table (Service: 30)
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
172.150.x.0/30 Remote BGP VPN 00h00m50s 170
4.4.4.x (tunneled:RSVP:1) 30
172.200.x.0/30 Local Local 00h00m54s 0
management-network 0
-------------------------------------------------------------------------------
No. of Routes: 2
- show router 30 interface
Interface Table (Service: 30)
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
"management-network" Up Up/Down VPRN 1/1/c3/1
172.200.x.x/30 n/a
-------------------------------------------------------------------------------
Interfaces : 1
If management traffic is not transported between the managed network and the NOC via dedicated circuit, MPLS/VPN service, or IPsec tunnel, this is a finding.
Fix Text (F-88299r1203735_fix)
This requirement is not applicable for the DODIN Backbone.
Ensure that a dedicated circuit, MPLS/VPN service, or IPsec tunnel is deployed to transport management traffic between the managed network and the NOC.
Create a VPRN/L3 VPN service for management traffic, as shown in the example below:
- configure service vprn 30 customer 1 create
- config>service>vprn# router-id 3.3.3.3
- config>service>vprn# autonomous-system 65100
- config>service>vprn# interface "management-network" create
- config>service>vprn>if# address 172.x.x.x/30
- config>service>vprn>if# sap 1/1/c3/1 create
- config>service>vprn>if>sap# exit
- config>service>vprn>if# exit
- config>service>vprn# bgp-ipvpn
- config>service>vprn>bgp-ipvpn# mpls
- config>service>vprn>bgp-ipvpn>mpls# auto-bind-tunnel
- config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel# resolution any
- config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel# exit
- config>service>vprn>bgp-ipvpn>mpls# route-distinguisher x.x.x.x:x
- config>service>vprn>bgp-ipvpn>mpls# vrf-target target:x:x
- config>service>vprn>bgp-ipvpn>mpls# no shutdown
- config>service>vprn>bgp-ipvpn>mpls# exit
- config>service>vprn>bgp-ipvpn# exit
- config>service>vprn# no shutdown
- config>service>vprn#