Issue with Device Template Configuration Update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 03:50 PM
Hello Cisco Community,
I am encountering an issue when adding a device template to vManage. Although all the settings and configurations in the template are correct, I receive the following error:
Failed to update configuration - /ncs: devices/device {vedge-208b6178-9e5c-7e4e-dea5-7c53e04009fd}/config/vpn/vpn-instance{0}/router/ospf/area(0}/interface{ge0/0} : Interface referenced by OSPF; Configure an address or remove the reference.
Has anyone experienced a similar issue or could provide guidance on resolving this? Any insights would be greatly appreciated.
Thank you!
- Labels:
-
SD-WAN vManage
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 08:30 PM
Can I see the policy you use? It seem it for control plane of OSPF.
MHM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-25-2024 03:32 PM
I have created a vEdge configuration using the following steps in the Template:
1. Basic Configuration
• System Settings
2. Transport & Management
• VPN 0
• OSPF: Enabled using vpn0-ospf template
• Interfaces: ge0/0, ge1/1 configured in VBN Interface
• VPN 512
3. Additional Settings
• Banner added
In the Feature Template, I configured the following:
• Interface ge0/0:
• Static route: Device-specific
• Tunnel: Enabled
• Tunnel color: MPLS
• Netconf: Enabled
• OSPF: Enabled
• SSH: Enabled
• OSPF Configuration (vpn0-ospf):
• Area: 1
• Interface name: ge0/0
Generated Configuration on vEdge:
vpn 0
no interface eth0
interface ge0/0
ip address 192.168.101.1/24
tunnel-interface
encapsulation ipsec
allow-service all
allow-service netconf
allow-service sshd
no shutdown
!
ip route 0.0.0.0/0 192.168.101.254
!
vpn 512
interface eth0
ip dhcp-client
no shutdown
!
commitI

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-25-2024 01:44 PM
In your OSPF configuration, you referenced g0/0 interface for area0, however that interface does not have IP so OSPF can pick it up.
Looks like ,you want to configure ospf but selected incorrect interface. Or you didn't configure interface before enabling OSPF.
Please rate and mark as an accepted solution if you have found any of the information provided useful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-25-2024 03:31 PM
I have created a vEdge configuration using the following steps in the Template:
1. Basic Configuration
• System Settings
2. Transport & Management
• VPN 0
• OSPF: Enabled using vpn0-ospf template
• Interfaces: ge0/0, ge1/1 configured in VBN Interface
• VPN 512
3. Additional Settings
• Banner added
In the Feature Template, I configured the following:
• Interface ge0/0:
• Static route: Device-specific
• Tunnel: Enabled
• Tunnel color: MPLS
• Netconf: Enabled
• OSPF: Enabled
• SSH: Enabled
• OSPF Configuration (vpn0-ospf):
• Area: 1
• Interface name: ge0/0
Generated Configuration on vEdge:
vpn 0
no interface eth0
interface ge0/0
ip address 192.168.101.1/24
tunnel-interface
encapsulation ipsec
allow-service all
allow-service netconf
allow-service sshd
no shutdown
!
ip route 0.0.0.0/0 192.168.101.254
!
vpn 512
interface eth0
ip dhcp-client
no shutdown
!
commit
