A network controller must modify configuration data stored on a NETCONF-capable access device. Which NETCONF operation is designed for this purpose?
The NETCONF <edit-config> operation is used to create, change, merge, replace, or delete configuration data in a target configuration datastore. The target can be a datastore such as running or candidate, depending on the capabilities supported by the network device. By comparison, <get-config> retrieves configuration data and does not modify it. <close-session> requests an orderly termination of the current NETCONF session, while <kill-session> forces the termination of another session identified by its session ID. NETCONF operations are carried within RPC messages and commonly transported over a secure protocol such as SSH. YANG models define the structure, types, constraints, and relationships of the configuration and operational data manipulated through NETCONF.
==============
Why must a managed ONT or residential gateway be reachable before an Auto Configuration Server can provision it using TR-069?
TR-069 enables remote management through communication between customer-premises equipment and an Auto Configuration Server. The device must be powered, operational, and able to establish or participate in a management session before configuration parameters, software information, diagnostics, or status data can be exchanged. An ACS cannot provision a device that is completely offline because no active communication path exists. TR-069 does not configure passive splitters, which contain no management processor or configurable service logic. The managed device can be located at the subscriber premises and does not need to be inside the central office. Communication is carried over the device's network connection rather than exclusively through an OLT serial console. Authentication and protected transport help secure management exchanges between the device and the ACS.
==============
Which Corteca component is intended primarily for use by the subscriber during Wi-Fi installation and management?
The Corteca mobile application provides subscriber-facing capabilities that can support self-installation and home Wi-Fi management. Depending on the enabled service, the subscriber can receive installation guidance, view the home network, manage connected devices, and perform supported troubleshooting or configuration tasks. The service provider uses other Corteca platform components for centralized service management, visibility, and operational control. An OLT network termination card provides access-node network connectivity and is not a subscriber application. An IPFIX collector receives traffic-flow records, while a NETCONF candidate datastore holds proposed device configuration before it is committed. Separating subscriber-facing and operator-facing functions allows the provider to offer controlled self-service capabilities without exposing the complete network-management environment or low-level access-device configuration to the end user.
==============
In an IPFIX deployment, which component observes traffic and sends flow records to a receiving system?
An IPFIX exporting process observes traffic at an observation point, creates flow records, and sends those records to an IPFIX collecting process. Templates describe the fields contained in the exported records, allowing the collector to interpret information such as source and destination addresses, transport ports, protocol identifiers, counters, and timestamps. The collector can store and analyze these records for traffic visibility, capacity planning, troubleshooting, accounting, or security analysis. IPFIX does not permanently store all collected information on the exporting network device. A passive optical splitter cannot inspect or export traffic because it has no active processing functions. An 802.1X supplicant participates in access authentication, while a SIP registrar maintains information used to locate SIP users or endpoints.
==============
An optical link experiences unexpectedly high signal loss immediately after a fiber cable is routed around a very tight corner. What is the most likely cause?
Macrobending occurs when an optical fiber is bent with a radius smaller than its supported minimum bend radius. The excessive bend can cause part of the optical signal to escape from the core, increasing attenuation and reducing the received optical power. This problem can appear after poor cable installation, improper storage, or routing the cable sharply around structural objects. Chromatic dispersion causes different wavelengths or spectral components of an optical pulse to travel at slightly different speeds, but it is not normally triggered by one tight physical corner. DSL crosstalk applies to copper pairs, while Dynamic Bandwidth Allocation controls upstream transmission opportunities in a PON. Correcting the cable routing and respecting the specified bend radius can remove or reduce the loss.
==============
Currently there are no comments in this discussion, be the first to comment!