Module nokia_srlinux¶
License: Inmanta EULA
Version: 23.10.1
Typedefs¶
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_mtu_t¶
Base type
yang::types::uint32
Type constraint
((self >= 512) and (self <= 9486))
- typedef nokia_srlinux::system_trace_options_t¶
Base type
string
Type constraint
(self in ['request', 'response', 'common'])
- typedef nokia_srlinux::acl::mac_filter_subinterface_specific_t¶
Base type
string
Type constraint
(self in ['disabled', 'input-only', 'output-only', 'input-and-output'])
- typedef nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv6_filter::entry_sequence_id_t¶
Base type
int
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match_dscp_set_t¶
Base type
nokia_srlinux::types::srl_nokia_common::dscp
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::dscp_value')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::dscp_name'))
- typedef nokia_srlinux::acl::system_filter::ipv4_filter::entry::match_protocol_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::ip_protocol_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['ipv6-hop', 'icmp', 'igmp', 'ggp', 'ipv4', 'st', 'tcp', 'egp', 'igp', 'udp', 'ipv6', 'idrp', 'rsvp', 'gre', 'esp', 'ah', 'icmp6', 'no-next-hdr', 'ipv6-dest-opts', 'eigrp', 'ospf', 'pim', 'vrrp', 'l2tp', 'sctp', 'mpls-in-ip', 'rohc']))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match_tcp_flags_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:\\(|\\)|&|\\||!|ack|rst|syn)+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port_value_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::l4_port_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint16')) and (int(self) >= 0)) and (int(self) <= 65535)) or (self in ['acap', 'afp-tcp', 'arns', 'asf-rmcp', 'ashare', 'atalk-rm', 'aurp', 'auth', 'bfd', 'bfd-echo', 'bftp', 'bgmp', 'bgp', 'bootpc', 'bootps', 'ccso-ns', 'chargen', 'cisco-tdp', 'citadel', 'clearcase', 'commerce', 'courier', 'daytime', 'dhcpv6-client', 'dhcpv6-server', 'dhcp-failover', 'dicom', 'discard', 'dnsix', 'domain', 'dsp', 'echo', 'epp', 'esro', 'exec', 'finger', 'ftp', 'ftp-data', 'ftps', 'ftps-data', 'godi', 'gopher', 'gtp-c', 'gtp-prime', 'gtp-u', 'ha-cluster', 'hostname', 'hp-alarm-mgr', 'http', 'http-alt', 'http-mgmt', 'http-rpc', 'https', 'ieee-mms-ssl', 'imap', 'imap3', 'imaps', 'ipp', 'ipsec', 'ipx', 'irc', 'iris-beep', 'isakmp', 'isakmp-nat', 'iscsi', 'iso-tsap', 'kerberos', 'kerberos-adm', 'klogin', 'kpasswd', 'kshell', 'l2tp', 'ldap', 'ldaps', 'ldp', 'lmp', 'login', 'lpd', 'lsp-ping', 'mac-server-adm', 'matip-a', 'matip-b', 'micro-bfd', 'microsoft-ds', 'mobile-ip', 'monitor', 'mpp', 'mssql-m', 'mssql-s', 'msdp', 'ms-exchange', 'msp', 'multihop-bfd', 'nas', 'ncp', 'netrjs-1', 'netrjs-2', 'netrjs-3', 'netrjs-4', 'netbios-data', 'netbios-ns', 'netbios-ss', 'netnews', 'netwall', 'new-rwho', 'nfs', 'nntp', 'nntps', 'ntp', 'odmr', 'olsr', 'openvpn', 'pim-auto-rp', 'pkix-timestamp', 'pop2', 'pop3', 'pop3s', 'pptp', 'ptp-event', 'ptp-general', 'print-srv', 'qmtp', 'qotd', 'radius', 'radius-acct', 'remote-mail', 'remotefs', 'remotecmd', 'rip', 'rje', 'rlp', 'rlzdb', 'rmc', 'rmonitor', 'rpc2portmap', 'rsync', 'rtelnet', 'rtsp', 'sgmp', 'silc', 'smux', 'sna-gw', 'snmp', 'snmp-trap', 'snpp', 'smtp', 'sql-svcs', 'sql', 'ssh', 'submission', 'sunrpc', 'svcloc', 'syslog', 'systat', 'tacacs', 'talk', 'tcpmux', 'tcpnethaspsrv', 'tftp', 'time', 'timed', 'ups', 'xdmcp', 'xns-ch', 'xns-mail', 'xns-time', 'z3950']))
- typedef nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::icmp_type_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::icmp_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['echo-reply', 'dest-unreachable', 'source-quench', 'redirect', 'echo', 'router-advertise', 'router-solicit', 'time-exceeded', 'param-problem', 'timestamp', 'timestamp-reply']))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port_value_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::l4_port_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint16')) and (int(self) >= 0)) and (int(self) <= 65535)) or (self in ['acap', 'afp-tcp', 'arns', 'asf-rmcp', 'ashare', 'atalk-rm', 'aurp', 'auth', 'bfd', 'bfd-echo', 'bftp', 'bgmp', 'bgp', 'bootpc', 'bootps', 'ccso-ns', 'chargen', 'cisco-tdp', 'citadel', 'clearcase', 'commerce', 'courier', 'daytime', 'dhcpv6-client', 'dhcpv6-server', 'dhcp-failover', 'dicom', 'discard', 'dnsix', 'domain', 'dsp', 'echo', 'epp', 'esro', 'exec', 'finger', 'ftp', 'ftp-data', 'ftps', 'ftps-data', 'godi', 'gopher', 'gtp-c', 'gtp-prime', 'gtp-u', 'ha-cluster', 'hostname', 'hp-alarm-mgr', 'http', 'http-alt', 'http-mgmt', 'http-rpc', 'https', 'ieee-mms-ssl', 'imap', 'imap3', 'imaps', 'ipp', 'ipsec', 'ipx', 'irc', 'iris-beep', 'isakmp', 'isakmp-nat', 'iscsi', 'iso-tsap', 'kerberos', 'kerberos-adm', 'klogin', 'kpasswd', 'kshell', 'l2tp', 'ldap', 'ldaps', 'ldp', 'lmp', 'login', 'lpd', 'lsp-ping', 'mac-server-adm', 'matip-a', 'matip-b', 'micro-bfd', 'microsoft-ds', 'mobile-ip', 'monitor', 'mpp', 'mssql-m', 'mssql-s', 'msdp', 'ms-exchange', 'msp', 'multihop-bfd', 'nas', 'ncp', 'netrjs-1', 'netrjs-2', 'netrjs-3', 'netrjs-4', 'netbios-data', 'netbios-ns', 'netbios-ss', 'netnews', 'netwall', 'new-rwho', 'nfs', 'nntp', 'nntps', 'ntp', 'odmr', 'olsr', 'openvpn', 'pim-auto-rp', 'pkix-timestamp', 'pop2', 'pop3', 'pop3s', 'pptp', 'ptp-event', 'ptp-general', 'print-srv', 'qmtp', 'qotd', 'radius', 'radius-acct', 'remote-mail', 'remotefs', 'remotecmd', 'rip', 'rje', 'rlp', 'rlzdb', 'rmc', 'rmonitor', 'rpc2portmap', 'rsync', 'rtelnet', 'rtsp', 'sgmp', 'silc', 'smux', 'sna-gw', 'snmp', 'snmp-trap', 'snpp', 'smtp', 'sql-svcs', 'sql', 'ssh', 'submission', 'sunrpc', 'svcloc', 'syslog', 'systat', 'tacacs', 'talk', 'tcpmux', 'tcpnethaspsrv', 'tftp', 'time', 'timed', 'ups', 'xdmcp', 'xns-ch', 'xns-mail', 'xns-time', 'z3950']))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::range_end_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::l4_port_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint16')) and (int(self) >= 0)) and (int(self) <= 65535)) or (self in ['acap', 'afp-tcp', 'arns', 'asf-rmcp', 'ashare', 'atalk-rm', 'aurp', 'auth', 'bfd', 'bfd-echo', 'bftp', 'bgmp', 'bgp', 'bootpc', 'bootps', 'ccso-ns', 'chargen', 'cisco-tdp', 'citadel', 'clearcase', 'commerce', 'courier', 'daytime', 'dhcpv6-client', 'dhcpv6-server', 'dhcp-failover', 'dicom', 'discard', 'dnsix', 'domain', 'dsp', 'echo', 'epp', 'esro', 'exec', 'finger', 'ftp', 'ftp-data', 'ftps', 'ftps-data', 'godi', 'gopher', 'gtp-c', 'gtp-prime', 'gtp-u', 'ha-cluster', 'hostname', 'hp-alarm-mgr', 'http', 'http-alt', 'http-mgmt', 'http-rpc', 'https', 'ieee-mms-ssl', 'imap', 'imap3', 'imaps', 'ipp', 'ipsec', 'ipx', 'irc', 'iris-beep', 'isakmp', 'isakmp-nat', 'iscsi', 'iso-tsap', 'kerberos', 'kerberos-adm', 'klogin', 'kpasswd', 'kshell', 'l2tp', 'ldap', 'ldaps', 'ldp', 'lmp', 'login', 'lpd', 'lsp-ping', 'mac-server-adm', 'matip-a', 'matip-b', 'micro-bfd', 'microsoft-ds', 'mobile-ip', 'monitor', 'mpp', 'mssql-m', 'mssql-s', 'msdp', 'ms-exchange', 'msp', 'multihop-bfd', 'nas', 'ncp', 'netrjs-1', 'netrjs-2', 'netrjs-3', 'netrjs-4', 'netbios-data', 'netbios-ns', 'netbios-ss', 'netnews', 'netwall', 'new-rwho', 'nfs', 'nntp', 'nntps', 'ntp', 'odmr', 'olsr', 'openvpn', 'pim-auto-rp', 'pkix-timestamp', 'pop2', 'pop3', 'pop3s', 'pptp', 'ptp-event', 'ptp-general', 'print-srv', 'qmtp', 'qotd', 'radius', 'radius-acct', 'remote-mail', 'remotefs', 'remotecmd', 'rip', 'rje', 'rlp', 'rlzdb', 'rmc', 'rmonitor', 'rpc2portmap', 'rsync', 'rtelnet', 'rtsp', 'sgmp', 'silc', 'smux', 'sna-gw', 'snmp', 'snmp-trap', 'snpp', 'smtp', 'sql-svcs', 'sql', 'ssh', 'submission', 'sunrpc', 'svcloc', 'syslog', 'systat', 'tacacs', 'talk', 'tcpmux', 'tcpnethaspsrv', 'tftp', 'time', 'timed', 'ups', 'xdmcp', 'xns-ch', 'xns-mail', 'xns-time', 'z3950']))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::range_start_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::l4_port_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint16')) and (int(self) >= 0)) and (int(self) <= 65535)) or (self in ['acap', 'afp-tcp', 'arns', 'asf-rmcp', 'ashare', 'atalk-rm', 'aurp', 'auth', 'bfd', 'bfd-echo', 'bftp', 'bgmp', 'bgp', 'bootpc', 'bootps', 'ccso-ns', 'chargen', 'cisco-tdp', 'citadel', 'clearcase', 'commerce', 'courier', 'daytime', 'dhcpv6-client', 'dhcpv6-server', 'dhcp-failover', 'dicom', 'discard', 'dnsix', 'domain', 'dsp', 'echo', 'epp', 'esro', 'exec', 'finger', 'ftp', 'ftp-data', 'ftps', 'ftps-data', 'godi', 'gopher', 'gtp-c', 'gtp-prime', 'gtp-u', 'ha-cluster', 'hostname', 'hp-alarm-mgr', 'http', 'http-alt', 'http-mgmt', 'http-rpc', 'https', 'ieee-mms-ssl', 'imap', 'imap3', 'imaps', 'ipp', 'ipsec', 'ipx', 'irc', 'iris-beep', 'isakmp', 'isakmp-nat', 'iscsi', 'iso-tsap', 'kerberos', 'kerberos-adm', 'klogin', 'kpasswd', 'kshell', 'l2tp', 'ldap', 'ldaps', 'ldp', 'lmp', 'login', 'lpd', 'lsp-ping', 'mac-server-adm', 'matip-a', 'matip-b', 'micro-bfd', 'microsoft-ds', 'mobile-ip', 'monitor', 'mpp', 'mssql-m', 'mssql-s', 'msdp', 'ms-exchange', 'msp', 'multihop-bfd', 'nas', 'ncp', 'netrjs-1', 'netrjs-2', 'netrjs-3', 'netrjs-4', 'netbios-data', 'netbios-ns', 'netbios-ss', 'netnews', 'netwall', 'new-rwho', 'nfs', 'nntp', 'nntps', 'ntp', 'odmr', 'olsr', 'openvpn', 'pim-auto-rp', 'pkix-timestamp', 'pop2', 'pop3', 'pop3s', 'pptp', 'ptp-event', 'ptp-general', 'print-srv', 'qmtp', 'qotd', 'radius', 'radius-acct', 'remote-mail', 'remotefs', 'remotecmd', 'rip', 'rje', 'rlp', 'rlzdb', 'rmc', 'rmonitor', 'rpc2portmap', 'rsync', 'rtelnet', 'rtsp', 'sgmp', 'silc', 'smux', 'sna-gw', 'snmp', 'snmp-trap', 'snpp', 'smtp', 'sql-svcs', 'sql', 'ssh', 'submission', 'sunrpc', 'svcloc', 'syslog', 'systat', 'tacacs', 'talk', 'tcpmux', 'tcpnethaspsrv', 'tftp', 'time', 'timed', 'ups', 'xdmcp', 'xns-ch', 'xns-mail', 'xns-time', 'z3950']))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match_next_header_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::ip_protocol_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['ipv6-hop', 'icmp', 'igmp', 'ggp', 'ipv4', 'st', 'tcp', 'egp', 'igp', 'udp', 'ipv6', 'idrp', 'rsvp', 'gre', 'esp', 'ah', 'icmp6', 'no-next-hdr', 'ipv6-dest-opts', 'eigrp', 'ospf', 'pim', 'vrrp', 'l2tp', 'sctp', 'mpls-in-ip', 'rohc']))
- typedef nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::icmp6_type_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::icmp6_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['dest-unreachable', 'packet-too-big', 'time-exceeded', 'param-problem', 'echo-request', 'echo-reply', 'mld-query', 'mld-report', 'mld-done', 'router-solicit', 'router-advertise', 'neighbor-solicit', 'neighbor-advertise', 'redirect', 'router-renumber', 'node-info-query', 'node-info-response', 'mld-v2', 'mcast-rtr-adv', 'mcast-rtr-solicit', 'mcast-rtr-term']))
- typedef nokia_srlinux::acl::mac_filter::entry::match_ethertype_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::ethertype
Type constraint
(std::validate_type('pydantic.constr',self,{'regex': '^(?:0x[0-9A-Fa-f]{4})$(?!\\n\\Z)'}) or (self in ['ipv4', 'arp', 'ipv6', 'flow-control', 'lacp', 'mpls-unicast', 'mpls-multicast', 'pppoe-discovery', 'pppoe-session', '8021x-authentication', 'lldp', 'macsec', 'pbb', 'ptp', 'eth-oam', 'fcoe', 'fcoe-initialization', 'roce']))
- typedef nokia_srlinux::acl::policers::system_cpu_policer_max_packet_burst_t¶
Base type
yang::types::uint32
Type constraint
((self >= 16) and (self <= 4000000))
- typedef nokia_srlinux::acl::policers::system_cpu_policer_peak_packet_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4000000))
- typedef nokia_srlinux::bfd::subinterface_desired_minimum_transmit_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10000) and (self <= 100000000))
- typedef nokia_srlinux::bfd::subinterface_detection_multiplier_t¶
Base type
yang::types::uint8
Type constraint
((self >= 3) and (self <= 20))
- typedef nokia_srlinux::bfd::subinterface_max_hop_count_t¶
Base type
yang::types::uint8
Type constraint
((self >= 2) and (self <= 255))
- typedef nokia_srlinux::bfd::subinterface_minimum_echo_receive_interval_t¶
Base type
yang::types::uint32
Type constraint
(((self >= 250000) and (self <= 100000000)) or (self == 0))
- typedef nokia_srlinux::bfd::subinterface_required_minimum_receive_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10000) and (self <= 100000000))
- typedef nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_desired_minimum_transmit_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10000) and (self <= 100000000))
- typedef nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_detection_multiplier_t¶
Base type
yang::types::uint8
Type constraint
((self >= 3) and (self <= 20))
- typedef nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_local_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_remote_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_required_minimum_receive_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10000) and (self <= 100000000))
- typedef nokia_srlinux::interface::breakout_mode_breakout_port_speed_t¶
Base type
string
Type constraint
(self in ['10G', '25G', '50G', '100G'])
- typedef nokia_srlinux::interface::breakout_mode_num_breakout_ports_t¶
Base type
string
Type constraint
(self in ['2', '3', '4', '8'])
- typedef nokia_srlinux::interface::ethernet_duplex_mode_t¶
Base type
string
Type constraint
(self in ['full', 'half'])
- typedef nokia_srlinux::interface::ethernet_port_speed_t¶
Base type
string
Type constraint
(self in ['10M', '100M', '1G', '10G', '25G', '40G', '50G', '100G', '200G', '400G', '1T'])
- typedef nokia_srlinux::interface::ethernet_reload_delay_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 86400))
- typedef nokia_srlinux::interface::ethernet_standby_signaling_t¶
Base type
string
Type constraint
(self in ['power-off', 'lacp'])
- typedef nokia_srlinux::interface::lag_lacp_fallback_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 4) and (self <= 3600))
- typedef nokia_srlinux::interface::lag_min_links_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::interface::linux_device_name_t¶
Base type
string
Type constraint
((std::length(self) >= 0) and (std::length(self) <= 10))
- typedef nokia_srlinux::platform::linecard::forwarding_complex::p4rt_id_t¶
Base type
yang::types::uint64
Type constraint
((self >= 1) and (self <= 18446744073709551615))
- typedef nokia_srlinux::interface::subinterface_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 9999))
- typedef nokia_srlinux::interface::subinterface_ip_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1280) and (self <= 9486))
- typedef nokia_srlinux::interface::subinterface_l2_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1450) and (self <= 9500))
- typedef nokia_srlinux::interface::subinterface_mpls_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1284) and (self <= 9496))
- typedef nokia_srlinux::interface::transceiver_forward_error_correction_t¶
Base type
string
Type constraint
(self in ['disabled', 'rs-528', 'rs-544', 'base-r', 'rs-108'])
- typedef nokia_srlinux::interface::vhost_vhost_socket_mode_t¶
Base type
string
Type constraint
(self in ['server', 'client'])
- typedef nokia_srlinux::interface::vhost_vhost_socket_queues_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 1024))
- typedef nokia_srlinux::interface::ethernet::hold_time_down_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 86400))
- typedef nokia_srlinux::interface::ethernet::hold_time_up_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 86400))
- typedef nokia_srlinux::interface::ethernet::storm_control_broadcast_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 100000000))
- typedef nokia_srlinux::interface::ethernet::storm_control_multicast_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 100000000))
- typedef nokia_srlinux::interface::ethernet::storm_control_units_t¶
Base type
string
Type constraint
(self in ['kbps', 'percentage'])
- typedef nokia_srlinux::interface::ethernet::storm_control_unknown_unicast_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 100000000))
- typedef nokia_srlinux::interface::lag::lacp_admin_key_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::interface::subinterface::anycast_gw_virtual_router_id_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::bridge_table::mac_duplication_action_t¶
Base type
string
Type constraint
(self in ['stop-learning', 'blackhole', 'oper-down'])
- typedef nokia_srlinux::network_instance::bridge_table::mac_limit_maximum_entries_t¶
Base type
yang::types::int32
Type constraint
((self >= 1) and (self <= 8192))
- typedef nokia_srlinux::network_instance::bridge_table::mac_limit_warning_threshold_pct_t¶
Base type
yang::types::int32
Type constraint
((self >= 6) and (self <= 100))
- typedef nokia_srlinux::interface::subinterface::ipv4::arp_debug_t¶
Base type
string
Type constraint
(self == 'messages')
- typedef nokia_srlinux::interface::subinterface::ipv4::arp_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 60) and (self <= 65535))
- typedef nokia_srlinux::interface::subinterface::ipv6::dhcp_relay_option_t¶
Base type
string
Type constraint
(self in ['interface-id', 'remote-id', 'client-link-layer-address'])
- typedef nokia_srlinux::interface::subinterface::ipv6::dhcp_relay_server_t¶
Base type
nokia_srlinux::types::srl_nokia_interfaces_ip_dhcp_relay::hostv6
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::domain_name'))
- typedef nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group_virtual_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::advertise_route_type_t¶
Base type
string
Type constraint
(self in ['static', 'dynamic'])
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::populate_route_type_t¶
Base type
string
Type constraint
(self in ['static', 'dynamic', 'evpn'])
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::virtual_ipv6_discovery::address_probe_interval_t¶
Base type
yang::types::uint32
Type constraint
(((self >= 5) and (self <= 86400)) or (self == 0))
- typedef nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::trace_options_trace_t¶
Base type
string
Type constraint
(self == 'messages')
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_debug_t¶
Base type
string
Type constraint
(self == 'messages')
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_learn_unsolicited_t¶
Base type
string
Type constraint
(self in ['none', 'global', 'link-local', 'both'])
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_reachable_time_t¶
Base type
yang::types::uint32
Type constraint
((self >= 30) and (self <= 3600))
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_stale_time_t¶
Base type
yang::types::uint32
Type constraint
((self >= 60) and (self <= 65535))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement_debug_t¶
Base type
string
Type constraint
(self == 'messages')
- typedef nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::limit_warning_threshold_pct_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 100))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_ip_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1280) and (self <= 9486))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_max_advertisement_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 4) and (self <= 1800))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_min_advertisement_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 3) and (self <= 1350))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_reachable_time_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 3600000))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_retransmit_time_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1800000))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_router_lifetime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 9000))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::prefix_preferred_lifetime_t¶
Base type
string
Type constraint
((self == 'infinite') or (yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')))
- typedef nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::prefix_valid_lifetime_t¶
Base type
string
Type constraint
((self == 'infinite') or (yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')))
- typedef nokia_srlinux::interface::subinterface::ra_guard::vlan_list_vlan_id_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 4095))
- typedef nokia_srlinux::interface::subinterface::vlan::encap::double_tagged_inner_vlan_id_t¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_id')) or (self in ['any', 'optional']))
- typedef nokia_srlinux::interface::subinterface::vlan::encap::double_tagged_outer_vlan_id_t¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_id')) or (self in ['any', 'optional']))
- typedef nokia_srlinux::interface::subinterface::vlan::encap::single_tagged_vlan_id_t¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_id')) or (self == 'any'))
- typedef nokia_srlinux::network_instance::static_routes::route_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::aggregate_routes::route::aggregator_as_number_t¶
Base type
nokia_srlinux::types::srl_nokia_common::as_number
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::network_instance::aggregate_routes::route::communities_add_t¶
Base type
string
Type constraint
((((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_type') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_regexp_type')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_well_known_type')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_large_community_type')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_large_community_regexp_type'))
- typedef nokia_srlinux::network_instance::bridge_table::mac_duplication_hold_down_time_t¶
Base type
string
Type constraint
((self == 'indefinite') or (((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 2)) and (int(self) <= 60)))
- typedef nokia_srlinux::network_instance::bridge_table::mac_duplication_monitoring_window_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 15))
- typedef nokia_srlinux::network_instance::bridge_table::mac_duplication_num_moves_t¶
Base type
yang::types::uint32
Type constraint
((self >= 3) and (self <= 10))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_arp_table_size_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 8192))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd_table_size_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 8192))
- typedef nokia_srlinux::network_instance::bridge_table::mac_learning::aging_age_time_t¶
Base type
yang::types::int32
Type constraint
((self >= 60) and (self <= 86400))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd::dynamic_learning_age_time_t¶
Base type
string
Type constraint
((self == 'never') or (((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 60)) and (int(self) <= 86400)))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd::dynamic_learning_send_refresh_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 120)) and (int(self) <= 86400)) or (self == 'never'))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd::ip_duplication_hold_down_time_t¶
Base type
string
Type constraint
((self == 'indefinite') or (((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 2)) and (int(self) <= 60)))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd::ip_duplication_monitoring_window_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 15))
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd::ip_duplication_num_moves_t¶
Base type
yang::types::uint32
Type constraint
((self >= 3) and (self <= 10))
- typedef nokia_srlinux::network_instance::protocols::bgp::trace_options::flag_modifier_t¶
Base type
string
Type constraint
(self in ['detail', 'receive', 'send'])
- typedef nokia_srlinux::network_instance::protocols::bgp::trace_options::flag_name_t¶
Base type
string
Type constraint
(self in ['events', 'packets', 'open', 'keepalive', 'graceful-restart', 'timers', 'route', 'notification', 'socket', 'update'])
- typedef nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn_advertise_neighbor_type_t¶
Base type
string
Type constraint
(self in ['router', 'host', 'router-host'])
- typedef nokia_srlinux::network_instance::bridge_table::static_mac::mac_destination_t¶
Base type
string
Type constraint
((self == 'blackhole') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::subinterface_all'))
- typedef nokia_srlinux::transport_security::macsec::interface::interface_ref_subinterface_t¶
Base type
int
Type constraint
((self >= 0) and (self <= 9999))
- typedef nokia_srlinux::network_instance::ip_load_balancing::resilient_hash_prefix_hash_buckets_per_path_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 32))
- typedef nokia_srlinux::network_instance::ip_load_balancing::resilient_hash_prefix_ip_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::ip_load_balancing::resilient_hash_prefix_max_paths_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_desired_minimum_transmit_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10000) and (self <= 100000000))
- typedef nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_detection_multiplier_t¶
Base type
yang::types::uint8
Type constraint
((self >= 3) and (self <= 20))
- typedef nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_mode_t¶
Base type
string
Type constraint
(self in ['none', 'ecmp-protected', 'linear'])
- typedef nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_revert_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4320))
- typedef nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 32))
- typedef nokia_srlinux::network_instance::mpls::static_entry_operation_t¶
Base type
string
Type constraint
(self in ['pop', 'swap'])
- typedef nokia_srlinux::network_instance::mpls::static_entry_preference_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance_id_t¶
Base type
int
Type constraint
((self >= 1) and (self <= 2))
- typedef nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::export_rt_rt_t¶
Base type
nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_type
Type constraint
((((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:color:[01]{2}:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::import_rt_rt_t¶
Base type
nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_type
Type constraint
((((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:color:[01]{2}:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::group_range_group_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::group_range_rate_threshold_t¶
Base type
yang::types::uint64
Type constraint
((self >= 0) and (self <= 4294967294))
- typedef nokia_srlinux::network_instance::next_hop_groups::group::nexthop_ip_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_with_zone
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_with_zone') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_with_zone'))
- typedef nokia_srlinux::network_instance::next_hop_groups::group::nexthop_pushed_mpls_label_stack_t¶
Base type
nokia_srlinux::types::srl_nokia_common::mpls_label_with_implicit_and_explicit_null
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved')) or (self in ['IPV4_EXPLICIT_NULL', 'IPV6_EXPLICIT_NULL', 'IMPLICIT_NULL']))
- typedef nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::enable_bfd_local_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::enable_bfd_local_discriminator_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16384))
- typedef nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::enable_bfd_remote_discriminator_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16384))
- typedef nokia_srlinux::network_instance::policy_forwarding::policy_type_t¶
Base type
string
Type constraint
(self in ['pbr-policy', 'vrf-selection-policy'])
- typedef nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4_dscp_set_t¶
Base type
nokia_srlinux::types::srl_nokia_common::dscp
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::dscp_value')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::dscp_name'))
- typedef nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4_protocol_t¶
Base type
nokia_srlinux::types::srl_nokia_packet_match_types::ip_protocol_type
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['ipv6-hop', 'icmp', 'igmp', 'ggp', 'ipv4', 'st', 'tcp', 'egp', 'igp', 'udp', 'ipv6', 'idrp', 'rsvp', 'gre', 'esp', 'ah', 'icmp6', 'no-next-hdr', 'ipv6-dest-opts', 'eigrp', 'ospf', 'pim', 'vrrp', 'l2tp', 'sctp', 'mpls-in-ip', 'rohc']))
- typedef nokia_srlinux::network_instance::protocols::bgp_max_ecmp_hash_buckets_per_next_hop_group_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 128))
- typedef nokia_srlinux::network_instance::protocols::bgp_router_id_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::gribi_default_preference_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::gribi_max_ecmp_hash_buckets_per_next_hop_group_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 256))
- typedef nokia_srlinux::network_instance::protocols::igmp_query_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_igmp::igmp_interval_type
Type constraint
((self >= 2) and (self <= 1024))
- typedef nokia_srlinux::network_instance::protocols::igmp_query_last_member_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_igmp::igmp_interval_type
Type constraint
((self >= 1) and (self <= 1023))
- typedef nokia_srlinux::network_instance::protocols::igmp_query_response_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_igmp::igmp_interval_type
Type constraint
((self >= 1) and (self <= 1023))
- typedef nokia_srlinux::network_instance::protocols::igmp_robust_count_t¶
Base type
yang::types::uint32
Type constraint
((self >= 2) and (self <= 10))
- typedef nokia_srlinux::network_instance::protocols::igmp_snooping_query_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_igmp_snooping::igmp_interval_type
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::igmp_snooping_robust_count_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::mld_query_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld::mld_interval_type
Type constraint
((self >= 2) and (self <= 1024))
- typedef nokia_srlinux::network_instance::protocols::mld_query_last_member_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld::mld_interval_type
Type constraint
((self >= 1) and (self <= 1023))
- typedef nokia_srlinux::network_instance::protocols::mld_query_response_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld::mld_interval_type
Type constraint
((self >= 1) and (self <= 1023))
- typedef nokia_srlinux::network_instance::protocols::mld_robust_count_t¶
Base type
yang::types::uint32
Type constraint
((self >= 2) and (self <= 10))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping_query_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld_snooping::mld_interval_type
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping_robust_count_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::pim_ecmp_balance_hold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 600))
- typedef nokia_srlinux::network_instance::protocols::bgp::convergence_min_wait_to_advertise_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::graceful_restart_requested_restart_time_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::graceful_restart_stale_routes_time_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::bgp::group_group_name_t¶
Base type
nokia_srlinux::types::srl_nokia_common::name
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 64))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor_peer_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_with_zone
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_with_zone') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_with_zone'))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor_peer_group_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 64))
- typedef nokia_srlinux::network_instance::protocols::bgp::preference_ebgp_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::bgp::preference_ibgp_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::route_reflector_cluster_id_t¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::dotted_quad'))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::transport_tcp_mss_t¶
Base type
yang::types::uint16
Type constraint
((self >= 536) and (self <= 9446))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::add_paths_send_max_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 16))
- typedef nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::convergence_max_wait_to_advertise_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv6_next_hops::tunnel_resolution_mode_t¶
Base type
string
Type constraint
(self in ['prefer', 'require', 'disabled'])
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::as_path_options::remove_private_as_mode_t¶
Base type
string
Type constraint
(self in ['disabled', 'delete', 'replace'])
- typedef nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::interface_allowed_peer_as_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[1-9][0-9]*)|(?:[1-9][0-9]*)\\.\\.(?:[1-9][0-9]*))$(?!\\n\\Z)'})
- typedef nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::interface_peer_group_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 64))
- typedef nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::match_allowed_peer_as_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[1-9][0-9]*)|(?:[1-9][0-9]*)\\.\\.(?:[1-9][0-9]*))$(?!\\n\\Z)'})
- typedef nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::match_peer_group_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 64))
- typedef nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::match_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::multihop_maximum_hops_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_connect_retry_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_hold_time_t¶
Base type
yang::types::uint16
Type constraint
(((self >= 3) and (self <= 65535)) or (self == 0))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_keepalive_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 21845))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_minimum_advertisement_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::transport_local_address_t¶
Base type
string
Type constraint
((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ip_address') and (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))) or (self == self))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv6_unicast::prefix_limit_max_received_routes_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::link_bandwidth_add_next_hop_count_to_received_bgp_routes_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::int32')) and (int(self) >= 1)) and (int(self) <= 128)) or (self == 'disable'))
- typedef nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance_ecmp_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 32))
- typedef nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance_encapsulation_type_t¶
Base type
string
Type constraint
(self == 'mpls')
- typedef nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table_next_hop_t¶
Base type
nokia_srlinux::types::srl_nokia_common::next_hop_type
Type constraint
((self == 'use-system-ipv4-address') or (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ip_address') and (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))))
- typedef nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::inclusive_mcast_originating_ip_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::advertise_maximum_dynamic_weight_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 128))
- typedef nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::advertise_weight_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 1)) and (int(self) <= 128)) or (self == 'dynamic'))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::weighted_ecmp_max_ecmp_hash_buckets_per_next_hop_group_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 128))
- typedef nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::internal_tags_tag_set_t¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::route_distinguisher_rd_t¶
Base type
nokia_srlinux::types::srl_nokia_common::route_distinguisher
Type constraint
(((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_0') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_1')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_2')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_2b'))
- typedef nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::route_target_export_rt_t¶
Base type
nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_type
Type constraint
((((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:color:[01]{2}:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::route_target_import_rt_t¶
Base type
nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_type
Type constraint
((((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:color:[01]{2}:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::te_database_install::bgp_ls_igp_identifier_t¶
Base type
yang::types::uint64
Type constraint
((self >= 0) and (self <= 18446744073709551615))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping::interface_maximum_number_group_sources_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4096))
- typedef nokia_srlinux::network_instance::protocols::pim::interface_maximum_number_groups_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16000))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping::interface_maximum_number_sources_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 512))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping::interface_query_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld_snooping::mld_interval_type
Type constraint
((self >= 2) and (self <= 1024))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping::interface_query_last_member_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld_snooping::mld_interval_type
Type constraint
((self >= 1) and (self <= 5))
- typedef nokia_srlinux::network_instance::protocols::mld_snooping::interface_query_response_interval_t¶
Base type
nokia_srlinux::types::srl_nokia_mld_snooping::mld_interval_type
Type constraint
((self >= 1) and (self <= 1023))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::packet_modifier_t¶
Base type
string
Type constraint
(self in ['ingress', 'egress', 'in-and-egress', 'drop'])
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::packet_type_t¶
Base type
string
Type constraint
(self in ['all', 'hello', 'dbdescr', 'ls-request', 'ls-update', 'ls-ack'])
- typedef nokia_srlinux::network_instance::protocols::mld_snooping::interface_robust_count_t¶
Base type
yang::types::uint32
Type constraint
((self >= 2) and (self <= 10))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance_instance_id_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::auto_cost_reference_bandwidth_t¶
Base type
yang::types::uint64
Type constraint
((self >= 1) and (self <= 8000000000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::graceful_restart_acceptable_duration_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 20000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::ldp_synchronization_hold_down_timer_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers_lsp_lifetime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 350) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::transport_lsp_mtu_size_t¶
Base type
yang::types::uint16
Type constraint
((self >= 490) and (self <= 9490))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::level1_to_level2::summary_address_ip_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::delay_delay_selection_t¶
Base type
string
Type constraint
(self in ['static', 'dynamic', 'static-preferred', 'dynamic-preferred'])
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::level_priority_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 127))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::timers_csnp_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::timers_lsp_pacing_interval_t¶
Base type
yang::types::uint64
Type constraint
((self >= 0) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::weighted_ecmp_load_balancing_weight_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 1)) and (int(self) <= 4294967295)) or (self in ['auto', 'none']))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::level::timers_hello_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 20000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::level::timers_hello_multiplier_t¶
Base type
yang::types::uint8
Type constraint
((self >= 2) and (self <= 100))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv4_adjacency_sid_assignment_t¶
Base type
string
Type constraint
(self in ['static', 'dynamic', 'none'])
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv4_node_sid_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1048575))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv6_adjacency_sid_assignment_t¶
Base type
string
Type constraint
(self in ['static', 'dynamic', 'none'])
- typedef nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv6_node_sid_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1048575))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::level::route_preference_external_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::level::route_preference_internal_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::multi_homed_prefix_preference_t¶
Base type
string
Type constraint
(self in ['none', 'all'])
- typedef nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::ti_lfa_max_sr_policy_lfa_labels_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 3))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::remote_lfa::node_protect_max_pq_nodes_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 32))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::overload::on_boot_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 60) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::mpls::dynamic_adjacency_sids_hold_time_t¶
Base type
string
Type constraint
((self == 'none') or (((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint16')) and (int(self) >= 1)) and (int(self) <= 300)))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_generation_initial_wait_t¶
Base type
yang::types::uint64
Type constraint
((self >= 10) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_generation_max_wait_t¶
Base type
yang::types::uint64
Type constraint
((self >= 10) and (self <= 120000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_generation_second_wait_t¶
Base type
yang::types::uint64
Type constraint
((self >= 10) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_refresh_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 150) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::spf_initial_wait_t¶
Base type
yang::types::uint64
Type constraint
((self >= 10) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::spf_max_wait_t¶
Base type
yang::types::uint64
Type constraint
((self >= 10) and (self <= 120000))
- typedef nokia_srlinux::network_instance::protocols::isis::instance::timers::spf_second_wait_t¶
Base type
yang::types::uint64
Type constraint
((self >= 10) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::ldp::graceful_restart_max_reconnect_time_t¶
Base type
yang::types::uint16
Type constraint
((self >= 10) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::ldp::graceful_restart_max_recovery_time_t¶
Base type
yang::types::uint16
Type constraint
((self >= 30) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::ldp::multipath_max_paths_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::network_instance::protocols::ldp::peers_session_keepalive_holdtime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 45) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::ldp::peers_session_keepalive_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 15) and (self <= 1200))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces_hello_holdtime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 15) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces_hello_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 5) and (self <= 1200))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::targeted_hello_holdtime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 15) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::targeted_hello_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 5) and (self <= 1200))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface_hello_holdtime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 15) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::pim::interface_hello_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::target_hello_holdtime_t¶
Base type
yang::types::uint16
Type constraint
((self >= 15) and (self <= 3600))
- typedef nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::target_hello_interval_t¶
Base type
yang::types::uint16
Type constraint
((self >= 5) and (self <= 1200))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance_advertise_router_capability_t¶
Base type
string
Type constraint
(self in ['false', 'link', 'area', 'as'])
- typedef nokia_srlinux::network_instance::protocols::ospf::instance_preference_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance_reference_bandwidth_t¶
Base type
yang::types::uint64
Type constraint
((self >= 1) and (self <= 8000000000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::asbr_trace_path_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::int32')) and (int(self) >= 0)) and (int(self) <= 31)) or (self == 'none'))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::export_limit_log_percent_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 100))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::export_limit_number_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::external_db_overflow_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 2147483647))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::external_db_overflow_limit_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 2147483647))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers_incremental_spf_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers_lsa_accumulate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers_lsa_arrival_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 600000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers_redistribute_delay_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::area_range_ip_prefix_mask_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_dead_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 2) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_priority_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_retransmit_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_transit_delay_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::area::stub_default_metric_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::overload::overload_on_boot_timeout_t¶
Base type
yang::types::uint32
Type constraint
((self >= 60) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::overload::rtr_adv_lsa_limit_max_lsa_count_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::overload::rtr_adv_lsa_limit_overload_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 1800))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers::lsa_generate_lsa_initial_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10) and (self <= 600000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers::lsa_generate_lsa_second_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10) and (self <= 600000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers::lsa_generate_max_lsa_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10) and (self <= 600000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers::spf_wait_spf_initial_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers::spf_wait_spf_max_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10) and (self <= 120000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::timers::spf_wait_spf_second_wait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 10) and (self <= 100000))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::lsdb_type_t¶
Base type
string
Type constraint
(self in ['all', 'router', 'network', 'summary', 'nssa', 'external', 'opaque', 'inter-area-prefix', 'inter-area-router', 'intra-area-prefix'])
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::routes_dest_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::spf_dest_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::interface_assert_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 300))
- typedef nokia_srlinux::network_instance::protocols::pim::interface_dr_priority_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 4294967295))
- typedef nokia_srlinux::network_instance::protocols::pim::interface_hello_multiplier_t¶
Base type
yang::types::uint32
Type constraint
((self >= 20) and (self <= 100))
- typedef nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::rendezvous_point_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::spt_switchover::group_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::protocols::pim::spt_switchover::group_threshold_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 1)) and (int(self) <= 4294967294)) or (self == 'infinity'))
- typedef nokia_srlinux::network_instance::protocols::pim::ssm::ssm_ranges::group_range_ip_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::all_event_types_group_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::all_event_types_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::assert_group_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::assert_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::data_exception_group_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::data_exception_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::database_group_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::database_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::join_prune_group_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::join_prune_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::register_group_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::register_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::segment_routing::mpls::local_prefix_sid_ipv4_label_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1048575))
- typedef nokia_srlinux::network_instance::segment_routing::mpls::local_prefix_sid_ipv6_label_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1048575))
- typedef nokia_srlinux::network_instance::segment_routing::mpls::local_prefix_sid_prefix_sid_index_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 4))
- typedef nokia_srlinux::network_instance::static_routes::route_preference_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::network_instance::traffic_engineering::interface_te_metric_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16777215))
- typedef nokia_srlinux::network_instance::traffic_engineering::admin_groups::group_bit_position_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 31))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_dead_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_keepalive_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_max_pce_init_lsps_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 8191))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_redelegation_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 3600))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_unknown_message_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::system::sync::ptp::instance::port_ds_list::source::peer_ip_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_local_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_excluding_all_zero
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero'))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_preference_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 100))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_route_preference_t¶
Base type
string
Type constraint
(self in ['inband', 'outband', 'both'])
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_tls_client_profile_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 247))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_tls_wait_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 60) and (self <= 255))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::state_timer_timer_action_t¶
Base type
string
Type constraint
(self in ['none', 'remove'])
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::state_timer_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 3600))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_association_id_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_association_source_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_excluding_all_zero
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero'))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_disjointness_type_t¶
Base type
string
Type constraint
(self in ['strict', 'loose'])
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_diversity_type_t¶
Base type
string
Type constraint
(self in ['none', 'link', 'node', 'srlg-link', 'srlg-node'])
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::policy_association_id_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::policy_association_source_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_excluding_all_zero
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero'))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_candidate_path_preference_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_color_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 4294967295))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_endpoint_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_excluding_all_zero
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero'))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_head_end_t¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or (self == 'local'))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_metric_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16777215))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_re_optimization_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 360))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy_retry_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 600))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::ip_hop_type_t¶
Base type
string
Type constraint
(self in ['strict', 'loose'])
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::ip_ip_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::entropy_label_transmit_t¶
Base type
string
Type constraint
(self in ['enable', 'disable'])
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list_segment_list_index_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 32))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list_segment_list_preference_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list_segment_list_type_t¶
Base type
string
Type constraint
(self in ['primary', 'secondary', 'standby'])
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::priority_hold_priority_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 7))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::priority_setup_priority_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 7))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_exclude_hop_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address_excluding_all_zero
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero'))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_hop_limit_t¶
Base type
yang::types::uint8
Type constraint
((self >= 2) and (self <= 255))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_local_sr_protection_t¶
Base type
string
Type constraint
(self in ['none', 'preferred', 'mandated'])
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_metric_type_t¶
Base type
string
Type constraint
(self in ['igp', 'te'])
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::segment_depth_additional_frr_segment_limit_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 3))
- typedef nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::segment_depth_segment_limit_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 14))
- typedef nokia_srlinux::oam::ethcfm::domain_dns_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 43))
- typedef nokia_srlinux::oam::ethcfm::domain_mac_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[0-9A-Fa-f]{2}(?::[0-9A-Fa-f]{2}){5})$(?!\\n\\Z)'})
- typedef nokia_srlinux::oam::ethcfm::domain_name_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 43))
- typedef nokia_srlinux::oam::ethcfm::sender_id_chassis_local_name_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 45))
- typedef nokia_srlinux::oam::ethcfm::domain::association_icc_value_t¶
Base type
string
Type constraint
((std::length(self) >= 8) and (std::length(self) <= 13))
- typedef nokia_srlinux::oam::ethcfm::domain::association_id_t¶
Base type
string
Type constraint
(((std::length(self) >= 3) and (std::length(self) <= 15)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:[0-9A-Fa-f]{6}(?::[0-9A-Fa-f]{8}))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::oam::ethcfm::domain::association_name_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 45))
- typedef nokia_srlinux::oam::ethcfm::domain::association_vid_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 4094))
- typedef nokia_srlinux::oam::ethcfm::domain::association::ccm_hold_time_delay_timeout_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 1000))
- typedef nokia_srlinux::oam::ethcfm::domain::association::remote_mep_auto_discovery_aging_timer_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 1)) and (int(self) <= 86400)) or (self == 'none'))
- typedef nokia_srlinux::oam::ippm::source_udp_port_pools::port_application_assignment_t¶
Base type
string
Type constraint
(self in ['oam-pm-ip', 'link-measurement'])
- typedef nokia_srlinux::oam::ippm::source_udp_port_pools::port_port_number_t¶
Base type
nokia_srlinux::types::srl_nokia_common::port_number
Type constraint
((self >= 64374) and (self <= 64383))
- typedef nokia_srlinux::oam::link_measurement::measurement_template_delay_t¶
Base type
string
Type constraint
(self in ['minimum', 'maximum', 'average'])
- typedef nokia_srlinux::oam::link_measurement::measurement_template_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 10))
- typedef nokia_srlinux::oam::link_measurement::measurement_template_last_reported_delay_hold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 86400))
- typedef nokia_srlinux::oam::link_measurement::measurement_template_unidirectional_measurement_t¶
Base type
string
Type constraint
(self in ['derived', 'actual'])
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp_dscp_t¶
Base type
nokia_srlinux::types::srl_nokia_common::dscp
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::dscp_value')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::dscp_name'))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::stamp_pad_tlv_size_t¶
Base type
yang::types::uint32
Type constraint
(((self >= 3) and (self <= 9502)) or (self == 0))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp_source_udp_port_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::port_number')) and (int(self) >= 64374)) and (int(self) <= 64383)) or (self == 'auto'))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp_timestamp_format_t¶
Base type
string
Type constraint
(self in ['ntp', 'ptp'])
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp_ttl_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window_multiplier_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 12))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window_window_integrity_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 100))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::ipv6_destination_discovery_discovery_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 10))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::ipv6_destination_discovery_discovery_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 1800))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::ipv6_destination_discovery_update_interval_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 3600))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window_multiplier_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 900))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window_window_integrity_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 100))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::threshold_absolute_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 100000))
- typedef nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::threshold_relative_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 500))
- typedef nokia_srlinux::oam::performance_monitoring::ethcfm::session_target_t¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::unicast_mac_address') or (yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_ethcfm_types::mep_id_type')))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type_bin_count_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 10))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::bin_bin_number_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 9))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::bin_lower_bound_t¶
Base type
yang::types::uint32
Type constraint
(((self >= 1) and (self <= 4294967295)) or (self == 0))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_clear_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 863999))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_exclude_lowest_bin_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 9))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_lowest_bin_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 9))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_raise_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 864000))
- typedef nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::exclude_from_avg_bins_t¶
Base type
string
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 39)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:all|(?:(?:[0-9]|(?:[0-9]-[0-9]))(?:,(?:[0-9]|(?:[0-9]-[0-9])))*)))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::avg_flr_event_clear_threshold_t¶
Base type
number
Type constraint
((self >= 0) and (self <= 99999))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::avg_flr_event_raise_threshold_t¶
Base type
number
Type constraint
((self >= 1) and (self <= 100000))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::chli_event_clear_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 863999))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::chli_event_raise_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 864000))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::hli_event_clear_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 863999))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::hli_event_raise_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 864000))
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 863999))
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 864000))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::undetermined_availability_event_clear_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 863999))
- typedef nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::undetermined_availability_event_raise_threshold_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 864000))
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 863999))
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 864000))
- typedef nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_dmm_test_test_duration_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 86400))
- typedef nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_dmm_test_test_id_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 0)) and (int(self) <= 2147483647)) or (self == 'auto'))
- typedef nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test_test_duration_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 86400))
- typedef nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test_test_id_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 0)) and (int(self) <= 2147483647)) or (self == 'auto'))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::timing_chli_threshold_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 9))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::timing_consecutive_delta_t_t¶
Base type
yang::types::uint8
Type constraint
((self >= 2) and (self <= 10))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::timing_frames_per_delta_t_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 50))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session_destination_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session_source_ip_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session_source_udp_port_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 64374)) and (int(self) <= 64383)) or (self == 'auto'))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session_ttl_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::forwarding_next_hop_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::stamp_test_duration_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 86400))
- typedef nokia_srlinux::oam::performance_monitoring::ip::session::stamp_test_id_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) and (int(self) >= 0)) and (int(self) <= 2147483647)) or (self == 'auto'))
- typedef nokia_srlinux::oam::stamp::session_reflector_inactivity_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 604800))
- typedef nokia_srlinux::oam::stamp::session_reflector::network_instance_udp_port_t¶
Base type
yang::types::uint16
Type constraint
(((self >= 64364) and (self <= 64373)) or (self == 862))
- typedef nokia_srlinux::oam::stamp::session_reflector::network_instance::ip_prefix_ip_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::oam::twamp::server::network_instance_control_packet_dscp_t¶
Base type
nokia_srlinux::types::srl_nokia_common::dscp
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::dscp_value')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::dscp_name'))
- typedef nokia_srlinux::oam::twamp::server::network_instance_maximum_connections_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::oam::twamp::server::network_instance_maximum_sessions_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 128))
- typedef nokia_srlinux::oam::twamp::server::network_instance_servwait_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 604800))
- typedef nokia_srlinux::oam::twamp::server::network_instance::client_connection_maximum_connections_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::oam::twamp::server::network_instance::client_connection_maximum_sessions_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 128))
- typedef nokia_srlinux::oam::twamp::server::network_instance::client_connection_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::platform::chassis_mac_address_allocation_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 8192))
- typedef nokia_srlinux::platform::control_slot_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:A|B)$(?!\\n\\Z)'})
- typedef nokia_srlinux::platform::fabric_slot_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::platform::linecard_slot_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 8))
- typedef nokia_srlinux::platform::vxdp_cpu_set_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 1024))
- typedef nokia_srlinux::platform::chassis::power::redundancy_mode_t¶
Base type
string
Type constraint
(self in ['feed', 'module', 'none'])
- typedef nokia_srlinux::platform::linecard::forwarding_complex_name_t¶
Base type
string
Type constraint
(self in ['0', '1'])
- typedef nokia_srlinux::platform::linecard::forwarding_complex::pipeline_index_t¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 7)) or (self in ['egress', 'ingress']))
- typedef nokia_srlinux::platform::redundancy::synchronization::overlay_synchronization_frequency_t¶
Base type
yang::types::uint32
Type constraint
((self >= 30) and (self <= 65535))
- typedef nokia_srlinux::platform::resource_management::unified_forwarding_resources_alpm_t¶
Base type
string
Type constraint
(self in ['disabled', 'enabled', 'high-scale'])
- typedef nokia_srlinux::platform::resource_management::unified_forwarding_resources_ipv6_128bit_lpm_entries_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 8192))
- typedef nokia_srlinux::platform::resource_management::unified_forwarding_resources_requested_extra_ip_host_entries_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 262144))
- typedef nokia_srlinux::routing_policy::community_set_member_t¶
Base type
string
Type constraint
((((((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_well_known_type') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_type')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_large_community_type')) or (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_type') and ((((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:color:[01]{2}:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})))) or (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_regexp_type') and ((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:[^\r\n]*:[^\r\n]*)$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:[^\r\n]*:[^\r\n]*)$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:ext:[^\r\n]*:[^\r\n]*)$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:bgp\\-tunnel\\-encap:[^\r\n]*)$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:[a-z]+:[0-9]+:[0-9]+)$(?!\\n\\Z)'})))) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_large_community_regexp_type')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_regexp_type'))
- typedef nokia_srlinux::routing_policy::policy::statement::action::bgp::med_set_t¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint32')) or (self == 'route-table-cost'))
- typedef nokia_srlinux::routing_policy::policy::statement::action::bgp::origin_set_t¶
Base type
string
Type constraint
(self in ['igp', 'egp', 'incomplete'])
- typedef nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::prepend_as_number_t¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_policy_types::as_number')) or (self == 'auto'))
- typedef nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::prepend_repeat_n_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 50))
- typedef nokia_srlinux::routing_policy::policy::statement::match::isis_level_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 2))
- typedef nokia_srlinux::routing_policy::policy::statement::match::isis_route_type_t¶
Base type
string
Type constraint
(self in ['internal', 'external'])
- typedef nokia_srlinux::routing_policy::policy::statement::match::ospf_instance_id_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::routing_policy::policy::statement::match::bgp::as_path_length_value_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::routing_policy::policy::statement::match::bgp::evpn_route_type_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 5))
- typedef nokia_srlinux::routing_policy::prefix_set::prefix_ip_prefix_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::routing_policy::prefix_set::prefix_mask_length_range_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[0-9]+\\.\\.[0-9]+)|exact)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::configuration_max_candidates_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::system::configuration_max_checkpoints_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::system::dns_server_list_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::event_handler_run_as_user_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::gnmi_server_commit_confirmed_timeout_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 86400))
- typedef nokia_srlinux::system::gnmi_server_rate_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::gnmi_server_session_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::gnmi_server_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::gnmi_server_trace_options_t¶
Base type
string
Type constraint
(self in ['request', 'response', 'common', 'grpc'])
- typedef nokia_srlinux::system::gribi_server_rate_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::gribi_server_session_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::gribi_server_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::gribi_server_trace_options_t¶
Base type
string
Type constraint
(self in ['request', 'response', 'common', 'grpc'])
- typedef nokia_srlinux::system::json_rpc_server_commit_confirmed_timeout_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 86400))
- typedef nokia_srlinux::system::json_rpc_server_trace_options_t¶
Base type
string
Type constraint
(self in ['request', 'response', 'common'])
- typedef nokia_srlinux::system::lldp_trace_options_t¶
Base type
string
Type constraint
(self in ['received', 'transmitted', 'common'])
- typedef nokia_srlinux::system::mtu_default_ip_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1280) and (self <= 9486))
- typedef nokia_srlinux::system::mtu_default_l2_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1500) and (self <= 9500))
- typedef nokia_srlinux::system::mtu_default_mpls_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1284) and (self <= 9496))
- typedef nokia_srlinux::system::mtu_default_port_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1500) and (self <= 9500))
- typedef nokia_srlinux::system::mtu_min_path_mtu_t¶
Base type
yang::types::uint16
Type constraint
((self >= 552) and (self <= 9232))
- typedef nokia_srlinux::system::name_host_name_t¶
Base type
string
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 63)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9A-Za-z]|[0-9A-Za-z][\\-0-9A-Za-z]*[0-9A-Za-z])\\.)*(?:[0-9A-Za-z]|[0-9A-Za-z][\\-0-9A-Za-z]*[0-9A-Za-z]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::system::ntp_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::p4rt_server_rate_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::p4rt_server_session_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::p4rt_server_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::p4rt_server_trace_options_t¶
Base type
string
Type constraint
(self in ['request', 'response', 'common', 'grpc'])
- typedef nokia_srlinux::system::ra_guard_policy_action_t¶
Base type
string
Type constraint
(self in ['accept', 'discard'])
- typedef nokia_srlinux::system::ra_guard_policy_hop_limit_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::system::ra_guard_policy_router_preference_t¶
Base type
string
Type constraint
(self in ['high', 'medium', 'low'])
- typedef nokia_srlinux::system::sflow_dscp_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 63))
- typedef nokia_srlinux::system::sflow_sample_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 2000000))
- typedef nokia_srlinux::system::sflow_sample_size_t¶
Base type
yang::types::uint16
Type constraint
(self in [256, 512])
- typedef nokia_srlinux::system::sflow_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::aaa::server_group_timeout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 3600))
- typedef nokia_srlinux::system::aaa::authentication::admin_user_role_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::aaa::authentication::admin_user_spiffe_ids_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:\\^spiffe://[^\r\n]*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::aaa::authentication::password_aging_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 500))
- typedef nokia_srlinux::system::aaa::authentication::password_hash_method_t¶
Base type
string
Type constraint
(self in ['ar2', 'sha2'])
- typedef nokia_srlinux::system::aaa::authentication::password_history_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 20))
- typedef nokia_srlinux::system::aaa::authentication::user_role_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::aaa::authentication::user_spiffe_ids_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:\\^spiffe://[^\r\n]*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::aaa::authentication::user_username_t¶
Base type
nokia_srlinux::types::srl_nokia_common::name
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::aaa::authentication::password::complexity_rules_maximum_length_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 1023))
- typedef nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_length_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 12))
- typedef nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_lowercase_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 10))
- typedef nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_numeric_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 10))
- typedef nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_special_character_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 10))
- typedef nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_uppercase_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 10))
- typedef nokia_srlinux::system::aaa::authentication::password::lockout_policy_attempts_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 64))
- typedef nokia_srlinux::system::aaa::authentication::password::lockout_policy_lockout_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 1440))
- typedef nokia_srlinux::system::aaa::authentication::password::lockout_policy_time_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 1440))
- typedef nokia_srlinux::system::aaa::authorization::role_rolename_t¶
Base type
nokia_srlinux::types::srl_nokia_common::name
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::aaa::authorization::role_services_t¶
Base type
string
Type constraint
(self in ['cli', 'gnmi', 'gnoi', 'gnsi', 'gribi', 'netconf', 'p4rt', 'json-rpc', 'ftp', 'grpc-reflection'])
- typedef nokia_srlinux::system::aaa::authorization::role::tacacs_priv_lvl_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 15))
- typedef nokia_srlinux::system::ntp::server_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::host
Type constraint
((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ip_address') and (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::domain_name'))
- typedef nokia_srlinux::system::authentication::keychain::key::receive_lifetime_end_time_t¶
Base type
string
Type constraint
((self == 'forever') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::date_and_time'))
- typedef nokia_srlinux::system::boot::autoboot_attempts_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 10))
- typedef nokia_srlinux::system::boot::autoboot_timeout_t¶
Base type
yang::types::uint32
Type constraint
((self >= 200) and (self <= 3600))
- typedef nokia_srlinux::system::configuration::role_name_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::configuration::role::rule_path_reference_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[ -"#-&\\(-\\*\\+-\\-\\.-;=\\?-\\]\\^-\\{\\|\\}~]+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::options_bootfile_name_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 128))
- typedef nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::options_hostname_t¶
Base type
string
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 63)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[A-Za-z]|[A-Za-z][\\-\\.0-9A-Z_a-z]*[0-9A-Za-z]))*(?:[A-Za-z]|[A-Za-z][\\-\\.0-9A-Z_a-z]*[0-9A-Za-z]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::options_tftp_server_name_t¶
Base type
string
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 63)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[A-Za-z]|[A-Za-z][\\-\\.0-9A-Z_a-z]*[0-9A-Za-z]))*(?:[A-Za-z]|[A-Za-z][\\-\\.0-9A-Z_a-z]*[0-9A-Za-z]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::system::event_handler::instance_paths_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[ -"#-&\\(-\\*\\+-\\-\\.-;=\\?-\\]\\^-\\{\\|\\}~]+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::event_handler::instance_upython_script_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[^\\./][^/]*)|(?:\\.[^\\./]+)|(?:\\.\\.[^/])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::ssh_server::network_instance_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::p4rt_server::network_instance_tls_profile_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 247))
- typedef nokia_srlinux::system::gnmi_server::network_instance_yang_models_t¶
Base type
string
Type constraint
(self in ['native', 'openconfig'])
- typedef nokia_srlinux::system::p4rt_server::unix_socket_tls_profile_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 247))
- typedef nokia_srlinux::system::gnmi_server::unix_socket_yang_models_t¶
Base type
string
Type constraint
(self in ['native', 'openconfig'])
- typedef nokia_srlinux::system::json_rpc_server::network_instance::http_session_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 100))
- typedef nokia_srlinux::system::json_rpc_server::network_instance::http_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::json_rpc_server::network_instance::https_session_limit_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 100))
- typedef nokia_srlinux::system::json_rpc_server::network_instance::https_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::json_rpc_server::network_instance::https_tls_profile_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 247))
- typedef nokia_srlinux::system::lldp::interface::bgp_auto_discovery_peering_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::logging::buffer_filter_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[!%\\(-\\*,-/0-9;<>@-\\\\\\]-_a-\\}])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::logging::buffer_persist_t¶
Base type
yang::types::uint32
Type constraint
(((self >= 60) and (self <= 604800)) or (self == 0))
- typedef nokia_srlinux::system::logging::console_filter_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[!%\\(-\\*,-/0-9;<>@-\\\\\\]-_a-\\}])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::logging::file_filter_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[!%\\(-\\*,-/0-9;<>@-\\\\\\]-_a-\\}])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::logging::filter_filter_name_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[!%\\(-\\*,-/0-9;<>@-\\\\\\]-_a-\\}])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::logging::remote_server_filter_t¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[!%\\(-\\*,-/0-9;<>@-\\\\\\]-_a-\\}])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::system::logging::remote_server_host_t¶
Base type
nokia_srlinux::types::srl_nokia_common::host
Type constraint
((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ip_address') and (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::domain_name'))
- typedef nokia_srlinux::system::logging::remote_server_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::maintenance::group::members::bgp::network_instance_neighbor_t¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_with_zone') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_with_zone'))
- typedef nokia_srlinux::system::maintenance::group::members::bgp::network_instance_peer_group_t¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 64))
- typedef nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::remote_encap_t¶
Base type
string
Type constraint
(self in ['l2ogre', 'l3ogre'])
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::timers_activation_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 100))
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::timers_boot_timer_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 6000))
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment_name_t¶
Base type
nokia_srlinux::types::srl_nokia_common::name
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 32))
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::next_hop_l3_next_hop_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes_next_hop_t¶
Base type
string
Type constraint
(self == 'use-system-ipv4-address')
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg_preference_value_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg::capabilities_ac_df_t¶
Base type
string
Type constraint
(self in ['include', 'exclude'])
- typedef nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes::ethernet_segment_originating_ip_t¶
Base type
string
Type constraint
(self == 'use-system-ipv4-address')
- typedef nokia_srlinux::system::packet_link_qualification::profile::packet_generator_packet_rate_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::system::packet_link_qualification::profile::packet_generator_packet_size_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::system::protocols::bgp_restart_max_wait_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 3600))
- typedef nokia_srlinux::system::sflow::collector_collector_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::sflow::collector_collector_id_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 8))
- typedef nokia_srlinux::system::sflow::collector_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::snmp::access_group::community_entry_prefix_list_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_prefix
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::system::snmp::access_group::security_entry::authentication_password_t¶
Base type
string
Type constraint
((std::length(self) >= 8) and (std::length(self) <= 255))
- typedef nokia_srlinux::system::snmp::access_group::security_entry::privacy_password_t¶
Base type
string
Type constraint
((std::length(self) >= 8) and (std::length(self) <= 255))
- typedef nokia_srlinux::system::sync::freq_clock_network_type_t¶
Base type
string
Type constraint
(self in ['sdh', 'sonet'])
- typedef nokia_srlinux::system::sync::freq_clock_wait_to_restore_t¶
Base type
yang::types::int8
Type constraint
((self >= 0) and (self <= 12))
- typedef nokia_srlinux::system::sync::ptp_ptp_profile_t¶
Base type
string
Type constraint
(self == 'itug8275dot1')
- typedef nokia_srlinux::system::sync::freq_references::instance_instance_number_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 5))
- typedef nokia_srlinux::system::sync::freq_references::instance_priority_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 5))
- typedef nokia_srlinux::system::sync::gnss::gnss_a_antenna_cable_delay_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 1000))
- typedef nokia_srlinux::system::sync::gnss::gnss_a_elevation_mask_angle_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 89))
- typedef nokia_srlinux::system::sync::gnss::gnss_b_antenna_cable_delay_t¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 1000))
- typedef nokia_srlinux::system::sync::gnss::gnss_b_elevation_mask_angle_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 89))
- typedef nokia_srlinux::system::sync::ptp::instance_instance_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 2))
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_announce_receipt_timeout_t¶
Base type
yang::types::uint8
Type constraint
((self >= 2) and (self <= 10))
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_domain_number_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_instance_type_t¶
Base type
string
Type constraint
(self == 'bc')
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_local_priority_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_log_announce_interval_t¶
Base type
yang::types::int8
Type constraint
((self >= -3) and (self <= 4))
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_priority1_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::system::sync::ptp::instance::default_ds_priority2_t¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 255))
- typedef nokia_srlinux::system::sync::ptp::instance::network_instances_peer_limit_t¶
Base type
yang::types::int32
Type constraint
((self >= 0) and (self <= 512))
- typedef nokia_srlinux::system::sync::ptp::instance::network_instances_source_address_t¶
Base type
nokia_srlinux::types::srl_nokia_common::ip_address
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::system::sync::ptp::instance::port_ds_list_dest_mac_t¶
Base type
string
Type constraint
(self in ['forwardable', 'non-forwardable'])
- typedef nokia_srlinux::system::sync::ptp::instance::port_ds_list_local_priority_t¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 255))
- typedef nokia_srlinux::system::sync::ptp::instance::port_ds_list_log_min_delay_req_interval_t¶
Base type
yang::types::int8
Type constraint
(self == -6)
- typedef nokia_srlinux::system::sync::ptp::instance::port_ds_list_log_sync_interval_t¶
Base type
yang::types::int8
Type constraint
(self == -6)
- typedef nokia_srlinux::system::sync::ptp::instance::port_ds_list_port_index_t¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 1500))
- typedef nokia_srlinux::system::tls::server_profile_name_t¶
Base type
nokia_srlinux::types::srl_nokia_common::name
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 247))
- typedef nokia_srlinux::transport_security::macsec::mka::policy_hello_interval_t¶
Base type
yang::types::uint32
Type constraint
(((self >= 1) and (self <= 6)) or (self == 0))
- typedef nokia_srlinux::transport_security::macsec::mka::policy_maximum_number_of_peers_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 512))
- typedef nokia_srlinux::tunnel_interface::vxlan_interface_index_t¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 99999999))
- typedef nokia_srlinux::tunnel_interface::vxlan_interface::egress_source_ip_t¶
Base type
string
Type constraint
(self == 'use-system-ipv4-address')
- typedef nokia_srlinux::tunnel_interface::vxlan_interface::ingress_vni_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16777215))
- typedef nokia_srlinux::tunnel_interface::vxlan_interface::egress::inner_ethernet_header_source_mac_t¶
Base type
string
Type constraint
(self == 'use-system-mac')
- typedef nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::destination_vni_t¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 16777215))
- typedef nokia_srlinux::types::srl_nokia_common::dotted_quad¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_bgp::community_type¶
Base type
string
Type constraint
(self in ['standard', 'extended', 'large'])
- typedef nokia_srlinux::types::srl_nokia_bgp::ip_ecmp¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::types::srl_nokia_common::percentage¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 100))
- typedef nokia_srlinux::types::srl_nokia_bgp_evpn::ethernet_tag_id¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 16777215))
- typedef nokia_srlinux::types::srl_nokia_boot::client_id¶
Base type
string
Type constraint
(self == 'serial')
- typedef nokia_srlinux::types::srl_nokia_bridge_table_proxy_arp_nd::neighbor_type¶
Base type
string
Type constraint
(self in ['router', 'host'])
- typedef nokia_srlinux::types::srl_nokia_common::admin_state¶
Base type
string
Type constraint
(self in ['enable', 'disable'])
- typedef nokia_srlinux::types::srl_nokia_common::alphanumeric¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[!#-\\)\\+-;=\\?-Z\\^-z\\|~][ !#-\\)\\+-;=\\?-Z\\^-z\\|~]*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_policy_types::as_number¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::types::srl_nokia_common::classify_profile¶
Base type
string
Type constraint
(self in ['in', 'out', 'exceed', 'in-plus', 'in-low', 'out-low'])
- typedef nokia_srlinux::types::srl_nokia_common::date_and_time¶
Base type
string
Type constraint
(((std::length(self) >= 20) and (std::length(self) <= 32)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[\\+\\-]\\d{2}:\\d{2}))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::description¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 255))
- typedef nokia_srlinux::types::srl_nokia_common::domain_name¶
Base type
string
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 253)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:(?:[0-9A-Z_a-z](?:[\\-0-9A-Z_a-z]){0,61})?[0-9A-Za-z]\\.)*(?:[0-9A-Z_a-z](?:[\\-0-9A-Z_a-z]){0,61})?[0-9A-Za-z]\\.?)|\\.)$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::dscp¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::dscp_value')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::dscp_name'))
- typedef nokia_srlinux::types::srl_nokia_common::dscp_name¶
Base type
string
Type constraint
(self in ['CS0', 'LE', 'CS1', 'AF11', 'AF12', 'AF13', 'CS2', 'AF21', 'AF22', 'AF23', 'CS3', 'AF31', 'AF32', 'AF33', 'CS4', 'AF41', 'AF42', 'AF43', 'CS5', 'EF', 'CS6', 'CS7'])
- typedef nokia_srlinux::types::srl_nokia_common::dscp_value¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 63))
- typedef nokia_srlinux::types::srl_nokia_common::esi¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[0-9A-Fa-f]{2}(?::[0-9A-Fa-f]{2}){9})$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::evi¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 65535))
- typedef nokia_srlinux::types::srl_nokia_common::hex_string¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[0-9A-Fa-f]{2}(?::[0-9A-Fa-f]{2})*)?)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::host¶
Base type
string
Type constraint
((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ip_address') and (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::domain_name'))
- typedef nokia_srlinux::types::srl_nokia_common::interface_all¶
Base type
nokia_srlinux::types::srl_nokia_common::interface_name
Type constraint
(((std::length(self) >= 3) and (std::length(self) <= 20)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:mgmt0|mgmt0-standby|system0|lo(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])|lif-[^\r\n]*|vhn-[^\r\n]*|enp(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])s(?:0|[1-9]|[12][0-9]|3[01])f[0-7]|ethernet-(?:[1-9](?:\\d){0,1}(?:/[a-d])?(?:/[1-9](?:\\d){0,1})?/(?:(?:[1-9](?:\\d){0,1})|(?:1[01]\\d)|(?:12[0-8])))|irb(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])|lag(?:(?:[1-9](?:\\d){0,2})|(?:1000))))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::interface_name¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_common::ip_address¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))
- typedef nokia_srlinux::types::srl_nokia_common::ip_address_excluding_all_zero¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero'))
- typedef nokia_srlinux::types::srl_nokia_common::ip_address_with_zone¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address_with_zone') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address_with_zone'))
- typedef nokia_srlinux::types::srl_nokia_common::ip_prefix¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_prefix') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_prefix'))
- typedef nokia_srlinux::types::srl_nokia_common::ipv4_address¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero¶
Base type
nokia_srlinux::types::srl_nokia_common::ipv4_address
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[^\r\n]*[1-9][^\r\n]*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv4_address_with_zone¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv4_prefix¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])/(?:(?:[0-9])|(?:[12][0-9])|(?:3[0-2])))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv4_prefix_with_host_bits¶
Base type
nokia_srlinux::types::srl_nokia_common::ipv4_prefix
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_common::ipv6_address¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?::|[0-9A-Fa-f]{0,4}):)(?:[0-9A-Fa-f]{0,4}:){0,5}(?:(?:(?:[0-9A-Fa-f]{0,4}:)?(?::|[0-9A-Fa-f]{0,4}))|(?:(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9]))))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero¶
Base type
nokia_srlinux::types::srl_nokia_common::ipv6_address
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[^\r\n]*[1-9A-Fa-f][^\r\n]*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv6_address_type¶
Base type
string
Type constraint
(self in ['global-unicast', 'link-local-unicast'])
- typedef nokia_srlinux::types::srl_nokia_common::ipv6_address_with_zone¶
Base type
string
Type constraint
((std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?::|[0-9A-Fa-f]{0,4}):)(?:[0-9A-Fa-f]{0,4}:){0,5}(?:(?:(?:[0-9A-Fa-f]{0,4}:)?(?::|[0-9A-Fa-f]{0,4}))|(?:(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))(?:%[^\r\n]+)?)$(?!\\n\\Z)'}) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[^:]+:){6}(?:(?:[^:]+:[^:]+)|(?:[^\r\n]*\\.[^\r\n]*)))|(?:(?:(?:[^:]+:)*[^:]+)?::(?:(?:[^:]+:)*[^:]+)?)(?:%[^\r\n]+)?)$(?!\\n\\Z)'})) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[^%]+)(?:%(?:mgmt0\\.0|system0\\.0|lo(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,3})|lif-[^\r\n]*\\.(?:0|[1-9](?:\\d){0,3})|vhn-[^\r\n]*\\.(?:0|[1-9](?:\\d){0,3})|enp(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])s(?:0|[1-9]|[12][0-9]|3[01])f[0-7]\\.(?:0|[1-9](?:\\d){0,3})|ethernet-(?:[1-9](?:\\d){0,1}(?:/[a-d])?(?:/[1-9](?:\\d){0,1})?/(?:(?:[1-9](?:\\d){0,1})|(?:1[01]\\d)|(?:12[0-8])))\\.(?:[0]|[1-9](?:\\d){0,3})|irb(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,3})|lag(?:(?:[1-9](?:\\d){0,2})|(?:1000))\\.(?:0|[1-9](?:\\d){0,3})))?)$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::ipv6_prefix¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?::|[0-9A-Fa-f]{0,4}):)(?:[0-9A-Fa-f]{0,4}:){0,5}(?:(?:(?:[0-9A-Fa-f]{0,4}:)?(?::|[0-9A-Fa-f]{0,4}))|(?:(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))(?:/(?:(?:[0-9])|(?:[0-9]{2})|(?:1[01][0-9])|(?:12[0-8]))))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::ipv6_prefix_with_host_bits¶
Base type
nokia_srlinux::types::srl_nokia_common::ipv6_prefix
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_common::local_file¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:/[\\-\\.0-9A-Z_a-z]+)+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::mac_address¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[0-9A-Fa-f]{2}(?::[0-9A-Fa-f]{2}){5})$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved¶
Base type
yang::types::uint32
Type constraint
((self >= 16) and (self <= 1048575))
- typedef nokia_srlinux::types::srl_nokia_common::mpls_label_with_implicit_and_explicit_null¶
Base type
string
Type constraint
((yang::is_int(self) and yang::validate_type(int(self),'nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved')) or (self in ['IPV4_EXPLICIT_NULL', 'IPV6_EXPLICIT_NULL', 'IMPLICIT_NULL']))
- typedef nokia_srlinux::types::srl_nokia_common::name¶
Base type
nokia_srlinux::types::srl_nokia_common::alphanumeric
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 255))
- typedef nokia_srlinux::types::srl_nokia_common::name_without_space¶
Base type
nokia_srlinux::types::srl_nokia_common::name
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[!#-\\)\\+-;=\\?-Z\\^-z\\|~][!#-\\)\\+-;=\\?-Z\\^-z\\|~]*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::next_hop_type¶
Base type
string
Type constraint
((self == 'use-system-ipv4-address') or (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ip_address') and (yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address'))))
- typedef nokia_srlinux::types::srl_nokia_common::port_number¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 65535))
- typedef nokia_srlinux::types::srl_nokia_common::restricted_name¶
Base type
string
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 247)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:[!#-\\)\\+-\\.0-;=\\?-Z\\^-z\\|~][ !#-\\)\\+-\\.0-;=\\?-Z\\^-z\\|~]*)$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::route_distinguisher¶
Base type
string
Type constraint
(((yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_0') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_1')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_2')) or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_2b'))
- typedef nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_0¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_1¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_2¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::route_distinguisher_type_2b¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9])[^\r\n](?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_common::routing_password¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_common::rule_sequence_id¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 128))
- typedef nokia_srlinux::types::srl_nokia_common::subinterface_all¶
Base type
nokia_srlinux::types::srl_nokia_common::subinterface_name
Type constraint
(((std::length(self) >= 5) and (std::length(self) <= 25)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:mgmt0\\.0|system0\\.0|lo(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,3})|lif-[^\r\n]*\\.(?:0|[1-9](?:\\d){0,3})|vhn-[^\r\n]*\\.(?:0|[1-9](?:\\d){0,3})|enp(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])s(?:0|[1-9]|[12][0-9]|3[01])f[0-7]\\.(?:0|[1-9](?:\\d){0,3})|ethernet-(?:[1-9](?:\\d){0,1}(?:/[a-d])?(?:/[1-9](?:\\d){0,1})?/(?:(?:[1-9](?:\\d){0,1})|(?:1[01]\\d)|(?:12[0-8])))\\.(?:[0]|[1-9](?:\\d){0,3})|irb(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,3})|lag(?:(?:[1-9](?:\\d){0,2})|(?:1000))\\.(?:0|[1-9](?:\\d){0,3})))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::subinterface_name¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_common::subinterface_no_mgmt¶
Base type
nokia_srlinux::types::srl_nokia_common::subinterface_name
Type constraint
(((std::length(self) >= 5) and (std::length(self) <= 25)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:system0\\.0|lo(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,3})|lif-[^\r\n]*\\.(?:0|[1-9](?:\\d){0,3})|vhn-[^\r\n]*\\.(?:0|[1-9](?:\\d){0,3})|enp(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])s(?:0|[1-9]|[12][0-9]|3[01])f[0-7]\\.(?:0|[1-9](?:\\d){0,3})|ethernet-(?:[1-9](?:\\d){0,1}(?:/[a-d])?(?:/[1-9](?:\\d){0,1})?/(?:(?:[1-9](?:\\d){0,1})|(?:1[01]\\d)|(?:12[0-8])))\\.(?:[0]|[1-9](?:\\d){0,3})|irb(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,3})|lag(?:(?:[1-9](?:\\d){0,2})|(?:1000))\\.(?:0|[1-9](?:\\d){0,3})))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::unicast_mac_address¶
Base type
nokia_srlinux::types::srl_nokia_common::mac_address
Type constraint
(std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[0-9A-Fa-f][02468ACEace])(?::[0-9A-Fa-f]{2}){5})$(?!\\n\\Z)'}) and std::validate_type('pydantic.constr',self,{'regex': '^(?:[^\r\n]*[1-9A-Fa-f][^\r\n]*)$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_common::user_password¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_common::uuid¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{12})$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_configuration_role::path_action¶
Base type
string
Type constraint
(self in ['read', 'write', 'deny'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::action_type¶
Base type
string
Type constraint
(self in ['permit', 'deny'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::admin_name¶
Base type
nokia_srlinux::types::srl_nokia_ethcfm_types::string_not_all_spaces
Type constraint
(((std::length(self) >= 1) and (std::length(self) <= 64)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[1-9]|[1-9][0-9]{1,8}|[1-3][0-9]{9}|4[01][0-9]{8}|42[0-8][0-9]{7}|429[0-3][0-9]{6}|4294[0-8][0-9]{5}|42949[0-5][0-9]{4}|429496[0-6][0-9]{3}|4294967[01][0-9]{2}|42949672[0-8][0-9]|429496729[0-5])|(?:[^ \\+0-9_][^\x00-\x1f\x7f-\x9f\xad\\u0378\\u0379\\u0380-\\u0383\\u038b\\u038d\\u03a2\\u0530\\u0557\\u0558\\u058b\\u058c\\u0590\\u05c8-\\u05cf\\u05eb-\\u05ee\\u05f5-\\u0605\\u061c\\u061d\\u06dd\\u070e\\u070f\\u074b\\u074c\\u07b2-\\u07bf\\u07fb\\u07fc\\u082e\\u082f\\u083f\\u085c\\u085d\\u085f\\u086b-\\u089f\\u08b5\\u08be-\\u08d2\\u08e2\\u0984\\u098d\\u098e\\u0991\\u0992\\u09a9\\u09b1\\u09b3-\\u09b5\\u09ba\\u09bb\\u09c5\\u09c6\\u09c9\\u09ca\\u09cf-\\u09d6\\u09d8-\\u09db\\u09de\\u09e4\\u09e5\\u09ff\\u0a00\\u0a04\\u0a0b-\\u0a0e\\u0a11\\u0a12\\u0a29\\u0a31\\u0a34\\u0a37\\u0a3a\\u0a3b\\u0a3d\\u0a43-\\u0a46\\u0a49\\u0a4a\\u0a4e-\\u0a50\\u0a52-\\u0a58\\u0a5d\\u0a5f-\\u0a65\\u0a77-\\u0a80\\u0a84\\u0a8e\\u0a92\\u0aa9\\u0ab1\\u0ab4\\u0aba\\u0abb\\u0ac6\\u0aca\\u0ace\\u0acf\\u0ad1-\\u0adf\\u0ae4\\u0ae5\\u0af2-\\u0af8\\u0b00\\u0b04\\u0b0d\\u0b0e\\u0b11\\u0b12\\u0b29\\u0b31\\u0b34\\u0b3a\\u0b3b\\u0b45\\u0b46\\u0b49\\u0b4a\\u0b4e-\\u0b55\\u0b58-\\u0b5b\\u0b5e\\u0b64\\u0b65\\u0b78-\\u0b81\\u0b84\\u0b8b-\\u0b8d\\u0b91\\u0b96-\\u0b98\\u0b9b\\u0b9d\\u0ba0-\\u0ba2\\u0ba5-\\u0ba7\\u0bab-\\u0bad\\u0bba-\\u0bbd\\u0bc3-\\u0bc5\\u0bc9\\u0bce\\u0bcf\\u0bd1-\\u0bd6\\u0bd8-\\u0be5\\u0bfb-\\u0bff\\u0c0d\\u0c11\\u0c29\\u0c3a-\\u0c3c\\u0c45\\u0c49\\u0c4e-\\u0c54\\u0c57\\u0c5b-\\u0c5f\\u0c64\\u0c65\\u0c70-\\u0c76\\u0c8d\\u0c91\\u0ca9\\u0cb4\\u0cba\\u0cbb\\u0cc5\\u0cc9\\u0cce-\\u0cd4\\u0cd7-\\u0cdd\\u0cdf\\u0ce4\\u0ce5\\u0cf0\\u0cf3-\\u0cff\\u0d04\\u0d0d\\u0d11\\u0d45\\u0d49\\u0d50-\\u0d53\\u0d64\\u0d65\\u0d80\\u0d81\\u0d84\\u0d97-\\u0d99\\u0db2\\u0dbc\\u0dbe\\u0dbf\\u0dc7-\\u0dc9\\u0dcb-\\u0dce\\u0dd5\\u0dd7\\u0de0-\\u0de5\\u0df0\\u0df1\\u0df5-\\u0e00\\u0e3b-\\u0e3e\\u0e5c-\\u0e80\\u0e83\\u0e85\\u0e8b\\u0ea4\\u0ea6\\u0ebe\\u0ebf\\u0ec5\\u0ec7\\u0ece\\u0ecf\\u0eda\\u0edb\\u0ee0-\\u0eff\\u0f48\\u0f6d-\\u0f70\\u0f98\\u0fbd\\u0fcd\\u0fdb-\\u0fff\\u10c6\\u10c8-\\u10cc\\u10ce\\u10cf\\u1249\\u124e\\u124f\\u1257\\u1259\\u125e\\u125f\\u1289\\u128e\\u128f\\u12b1\\u12b6\\u12b7\\u12bf\\u12c1\\u12c6\\u12c7\\u12d7\\u1311\\u1316\\u1317\\u135b\\u135c\\u137d-\\u137f\\u139a-\\u139f\\u13f6\\u13f7\\u13fe\\u13ff\\u169d-\\u169f\\u16f9-\\u16ff\\u170d\\u1715-\\u171f\\u1737-\\u173f\\u1754-\\u175f\\u176d\\u1771\\u1774-\\u177f\\u17de\\u17df\\u17ea-\\u17ef\\u17fa-\\u17ff\\u180e\\u180f\\u181a-\\u181f\\u1879-\\u187f\\u18ab-\\u18af\\u18f6-\\u18ff\\u191f\\u192c-\\u192f\\u193c-\\u193f\\u1941-\\u1943\\u196e\\u196f\\u1975-\\u197f\\u19ac-\\u19af\\u19ca-\\u19cf\\u19db-\\u19dd\\u1a1c\\u1a1d\\u1a5f\\u1a7d\\u1a7e\\u1a8a-\\u1a8f\\u1a9a-\\u1a9f\\u1aae\\u1aaf\\u1abf-\\u1aff\\u1b4c-\\u1b4f\\u1b7d-\\u1b7f\\u1bf4-\\u1bfb\\u1c38-\\u1c3a\\u1c4a-\\u1c4c\\u1c89-\\u1c8f\\u1cbb\\u1cbc\\u1cc8-\\u1ccf\\u1cfb-\\u1cff\\u1dfa\\u1f16\\u1f17\\u1f1e\\u1f1f\\u1f46\\u1f47\\u1f4e\\u1f4f\\u1f58\\u1f5a\\u1f5c\\u1f5e\\u1f7e\\u1f7f\\u1fb5\\u1fc5\\u1fd4\\u1fd5\\u1fdc\\u1ff0\\u1ff1\\u1ff5\\u1fff\\u200b-\\u200f\\u202a-\\u202e\\u2060-\\u206f\\u2072\\u2073\\u208f\\u209d-\\u209f\\u20c0-\\u20cf\\u20f1-\\u20ff\\u218c-\\u218f\\u2427-\\u243f\\u244b-\\u245f\\u2b74\\u2b75\\u2b96\\u2b97\\u2c2f\\u2c5f\\u2cf4-\\u2cf8\\u2d26\\u2d28-\\u2d2c\\u2d2e\\u2d2f\\u2d68-\\u2d6e\\u2d71-\\u2d7e\\u2d97-\\u2d9f\\u2da7\\u2daf\\u2db7\\u2dbf\\u2dc7\\u2dcf\\u2dd7\\u2ddf\\u2e50-\\u2e7f\\u2e9a\\u2ef4-\\u2eff\\u2fd6-\\u2fef\\u2ffc-\\u2fff\\u3040\\u3097\\u3098\\u3100-\\u3104\\u3130\\u318f\\u31bb-\\u31bf\\u31e4-\\u31ef\\u321f\\u4db6-\\u4dbf\\u9ff0-\\u9fff\\ua48d-\\ua48f\\ua4c7-\\ua4cf\\ua62c-\\ua63f\\ua6f8-\\ua6ff\\ua7c0\\ua7c1\\ua7c7-\\ua7f6\\ua82c-\\ua82f\\ua83a-\\ua83f\\ua878-\\ua87f\\ua8c6-\\ua8cd\\ua8da-\\ua8df\\ua954-\\ua95e\\ua97d-\\ua97f\\ua9ce\\ua9da-\\ua9dd\\ua9ff\\uaa37-\\uaa3f\\uaa4e\\uaa4f\\uaa5a\\uaa5b\\uaac3-\\uaada\\uaaf7-\\uab00\\uab07\\uab08\\uab0f\\uab10\\uab17-\\uab1f\\uab27\\uab2f\\uab68-\\uab6f\\uabee\\uabef\\uabfa-\\uabff\\ud7a4-\\ud7af\\ud7c7-\\ud7ca\\ud7fc-\\uf8ff\\ufa6e\\ufa6f\\ufada-\\ufaff\\ufb07-\\ufb12\\ufb18-\\ufb1c\\ufb37\\ufb3d\\ufb3f\\ufb42\\ufb45\\ufbc2-\\ufbd2\\ufd40-\\ufd4f\\ufd90\\ufd91\\ufdc8-\\ufdef\\ufdfe\\ufdff\\ufe1a-\\ufe1f\\ufe53\\ufe67\\ufe6c-\\ufe6f\\ufe75\\ufefd-\\uff00\\uffbf-\\uffc1\\uffc8\\uffc9\\uffd0\\uffd1\\uffd8\\uffd9\\uffdd-\\uffdf\\uffe7\\uffef-\\ufffb\\ufffe\\uffff\\U0001000c\\U00010027\\U0001003b\\U0001003e\\U0001004e\\U0001004f\\U0001005e-\\U0001007f\\U000100fb-\\U000100ff\\U00010103-\\U00010106\\U00010134-\\U00010136\\U0001018f\\U0001019c-\\U0001019f\\U000101a1-\\U000101cf\\U000101fe-\\U0001027f\\U0001029d-\\U0001029f\\U000102d1-\\U000102df\\U000102fc-\\U000102ff\\U00010324-\\U0001032c\\U0001034b-\\U0001034f\\U0001037b-\\U0001037f\\U0001039e\\U000103c4-\\U000103c7\\U000103d6-\\U000103ff\\U0001049e\\U0001049f\\U000104aa-\\U000104af\\U000104d4-\\U000104d7\\U000104fc-\\U000104ff\\U00010528-\\U0001052f\\U00010564-\\U0001056e\\U00010570-\\U000105ff\\U00010737-\\U0001073f\\U00010756-\\U0001075f\\U00010768-\\U000107ff\\U00010806\\U00010807\\U00010809\\U00010836\\U00010839-\\U0001083b\\U0001083d\\U0001083e\\U00010856\\U0001089f-\\U000108a6\\U000108b0-\\U000108df\\U000108f3\\U000108f6-\\U000108fa\\U0001091c-\\U0001091e\\U0001093a-\\U0001093e\\U00010940-\\U0001097f\\U000109b8-\\U000109bb\\U000109d0\\U000109d1\\U00010a04\\U00010a07-\\U00010a0b\\U00010a14\\U00010a18\\U00010a36\\U00010a37\\U00010a3b-\\U00010a3e\\U00010a49-\\U00010a4f\\U00010a59-\\U00010a5f\\U00010aa0-\\U00010abf\\U00010ae7-\\U00010aea\\U00010af7-\\U00010aff\\U00010b36-\\U00010b38\\U00010b56\\U00010b57\\U00010b73-\\U00010b77\\U00010b92-\\U00010b98\\U00010b9d-\\U00010ba8\\U00010bb0-\\U00010bff\\U00010c49-\\U00010c7f\\U00010cb3-\\U00010cbf\\U00010cf3-\\U00010cf9\\U00010d28-\\U00010d2f\\U00010d3a-\\U00010e5f\\U00010e7f-\\U00010eff\\U00010f28-\\U00010f2f\\U00010f5a-\\U00010fdf\\U00010ff7-\\U00010fff\\U0001104e-\\U00011051\\U00011070-\\U0001107e\\U000110bd\\U000110c2-\\U000110cf\\U000110e9-\\U000110ef\\U000110fa-\\U000110ff\\U00011135\\U00011147-\\U0001114f\\U00011177-\\U0001117f\\U000111ce\\U000111cf\\U000111e0\\U000111f5-\\U000111ff\\U00011212\\U0001123f-\\U0001127f\\U00011287\\U00011289\\U0001128e\\U0001129e\\U000112aa-\\U000112af\\U000112eb-\\U000112ef\\U000112fa-\\U000112ff\\U00011304\\U0001130d\\U0001130e\\U00011311\\U00011312\\U00011329\\U00011331\\U00011334\\U0001133a\\U00011345\\U00011346\\U00011349\\U0001134a\\U0001134e\\U0001134f\\U00011351-\\U00011356\\U00011358-\\U0001135c\\U00011364\\U00011365\\U0001136d-\\U0001136f\\U00011375-\\U000113ff\\U0001145a\\U0001145c\\U00011460-\\U0001147f\\U000114c8-\\U000114cf\\U000114da-\\U0001157f\\U000115b6\\U000115b7\\U000115de-\\U000115ff\\U00011645-\\U0001164f\\U0001165a-\\U0001165f\\U0001166d-\\U0001167f\\U000116b9-\\U000116bf\\U000116ca-\\U000116ff\\U0001171b\\U0001171c\\U0001172c-\\U0001172f\\U00011740-\\U000117ff\\U0001183c-\\U0001189f\\U000118f3-\\U000118fe\\U00011900-\\U0001199f\\U000119a8\\U000119a9\\U000119d8\\U000119d9\\U000119e5-\\U000119ff\\U00011a48-\\U00011a4f\\U00011aa3-\\U00011abf\\U00011af9-\\U00011bff\\U00011c09\\U00011c37\\U00011c46-\\U00011c4f\\U00011c6d-\\U00011c6f\\U00011c90\\U00011c91\\U00011ca8\\U00011cb7-\\U00011cff\\U00011d07\\U00011d0a\\U00011d37-\\U00011d39\\U00011d3b\\U00011d3e\\U00011d48-\\U00011d4f\\U00011d5a-\\U00011d5f\\U00011d66\\U00011d69\\U00011d8f\\U00011d92\\U00011d99-\\U00011d9f\\U00011daa-\\U00011edf\\U00011ef9-\\U00011fbf\\U00011ff2-\\U00011ffe\\U0001239a-\\U000123ff\\U0001246f\\U00012475-\\U0001247f\\U00012544-\\U00012fff\\U0001342f-\\U000143ff\\U00014647-\\U000167ff\\U00016a39-\\U00016a3f\\U00016a5f\\U00016a6a-\\U00016a6d\\U00016a70-\\U00016acf\\U00016aee\\U00016aef\\U00016af6-\\U00016aff\\U00016b46-\\U00016b4f\\U00016b5a\\U00016b62\\U00016b78-\\U00016b7c\\U00016b90-\\U00016e3f\\U00016e9b-\\U00016eff\\U00016f4b-\\U00016f4e\\U00016f88-\\U00016f8e\\U00016fa0-\\U00016fdf\\U00016fe4-\\U00016fff\\U000187f8-\\U000187ff\\U00018af3-\\U0001afff\\U0001b11f-\\U0001b14f\\U0001b153-\\U0001b163\\U0001b168-\\U0001b16f\\U0001b2fc-\\U0001bbff\\U0001bc6b-\\U0001bc6f\\U0001bc7d-\\U0001bc7f\\U0001bc89-\\U0001bc8f\\U0001bc9a\\U0001bc9b\\U0001bca0-\\U0001cfff\\U0001d0f6-\\U0001d0ff\\U0001d127\\U0001d128\\U0001d173-\\U0001d17a\\U0001d1e9-\\U0001d1ff\\U0001d246-\\U0001d2df\\U0001d2f4-\\U0001d2ff\\U0001d357-\\U0001d35f\\U0001d379-\\U0001d3ff\\U0001d455\\U0001d49d\\U0001d4a0\\U0001d4a1\\U0001d4a3\\U0001d4a4\\U0001d4a7\\U0001d4a8\\U0001d4ad\\U0001d4ba\\U0001d4bc\\U0001d4c4\\U0001d506\\U0001d50b\\U0001d50c\\U0001d515\\U0001d51d\\U0001d53a\\U0001d53f\\U0001d545\\U0001d547-\\U0001d549\\U0001d551\\U0001d6a6\\U0001d6a7\\U0001d7cc\\U0001d7cd\\U0001da8c-\\U0001da9a\\U0001daa0\\U0001dab0-\\U0001dfff\\U0001e007\\U0001e019\\U0001e01a\\U0001e022\\U0001e025\\U0001e02b-\\U0001e0ff\\U0001e12d-\\U0001e12f\\U0001e13e\\U0001e13f\\U0001e14a-\\U0001e14d\\U0001e150-\\U0001e2bf\\U0001e2fa-\\U0001e2fe\\U0001e300-\\U0001e7ff\\U0001e8c5\\U0001e8c6\\U0001e8d7-\\U0001e8ff\\U0001e94c-\\U0001e94f\\U0001e95a-\\U0001e95d\\U0001e960-\\U0001ec70\\U0001ecb5-\\U0001ed00\\U0001ed3e-\\U0001edff\\U0001ee04\\U0001ee20\\U0001ee23\\U0001ee25\\U0001ee26\\U0001ee28\\U0001ee33\\U0001ee38\\U0001ee3a\\U0001ee3c-\\U0001ee41\\U0001ee43-\\U0001ee46\\U0001ee48\\U0001ee4a\\U0001ee4c\\U0001ee50\\U0001ee53\\U0001ee55\\U0001ee56\\U0001ee58\\U0001ee5a\\U0001ee5c\\U0001ee5e\\U0001ee60\\U0001ee63\\U0001ee65\\U0001ee66\\U0001ee6b\\U0001ee73\\U0001ee78\\U0001ee7d\\U0001ee7f\\U0001ee8a\\U0001ee9c-\\U0001eea0\\U0001eea4\\U0001eeaa\\U0001eebc-\\U0001eeef\\U0001eef2-\\U0001efff\\U0001f02c-\\U0001f02f\\U0001f094-\\U0001f09f\\U0001f0af\\U0001f0b0\\U0001f0c0\\U0001f0d0\\U0001f0f6-\\U0001f0ff\\U0001f10d-\\U0001f10f\\U0001f16d-\\U0001f16f\\U0001f1ad-\\U0001f1e5\\U0001f203-\\U0001f20f\\U0001f23c-\\U0001f23f\\U0001f249-\\U0001f24f\\U0001f252-\\U0001f25f\\U0001f266-\\U0001f2ff\\U0001f6d6-\\U0001f6df\\U0001f6ed-\\U0001f6ef\\U0001f6fb-\\U0001f6ff\\U0001f774-\\U0001f77f\\U0001f7d9-\\U0001f7df\\U0001f7ec-\\U0001f7ff\\U0001f80c-\\U0001f80f\\U0001f848-\\U0001f84f\\U0001f85a-\\U0001f85f\\U0001f888-\\U0001f88f\\U0001f8ae-\\U0001f8ff\\U0001f90c\\U0001f972\\U0001f977-\\U0001f979\\U0001f9a3\\U0001f9a4\\U0001f9ab-\\U0001f9ad\\U0001f9cb\\U0001f9cc\\U0001fa54-\\U0001fa5f\\U0001fa6e\\U0001fa6f\\U0001fa74-\\U0001fa77\\U0001fa7b-\\U0001fa7f\\U0001fa83-\\U0001fa8f\\U0001fa96-\\U0001ffff\\U0002a6d7-\\U0002a6ff\\U0002b735-\\U0002b73f\\U0002b81e\\U0002b81f\\U0002cea2-\\U0002ceaf\\U0002ebe1-\\U0002f7ff\\U0002fa1e-\\U000e00ff\\U000e01f0-\\U0010ffff]*[^ ])|(?:[^ \\+0-9_]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::association_format_type¶
Base type
string
Type constraint
(self in ['vlan-id', 'string', 'integer', 'vpn-id', 'icc-based'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::ccm_interval_type¶
Base type
string
Type constraint
(self in ['300hz', '10ms', '100ms', '1s', '10s', '60s', '600s'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::chassis_id_subtype¶
Base type
string
Type constraint
(self in ['system', 'local'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::domain_format_type¶
Base type
string
Type constraint
(self in ['none', 'dns-like', 'mac-address', 'string'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::id_permission_type¶
Base type
string
Type constraint
(self in ['none', 'chassis'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::lowest_alarm_priority_type¶
Base type
string
Type constraint
(self in ['all-def', 'mac-remote-error-xcon', 'remote-error-xcon', 'error-xcon', 'xcon', 'no-xcon'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::md_level_type¶
Base type
yang::types::uint8
Type constraint
((self >= 0) and (self <= 7))
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::md_levels_ordered_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:\\^(?:0|0 1|0 1 2|0 1 2 3|0 1 2 3 4|0 1 2 3 4 5|0 1 2 3 4 5 6|0 1 2 3 4 5 6 7)\\$)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::mep_direction_type¶
Base type
string
Type constraint
(self in ['down', 'up'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::mep_id_type¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 8191))
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type¶
Base type
string
Type constraint
(self in ['emergency', 'alert', 'critical', 'error', 'warning', 'notice', 'informational', 'debug'])
- typedef nokia_srlinux::types::srl_nokia_ethcfm_types::string_not_all_spaces¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[^\r\n]*\\S[^\r\n]*)|(?:))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_igmp_snooping::igmp_interval_type¶
Base type
yang::types::uint32
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_igmp_snooping::igmp_version¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 3))
- typedef nokia_srlinux::types::srl_nokia_interfaces_ip_dhcp_relay::hostv4¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv4_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::domain_name'))
- typedef nokia_srlinux::types::srl_nokia_interfaces_ip_dhcp_relay::hostv6¶
Base type
string
Type constraint
(yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::ipv6_address') or yang::validate_type(self,'nokia_srlinux::types::srl_nokia_common::domain_name'))
- typedef nokia_srlinux::types::srl_nokia_interfaces_lag::lacp_fallback_type¶
Base type
string
Type constraint
(self == 'static')
- typedef nokia_srlinux::types::srl_nokia_interfaces_lag::lag_type¶
Base type
string
Type constraint
(self in ['lacp', 'static'])
- typedef nokia_srlinux::types::srl_nokia_interfaces_lag::member_speed_type¶
Base type
string
Type constraint
(self in ['10M', '100M', '1G', '10G', '25G', '40G', '50G', '100G', '400G'])
- typedef nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_discovery_address_type¶
Base type
string
Type constraint
(self in ['IPv4', 'IPv6', 'IPv4v6'])
- typedef nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_id¶
Base type
yang::types::uint16
Type constraint
((self >= 1) and (self <= 4094))
- typedef nokia_srlinux::types::srl_nokia_isis::isis_admin_tag¶
Base type
yang::types::uint32
Type constraint
((self >= 1) and (self <= 4294967295))
- typedef nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type¶
Base type
string
Type constraint
(self in ['strict', 'loose', 'disable'])
- typedef nokia_srlinux::types::srl_nokia_isis::isis_auth_type¶
Base type
string
Type constraint
(self in ['cleartext', 'hmac-md5', 'hmac-sha-256'])
- typedef nokia_srlinux::types::srl_nokia_isis::isis_circuit_type¶
Base type
string
Type constraint
(self in ['point-to-point', 'broadcast'])
- typedef nokia_srlinux::types::srl_nokia_isis::isis_ecmp¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::types::srl_nokia_isis::isis_hello_padding_type¶
Base type
string
Type constraint
(self in ['strict', 'loose', 'adaptive', 'disable'])
- typedef nokia_srlinux::types::srl_nokia_isis::isis_level¶
Base type
string
Type constraint
(self in ['L1', 'L2', 'L1L2'])
- typedef nokia_srlinux::types::srl_nokia_isis::isis_level_number¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 2))
- typedef nokia_srlinux::types::srl_nokia_isis::isis_metric_style¶
Base type
string
Type constraint
(self in ['narrow', 'wide'])
- typedef nokia_srlinux::types::srl_nokia_isis::isis_net_id¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[0-9A-Fa-f]{2}(?:\\.[0-9A-Fa-f]{4}){3,9}\\.[0]{2})$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_isis::isis_wide_metric¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 16777215))
- typedef nokia_srlinux::types::srl_nokia_keychains::algorithm_type¶
Base type
string
Type constraint
(self in ['cleartext', 'md5', 'hmac-md5', 'hmac-sha-1', 'hmac-sha-256', 'aes-128-cmac', 'aes-256-cmac'])
- typedef nokia_srlinux::types::srl_nokia_keychains::keychain_type¶
Base type
string
Type constraint
(self in ['tcp-md5', 'isis', 'ospf', 'tcp-ao', 'vrrp', 'macsec'])
- typedef nokia_srlinux::types::srl_nokia_lacp::lacp_activity_type¶
Base type
string
Type constraint
(self in ['ACTIVE', 'PASSIVE'])
- typedef nokia_srlinux::types::srl_nokia_lacp::lacp_period_type¶
Base type
string
Type constraint
(self in ['FAST', 'SLOW'])
- typedef nokia_srlinux::types::srl_nokia_ldp::interface_trace_option_flags¶
Base type
string
Type constraint
(self in ['all', 'events-discovery', 'messages-hello', 'messages-hello-detail'])
- typedef nokia_srlinux::types::srl_nokia_ldp::session_trace_option_flags¶
Base type
string
Type constraint
(self in ['all', 'events-all', 'events-session', 'events-binding', 'messages-all', 'messages-all-detail', 'messages-initialization', 'messages-initialization-detail', 'messages-keepalive', 'messages-label', 'messages-label-detail', 'messages-hello', 'messages-hello-detail'])
- typedef nokia_srlinux::types::srl_nokia_lldp::base_interface_ref¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_lldp_types::management_address_type¶
Base type
string
Type constraint
(self in ['IPv4', 'IPv6'])
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::directory_name_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:/(?:[^\r\n])*)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type¶
Base type
string
Type constraint
(self in ['all', 'audit', 'auth', 'authpriv', 'console', 'cron', 'daemon', 'ftp', 'kern', 'lpr', 'mail', 'news', 'ntp', 'syslog', 'user', 'uucp', 'local0', 'local1', 'local2', 'local3', 'local4', 'local5', 'local6', 'local7'])
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type_subset¶
Base type
nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type
Type constraint
(self in ['auth', 'authpriv', 'cron', 'daemon', 'ftp', 'kern', 'lpr', 'mail', 'news', 'ntp', 'syslog', 'user', 'uucp', 'local0', 'local1', 'local2', 'local3', 'local4', 'local5', 'local6', 'local7'])
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::restricted_file_name_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[^\\./][^/]*)|(?:\\.[^\\./]+)|(?:\\.\\.[^/])+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::subsystem_name_type¶
Base type
string
Type constraint
(self in ['aaa', 'accounting', 'acl', 'app', 'arpnd', 'bfd', 'bgp', 'bridgetable', 'chassis', 'debug', 'dhcp', 'ethcfm', 'evpn', 'fib', 'gnmi', 'gnsi', 'gribi', 'grpc', 'igmp', 'isis', 'json', 'lag', 'ldp', 'license', 'linux', 'lldp', 'log', 'mgmt', 'mirror', 'mld', 'mpls', 'netinst', 'ospf', 'p4rt', 'pcc', 'pim', 'platform', 'policy', 'qos', 'sdk', 'sflow', 'staticroute', 'sync', 'twamp', 'vxlan', 'xdp'])
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::transport_type¶
Base type
string
Type constraint
(self in ['udp', 'tcp'])
- typedef nokia_srlinux::types::srl_nokia_logging::logging_top::usage_capacity_size_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[1-9][0-9]{0,15}(?:K|M|G){0,1})$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_macsec::confidentiality_offset¶
Base type
string
Type constraint
(self in ['0-bytes', '30-bytes', '50-bytes'])
- typedef nokia_srlinux::types::srl_nokia_macsec::macsec_cipher_suite¶
Base type
string
Type constraint
(self in ['gcm-aes-128', 'gcm-aes-256', 'gcm-aes-xpn-128', 'gcm-aes-xpn-256'])
- typedef nokia_srlinux::types::srl_nokia_macsec::protocols¶
Base type
string
Type constraint
(self in ['lacp', 'lldp', 'cdp', 'eapol-start', 'efm-oam', 'eth-cfm', 'ptp', 'ubfd'])
- typedef nokia_srlinux::types::srl_nokia_macsec::tag_mode¶
Base type
string
Type constraint
(self in ['no-tag', 'single-tag', 'double-tag'])
- typedef nokia_srlinux::types::srl_nokia_mld_snooping::mld_interval_type¶
Base type
yang::types::uint32
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_mld_snooping::mld_version¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 2))
- typedef nokia_srlinux::types::srl_nokia_mvpn_l3::auto_discovery_type¶
Base type
string
Type constraint
(self == 'bgp')
- typedef nokia_srlinux::types::srl_nokia_mvpn_l3::c_multicast_route_type¶
Base type
string
Type constraint
(self == 'bgp')
- typedef nokia_srlinux::types::srl_nokia_network_instance::network_instance_subintf_name¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 255))
- typedef nokia_srlinux::types::srl_nokia_network_instance::network_instance_vxlan_if_ref¶
Base type
string
Type constraint
(((std::length(self) >= 8) and (std::length(self) <= 17)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:vxlan(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])\\.(?:0|[1-9](?:\\d){0,8})))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::bin_metric_type¶
Base type
string
Type constraint
(self in ['fd', 'fdr', 'ifdv'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::data_tlv_size¶
Base type
yang::types::uint32
Type constraint
(((self >= 3) and (self <= 9502)) or (self == 0))
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::delay_direction_type¶
Base type
string
Type constraint
(self in ['forward', 'backward', 'round-trip'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type¶
Base type
string
Type constraint
(self in ['forward', 'backward', 'aggregate'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_type¶
Base type
string
Type constraint
(self in ['forward', 'backward'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_boundary_type¶
Base type
string
Type constraint
(self in ['clock-aligned', 'test-relative'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_clock_offset¶
Base type
yang::types::uint32
Type constraint
((self >= 0) and (self <= 86399))
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_duration_type¶
Base type
string
Type constraint
(self in ['1-minute', '5-minutes', '15-minutes', '1-hour', '1-day'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_stored¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 96))
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_interval¶
Base type
string
Type constraint
(self in ['50ms', '100ms', '200ms', '300ms', '400ms', '500ms', '600ms', '700ms', '800ms', '900ms', '1s', '10s'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_interval_slm¶
Base type
string
Type constraint
(self in ['50ms', '100ms', '200ms', '300ms', '400ms', '500ms', '600ms', '700ms', '800ms', '900ms', '1s'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_session_type¶
Base type
string
Type constraint
(self in ['proactive', 'on-demand'])
- typedef nokia_srlinux::types::srl_nokia_oam_pm_types::timestamp_format¶
Base type
string
Type constraint
(self in ['ntp', 'ptp'])
- typedef nokia_srlinux::types::srl_nokia_ospf_types::interface_type¶
Base type
string
Type constraint
(self in ['broadcast', 'point-to-point'])
- typedef nokia_srlinux::types::srl_nokia_ospf_types::lsa_filter_out¶
Base type
string
Type constraint
(self in ['none', 'all', 'except-own-rtrlsa', 'except-own-rtrlsa-and-defaults'])
- typedef nokia_srlinux::types::srl_nokia_ospf_types::ospf_area_identifier¶
Base type
nokia_srlinux::types::ietf_yang_types::dotted_quad
Type constraint
(std::validate_type('pydantic.constr',self,{'regex': '^(?:[\\.0-9]*)$(?!\\n\\Z)'}) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])(?:%[0-9A-Za-zª²³µ¹º¼-¾Ã\x80-Ã\x96Ã\x98-öø-\\u02c1\\u02c6-\\u02d1\\u02e0-\\u02e4\\u02ec\\u02ee\\u0370-\\u0374\\u0376\\u0377\\u037a-\\u037d\\u037f\\u0386\\u0388-\\u038a\\u038c\\u038e-\\u03a1\\u03a3-\\u03f5\\u03f7-\\u0481\\u048a-\\u052f\\u0531-\\u0556\\u0559\\u0560-\\u0588\\u05d0-\\u05ea\\u05ef-\\u05f2\\u0620-\\u064a\\u0660-\\u0669\\u066e\\u066f\\u0671-\\u06d3\\u06d5\\u06e5\\u06e6\\u06ee-\\u06fc\\u06ff\\u0710\\u0712-\\u072f\\u074d-\\u07a5\\u07b1\\u07c0-\\u07ea\\u07f4\\u07f5\\u07fa\\u0800-\\u0815\\u081a\\u0824\\u0828\\u0840-\\u0858\\u0860-\\u086a\\u08a0-\\u08b4\\u08b6-\\u08bd\\u0904-\\u0939\\u093d\\u0950\\u0958-\\u0961\\u0966-\\u096f\\u0971-\\u0980\\u0985-\\u098c\\u098f\\u0990\\u0993-\\u09a8\\u09aa-\\u09b0\\u09b2\\u09b6-\\u09b9\\u09bd\\u09ce\\u09dc\\u09dd\\u09df-\\u09e1\\u09e6-\\u09f1\\u09f4-\\u09f9\\u09fc\\u0a05-\\u0a0a\\u0a0f\\u0a10\\u0a13-\\u0a28\\u0a2a-\\u0a30\\u0a32\\u0a33\\u0a35\\u0a36\\u0a38\\u0a39\\u0a59-\\u0a5c\\u0a5e\\u0a66-\\u0a6f\\u0a72-\\u0a74\\u0a85-\\u0a8d\\u0a8f-\\u0a91\\u0a93-\\u0aa8\\u0aaa-\\u0ab0\\u0ab2\\u0ab3\\u0ab5-\\u0ab9\\u0abd\\u0ad0\\u0ae0\\u0ae1\\u0ae6-\\u0aef\\u0af9\\u0b05-\\u0b0c\\u0b0f\\u0b10\\u0b13-\\u0b28\\u0b2a-\\u0b30\\u0b32\\u0b33\\u0b35-\\u0b39\\u0b3d\\u0b5c\\u0b5d\\u0b5f-\\u0b61\\u0b66-\\u0b6f\\u0b71-\\u0b77\\u0b83\\u0b85-\\u0b8a\\u0b8e-\\u0b90\\u0b92-\\u0b95\\u0b99\\u0b9a\\u0b9c\\u0b9e\\u0b9f\\u0ba3\\u0ba4\\u0ba8-\\u0baa\\u0bae-\\u0bb9\\u0bd0\\u0be6-\\u0bf2\\u0c05-\\u0c0c\\u0c0e-\\u0c10\\u0c12-\\u0c28\\u0c2a-\\u0c39\\u0c3d\\u0c58-\\u0c5a\\u0c60\\u0c61\\u0c66-\\u0c6f\\u0c78-\\u0c7e\\u0c80\\u0c85-\\u0c8c\\u0c8e-\\u0c90\\u0c92-\\u0ca8\\u0caa-\\u0cb3\\u0cb5-\\u0cb9\\u0cbd\\u0cde\\u0ce0\\u0ce1\\u0ce6-\\u0cef\\u0cf1\\u0cf2\\u0d05-\\u0d0c\\u0d0e-\\u0d10\\u0d12-\\u0d3a\\u0d3d\\u0d4e\\u0d54-\\u0d56\\u0d58-\\u0d61\\u0d66-\\u0d78\\u0d7a-\\u0d7f\\u0d85-\\u0d96\\u0d9a-\\u0db1\\u0db3-\\u0dbb\\u0dbd\\u0dc0-\\u0dc6\\u0de6-\\u0def\\u0e01-\\u0e30\\u0e32\\u0e33\\u0e40-\\u0e46\\u0e50-\\u0e59\\u0e81\\u0e82\\u0e84\\u0e86-\\u0e8a\\u0e8c-\\u0ea3\\u0ea5\\u0ea7-\\u0eb0\\u0eb2\\u0eb3\\u0ebd\\u0ec0-\\u0ec4\\u0ec6\\u0ed0-\\u0ed9\\u0edc-\\u0edf\\u0f00\\u0f20-\\u0f33\\u0f40-\\u0f47\\u0f49-\\u0f6c\\u0f88-\\u0f8c\\u1000-\\u102a\\u103f-\\u1049\\u1050-\\u1055\\u105a-\\u105d\\u1061\\u1065\\u1066\\u106e-\\u1070\\u1075-\\u1081\\u108e\\u1090-\\u1099\\u10a0-\\u10c5\\u10c7\\u10cd\\u10d0-\\u10fa\\u10fc-\\u1248\\u124a-\\u124d\\u1250-\\u1256\\u1258\\u125a-\\u125d\\u1260-\\u1288\\u128a-\\u128d\\u1290-\\u12b0\\u12b2-\\u12b5\\u12b8-\\u12be\\u12c0\\u12c2-\\u12c5\\u12c8-\\u12d6\\u12d8-\\u1310\\u1312-\\u1315\\u1318-\\u135a\\u1369-\\u137c\\u1380-\\u138f\\u13a0-\\u13f5\\u13f8-\\u13fd\\u1401-\\u166c\\u166f-\\u167f\\u1681-\\u169a\\u16a0-\\u16ea\\u16ee-\\u16f8\\u1700-\\u170c\\u170e-\\u1711\\u1720-\\u1731\\u1740-\\u1751\\u1760-\\u176c\\u176e-\\u1770\\u1780-\\u17b3\\u17d7\\u17dc\\u17e0-\\u17e9\\u17f0-\\u17f9\\u1810-\\u1819\\u1820-\\u1878\\u1880-\\u1884\\u1887-\\u18a8\\u18aa\\u18b0-\\u18f5\\u1900-\\u191e\\u1946-\\u196d\\u1970-\\u1974\\u1980-\\u19ab\\u19b0-\\u19c9\\u19d0-\\u19da\\u1a00-\\u1a16\\u1a20-\\u1a54\\u1a80-\\u1a89\\u1a90-\\u1a99\\u1aa7\\u1b05-\\u1b33\\u1b45-\\u1b4b\\u1b50-\\u1b59\\u1b83-\\u1ba0\\u1bae-\\u1be5\\u1c00-\\u1c23\\u1c40-\\u1c49\\u1c4d-\\u1c7d\\u1c80-\\u1c88\\u1c90-\\u1cba\\u1cbd-\\u1cbf\\u1ce9-\\u1cec\\u1cee-\\u1cf3\\u1cf5\\u1cf6\\u1cfa\\u1d00-\\u1dbf\\u1e00-\\u1f15\\u1f18-\\u1f1d\\u1f20-\\u1f45\\u1f48-\\u1f4d\\u1f50-\\u1f57\\u1f59\\u1f5b\\u1f5d\\u1f5f-\\u1f7d\\u1f80-\\u1fb4\\u1fb6-\\u1fbc\\u1fbe\\u1fc2-\\u1fc4\\u1fc6-\\u1fcc\\u1fd0-\\u1fd3\\u1fd6-\\u1fdb\\u1fe0-\\u1fec\\u1ff2-\\u1ff4\\u1ff6-\\u1ffc\\u2070\\u2071\\u2074-\\u2079\\u207f-\\u2089\\u2090-\\u209c\\u2102\\u2107\\u210a-\\u2113\\u2115\\u2119-\\u211d\\u2124\\u2126\\u2128\\u212a-\\u212d\\u212f-\\u2139\\u213c-\\u213f\\u2145-\\u2149\\u214e\\u2150-\\u2184\\u2185-\\u2189\\u2460-\\u249b\\u24ea-\\u24ff\\u2776-\\u2793\\u2c00-\\u2c2e\\u2c30-\\u2c5e\\u2c60-\\u2ce4\\u2ceb-\\u2cee\\u2cf2\\u2cf3\\u2cfd\\u2d00-\\u2d25\\u2d27\\u2d2d\\u2d30-\\u2d67\\u2d6f\\u2d80-\\u2d96\\u2da0-\\u2da6\\u2da8-\\u2dae\\u2db0-\\u2db6\\u2db8-\\u2dbe\\u2dc0-\\u2dc6\\u2dc8-\\u2dce\\u2dd0-\\u2dd6\\u2dd8-\\u2dde\\u2e2f\\u3005-\\u3007\\u3021-\\u3029\\u3031-\\u3035\\u3038-\\u303c\\u3041-\\u3096\\u309d-\\u309f\\u30a1-\\u30fa\\u30fc-\\u30ff\\u3105-\\u312f\\u3131-\\u318e\\u3192-\\u3195\\u31a0-\\u31ba\\u31f0-\\u31ff\\u3220-\\u3229\\u3248-\\u324f\\u3251-\\u325f\\u3280-\\u3289\\u32b1-\\u32bf\\u3400-\\u4db5\\u4e00-\\u9fef\\ua000-\\ua48c\\ua4d0-\\ua4fd\\ua500-\\ua60c\\ua610-\\ua62b\\ua640-\\ua66e\\ua67f-\\ua69d\\ua6a0-\\ua6ef\\ua717-\\ua71f\\ua722-\\ua788\\ua78b-\\ua7bf\\ua7c2-\\ua7c6\\ua7f7-\\ua801\\ua803-\\ua805\\ua807-\\ua80a\\ua80c-\\ua822\\ua830-\\ua835\\ua840-\\ua873\\ua882-\\ua8b3\\ua8d0-\\ua8d9\\ua8f2-\\ua8f7\\ua8fb\\ua8fd\\ua8fe\\ua900-\\ua925\\ua930-\\ua946\\ua960-\\ua97c\\ua984-\\ua9b2\\ua9cf-\\ua9d9\\ua9e0-\\ua9e4\\ua9e6-\\ua9fe\\uaa00-\\uaa28\\uaa40-\\uaa42\\uaa44-\\uaa4b\\uaa50-\\uaa59\\uaa60-\\uaa76\\uaa7a\\uaa7e-\\uaaaf\\uaab1\\uaab5\\uaab6\\uaab9-\\uaabd\\uaac0\\uaac2\\uaadb-\\uaadd\\uaae0-\\uaaea\\uaaf2-\\uaaf4\\uab01-\\uab06\\uab09-\\uab0e\\uab11-\\uab16\\uab20-\\uab26\\uab28-\\uab2e\\uab30-\\uab5a\\uab5c-\\uab67\\uab70-\\uabe2\\uabf0-\\uabf9\\uac00-\\ud7a3\\ud7b0-\\ud7c6\\ud7cb-\\ud7fb\\uf900-\\ufa6d\\ufa70-\\ufad9\\ufb00-\\ufb06\\ufb13-\\ufb17\\ufb1d\\ufb1f-\\ufb28\\ufb2a-\\ufb36\\ufb38-\\ufb3c\\ufb3e\\ufb40\\ufb41\\ufb43\\ufb44\\ufb46-\\ufbb1\\ufbd3-\\ufd3d\\ufd50-\\ufd8f\\ufd92-\\ufdc7\\ufdf0-\\ufdfb\\ufe70-\\ufe74\\ufe76-\\ufefc\\uff10-\\uff19\\uff21-\\uff3a\\uff41-\\uff5a\\uff66-\\uffbe\\uffc2-\\uffc7\\uffca-\\uffcf\\uffd2-\\uffd7\\uffda-\\uffdc\\U00010000-\\U0001000b\\U0001000d-\\U00010026\\U00010028-\\U0001003a\\U0001003c\\U0001003d\\U0001003f-\\U0001004d\\U00010050-\\U0001005d\\U00010080-\\U000100fa\\U00010107-\\U00010133\\U00010140-\\U00010178\\U0001018a\\U0001018b\\U00010280-\\U0001029c\\U000102a0-\\U000102d0\\U000102e1-\\U000102fb\\U00010300-\\U00010323\\U0001032d-\\U00010349\\U0001034a\\U00010350-\\U00010375\\U00010380-\\U0001039d\\U000103a0-\\U000103c3\\U000103c8-\\U000103cf\\U000103d1-\\U000103d5\\U00010400-\\U0001049d\\U000104a0-\\U000104a9\\U000104b0-\\U000104d3\\U000104d8-\\U000104fb\\U00010500-\\U00010527\\U00010530-\\U00010563\\U00010600-\\U00010736\\U00010740-\\U00010755\\U00010760-\\U00010767\\U00010800-\\U00010805\\U00010808\\U0001080a-\\U00010835\\U00010837\\U00010838\\U0001083c\\U0001083f-\\U00010855\\U00010858-\\U00010876\\U00010879-\\U0001089e\\U000108a7-\\U000108af\\U000108e0-\\U000108f2\\U000108f4\\U000108f5\\U000108fb-\\U00010915\\U00010916-\\U0001091b\\U00010920-\\U00010939\\U00010980-\\U000109b7\\U000109bc-\\U000109bf\\U000109c0-\\U000109cf\\U000109d2-\\U00010a00\\U00010a10-\\U00010a13\\U00010a15-\\U00010a17\\U00010a19-\\U00010a35\\U00010a40-\\U00010a48\\U00010a60-\\U00010a7e\\U00010a80-\\U00010a9f\\U00010ac0-\\U00010ac7\\U00010ac9-\\U00010ae4\\U00010aeb-\\U00010aef\\U00010b00-\\U00010b35\\U00010b40-\\U00010b55\\U00010b58-\\U00010b72\\U00010b78-\\U00010b91\\U00010ba9-\\U00010baf\\U00010c00-\\U00010c48\\U00010c80-\\U00010cb2\\U00010cc0-\\U00010cf2\\U00010cfa-\\U00010d23\\U00010d30-\\U00010d39\\U00010e60-\\U00010e7e\\U00010f00-\\U00010f27\\U00010f30-\\U00010f45\\U00010f51-\\U00010f54\\U00010fe0-\\U00010ff6\\U00011003-\\U00011037\\U00011052-\\U0001106f\\U00011083-\\U000110af\\U000110d0-\\U000110e8\\U000110f0-\\U000110f9\\U00011103-\\U00011126\\U00011136-\\U0001113f\\U00011144\\U00011150-\\U00011172\\U00011176\\U00011183-\\U000111b2\\U000111c1-\\U000111c4\\U000111d0-\\U000111da\\U000111dc\\U000111e1-\\U000111f4\\U00011200-\\U00011211\\U00011213-\\U0001122b\\U00011280-\\U00011286\\U00011288\\U0001128a-\\U0001128d\\U0001128f-\\U0001129d\\U0001129f-\\U000112a8\\U000112b0-\\U000112de\\U000112f0-\\U000112f9\\U00011305-\\U0001130c\\U0001130f\\U00011310\\U00011313-\\U00011328\\U0001132a-\\U00011330\\U00011332\\U00011333\\U00011335-\\U00011339\\U0001133d\\U00011350\\U0001135d-\\U00011361\\U00011400-\\U00011434\\U00011447-\\U0001144a\\U00011450-\\U00011459\\U0001145f\\U00011480-\\U000114af\\U000114c4\\U000114c5\\U000114c7\\U000114d0-\\U000114d9\\U00011580-\\U000115ae\\U000115d8-\\U000115db\\U00011600-\\U0001162f\\U00011644\\U00011650-\\U00011659\\U00011680-\\U000116aa\\U000116b8\\U000116c0-\\U000116c9\\U00011700-\\U0001171a\\U00011730-\\U0001173b\\U00011800-\\U0001182b\\U000118a0-\\U000118f2\\U000118ff\\U000119a0-\\U000119a7\\U000119aa-\\U000119d0\\U000119e1\\U000119e3\\U00011a00\\U00011a0b-\\U00011a32\\U00011a3a\\U00011a50\\U00011a5c-\\U00011a89\\U00011a9d\\U00011ac0-\\U00011af8\\U00011c00-\\U00011c08\\U00011c0a-\\U00011c2e\\U00011c40\\U00011c50-\\U00011c6c\\U00011c72-\\U00011c8f\\U00011d00-\\U00011d06\\U00011d08\\U00011d09\\U00011d0b-\\U00011d30\\U00011d46\\U00011d50-\\U00011d59\\U00011d60-\\U00011d65\\U00011d67\\U00011d68\\U00011d6a-\\U00011d89\\U00011d98\\U00011da0-\\U00011da9\\U00011ee0-\\U00011ef2\\U00011fc0-\\U00011fd4\\U00012000-\\U00012399\\U00012400-\\U0001246e\\U00012480-\\U00012543\\U00013000-\\U0001342e\\U00014400-\\U00014646\\U00016800-\\U00016a38\\U00016a40-\\U00016a5e\\U00016a60-\\U00016a69\\U00016ad0-\\U00016aed\\U00016b00-\\U00016b2f\\U00016b40-\\U00016b43\\U00016b50-\\U00016b59\\U00016b5b-\\U00016b61\\U00016b63-\\U00016b77\\U00016b7d-\\U00016b8f\\U00016e40-\\U00016e96\\U00016f00-\\U00016f4a\\U00016f50\\U00016f93-\\U00016f9f\\U00016fe0\\U00016fe1\\U00016fe3\\U00017000-\\U000187f7\\U00018800-\\U00018af2\\U0001b000-\\U0001b11e\\U0001b150-\\U0001b152\\U0001b164-\\U0001b167\\U0001b170-\\U0001b2fb\\U0001bc00-\\U0001bc6a\\U0001bc70-\\U0001bc7c\\U0001bc80-\\U0001bc88\\U0001bc90-\\U0001bc99\\U0001d2e0-\\U0001d2f3\\U0001d360-\\U0001d378\\U0001d400-\\U0001d454\\U0001d456-\\U0001d49c\\U0001d49e\\U0001d49f\\U0001d4a2\\U0001d4a5\\U0001d4a6\\U0001d4a9-\\U0001d4ac\\U0001d4ae-\\U0001d4b9\\U0001d4bb\\U0001d4bd-\\U0001d4c3\\U0001d4c5-\\U0001d505\\U0001d507-\\U0001d50a\\U0001d50d-\\U0001d514\\U0001d516-\\U0001d51c\\U0001d51e-\\U0001d539\\U0001d53b-\\U0001d53e\\U0001d540-\\U0001d544\\U0001d546\\U0001d54a-\\U0001d550\\U0001d552-\\U0001d6a5\\U0001d6a8-\\U0001d6c0\\U0001d6c2-\\U0001d6da\\U0001d6dc-\\U0001d6fa\\U0001d6fc-\\U0001d714\\U0001d716-\\U0001d734\\U0001d736-\\U0001d74e\\U0001d750-\\U0001d76e\\U0001d770-\\U0001d788\\U0001d78a-\\U0001d7a8\\U0001d7aa-\\U0001d7c2\\U0001d7c4-\\U0001d7cb\\U0001d7ce-\\U0001d7ff\\U0001e100-\\U0001e12c\\U0001e137-\\U0001e13d\\U0001e140-\\U0001e149\\U0001e14e\\U0001e2c0-\\U0001e2eb\\U0001e2f0-\\U0001e2f9\\U0001e800-\\U0001e8c4\\U0001e8c7-\\U0001e8cf\\U0001e900-\\U0001e943\\U0001e94b\\U0001e950-\\U0001e959\\U0001ec71-\\U0001ecab\\U0001ecad-\\U0001ecaf\\U0001ecb1-\\U0001ecb4\\U0001ed01-\\U0001ed2d\\U0001ed2f-\\U0001ed3d\\U0001ee00-\\U0001ee03\\U0001ee05-\\U0001ee1f\\U0001ee21\\U0001ee22\\U0001ee24\\U0001ee27\\U0001ee29-\\U0001ee32\\U0001ee34-\\U0001ee37\\U0001ee39\\U0001ee3b\\U0001ee42\\U0001ee47\\U0001ee49\\U0001ee4b\\U0001ee4d-\\U0001ee4f\\U0001ee51\\U0001ee52\\U0001ee54\\U0001ee57\\U0001ee59\\U0001ee5b\\U0001ee5d\\U0001ee5f\\U0001ee61\\U0001ee62\\U0001ee64\\U0001ee67-\\U0001ee6a\\U0001ee6c-\\U0001ee72\\U0001ee74-\\U0001ee77\\U0001ee79-\\U0001ee7c\\U0001ee7e\\U0001ee80-\\U0001ee89\\U0001ee8b-\\U0001ee9b\\U0001eea1-\\U0001eea3\\U0001eea5-\\U0001eea9\\U0001eeab-\\U0001eebb\\U0001f100-\\U0001f10c\\U00020000-\\U0002a6d6\\U0002a700-\\U0002b734\\U0002b740-\\U0002b81d\\U0002b820-\\U0002cea1\\U0002ceb0-\\U0002ebe0\\U0002f800-\\U0002fa1d]+)?)$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_ospf_types::ospf_ecmp¶
Base type
yang::types::uint8
Type constraint
((self >= 1) and (self <= 64))
- typedef nokia_srlinux::types::srl_nokia_ospf_types::ospf_metric¶
Base type
yang::types::uint16
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::ethertype¶
Base type
string
Type constraint
(std::validate_type('pydantic.constr',self,{'regex': '^(?:0x[0-9A-Fa-f]{4})$(?!\\n\\Z)'}) or (self in ['ipv4', 'arp', 'ipv6', 'flow-control', 'lacp', 'mpls-unicast', 'mpls-multicast', 'pppoe-discovery', 'pppoe-session', '8021x-authentication', 'lldp', 'macsec', 'pbb', 'ptp', 'eth-oam', 'fcoe', 'fcoe-initialization', 'roce']))
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::icmp6_type¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['dest-unreachable', 'packet-too-big', 'time-exceeded', 'param-problem', 'echo-request', 'echo-reply', 'mld-query', 'mld-report', 'mld-done', 'router-solicit', 'router-advertise', 'neighbor-solicit', 'neighbor-advertise', 'redirect', 'router-renumber', 'node-info-query', 'node-info-response', 'mld-v2', 'mcast-rtr-adv', 'mcast-rtr-solicit', 'mcast-rtr-term']))
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::icmp_type¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['echo-reply', 'dest-unreachable', 'source-quench', 'redirect', 'echo', 'router-advertise', 'router-solicit', 'time-exceeded', 'param-problem', 'timestamp', 'timestamp-reply']))
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::ip_protocol_type¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint8')) and (int(self) >= 0)) and (int(self) <= 255)) or (self in ['ipv6-hop', 'icmp', 'igmp', 'ggp', 'ipv4', 'st', 'tcp', 'egp', 'igp', 'udp', 'ipv6', 'idrp', 'rsvp', 'gre', 'esp', 'ah', 'icmp6', 'no-next-hdr', 'ipv6-dest-opts', 'eigrp', 'ospf', 'pim', 'vrrp', 'l2tp', 'sctp', 'mpls-in-ip', 'rohc']))
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::l4_port_type¶
Base type
string
Type constraint
((((yang::is_int(self) and yang::validate_type(int(self),'yang::types::uint16')) and (int(self) >= 0)) and (int(self) <= 65535)) or (self in ['acap', 'afp-tcp', 'arns', 'asf-rmcp', 'ashare', 'atalk-rm', 'aurp', 'auth', 'bfd', 'bfd-echo', 'bftp', 'bgmp', 'bgp', 'bootpc', 'bootps', 'ccso-ns', 'chargen', 'cisco-tdp', 'citadel', 'clearcase', 'commerce', 'courier', 'daytime', 'dhcpv6-client', 'dhcpv6-server', 'dhcp-failover', 'dicom', 'discard', 'dnsix', 'domain', 'dsp', 'echo', 'epp', 'esro', 'exec', 'finger', 'ftp', 'ftp-data', 'ftps', 'ftps-data', 'godi', 'gopher', 'gtp-c', 'gtp-prime', 'gtp-u', 'ha-cluster', 'hostname', 'hp-alarm-mgr', 'http', 'http-alt', 'http-mgmt', 'http-rpc', 'https', 'ieee-mms-ssl', 'imap', 'imap3', 'imaps', 'ipp', 'ipsec', 'ipx', 'irc', 'iris-beep', 'isakmp', 'isakmp-nat', 'iscsi', 'iso-tsap', 'kerberos', 'kerberos-adm', 'klogin', 'kpasswd', 'kshell', 'l2tp', 'ldap', 'ldaps', 'ldp', 'lmp', 'login', 'lpd', 'lsp-ping', 'mac-server-adm', 'matip-a', 'matip-b', 'micro-bfd', 'microsoft-ds', 'mobile-ip', 'monitor', 'mpp', 'mssql-m', 'mssql-s', 'msdp', 'ms-exchange', 'msp', 'multihop-bfd', 'nas', 'ncp', 'netrjs-1', 'netrjs-2', 'netrjs-3', 'netrjs-4', 'netbios-data', 'netbios-ns', 'netbios-ss', 'netnews', 'netwall', 'new-rwho', 'nfs', 'nntp', 'nntps', 'ntp', 'odmr', 'olsr', 'openvpn', 'pim-auto-rp', 'pkix-timestamp', 'pop2', 'pop3', 'pop3s', 'pptp', 'ptp-event', 'ptp-general', 'print-srv', 'qmtp', 'qotd', 'radius', 'radius-acct', 'remote-mail', 'remotefs', 'remotecmd', 'rip', 'rje', 'rlp', 'rlzdb', 'rmc', 'rmonitor', 'rpc2portmap', 'rsync', 'rtelnet', 'rtsp', 'sgmp', 'silc', 'smux', 'sna-gw', 'snmp', 'snmp-trap', 'snpp', 'smtp', 'sql-svcs', 'sql', 'ssh', 'submission', 'sunrpc', 'svcloc', 'syslog', 'systat', 'tacacs', 'talk', 'tcpmux', 'tcpnethaspsrv', 'tftp', 'time', 'timed', 'ups', 'xdmcp', 'xns-ch', 'xns-mail', 'xns-time', 'z3950']))
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::operator¶
Base type
string
Type constraint
(self in ['le', 'ge', 'eq'])
- typedef nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type¶
Base type
yang::types::uint16
Type constraint
((self >= 0) and (self <= 4095))
- typedef nokia_srlinux::types::srl_nokia_policy_types::as_path_regexp¶
Base type
string
Type constraint
((std::length(self) >= 1) and (std::length(self) <= 65535))
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_regexp_type¶
Base type
string
Type constraint
((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:[^\r\n]*:[^\r\n]*)$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:[^\r\n]*:[^\r\n]*)$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:ext:[^\r\n]*:[^\r\n]*)$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:bgp\\-tunnel\\-encap:[^\r\n]*)$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:[a-z]+:[0-9]+:[0-9]+)$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_ext_community_type¶
Base type
string
Type constraint
((((((std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:target:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\\.){3}(?:[0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:origin:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})) or std::validate_type('pydantic.constr',self,{'regex': '^(?:color:[01]{2}:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'}))
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_family_type¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_large_community_regexp_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[$\\(-\\-\\.0-9\\?\\[\\\\\\]\\^\\{\\|\\}]+:[$\\(-\\-\\.0-9\\?\\[\\\\\\]\\^\\{\\|\\}]+:[$\\(-\\-\\.0-9\\?\\[\\\\\\]\\^\\{\\|\\}]+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_large_community_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]):(?:429496729[0-5]|42949672[0-8][0-9]|4294967[01][0-9]{2}|429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|4294[0-8][0-9]{5}|429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|[1-3][0-9]{9}|[1-9][0-9]{1,8}|[0-9]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_regexp_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:[$\\(-\\-\\.0-9\\?\\[\\\\\\]\\^\\{\\|\\}]+:[$\\(-\\-\\.0-9\\?\\[\\\\\\]\\^\\{\\|\\}]+)$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_type¶
Base type
string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]):(?:6553[0-5]|655[0-2][0-9]|654[0-9]{2}|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{1,3}|[0-9]))$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_policy_types::bgp_std_community_well_known_type¶
Base type
string
Type constraint
(self == self)
- typedef nokia_srlinux::types::srl_nokia_policy_types::comparison_operator_type¶
Base type
string
Type constraint
(self in ['eq', 'ge', 'le'])
- typedef nokia_srlinux::types::srl_nokia_policy_types::policy_result_type¶
Base type
string
Type constraint
(self in ['accept', 'reject'])
- typedef nokia_srlinux::types::srl_nokia_snmp::auth_protocol¶
Base type
string
Type constraint
(self in ['hmac-md5-96', 'hmac-sha1-96', 'hmac-sha2-224', 'hmac-sha2-256', 'hmac-sha2-384', 'hmac-sha2-512'])
- typedef nokia_srlinux::types::srl_nokia_snmp::engine_id¶
Base type
nokia_srlinux::types::srl_nokia_common::hex_string
Type constraint
std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:[0-9A-Fa-f]){2}(?::(?:[0-9A-Fa-f]){2}){4,31})$(?!\\n\\Z)'})
- typedef nokia_srlinux::types::srl_nokia_snmp::priv_protocol¶
Base type
string
Type constraint
(self in ['cbc-des', 'cfb128-aes-128', 'cfb128-aes-192', 'cfb128-aes-256'])
- typedef nokia_srlinux::types::srl_nokia_snmp::security_level¶
Base type
string
Type constraint
(self in ['no-auth-no-priv', 'auth-no-priv', 'auth-priv'])
- typedef nokia_srlinux::types::srl_nokia_sync_types::settable_ql_values¶
Base type
string
Type constraint
(self in ['unused', 'prs', 'stu', 'st2', 'tnc', 'st3e', 'st3', 'prc', 'ssua', 'ssub', 'sec', 'eec1', 'eec2'])
- typedef nokia_srlinux::types::srl_nokia_system_network_instance_bgp_evpn_ethernet_segments::df_algorithm_type¶
Base type
string
Type constraint
(self in ['default', 'preference', 'manual'])
- typedef nokia_srlinux::types::srl_nokia_system_network_instance_bgp_evpn_ethernet_segments::es_type¶
Base type
string
Type constraint
(self in ['none', 'virtual'])
- typedef nokia_srlinux::types::srl_nokia_system_network_instance_bgp_evpn_ethernet_segments::multi_homing_mode¶
Base type
string
Type constraint
(self in ['all-active', 'single-active'])
- typedef nokia_srlinux::types::srl_nokia_te_policies::dynamic_segment_path_computation_type¶
Base type
string
Type constraint
(self in ['local-cspf', 'pce'])
- typedef nokia_srlinux::types::srl_nokia_te_policies::te_policy_type¶
Base type
string
Type constraint
(self in ['sr-mpls-colored', 'sr-mpls-uncolored'])
- typedef nokia_srlinux::types::srl_nokia_timezone::tzdata_timezone¶
Base type
string
Type constraint
(self in ['Africa/Abidjan', 'Africa/Accra', 'Africa/Addis_Ababa', 'Africa/Algiers', 'Africa/Asmara', 'Africa/Bamako', 'Africa/Bangui', 'Africa/Banjul', 'Africa/Bissau', 'Africa/Blantyre', 'Africa/Brazzaville', 'Africa/Bujumbura', 'Africa/Cairo', 'Africa/Casablanca', 'Africa/Ceuta', 'Africa/Conakry', 'Africa/Dakar', 'Africa/Dar_es_Salaam', 'Africa/Djibouti', 'Africa/Douala', 'Africa/El_Aaiun', 'Africa/Freetown', 'Africa/Gaborone', 'Africa/Harare', 'Africa/Johannesburg', 'Africa/Juba', 'Africa/Kampala', 'Africa/Khartoum', 'Africa/Kigali', 'Africa/Kinshasa', 'Africa/Lagos', 'Africa/Libreville', 'Africa/Lome', 'Africa/Luanda', 'Africa/Lubumbashi', 'Africa/Lusaka', 'Africa/Malabo', 'Africa/Maputo', 'Africa/Maseru', 'Africa/Mbabane', 'Africa/Mogadishu', 'Africa/Monrovia', 'Africa/Nairobi', 'Africa/Ndjamena', 'Africa/Niamey', 'Africa/Nouakchott', 'Africa/Ouagadougou', 'Africa/Porto-Novo', 'Africa/Sao_Tome', 'Africa/Tripoli', 'Africa/Tunis', 'Africa/Windhoek', 'America/Adak', 'America/Anchorage', 'America/Anguilla', 'America/Antigua', 'America/Araguaina', 'America/Argentina/Buenos_Aires', 'America/Argentina/Catamarca', 'America/Argentina/Cordoba', 'America/Argentina/Jujuy', 'America/Argentina/La_Rioja', 'America/Argentina/Mendoza', 'America/Argentina/Rio_Gallegos', 'America/Argentina/Salta', 'America/Argentina/San_Juan', 'America/Argentina/San_Luis', 'America/Argentina/Tucuman', 'America/Argentina/Ushuaia', 'America/Aruba', 'America/Asuncion', 'America/Atikokan', 'America/Bahia', 'America/Bahia_Banderas', 'America/Barbados', 'America/Belem', 'America/Belize', 'America/Blanc-Sablon', 'America/Boa_Vista', 'America/Bogota', 'America/Boise', 'America/Cambridge_Bay', 'America/Campo_Grande', 'America/Cancun', 'America/Caracas', 'America/Cayenne', 'America/Cayman', 'America/Chicago', 'America/Chihuahua', 'America/Costa_Rica', 'America/Creston', 'America/Cuiaba', 'America/Curacao', 'America/Danmarkshavn', 'America/Dawson', 'America/Dawson_Creek', 'America/Denver', 'America/Detroit', 'America/Dominica', 'America/Edmonton', 'America/Eirunepe', 'America/El_Salvador', 'America/Fort_Nelson', 'America/Fortaleza', 'America/Glace_Bay', 'America/Godthab', 'America/Goose_Bay', 'America/Grand_Turk', 'America/Grenada', 'America/Guadeloupe', 'America/Guatemala', 'America/Guayaquil', 'America/Guyana', 'America/Halifax', 'America/Havana', 'America/Hermosillo', 'America/Indiana/Indianapolis', 'America/Indiana/Knox', 'America/Indiana/Marengo', 'America/Indiana/Petersburg', 'America/Indiana/Tell_City', 'America/Indiana/Vevay', 'America/Indiana/Vincennes', 'America/Indiana/Winamac', 'America/Inuvik', 'America/Iqaluit', 'America/Jamaica', 'America/Juneau', 'America/Kentucky/Louisville', 'America/Kentucky/Monticello', 'America/Kralendijk', 'America/La_Paz', 'America/Lima', 'America/Los_Angeles', 'America/Lower_Princes', 'America/Maceio', 'America/Managua', 'America/Manaus', 'America/Marigot', 'America/Martinique', 'America/Matamoros', 'America/Mazatlan', 'America/Menominee', 'America/Merida', 'America/Metlakatla', 'America/Mexico_City', 'America/Miquelon', 'America/Moncton', 'America/Monterrey', 'America/Montevideo', 'America/Montserrat', 'America/Nassau', 'America/New_York', 'America/Nipigon', 'America/Nome', 'America/Noronha', 'America/North_Dakota/Beulah', 'America/North_Dakota/Center', 'America/North_Dakota/New_Salem', 'America/Ojinaga', 'America/Panama', 'America/Pangnirtung', 'America/Paramaribo', 'America/Phoenix', 'America/Port-au-Prince', 'America/Port_of_Spain', 'America/Porto_Velho', 'America/Puerto_Rico', 'America/Punta_Arenas', 'America/Rainy_River', 'America/Rankin_Inlet', 'America/Recife', 'America/Regina', 'America/Resolute', 'America/Rio_Branco', 'America/Santarem', 'America/Santiago', 'America/Santo_Domingo', 'America/Sao_Paulo', 'America/Scoresbysund', 'America/Sitka', 'America/St_Barthelemy', 'America/St_Johns', 'America/St_Kitts', 'America/St_Lucia', 'America/St_Thomas', 'America/St_Vincent', 'America/Swift_Current', 'America/Tegucigalpa', 'America/Thule', 'America/Thunder_Bay', 'America/Tijuana', 'America/Toronto', 'America/Tortola', 'America/Vancouver', 'America/Whitehorse', 'America/Winnipeg', 'America/Yakutat', 'America/Yellowknife', 'Antarctica/Casey', 'Antarctica/Davis', 'Antarctica/DumontDUrville', 'Antarctica/Macquarie', 'Antarctica/Mawson', 'Antarctica/McMurdo', 'Antarctica/Palmer', 'Antarctica/Rothera', 'Antarctica/Syowa', 'Antarctica/Troll', 'Antarctica/Vostok', 'Arctic/Longyearbyen', 'Asia/Aden', 'Asia/Almaty', 'Asia/Amman', 'Asia/Anadyr', 'Asia/Aqtau', 'Asia/Aqtobe', 'Asia/Ashgabat', 'Asia/Atyrau', 'Asia/Baghdad', 'Asia/Bahrain', 'Asia/Baku', 'Asia/Bangkok', 'Asia/Barnaul', 'Asia/Beirut', 'Asia/Bishkek', 'Asia/Brunei', 'Asia/Chita', 'Asia/Choibalsan', 'Asia/Colombo', 'Asia/Damascus', 'Asia/Dhaka', 'Asia/Dili', 'Asia/Dubai', 'Asia/Dushanbe', 'Asia/Famagusta', 'Asia/Gaza', 'Asia/Hebron', 'Asia/Ho_Chi_Minh', 'Asia/Hong_Kong', 'Asia/Hovd', 'Asia/Irkutsk', 'Asia/Jakarta', 'Asia/Jayapura', 'Asia/Jerusalem', 'Asia/Kabul', 'Asia/Kamchatka', 'Asia/Karachi', 'Asia/Kathmandu', 'Asia/Khandyga', 'Asia/Kolkata', 'Asia/Krasnoyarsk', 'Asia/Kuala_Lumpur', 'Asia/Kuching', 'Asia/Kuwait', 'Asia/Macau', 'Asia/Magadan', 'Asia/Makassar', 'Asia/Manila', 'Asia/Muscat', 'Asia/Nicosia', 'Asia/Novokuznetsk', 'Asia/Novosibirsk', 'Asia/Omsk', 'Asia/Oral', 'Asia/Phnom_Penh', 'Asia/Pontianak', 'Asia/Pyongyang', 'Asia/Qatar', 'Asia/Qostanay', 'Asia/Qyzylorda', 'Asia/Riyadh', 'Asia/Sakhalin', 'Asia/Samarkand', 'Asia/Seoul', 'Asia/Shanghai', 'Asia/Singapore', 'Asia/Srednekolymsk', 'Asia/Taipei', 'Asia/Tashkent', 'Asia/Tbilisi', 'Asia/Tehran', 'Asia/Thimphu', 'Asia/Tokyo', 'Asia/Tomsk', 'Asia/Ulaanbaatar', 'Asia/Urumqi', 'Asia/Ust-Nera', 'Asia/Vientiane', 'Asia/Vladivostok', 'Asia/Yakutsk', 'Asia/Yangon', 'Asia/Yekaterinburg', 'Asia/Yerevan', 'Atlantic/Azores', 'Atlantic/Bermuda', 'Atlantic/Canary', 'Atlantic/Cape_Verde', 'Atlantic/Faroe', 'Atlantic/Madeira', 'Atlantic/Reykjavik', 'Atlantic/South_Georgia', 'Atlantic/St_Helena', 'Atlantic/Stanley', 'Australia/Adelaide', 'Australia/Brisbane', 'Australia/Broken_Hill', 'Australia/Currie', 'Australia/Darwin', 'Australia/Eucla', 'Australia/Hobart', 'Australia/Lindeman', 'Australia/Lord_Howe', 'Australia/Melbourne', 'Australia/Perth', 'Australia/Sydney', 'Europe/Amsterdam', 'Europe/Andorra', 'Europe/Astrakhan', 'Europe/Athens', 'Europe/Belgrade', 'Europe/Berlin', 'Europe/Bratislava', 'Europe/Brussels', 'Europe/Bucharest', 'Europe/Budapest', 'Europe/Busingen', 'Europe/Chisinau', 'Europe/Copenhagen', 'Europe/Dublin', 'Europe/Gibraltar', 'Europe/Guernsey', 'Europe/Helsinki', 'Europe/Isle_of_Man', 'Europe/Istanbul', 'Europe/Jersey', 'Europe/Kaliningrad', 'Europe/Kiev', 'Europe/Kirov', 'Europe/Lisbon', 'Europe/Ljubljana', 'Europe/London', 'Europe/Luxembourg', 'Europe/Madrid', 'Europe/Malta', 'Europe/Mariehamn', 'Europe/Minsk', 'Europe/Monaco', 'Europe/Moscow', 'Europe/Oslo', 'Europe/Paris', 'Europe/Podgorica', 'Europe/Prague', 'Europe/Riga', 'Europe/Rome', 'Europe/Samara', 'Europe/San_Marino', 'Europe/Sarajevo', 'Europe/Saratov', 'Europe/Simferopol', 'Europe/Skopje', 'Europe/Sofia', 'Europe/Stockholm', 'Europe/Tallinn', 'Europe/Tirane', 'Europe/Ulyanovsk', 'Europe/Uzhgorod', 'Europe/Vaduz', 'Europe/Vatican', 'Europe/Vienna', 'Europe/Vilnius', 'Europe/Volgograd', 'Europe/Warsaw', 'Europe/Zagreb', 'Europe/Zaporozhye', 'Europe/Zurich', 'Indian/Antananarivo', 'Indian/Chagos', 'Indian/Christmas', 'Indian/Cocos', 'Indian/Comoro', 'Indian/Kerguelen', 'Indian/Mahe', 'Indian/Maldives', 'Indian/Mauritius', 'Indian/Mayotte', 'Indian/Reunion', 'Pacific/Apia', 'Pacific/Auckland', 'Pacific/Bougainville', 'Pacific/Chatham', 'Pacific/Chuuk', 'Pacific/Easter', 'Pacific/Efate', 'Pacific/Enderbury', 'Pacific/Fakaofo', 'Pacific/Fiji', 'Pacific/Funafuti', 'Pacific/Galapagos', 'Pacific/Gambier', 'Pacific/Guadalcanal', 'Pacific/Guam', 'Pacific/Honolulu', 'Pacific/Kiritimati', 'Pacific/Kosrae', 'Pacific/Kwajalein', 'Pacific/Majuro', 'Pacific/Marquesas', 'Pacific/Midway', 'Pacific/Nauru', 'Pacific/Niue', 'Pacific/Norfolk', 'Pacific/Noumea', 'Pacific/Pago_Pago', 'Pacific/Palau', 'Pacific/Pitcairn', 'Pacific/Pohnpei', 'Pacific/Port_Moresby', 'Pacific/Rarotonga', 'Pacific/Saipan', 'Pacific/Tahiti', 'Pacific/Tarawa', 'Pacific/Tongatapu', 'Pacific/Wake', 'Pacific/Wallis', 'UTC'])
- typedef nokia_srlinux::types::srl_nokia_tunnel_interfaces::tunnel_interface_all¶
Base type
string
Type constraint
(((std::length(self) >= 6) and (std::length(self) <= 8)) and std::validate_type('pydantic.constr',self,{'regex': '^(?:(?:vxlan(?:0|1[0-9][0-9]|2(?:[0-4][0-9]|5[0-5])|[1-9][0-9]|[1-9])))$(?!\\n\\Z)'}))
Entities¶
- entity nokia_srlinux::Acl¶
Parents:
nokia_srlinux::Base
Top level container for configuration and operational state related to access control lists (ACLs) Yang definition can be found here: srl_nokia-acl.yang:L2329
- attribute bool? egress_mac_filtering=null¶
Must be set to true in order to apply any MAC ACLs to any subinterface in the egress traffic direction. Internally this sets the following limits: - maximum number of IPv4 ACL instances that can be created to process egress traffic = 32 - maximum number of IPv6 ACL instances that can be created to process egress traffic = 32 - maximum number of MAC ACL instances that can be created to process egress traffic = 32 Remember that the number of ACL instances per ACL policy is greater than one if subinterface-specific is set to input-and-output or output-only. A setting of true is blocked if the number of IPv4 ACL instances applied to egress traffic is already greater than 32, or if the number of IPv6 ACL instances applied to egress traffic is already greater than 32. :rel cpm_filter: Top level container for CPM filters :rel ipv4_filter: List of IPv4 filter policies :rel ipv6_filter: List of IPv6 filter policies :rel mac_filter: List of MAC ACL policies :rel policers: Container for policer definitions used by ACL entries :rel system_filter: Top level container for System filters
- relation nokia_srlinux::acl::CpmFilter cpm_filter [0:1]¶
Relation to parent container Peer relation: Top level container for CPM filters
other end:
nokia_srlinux::acl::CpmFilter.parent_acl [1]
- relation nokia_srlinux::acl::Ipv4Filter ipv4_filter [0:*]¶
Relation to parent container Peer relation: List of IPv4 filter policies
- relation nokia_srlinux::acl::Ipv6Filter ipv6_filter [0:*]¶
Relation to parent container Peer relation: List of IPv6 filter policies
- relation nokia_srlinux::acl::MacFilter mac_filter [0:*]¶
Relation to parent container Peer relation: List of MAC ACL policies
other end:
nokia_srlinux::acl::MacFilter.parent_acl [1]
- relation nokia_srlinux::acl::Policers policers [0:1]¶
Relation to parent container Peer relation: Container for policer definitions used by ACL entries
other end:
nokia_srlinux::acl::Policers.parent_acl [1]
- relation nokia_srlinux::acl::SystemFilter system_filter [0:1]¶
Relation to parent container Peer relation: Top level container for System filters
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupAclYangContainer
constrainttrue
- entity nokia_srlinux::Base¶
Parents:
std::Entity
Base for all entities representing any part of device configuration.
By default the orchestrator manages the full configuration (comanage is false) of the resource represented by the entity. This means that when the configuration is modified outside the orchestrator, the configuration is replaced by the orchestrator on the next deploy or repair. This is achieved by setting the operation on the corresponding yang container to replace. When comanage is set to true, the yang container is set to the default merge behavior. This means that any parameter or container NOT managed by the container is not touched during deploy or repair. However, when modifying key attributes of a container care must be taken to set the old container to purged so that it will be removed, otherwise invalid configurations may be created
- attribute bool comanaged=true¶
True for ‘merge’, False for ‘replace’
- attribute bool purged=false¶
True if should be removed :rel device: The device this entity should deploy to :rel resource: The resource this entity is a part of :rel yang_container:
- relation nokia_srlinux::BaseDevice device [1]¶
The device this entity should deploy to Peer relation:
- relation nokia_srlinux::Resource resource [0:1]¶
The resource this entity is a part of Peer relation:
other end:
nokia_srlinux::Resource.entities [0:*]
- relation yang::Container yang_container [1]¶
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::yangBaseEntity
constrainttrue
- entity nokia_srlinux::BaseDevice¶
Parents:
yang::BaseDevice
Entity representing a device a config should be deployed to
- attribute string[] models=List()¶
List of the model names this module uses
- dict nokia_srlinux::BaseDevice.module_mapping={'srl_nokia-aaa': 'urn:srl_nokia/aaa', 'srl_nokia-aaa-password': 'urn:srl_nokia/aaa-password', 'srl_nokia-aaa-radius': 'urn:srl_nokia/aaa-radius', 'srl_nokia-aaa-tacacs': 'urn:srl_nokia/aaa-tacacs', 'srl_nokia-aaa-types': 'urn:srl_nokia/aaa-types', 'srl_nokia-acl': 'urn:srl_nokia/acl', 'srl_nokia-acl-policers': 'urn:srl_nokia/acl-policers', 'srl_nokia-acl-qos': 'urn:srl_nokia/acl-qos', 'srl_nokia-aggregate-routes': 'urn:srl_nokia/aggregate-routes', 'srl_nokia-app-mgmt': 'urn:srl_nokia/app-mgmt', 'srl_nokia-bfd': 'urn:srl_nokia/bfd', 'srl_nokia-bgp': 'urn:srl_nokia/bgp', 'srl_nokia-bgp-evpn': 'urn:srl_nokia/network-instance/protocols/bgp-evpn', 'srl_nokia-bgp-evpn-bgp-instance-mpls-bridge-table-multicast-destinations': 'urn:srl_nokia/network-instance/protocols/bgp-evpn/bgp-instance/mpls/bridge-table/multicast-destinations', 'srl_nokia-bgp-evpn-bgp-instance-mpls-bridge-table-statistics': 'urn:srl_nokia/network-instance/protocols/bgp-evpn/bgp-instance/mpls/bridge-table/statistics', 'srl_nokia-bgp-evpn-bgp-instance-mpls-bridge-table-unicast-destinations': 'urn:srl_nokia/network-instance/protocols/bgp-evpn/bgp-instance/mpls/bridge-table/unicast-destinations', 'srl_nokia-bgp-evpn-bgp-instance-mpls-vpws-destinations': 'urn:srl_nokia/network-instance/protocols/bgp-evpn/bgp-instance/mpls/vpws-destinations', 'srl_nokia-bgp-ipvpn': 'urn:srl_nokia/network-instance/protocols/bgp-ipvpn', 'srl_nokia-bgp-vpn': 'urn:srl_nokia/bgp-vpn', 'srl_nokia-boot': 'urn:srl_nokia/boot', 'srl_nokia-bridge-table': 'urn:srl_nokia/network-instance/bridge-table', 'srl_nokia-bridge-table-mac-duplication': 'urn:srl_nokia/network-instance/bridge-table/mac-duplication', 'srl_nokia-bridge-table-mac-duplication-entries': 'urn:srl_nokia/network-instance/bridge-table/mac-duplication/mac-duplication-entries', 'srl_nokia-bridge-table-mac-learning': 'urn:srl_nokia/network-instance/bridge-table/mac-learning', 'srl_nokia-bridge-table-mac-learning-entries': 'urn:srl_nokia/network-instance/bridge-table/mac-learning/mac-learning-entries', 'srl_nokia-bridge-table-mac-limit': 'urn:srl_nokia/network-instance/bridge-table/mac-limit', 'srl_nokia-bridge-table-mac-table': 'urn:srl_nokia/network-instance/bridge-table/mac-table', 'srl_nokia-bridge-table-proxy-arp-nd': 'urn:srl_nokia/network-instance/bridge-table/proxy-arp-nd', 'srl_nokia-bridge-table-reserved-macs': 'urn:srl_nokia/network-instance/bridge-table/reserved-macs', 'srl_nokia-bridge-table-shg': 'urn:srl_nokia/network-instance/bridge-table/shg', 'srl_nokia-bridge-table-static-mac': 'urn:srl_nokia/network-instance/bridge-table/static-mac', 'srl_nokia-common': 'urn:srl_nokia/common', 'srl_nokia-configuration': 'urn:srl_nokia/configuration', 'srl_nokia-configuration-role': 'urn:srl_nokia/configuration-role', 'srl_nokia-connection-point': 'urn:srl_nokia/network-instance/connection-point', 'srl_nokia-dhcp-server': 'urn:srl_nokia/dhcp-server', 'srl_nokia-dns': 'urn:srl_nokia/dns', 'srl_nokia-ethcfm': 'urn:srl_nokia/ethcfm', 'srl_nokia-ethcfm-types': 'urn:srl_nokia/ethcfm/types', 'srl_nokia-event-handler': 'urn:srl_nokia/event-handler', 'srl_nokia-extensions': 'urn:srl_nokia/extensions', 'srl_nokia-features': 'urn:srl_nokia/features', 'srl_nokia-ftp': 'urn:srl_nokia/ftp', 'srl_nokia-gnmi-server': 'urn:srl_nokia/gnmi-server', 'srl_nokia-gnsi-authz': 'urn:srl_nokia/gnsi-authz', 'srl_nokia-gnsi-certz': 'urn:srl_nokia/gnsi-certz', 'srl_nokia-gribi-server': 'urn:srl_nokia/gribi-server', 'srl_nokia-icmp': 'urn:srl_nokia/icmp', 'srl_nokia-if-ip': 'urn:srl_nokia/interfaces/ip', 'srl_nokia-if-mpls': 'urn:srl_nokia/interfaces/mpls', 'srl_nokia-igmp': 'urn:srl_nokia/igmp', 'srl_nokia-igmp-snooping': 'urn:srl_nokia/igmp-snooping', 'srl_nokia-igmp-types': 'urn:srl_nokia/igmp-types', 'srl_nokia-interfaces': 'urn:srl_nokia/interfaces', 'srl_nokia-interfaces-bridge-table': 'urn:srl_nokia/interfaces/bridge-table', 'srl_nokia-interfaces-bridge-table-mac-duplication-entries': 'urn:srl_nokia/interfaces/bridge-table/mac-duplication/mac-duplication-entries', 'srl_nokia-interfaces-bridge-table-mac-learning-entries': 'urn:srl_nokia/interfaces/bridge-table/mac-duplication/mac-learning-entries', 'srl_nokia-interfaces-bridge-table-mac-table': 'urn:srl_nokia/interfaces/bridge-table/mac-table', 'srl_nokia-interfaces-bridge-table-statistics': 'urn:srl_nokia/interfaces/bridge-table/statistics', 'srl_nokia-interfaces-ethernet-segment-association': 'urn:srl_nokia/interfaces/ethernet-segment-association', 'srl_nokia-interfaces-ip-dhcp': 'urn:srl_nokia/interfaces/ip/dhcp', 'srl_nokia-interfaces-ip-dhcp-relay': 'urn:srl_nokia/interfaces/ip/dhcp/relay', 'srl_nokia-interfaces-ip-dhcp-server': 'urn:srl_nokia/interfaces/ip/dhcp/server', 'srl_nokia-interfaces-ip-vrrp': 'urn:srl_nokia/interfaces/ip/vrrp', 'srl_nokia-interfaces-l2cp': 'urn:srl_nokia/interfaces/l2cp', 'srl_nokia-interfaces-lag': 'urn:srl_nokia/interfaces/lags', 'srl_nokia-interfaces-local-mirror-destination': 'urn:srl_nokia/interfaces/local-mirror-destination', 'srl_nokia-interfaces-nbr': 'urn:srl_nokia/interfaces/ip/nbr', 'srl_nokia-interfaces-nbr-evpn': 'urn:srl_nokia/interfaces/ip/nbr/evpn', 'srl_nokia-interfaces-nbr-virtual-ip-discovery': 'urn:srl_nokia/interfaces/ip/nbr/virtual-ip-discovery', 'srl_nokia-interfaces-p4rt': 'urn:srl_nokia/interfaces/p4rt', 'srl_nokia-interfaces-router-adv': 'urn:srl_nokia/interfaces/ip/ra', 'srl_nokia-interfaces-vlans': 'urn:srl_nokia/interfaces/vlans', 'srl_nokia-interfaces-vxdp': 'urn:srl_nokia/interfaces-vxdp', 'srl_nokia-ip-route-tables': 'urn:srl_nokia/ip-route-tables', 'srl_nokia-ippm-source-udp-pool': 'urn:srl_nokia/ippm-sourceudp--pool', 'srl_nokia-isis': 'urn:srl_nokia/isis', 'srl_nokia-isis-lsdb': 'urn:srl_nokia/isis-lsdb', 'srl_nokia-isis-lsdb-types': 'urn:srl_nokia/isis/lsdb-types', 'srl_nokia-json-rpc': 'urn:srl_nokia/json-rpc', 'srl_nokia-keychains': 'urn:srl_nokia/keychains', 'srl_nokia-lacp': 'urn:srl_nokia/lacp', 'srl_nokia-ldp': 'urn:srl_nokia/ldp', 'srl_nokia-license': 'urn:srl_nokia/license', 'srl_nokia-link-measurement': 'urn:srl_nokia/link-measurement', 'srl_nokia-linux': 'urn:srl_nokia/linux', 'srl_nokia-lldp': 'urn:srl_nokia/lldp', 'srl_nokia-lldp-types': 'urn:srl_nokia/lldp-types', 'srl_nokia-load-balancing': 'urn:srl_nokia/load-balancing', 'srl_nokia-logging': 'urn:srl_nokia-logging', 'srl_nokia-lsp-ping-trace': 'urn:srl_nokia/lsp-ping-trace', 'srl_nokia-macsec': 'urn:srl_nokia-macsec', 'srl_nokia-maintenance-mode': 'urn:srl_nokia/maintenance-mode', 'srl_nokia-maintenance-policies': 'urn:srl_nokia/maintenance-policies', 'srl_nokia-micro-bfd': 'urn:srl_nokia/micro-bfd', 'srl_nokia-mirroring': 'urn:srl_nokia/system/mirroring', 'srl_nokia-mld': 'urn:srl_nokia/mld', 'srl_nokia-mld-snooping': 'urn:srl_nokia/mld-snooping', 'srl_nokia-mpls': 'urn:srl_nokia/mpls', 'srl_nokia-mpls-label-management': 'urn:srl_nokia/mpls-label-management', 'srl_nokia-mpls-route-tables': 'urn:srl_nokia/mpls-route-tables', 'srl_nokia-mpls-services-evpn-label-management': 'urn:srl_nokia/mpls-services-evpn-management', 'srl_nokia-mpls-services-network-instance-label-management': 'urn:srl_nokia/mpls-services-network-instance-management', 'srl_nokia-mtu': 'urn:srl_nokia/mtu', 'srl_nokia-multicast-mfib-tables': 'urn:srl_nokia/network-instance/mfib-tables', 'srl_nokia-mvpn-l3': 'urn:srl_nokia/mvpn-l3', 'srl_nokia-network-instance': 'urn:srl_nokia/network-instance', 'srl_nokia-network-instance-mtu': 'urn:srl_nokia/netinst-mtu', 'srl_nokia-next-hop-groups': 'urn:srl_nokia/next-hop-groups', 'srl_nokia-ntp': 'urn:srl_nokia/ntp', 'srl_nokia-oam': 'urn:srl_nokia/oam', 'srl_nokia-oam-pm': 'urn:srl_nokia/oam/pm/', 'srl_nokia-oam-pm-ethcfm': 'urn:srl_nokia/oam/pm/ethcfm', 'srl_nokia-oam-pm-ip': 'urn:srl_nokia/oam/pm/ip', 'srl_nokia-oam-pm-types': 'urn:srl_nokia/oam/pm/types', 'srl_nokia-openconfig': 'urn:srl_nokia/openconfig', 'srl_nokia-ospf': 'urn:srl_nokia/ospf', 'srl_nokia-ospf-types': 'urn:srl_nokia/ospf-types', 'srl_nokia-p4rt-server': 'urn:srl_nokia/p4rt-server', 'srl_nokia-packet-link-qual': 'urn:srl_nokia/packet-link-qual', 'srl_nokia-packet-match-types': 'urn:srl_nokia/packet-match-types', 'srl_nokia-pcep': 'urn:srl_nokia/pcep', 'srl_nokia-pim': 'urn:srl_nokia/pim', 'srl_nokia-platform': 'urn:srl_nokia/platform', 'srl_nokia-platform-acl': 'urn:srl_nokia/platform-acl', 'srl_nokia-platform-cgroup': 'urn:srl_nokia/platform-cgroup', 'srl_nokia-platform-chassis': 'urn:srl_nokia/platform-chassis', 'srl_nokia-platform-control': 'urn:srl_nokia/platform-control', 'srl_nokia-platform-cpu': 'urn:srl_nokia/platform-cpu', 'srl_nokia-platform-datapath-resources': 'urn:srl_nokia/platform-datapath-resources', 'srl_nokia-platform-disk': 'urn:srl_nokia/platform-disk', 'srl_nokia-platform-fabric': 'urn:srl_nokia/platform-fabric', 'srl_nokia-platform-fan': 'urn:srl_nokia/platform-fan', 'srl_nokia-platform-healthz': 'urn:srl_nokia/platform-healthz', 'srl_nokia-platform-lc': 'urn:srl_nokia/platform-lc', 'srl_nokia-platform-linecard-fib': 'urn:srl_nokia/platform-lc-fib', 'srl_nokia-platform-memory': 'urn:srl_nokia/platform-memory', 'srl_nokia-platform-mtu': 'urn:srl_nokia/platform-mtu', 'srl_nokia-platform-p4rt': 'urn:srl_nokia/platform/p4rt', 'srl_nokia-platform-pipeline-counters': 'urn:srl_nokia/platform-host-interface-pipeline', 'srl_nokia-platform-psu': 'urn:srl_nokia/platform-psu', 'srl_nokia-platform-qos': 'urn:srl_nokia/platform-qos', 'srl_nokia-platform-redundancy': 'urn:srl_nokia/platform-redundancy', 'srl_nokia-platform-resource-mgmt': 'urn:srl_nokia/platform-res-mgmt', 'srl_nokia-platform-resource-monitoring': 'urn:srl_nokia/platform-res-monitor', 'srl_nokia-platform-secure-boot': 'urn:srl_nokia/platform-secure-boot', 'srl_nokia-platform-tcam': 'urn:srl_nokia/platform-tcam', 'srl_nokia-platform-tpm': 'urn:srl_nokia/platform-tpm', 'srl_nokia-platform-vxdp': 'urn:srl_nokia/platform-vxdp', 'srl_nokia-policy-forwarding': 'urn:srl_nokia/policy-forwarding', 'srl_nokia-policy-types': 'urn:srl_nokia/policy-types', 'srl_nokia-qos': 'urn:srl_nokia/qos', 'srl_nokia-qos-policers': 'urn:srl_nokia/qos-policers', 'srl_nokia-ra_guard': 'urn:srl_nokia/ra_guard', 'srl_nokia-rib-bgp': 'urn:srl_nokia/bgp-rib', 'srl_nokia-routing-policy': 'urn:srl_nokia/routing-policy', 'srl_nokia-segment-routing': 'urn:srl_nokia/segment-routing', 'srl_nokia-sflow': 'urn:srl_nokia/sflow', 'srl_nokia-snmp': 'urn:srl_nokia/snmp', 'srl_nokia-snmp-trace': 'urn:srl_nokia-snmp-trace', 'srl_nokia-ssh': 'urn:srl_nokia/ssh', 'srl_nokia-stamp': 'urn:srl_nokia/stamp', 'srl_nokia-static-routes': 'urn:srl_nokia/static-routes', 'srl_nokia-sync': 'urn:srl_nokia/sync', 'srl_nokia-sync-freq': 'urn:srl_nokia/sync-freq', 'srl_nokia-sync-interfaces': 'urn:srl_nokia/sync-interfaces', 'srl_nokia-sync-ptp': 'urn:srl_nokia/sync-ptp', 'srl_nokia-sync-types': 'urn:srl_nokia/sync-types', 'srl_nokia-system': 'urn:srl_nokia/system', 'srl_nokia-system-banner': 'urn:srl_nokia/system-banner', 'srl_nokia-system-bridge-table': 'urn:srl_nokia/system/bridge-table', 'srl_nokia-system-bridge-table-proxy-arp': 'urn:srl_nokia/system/bridge-table/proxy-arp', 'srl_nokia-system-info': 'urn:srl_nokia/system-info', 'srl_nokia-system-multicast': 'urn:srl_nokia/system/multicast', 'srl_nokia-system-multicast-mfib-table': 'urn:srl_nokia/system/multicast/mfib', 'srl_nokia-system-name': 'urn:srl_nokia/system-name', 'srl_nokia-system-network-instance': 'urn:srl_nokia/system-network-instance', 'srl_nokia-system-network-instance-bgp-evpn-ethernet-segments': 'urn:srl_nokia/system-bgp-evpn-ethernet-segments', 'srl_nokia-system-network-instance-bgp-vpn': 'urn:srl_nokia/system-bgp-vpn', 'srl_nokia-system-protocols': 'urn:srl_nokia/system-protocols', 'srl_nokia-tcp-udp': 'urn:srl_nokia/tcp-udp', 'srl_nokia-te-policies': 'urn:srl_nokia/te-policies', 'srl_nokia-timezone': 'urn:srl_nokia/timezone', 'srl_nokia-tls': 'urn:srl_nokia/tls', 'srl_nokia-traffic-engineering': 'urn:srl_nokia/te', 'srl_nokia-transport-security': 'urn:srl_nokia/transport-security', 'srl_nokia-tunnel': 'urn:srl_nokia/tunnel', 'srl_nokia-tunnel-interfaces': 'urn:srl_nokia/tunnel-interfaces', 'srl_nokia-tunnel-interfaces-vxlan-interface-bridge-table': 'urn:srl_nokia/tunnel-interface/vxlan-interface/bridge-table/statistics', 'srl_nokia-tunnel-interfaces-vxlan-interface-bridge-table-multicast-destinations': 'urn:srl_nokia/tunnel-interface/vxlan-interface/bridge-table/multicast-destinations', 'srl_nokia-tunnel-interfaces-vxlan-interface-bridge-table-unicast-destinations': 'urn:srl_nokia/tunnel-interface/vxlan-interface/bridge-table/unicast-destinations', 'srl_nokia-tunnel-interfaces-vxlan-interface-bridge-table-unicast-es-destination-vteps': 'urn:srl_nokia/tunnel-interface/vxlan-interface/bridge-table/unicast-destinations/es-destination', 'srl_nokia-tunnel-tables': 'urn:srl_nokia/tunnel-tables', 'srl_nokia-twamp': 'urn:srl_nokia/twamp', 'srl_nokia-vxlan-tunnel-vtep': 'urn:srl_nokia/tunnel/vxlan-tunnel'}
Dictionary contraing namespaces definitions. Key - module name. Value - namespace URI.
The following implementations are defined for this entity:
- entity nokia_srlinux::Bfd¶
Parents:
nokia_srlinux::Base
Context to configure BFD parameters and report BFD sessions state Yang definition can be found here: srl_nokia-bfd.yang:L140
- Rel micro_bfd_sessions:
Context to configure micro-BFD session parameters and report sessions state
- Rel subinterface:
List of subinterface references to associating BFD config and state
- relation nokia_srlinux::bfd::MicroBfdSessions micro_bfd_sessions [0:1]¶
Relation to parent container Peer relation: Context to configure micro-BFD session parameters and report sessions state
other end:
nokia_srlinux::bfd::MicroBfdSessions.parent_bfd [1]
- relation nokia_srlinux::bfd::Subinterface subinterface [0:*]¶
Relation to parent container Peer relation: List of subinterface references to associating BFD config and state
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupBfdYangContainer
constrainttrue
- entity nokia_srlinux::GnmiDevice¶
Parents:
nokia_srlinux::BaseDevice
,yang::GnmiDevice
Entity representing a device that should be configured using gnmi as backend
The following implements statements select implementations for this entity:
constraint
true
nokia_srlinux::yangDevice
constrainttrue
- entity nokia_srlinux::Interface¶
Parents:
nokia_srlinux::Base
The list of named interfaces on the device Yang definition can be found here: srl_nokia-interfaces.yang:L793
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The configured, desired state of the interface
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user-configured description of the interface
- attribute nokia_srlinux::interface_mtu_t? mtu=null¶
Port MTU in bytes including ethernet overhead but excluding 4-bytes FCS If a transmitted packet exceeds this size it is dropped. The default value for ethernet-x interfaces is taken from /system/mtu/default-port-mtu. For the mgmt0 and mgmt0-standby interfaces the default is 1514 bytes, but the value can be changed for each interface individually. Port MTU is not configurable for loopback interfaces. The max mtu for the mgmt0 and mgmt0-standby interfaces is 9216. The 7220 IXR-D1, 7220 IXR-D2, 7220 IXR-D3, 7220 IXR-H2, and 7220 IXR-H3 systems support a maximum port MTU of 9412 bytes and minimum of 1500 bytes. The VSRL system supports a maximum port MTU of 9500 and minimum of 1450 bytes. All other systems support a maximum port MTU of 9500 and minimum of 1500 bytes. Each 7250 IXR IMM supports a maximum of 8 different port MTU values. 7220 IXR systems do not have any limit on the maximum number of different port MTU values.
- attribute nokia_srlinux::types::srl_nokia_common::interface_all name¶
The name of the interface Valid options are: irb<N>, N=0..255 lif-<lif_name> enp<bus>s<dev>f<fn>, bus=0..255, dev=0..31, fn=0..7 vhn-<vhn_name> lag<N>, N=1..128 [note1] lo<N>, N=0..255 mgmt0 mgmt0-standby ethernet-<slot>/<port> ethernet-<slot>/<mda>/<port> system0 <lif_name>=Linux interface name <vhn_name>=vhost interface name <slot>=slot number {1,2,3,..} <mda>=mda id {a,b,c,d} <port>=port id {1,2,3,..} [note1] N=1..32 for 7220-D1. N=1..64 for 7220-D2, 7220-D3, 7220-D5. N=1..127 for 7220-H2, 7220-H3.
- attribute string? tpid=null¶
Optionally set the tag protocol identifier field (TPID) that is accepted on the VLAN
- attribute nokia_srlinux::types::srl_nokia_common::uuid? uuid=null¶
The system-generated or user-configured UUID for the interface
- attribute bool? vlan_tagging=null¶
When set to true the interface is allowed to accept frames with one or more VLAN tags :rel breakout_mode: Configuration of breakout options. The 7220 D3 supports 4x10 and 4x25 breakout on ports 3-33. The 7220 D3L supports 4x10 and 4x25 breakout on ports 1-31. The 7220 H3 supports 2x100/4x100 breakout on ports 3-34. The 7220 H4 supports 4x100 breakout on ports 1-64. The 7220 D4 supports 4x100 breakout on ports 30-36. The 7220 D4 supports 4x25 breakout on ports 9, 15, 16 and 30-36. The 7220 D4 supports 4x10 breakout on ports 9, 15, 16 and 30-36. The 7220 D5 supports 4x10, 4x25 and 2x100/4x100 breakout on ports 1-32. 7250 IXR-6e/10e 36p QSFPDD IMM all port: 4x100GE and 2x100GE :rel ethernet: :rel lag: Container for options related to LAG :rel linux: Top-level container for configuration and state related to Linux interfaces :rel p4rt: Top-level container for P4Runtime interface configuration and state :rel sflow: Context to configure sFlow parameters :rel subinterface: The list of subinterfaces (logical interfaces) associated with a physical interface :rel transceiver: :rel vhost: Top-level container for vhost-user interface configuration and state
- relation nokia_srlinux::interface::BreakoutMode breakout_mode [0:1]¶
Relation to parent container Peer relation: Configuration of breakout options.
The 7220 D3 supports 4x10 and 4x25 breakout on ports 3-33. The 7220 D3L supports 4x10 and 4x25 breakout on ports 1-31. The 7220 H3 supports 2x100/4x100 breakout on ports 3-34. The 7220 H4 supports 4x100 breakout on ports 1-64. The 7220 D4 supports 4x100 breakout on ports 30-36. The 7220 D4 supports 4x25 breakout on ports 9, 15, 16 and 30-36. The 7220 D4 supports 4x10 breakout on ports 9, 15, 16 and 30-36. The 7220 D5 supports 4x10, 4x25 and 2x100/4x100 breakout on ports 1-32. 7250 IXR-6e/10e 36p QSFPDD IMM all port: 4x100GE and 2x100GE
other end:
nokia_srlinux::interface::BreakoutMode.parent_interface [1]
- relation nokia_srlinux::interface::Ethernet ethernet [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::Ethernet.parent_interface [1]
- relation nokia_srlinux::interface::Lag lag [0:1]¶
Relation to parent container Peer relation: Container for options related to LAG
other end:
nokia_srlinux::interface::Lag.parent_interface [1]
- relation nokia_srlinux::interface::Linux linux [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to Linux interfaces
other end:
nokia_srlinux::interface::Linux.parent_interface [1]
- relation nokia_srlinux::interface::P4rt p4rt [0:1]¶
Relation to parent container Peer relation: Top-level container for P4Runtime interface configuration and state
other end:
nokia_srlinux::interface::P4rt.parent_interface [1]
- relation nokia_srlinux::interface::Sflow sflow [0:1]¶
Relation to parent container Peer relation: Context to configure sFlow parameters
other end:
nokia_srlinux::interface::Sflow.parent_interface [1]
- relation nokia_srlinux::interface::Subinterface subinterface [0:4095]¶
Relation to parent container Peer relation: The list of subinterfaces (logical interfaces) associated with a physical interface
other end:
nokia_srlinux::interface::Subinterface.parent_interface [1]
- relation nokia_srlinux::interface::Transceiver transceiver [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::Transceiver.parent_interface [1]
- relation nokia_srlinux::interface::Vhost vhost [0:1]¶
Relation to parent container Peer relation: Top-level container for vhost-user interface configuration and state
other end:
nokia_srlinux::interface::Vhost.parent_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupInterfaceYangContainer
constrainttrue
- entity nokia_srlinux::NetworkInstance¶
Parents:
nokia_srlinux::Base
Network instances configured on the local system Yang definition can be found here: srl_nokia-network-instance.yang:L154
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf contains the configured, desired state of the network instance.
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user-entered description of this network instance.
- attribute nokia_srlinux::types::srl_nokia_common::restricted_name name¶
A unique name identifying the network instance
- attribute nokia_srlinux::types::srl_nokia_common::dotted_quad? router_id=null¶
A identifier for the local network instance - typically used within associated routing protocols or signalling routing information in another network instance
- attribute string? type=null¶
The type of network instance. The value of this leaf indicates the type of forwarding entries that should be supported by this network instance :rel aggregate_routes: :rel bridge_table: :rel connection_point: Connection-point information. :rel inter_instance_policies: Policies for leaking routes between this network instance and other network instances :rel interface: List of subinterfaces used by this network-instance :rel ip_forwarding: Forwarding options that apply to the entire network instance. :rel ip_load_balancing: Container for IP load-balancing options that are specific to the network-instance :rel maintenance_policies: Container with maintenance policies :rel mpls: :rel mpls_forwarding: :rel mtu: Top-level container for configuration and state data related to network-instance MTU :rel multicast_l3_vpn: :rel next_hop_groups: :rel policy_forwarding: Configuration and operational state relating to policy-forwarding within a network instance. :rel protocols: The routing protocols that are enabled for this network-instance. :rel segment_routing: Container with segment routing configuration options :rel static_routes: :rel traffic_engineering: Container with traffic engineering options for the network-instance :rel traffic_engineering_policies: Container with traffic engineering policies :rel vxlan_interface: List of vxlan-interfaces used by this network-instance
- relation nokia_srlinux::network_instance::AggregateRoutes aggregate_routes [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::AggregateRoutes.parent_network_instance [1]
- relation nokia_srlinux::network_instance::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::BridgeTable.parent_network_instance [1]
- relation nokia_srlinux::network_instance::ConnectionPoint connection_point [0:*]¶
Relation to parent container Peer relation: Connection-point information.
other end:
nokia_srlinux::network_instance::ConnectionPoint.parent_network_instance [1]
- relation nokia_srlinux::network_instance::InterInstancePolicies inter_instance_policies [0:1]¶
Relation to parent container Peer relation: Policies for leaking routes between this network instance and other network instances
other end:
nokia_srlinux::network_instance::InterInstancePolicies.parent_network_instance [1]
- relation nokia_srlinux::network_instance::Interface interface [0:*]¶
Relation to parent container Peer relation: List of subinterfaces used by this network-instance
other end:
nokia_srlinux::network_instance::Interface.parent_network_instance [1]
- relation nokia_srlinux::network_instance::IpForwarding ip_forwarding [0:1]¶
Relation to parent container Peer relation: Forwarding options that apply to the entire network instance.
other end:
nokia_srlinux::network_instance::IpForwarding.parent_network_instance [1]
- relation nokia_srlinux::network_instance::IpLoadBalancing ip_load_balancing [0:1]¶
Relation to parent container Peer relation: Container for IP load-balancing options that are specific to the network-instance
other end:
nokia_srlinux::network_instance::IpLoadBalancing.parent_network_instance [1]
- relation nokia_srlinux::network_instance::MaintenancePolicies maintenance_policies [0:1]¶
Relation to parent container Peer relation: Container with maintenance policies
other end:
nokia_srlinux::network_instance::MaintenancePolicies.parent_network_instance [1]
- relation nokia_srlinux::network_instance::Mpls mpls [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Mpls.parent_network_instance [1]
- relation nokia_srlinux::network_instance::MplsForwarding mpls_forwarding [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::MplsForwarding.parent_network_instance [1]
- relation nokia_srlinux::network_instance::Mtu mtu [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to network-instance MTU
other end:
nokia_srlinux::network_instance::Mtu.parent_network_instance [1]
- relation nokia_srlinux::network_instance::MulticastL3Vpn multicast_l3_vpn [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::MulticastL3Vpn.parent_network_instance [1]
- relation nokia_srlinux::network_instance::NextHopGroups next_hop_groups [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::NextHopGroups.parent_network_instance [1]
- relation nokia_srlinux::network_instance::PolicyForwarding policy_forwarding [0:1]¶
Relation to parent container Peer relation: Configuration and operational state relating to policy-forwarding within a network instance.
other end:
nokia_srlinux::network_instance::PolicyForwarding.parent_network_instance [1]
- relation nokia_srlinux::network_instance::Protocols protocols [0:1]¶
Relation to parent container Peer relation: The routing protocols that are enabled for this network-instance.
other end:
nokia_srlinux::network_instance::Protocols.parent_network_instance [1]
- relation nokia_srlinux::network_instance::SegmentRouting segment_routing [0:1]¶
Relation to parent container Peer relation: Container with segment routing configuration options
other end:
nokia_srlinux::network_instance::SegmentRouting.parent_network_instance [1]
- relation nokia_srlinux::network_instance::StaticRoutes static_routes [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::StaticRoutes.parent_network_instance [1]
- relation nokia_srlinux::network_instance::TrafficEngineering traffic_engineering [0:1]¶
Relation to parent container Peer relation: Container with traffic engineering options for the network-instance
other end:
nokia_srlinux::network_instance::TrafficEngineering.parent_network_instance [1]
- relation nokia_srlinux::network_instance::TrafficEngineeringPolicies traffic_engineering_policies [0:1]¶
Relation to parent container Peer relation: Container with traffic engineering policies
other end:
nokia_srlinux::network_instance::TrafficEngineeringPolicies.parent_network_instance [1]
- relation nokia_srlinux::network_instance::VxlanInterface vxlan_interface [0:1]¶
Relation to parent container Peer relation: List of vxlan-interfaces used by this network-instance
other end:
nokia_srlinux::network_instance::VxlanInterface.parent_network_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupNetworkInstanceYangContainer
constrainttrue
- entity nokia_srlinux::Oam¶
Parents:
nokia_srlinux::Base
Enclosing container for OAM Yang definition can be found here: srl_nokia-oam.yang:L29
- Rel ethcfm:
OAM configuration and operational data for the management of Ethernet (ETH-CFM)
- Rel ippm:
- Rel link_measurement:
- Rel performance_monitoring:
OAM Performance Monitoring
- Rel stamp:
- Rel twamp:
- relation nokia_srlinux::oam::Ethcfm ethcfm [0:1]¶
Relation to parent container Peer relation: OAM configuration and operational data for the management of Ethernet (ETH-CFM)
other end:
nokia_srlinux::oam::Ethcfm.parent_oam [1]
- relation nokia_srlinux::oam::Ippm ippm [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::Ippm.parent_oam [1]
- relation nokia_srlinux::oam::LinkMeasurement link_measurement [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::LinkMeasurement.parent_oam [1]
- relation nokia_srlinux::oam::PerformanceMonitoring performance_monitoring [0:1]¶
Relation to parent container Peer relation: OAM Performance Monitoring
other end:
nokia_srlinux::oam::PerformanceMonitoring.parent_oam [1]
- relation nokia_srlinux::oam::Stamp stamp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::Stamp.parent_oam [1]
- relation nokia_srlinux::oam::Twamp twamp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::Twamp.parent_oam [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupOamYangContainer
constrainttrue
- entity nokia_srlinux::Platform¶
Parents:
nokia_srlinux::Base
Enclosing container for platform components Yang definition can be found here: srl_nokia-platform.yang:L319
- Rel chassis:
Top-level container for chassis configuration and state
- Rel control:
Top-level container for control module configuration and state
- Rel fabric:
Top-level container for fabric configuration and state
- Rel linecard:
Top-level container for linecard configuration and state
- Rel redundancy:
Top-level container for platform redundancy
- Rel resource_management:
Container for managing resources in a system-wide context
- Rel resource_monitoring:
- Rel vxdp:
Top-level container for vXDP configuration and state
- relation nokia_srlinux::platform::Chassis chassis [0:1]¶
Relation to parent container Peer relation: Top-level container for chassis configuration and state
other end:
nokia_srlinux::platform::Chassis.parent_platform [1]
- relation nokia_srlinux::platform::Control control [0:*]¶
Relation to parent container Peer relation: Top-level container for control module configuration and state
other end:
nokia_srlinux::platform::Control.parent_platform [1]
- relation nokia_srlinux::platform::Fabric fabric [0:*]¶
Relation to parent container Peer relation: Top-level container for fabric configuration and state
other end:
nokia_srlinux::platform::Fabric.parent_platform [1]
- relation nokia_srlinux::platform::Linecard linecard [0:*]¶
Relation to parent container Peer relation: Top-level container for linecard configuration and state
other end:
nokia_srlinux::platform::Linecard.parent_platform [1]
- relation nokia_srlinux::platform::Redundancy redundancy [0:1]¶
Relation to parent container Peer relation: Top-level container for platform redundancy
other end:
nokia_srlinux::platform::Redundancy.parent_platform [1]
- relation nokia_srlinux::platform::ResourceManagement resource_management [0:1]¶
Relation to parent container Peer relation: Container for managing resources in a system-wide context
other end:
nokia_srlinux::platform::ResourceManagement.parent_platform [1]
- relation nokia_srlinux::platform::ResourceMonitoring resource_monitoring [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::ResourceMonitoring.parent_platform [1]
- relation nokia_srlinux::platform::Vxdp vxdp [0:1]¶
Relation to parent container Peer relation: Top-level container for vXDP configuration and state
other end:
nokia_srlinux::platform::Vxdp.parent_platform [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupPlatformYangContainer
constrainttrue
- entity nokia_srlinux::Resource¶
Parents:
yang::ResourceBuilder
All entities modelled in this module are translated to the correct yang model. Each device creates a global yang resource that collects all containers in the model.
When an entity that inherits from Base is associated with this resource, it will be added to a different yang resource. This can be used to create a distinction between global configuration and service specific configuration and put them in their own failure domain.
- Rel entities:
- relation nokia_srlinux::Base entities [0:*]¶
The resource this entity is a part of Peer relation:
other end:
nokia_srlinux::Base.resource [0:1]
The following implements statements select implementations for this entity:
constraint
true
- entity nokia_srlinux::RoutingPolicy¶
Parents:
nokia_srlinux::Base
Top-level container for all routing policy configuration Yang definition can be found here: srl_nokia-routing-policy.yang:L593
- Rel as_path_set:
AS Path regular expressions for use in policy entries
- Rel community_set:
List of BGP community sets containing standard and large BGP communities
- Rel policy:
List of policy definitions, keyed by unique name
These policy definitions are expected to be referenced (by name) in policy in import-policy and/or export-policy statements. :rel prefix_set: List of defined prefix sets :rel tag_set: List of administrative tag sets
- relation nokia_srlinux::routing_policy::AsPathSet as_path_set [0:*]¶
Relation to parent container Peer relation: AS Path regular expressions for use in policy entries
other end:
nokia_srlinux::routing_policy::AsPathSet.parent_routing_policy [1]
- relation nokia_srlinux::routing_policy::CommunitySet community_set [0:*]¶
Relation to parent container Peer relation: List of BGP community sets containing standard and large BGP communities
other end:
nokia_srlinux::routing_policy::CommunitySet.parent_routing_policy [1]
- relation nokia_srlinux::routing_policy::Policy policy [0:*]¶
Relation to parent container Peer relation: List of policy definitions, keyed by unique name These policy definitions are expected to be referenced (by name) in policy in import-policy and/or export-policy statements.
other end:
nokia_srlinux::routing_policy::Policy.parent_routing_policy [1]
- relation nokia_srlinux::routing_policy::PrefixSet prefix_set [0:*]¶
Relation to parent container Peer relation: List of defined prefix sets
other end:
nokia_srlinux::routing_policy::PrefixSet.parent_routing_policy [1]
- relation nokia_srlinux::routing_policy::TagSet tag_set [0:255]¶
Relation to parent container Peer relation: List of administrative tag sets
other end:
nokia_srlinux::routing_policy::TagSet.parent_routing_policy [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupRoutingPolicyYangContainer
constrainttrue
- entity nokia_srlinux::System¶
Parents:
nokia_srlinux::Base
Enclosing container for system management Yang definition can be found here: srl_nokia-system.yang:L45
- attribute nokia_srlinux::system_trace_options_t[]? trace_options=null¶
Management server trace options :rel aaa: Top-level container for AAA services :rel authentication: Container for protocol authentication options available system wide :rel banner: Contains configuration and state related to system banners :rel boot: Top-level container for configuration and state data related to booting the system :rel bridge_table: system bridge-table information :rel clock: Top-level container for system clock configuration and state :rel configuration: Top-level container for configuration and state data related to the system configuration :rel dhcp_server: Configures the dhcp server :rel dns: Top-level container for DNS configuration and state :rel event_handler: Top-level container for configuration and state of event handler and event handling instances :rel ftp_server: Top-level container for FTP server configuration and state :rel gnmi_server: Configures the gNMI server access API :rel gribi_server: Configures the gRPC Routing Information Base Interface (gRIBI) service :rel information: Top-level container for system information configuration and state :rel json_rpc_server: Configures the JSON RPC access API :rel lacp: :rel license: List of licenses configured on the system :rel lldp: Top-level container for LLDP configuration and state data :rel logging: System logging provides the interface to syslog services to setup output entities on a selection of log sources. :rel maintenance: Top-level container for Maintenance Mode configuration :rel management: Enclosing container for options relating to management server :rel mirroring: Top level container for configuration and operational state for mirroring :rel mpls: Container for system wide MPLS label management :rel mtu: Top-level container for configuration and state data related to the system MTU :rel multicast: system multicast information :rel name: Contains configuration and state related to system naming :rel network_instance: :rel ntp: Top-level container for NTP configuration and state :rel p4rt_server: Configures the P4Runtime service :rel packet_link_qualification: Top-level container for gNOI Packet Link Qualification profiles :rel protocols: The routing protocols that are supported by the system :rel ra_guard_policy: List containing RA Guard Policy and parameters :rel sflow: Context to configure sFlow Agent parameters and report sFlow state :rel snmp: Top-level container for SNMP configuration and state :rel ssh_server: Top-level container for SSH server configuration and state :rel sync: Context to configure sync parameters and report sessions state :rel tls: Top-level container for TLS configuration and state
- relation nokia_srlinux::system::Aaa aaa [0:1]¶
Relation to parent container Peer relation: Top-level container for AAA services
other end:
nokia_srlinux::system::Aaa.parent_system [1]
- relation nokia_srlinux::system::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container for protocol authentication options available system wide
other end:
nokia_srlinux::system::Authentication.parent_system [1]
- relation nokia_srlinux::system::Banner banner [0:1]¶
Relation to parent container Peer relation: Contains configuration and state related to system banners
- relation nokia_srlinux::system::Boot boot [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to booting the system
- relation nokia_srlinux::system::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation: system bridge-table information
other end:
nokia_srlinux::system::BridgeTable.parent_system [1]
- relation nokia_srlinux::system::Clock clock [0:1]¶
Relation to parent container Peer relation: Top-level container for system clock configuration and state
- relation nokia_srlinux::system::Configuration configuration [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to the system configuration
other end:
nokia_srlinux::system::Configuration.parent_system [1]
- relation nokia_srlinux::system::DhcpServer dhcp_server [0:1]¶
Relation to parent container Peer relation: Configures the dhcp server
other end:
nokia_srlinux::system::DhcpServer.parent_system [1]
- relation nokia_srlinux::system::Dns dns [0:1]¶
Relation to parent container Peer relation: Top-level container for DNS configuration and state
other end:
nokia_srlinux::system::Dns.parent_system [1]
- relation nokia_srlinux::system::EventHandler event_handler [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state of event handler and event handling instances
other end:
nokia_srlinux::system::EventHandler.parent_system [1]
- relation nokia_srlinux::system::FtpServer ftp_server [0:1]¶
Relation to parent container Peer relation: Top-level container for FTP server configuration and state
other end:
nokia_srlinux::system::FtpServer.parent_system [1]
- relation nokia_srlinux::system::GnmiServer gnmi_server [0:1]¶
Relation to parent container Peer relation: Configures the gNMI server access API
other end:
nokia_srlinux::system::GnmiServer.parent_system [1]
- relation nokia_srlinux::system::GribiServer gribi_server [0:1]¶
Relation to parent container Peer relation: Configures the gRPC Routing Information Base Interface (gRIBI) service
other end:
nokia_srlinux::system::GribiServer.parent_system [1]
- relation nokia_srlinux::system::Information information [0:1]¶
Relation to parent container Peer relation: Top-level container for system information configuration and state
other end:
nokia_srlinux::system::Information.parent_system [1]
- relation nokia_srlinux::system::JsonRpcServer json_rpc_server [0:1]¶
Relation to parent container Peer relation: Configures the JSON RPC access API
other end:
nokia_srlinux::system::JsonRpcServer.parent_system [1]
- relation nokia_srlinux::system::Lacp lacp [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::License license [0:5]¶
Relation to parent container Peer relation: List of licenses configured on the system
- relation nokia_srlinux::system::Lldp lldp [0:1]¶
Relation to parent container Peer relation: Top-level container for LLDP configuration and state data
- relation nokia_srlinux::system::Logging logging [0:1]¶
Relation to parent container Peer relation: System logging provides the interface to syslog services to setup output entities on a selection of log sources.
- relation nokia_srlinux::system::Maintenance maintenance [0:1]¶
Relation to parent container Peer relation: Top-level container for Maintenance Mode configuration
other end:
nokia_srlinux::system::Maintenance.parent_system [1]
- relation nokia_srlinux::system::Management management [0:1]¶
Relation to parent container Peer relation: Enclosing container for options relating to management server
other end:
nokia_srlinux::system::Management.parent_system [1]
- relation nokia_srlinux::system::Mirroring mirroring [0:1]¶
Relation to parent container Peer relation: Top level container for configuration and operational state for mirroring
other end:
nokia_srlinux::system::Mirroring.parent_system [1]
- relation nokia_srlinux::system::Mpls mpls [0:1]¶
Relation to parent container Peer relation: Container for system wide MPLS label management
- relation nokia_srlinux::system::Mtu mtu [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to the system MTU
other end:
nokia_srlinux::system::Mtu.parent_system [1]
- relation nokia_srlinux::system::Multicast multicast [0:1]¶
Relation to parent container Peer relation: system multicast information
other end:
nokia_srlinux::system::Multicast.parent_system [1]
- relation nokia_srlinux::system::Name name [0:1]¶
Relation to parent container Peer relation: Contains configuration and state related to system naming
- relation nokia_srlinux::system::NetworkInstance network_instance [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::NetworkInstance.parent_system [1]
- relation nokia_srlinux::system::Ntp ntp [0:1]¶
Relation to parent container Peer relation: Top-level container for NTP configuration and state
other end:
nokia_srlinux::system::Ntp.parent_system [1]
- relation nokia_srlinux::system::P4rtServer p4rt_server [0:1]¶
Relation to parent container Peer relation: Configures the P4Runtime service
other end:
nokia_srlinux::system::P4rtServer.parent_system [1]
- relation nokia_srlinux::system::PacketLinkQualification packet_link_qualification [0:1]¶
Relation to parent container Peer relation: Top-level container for gNOI Packet Link Qualification profiles
other end:
nokia_srlinux::system::PacketLinkQualification.parent_system [1]
- relation nokia_srlinux::system::Protocols protocols [0:1]¶
Relation to parent container Peer relation: The routing protocols that are supported by the system
other end:
nokia_srlinux::system::Protocols.parent_system [1]
- relation nokia_srlinux::system::RaGuardPolicy ra_guard_policy [0:64]¶
Relation to parent container Peer relation: List containing RA Guard Policy and parameters
other end:
nokia_srlinux::system::RaGuardPolicy.parent_system [1]
- relation nokia_srlinux::system::Sflow sflow [0:1]¶
Relation to parent container Peer relation: Context to configure sFlow Agent parameters and report sFlow state
- relation nokia_srlinux::system::Snmp snmp [0:1]¶
Relation to parent container Peer relation: Top-level container for SNMP configuration and state
- relation nokia_srlinux::system::SshServer ssh_server [0:1]¶
Relation to parent container Peer relation: Top-level container for SSH server configuration and state
other end:
nokia_srlinux::system::SshServer.parent_system [1]
- relation nokia_srlinux::system::Sync sync [0:1]¶
Relation to parent container Peer relation: Context to configure sync parameters and report sessions state
- relation nokia_srlinux::system::Tls tls [0:1]¶
Relation to parent container Peer relation: Top-level container for TLS configuration and state
other end:
nokia_srlinux::system::Tls.parent_system [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupSystemYangContainer
constrainttrue
- entity nokia_srlinux::TransportSecurity¶
Parents:
nokia_srlinux::Base
Enclosing container for transport security Yang definition can be found here: srl_nokia-transport-security.yang:L32
- Rel macsec:
- relation nokia_srlinux::transport_security::Macsec macsec [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::transport_security::Macsec.parent_transport_security [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupTransportSecurityYangContainer
constrainttrue
- entity nokia_srlinux::Tunnel¶
Parents:
nokia_srlinux::Base
This model collects all config and state aspects of the tunnel table in SRLinux. Yang definition can be found here: srl_nokia-tunnel.yang:L32
- Rel vxlan_tunnel:
- relation nokia_srlinux::tunnel::VxlanTunnel vxlan_tunnel [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel::VxlanTunnel.parent_tunnel [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupTunnelYangContainer
constrainttrue
- entity nokia_srlinux::TunnelInterface¶
Parents:
nokia_srlinux::Base
In the case that the interface is logical tunnel interface, the parameters for the tunnel are specified within this subtree. Tunnel interfaces have only a single logical subinterface associated with them. Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L70
- attribute nokia_srlinux::types::srl_nokia_tunnel_interfaces::tunnel_interface_all name¶
The name of the tunnel-interface. Valid options are: vxlan<N>, N=0..255 :rel vxlan_interface: The list of vxlan-interfaces.
- relation nokia_srlinux::tunnel_interface::VxlanInterface vxlan_interface [0:16384]¶
Relation to parent container Peer relation: The list of vxlan-interfaces.
other end:
nokia_srlinux::tunnel_interface::VxlanInterface.parent_tunnel_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::setupTunnelInterfaceYangContainer
constrainttrue
- entity nokia_srlinux::acl::CpmFilter¶
Parents:
nokia_srlinux::Base
Top level container for CPM filters Yang definition can be found here: srl_nokia-acl.yang:L1849
- Rel ipv4_filter:
Top level container for CPM IPv4 filters
- Rel ipv6_filter:
Top level container for CPM IPv6 filters
- Rel mac_filter:
Top level container for CPM MAC filter
- Rel parent_acl:
Relation to parent container
- relation nokia_srlinux::Acl parent_acl [1]¶
Relation to parent container Peer relation: Top level container for CPM filters
other end:
nokia_srlinux::Acl.cpm_filter [0:1]
- relation nokia_srlinux::acl::cpm_filter::Ipv4Filter ipv4_filter [0:1]¶
Relation to parent container Peer relation: Top level container for CPM IPv4 filters
other end:
nokia_srlinux::acl::cpm_filter::Ipv4Filter.parent_cpm_filter [1]
- relation nokia_srlinux::acl::cpm_filter::Ipv6Filter ipv6_filter [0:1]¶
Relation to parent container Peer relation: Top level container for CPM IPv6 filters
other end:
nokia_srlinux::acl::cpm_filter::Ipv6Filter.parent_cpm_filter [1]
- relation nokia_srlinux::acl::cpm_filter::MacFilter mac_filter [0:1]¶
Relation to parent container Peer relation: Top level container for CPM MAC filter
other end:
nokia_srlinux::acl::cpm_filter::MacFilter.parent_cpm_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::setupCpmFilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::Ipv4Filter¶
Parents:
nokia_srlinux::Base
List of IPv4 filter policies Yang definition can be found here: srl_nokia-acl.yang:L1491
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the IPv4 filter policy
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the IPv4 filter policy. :rel entry: List of filter rules. :rel parent_acl: Relation to parent container
- relation nokia_srlinux::Acl parent_acl [1]¶
Relation to parent container Peer relation: List of IPv4 filter policies
other end:
nokia_srlinux::Acl.ipv4_filter [0:*]
- relation nokia_srlinux::acl::ipv4_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::ipv4_filter::Entry.parent_ipv4_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::setupIpv4FilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::Ipv6Filter¶
Parents:
nokia_srlinux::Base
List of IPv6 filter policies Yang definition can be found here: srl_nokia-acl.yang:L1576
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the IPv6 filter policy
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the IPv6 filter policy. :rel entry: List of filter rules. :rel parent_acl: Relation to parent container
- relation nokia_srlinux::Acl parent_acl [1]¶
Relation to parent container Peer relation: List of IPv6 filter policies
other end:
nokia_srlinux::Acl.ipv6_filter [0:*]
- relation nokia_srlinux::acl::ipv6_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::ipv6_filter::Entry.parent_ipv6_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::setupIpv6FilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::MacFilter¶
Parents:
nokia_srlinux::Base
List of MAC ACL policies Yang definition can be found here: srl_nokia-acl.yang:L1802
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the MAC ACL policy
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the MAC ACL policy.
- attribute bool? statistics_per_entry=null¶
Collect statistics for each entry of the ACL The exact set of statistics depend on the subinterface-specific mode
- attribute nokia_srlinux::acl::mac_filter_subinterface_specific_t? subinterface_specific=null¶
Controls the instantiation of the filter when it is applied as an input or output ACL disabled: all subinterfaces on a single linecard that reference the ACL as an input ACL use a shared filter instance, and all subinterfaces on a single linecard that reference the ACL as an output ACL use a shared filter instance input-only: all subinterfaces on a single linecard that reference the ACL as an output ACL use a shared filter instance, but each subinterface that references the ACL as an input ACL uses its own separate instance of the filter output-only: all subinterfaces on a single linecard that reference the ACL as an input ACL use a shared filter instance, but each subinterface that references the ACL as an output ACL uses its own separate instance of the filter input-and-output: each subinterface that references the ACL as either an input ACL or an output ACL uses its own separate instance of the filter :rel entry: List of filter rules. :rel parent_acl: Relation to parent container
- relation nokia_srlinux::Acl parent_acl [1]¶
Relation to parent container Peer relation: List of MAC ACL policies
other end:
nokia_srlinux::Acl.mac_filter [0:*]
- relation nokia_srlinux::acl::mac_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::mac_filter::Entry.parent_mac_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::setupMacFilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::Policers¶
Parents:
nokia_srlinux::Base
Container for policer definitions used by ACL entries Yang definition can be found here: srl_nokia-acl.yang:L378
- Rel parent_acl:
Relation to parent container
- Rel system_cpu_policer:
List of system CPU policer templates. For each policer in this list one or more policer instances are implemented in the XDP-CPM software and these policer instances process the aggregate of terminating traffic received from all linecards.
- relation nokia_srlinux::Acl parent_acl [1]¶
Relation to parent container Peer relation: Container for policer definitions used by ACL entries
other end:
nokia_srlinux::Acl.policers [0:1]
- relation nokia_srlinux::acl::policers::SystemCpuPolicer system_cpu_policer [0:*]¶
Relation to parent container Peer relation: List of system CPU policer templates. For each policer in this list one or more policer instances are implemented in the XDP-CPM software and these policer instances process the aggregate of terminating traffic received from all linecards.
other end:
nokia_srlinux::acl::policers::SystemCpuPolicer.parent_policers [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::setupPolicersYangContainer
constrainttrue
- entity nokia_srlinux::acl::SystemFilter¶
Parents:
nokia_srlinux::Base
Top level container for System filters Yang definition can be found here: srl_nokia-acl.yang:L1895
- Rel ipv4_filter:
Top level container for System IPv4 filters
- Rel ipv6_filter:
Top level container for System IPv6 filters
- Rel parent_acl:
Relation to parent container
- relation nokia_srlinux::Acl parent_acl [1]¶
Relation to parent container Peer relation: Top level container for System filters
other end:
nokia_srlinux::Acl.system_filter [0:1]
- relation nokia_srlinux::acl::system_filter::Ipv4Filter ipv4_filter [0:1]¶
Relation to parent container Peer relation: Top level container for System IPv4 filters
other end:
nokia_srlinux::acl::system_filter::Ipv4Filter.parent_system_filter [1]
- relation nokia_srlinux::acl::system_filter::Ipv6Filter ipv6_filter [0:1]¶
Relation to parent container Peer relation: Top level container for System IPv6 filters
other end:
nokia_srlinux::acl::system_filter::Ipv6Filter.parent_system_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::setupSystemFilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::cpm_filter::Ipv4Filter¶
Parents:
nokia_srlinux::Base
Top level container for CPM IPv4 filters Yang definition can be found here: srl_nokia-acl.yang:L1852
- Rel entry:
List of filter rules.
- Rel parent_cpm_filter:
Relation to parent container
- relation nokia_srlinux::acl::CpmFilter parent_cpm_filter [1]¶
Relation to parent container Peer relation: Top level container for CPM IPv4 filters
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry.parent_ipv4_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::cpm_filter::setupIpv4FilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::cpm_filter::Ipv6Filter¶
Parents:
nokia_srlinux::Base
Top level container for CPM IPv6 filters Yang definition can be found here: srl_nokia-acl.yang:L1858
- Rel entry:
List of filter rules.
- Rel parent_cpm_filter:
Relation to parent container
- relation nokia_srlinux::acl::CpmFilter parent_cpm_filter [1]¶
Relation to parent container Peer relation: Top level container for CPM IPv6 filters
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry.parent_ipv6_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::cpm_filter::setupIpv6FilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::cpm_filter::MacFilter¶
Parents:
nokia_srlinux::Base
Top level container for CPM MAC filter Yang definition can be found here: srl_nokia-acl.yang:L1864
- attribute bool? statistics_per_entry=null¶
Collect the following statistics per entry: the number of packets matching each entry, and the elapsed time since a packet last matched each entry :rel entry: List of filter rules. :rel parent_cpm_filter: Relation to parent container
- relation nokia_srlinux::acl::CpmFilter parent_cpm_filter [1]¶
Relation to parent container Peer relation: Top level container for CPM MAC filter
- relation nokia_srlinux::acl::cpm_filter::mac_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::Entry.parent_mac_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::cpm_filter::setupMacFilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1399
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the CPM filter entry. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_ipv4_filter: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::Ipv4Filter parent_ipv4_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::cpm_filter::Ipv4Filter.entry [0:*]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the CPM filter entry.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the CPM filter entry. Yang definition can be found here: srl_nokia-acl.yang:L679
- attribute bool? collect_stats=null¶
Collect statistics for each entry of the ACL. If this is set to false no hardware resources are allocated to collecting statistics for this ACL entry. :rel accept: Accept matching packets and forward them towards their normal destination :rel drop: Drop matching packets. Dropped IP packets do not result in sending ICMP messages back to the source :rel parent_entry: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the CPM filter entry.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-acl.yang:L862
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute bool? first_fragment=null¶
Match the first fragment of an IPv4 datagram A packet matches the true condition if the IPv4 header indicates that the fragment-offset is zero and and the more-fragments bit is 1. It is not valid to configure this leaf without configuring a match value for the fragment leaf.
- attribute bool? fragment=null¶
Match an IPv4 fragment A packet matches the true condition if the IPv4 header indicates that the fragment-offset is zero and and the more-fragments bit is 1 or if the IPv4 header indicates that the fragment-offset is greater than 0. A packet matches the false condition if it is unfragmented.
- attribute string? network_instance=null¶
Reference to a configured network-instance
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match_protocol_t? protocol=null¶
An IPv4 packet matches this condition if its IP protocol type field matches the specified value
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match_tcp_flags_t? tcp_flags=null¶
A logical expression using the &, | and ! logical operators and the TCP flag names: rst, syn and ack. :rel destination_ip: Packet matching criteria based on destination IPv4 address :rel destination_port: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. :rel icmp: A packet matches this condition if its ICMP type and code matches one of the specified combinations The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly. :rel parent_entry: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv4 address :rel source_port: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationIp destination_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv4 address
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationIp.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationPort destination_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationPort.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::Icmp icmp [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::Icmp.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourceIp.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourcePort source_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourcePort.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets and forward them towards their normal destination Yang definition can be found here: srl_nokia-acl.yang:L684
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry For IP packets matched by an IP filter entry the log entry contains the following information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: accept - IP protocol - packet-length - source IP address - source L4 port number (TCP/UDP packets) - destination IP address - destination L4 port number (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) For Ethernet packets matched by a MAC filter entry the log entry contains the folllowing information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: drop - source MAC address - destination MAC address - list of VLAN IDs, from outermost (including the subinterface-defining VLAN tag, if any) to innermost - Ethertype after the last 802.1Q VLAN tag (if any) :rel parent_action: Relation to parent container :rel rate_limit: Rate-limit accepted packets
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action.accept [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::accept::RateLimit rate_limit [0:1]¶
Relation to parent container Peer relation: Rate-limit accepted packets
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::accept::RateLimit.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L750
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::accept::RateLimit¶
Parents:
nokia_srlinux::Base
Rate-limit accepted packets Yang definition can be found here: srl_nokia-acl.yang:L688
- attribute string? policer=null¶
Reference to a policer
- attribute string? system_cpu_policer=null¶
Reference to a system-cpu-policer. :rel parent_accept: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Accept parent_accept [1]¶
Relation to parent container Peer relation: Rate-limit accepted packets
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::Accept.rate_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on destination IPv4 address Yang definition can be found here: srl_nokia-acl.yang:L866
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Match a packet if its destination IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? mask=null¶
Match a packet if its destination IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its destination IP address is within the specified IPv4 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv4 address
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match.destination_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationPort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1095
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::destination_port_value_t? value=null¶
A destination port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match.destination_port [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::destination_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::Icmp¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L925
- attribute yang::types::uint8[]? code=null¶
Match if the ICMP code value is any value in the list Requires ICMP type to be specified because codes are type dependent.
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::icmp_type_t? type=null¶
Match a single ICMP type value. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match.icmp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv4 address Yang definition can be found here: srl_nokia-acl.yang:L957
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Match a packet if its source IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? mask=null¶
Match a packet if its source IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv4 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourcePort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1159
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port_value_t? value=null¶
A source port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::Match.source_port [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port::Range.parent_source_port [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::destination_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1124
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::destination_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::destination_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_destination_port: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationPort parent_destination_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::DestinationPort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1188
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_source_port: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourcePort parent_source_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::SourcePort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1635
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the CPM filter entry. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_ipv6_filter: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::Ipv6Filter parent_ipv6_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::cpm_filter::Ipv6Filter.entry [0:*]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the CPM filter entry.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the CPM filter entry. Yang definition can be found here: srl_nokia-acl.yang:L679
- attribute bool? collect_stats=null¶
Collect statistics for each entry of the ACL. If this is set to false no hardware resources are allocated to collecting statistics for this ACL entry. :rel accept: Accept matching packets and forward them towards their normal destination :rel drop: Drop matching packets. Dropped IP packets do not result in sending ICMP messages back to the source :rel parent_entry: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the CPM filter entry.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-acl.yang:L996
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute string? network_instance=null¶
Reference to a configured network-instance
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match_next_header_t? next_header=null¶
An IPv6 packet matches this condition if its first next-header field (in the IPv6 fixed header) contains the specified value
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match_tcp_flags_t? tcp_flags=null¶
A logical expression using the &, | and ! logical operators and the TCP flag names: rst, syn and ack. :rel destination_ip: Packet matching criteria based on destination IPv6 address :rel destination_port: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. :rel icmp6: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly. :rel parent_entry: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv6 address :rel source_port: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationIp destination_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv6 address
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationIp.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationPort destination_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationPort.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::Icmp6 icmp6 [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::Icmp6.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv6 address
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourceIp.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourcePort source_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourcePort.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets and forward them towards their normal destination Yang definition can be found here: srl_nokia-acl.yang:L684
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry For IP packets matched by an IP filter entry the log entry contains the following information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: accept - IP protocol - packet-length - source IP address - source L4 port number (TCP/UDP packets) - destination IP address - destination L4 port number (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) For Ethernet packets matched by a MAC filter entry the log entry contains the folllowing information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: drop - source MAC address - destination MAC address - list of VLAN IDs, from outermost (including the subinterface-defining VLAN tag, if any) to innermost - Ethertype after the last 802.1Q VLAN tag (if any) :rel parent_action: Relation to parent container :rel rate_limit: Rate-limit accepted packets
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action.accept [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::accept::RateLimit rate_limit [0:1]¶
Relation to parent container Peer relation: Rate-limit accepted packets
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::accept::RateLimit.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L750
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::accept::RateLimit¶
Parents:
nokia_srlinux::Base
Rate-limit accepted packets Yang definition can be found here: srl_nokia-acl.yang:L688
- attribute string? policer=null¶
Reference to a policer
- attribute string? system_cpu_policer=null¶
Reference to a system-cpu-policer. :rel parent_accept: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Accept parent_accept [1]¶
Relation to parent container Peer relation: Rate-limit accepted packets
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::Accept.rate_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on destination IPv6 address Yang definition can be found here: srl_nokia-acl.yang:L1000
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? address=null¶
Match a packet if its destination IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? mask=null¶
Match a packet if its destination IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix? prefix=null¶
Match a packet if its destination IP address is within the specified IPv6 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv6 address
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match.destination_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationPort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1095
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::destination_port_value_t? value=null¶
A destination port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match.destination_port [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::destination_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::Icmp6¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1031
- attribute yang::types::uint8[]? code=null¶
Match if the ICMPv6 code value is any value in the list Requires ICMPv6 type to be specified because codes are type dependent.
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::icmp6_type_t? type=null¶
Match a single ICMPv6 type value :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match.icmp6 [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv6 address Yang definition can be found here: srl_nokia-acl.yang:L1063
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? address=null¶
Match a packet if its source IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? mask=null¶
Match a packet if its source IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv6 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv6 address
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourcePort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1159
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port_value_t? value=null¶
A source port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::Match.source_port [0:1]
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port::Range.parent_source_port [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::destination_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1124
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::destination_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::destination_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_destination_port: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationPort parent_destination_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::DestinationPort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1188
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_source_port: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourcePort parent_source_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::SourcePort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1773
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::cpm_filter::mac_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the CPM filter entry. :rel match: Container for the conditions that determine whether an Ethernet frame matches this entry :rel parent_mac_filter: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::MacFilter parent_mac_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::cpm_filter::MacFilter.entry [0:*]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the CPM filter entry.
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether an Ethernet frame matches this entry
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the CPM filter entry. Yang definition can be found here: srl_nokia-acl.yang:L679
- attribute bool? collect_stats=null¶
Collect statistics for each entry of the ACL. If this is set to false no hardware resources are allocated to collecting statistics for this ACL entry. :rel accept: Accept matching packets and forward them towards their normal destination :rel drop: Drop matching packets. Dropped IP packets do not result in sending ICMP messages back to the source :rel parent_entry: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the CPM filter entry.
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether an Ethernet frame matches this entry Yang definition can be found here: srl_nokia-acl.yang:L1239
- attribute nokia_srlinux::acl::cpm_filter::mac_filter::entry::match_ethertype_t? ethertype=null¶
An Ethernet frame matches this condition if its ethertype value (after 802.1Q VLAN tags) matches the specified value :rel destination_mac: Ethernet frame matching criteria based on destination MAC address :rel parent_entry: Relation to parent container :rel source_mac: Ethernet frame matching criteria based on source MAC address :rel vlan: Ethernet frame matching criteria based on VLAN tags
- relation nokia_srlinux::acl::cpm_filter::mac_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether an Ethernet frame matches this entry
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::DestinationMac destination_mac [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on destination MAC address
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::DestinationMac.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::SourceMac source_mac [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on source MAC address
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::SourceMac.parent_match [1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::Vlan vlan [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on VLAN tags
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::Vlan.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets and forward them towards their normal destination Yang definition can be found here: srl_nokia-acl.yang:L684
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry For IP packets matched by an IP filter entry the log entry contains the following information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: accept - IP protocol - packet-length - source IP address - source L4 port number (TCP/UDP packets) - destination IP address - destination L4 port number (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) For Ethernet packets matched by a MAC filter entry the log entry contains the folllowing information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: drop - source MAC address - destination MAC address - list of VLAN IDs, from outermost (including the subinterface-defining VLAN tag, if any) to innermost - Ethertype after the last 802.1Q VLAN tag (if any) :rel parent_action: Relation to parent container :rel rate_limit: Rate-limit accepted packets
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action.accept [0:1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::accept::RateLimit rate_limit [0:1]¶
Relation to parent container Peer relation: Rate-limit accepted packets
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::accept::RateLimit.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L750
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::accept::RateLimit¶
Parents:
nokia_srlinux::Base
Rate-limit accepted packets Yang definition can be found here: srl_nokia-acl.yang:L688
- attribute string? policer=null¶
Reference to a policer
- attribute string? system_cpu_policer=null¶
Reference to a system-cpu-policer. :rel parent_accept: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Accept parent_accept [1]¶
Relation to parent container Peer relation: Rate-limit accepted packets
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::Accept.rate_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::DestinationMac¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on destination MAC address Yang definition can be found here: srl_nokia-acl.yang:L1243
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? address=null¶
Match an Ethernet frame if its destination MAC address logically anded with the mask equals this MAC address.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? mask=null¶
Match an Ethernet frame if its destination MAC address logically anded with the mask equals the configured MAC address. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on destination MAC address
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match.destination_mac [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::SourceMac¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on source MAC address Yang definition can be found here: srl_nokia-acl.yang:L1268
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? address=null¶
Match an Ethernet frame if its source MAC address logically anded with the mask equals this MAC address.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? mask=null¶
Match an Ethernet frame if its source MAC address logically anded with the mask equals the configured MAC address. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on source MAC address
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match.source_mac [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::Vlan¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on VLAN tags Yang definition can be found here: srl_nokia-acl.yang:L1288
- Rel outermost_vlan_id:
Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed.
- Rel parent_match:
Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on VLAN tags
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::Match.vlan [0:1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::OutermostVlanId outermost_vlan_id [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed.
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::OutermostVlanId.parent_vlan [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::OutermostVlanId¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed. Yang definition can be found here: srl_nokia-acl.yang:L1291
- attribute bool? none=null¶
When configured, only untagged frames are matched.
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type? value=null¶
A VLAN ID number A value of zero is used to match priority-tagged 802.1Q frames. :rel parent_vlan: Relation to parent container :rel range: Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values.
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::Vlan parent_vlan [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed.
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::Vlan.outermost_vlan_id [0:1]
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::outermost_vlan_id::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::outermost_vlan_id::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values. Yang definition can be found here: srl_nokia-acl.yang:L1314
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type? start=null¶
The starting VLAN ID to include in the range
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type? x_end=null¶
The ending VLAN ID to include in the range :rel parent_outermost_vlan_id: Relation to parent container
- relation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::OutermostVlanId parent_outermost_vlan_id [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values.
other end:
nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::OutermostVlanId.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1363
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::ipv4_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the filter entry. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_ipv4_filter: Relation to parent container
- relation nokia_srlinux::acl::Ipv4Filter parent_ipv4_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::Ipv4Filter.entry [0:*]
- relation nokia_srlinux::acl::ipv4_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the filter entry.
other end:
nokia_srlinux::acl::ipv4_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::ipv4_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::ipv4_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::ipv4_filter::setupEntryYangContainer
constrainttrue
- entity nokia_srlinux::acl::ipv4_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the filter entry. Yang definition can be found here: srl_nokia-acl.yang:L522
- attribute bool? collect_stats=null¶
Collect statistics for each entry of the ACL. If this is set to false no hardware resources are allocated to collecting statistics for this ACL entry. :rel accept: Accept matching packets and forward them towards their normal destination :rel drop: Drop matching packets. Dropped IP packets do not result in sending ICMP messages back to the source :rel parent_entry: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the filter entry.
other end:
nokia_srlinux::acl::ipv4_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::ipv4_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::ipv4_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::ipv4_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::ipv4_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::ipv4_filter::entry::setupActionYangContainer
constrainttrue
- entity nokia_srlinux::acl::ipv4_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-acl.yang:L862
- attribute nokia_srlinux::acl::ipv4_filter::entry::match_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute bool? first_fragment=null¶
Match the first fragment of an IPv4 datagram A packet matches the true condition if the IPv4 header indicates that the fragment-offset is zero and and the more-fragments bit is 1. It is not valid to configure this leaf without configuring a match value for the fragment leaf.
- attribute bool? fragment=null¶
Match an IPv4 fragment A packet matches the true condition if the IPv4 header indicates that the fragment-offset is zero and and the more-fragments bit is 1 or if the IPv4 header indicates that the fragment-offset is greater than 0. A packet matches the false condition if it is unfragmented.
- attribute nokia_srlinux::acl::ipv4_filter::entry::match_protocol_t? protocol=null¶
An IPv4 packet matches this condition if its IP protocol type field matches the specified value
- attribute nokia_srlinux::acl::ipv4_filter::entry::match_tcp_flags_t? tcp_flags=null¶
A logical expression using the &, | and ! logical operators and the TCP flag names: rst, syn and ack. :rel destination_ip: Packet matching criteria based on destination IPv4 address :rel destination_port: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. :rel icmp: A packet matches this condition if its ICMP type and code matches one of the specified combinations The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly. :rel parent_entry: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv4 address :rel source_port: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
- relation nokia_srlinux::acl::ipv4_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::ipv4_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::DestinationIp destination_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv4 address
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::DestinationIp.parent_match [1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::DestinationPort destination_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::DestinationPort.parent_match [1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::Icmp icmp [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::Icmp.parent_match [1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::SourceIp.parent_match [1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::SourcePort source_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::SourcePort.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::ipv4_filter::entry::setupMatchYangContainer
constrainttrue
- entity nokia_srlinux::acl::ipv4_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets and forward them towards their normal destination Yang definition can be found here: srl_nokia-acl.yang:L526
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry For IP packets matched by an IP filter entry the log entry contains the following information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: accept - IP protocol - packet-length - source IP address - source L4 port number (TCP/UDP packets) - destination IP address - destination L4 port number (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) For Ethernet packets matched by a MAC filter entry the log entry contains the folllowing information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: drop - source MAC address - destination MAC address - list of VLAN IDs, from outermost (including the subinterface-defining VLAN tag, if any) to innermost - Ethertype after the last 802.1Q VLAN tag (if any)
- attribute nokia_srlinux::types::srl_nokia_common::classify_profile? profile=null¶
The QoS profile to which the packet is mapped :rel forward: Enable the next-hop context :rel parent_action: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::ipv4_filter::entry::Action.accept [0:1]
- relation nokia_srlinux::acl::ipv4_filter::entry::action::accept::Forward forward [0:1]¶
Relation to parent container Peer relation: Enable the next-hop context
other end:
nokia_srlinux::acl::ipv4_filter::entry::action::accept::Forward.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L627
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::ipv4_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::action::accept::Forward¶
Parents:
nokia_srlinux::Base
Enable the next-hop context Yang definition can be found here: srl_nokia-acl.yang:L607
- Rel next_hop:
- Rel parent_accept:
Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::action::Accept parent_accept [1]¶
Relation to parent container Peer relation: Enable the next-hop context
other end:
nokia_srlinux::acl::ipv4_filter::entry::action::Accept.forward [0:1]
- relation nokia_srlinux::acl::ipv4_filter::entry::action::accept::forward::NextHop next_hop [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::acl::ipv4_filter::entry::action::accept::forward::NextHop.parent_forward [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::action::accept::forward::NextHop¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-acl.yang:L612
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
IPv4 address of next hop to forward matching packets.
- attribute bool? indirect=null¶
Allow next hop to be indirectly reachable. :rel parent_forward: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::action::accept::Forward parent_forward [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::acl::ipv4_filter::entry::action::accept::Forward.next_hop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::DestinationIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on destination IPv4 address Yang definition can be found here: srl_nokia-acl.yang:L866
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Match a packet if its destination IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? mask=null¶
Match a packet if its destination IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its destination IP address is within the specified IPv4 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv4 address
other end:
nokia_srlinux::acl::ipv4_filter::entry::Match.destination_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::DestinationPort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1095
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::destination_port_value_t? value=null¶
A destination port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv4_filter::entry::Match.destination_port [0:1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::destination_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::destination_port::Range.parent_destination_port [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::Icmp¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L925
- attribute yang::types::uint8[]? code=null¶
Match if the ICMP code value is any value in the list Requires ICMP type to be specified because codes are type dependent.
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::icmp_type_t? type=null¶
Match a single ICMP type value. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv4_filter::entry::Match.icmp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv4 address Yang definition can be found here: srl_nokia-acl.yang:L957
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Match a packet if its source IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? mask=null¶
Match a packet if its source IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv4 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::acl::ipv4_filter::entry::Match.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::SourcePort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1159
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::source_port_value_t? value=null¶
A source port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv4_filter::entry::Match.source_port [0:1]
- relation nokia_srlinux::acl::ipv4_filter::entry::match::source_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::source_port::Range.parent_source_port [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::destination_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1124
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::destination_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::destination_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_destination_port: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::match::DestinationPort parent_destination_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::DestinationPort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv4_filter::entry::match::source_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1188
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::source_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::ipv4_filter::entry::match::source_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_source_port: Relation to parent container
- relation nokia_srlinux::acl::ipv4_filter::entry::match::SourcePort parent_source_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv4_filter::entry::match::SourcePort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1552
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::ipv6_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries. :rel action: Container for the actions to be applied to packets matching the filter entry. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_ipv6_filter: Relation to parent container
- relation nokia_srlinux::acl::Ipv6Filter parent_ipv6_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::Ipv6Filter.entry [0:*]
- relation nokia_srlinux::acl::ipv6_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the filter entry.
other end:
nokia_srlinux::acl::ipv6_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::ipv6_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::ipv6_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::ipv6_filter::setupEntryYangContainer
constrainttrue
- entity nokia_srlinux::acl::ipv6_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the filter entry. Yang definition can be found here: srl_nokia-acl.yang:L522
- attribute bool? collect_stats=null¶
Collect statistics for each entry of the ACL. If this is set to false no hardware resources are allocated to collecting statistics for this ACL entry. :rel accept: Accept matching packets and forward them towards their normal destination :rel drop: Drop matching packets. Dropped IP packets do not result in sending ICMP messages back to the source :rel parent_entry: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the filter entry.
other end:
nokia_srlinux::acl::ipv6_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::ipv6_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::ipv6_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::ipv6_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::ipv6_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::ipv6_filter::entry::setupActionYangContainer
constrainttrue
- entity nokia_srlinux::acl::ipv6_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-acl.yang:L996
- attribute nokia_srlinux::acl::ipv6_filter::entry::match_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute nokia_srlinux::acl::ipv6_filter::entry::match_next_header_t? next_header=null¶
An IPv6 packet matches this condition if its first next-header field (in the IPv6 fixed header) contains the specified value
- attribute nokia_srlinux::acl::ipv6_filter::entry::match_tcp_flags_t? tcp_flags=null¶
A logical expression using the &, | and ! logical operators and the TCP flag names: rst, syn and ack. :rel destination_ip: Packet matching criteria based on destination IPv6 address :rel destination_port: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. :rel icmp6: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly. :rel parent_entry: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv6 address :rel source_port: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
- relation nokia_srlinux::acl::ipv6_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::ipv6_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::DestinationIp destination_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv6 address
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::DestinationIp.parent_match [1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::DestinationPort destination_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::DestinationPort.parent_match [1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::Icmp6 icmp6 [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::Icmp6.parent_match [1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv6 address
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::SourceIp.parent_match [1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::SourcePort source_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::SourcePort.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::ipv6_filter::entry::setupMatchYangContainer
constrainttrue
- entity nokia_srlinux::acl::ipv6_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets and forward them towards their normal destination Yang definition can be found here: srl_nokia-acl.yang:L526
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry For IP packets matched by an IP filter entry the log entry contains the following information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: accept - IP protocol - packet-length - source IP address - source L4 port number (TCP/UDP packets) - destination IP address - destination L4 port number (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) For Ethernet packets matched by a MAC filter entry the log entry contains the folllowing information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: drop - source MAC address - destination MAC address - list of VLAN IDs, from outermost (including the subinterface-defining VLAN tag, if any) to innermost - Ethertype after the last 802.1Q VLAN tag (if any)
- attribute nokia_srlinux::types::srl_nokia_common::classify_profile? profile=null¶
The QoS profile to which the packet is mapped :rel forward: Enable the next-hop context :rel parent_action: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::ipv6_filter::entry::Action.accept [0:1]
- relation nokia_srlinux::acl::ipv6_filter::entry::action::accept::Forward forward [0:1]¶
Relation to parent container Peer relation: Enable the next-hop context
other end:
nokia_srlinux::acl::ipv6_filter::entry::action::accept::Forward.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L627
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::ipv6_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::action::accept::Forward¶
Parents:
nokia_srlinux::Base
Enable the next-hop context Yang definition can be found here: srl_nokia-acl.yang:L607
- Rel next_hop:
- Rel parent_accept:
Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::action::Accept parent_accept [1]¶
Relation to parent container Peer relation: Enable the next-hop context
other end:
nokia_srlinux::acl::ipv6_filter::entry::action::Accept.forward [0:1]
- relation nokia_srlinux::acl::ipv6_filter::entry::action::accept::forward::NextHop next_hop [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::acl::ipv6_filter::entry::action::accept::forward::NextHop.parent_forward [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::action::accept::forward::NextHop¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-acl.yang:L612
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
IPv4 address of next hop to forward matching packets.
- attribute bool? indirect=null¶
Allow next hop to be indirectly reachable. :rel parent_forward: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::action::accept::Forward parent_forward [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::acl::ipv6_filter::entry::action::accept::Forward.next_hop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::DestinationIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on destination IPv6 address Yang definition can be found here: srl_nokia-acl.yang:L1000
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? address=null¶
Match a packet if its destination IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? mask=null¶
Match a packet if its destination IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix? prefix=null¶
Match a packet if its destination IP address is within the specified IPv6 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv6 address
other end:
nokia_srlinux::acl::ipv6_filter::entry::Match.destination_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::DestinationPort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1095
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::destination_port_value_t? value=null¶
A destination port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv6_filter::entry::Match.destination_port [0:1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::destination_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::destination_port::Range.parent_destination_port [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::Icmp6¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1031
- attribute yang::types::uint8[]? code=null¶
Match if the ICMPv6 code value is any value in the list Requires ICMPv6 type to be specified because codes are type dependent.
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::icmp6_type_t? type=null¶
Match a single ICMPv6 type value :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv6_filter::entry::Match.icmp6 [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv6 address Yang definition can be found here: srl_nokia-acl.yang:L1063
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? address=null¶
Match a packet if its source IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? mask=null¶
Match a packet if its source IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv6 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv6 address
other end:
nokia_srlinux::acl::ipv6_filter::entry::Match.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::SourcePort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1159
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::source_port_value_t? value=null¶
A source port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::ipv6_filter::entry::Match.source_port [0:1]
- relation nokia_srlinux::acl::ipv6_filter::entry::match::source_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::source_port::Range.parent_source_port [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::destination_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1124
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::destination_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::destination_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_destination_port: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::match::DestinationPort parent_destination_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::DestinationPort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::ipv6_filter::entry::match::source_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1188
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::source_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::ipv6_filter::entry::match::source_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_source_port: Relation to parent container
- relation nokia_srlinux::acl::ipv6_filter::entry::match::SourcePort parent_source_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::ipv6_filter::entry::match::SourcePort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1738
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::mac_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the filter entry. :rel match: Container for the conditions that determine whether an Ethernet frame matches this entry :rel parent_mac_filter: Relation to parent container
- relation nokia_srlinux::acl::MacFilter parent_mac_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::MacFilter.entry [0:*]
- relation nokia_srlinux::acl::mac_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the filter entry.
other end:
nokia_srlinux::acl::mac_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::mac_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether an Ethernet frame matches this entry
other end:
nokia_srlinux::acl::mac_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::mac_filter::setupEntryYangContainer
constrainttrue
- entity nokia_srlinux::acl::mac_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the filter entry. Yang definition can be found here: srl_nokia-acl.yang:L522
- attribute bool? collect_stats=null¶
Collect statistics for each entry of the ACL. If this is set to false no hardware resources are allocated to collecting statistics for this ACL entry. :rel accept: Accept matching packets and forward them towards their normal destination :rel drop: Drop matching packets. Dropped IP packets do not result in sending ICMP messages back to the source :rel parent_entry: Relation to parent container
- relation nokia_srlinux::acl::mac_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the filter entry.
other end:
nokia_srlinux::acl::mac_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::mac_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::mac_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::mac_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::mac_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::mac_filter::entry::setupActionYangContainer
constrainttrue
- entity nokia_srlinux::acl::mac_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether an Ethernet frame matches this entry Yang definition can be found here: srl_nokia-acl.yang:L1239
- attribute nokia_srlinux::acl::mac_filter::entry::match_ethertype_t? ethertype=null¶
An Ethernet frame matches this condition if its ethertype value (after 802.1Q VLAN tags) matches the specified value :rel destination_mac: Ethernet frame matching criteria based on destination MAC address :rel parent_entry: Relation to parent container :rel source_mac: Ethernet frame matching criteria based on source MAC address :rel vlan: Ethernet frame matching criteria based on VLAN tags
- relation nokia_srlinux::acl::mac_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether an Ethernet frame matches this entry
other end:
nokia_srlinux::acl::mac_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::mac_filter::entry::match::DestinationMac destination_mac [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on destination MAC address
other end:
nokia_srlinux::acl::mac_filter::entry::match::DestinationMac.parent_match [1]
- relation nokia_srlinux::acl::mac_filter::entry::match::SourceMac source_mac [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on source MAC address
other end:
nokia_srlinux::acl::mac_filter::entry::match::SourceMac.parent_match [1]
- relation nokia_srlinux::acl::mac_filter::entry::match::Vlan vlan [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on VLAN tags
other end:
nokia_srlinux::acl::mac_filter::entry::match::Vlan.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::mac_filter::entry::setupMatchYangContainer
constrainttrue
- entity nokia_srlinux::acl::mac_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets and forward them towards their normal destination Yang definition can be found here: srl_nokia-acl.yang:L526
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry For IP packets matched by an IP filter entry the log entry contains the following information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: accept - IP protocol - packet-length - source IP address - source L4 port number (TCP/UDP packets) - destination IP address - destination L4 port number (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) For Ethernet packets matched by a MAC filter entry the log entry contains the folllowing information: - timestamp - filter name - filter entry sequence-id - incoming subinterface name - action: drop - source MAC address - destination MAC address - list of VLAN IDs, from outermost (including the subinterface-defining VLAN tag, if any) to innermost - Ethertype after the last 802.1Q VLAN tag (if any)
- attribute nokia_srlinux::types::srl_nokia_common::classify_profile? profile=null¶
The QoS profile to which the packet is mapped :rel forward: Enable the next-hop context :rel parent_action: Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets and forward them towards their normal destination
other end:
nokia_srlinux::acl::mac_filter::entry::Action.accept [0:1]
- relation nokia_srlinux::acl::mac_filter::entry::action::accept::Forward forward [0:1]¶
Relation to parent container Peer relation: Enable the next-hop context
other end:
nokia_srlinux::acl::mac_filter::entry::action::accept::Forward.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L627
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets.
Dropped IP packets do not result in sending ICMP messages back to the source
other end:
nokia_srlinux::acl::mac_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::action::accept::Forward¶
Parents:
nokia_srlinux::Base
Enable the next-hop context Yang definition can be found here: srl_nokia-acl.yang:L607
- Rel next_hop:
- Rel parent_accept:
Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::action::Accept parent_accept [1]¶
Relation to parent container Peer relation: Enable the next-hop context
other end:
nokia_srlinux::acl::mac_filter::entry::action::Accept.forward [0:1]
- relation nokia_srlinux::acl::mac_filter::entry::action::accept::forward::NextHop next_hop [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::acl::mac_filter::entry::action::accept::forward::NextHop.parent_forward [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::action::accept::forward::NextHop¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-acl.yang:L612
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
IPv4 address of next hop to forward matching packets.
- attribute bool? indirect=null¶
Allow next hop to be indirectly reachable. :rel parent_forward: Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::action::accept::Forward parent_forward [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::acl::mac_filter::entry::action::accept::Forward.next_hop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::match::DestinationMac¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on destination MAC address Yang definition can be found here: srl_nokia-acl.yang:L1243
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? address=null¶
Match an Ethernet frame if its destination MAC address logically anded with the mask equals this MAC address.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? mask=null¶
Match an Ethernet frame if its destination MAC address logically anded with the mask equals the configured MAC address. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on destination MAC address
other end:
nokia_srlinux::acl::mac_filter::entry::Match.destination_mac [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::match::SourceMac¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on source MAC address Yang definition can be found here: srl_nokia-acl.yang:L1268
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? address=null¶
Match an Ethernet frame if its source MAC address logically anded with the mask equals this MAC address.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? mask=null¶
Match an Ethernet frame if its source MAC address logically anded with the mask equals the configured MAC address. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on source MAC address
other end:
nokia_srlinux::acl::mac_filter::entry::Match.source_mac [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::match::Vlan¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on VLAN tags Yang definition can be found here: srl_nokia-acl.yang:L1288
- Rel outermost_vlan_id:
Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed.
- Rel parent_match:
Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on VLAN tags
other end:
nokia_srlinux::acl::mac_filter::entry::Match.vlan [0:1]
- relation nokia_srlinux::acl::mac_filter::entry::match::vlan::OutermostVlanId outermost_vlan_id [0:1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed.
other end:
nokia_srlinux::acl::mac_filter::entry::match::vlan::OutermostVlanId.parent_vlan [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::match::vlan::OutermostVlanId¶
Parents:
nokia_srlinux::Base
Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed. Yang definition can be found here: srl_nokia-acl.yang:L1291
- attribute bool? none=null¶
When configured, only untagged frames are matched.
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type? value=null¶
A VLAN ID number A value of zero is used to match priority-tagged 802.1Q frames. :rel parent_vlan: Relation to parent container :rel range: Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values.
- relation nokia_srlinux::acl::mac_filter::entry::match::Vlan parent_vlan [1]¶
Relation to parent container Peer relation: Ethernet frame matching criteria based on the outermost VLAN ID found before the subinterface-defining VLAN tag (if any) is removed.
other end:
nokia_srlinux::acl::mac_filter::entry::match::Vlan.outermost_vlan_id [0:1]
- relation nokia_srlinux::acl::mac_filter::entry::match::vlan::outermost_vlan_id::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::mac_filter::entry::match::vlan::outermost_vlan_id::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values. Yang definition can be found here: srl_nokia-acl.yang:L1314
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type? start=null¶
The starting VLAN ID to include in the range
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::vlan_id_type? x_end=null¶
The ending VLAN ID to include in the range :rel parent_outermost_vlan_id: Relation to parent container
- relation nokia_srlinux::acl::mac_filter::entry::match::vlan::OutermostVlanId parent_outermost_vlan_id [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of VLAN IDs. Matched values include the start and end values.
other end:
nokia_srlinux::acl::mac_filter::entry::match::vlan::OutermostVlanId.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::policers::SystemCpuPolicer¶
Parents:
nokia_srlinux::Base
List of system CPU policer templates. For each policer in this list one or more policer instances are implemented in the XDP-CPM software and these policer instances process the aggregate of terminating traffic received from all linecards. Yang definition can be found here: srl_nokia-acl.yang:L381
- attribute bool? entry_specific=null¶
If set to false, only one policer instance is created from this template and it is shared by all entries of all cpm-filter ACLs that refer to this policer. If set to true, multiple policer instances are created from this template, one for each cpm-filter entry that refers to the policer template.
- attribute nokia_srlinux::acl::policers::system_cpu_policer_max_packet_burst_t? max_packet_burst=null¶
The maximum depth of the policer bucket in number of packets
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
User-defined name of the policer
- attribute nokia_srlinux::acl::policers::system_cpu_policer_peak_packet_rate_t? peak_packet_rate=null¶
The maximum number of packets per second (bucket empty/fill rate) :rel parent_policers: Relation to parent container
- relation nokia_srlinux::acl::Policers parent_policers [1]¶
Relation to parent container Peer relation: List of system CPU policer templates. For each policer in this list one or more policer instances are implemented in the XDP-CPM software and these policer instances process the aggregate of terminating traffic received from all linecards.
other end:
nokia_srlinux::acl::Policers.system_cpu_policer [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::policers::setupSystemCpuPolicerYangContainer
constrainttrue
- entity nokia_srlinux::acl::system_filter::Ipv4Filter¶
Parents:
nokia_srlinux::Base
Top level container for System IPv4 filters Yang definition can be found here: srl_nokia-acl.yang:L1899
- Rel entry:
List of filter rules.
- Rel parent_system_filter:
Relation to parent container
- relation nokia_srlinux::acl::SystemFilter parent_system_filter [1]¶
Relation to parent container Peer relation: Top level container for System IPv4 filters
other end:
nokia_srlinux::acl::SystemFilter.ipv4_filter [0:1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::Entry.parent_ipv4_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::system_filter::setupIpv4FilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::system_filter::Ipv6Filter¶
Parents:
nokia_srlinux::Base
Top level container for System IPv6 filters Yang definition can be found here: srl_nokia-acl.yang:L1905
- Rel entry:
List of filter rules.
- Rel parent_system_filter:
Relation to parent container
- relation nokia_srlinux::acl::SystemFilter parent_system_filter [1]¶
Relation to parent container Peer relation: Top level container for System IPv6 filters
other end:
nokia_srlinux::acl::SystemFilter.ipv6_filter [0:1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::Entry entry [0:*]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::Entry.parent_ipv6_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::acl::system_filter::setupIpv6FilterYangContainer
constrainttrue
- entity nokia_srlinux::acl::system_filter::ipv4_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1462
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry_sequence_id_t sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the System filter entry. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_ipv4_filter: Relation to parent container
- relation nokia_srlinux::acl::system_filter::Ipv4Filter parent_ipv4_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::system_filter::Ipv4Filter.entry [0:*]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the System filter entry.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the System filter entry. Yang definition can be found here: srl_nokia-acl.yang:L822
- Rel accept:
Accept matching packets
- Rel drop:
Drop matching packets without sending any ICMP messages back to the source
- Rel parent_entry:
Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the System filter entry.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets without sending any ICMP messages back to the source
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-acl.yang:L862
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute bool? first_fragment=null¶
Match the first fragment of an IPv4 datagram A packet matches the true condition if the IPv4 header indicates that the fragment-offset is zero and and the more-fragments bit is 1. It is not valid to configure this leaf without configuring a match value for the fragment leaf.
- attribute bool? fragment=null¶
Match an IPv4 fragment A packet matches the true condition if the IPv4 header indicates that the fragment-offset is zero and and the more-fragments bit is 1 or if the IPv4 header indicates that the fragment-offset is greater than 0. A packet matches the false condition if it is unfragmented.
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match_protocol_t? protocol=null¶
An IPv4 packet matches this condition if its IP protocol type field matches the specified value
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match_tcp_flags_t? tcp_flags=null¶
A logical expression using the &, | and ! logical operators and the TCP flag names: rst, syn and ack. :rel destination_ip: Packet matching criteria based on destination IPv4 address :rel destination_port: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. :rel icmp: A packet matches this condition if its ICMP type and code matches one of the specified combinations The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly. :rel parent_entry: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv4 address :rel source_port: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
- relation nokia_srlinux::acl::system_filter::ipv4_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationIp destination_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv4 address
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationIp.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationPort destination_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationPort.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::Icmp icmp [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::Icmp.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourceIp.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourcePort source_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourcePort.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets Yang definition can be found here: srl_nokia-acl.yang:L827
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action.accept [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets without sending any ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L832
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry The log entry contains the following information: - timestamp - filter name - filter entry sequence-id - action: drop - IP protocol - packet-length - source-IP - source-port (TCP/UDP packets) - dest-IP - dest-port (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) :rel parent_action: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets without sending any ICMP messages back to the source
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on destination IPv4 address Yang definition can be found here: srl_nokia-acl.yang:L866
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Match a packet if its destination IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? mask=null¶
Match a packet if its destination IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its destination IP address is within the specified IPv4 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv4 address
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match.destination_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationPort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1095
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::destination_port_value_t? value=null¶
A destination port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match.destination_port [0:1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::destination_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::Icmp¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L925
- attribute yang::types::uint8[]? code=null¶
Match if the ICMP code value is any value in the list Requires ICMP type to be specified because codes are type dependent.
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::icmp_type_t? type=null¶
Match a single ICMP type value. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMP type and code matches one of the specified combinations
The rule should also have a condition that the IP protocol equals 1 (ICMP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match.icmp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv4 address Yang definition can be found here: srl_nokia-acl.yang:L957
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Match a packet if its source IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? mask=null¶
Match a packet if its source IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv4 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourcePort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1159
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::source_port_value_t? value=null¶
A source port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::Match.source_port [0:1]
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::source_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::destination_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1124
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::destination_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::destination_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_destination_port: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationPort parent_destination_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::DestinationPort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::source_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1188
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::source_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::source_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_source_port: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourcePort parent_source_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::SourcePort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::Entry¶
Parents:
nokia_srlinux::Base
List of filter rules. Yang definition can be found here: srl_nokia-acl.yang:L1698
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the filter entry
- attribute nokia_srlinux::types::srl_nokia_common::rule_sequence_id sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the System filter entry. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_ipv6_filter: Relation to parent container
- relation nokia_srlinux::acl::system_filter::Ipv6Filter parent_ipv6_filter [1]¶
Relation to parent container Peer relation: List of filter rules.
other end:
nokia_srlinux::acl::system_filter::Ipv6Filter.entry [0:*]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the System filter entry.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action.parent_entry [1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match.parent_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the System filter entry. Yang definition can be found here: srl_nokia-acl.yang:L822
- Rel accept:
Accept matching packets
- Rel drop:
Drop matching packets without sending any ICMP messages back to the source
- Rel parent_entry:
Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the System filter entry.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::Entry.action [0:1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::Accept accept [0:1]¶
Relation to parent container Peer relation: Accept matching packets
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::Accept.parent_action [1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::Drop drop [0:1]¶
Relation to parent container Peer relation: Drop matching packets without sending any ICMP messages back to the source
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::Drop.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-acl.yang:L996
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match_next_header_t? next_header=null¶
An IPv6 packet matches this condition if its first next-header field (in the IPv6 fixed header) contains the specified value
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match_tcp_flags_t? tcp_flags=null¶
A logical expression using the &, | and ! logical operators and the TCP flag names: rst, syn and ack. :rel destination_ip: Packet matching criteria based on destination IPv6 address :rel destination_port: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. :rel icmp6: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly. :rel parent_entry: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv6 address :rel source_port: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
- relation nokia_srlinux::acl::system_filter::ipv6_filter::Entry parent_entry [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::Entry.match [0:1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationIp destination_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv6 address
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationIp.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationPort destination_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationPort.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::Icmp6 icmp6 [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::Icmp6.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv6 address
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourceIp.parent_match [1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourcePort source_port [0:1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourcePort.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::Accept¶
Parents:
nokia_srlinux::Base
Accept matching packets Yang definition can be found here: srl_nokia-acl.yang:L827
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Accept matching packets
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action.accept [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::Drop¶
Parents:
nokia_srlinux::Base
Drop matching packets without sending any ICMP messages back to the source Yang definition can be found here: srl_nokia-acl.yang:L832
- attribute bool? log=null¶
When this is true, a log is created for each packet matching the entry The log entry contains the following information: - timestamp - filter name - filter entry sequence-id - action: drop - IP protocol - packet-length - source-IP - source-port (TCP/UDP packets) - dest-IP - dest-port (TCP/UDP packets) - icmp-type (ICMP packets) - icmp-code (ICMP packets) :rel parent_action: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action parent_action [1]¶
Relation to parent container Peer relation: Drop matching packets without sending any ICMP messages back to the source
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Action.drop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on destination IPv6 address Yang definition can be found here: srl_nokia-acl.yang:L1000
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? address=null¶
Match a packet if its destination IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? mask=null¶
Match a packet if its destination IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix? prefix=null¶
Match a packet if its destination IP address is within the specified IPv6 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on destination IPv6 address
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match.destination_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationPort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1095
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port_value_t? value=null¶
A destination port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its destination TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match.destination_port [0:1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::Icmp6¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1031
- attribute yang::types::uint8[]? code=null¶
Match if the ICMPv6 code value is any value in the list Requires ICMPv6 type to be specified because codes are type dependent.
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::icmp6_type_t? type=null¶
Match a single ICMPv6 type value :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its ICMPv6 type and code matches one of the specified combinations
The rule should also have a condition that the next-header value equals 58 (ICMPv6) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match.icmp6 [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv6 address Yang definition can be found here: srl_nokia-acl.yang:L1063
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? address=null¶
Match a packet if its source IP address logically anded with the inverse of the mask equals this IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? mask=null¶
Match a packet if its source IP address logically anded with the inverse of this mask equals the configured IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv6 prefix. :rel parent_match: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv6 address
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourcePort¶
Parents:
nokia_srlinux::Base
A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly. Yang definition can be found here: srl_nokia-acl.yang:L1159
- attribute nokia_srlinux::types::srl_nokia_packet_match_types::operator? operator=null¶
Comparison operator eq = equal ge = greater than or equal to le = less than or equal to
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port_value_t? value=null¶
A source port number :rel parent_match: Relation to parent container :rel range: Container used to specify a contiguous range of TCP/UDP port numbers
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match parent_match [1]¶
Relation to parent container Peer relation: A packet matches this condition if its source TCP or UDP port number matches the value or range that is specified
The rule should also have a condition that the IP protocol equals 6 (TCP) or 17 (UDP) in order for this to be interpreted correctly.
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::Match.source_port [0:1]
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::Range range [0:1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1124
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_destination_port: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationPort parent_destination_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::DestinationPort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::Range¶
Parents:
nokia_srlinux::Base
Container used to specify a contiguous range of TCP/UDP port numbers Yang definition can be found here: srl_nokia-acl.yang:L1188
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::range_start_t? start=null¶
The starting port number to include in the range
- attribute nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::range_end_t? x_end=null¶
The ending port number to include in the range :rel parent_source_port: Relation to parent container
- relation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourcePort parent_source_port [1]¶
Relation to parent container Peer relation: Container used to specify a contiguous range of TCP/UDP port numbers
other end:
nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::SourcePort.range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::bfd::MicroBfdSessions¶
Parents:
nokia_srlinux::Base
Context to configure micro-BFD session parameters and report sessions state Yang definition can be found here: srl_nokia-micro-bfd.yang:L138
- Rel lag_interface:
List of interface references to associate a micro-BFD session config and state
- Rel parent_bfd:
Relation to parent container
- relation nokia_srlinux::Bfd parent_bfd [1]¶
Relation to parent container Peer relation: Context to configure micro-BFD session parameters and report sessions state
other end:
nokia_srlinux::Bfd.micro_bfd_sessions [0:1]
- relation nokia_srlinux::bfd::micro_bfd_sessions::LagInterface lag_interface [0:*]¶
Relation to parent container Peer relation: List of interface references to associate a micro-BFD session config and state
other end:
nokia_srlinux::bfd::micro_bfd_sessions::LagInterface.parent_micro_bfd_sessions [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::bfd::setupMicroBfdSessionsYangContainer
constrainttrue
- entity nokia_srlinux::bfd::Subinterface¶
Parents:
nokia_srlinux::Base
List of subinterface references to associating BFD config and state Yang definition can be found here: srl_nokia-bfd.yang:L144
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable BFD for this subinterface
- attribute nokia_srlinux::bfd::subinterface_desired_minimum_transmit_interval_t? desired_minimum_transmit_interval=null¶
The minimum interval between transmission of BFD control packets This value is advertised to the peer, however the actual interval used is specified by taking the maximum of desired-minimum-transmit-interval and the value of the remote required-minimum-receive interval value. This value is specified as an integer number of microseconds.
- attribute nokia_srlinux::bfd::subinterface_detection_multiplier_t? detection_multiplier=null¶
The number of packets that must be missed to declare this session as down The detection interval for the BFD session is calculated by multiplying the value of the negotiated transmission interval by this value.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_no_mgmt id¶
Reference ID for associated subinterface Example: ethernet-2/1.100 (Reference Interface ethernet-2/1, subinterface 100).
- attribute nokia_srlinux::bfd::subinterface_max_hop_count_t? max_hop_count=null¶
TTL to be used in the BFD IP header for multihop BFD.
- attribute nokia_srlinux::bfd::subinterface_minimum_echo_receive_interval_t? minimum_echo_receive_interval=null¶
The minimum interval between echo packets the local node can receive Implicitly enabled echo mode on the associated interface.
- attribute nokia_srlinux::bfd::subinterface_required_minimum_receive_t? required_minimum_receive=null¶
The minimum interval between received BFD control packets that this system should support This value is advertised to the remote peer to indicate the maximum frequency (i.e., minimum inter-packet interval) between BFD control packets that is acceptable to the local system. This value is specified as an integer number of microseconds. :rel parent_bfd: Relation to parent container
- relation nokia_srlinux::Bfd parent_bfd [1]¶
Relation to parent container Peer relation: List of subinterface references to associating BFD config and state
other end:
nokia_srlinux::Bfd.subinterface [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::bfd::setupSubinterfaceYangContainer
constrainttrue
- entity nokia_srlinux::bfd::micro_bfd_sessions::LagInterface¶
Parents:
nokia_srlinux::Base
List of interface references to associate a micro-BFD session config and state Yang definition can be found here: srl_nokia-micro-bfd.yang:L142
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable BFD for this subinterface
- attribute nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_desired_minimum_transmit_interval_t? desired_minimum_transmit_interval=null¶
The minimum interval between transmission of BFD control packets This value is advertised to the peer, however the actual interval used is specified by taking the maximum of desired-minimum-transmit-interval and the value of the remote required-minimum-receive interval value. This value is specified as an integer number of microseconds.
- attribute nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_detection_multiplier_t? detection_multiplier=null¶
The number of packets that must be missed to declare this session as down The detection interval for the BFD session is calculated by multiplying the value of the negotiated transmission interval by this value.
- attribute nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_local_address_t? local_address=null¶
IP address to be used as source address in BFD packets
- attribute string name¶
Reference ID for associated lag interface Example: lag1 (Reference Interface lag1).
- attribute nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_remote_address_t? remote_address=null¶
The remote IP address for the far-end of the BFD session This must be the same IP version as the local-address.
- attribute nokia_srlinux::bfd::micro_bfd_sessions::lag_interface_required_minimum_receive_t? required_minimum_receive=null¶
The minimum interval between received BFD control packets that this system should support This value is advertised to the remote peer to indicate the maximum frequency (i.e., minimum inter-packet interval) between BFD control packets that is acceptable to the local system. This value is specified as an integer number of microseconds. :rel parent_micro_bfd_sessions: Relation to parent container
- relation nokia_srlinux::bfd::MicroBfdSessions parent_micro_bfd_sessions [1]¶
Relation to parent container Peer relation: List of interface references to associate a micro-BFD session config and state
other end:
nokia_srlinux::bfd::MicroBfdSessions.lag_interface [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::BreakoutMode¶
Parents:
nokia_srlinux::Base
Configuration of breakout options.
The 7220 D3 supports 4x10 and 4x25 breakout on ports 3-33. The 7220 D3L supports 4x10 and 4x25 breakout on ports 1-31. The 7220 H3 supports 2x100/4x100 breakout on ports 3-34. The 7220 H4 supports 4x100 breakout on ports 1-64. The 7220 D4 supports 4x100 breakout on ports 30-36. The 7220 D4 supports 4x25 breakout on ports 9, 15, 16 and 30-36. The 7220 D4 supports 4x10 breakout on ports 9, 15, 16 and 30-36. The 7220 D5 supports 4x10, 4x25 and 2x100/4x100 breakout on ports 1-32. 7250 IXR-6e/10e 36p QSFPDD IMM all port: 4x100GE and 2x100GE Yang definition can be found here: srl_nokia-interfaces.yang:L257
- attribute nokia_srlinux::interface::breakout_mode_breakout_port_speed_t? breakout_port_speed=null¶
The speed of each breakout port
- attribute nokia_srlinux::interface::breakout_mode_num_breakout_ports_t? num_breakout_ports=null¶
The number of breakout ports supported by this connector :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: Configuration of breakout options.
The 7220 D3 supports 4x10 and 4x25 breakout on ports 3-33. The 7220 D3L supports 4x10 and 4x25 breakout on ports 1-31. The 7220 H3 supports 2x100/4x100 breakout on ports 3-34. The 7220 H4 supports 4x100 breakout on ports 1-64. The 7220 D4 supports 4x100 breakout on ports 30-36. The 7220 D4 supports 4x25 breakout on ports 9, 15, 16 and 30-36. The 7220 D4 supports 4x10 breakout on ports 9, 15, 16 and 30-36. The 7220 D5 supports 4x10, 4x25 and 2x100/4x100 breakout on ports 1-32. 7250 IXR-6e/10e 36p QSFPDD IMM all port: 4x100GE and 2x100GE
other end:
nokia_srlinux::Interface.breakout_mode [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupBreakoutModeYangContainer
constrainttrue
- entity nokia_srlinux::interface::Ethernet¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces.yang:L1519
- attribute string? aggregate_id=null¶
lag interface with which this interface is associated
- attribute bool? auto_negotiate=null¶
When set to true the interface uses auto-negotiation for speed, duplex and flow-control settings. When set to false, the transmission parameters are specified manually.
- attribute bool? dac_link_training=null¶
If the system detects that the transceiver is connected to a DAC cable then a true setting enables link training for better link stastability. The link training setting must be the same at both ends of the DAC cable or else the link may not come up.
- attribute nokia_srlinux::interface::ethernet_duplex_mode_t? duplex_mode=null¶
When auto-negotiate is true, this sets the duplex mode that will be advertised to the peer. When auto-negotiate is false, this directly sets the duplex mode of the interface.
- attribute bool? forwarding_viable=null¶
If true: this LAG member link should be used for the transmission of traffic if all other LAG/port attributes allow it. If false: this LAG member link should not be used for the transmission of traffic. In all cases: This LAG member link should process any received frames when it is an active member link. L2 protocols such as LLDP, LACP and micro-BFD should continue to be sent and processed.
- attribute yang::types::uint16? lacp_port_priority=null¶
Configure the port priority for LACP. This value is used to determine which port should be activated with LACP fallback mode. Lower values are more preferred.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? mac_address=null¶
MAC address of the interface If not configured, this is set to the hw-mac-address, which is populated depending on interface type: - For interfaces with a discoverable MAC address (either populated by an external system or present in hardware) the discovered value is populated. - For interfaces without a discoverable MAC address, the address is generated from a hash of the interface name and the chassis MAC address. When deleted, will revert back to the value of hw-mac-address.
- attribute nokia_srlinux::interface::ethernet_port_speed_t? port_speed=null¶
The speed of the port or channel The default speed of a port (when there is no configured value and auto-negotiation is disabled or unsupported) depends on the platform and port/connector number as follows: mgmt0 and mgmt0-standby ports: 1G J2 IMM ports 1-32: 100G J2 IMM ports 33-36: 100G 7220-D1 ports 1-48: 1G 7220-D1 ports 49-52: 10G 7220-D2/D2L ports 1-48: 25G 7220-D2/D2L ports 49-56: 100G 7220-D2L ports 57-58: 10G 7220-D3 ports 1-2: 10G 7220-D3 ethernet-1/[3-34]: 100G 7220-D3 ethernet-1/[3-33]/n: 25G 7220-D3L ethernet-1/[1-32]: 100G 7220-D3L ethernet-1/[1-31]/n: 25G 7220-D3L ports 33-34: 10G 7220-D4 ports 1-28: 100G 7220-D4 ports 29-36: 400G 7220-D5 ports 1-32: 400G 7220-D5 ports 33-38: 10G 7220-H2 ports 1-128: 100G 7220-H3 ports 1-2: 10G 7220-H3 ports 3-34: 400G 7220-H4 ports 1-64: 400G 7220-H4 ports 65-66: 10G Supported speeds: mgmt0 and mgmt0-standby ports: 1G J2 IMM ports 1-32: 40G, 100G [note1] J2 IMM ports 33-36: 40G, 100G, 400G 7220-D1 ports 1-48: 10M, 100M, 1G 7220-D1 ports 49-52: 10G 7220-D2/D2L ports 1-48: 1G, 10G, 25G [note2] 7220-D2 ports 49-56: 10G, 25G, 40G, 100G 7220-D2L ports 49-56: 10G, 25G, 40G, 100G 7220-D2L ports 57-58: 10G 7220-D3 ports 1-2: 10G 7220-D3 ethernet-1/[3-34]: 10G, 25G, 40G, 50G, 100G 7220-D3 ethernet-1/[3-33]/n: 10G, 25G 7220-D3L ethernet-1/[1-32]: 10G, 25G, 40G, 50G, 100G 7220-D3L ethernet-1/[1-31]/n: 10G, 25G 7220-D3L ports 33-34: 10G 7220-D4 ports 1-8: 40G, 100G 7220-D4 ports 9-28: 10G, 25G, 40G, 100G 7220-D4 ports 29-36: 10G, 25G, 40G, 100G, 400G 7220-D5 ports 1-32: 40G, 100G, 400G 7220-D5 ports 33-38: 10G 7220-H2 ports 1-128: 100G 7220-H3 ports 1-2: 10G 7220-H3 ports 3-34: 40G, 100G, 200G, 400G 7220-H4 ports 1-64: 40G, 100G, 400G 7220-H4 ports 65-66: 10G [note1] Ports 9-12 cannot operate at different port speeds (some at 40G and others at 100G). The required speed of ports 9-12 is based on the port-speed of the lowest-numbered configured port in this block; if any higher-numbered port in the block is configured with a different port speed that port will not come up. [note2] On 7220-D2: if one port in each consecutive group of 4 ports (1-4, 5-8, .. , 45-48) is 25G the other 3 ports must also be 25G; if one port in each consecutive group of 4 ports (1-4, 5-8, .. , 45-48) is 1G or 10G the other 3 ports must also be 1G or 10G. On 7220-D2L: if one port in each port group of 4 ports ({1, 2, 3, 6}, {4, 5, 7, 9}, {8, 10, 11, 12}, {13, 14, 15, 18}, {16, 17, 19, 21}, {20, 22, 23, 24}, {25, 26, 27, 30}, {28, 29, 31, 33}, {32, 34, 35, 36}, {37, 38, 39, 42}, {40, 41, 43, 45}, {44, 46, 47, 48}) is 25G the other 3 ports must also be 25G; if one port in each port group of 4 ports is 1G or 10G the other 3 ports must also be 1G or 10G. 7250 IXR details: If the interface corresponds to a connector that has no installed transceiver then the value is accepted without any checking or restriction, and info from state will display the configured value. Otherwise if the configured port-speed is NOT supported by the installed transceiver the port is forced operationally down.
- attribute yang::types::int32? ptp_asymmetry=null¶
This command configures the PTP asymmetry delay on the Ethernet port This command is used to correct known asymmetry as part of time of day or phase recovery using PTP packets on both local and downstream PTP clocks.
- attribute nokia_srlinux::interface::ethernet_reload_delay_t? reload_delay=null¶
Configure reload-delay timer for Ethernet interfaces. The reload-delay timer starts when the associated XDP interface state is learned. While the timer is running, the interface transceiver laser is disabled to avoid attracting traffic from the connected device at the other end of the interface. The reload-delay timer should be used in multi-homing interfaces and be set to a value long enough to allow the system to recover all the network protocols upon reboot, before start attracting traffic from the multi-homed device.
- attribute nokia_srlinux::interface::ethernet_standby_signaling_t? standby_signaling=null¶
Indicates the standby-signaling used in the interface. An application using a port-based redundancy mechanism will trigger the standby signaling on the ethernet interface if the interface is selected as standby. :rel flow_control: :rel hold_time: Configure interface hold timers for Ethernet interfaces :rel l2cp_transparency: Configuration and state of the Layer-2 Control Protocol transparency :rel parent_interface: Relation to parent container :rel storm_control: :rel synce: This struct containing all attributes for SyncE in line/client ports.
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Interface.ethernet [0:1]
- relation nokia_srlinux::interface::ethernet::FlowControl flow_control [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::ethernet::FlowControl.parent_ethernet [1]
- relation nokia_srlinux::interface::ethernet::HoldTime hold_time [0:1]¶
Relation to parent container Peer relation: Configure interface hold timers for Ethernet interfaces
other end:
nokia_srlinux::interface::ethernet::HoldTime.parent_ethernet [1]
- relation nokia_srlinux::interface::ethernet::L2cpTransparency l2cp_transparency [0:1]¶
Relation to parent container Peer relation: Configuration and state of the Layer-2 Control Protocol transparency
other end:
nokia_srlinux::interface::ethernet::L2cpTransparency.parent_ethernet [1]
- relation nokia_srlinux::interface::ethernet::StormControl storm_control [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::ethernet::StormControl.parent_ethernet [1]
- relation nokia_srlinux::interface::ethernet::Synce synce [0:1]¶
Relation to parent container Peer relation: This struct containing all attributes for SyncE in line/client ports.
other end:
nokia_srlinux::interface::ethernet::Synce.parent_ethernet [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupEthernetYangContainer
constrainttrue
- entity nokia_srlinux::interface::Lag¶
Parents:
nokia_srlinux::Base
Container for options related to LAG Yang definition can be found here: srl_nokia-interfaces-lag.yang:L183
- attribute nokia_srlinux::types::srl_nokia_interfaces_lag::lacp_fallback_type? lacp_fallback_mode=null¶
Specifies lacp-fallback mode if enabled
- attribute nokia_srlinux::interface::lag_lacp_fallback_timeout_t? lacp_fallback_timeout=null¶
Specifies the LACP-fallback timeout interval in seconds
- attribute nokia_srlinux::types::srl_nokia_interfaces_lag::lag_type? lag_type=null¶
Sets the type of LAG, i.e., how it is configured / maintained
- attribute nokia_srlinux::types::srl_nokia_interfaces_lag::member_speed_type? member_speed=null¶
Specifies the link speed of allowed member-links
- attribute nokia_srlinux::interface::lag_min_links_t? min_links=null¶
Specifies the mininum number of member interfaces that must be active for the aggregate interface to be available :rel lacp: LACP parameters for the associated LAG :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container for options related to LAG
other end:
nokia_srlinux::Interface.lag [0:1]
- relation nokia_srlinux::interface::lag::Lacp lacp [0:1]¶
Relation to parent container Peer relation: LACP parameters for the associated LAG
other end:
nokia_srlinux::interface::lag::Lacp.parent_lag [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupLagYangContainer
constrainttrue
- entity nokia_srlinux::interface::Linux¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state related to Linux interfaces Yang definition can be found here: srl_nokia-interfaces-vxdp.yang:L59
- attribute nokia_srlinux::interface::linux_device_name_t? device_name=null¶
Slow path device name of this interface in Linux This is the interface name that can be used to look at this interface within Linux. If not specified it is auto-derived by the system. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to Linux interfaces
other end:
nokia_srlinux::Interface.linux [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupLinuxYangContainer
constrainttrue
- entity nokia_srlinux::interface::P4rt¶
Parents:
nokia_srlinux::Base
Top-level container for P4Runtime interface configuration and state Yang definition can be found here: srl_nokia-interfaces-p4rt.yang:L36
- attribute nokia_srlinux::interface::p4rt_id_t? id=null¶
The numeric identifier used by the controller to address the interface This ID is the interface ifIndex by default, or is assigned by an external-to-the-device entity (e.g., an SDN management system) to establish an externally deterministic numeric reference for the interface. The programming entity must ensure that the ID is unique within the required context. Note that this identifier is used only when a numeric reference to the interface is required, it does not replace the unique name assigned to the interface. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: Top-level container for P4Runtime interface configuration and state
other end:
nokia_srlinux::Interface.p4rt [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupP4rtYangContainer
constrainttrue
- entity nokia_srlinux::interface::Sflow¶
Parents:
nokia_srlinux::Base
Context to configure sFlow parameters Yang definition can be found here: srl_nokia-interfaces.yang:L372
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable sFlow on this interface :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: Context to configure sFlow parameters
other end:
nokia_srlinux::Interface.sflow [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupSflowYangContainer
constrainttrue
- entity nokia_srlinux::interface::Subinterface¶
Parents:
nokia_srlinux::Base
The list of subinterfaces (logical interfaces) associated with a physical interface Yang definition can be found here: srl_nokia-interfaces.yang:L715
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The configured, desired state of the subinterface
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user-configured description of the interface
- attribute nokia_srlinux::interface::subinterface_ip_mtu_t? ip_mtu=null¶
IP MTU of the subinterface in bytes. Includes the IP header but excludes Ethernet encapsulation. IP MTU specifies the maximum sized IPv4 or IPv6 packet that can be transmitted on the subinterface. If an IPv4 or IPv6 packet exceeds this size it is dropped and this may result in the generation of an ICMP error message back to the source. The default IP MTU for a subinterface is taken from /system/mtu/default-ip-mtu. For the mgmt0 and mgmt0-standby subinterfaces the default is the associated interface MTU minus the Ethernet encapsulation overhead. The IP MTU is not configurable for subinterfaces of loopback interfaces. The 7220 IXR-D1, 7220 IXR-D2, 7220 IXR-D3, 7220 IXR-H2, and 7220 IXR-H3 systems support a maximum IP MTU of 9398 bytes. Each 7250 IXR IMM supports a maximum of 4 different IP MTU values. 7220 IXR systems do not have any limit on the maximum number of different IP MTU values.
- attribute nokia_srlinux::interface::subinterface_l2_mtu_t? l2_mtu=null¶
Layer-2 MTU of the subinterface in bytes. Includes the Ethernet header and VLAN tags, and excludes 4-bytes FCS. L2 MTU specifies the maximum sized Ethernet frame that can be transmitted on the subinterface. If a frame exceeds this size it is discarded. If the l2-mtu of the subinterface exceeds the port-mtu of the associated interface, the subinterface will remain operationally down. The default value for a subinterface is taken from /system/mtu/default-l2-mtu. The L2 MTU is only configurable for bridged subinterfaces. The 7220 IXR-D1, 7220 IXR-D2, 7220 IXR-D3, 7220 IXR-H2, and 7220 IXR-H3 systems support a maximum L2 MTU of 9412 bytes and minimum of 1500 bytes. The VSRL system supports a maximum L2 MTU of 9500 and minimum of 1450 bytes. All other systems support a maximum L2 MTU of 9500 and minimum of 1500 bytes.
- attribute nokia_srlinux::interface::subinterface_mpls_mtu_t? mpls_mtu=null¶
MPLS MTU of the subinterface in bytes, including the transmitted label stack. MPLS MTU specifies the maximum sized MPLS packet that can be transmitted on the subinterface. If an MPLS packet containing any payload exceeds this size then it is dropped. If the payload of the dropped packet is IPv4 or IPv6 then this may also result in the generation of an ICMP error message that is either tunneled or sent back to the source. The default MPLS MTU for a subinterface is taken from /system/mtu/default-mpls-mtu. The MPLS MTU is not configurable for subinterfaces of loopback interfaces. Each 7250 IXR IMM supports a maximum of 4 different MPLS MTU values.
- attribute string? type=null¶
Indicates the context in which the ethernet subinterface will be used
- attribute nokia_srlinux::types::srl_nokia_common::uuid? uuid=null¶
The system-generated or user-configured UUID for the sub interface
- attribute nokia_srlinux::interface::subinterface_index_t x_index¶
The index of the subinterface, or logical interface number :rel acl: Container for ACL policies applied to the subinterface :rel anycast_gw: :rel bridge_table: Enable the Bridge Table on the subinterface and configure associated parameters :rel eth_cfm: Configuration of ETH-CFM functions independent of Maintenance Domain context This is an ETH-CFM function that is configured directly under the subinterface :rel ipv4: IPv4 configuration and state for the subinterface :rel ipv6: IPv6 configuration and state for the subinterface :rel parent_interface: Relation to parent container :rel ra_guard: :rel vlan: Parameters for VLAN definition under SRL interfaces.
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: The list of subinterfaces (logical interfaces) associated with a physical interface
- relation nokia_srlinux::interface::subinterface::Acl acl [0:1]¶
Relation to parent container Peer relation: Container for ACL policies applied to the subinterface
other end:
nokia_srlinux::interface::subinterface::Acl.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::AnycastGw anycast_gw [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::AnycastGw.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation: Enable the Bridge Table on the subinterface and configure associated parameters
other end:
nokia_srlinux::interface::subinterface::BridgeTable.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::EthCfm eth_cfm [0:1]¶
Relation to parent container Peer relation: Configuration of ETH-CFM functions independent of Maintenance Domain context
This is an ETH-CFM function that is configured directly under the subinterface
other end:
nokia_srlinux::interface::subinterface::EthCfm.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation: IPv4 configuration and state for the subinterface
other end:
nokia_srlinux::interface::subinterface::Ipv4.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::Ipv6 ipv6 [0:1]¶
Relation to parent container Peer relation: IPv6 configuration and state for the subinterface
other end:
nokia_srlinux::interface::subinterface::Ipv6.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::RaGuard ra_guard [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::RaGuard.parent_subinterface [1]
- relation nokia_srlinux::interface::subinterface::Vlan vlan [0:1]¶
Relation to parent container Peer relation: Parameters for VLAN definition under SRL interfaces.
other end:
nokia_srlinux::interface::subinterface::Vlan.parent_subinterface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupSubinterfaceYangContainer
constrainttrue
- entity nokia_srlinux::interface::Transceiver¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces.yang:L1062
- attribute bool? ddm_events=null¶
Controls the reporting of DDM events When set to true, log events and state related to the Digital Diagnostic Monitoring (DDM) capabilities of the transceiver are generated and populated. When set to false, no DDM-related log events and state are generated and populated for this port/transceiver. When read from state this leaf always returns false (even if the configured value is true) when the Ethernet port is a copper/RJ45 port.
- attribute nokia_srlinux::interface::transceiver_forward_error_correction_t? forward_error_correction=null¶
The forward error correction algorithm to use on the optical channel The same FEC algorithm must be used at both ends of a link. 25G interfaces support disabled, base-r rs-108 and rs-528; configuring other (incompatible) options will bring the port down. The FEC requirement for a 25G interface depends on the cable type. A CA-N DAC cable has a loss specification that requires no FEC. A CA-S DAC cable requires base-r FEC at a minimum. A CA-L DAC cable requires the stronger rs-108 Reed Solomon FEC. 100G interfaces support disabled and rs-528; configuring other (incompatible) options will bring the port down. 400G interfaces require rs-544; configuring other (unsupported) options will bring the port down.
- attribute string? functional_type=null¶
Indicates the module functional type which will be deployed for this interface This refines the set of leaves available within the transceiver configuration.
- attribute bool? tx_laser=null¶
Enable (true) or disable (false) the transmit laser of the transceiver When read from state this leaf always returns false (even if the configured value is true) when the Ethernet port is a copper/RJ45 port. Default is true (for interfaces that support transceivers). :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Interface.transceiver [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupTransceiverYangContainer
constrainttrue
- entity nokia_srlinux::interface::Vhost¶
Parents:
nokia_srlinux::Base
Top-level container for vhost-user interface configuration and state Yang definition can be found here: srl_nokia-interfaces-vxdp.yang:L134
- attribute nokia_srlinux::interface::vhost_vhost_socket_mode_t? vhost_socket_mode=null¶
The vhost-user socket mode If set to server, the socket is created by SR Linux, if set to client SR Linux will connect to a pre-existing socket.
- attribute nokia_srlinux::types::srl_nokia_common::local_file? vhost_socket_path=null¶
Filesystem path to the vhost-user socket
- attribute nokia_srlinux::interface::vhost_vhost_socket_queues_t? vhost_socket_queues=null¶
The number of vhost-user queues The number of queues are retrieved from the vhost-user socket if not configured. This should be set equivalent to the number of vCPUs allocated to the other end of the vhost-user interface. This value must not exceed the count of vCPUs provided as the vXDP cpu-set. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::Interface parent_interface [1]¶
Relation to parent container Peer relation: Top-level container for vhost-user interface configuration and state
other end:
nokia_srlinux::Interface.vhost [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::setupVhostYangContainer
constrainttrue
- entity nokia_srlinux::interface::ethernet::FlowControl¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces.yang:L1612
- attribute bool? receive=null¶
When this is true PAUSE frames received on this interface are accepted and processed, and, if auto-negotiation is enabled it also causes the capability to receive PAUSE frames to be signaled to the peer (applicable only to ports 1-48 of the 7220 IXR-D1 and to mgmt0 and mgmt0-standby ports). When this is false PAUSE frames received on this interface are ignored, and, if auto-negotiation is enabled it causes the capability to receive PAUSE frames to be signaled to the peer as non-support (applicable only to ports 1-48 of the 7220 IXR-D1 and to mgmt0 and mgmt0-standby ports)
- attribute bool? transmit=null¶
Enables/disables the sending of PAUSE frames. If auto-negotiation is enabled (applicable only to ports 1-48 of the 7220 IXR-D1 and to mgmt0 and mgmt0-standby ports) PAUSE frames are sent to the peer only if the peer advertised support for PAUSE frames. :rel parent_ethernet: Relation to parent container
- relation nokia_srlinux::interface::Ethernet parent_ethernet [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::Ethernet.flow_control [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::HoldTime¶
Parents:
nokia_srlinux::Base
Configure interface hold timers for Ethernet interfaces Yang definition can be found here: srl_nokia-interfaces.yang:L1861
- attribute nokia_srlinux::interface::ethernet::hold_time_down_t? down=null¶
Holds link down events for the configured time. The hold-time down behavior is triggered with events that try to bring the ethernet interface down and can change quickly. It is not triggered with an admin-state disable event or interface disable due to other internal reasons (such as fabric unavailability). When running, the interface will not be brought down till the timer expires. The typical use of the hold-time down is to provide stability and avoid the protocols to advertise/withdraw messages if there are flapping optics. The hold-time down is aborted if the user does admin-state disable or if the interface is disabled due to other internal reasons that prevent the traffic to be forwarded on the interface.
- attribute nokia_srlinux::interface::ethernet::hold_time_up_t? up=null¶
Holds link up events for the configured time. The hold-time up behavior is triggered with any event that tries to bring up the ethernet interface (interface admin-state enable, a reboot, etc). While the hold-time up is running, the transceiver laser will be enabled, however the higher layers will not be notified that the interface is operationally up until the timer expires. :rel parent_ethernet: Relation to parent container
- relation nokia_srlinux::interface::Ethernet parent_ethernet [1]¶
Relation to parent container Peer relation: Configure interface hold timers for Ethernet interfaces
other end:
nokia_srlinux::interface::Ethernet.hold_time [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::ethernet::setupHoldTimeYangContainer
constrainttrue
- entity nokia_srlinux::interface::ethernet::L2cpTransparency¶
Parents:
nokia_srlinux::Base
Configuration and state of the Layer-2 Control Protocol transparency Yang definition can be found here: srl_nokia-interfaces-l2cp.yang:L252
- attribute bool? tunnel_all_l2cp=null¶
Configures the tunneling of all the L2CP protocols. When set to true this command triggers the installation of an ingress TCAM rule with the highest priority (above all the individual L2CP tunnel rules) which allows the forwarding of any Layer-2 Control Protocol coming into the interface. All the L2CP frames identified by MAC DA = 01:80:c2:00:00:0x or MAC DA = 01:80:c2:00:00:2x, with ‘x’ being any hex value, are tunneled. When set to false, all L2CP frames without a specific L2CP tunnel rule are discarded. :rel dot1x: Container for the configuration of 802.1x Port based Network Access Control. :rel lacp: Container for L2CP transparency of the Link Aggregation Control Protocol :rel lldp: Container for L2CP transparency of the Link Layer Discovery Protocol :rel parent_ethernet: Relation to parent container :rel ptp: Container for the configuration of Precision Time Protocol Peer-Delay frames. :rel xstp: Container for the configuration of all the Spanning Tree Protocols. It includes Spanning Tree Protocol (STP), Rapid RSTP (RSTP) and Multiple STP (MSTP)
- relation nokia_srlinux::interface::Ethernet parent_ethernet [1]¶
Relation to parent container Peer relation: Configuration and state of the Layer-2 Control Protocol transparency
other end:
nokia_srlinux::interface::Ethernet.l2cp_transparency [0:1]
- relation nokia_srlinux::interface::ethernet::l2cp_transparency::Dot1x dot1x [0:1]¶
Relation to parent container Peer relation: Container for the configuration of 802.1x Port based Network Access Control.
other end:
nokia_srlinux::interface::ethernet::l2cp_transparency::Dot1x.parent_l2cp_transparency [1]
- relation nokia_srlinux::interface::ethernet::l2cp_transparency::Lacp lacp [0:1]¶
Relation to parent container Peer relation: Container for L2CP transparency of the Link Aggregation Control Protocol
other end:
nokia_srlinux::interface::ethernet::l2cp_transparency::Lacp.parent_l2cp_transparency [1]
- relation nokia_srlinux::interface::ethernet::l2cp_transparency::Lldp lldp [0:1]¶
Relation to parent container Peer relation: Container for L2CP transparency of the Link Layer Discovery Protocol
other end:
nokia_srlinux::interface::ethernet::l2cp_transparency::Lldp.parent_l2cp_transparency [1]
- relation nokia_srlinux::interface::ethernet::l2cp_transparency::Ptp ptp [0:1]¶
Relation to parent container Peer relation: Container for the configuration of Precision Time Protocol Peer-Delay frames.
other end:
nokia_srlinux::interface::ethernet::l2cp_transparency::Ptp.parent_l2cp_transparency [1]
- relation nokia_srlinux::interface::ethernet::l2cp_transparency::Xstp xstp [0:1]¶
Relation to parent container Peer relation: Container for the configuration of all the Spanning Tree Protocols.
It includes Spanning Tree Protocol (STP), Rapid RSTP (RSTP) and Multiple STP (MSTP)
other end:
nokia_srlinux::interface::ethernet::l2cp_transparency::Xstp.parent_l2cp_transparency [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::StormControl¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces.yang:L1914
- attribute nokia_srlinux::interface::ethernet::storm_control_broadcast_rate_t? broadcast_rate=null¶
The maximum rate allowed for ingress broadcast frames on the interface
- attribute nokia_srlinux::interface::ethernet::storm_control_multicast_rate_t? multicast_rate=null¶
The maximum rate allowed for ingress multicast frames on the interface
- attribute nokia_srlinux::interface::ethernet::storm_control_units_t? units=null¶
Units of storm-control policer in kbps or percentage of the interface bandwidth
- attribute nokia_srlinux::interface::ethernet::storm_control_unknown_unicast_rate_t? unknown_unicast_rate=null¶
The maximum rate allowed for ingress unknown unicast frames on the interface :rel parent_ethernet: Relation to parent container
- relation nokia_srlinux::interface::Ethernet parent_ethernet [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::Ethernet.storm_control [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::Synce¶
Parents:
nokia_srlinux::Base
This struct containing all attributes for SyncE in line/client ports. Yang definition can be found here: srl_nokia-interfaces.yang:L1984
- Rel parent_ethernet:
Relation to parent container
- Rel ssm:
This struct containing all attributes for QL/SSM with SyncE in these ports.
- relation nokia_srlinux::interface::Ethernet parent_ethernet [1]¶
Relation to parent container Peer relation: This struct containing all attributes for SyncE in line/client ports.
- relation nokia_srlinux::interface::ethernet::synce::Ssm ssm [0:1]¶
Relation to parent container Peer relation: This struct containing all attributes for QL/SSM with SyncE in these ports.
other end:
nokia_srlinux::interface::ethernet::synce::Ssm.parent_synce [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::ethernet::setupSynceYangContainer
constrainttrue
- entity nokia_srlinux::interface::ethernet::l2cp_transparency::Dot1x¶
Parents:
nokia_srlinux::Base
Container for the configuration of 802.1x Port based Network Access Control. Yang definition can be found here: srl_nokia-interfaces-l2cp.yang:L346
- attribute bool? tunnel=null¶
Configures if incoming dot1x frames are tunneled. Dot1x frames are identified by MAC DA 01-80-c2-00-00-03 and Ethertype 0x888e. :rel parent_l2cp_transparency: Relation to parent container
- relation nokia_srlinux::interface::ethernet::L2cpTransparency parent_l2cp_transparency [1]¶
Relation to parent container Peer relation: Container for the configuration of 802.1x Port based Network Access Control.
other end:
nokia_srlinux::interface::ethernet::L2cpTransparency.dot1x [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::l2cp_transparency::Lacp¶
Parents:
nokia_srlinux::Base
Container for L2CP transparency of the Link Aggregation Control Protocol Yang definition can be found here: srl_nokia-interfaces-l2cp.yang:L302
- attribute bool? tunnel=null¶
Configures if incoming LACP frames are tunneled. LACP frames are identified by MAC DA 01-80-c2-00-00-02, Ethertype 0x8809 and slow-protocol sub-type 0x01. :rel parent_l2cp_transparency: Relation to parent container
- relation nokia_srlinux::interface::ethernet::L2cpTransparency parent_l2cp_transparency [1]¶
Relation to parent container Peer relation: Container for L2CP transparency of the Link Aggregation Control Protocol
other end:
nokia_srlinux::interface::ethernet::L2cpTransparency.lacp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::l2cp_transparency::Lldp¶
Parents:
nokia_srlinux::Base
Container for L2CP transparency of the Link Layer Discovery Protocol Yang definition can be found here: srl_nokia-interfaces-l2cp.yang:L280
- attribute bool? tunnel=null¶
Configures if incoming LLDP frames are tunneled. LLDP frames are identified by MAC DA 01-80-c2-00-00-00 and Ethertype 0x88cc. :rel parent_l2cp_transparency: Relation to parent container
- relation nokia_srlinux::interface::ethernet::L2cpTransparency parent_l2cp_transparency [1]¶
Relation to parent container Peer relation: Container for L2CP transparency of the Link Layer Discovery Protocol
other end:
nokia_srlinux::interface::ethernet::L2cpTransparency.lldp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::l2cp_transparency::Ptp¶
Parents:
nokia_srlinux::Base
Container for the configuration of Precision Time Protocol Peer-Delay frames. Yang definition can be found here: srl_nokia-interfaces-l2cp.yang:L365
- attribute bool? tunnel=null¶
Configures if incoming ptp frames are tunneled. ptp frames are identified by MAC DA 01-80-c2-00-00-0e and Ethertype 0x88f7. :rel parent_l2cp_transparency: Relation to parent container
- relation nokia_srlinux::interface::ethernet::L2cpTransparency parent_l2cp_transparency [1]¶
Relation to parent container Peer relation: Container for the configuration of Precision Time Protocol Peer-Delay frames.
other end:
nokia_srlinux::interface::ethernet::L2cpTransparency.ptp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::l2cp_transparency::Xstp¶
Parents:
nokia_srlinux::Base
Container for the configuration of all the Spanning Tree Protocols.
It includes Spanning Tree Protocol (STP), Rapid RSTP (RSTP) and Multiple STP (MSTP) Yang definition can be found here: srl_nokia-interfaces-l2cp.yang:L325
- attribute bool? tunnel=null¶
Configures if incoming xSTP frames are tunneled. xSTP frames are identified by MAC DA 01-80-c2-00-00-00 and any Ethertype. :rel parent_l2cp_transparency: Relation to parent container
- relation nokia_srlinux::interface::ethernet::L2cpTransparency parent_l2cp_transparency [1]¶
Relation to parent container Peer relation: Container for the configuration of all the Spanning Tree Protocols.
It includes Spanning Tree Protocol (STP), Rapid RSTP (RSTP) and Multiple STP (MSTP)
other end:
nokia_srlinux::interface::ethernet::L2cpTransparency.xstp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::ethernet::synce::Ssm¶
Parents:
nokia_srlinux::Base
This struct containing all attributes for QL/SSM with SyncE in these ports. Yang definition can be found here: srl_nokia-interfaces.yang:L1992
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configure the administrative state for SyncE in line/client ports. When enabled, the assoicated transmit and receiver ports are set to synchronous mode and ESMC/SSM processing is enabled. Otherwise, all syncE functions are disabled in the port. :rel parent_synce: Relation to parent container
- relation nokia_srlinux::interface::ethernet::Synce parent_synce [1]¶
Relation to parent container Peer relation: This struct containing all attributes for QL/SSM with SyncE in these ports.
other end:
nokia_srlinux::interface::ethernet::Synce.ssm [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::ethernet::synce::setupSsmYangContainer
constrainttrue
- entity nokia_srlinux::interface::lag::Lacp¶
Parents:
nokia_srlinux::Base
LACP parameters for the associated LAG Yang definition can be found here: srl_nokia-lacp.yang:L288
- attribute nokia_srlinux::interface::lag::lacp_admin_key_t? admin_key=null¶
Configure the LACP admin-key to be advertised by the local system. If this value is not specified a value starting from 32768 is automatically assigned by the system.
- attribute nokia_srlinux::types::srl_nokia_lacp::lacp_period_type? interval=null¶
Set the period between LACP messages – uses the lacp-period-type enumeration.
- attribute nokia_srlinux::types::srl_nokia_lacp::lacp_activity_type? lacp_mode=null¶
ACTIVE is to initiate the transmission of LACP packets. PASSIVE is to wait for peer to initiate the transmission of LACP packets.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? system_id_mac=null¶
The MAC address portion of the node’s System ID. This is combined with the system priority to construct the 8-octet system-id. If not configured, the system-ID configured at the system/ level is used.
- attribute yang::types::uint16? system_priority=null¶
System priority used by the node on this LAG interface. Lower value is higher priority for determining which node is the controlling system. If not configured, the system-priority configured at the system/ level is used. :rel parent_lag: Relation to parent container
- relation nokia_srlinux::interface::Lag parent_lag [1]¶
Relation to parent container Peer relation: LACP parameters for the associated LAG
other end:
nokia_srlinux::interface::Lag.lacp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::lag::setupLacpYangContainer
constrainttrue
- entity nokia_srlinux::interface::subinterface::Acl¶
Parents:
nokia_srlinux::Base
Container for ACL policies applied to the subinterface Yang definition can be found here: srl_nokia-acl.yang:L2384
- Rel input:
Container for ACL options that apply to ingress traffic on the subinterface
- Rel output:
Container for ACL options that apply to egress traffic on the subinterface
- Rel parent_subinterface:
Relation to parent container
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation: Container for ACL policies applied to the subinterface
- relation nokia_srlinux::interface::subinterface::acl::Input input [0:1]¶
Relation to parent container Peer relation: Container for ACL options that apply to ingress traffic on the subinterface
other end:
nokia_srlinux::interface::subinterface::acl::Input.parent_acl [1]
- relation nokia_srlinux::interface::subinterface::acl::Output output [0:1]¶
Relation to parent container Peer relation: Container for ACL options that apply to egress traffic on the subinterface
other end:
nokia_srlinux::interface::subinterface::acl::Output.parent_acl [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::subinterface::setupAclYangContainer
constrainttrue
- entity nokia_srlinux::interface::subinterface::AnycastGw¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-if-ip.yang:L403
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? anycast_gw_mac=null¶
The MAC address of associated to the anycast-gw IP address. If the anycast-gw MAC address is not configured, it will be auto-derived from the virtual-router-id value as per draft-ietf-bess-evpn-inter-subnet-forwarding following the format 00:00:5E:00:01:VRID.
- attribute nokia_srlinux::interface::subinterface::anycast_gw_virtual_router_id_t? virtual_router_id=null¶
The Virtual Router Identifier (VRID) value used to auto-derive the anycast-gw-mac in the format 00:00:5E:00:01:VRID. :rel parent_subinterface: Relation to parent container
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::Subinterface.anycast_gw [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::BridgeTable¶
Parents:
nokia_srlinux::Base
Enable the Bridge Table on the subinterface and configure associated parameters Yang definition can be found here: srl_nokia-interfaces-bridge-table.yang:L33
- attribute bool? discard_unknown_src_mac=null¶
Discard frames with unknown source mac addresses. The source mac address of the discarded frame is never learned when this command is enabled. :rel mac_duplication: :rel mac_learning: :rel mac_limit: Bridge Table size and thresholds. :rel parent_subinterface: Relation to parent container
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation: Enable the Bridge Table on the subinterface and configure associated parameters
other end:
nokia_srlinux::interface::Subinterface.bridge_table [0:1]
- relation nokia_srlinux::interface::subinterface::bridge_table::MacDuplication mac_duplication [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::bridge_table::MacDuplication.parent_bridge_table [1]
- relation nokia_srlinux::interface::subinterface::bridge_table::MacLearning mac_learning [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::bridge_table::MacLearning.parent_bridge_table [1]
- relation nokia_srlinux::interface::subinterface::bridge_table::MacLimit mac_limit [0:1]¶
Relation to parent container Peer relation: Bridge Table size and thresholds.
other end:
nokia_srlinux::interface::subinterface::bridge_table::MacLimit.parent_bridge_table [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::EthCfm¶
Parents:
nokia_srlinux::Base
Configuration of ETH-CFM functions independent of Maintenance Domain context
This is an ETH-CFM function that is configured directly under the subinterface Yang definition can be found here: srl_nokia-ethcfm.yang:L977
- Rel ingress_squelching:
Ingress ETH-CFM functions independent of Maintenance Domain context
- Rel parent_subinterface:
Relation to parent container
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation: Configuration of ETH-CFM functions independent of Maintenance Domain context
This is an ETH-CFM function that is configured directly under the subinterface
other end:
nokia_srlinux::interface::Subinterface.eth_cfm [0:1]
- relation nokia_srlinux::interface::subinterface::eth_cfm::IngressSquelching ingress_squelching [0:1]¶
Relation to parent container Peer relation: Ingress ETH-CFM functions independent of Maintenance Domain context
other end:
nokia_srlinux::interface::subinterface::eth_cfm::IngressSquelching.parent_eth_cfm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::subinterface::setupEthCfmYangContainer
constrainttrue
- entity nokia_srlinux::interface::subinterface::Ipv4¶
Parents:
nokia_srlinux::Base
IPv4 configuration and state for the subinterface Yang definition can be found here: srl_nokia-if-ip.yang:L141
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable/disable IPv4 on the subinterface When set to enable, and even before an IPv4 address is configured, the subinterface starts to accept incoming packets with dest-ip 255.255.255.255, which is necessary to support dhcp-client functionality.
- attribute bool? allow_directed_broadcast=null¶
When this is set to true the software is allowed to re-broadcast targeted broadcast IPv4 packets on this subinterface Detailed handling of subnet broadcast is as follows: If a targeted broadcast packet is received on subinterface X that has the matching subnet then it is delivered to the CPM and CPM will reply to an ICMP echo. If a targeted broadcast packet is received on subinterface X but the matching subnet is associated with subinterface Y, and subinterface Y is configured with allow-directed-broadcasts=false then it is delivered to the CPM and CPM replies to an ICMP echo per above, but it does not re-broadcast the packet on subinterface Y. If a targeted broadcast packet is received on subinterface X but the matching subnet is associated with subinterface Y, and subinterface Y is configured with allow-directed-broadcasts=true then it is delivered to the CPM and CPM replies to an ICMP echo per above, and CPM also re-broadcasts the packet on subinterface Y. :rel address: The list of IPv4 addresses assigned to the subinterface. :rel arp: Container for the IPv4 ARP protocol :rel dhcp_client: Container for options related to DHCP :rel dhcp_relay: Container for options related to DHCPv4 relay :rel dhcp_server: :rel parent_subinterface: Relation to parent container :rel unnumbered: Top-level container for configuring unnumbered interfaces
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation: IPv4 configuration and state for the subinterface
other end:
nokia_srlinux::interface::Subinterface.ipv4 [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::Address address [0:64]¶
Relation to parent container Peer relation: The list of IPv4 addresses assigned to the subinterface.
other end:
nokia_srlinux::interface::subinterface::ipv4::Address.parent_ipv4 [1]
- relation nokia_srlinux::interface::subinterface::ipv4::Arp arp [0:1]¶
Relation to parent container Peer relation: Container for the IPv4 ARP protocol
other end:
nokia_srlinux::interface::subinterface::ipv4::Arp.parent_ipv4 [1]
- relation nokia_srlinux::interface::subinterface::ipv4::DhcpClient dhcp_client [0:1]¶
Relation to parent container Peer relation: Container for options related to DHCP
other end:
nokia_srlinux::interface::subinterface::ipv4::DhcpClient.parent_ipv4 [1]
- relation nokia_srlinux::interface::subinterface::ipv4::DhcpRelay dhcp_relay [0:1]¶
Relation to parent container Peer relation: Container for options related to DHCPv4 relay
other end:
nokia_srlinux::interface::subinterface::ipv4::DhcpRelay.parent_ipv4 [1]
- relation nokia_srlinux::interface::subinterface::ipv4::DhcpServer dhcp_server [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv4::DhcpServer.parent_ipv4 [1]
- relation nokia_srlinux::interface::subinterface::ipv4::Unnumbered unnumbered [0:1]¶
Relation to parent container Peer relation: Top-level container for configuring unnumbered interfaces
other end:
nokia_srlinux::interface::subinterface::ipv4::Unnumbered.parent_ipv4 [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::subinterface::setupIpv4YangContainer
constrainttrue
- entity nokia_srlinux::interface::subinterface::Ipv6¶
Parents:
nokia_srlinux::Base
IPv6 configuration and state for the subinterface Yang definition can be found here: srl_nokia-if-ip.yang:L302
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable/disable IPv6 on the subinterface When set to enable, and even before a global unicast IPv6 address is configured, chassis manager assigns an IPv6 link-local address to the subinterface, which will appear as a read-only entry in the address list. At this stage, the subinterface can receive IPv6 packets with any of the following destinations: - IPv6 link-local address - solicited-node multicast address for the link-local address - ff02::1 (all IPv6 devices) - ff02::2 (all IPv6 routers) :rel address: The list of IPv6 addresses assigned to the subinterface. :rel dhcp_client: Container for options related to DHCPv6 :rel dhcp_relay: Container for options related to DHCPv6 relay :rel dhcpv6_server: :rel neighbor_discovery: Container for the IPv6 Neighbor Discovery protocol :rel parent_subinterface: Relation to parent container :rel router_advertisement: Container for configuring IPv6 router discovery options
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation: IPv6 configuration and state for the subinterface
other end:
nokia_srlinux::interface::Subinterface.ipv6 [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::Address address [0:18]¶
Relation to parent container Peer relation: The list of IPv6 addresses assigned to the subinterface.
other end:
nokia_srlinux::interface::subinterface::ipv6::Address.parent_ipv6 [1]
- relation nokia_srlinux::interface::subinterface::ipv6::DhcpClient dhcp_client [0:1]¶
Relation to parent container Peer relation: Container for options related to DHCPv6
other end:
nokia_srlinux::interface::subinterface::ipv6::DhcpClient.parent_ipv6 [1]
- relation nokia_srlinux::interface::subinterface::ipv6::DhcpRelay dhcp_relay [0:1]¶
Relation to parent container Peer relation: Container for options related to DHCPv6 relay
other end:
nokia_srlinux::interface::subinterface::ipv6::DhcpRelay.parent_ipv6 [1]
- relation nokia_srlinux::interface::subinterface::ipv6::Dhcpv6Server dhcpv6_server [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv6::Dhcpv6Server.parent_ipv6 [1]
- relation nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery neighbor_discovery [0:1]¶
Relation to parent container Peer relation: Container for the IPv6 Neighbor Discovery protocol
other end:
nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery.parent_ipv6 [1]
- relation nokia_srlinux::interface::subinterface::ipv6::RouterAdvertisement router_advertisement [0:1]¶
Relation to parent container Peer relation: Container for configuring IPv6 router discovery options
other end:
nokia_srlinux::interface::subinterface::ipv6::RouterAdvertisement.parent_ipv6 [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::subinterface::setupIpv6YangContainer
constrainttrue
- entity nokia_srlinux::interface::subinterface::RaGuard¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ra_guard.yang:L118
- attribute string? policy=null¶
Reference to RA Guard Policy to apply to the associated subinterface :rel parent_subinterface: Relation to parent container :rel vlan_list: List of VLAN IDs that the RA policy should be matched against
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::Subinterface.ra_guard [0:1]
- relation nokia_srlinux::interface::subinterface::ra_guard::VlanList vlan_list [0:*]¶
Relation to parent container Peer relation: List of VLAN IDs that the RA policy should be matched against
other end:
nokia_srlinux::interface::subinterface::ra_guard::VlanList.parent_ra_guard [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::Vlan¶
Parents:
nokia_srlinux::Base
Parameters for VLAN definition under SRL interfaces. Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L499
- Rel encap:
VLAN match parmeters for the associated subinterface.
- Rel parent_subinterface:
Relation to parent container
- Rel vlan_discovery:
When present the subinterface should perform vlan discovery by broadcasting dhcp message on all vlanids
- relation nokia_srlinux::interface::Subinterface parent_subinterface [1]¶
Relation to parent container Peer relation: Parameters for VLAN definition under SRL interfaces.
other end:
nokia_srlinux::interface::Subinterface.vlan [0:1]
- relation nokia_srlinux::interface::subinterface::vlan::Encap encap [0:1]¶
Relation to parent container Peer relation: VLAN match parmeters for the associated subinterface.
other end:
nokia_srlinux::interface::subinterface::vlan::Encap.parent_vlan [1]
- relation nokia_srlinux::interface::subinterface::vlan::VlanDiscovery vlan_discovery [0:1]¶
Relation to parent container Peer relation: When present the subinterface should perform vlan discovery by broadcasting dhcp message on all vlanids
other end:
nokia_srlinux::interface::subinterface::vlan::VlanDiscovery.parent_vlan [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::interface::subinterface::setupVlanYangContainer
constrainttrue
- entity nokia_srlinux::interface::subinterface::acl::Input¶
Parents:
nokia_srlinux::Base
Container for ACL options that apply to ingress traffic on the subinterface Yang definition can be found here: srl_nokia-acl.yang:L2387
- attribute string[]? ipv4_filter=null¶
IPv4 ACL filter(s) to be applied on this subinterface On 7220 and 7250 IXR platforms only a single IPv4 filter is supported.
- attribute string[]? ipv6_filter=null¶
IPv6 ACL filter(s) to be applied on this subinterface On 7220 and 7250 IXR platforms only a single IPv6 filter is supported.
- attribute string[]? mac_filter=null¶
MAC ACL filter to be applied on this subinterface On 7220 IXR platforms MAC ACL is mutually exclusive with IP ACLs. :rel parent_acl: Relation to parent container
- relation nokia_srlinux::interface::subinterface::Acl parent_acl [1]¶
Relation to parent container Peer relation: Container for ACL options that apply to ingress traffic on the subinterface
other end:
nokia_srlinux::interface::subinterface::Acl.input [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::acl::Output¶
Parents:
nokia_srlinux::Base
Container for ACL options that apply to egress traffic on the subinterface Yang definition can be found here: srl_nokia-acl.yang:L2468
- attribute string[]? ipv4_filter=null¶
IPv4 ACL filter(s) to be applied on this subinterface On 7220 and 7250 IXR platforms only a single IPv4 filter is supported.
- attribute string[]? ipv6_filter=null¶
IPv6 ACL filter(s) to be applied on this subinterface On 7220 and 7250 IXR platforms only a single IPv6 filter is supported.
- attribute string[]? mac_filter=null¶
MAC ACL filter to be applied on this subinterface On 7220 IXR platforms MAC ACL is mutually exclusive with IP ACLs. :rel parent_acl: Relation to parent container
- relation nokia_srlinux::interface::subinterface::Acl parent_acl [1]¶
Relation to parent container Peer relation: Container for ACL options that apply to egress traffic on the subinterface
other end:
nokia_srlinux::interface::subinterface::Acl.output [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::bridge_table::MacDuplication¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-bridge-table.yang:L89
- attribute nokia_srlinux::interface::subinterface::bridge_table::mac_duplication_action_t? action=null¶
Action to take on the subinterface upon detecting at least one mac addresses as duplicate on the subinterface. In particular: - use-net-instance-action: upon detecting a duplicate mac on the subinterface, the action on the subinterface will be inherited from the action configured under network-instance/bridge-table/mac-duplication/action. - oper-down: if configured, upon detecting a duplicate mac on the subinterface, the subinterface will be brought oper-down, with oper-down-reason mac-dup-detected. The duplicate macs on the interface will be kept in CPM though, and shown in the duplicate-entries state. In this case, arriving frames on a different subinterface with the duplicate mac as source mac are dropped. Arriving frames on a different subinterface with a destination mac matching the duplicate mac are dropped. - blackhole: upon detecting a duplicate mac on the subinterface, the mac will be blackholed. Any frame received on this or any other subinterface with source mac matching a blackhole mac will be discarded. Any frame received with destination mac matching the blackhole mac will be discarded, although still processed for source mac learning. - stop-learning: upon detecting a duplicate mac on the subinterface, existing macs are kept (and refreshed) but new macs are no longer learned on this subinterface. The duplicate mac will stay learned on the subinterface. Frames arriving to a different subinterface with a source mac matching the duplicate mac will be dropped. Frames arriving to a different subinterface with a destination mac matching the duplicate mac will be forwarded normally. :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::interface::subinterface::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::BridgeTable.mac_duplication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::bridge_table::MacLearning¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-bridge-table.yang:L67
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the learning procedures for dynamic mac addresses. If disabled, the existing macs in the bridge-table will be kept (and refreshed if new frames arrive for them) but no new mac addresses will be learned. Frames with unknown mac addresses are not dropped, unless discard-unknown-src-mac is configured. :rel aging: :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::interface::subinterface::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::BridgeTable.mac_learning [0:1]
- relation nokia_srlinux::interface::subinterface::bridge_table::mac_learning::Aging aging [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::bridge_table::mac_learning::Aging.parent_mac_learning [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::bridge_table::MacLimit¶
Parents:
nokia_srlinux::Base
Bridge Table size and thresholds. Yang definition can be found here: srl_nokia-interfaces-bridge-table.yang:L45
- attribute nokia_srlinux::interface::subinterface::bridge_table::mac_limit_maximum_entries_t? maximum_entries=null¶
Maximum number of mac addresses allowed in the bridge-table.
- attribute nokia_srlinux::interface::subinterface::bridge_table::mac_limit_warning_threshold_pct_t? warning_threshold_pct=null¶
Percentage of the configured max-number-macs over which a warning is triggered. The warning message is cleared when the percentage drops below the configured percentage minus 5% :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::interface::subinterface::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation: Bridge Table size and thresholds.
other end:
nokia_srlinux::interface::subinterface::BridgeTable.mac_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::bridge_table::mac_learning::Aging¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-bridge-table.yang:L78
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the aging for the dynamic mac entries in the bridge table. If disabled, dynamically learned mac entries will be programmed in the bridge table until the network instance is disabled. :rel parent_mac_learning: Relation to parent container
- relation nokia_srlinux::interface::subinterface::bridge_table::MacLearning parent_mac_learning [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::bridge_table::MacLearning.aging [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::eth_cfm::IngressSquelching¶
Parents:
nokia_srlinux::Base
Ingress ETH-CFM functions independent of Maintenance Domain context Yang definition can be found here: srl_nokia-ethcfm.yang:L982
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::md_levels_ordered_type? squelch_levels=null¶
Contiguous ETH-CFM Maintenance Domain levels silently discarded at ingress, matching subinterface and level ETH-CFM packets ingressing a subinterface that match the definition of the subinterface and have an ETH-CFM level that is part of the squelching configuration will be silently discarded without processing. The lookup is an exact match of the subinterface followed immediately by the ETH-CFM etype 0x8902 and a level equal to any configured squelch values. The lookup for the ETH-CFM level cannot exceed a total of two VLAN tags. Ingress squelching will occur prior to any ingress ETH-CFM MP processing. For example, if a down MEP exists on the subinterface with a level covered by the configured squelch levels the packet will be dropped before the packet it reaches the down MEP. :rel parent_eth_cfm: Relation to parent container
- relation nokia_srlinux::interface::subinterface::EthCfm parent_eth_cfm [1]¶
Relation to parent container Peer relation: Ingress ETH-CFM functions independent of Maintenance Domain context
other end:
nokia_srlinux::interface::subinterface::EthCfm.ingress_squelching [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::Address¶
Parents:
nokia_srlinux::Base
The list of IPv4 addresses assigned to the subinterface. Yang definition can be found here: srl_nokia-if-ip.yang:L155
- attribute bool? anycast_gw=null¶
This designates the associated IPv4 address as an anycast-gateway IPv4 address of the subinterface. When this parameter is set to true: - The IPv4 address is associated with the anycast-gw MAC address in the same subinterface. ARP Requests received for the anycast-gw IPv4 address will be replied using this anycast-gw MAC address. - The IPv4 address can have duplicate IPv4 addresses in other IRB subinterfaces of routers attached to the same broadcast domain. Because of that ARP duplicate-address-detection procedures do not apply to anycast-gw IP addresses.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix_with_host_bits ip_prefix¶
The IPv4 address and prefix length in CIDR notation Subnets on the same subinterface are allowed to overlap as long as the host bits are different. When a locally originated unicast packet is destined to a host covered by multiple subnets associated with a subinterface, the source address is chosen to be the numerically lowest IP address among all these subnets. For example, if the addresses 172.16.1.1/12, 172.16.1.2/12, and 172.16.1.3/12 are configured on the same interface, 172.16.1.1 would be used as a local address when you issue a ping 172.16.1.5 command
- attribute bool? primary=null¶
One of the IPv4 prefixes assigned to the subinterface can be explicitly configured as primary by setting this leaf to true. This designates the associated IPv4 address as a primary IPv4 address of the subinterface. By default, the numerically lowest value IPv4 address is selected as the primary address. The primary address is used as the source address for locally originated broadcast and multicast packets sent out the subinterface. :rel parent_ipv4: Relation to parent container :rel vrrp: VRRP Configuration and State under a IPv4 context of a sub-interface
- relation nokia_srlinux::interface::subinterface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: The list of IPv4 addresses assigned to the subinterface.
other end:
nokia_srlinux::interface::subinterface::Ipv4.address [0:64]
- relation nokia_srlinux::interface::subinterface::ipv4::address::Vrrp vrrp [0:1]¶
Relation to parent container Peer relation: VRRP Configuration and State under a IPv4 context of a sub-interface
other end:
nokia_srlinux::interface::subinterface::ipv4::address::Vrrp.parent_address [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::Arp¶
Parents:
nokia_srlinux::Base
Container for the IPv4 ARP protocol Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L205
- attribute nokia_srlinux::interface::subinterface::ipv4::arp_debug_t[]? debug=null¶
List of events to debug
- attribute bool? duplicate_address_detection=null¶
If set to true IPv4 Address Conflict Detection per RFC 5227 is performed on the IPv4 address assigned to the subinterface
- attribute bool? learn_unsolicited=null¶
If set to true an ARP entry should be learned from any received ARP packets.
- attribute bool? proxy_arp=null¶
When set to true, the router replies with its own MAC to ARP Request destined to any host.
- attribute nokia_srlinux::interface::subinterface::ipv4::arp_timeout_t? timeout=null¶
Duration of time that dynamic ARP entries remain in the ARP cache before they expire A change to this value does not affect existing entries until they are refreshed. :rel evpn: Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes. :rel host_route: Configure which types of ARP or ND entries will be populated in the route-table. :rel neighbor: List of static and dynamic ARP cache entries that map an IPv4 address to a MAC address To configure a static ARP entry a value must be written into this leaf and the link-layer-address leaf. :rel parent_ipv4: Relation to parent container :rel virtual_ipv4_discovery: Enable Virtual IPv4 discovery on the subinterface and configure associated parameters When enabled, the system will attempt to discover the configured virtual IPv4 addresses on the listed bridged subinterfaces.
- relation nokia_srlinux::interface::subinterface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Container for the IPv4 ARP protocol
other end:
nokia_srlinux::interface::subinterface::Ipv4.arp [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes.
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::Evpn.parent_arp [1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::HostRoute host_route [0:1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be populated in the route-table.
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::HostRoute.parent_arp [1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::Neighbor neighbor [0:*]¶
Relation to parent container Peer relation: List of static and dynamic ARP cache entries that map an IPv4 address to a MAC address
To configure a static ARP entry a value must be written into this leaf and the link-layer-address leaf.
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::Neighbor.parent_arp [1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::VirtualIpv4Discovery virtual_ipv4_discovery [0:1]¶
Relation to parent container Peer relation: Enable Virtual IPv4 discovery on the subinterface and configure associated parameters
When enabled, the system will attempt to discover the configured virtual IPv4 addresses on the listed bridged subinterfaces.
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::VirtualIpv4Discovery.parent_arp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::DhcpClient¶
Parents:
nokia_srlinux::Base
Container for options related to DHCP Yang definition can be found here: srl_nokia-interfaces-ip-dhcp.yang:L32
- Rel parent_ipv4:
Relation to parent container
- Rel trace_options:
Container for tracing DHCPv4 operations on the subinterface
- relation nokia_srlinux::interface::subinterface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Container for options related to DHCP
other end:
nokia_srlinux::interface::subinterface::Ipv4.dhcp_client [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::dhcp_client::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Container for tracing DHCPv4 operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv4::dhcp_client::TraceOptions.parent_dhcp_client [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::DhcpRelay¶
Parents:
nokia_srlinux::Base
Container for options related to DHCPv4 relay Yang definition can be found here: srl_nokia-interfaces-ip-dhcp-relay.yang:L114
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The configurable state of the dhcp relay agent
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? gi_address=null¶
IPv4 address to be used as giaddr of the relayed packets towards DHCPv4 servers. This address can be any IPv4 address configured within the network-instance towards the DHCPv4 server
- attribute string? network_instance=null¶
network instance to relay dhcp packets to
- attribute nokia_srlinux::interface::subinterface::ipv4::dhcp_relay_option_t[]? option=null¶
List of option82 suboptions to insert into relayed packet towards DHCPv4 server
- attribute nokia_srlinux::interface::subinterface::ipv4::dhcp_relay_server_t[]? server=null¶
List of the DHCPv4 servers that the DHCPv4 relay function will relay DHCPv4 packets to/from
- attribute bool? use_gi_addr_as_src_ip_addr=null¶
When this is set, the configured giaddress will be used as source ip address. :rel parent_ipv4: Relation to parent container :rel trace_options: Container for tracing DHCPv4 relay operations on the subinterface
- relation nokia_srlinux::interface::subinterface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Container for options related to DHCPv4 relay
other end:
nokia_srlinux::interface::subinterface::Ipv4.dhcp_relay [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::dhcp_relay::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Container for tracing DHCPv4 relay operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv4::dhcp_relay::TraceOptions.parent_dhcp_relay [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::DhcpServer¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-ip-dhcp-server.yang:L54
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables/Disables DHCP server function on subinterface :rel parent_ipv4: Relation to parent container
- relation nokia_srlinux::interface::subinterface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::Ipv4.dhcp_server [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::Unnumbered¶
Parents:
nokia_srlinux::Base
Top-level container for configuring unnumbered interfaces Yang definition can be found here: srl_nokia-if-ip.yang:L230
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When enabled, the subinterface should operate in unnumbered mode for IPv4
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all? interface=null¶
Reference to the subinterface with the IPv4 address to be borrowed :rel parent_ipv4: Relation to parent container
- relation nokia_srlinux::interface::subinterface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Top-level container for configuring unnumbered interfaces
other end:
nokia_srlinux::interface::subinterface::Ipv4.unnumbered [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::address::Vrrp¶
Parents:
nokia_srlinux::Base
VRRP Configuration and State under a IPv4 context of a sub-interface Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L338
- Rel parent_address:
Relation to parent container
- Rel vrrp_group:
VRRP Group Specific Configuration under IPv4 context
- relation nokia_srlinux::interface::subinterface::ipv4::Address parent_address [1]¶
Relation to parent container Peer relation: VRRP Configuration and State under a IPv4 context of a sub-interface
other end:
nokia_srlinux::interface::subinterface::ipv4::Address.vrrp [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup vrrp_group [0:*]¶
Relation to parent container Peer relation: VRRP Group Specific Configuration under IPv4 context
other end:
nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup.parent_vrrp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup¶
Parents:
nokia_srlinux::Base
VRRP Group Specific Configuration under IPv4 context Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L344
- attribute bool? accept_mode=null¶
Allows ssh,ping,traceroute to be accepted on the virtual IP address
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state for the associated VRRP group instance
- attribute yang::types::uint16? advertise_interval=null¶
The interval between VRRP messages in milliseconds
- attribute yang::types::uint16? init_delay=null¶
Initialization delay before a router that just rebooted will preemt an existing master router. Only applicable if preemt is enabled
- attribute bool? master_inherit_interval=null¶
Learn VRRP advertisement interval from master
- attribute yang::types::uint16? oper_interval=null¶
The operational advertisement interval between VRRP messages
- attribute bool? preempt=null¶
Enable VRRP master pre-emption. If enabled, router with higher priority can assume master role. If disabled, router can only become master if no other master is present
- attribute yang::types::uint16? preempt_delay=null¶
Delay before a router preemts an existing master router, only applicable if preemt is enabled
- attribute yang::types::uint8? priority=null¶
Base VRRP Priority for associated Virtual Address
- attribute yang::types::uint8? version=null¶
VRRP version for the Instance
- attribute nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group_virtual_address_t[]? virtual_address=null¶
Associated Virtual IP address.
- attribute yang::types::uint8 virtual_router_id¶
VRRP Group Index :rel authentication: Context to configure authentication keychain :rel interface_tracking: Interface reference for interface tracking :rel parent_vrrp: Relation to parent container :rel statistics:
- relation nokia_srlinux::interface::subinterface::ipv4::address::Vrrp parent_vrrp [1]¶
Relation to parent container Peer relation: VRRP Group Specific Configuration under IPv4 context
other end:
nokia_srlinux::interface::subinterface::ipv4::address::Vrrp.vrrp_group [0:*]
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Context to configure authentication keychain
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::InterfaceTracking interface_tracking [0:1]¶
Relation to parent container Peer relation: Interface reference for interface tracking
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::Statistics statistics [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::Authentication¶
Parents:
nokia_srlinux::Base
Context to configure authentication keychain Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L159
- attribute string? keychain=null¶
Reference to a keychain. The keychain type must be md5 or clear-text :rel parent_vrrp_group: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup parent_vrrp_group [1]¶
Relation to parent container Peer relation: Context to configure authentication keychain
other end:
nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::InterfaceTracking¶
Parents:
nokia_srlinux::Base
Interface reference for interface tracking Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L177
- Rel parent_vrrp_group:
Relation to parent container
- Rel track_interface:
Interface reference for interface tracking.
VRRP Group can track multiple interfaces.
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup parent_vrrp_group [1]¶
Relation to parent container Peer relation: Interface reference for interface tracking
other end:
nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup.interface_tracking [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::interface_tracking::TrackInterface track_interface [0:*]¶
Relation to parent container Peer relation: Interface reference for interface tracking. VRRP Group can track multiple interfaces.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::Statistics¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L255
- Rel parent_vrrp_group:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup parent_vrrp_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv4::address::vrrp::VrrpGroup.statistics [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::interface_tracking::TrackInterface¶
Parents:
nokia_srlinux::Base
Interface reference for interface tracking. VRRP Group can track multiple interfaces. Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L180
- attribute string interface¶
Interface to track
- attribute yang::types::uint8? priority_decrement=null¶
For each tracked interface that is down then the priority is decremented by the specific amount to a minimum value of 0 :rel parent_interface_tracking: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::InterfaceTracking parent_interface_tracking [1]¶
Relation to parent container Peer relation: Interface reference for interface tracking. VRRP Group can track multiple interfaces.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::Evpn¶
Parents:
nokia_srlinux::Base
Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes. Yang definition can be found here: srl_nokia-interfaces-nbr-evpn.yang:L79
- Rel advertise:
- Rel parent_arp:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::Arp parent_arp [1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes.
other end:
nokia_srlinux::interface::subinterface::ipv4::Arp.evpn [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::evpn::Advertise advertise [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::evpn::Advertise.parent_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::HostRoute¶
Parents:
nokia_srlinux::Base
Configure which types of ARP or ND entries will be populated in the route-table. Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L155
- Rel parent_arp:
Relation to parent container
- Rel populate:
- relation nokia_srlinux::interface::subinterface::ipv4::Arp parent_arp [1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be populated in the route-table.
other end:
nokia_srlinux::interface::subinterface::ipv4::Arp.host_route [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::host_route::Populate populate [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::host_route::Populate.parent_host_route [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::Neighbor¶
Parents:
nokia_srlinux::Base
List of static and dynamic ARP cache entries that map an IPv4 address to a MAC address
To configure a static ARP entry a value must be written into this leaf and the link-layer-address leaf. Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L231
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address ipv4_address¶
IPv4 address resolved by the ARP entry To configure a static neighbor entry a value must be written into this leaf and the link-layer-address leaf.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? link_layer_address=null¶
The resolving MAC address of the ARP entry To configure a static ARP entry a value must be written into this leaf and the ipv4-address leaf. :rel parent_arp: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::Arp parent_arp [1]¶
Relation to parent container Peer relation: List of static and dynamic ARP cache entries that map an IPv4 address to a MAC address
To configure a static ARP entry a value must be written into this leaf and the link-layer-address leaf.
other end:
nokia_srlinux::interface::subinterface::ipv4::Arp.neighbor [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::VirtualIpv4Discovery¶
Parents:
nokia_srlinux::Base
Enable Virtual IPv4 discovery on the subinterface and configure associated parameters
When enabled, the system will attempt to discover the configured virtual IPv4 addresses on the listed bridged subinterfaces. Yang definition can be found here: srl_nokia-interfaces-nbr-virtual-ip-discovery.yang:L76
- Rel address:
The list of virtual IPv4 addresses to be discovered on the subinterface.
- Rel parent_arp:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::Arp parent_arp [1]¶
Relation to parent container Peer relation: Enable Virtual IPv4 discovery on the subinterface and configure associated parameters
When enabled, the system will attempt to discover the configured virtual IPv4 addresses on the listed bridged subinterfaces.
other end:
nokia_srlinux::interface::subinterface::ipv4::Arp.virtual_ipv4_discovery [0:1]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::virtual_ipv4_discovery::Address address [0:640]¶
Relation to parent container Peer relation: The list of virtual IPv4 addresses to be discovered on the subinterface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::evpn::Advertise¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-nbr-evpn.yang:L87
- attribute nokia_srlinux::interface::subinterface::ipv4::arp::evpn::advertise_route_type_t route_type¶
Controls what type of ARP or ND entries to advertise. :rel internal_tags: Configuration and state of internal tags :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::arp::Evpn parent_evpn [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::Evpn.advertise [0:*]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::evpn::advertise::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::evpn::advertise::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-interfaces-nbr-evpn.yang:L47
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_advertise: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::arp::evpn::Advertise parent_advertise [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::evpn::Advertise.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::host_route::Populate¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L158
- attribute bool? datapath_programming=null¶
When set to true, the host route is programmed in the datapath
- attribute nokia_srlinux::interface::subinterface::ipv4::arp::host_route::populate_route_type_t route_type¶
Controls what type of ARP or ND entries generate a host route. :rel internal_tags: Configuration and state of internal tags :rel parent_host_route: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::arp::HostRoute parent_host_route [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::HostRoute.populate [0:*]
- relation nokia_srlinux::interface::subinterface::ipv4::arp::host_route::populate::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::host_route::populate::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L140
- attribute string? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_populate: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::arp::host_route::Populate parent_populate [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::host_route::Populate.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::arp::virtual_ipv4_discovery::Address¶
Parents:
nokia_srlinux::Base
The list of virtual IPv4 addresses to be discovered on the subinterface. Yang definition can be found here: srl_nokia-interfaces-nbr-virtual-ip-discovery.yang:L87
- attribute nokia_srlinux::types::srl_nokia_common::unicast_mac_address[]? allowed_macs=null¶
List of allowed mac addresses for a discovered virtual IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address ipv4_address¶
The virtual IPv4 address.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all[]? probe_bridged_subinterfaces=null¶
Configure the list of bridged sub-interfaces on the associated MAC-VRF to which the ARP probes are sent.
- attribute nokia_srlinux::interface::subinterface::ipv4::arp::virtual_ipv4_discovery::address_probe_interval_t? probe_interval=null¶
Configure the ARP probe interval at which the system sends an ARP request for the virtual IPv4 address. The default value of zero determines that the system sends an ARP Request for the virtual IPv4 only when the address is configured. The creation of the ARP entry for the virtual IPv4 address will in this case rely on the server sending a Gratuitous ARP for the virtual IPv4 address. When the value is set to a non-zero interval, the system sends a periodic ARP Request at the configured interval and irrespective of the ARP entry being already created. :rel parent_virtual_ipv4_discovery: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::arp::VirtualIpv4Discovery parent_virtual_ipv4_discovery [1]¶
Relation to parent container Peer relation: The list of virtual IPv4 addresses to be discovered on the subinterface.
other end:
nokia_srlinux::interface::subinterface::ipv4::arp::VirtualIpv4Discovery.address [0:640]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::dhcp_client::TraceOptions¶
Parents:
nokia_srlinux::Base
Container for tracing DHCPv4 operations on the subinterface Yang definition can be found here: srl_nokia-interfaces-ip-dhcp.yang:L39
- attribute nokia_srlinux::interface::subinterface::ipv4::dhcp_client::trace_options_trace_t[]? trace=null¶
List of events to trace :rel parent_dhcp_client: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::DhcpClient parent_dhcp_client [1]¶
Relation to parent container Peer relation: Container for tracing DHCPv4 operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv4::DhcpClient.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv4::dhcp_relay::TraceOptions¶
Parents:
nokia_srlinux::Base
Container for tracing DHCPv4 relay operations on the subinterface Yang definition can be found here: srl_nokia-interfaces-ip-dhcp-relay.yang:L182
- attribute nokia_srlinux::interface::subinterface::ipv4::dhcp_relay::trace_options_trace_t[]? trace=null¶
List of events to trace :rel parent_dhcp_relay: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv4::DhcpRelay parent_dhcp_relay [1]¶
Relation to parent container Peer relation: Container for tracing DHCPv4 relay operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv4::DhcpRelay.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::Address¶
Parents:
nokia_srlinux::Base
The list of IPv6 addresses assigned to the subinterface. Yang definition can be found here: srl_nokia-if-ip.yang:L320
- attribute bool? anycast_gw=null¶
This designates the associated IPv6 address as an anycast-gateway IPv6 address of the subinterface. When this parameter is set to true: - The IPv6 address is associated with the anycast-gw MAC address in the same subinterface. Neighbor Solicitations received for the anycast-gw IPv6 address will be replied using this anycast-gw MAC address. - The IPv6 address can have duplicate IPv6 addresses in other IRB subinterfaces of routers attached to the same broadcast domain. Because of that, ND duplicate-address-detection procedures do not apply to anycast-gw IP addresses.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix_with_host_bits ip_prefix¶
The IPv6 address and prefix-length in CIDR notation Up to 16 global unicast IPv6 addresses can be assigned to each subinterface. Global unicast IPv6 address subnets on the same subinterface are allowed to overlap as long as the host bits are different. When a locally originated unicast packet is destined to a host covered by multiple subnets associated with a subinterface, the source address is chosen to be the numerically lowest IP address among all these subnets.
- attribute bool? primary=null¶
One of the IPv6 prefixes assigned to the subinterface can be explicitly configured as primary by setting this leaf to true. This designates the associated IPv6 address as a primary IPv6 address of the subinterface. By default, the numerically lowest value IPv6 address is selected as the primary address. The primary address is used as the source address for locally originated broadcast and multicast packets sent out the subinterface.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address_type? type=null¶
Specifies the explicit type of the IPv6 address being assigned to the subinterface By default, addresses are assumed to be global unicast. Where a link-local address is to be explicitly configured, this leaf should be set to link-local. :rel parent_ipv6: Relation to parent container :rel vrrp: VRRP Configuration and State under a IPv6 context of a sub-interface
- relation nokia_srlinux::interface::subinterface::Ipv6 parent_ipv6 [1]¶
Relation to parent container Peer relation: The list of IPv6 addresses assigned to the subinterface.
other end:
nokia_srlinux::interface::subinterface::Ipv6.address [0:18]
- relation nokia_srlinux::interface::subinterface::ipv6::address::Vrrp vrrp [0:1]¶
Relation to parent container Peer relation: VRRP Configuration and State under a IPv6 context of a sub-interface
other end:
nokia_srlinux::interface::subinterface::ipv6::address::Vrrp.parent_address [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::DhcpClient¶
Parents:
nokia_srlinux::Base
Container for options related to DHCPv6 Yang definition can be found here: srl_nokia-interfaces-ip-dhcp.yang:L57
- Rel parent_ipv6:
Relation to parent container
- Rel trace_options:
Container for tracing DHCPv6 operations on the subinterface
- relation nokia_srlinux::interface::subinterface::Ipv6 parent_ipv6 [1]¶
Relation to parent container Peer relation: Container for options related to DHCPv6
other end:
nokia_srlinux::interface::subinterface::Ipv6.dhcp_client [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::dhcp_client::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Container for tracing DHCPv6 operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv6::dhcp_client::TraceOptions.parent_dhcp_client [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::DhcpRelay¶
Parents:
nokia_srlinux::Base
Container for options related to DHCPv6 relay Yang definition can be found here: srl_nokia-interfaces-ip-dhcp-relay.yang:L237
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The configurable state of the dhcp relay agent
- attribute string? network_instance=null¶
network instance to relay dhcp packets to
- attribute nokia_srlinux::interface::subinterface::ipv6::dhcp_relay_option_t[]? option=null¶
List of options to insert into relayed packet towards DHCPv6 server
- attribute nokia_srlinux::interface::subinterface::ipv6::dhcp_relay_server_t[]? server=null¶
List of the DHCPv6 servers that the DHCPv6 relay function will relay DHCPv6 packets to/from
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? source_address=null¶
Source IPv6 address of the relayed packets towards DHCPv6 servers this address can be any IPv6 address configured within the network-instance towards the DHCPv6 server :rel parent_ipv6: Relation to parent container :rel trace_options: Container for tracing DHCPv6 relay operations on the subinterface
- relation nokia_srlinux::interface::subinterface::Ipv6 parent_ipv6 [1]¶
Relation to parent container Peer relation: Container for options related to DHCPv6 relay
other end:
nokia_srlinux::interface::subinterface::Ipv6.dhcp_relay [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::dhcp_relay::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Container for tracing DHCPv6 relay operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv6::dhcp_relay::TraceOptions.parent_dhcp_relay [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::Dhcpv6Server¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-ip-dhcp-server.yang:L71
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables/Disables DHCPv6 server function on subinterface :rel parent_ipv6: Relation to parent container
- relation nokia_srlinux::interface::subinterface::Ipv6 parent_ipv6 [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::Ipv6.dhcpv6_server [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery¶
Parents:
nokia_srlinux::Base
Container for the IPv6 Neighbor Discovery protocol Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L297
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_debug_t[]? debug=null¶
List of events to debug
- attribute bool? duplicate_address_detection=null¶
Enables Duplicate Addres Detection on all tentative addresses This applies to link-local and global unicast addresses. Only one transmission is done; there are no retransmissions. Must be true on an IPv6 subinterface that has dhcp-client enabled.
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_learn_unsolicited_t? learn_unsolicited=null¶
Sets if neighbors should be learned from unsolicited neighbor advertisements for global or link local addresses or both.
- attribute bool? proxy_nd=null¶
When set to true, the router replies with its own MAC to Neighbor Solicitations destined to any host.
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_reachable_time_t? reachable_time=null¶
The period of time that a dynamic IPv6 neighbor cache entry is considered reachable after a reachability confirmation event After this time expires the neighbor state moves to STALE.
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery_stale_time_t? stale_time=null¶
The maximum time that a dynamic IPv6 neighbor cache entry can remain in the STALE state before it is removed This limit is reached only if no traffic is sent/queued towards the neighbor during the entire duration of the timer. :rel evpn: Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes. :rel host_route: Configure which types of ARP or ND entries will be populated in the route-table. :rel limit: Container for the configuration of Neighbor-Discovery limit :rel neighbor: List of static and dynamic ND cache entries that map an IPv6 address to a MAC address :rel parent_ipv6: Relation to parent container :rel virtual_ipv6_discovery: Enable Virtual IPv6 discovery on the subinterface and configure associated parameters When enabled, the system will attempt to discover the configured virtual IPv6 addresses on the listed bridged subinterfaces.
- relation nokia_srlinux::interface::subinterface::Ipv6 parent_ipv6 [1]¶
Relation to parent container Peer relation: Container for the IPv6 Neighbor Discovery protocol
other end:
nokia_srlinux::interface::subinterface::Ipv6.neighbor_discovery [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes.
other end:
nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Evpn.parent_neighbor_discovery [1]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::HostRoute host_route [0:1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be populated in the route-table.
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Limit limit [0:1]¶
Relation to parent container Peer relation: Container for the configuration of Neighbor-Discovery limit
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Neighbor neighbor [0:*]¶
Relation to parent container Peer relation: List of static and dynamic ND cache entries that map an IPv6 address to a MAC address
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::VirtualIpv6Discovery virtual_ipv6_discovery [0:1]¶
Relation to parent container Peer relation: Enable Virtual IPv6 discovery on the subinterface and configure associated parameters
When enabled, the system will attempt to discover the configured virtual IPv6 addresses on the listed bridged subinterfaces.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::RouterAdvertisement¶
Parents:
nokia_srlinux::Base
Container for configuring IPv6 router discovery options Yang definition can be found here: srl_nokia-interfaces-router-adv.yang:L39
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement_debug_t[]? debug=null¶
List of events to debug :rel parent_ipv6: Relation to parent container :rel router_role: IPv6 router advertisement options that apply when the role of the interface is a router interface.
- relation nokia_srlinux::interface::subinterface::Ipv6 parent_ipv6 [1]¶
Relation to parent container Peer relation: Container for configuring IPv6 router discovery options
other end:
nokia_srlinux::interface::subinterface::Ipv6.router_advertisement [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::router_advertisement::RouterRole router_role [0:1]¶
Relation to parent container Peer relation: IPv6 router advertisement options that apply when the role of the interface is a router interface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::address::Vrrp¶
Parents:
nokia_srlinux::Base
VRRP Configuration and State under a IPv6 context of a sub-interface Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L369
- Rel parent_address:
Relation to parent container
- Rel vrrp_group:
VRRP Group Specific Configuration under IPv6 context
- relation nokia_srlinux::interface::subinterface::ipv6::Address parent_address [1]¶
Relation to parent container Peer relation: VRRP Configuration and State under a IPv6 context of a sub-interface
other end:
nokia_srlinux::interface::subinterface::ipv6::Address.vrrp [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup vrrp_group [0:*]¶
Relation to parent container Peer relation: VRRP Group Specific Configuration under IPv6 context
other end:
nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup.parent_vrrp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup¶
Parents:
nokia_srlinux::Base
VRRP Group Specific Configuration under IPv6 context Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L375
- attribute bool? accept_mode=null¶
Allows ssh,ping,traceroute to be accepted on the virtual IP address
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state for the associated VRRP group instance
- attribute yang::types::uint16? advertise_interval=null¶
The interval between VRRP messages in milliseconds
- attribute yang::types::uint16? init_delay=null¶
Initialization delay before a router that just rebooted will preemt an existing master router. Only applicable if preemt is enabled
- attribute bool? master_inherit_interval=null¶
Learn VRRP advertisement interval from master
- attribute yang::types::uint16? oper_interval=null¶
The operational advertisement interval between VRRP messages
- attribute bool? preempt=null¶
Enable VRRP master pre-emption. If enabled, router with higher priority can assume master role. If disabled, router can only become master if no other master is present
- attribute yang::types::uint16? preempt_delay=null¶
Delay before a router preemts an existing master router, only applicable if preemt is enabled
- attribute yang::types::uint8? priority=null¶
Base VRRP Priority for associated Virtual Address
- attribute yang::types::uint8? version=null¶
VRRP version for the Instance
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address[]? virtual_address=null¶
Associated Virtual IP address.
- attribute yang::types::uint8 virtual_router_id¶
VRRP Group Index :rel authentication: Context to configure authentication keychain :rel interface_tracking: Interface reference for interface tracking :rel parent_vrrp: Relation to parent container :rel statistics:
- relation nokia_srlinux::interface::subinterface::ipv6::address::Vrrp parent_vrrp [1]¶
Relation to parent container Peer relation: VRRP Group Specific Configuration under IPv6 context
other end:
nokia_srlinux::interface::subinterface::ipv6::address::Vrrp.vrrp_group [0:*]
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Context to configure authentication keychain
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::InterfaceTracking interface_tracking [0:1]¶
Relation to parent container Peer relation: Interface reference for interface tracking
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::Statistics statistics [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::Authentication¶
Parents:
nokia_srlinux::Base
Context to configure authentication keychain Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L159
- attribute string? keychain=null¶
Reference to a keychain. The keychain type must be md5 or clear-text :rel parent_vrrp_group: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup parent_vrrp_group [1]¶
Relation to parent container Peer relation: Context to configure authentication keychain
other end:
nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::InterfaceTracking¶
Parents:
nokia_srlinux::Base
Interface reference for interface tracking Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L177
- Rel parent_vrrp_group:
Relation to parent container
- Rel track_interface:
Interface reference for interface tracking.
VRRP Group can track multiple interfaces.
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup parent_vrrp_group [1]¶
Relation to parent container Peer relation: Interface reference for interface tracking
other end:
nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup.interface_tracking [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::interface_tracking::TrackInterface track_interface [0:*]¶
Relation to parent container Peer relation: Interface reference for interface tracking. VRRP Group can track multiple interfaces.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::Statistics¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L255
- Rel parent_vrrp_group:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup parent_vrrp_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv6::address::vrrp::VrrpGroup.statistics [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::interface_tracking::TrackInterface¶
Parents:
nokia_srlinux::Base
Interface reference for interface tracking. VRRP Group can track multiple interfaces. Yang definition can be found here: srl_nokia-interfaces-ip-vrrp.yang:L180
- attribute string interface¶
Interface to track
- attribute yang::types::uint8? priority_decrement=null¶
For each tracked interface that is down then the priority is decremented by the specific amount to a minimum value of 0 :rel parent_interface_tracking: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::InterfaceTracking parent_interface_tracking [1]¶
Relation to parent container Peer relation: Interface reference for interface tracking. VRRP Group can track multiple interfaces.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::dhcp_client::TraceOptions¶
Parents:
nokia_srlinux::Base
Container for tracing DHCPv6 operations on the subinterface Yang definition can be found here: srl_nokia-interfaces-ip-dhcp.yang:L64
- attribute nokia_srlinux::interface::subinterface::ipv6::dhcp_client::trace_options_trace_t[]? trace=null¶
List of events to trace :rel parent_dhcp_client: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::DhcpClient parent_dhcp_client [1]¶
Relation to parent container Peer relation: Container for tracing DHCPv6 operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv6::DhcpClient.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::dhcp_relay::TraceOptions¶
Parents:
nokia_srlinux::Base
Container for tracing DHCPv6 relay operations on the subinterface Yang definition can be found here: srl_nokia-interfaces-ip-dhcp-relay.yang:L303
- attribute nokia_srlinux::interface::subinterface::ipv6::dhcp_relay::trace_options_trace_t[]? trace=null¶
List of events to trace :rel parent_dhcp_relay: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::DhcpRelay parent_dhcp_relay [1]¶
Relation to parent container Peer relation: Container for tracing DHCPv6 relay operations on the subinterface
other end:
nokia_srlinux::interface::subinterface::ipv6::DhcpRelay.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Evpn¶
Parents:
nokia_srlinux::Base
Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes. Yang definition can be found here: srl_nokia-interfaces-nbr-evpn.yang:L79
- Rel advertise:
- Rel parent_neighbor_discovery:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery parent_neighbor_discovery [1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be advertised in EVPN MAC/IP routes.
other end:
nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery.evpn [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::Advertise advertise [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::Advertise.parent_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::HostRoute¶
Parents:
nokia_srlinux::Base
Configure which types of ARP or ND entries will be populated in the route-table. Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L155
- Rel parent_neighbor_discovery:
Relation to parent container
- Rel populate:
- relation nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery parent_neighbor_discovery [1]¶
Relation to parent container Peer relation: Configure which types of ARP or ND entries will be populated in the route-table.
other end:
nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery.host_route [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::Populate populate [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Limit¶
Parents:
nokia_srlinux::Base
Container for the configuration of Neighbor-Discovery limit Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L170
- attribute bool? log_only=null¶
Generate only a log message when limit is reached When set to true, neighbor entries are still being learned after exceeding the max-entries limit.
- attribute yang::types::uint32? max_entries=null¶
The maximum number of neighbor entries allowed on the subinterface If not configured, the amount of neighbor entries on the subinterface is only limited by the total amount of entries supported by the router.
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::limit_warning_threshold_pct_t? warning_threshold_pct=null¶
Threshold percentage of the configured maximum number of entries When exceeded, an event is triggered. :rel parent_neighbor_discovery: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery parent_neighbor_discovery [1]¶
Relation to parent container Peer relation: Container for the configuration of Neighbor-Discovery limit
other end:
nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery.limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Neighbor¶
Parents:
nokia_srlinux::Base
List of static and dynamic ND cache entries that map an IPv6 address to a MAC address Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L351
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address ipv6_address¶
IPv6 address resolved by the ND cache entry To configure a static neighbor entry a value must be written into this leaf and the link-layer-address leaf.
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? link_layer_address=null¶
The resolving MAC address of the ND cache entry To configure a static neighbor entry a value must be written into this leaf and the ipv6-address leaf. :rel parent_neighbor_discovery: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery parent_neighbor_discovery [1]¶
Relation to parent container Peer relation: List of static and dynamic ND cache entries that map an IPv6 address to a MAC address
other end:
nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery.neighbor [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::VirtualIpv6Discovery¶
Parents:
nokia_srlinux::Base
Enable Virtual IPv6 discovery on the subinterface and configure associated parameters
When enabled, the system will attempt to discover the configured virtual IPv6 addresses on the listed bridged subinterfaces. Yang definition can be found here: srl_nokia-interfaces-nbr-virtual-ip-discovery.yang:L136
- Rel address:
The list of virtual IPv6 addresses to be discovered on the subinterface.
- Rel parent_neighbor_discovery:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery parent_neighbor_discovery [1]¶
Relation to parent container Peer relation: Enable Virtual IPv6 discovery on the subinterface and configure associated parameters
When enabled, the system will attempt to discover the configured virtual IPv6 addresses on the listed bridged subinterfaces.
other end:
nokia_srlinux::interface::subinterface::ipv6::NeighborDiscovery.virtual_ipv6_discovery [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::virtual_ipv6_discovery::Address address [0:640]¶
Relation to parent container Peer relation: The list of virtual IPv6 addresses to be discovered on the subinterface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::Advertise¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-nbr-evpn.yang:L87
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::advertise_route_type_t route_type¶
Controls what type of ARP or ND entries to advertise. :rel internal_tags: Configuration and state of internal tags :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Evpn parent_evpn [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::Evpn.advertise [0:*]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::advertise::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::advertise::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-interfaces-nbr-evpn.yang:L47
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_advertise: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::Advertise parent_advertise [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::Populate¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L158
- attribute bool? datapath_programming=null¶
When set to true, the host route is programmed in the datapath
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::populate_route_type_t route_type¶
Controls what type of ARP or ND entries generate a host route. :rel internal_tags: Configuration and state of internal tags :rel parent_host_route: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::HostRoute parent_host_route [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::HostRoute.populate [0:*]
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::populate::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::populate::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-interfaces-nbr.yang:L140
- attribute string? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_populate: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::Populate parent_populate [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::virtual_ipv6_discovery::Address¶
Parents:
nokia_srlinux::Base
The list of virtual IPv6 addresses to be discovered on the subinterface. Yang definition can be found here: srl_nokia-interfaces-nbr-virtual-ip-discovery.yang:L147
- attribute nokia_srlinux::types::srl_nokia_common::unicast_mac_address[]? allowed_macs=null¶
List of allowed mac addresses for a discovered virtual IP address.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address ipv6_address¶
The virtual IPv6 address.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all[]? probe_bridged_subinterfaces=null¶
Configure the list of bridged sub-interfaces on the associated MAC-VRF to which the NS probes are sent.
- attribute nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::virtual_ipv6_discovery::address_probe_interval_t? probe_interval=null¶
Configure the probe interval at which the system sends a Neighbor Solicitation (NS) for the virtual IPv6 address. The default value of zero determines that the system sends a NS for the virtual IPv6 only when the address is configured. The creation of the Neighbor entry for the virtual IPv6 address will in this case rely on the server sending an unsolicited Neighbor Advertisement for the virtual IPv6 address. When the value is set to a non-zero interval, the system sends a periodic NS at the configured interval and irrespective of the Neighbor entry being already created. :rel parent_virtual_ipv6_discovery: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::VirtualIpv6Discovery parent_virtual_ipv6_discovery [1]¶
Relation to parent container Peer relation: The list of virtual IPv6 addresses to be discovered on the subinterface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::router_advertisement::RouterRole¶
Parents:
nokia_srlinux::Base
IPv6 router advertisement options that apply when the role of the interface is a router interface. Yang definition can be found here: srl_nokia-interfaces-router-adv.yang:L42
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the sending of router advertisements on the subinterface.
- attribute yang::types::uint8? current_hop_limit=null¶
The current hop limit to advertise in the router advertisement messages.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_ip_mtu_t? ip_mtu=null¶
The IP MTU to advertise in the router advertisement messages and that hosts should associate with the link on which these messages are received. If no value is specified the option is not included.
- attribute bool? managed_configuration_flag=null¶
When this is set the M-bit is set in the router advertisement messages, indicating that hosts should use DHCPv6 to obtain IPv6 addresses.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_max_advertisement_interval_t? max_advertisement_interval=null¶
The maximum time between sending router advertisement messages to the all-nodes multicast address. Each subinterface has its own timer. Whenever the timer fires the message is sent and then the timer is reset to a uniformly distributed random value between min-advertisement-interval and max-advertisement-interval. The RA message can be sent before timer expiry in response to a RS message.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_min_advertisement_interval_t? min_advertisement_interval=null¶
The minimum time between sending router advertisement messages to the all-nodes multicast address. Each subinterface has its own timer. Whenever the timer fires the message is sent and then the timer is reset to a uniformly distributed random value between min-advertisement-interval and max-advertisement-interval. The RA message can be sent before timer expiry in response to a RS message.
- attribute bool? other_configuration_flag=null¶
When this is set the O-bit is set in the router advertisement messages, indicating that hosts should use DHCPv6 to obtain other configuration information (besides addresses).
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_reachable_time_t? reachable_time=null¶
The time, in milliseconds, that is advertised as the reachable time in RA messages and that hosts use for the ICMPv6 Neighbor Unreachability Detection algorithm. A value of zero means unspecified by this router.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_retransmit_time_t? retransmit_time=null¶
The time, in milliseconds, that is advertised as the retrans-timer in RA messages and that hosts use for address resolution and the Neighbor Unreachability Detection algorithm. It represents the time between retransmitted NS messages. A value of zero means unspecified by this router.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role_router_lifetime_t? router_lifetime=null¶
The lifetime in seconds that is advertised as the router lifetime in RA messages. This indicates the time period for which the advertising router can be used as a default router/gateway. A value of 0 means the router should not be used as a default gateway. :rel parent_router_advertisement: Relation to parent container :rel prefix: The list of IPv6 prefixes to advertise in the router advertisement messages.
- relation nokia_srlinux::interface::subinterface::ipv6::RouterAdvertisement parent_router_advertisement [1]¶
Relation to parent container Peer relation: IPv6 router advertisement options that apply when the role of the interface is a router interface.
other end:
nokia_srlinux::interface::subinterface::ipv6::RouterAdvertisement.router_role [0:1]
- relation nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::Prefix prefix [0:16]¶
Relation to parent container Peer relation: The list of IPv6 prefixes to advertise in the router advertisement messages.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::Prefix¶
Parents:
nokia_srlinux::Base
The list of IPv6 prefixes to advertise in the router advertisement messages. Yang definition can be found here: srl_nokia-interfaces-router-adv.yang:L124
- attribute bool? autonomous_flag=null¶
When this is set in the prefix information option hosts can use the prefix for stateless address autoconfiguration (SLAAC).
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix ipv6_prefix¶
An IPv6 global unicast address prefix.
- attribute bool? on_link_flag=null¶
When this is set in the prefix information option hosts can use the prefix for on-link determination.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::prefix_preferred_lifetime_t? preferred_lifetime=null¶
The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred.
- attribute nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::prefix_valid_lifetime_t? valid_lifetime=null¶
The length of time in seconds (relative to the time the packet is sent) that the prefix is valid for the purpose of on-link determination. :rel parent_router_role: Relation to parent container
- relation nokia_srlinux::interface::subinterface::ipv6::router_advertisement::RouterRole parent_router_role [1]¶
Relation to parent container Peer relation: The list of IPv6 prefixes to advertise in the router advertisement messages.
other end:
nokia_srlinux::interface::subinterface::ipv6::router_advertisement::RouterRole.prefix [0:16]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::ra_guard::VlanList¶
Parents:
nokia_srlinux::Base
List of VLAN IDs that the RA policy should be matched against Yang definition can be found here: srl_nokia-ra_guard.yang:L131
- attribute nokia_srlinux::interface::subinterface::ra_guard::vlan_list_vlan_id_t vlan_id¶
- Rel parent_ra_guard:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::RaGuard parent_ra_guard [1]¶
Relation to parent container Peer relation: List of VLAN IDs that the RA policy should be matched against
other end:
nokia_srlinux::interface::subinterface::RaGuard.vlan_list [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::Encap¶
Parents:
nokia_srlinux::Base
VLAN match parmeters for the associated subinterface. Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L345
- Rel double_tagged:
When present, double-tagged frames with a specific, non-zero, outer and inner VLAN ID values are
associated to the subinterface
The outer and inner VLAN ID tags are considered service delimiting tags and are by default stripped at ingress and restored/added on egress. :rel parent_vlan: Relation to parent container :rel single_tagged: When present, tagged frames with a specific, non-zero, outer VLAN ID are associated to the subinterface
The outer VLAN-ID tag is considered service delimiting and it is by default stripped at ingress and restored/added on egress. :rel single_tagged_range: When present, tagged frames with a specific, non-zero, outer VLAN ID contained in a specified set of range are associated to the subinterface.
The outer VLAN ID tag of the frame is not stripped off on ingress, and no tag is pushed on egress. :rel untagged: When present, untagged frames and VLAN ID 0 priority tagged frames are associated to the subinterface when it belongs to an interface with vlan-tagging enabled.
- relation nokia_srlinux::interface::subinterface::Vlan parent_vlan [1]¶
Relation to parent container Peer relation: VLAN match parmeters for the associated subinterface.
other end:
nokia_srlinux::interface::subinterface::Vlan.encap [0:1]
- relation nokia_srlinux::interface::subinterface::vlan::encap::DoubleTagged double_tagged [0:1]¶
Relation to parent container Peer relation: When present, double-tagged frames with a specific, non-zero, outer and inner VLAN ID values are associated to the subinterface
The outer and inner VLAN ID tags are considered service delimiting tags and are by default stripped at ingress and restored/added on egress.
other end:
nokia_srlinux::interface::subinterface::vlan::encap::DoubleTagged.parent_encap [1]
- relation nokia_srlinux::interface::subinterface::vlan::encap::SingleTagged single_tagged [0:1]¶
Relation to parent container Peer relation: When present, tagged frames with a specific, non-zero, outer VLAN ID are associated to the subinterface
The outer VLAN-ID tag is considered service delimiting and it is by default stripped at ingress and restored/added on egress.
other end:
nokia_srlinux::interface::subinterface::vlan::encap::SingleTagged.parent_encap [1]
- relation nokia_srlinux::interface::subinterface::vlan::encap::SingleTaggedRange single_tagged_range [0:1]¶
Relation to parent container Peer relation: When present, tagged frames with a specific, non-zero, outer VLAN ID contained in a specified set of range are associated to the subinterface.
The outer VLAN ID tag of the frame is not stripped off on ingress, and no tag is pushed on egress.
other end:
nokia_srlinux::interface::subinterface::vlan::encap::SingleTaggedRange.parent_encap [1]
- relation nokia_srlinux::interface::subinterface::vlan::encap::Untagged untagged [0:1]¶
Relation to parent container Peer relation: When present, untagged frames and VLAN ID 0 priority tagged frames are associated to the subinterface when it belongs to an interface with vlan-tagging enabled.
other end:
nokia_srlinux::interface::subinterface::vlan::encap::Untagged.parent_encap [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::VlanDiscovery¶
Parents:
nokia_srlinux::Base
When present the subinterface should perform vlan discovery by broadcasting dhcp message on all vlanids Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L502
- attribute nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_discovery_address_type? type=null¶
Types of addresses over which vlan discovery is performed :rel parent_vlan: Relation to parent container
- relation nokia_srlinux::interface::subinterface::Vlan parent_vlan [1]¶
Relation to parent container Peer relation: When present the subinterface should perform vlan discovery by broadcasting dhcp message on all vlanids
other end:
nokia_srlinux::interface::subinterface::Vlan.vlan_discovery [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::encap::DoubleTagged¶
Parents:
nokia_srlinux::Base
When present, double-tagged frames with a specific, non-zero, outer and inner VLAN ID values are associated to the subinterface
The outer and inner VLAN ID tags are considered service delimiting tags and are by default stripped at ingress and restored/added on egress. Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L390
- attribute nokia_srlinux::interface::subinterface::vlan::encap::double_tagged_inner_vlan_id_t? inner_vlan_id=null¶
VLAN identifier for single-tagged packets.
- attribute nokia_srlinux::interface::subinterface::vlan::encap::double_tagged_outer_vlan_id_t? outer_vlan_id=null¶
VLAN identifier for single-tagged packets. :rel parent_encap: Relation to parent container
- relation nokia_srlinux::interface::subinterface::vlan::Encap parent_encap [1]¶
Relation to parent container Peer relation: When present, double-tagged frames with a specific, non-zero, outer and inner VLAN ID values are associated to the subinterface
The outer and inner VLAN ID tags are considered service delimiting tags and are by default stripped at ingress and restored/added on egress.
other end:
nokia_srlinux::interface::subinterface::vlan::Encap.double_tagged [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::encap::SingleTagged¶
Parents:
nokia_srlinux::Base
When present, tagged frames with a specific, non-zero, outer VLAN ID are associated to the subinterface
The outer VLAN-ID tag is considered service delimiting and it is by default stripped at ingress and restored/added on egress. Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L348
- attribute nokia_srlinux::interface::subinterface::vlan::encap::single_tagged_vlan_id_t? vlan_id=null¶
VLAN identifier for single-tagged packets. :rel parent_encap: Relation to parent container
- relation nokia_srlinux::interface::subinterface::vlan::Encap parent_encap [1]¶
Relation to parent container Peer relation: When present, tagged frames with a specific, non-zero, outer VLAN ID are associated to the subinterface
The outer VLAN-ID tag is considered service delimiting and it is by default stripped at ingress and restored/added on egress.
other end:
nokia_srlinux::interface::subinterface::vlan::Encap.single_tagged [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::encap::SingleTaggedRange¶
Parents:
nokia_srlinux::Base
When present, tagged frames with a specific, non-zero, outer VLAN ID contained in a specified set of range are associated to the subinterface.
The outer VLAN ID tag of the frame is not stripped off on ingress, and no tag is pushed on egress. Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L371
- Rel low_vlan_id:
- Rel parent_encap:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::vlan::encap::single_tagged_range::LowVlanId low_vlan_id [1:8]¶
Peer relation: Relation to parent container
- relation nokia_srlinux::interface::subinterface::vlan::Encap parent_encap [1]¶
Relation to parent container Peer relation: When present, tagged frames with a specific, non-zero, outer VLAN ID contained in a specified set of range are associated to the subinterface.
The outer VLAN ID tag of the frame is not stripped off on ingress, and no tag is pushed on egress.
other end:
nokia_srlinux::interface::subinterface::vlan::Encap.single_tagged_range [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::encap::Untagged¶
Parents:
nokia_srlinux::Base
When present, untagged frames and VLAN ID 0 priority tagged frames are associated to the subinterface when it belongs to an interface with vlan-tagging enabled. Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L356
- Rel parent_encap:
Relation to parent container
- relation nokia_srlinux::interface::subinterface::vlan::Encap parent_encap [1]¶
Relation to parent container Peer relation: When present, untagged frames and VLAN ID 0 priority tagged frames are associated to the subinterface when it belongs to an interface with vlan-tagging enabled.
other end:
nokia_srlinux::interface::subinterface::vlan::Encap.untagged [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::interface::subinterface::vlan::encap::single_tagged_range::LowVlanId¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-interfaces-vlans.yang:L195
- attribute nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_id? high_vlan_id=null¶
The high-value VLAN identifier in a range for single-tagged packets. The range is matched inclusively.
- attribute nokia_srlinux::types::srl_nokia_interfaces_vlans::vlan_id range_low_vlan_id¶
The low-value VLAN identifier in a range for single-tagged packets. The range is matched inclusively. :rel parent_single_tagged_range: Relation to parent container
- relation nokia_srlinux::interface::subinterface::vlan::encap::SingleTaggedRange parent_single_tagged_range [1]¶
Peer relation: Relation to parent container
other end:
nokia_srlinux::interface::subinterface::vlan::encap::SingleTaggedRange.low_vlan_id [1:8]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::AggregateRoutes¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-aggregate-routes.yang:L34
- Rel parent_network_instance:
Relation to parent container
- Rel route:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.aggregate_routes [0:1]
- relation nokia_srlinux::network_instance::aggregate_routes::Route route [0:16384]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::aggregate_routes::Route.parent_aggregate_routes [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::BridgeTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-network-instance.yang:L617
- attribute bool? discard_unknown_dest_mac=null¶
Discard frames with unknown destination mac addresses. The source mac address of the discarded frame is learned as long as the mac is valid, mac-learning is enabled, and the number of entries has not reached the maximum-entries threshold.
- attribute bool? protect_anycast_gw_mac=null¶
Protect anycast gateway mac’s installed in the FDB, when this mac-vrf is part of an IRB. :rel mac_duplication: Configuration of the MAC duplication procedures. :rel mac_learning: :rel mac_limit: Bridge Table size and thresholds. :rel parent_network_instance: Relation to parent container :rel proxy_arp: :rel proxy_nd: :rel split_horizon_group: Split-horizon-group information. :rel static_mac:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.bridge_table [0:1]
- relation nokia_srlinux::network_instance::bridge_table::MacDuplication mac_duplication [0:1]¶
Relation to parent container Peer relation: Configuration of the MAC duplication procedures.
other end:
nokia_srlinux::network_instance::bridge_table::MacDuplication.parent_bridge_table [1]
- relation nokia_srlinux::network_instance::bridge_table::MacLearning mac_learning [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::MacLearning.parent_bridge_table [1]
- relation nokia_srlinux::network_instance::bridge_table::MacLimit mac_limit [0:1]¶
Relation to parent container Peer relation: Bridge Table size and thresholds.
other end:
nokia_srlinux::network_instance::bridge_table::MacLimit.parent_bridge_table [1]
- relation nokia_srlinux::network_instance::bridge_table::ProxyArp proxy_arp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::ProxyArp.parent_bridge_table [1]
- relation nokia_srlinux::network_instance::bridge_table::ProxyNd proxy_nd [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::ProxyNd.parent_bridge_table [1]
- relation nokia_srlinux::network_instance::bridge_table::SplitHorizonGroup split_horizon_group [0:8]¶
Relation to parent container Peer relation: Split-horizon-group information.
other end:
nokia_srlinux::network_instance::bridge_table::SplitHorizonGroup.parent_bridge_table [1]
- relation nokia_srlinux::network_instance::bridge_table::StaticMac static_mac [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::StaticMac.parent_bridge_table [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupBridgeTableYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::ConnectionPoint¶
Parents:
nokia_srlinux::Base
Connection-point information. Yang definition can be found here: srl_nokia-connection-point.yang:L27
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A unique name identifying the connection-point :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Connection-point information.
other end:
nokia_srlinux::NetworkInstance.connection_point [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::InterInstancePolicies¶
Parents:
nokia_srlinux::Base
Policies for leaking routes between this network instance and other network instances Yang definition can be found here: srl_nokia-network-instance.yang:L325
- Rel apply_policy:
Container for specifying route leaking import and export policies
- Rel parent_network_instance:
Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Policies for leaking routes between this network instance and other network instances
other end:
nokia_srlinux::NetworkInstance.inter_instance_policies [0:1]
- relation nokia_srlinux::network_instance::inter_instance_policies::ApplyPolicy apply_policy [0:1]¶
Relation to parent container Peer relation: Container for specifying route leaking import and export policies
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::Interface¶
Parents:
nokia_srlinux::Base
List of subinterfaces used by this network-instance Yang definition can be found here: srl_nokia-network-instance.yang:L404
- attribute string? connection_point=null¶
- attribute nokia_srlinux::types::srl_nokia_network_instance::network_instance_subintf_name name¶
Name of the subinterface bound to this network-instance :rel bridge_table: :rel interface_ref: Reference to a subinterface :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: List of subinterfaces used by this network-instance
- relation nokia_srlinux::network_instance::interface::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::interface::BridgeTable.parent_interface [1]
- relation nokia_srlinux::network_instance::interface::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::interface::InterfaceRef.parent_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupInterfaceYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::IpForwarding¶
Parents:
nokia_srlinux::Base
Forwarding options that apply to the entire network instance. Yang definition can be found here: srl_nokia-network-instance.yang:L254
- attribute bool? receive_ipv4_check=null¶
If set to true then the following check is done on every subinterface of the network-instance: if an IPv4 packet is received on a subinterface and the IPv4 oper-status of this subinterface is down the packet is discarded. If this leaf is set to false then received IPv4 packets are accepted on all subinterfaces of the network-instance that are up, even if they do not have any IPv4 addresses.
- attribute bool? receive_ipv6_check=null¶
If set to true then the following check is done on every subinterface of the network-instance: if an IPv6 packet is received on a subinterface and the IPv6 oper-status of this subinterface is down the packet is discarded. If this leaf is set to false then received IPv6 packets are accepted on all subinterfaces of the network-instance that are up, even if they do not have any IPv6 addresses. :rel last_resort_lookup: :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Forwarding options that apply to the entire network instance.
other end:
nokia_srlinux::NetworkInstance.ip_forwarding [0:1]
- relation nokia_srlinux::network_instance::ip_forwarding::LastResortLookup last_resort_lookup [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::ip_forwarding::LastResortLookup.parent_ip_forwarding [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupIpForwardingYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::IpLoadBalancing¶
Parents:
nokia_srlinux::Base
Container for IP load-balancing options that are specific to the network-instance Yang definition can be found here: srl_nokia-network-instance.yang:L287
- Rel parent_network_instance:
Relation to parent container
- Rel resilient_hash_prefix:
List of IPv4 and IPv6 prefixes which should be programmed for resilient ECMP hashing.
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Container for IP load-balancing options that are specific to the network-instance
other end:
nokia_srlinux::NetworkInstance.ip_load_balancing [0:1]
- relation nokia_srlinux::network_instance::ip_load_balancing::ResilientHashPrefix resilient_hash_prefix [0:*]¶
Relation to parent container Peer relation: List of IPv4 and IPv6 prefixes which should be programmed for resilient ECMP hashing.
other end:
nokia_srlinux::network_instance::ip_load_balancing::ResilientHashPrefix.parent_ip_load_balancing [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::MaintenancePolicies¶
Parents:
nokia_srlinux::Base
Container with maintenance policies Yang definition can be found here: srl_nokia-maintenance-policies.yang:L32
- Rel parent_network_instance:
Relation to parent container
- Rel policy:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Container with maintenance policies
other end:
nokia_srlinux::NetworkInstance.maintenance_policies [0:1]
- relation nokia_srlinux::network_instance::maintenance_policies::Policy policy [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::maintenance_policies::Policy.parent_maintenance_policies [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::Mpls¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mpls.yang:L67
- attribute bool? icmp_tunneling=null¶
When enabled, ICMP messages generated by the router acting in the role of a transit LSR are injected in the forward direction of the LSP, to be turned around and sent back to the sender of the IP payload by the egress LER. If a transit LSR receives an MPLS packet that cannot be forwarded (e.g. label TTL has expired, or the egress subinterface MPLS MTU was exceeded) and the MPLS packet has an IP payload, the router will generate an appropriate ICMP error message. When icmp-tunneling is ‘false’ the ICMP error message is dropped if there is no IP route back to the source in the network-instance that received the MPLS packet.
- attribute string? static_label_block=null¶
- Rel ndk_label_block:
- rel parent_network_instance:
Relation to parent container :rel static_entry:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.mpls [0:1]
- relation nokia_srlinux::network_instance::mpls::NdkLabelBlock ndk_label_block [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::mpls::NdkLabelBlock.parent_mpls [1]
- relation nokia_srlinux::network_instance::mpls::StaticEntry static_entry [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::mpls::StaticEntry.parent_mpls [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupMplsYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::MplsForwarding¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-network-instance.yang:L240
- attribute bool? forward_received_packets=null¶
When set to true, MPLS packets received on any subinterface of the network-instance will be forwarded according to the matching ILM entries. When set to false, MPLS packets are discarded if received on any subinterface of the network-instance. In the default network-instance the default is ‘true’. :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.mpls_forwarding [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::Mtu¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state data related to network-instance MTU Yang definition can be found here: srl_nokia-network-instance-mtu.yang:L58
- attribute bool? path_mtu_discovery=null¶
Enables or disables path MTU discovery in this network-instance This is controlled via the kernel ip_no_pmtu_disc option. Path MTU discovery (PMTUD) is a standardized technique in networking for determining the MTU size on the network path between two hosts, usually with the goal of avoiding IP fragmentation. For IPv4 packets, Path MTU discovery works by setting the Don’t Fragment (DF) flag bit in the IP headers of outgoing packets. Then, any device along the path whose MTU is smaller than the packet will drop it, and send back an Internet Control Message Protocol (ICMP) Fragmentation Needed (Type 3, Code 4) message containing its MTU, allowing the source host to reduce its Path MTU appropriately. The process is repeated until the MTU is small enough to traverse the entire path without fragmentation. :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to network-instance MTU
other end:
nokia_srlinux::NetworkInstance.mtu [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupMtuYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::MulticastL3Vpn¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L340
- attribute nokia_srlinux::types::srl_nokia_mvpn_l3::auto_discovery_type? auto_discovery=null¶
set the auto discovery type for this mvpn
- attribute nokia_srlinux::types::srl_nokia_mvpn_l3::c_multicast_route_type? c_multicast_route=null¶
set the customer multicast routing type for this mvpn :rel bgp: :rel parent_network_instance: Relation to parent container :rel provider_tunnel:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.multicast_l3_vpn [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::Bgp bgp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::Bgp.parent_multicast_l3_vpn [1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel provider_tunnel [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel.parent_multicast_l3_vpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::NextHopGroups¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-next-hop-groups.yang:L50
- Rel group:
Specifies the next hop group.
- Rel parent_network_instance:
Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.next_hop_groups [0:1]
- relation nokia_srlinux::network_instance::next_hop_groups::Group group [0:*]¶
Relation to parent container Peer relation: Specifies the next hop group.
other end:
nokia_srlinux::network_instance::next_hop_groups::Group.parent_next_hop_groups [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupNextHopGroupsYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::PolicyForwarding¶
Parents:
nokia_srlinux::Base
Configuration and operational state relating to policy-forwarding within a network instance. Yang definition can be found here: srl_nokia-policy-forwarding.yang:L218
- Rel interface:
List of subinterfaces that use the policy forwarding policy.
- Rel parent_network_instance:
Relation to parent container
- Rel policy:
A forwarding policy is defined to have a set of match criteria, allowing particular fields of a packet’s header to be matched, and a set of forwarding actions which determines how the local system should forward the packet.
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Configuration and operational state relating to policy-forwarding within a network instance.
other end:
nokia_srlinux::NetworkInstance.policy_forwarding [0:1]
- relation nokia_srlinux::network_instance::policy_forwarding::Interface interface [0:*]¶
Relation to parent container Peer relation: List of subinterfaces that use the policy forwarding policy.
other end:
nokia_srlinux::network_instance::policy_forwarding::Interface.parent_policy_forwarding [1]
- relation nokia_srlinux::network_instance::policy_forwarding::Policy policy [0:4]¶
Relation to parent container Peer relation: A forwarding policy is defined to have a set of match criteria, allowing particular fields of a packet’s header to be matched, and a set of forwarding actions which determines how the local system should forward the packet.
other end:
nokia_srlinux::network_instance::policy_forwarding::Policy.parent_policy_forwarding [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::Protocols¶
Parents:
nokia_srlinux::Base
The routing protocols that are enabled for this network-instance. Yang definition can be found here: srl_nokia-network-instance.yang:L593
- Rel bgp:
- Rel bgp_evpn:
- Rel bgp_ipvpn:
- Rel bgp_vpn:
- Rel directly_connected:
Container for handling directly connected routes as a pseudo-protocol
- Rel gribi:
Container for gRIBI configuration and state.
- Rel igmp:
- Rel igmp_snooping:
- Rel isis:
- Rel ldp:
Container for LDP configuration and state.
- Rel linux:
Enables routing interaction with the Linux kernel
- Rel mld:
- Rel mld_snooping:
- Rel ospf:
Top-level configuration and operational state for
Open Shortest Path First (OSPF) :rel parent_network_instance: Relation to parent container :rel pim:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: The routing protocols that are enabled for this network-instance.
- relation nokia_srlinux::network_instance::protocols::Bgp bgp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Bgp.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::BgpEvpn bgp_evpn [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::BgpEvpn.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::BgpIpvpn bgp_ipvpn [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::BgpIpvpn.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::BgpVpn bgp_vpn [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::BgpVpn.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::DirectlyConnected directly_connected [0:1]¶
Relation to parent container Peer relation: Container for handling directly connected routes as a pseudo-protocol
other end:
nokia_srlinux::network_instance::protocols::DirectlyConnected.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Gribi gribi [0:1]¶
Relation to parent container Peer relation: Container for gRIBI configuration and state.
other end:
nokia_srlinux::network_instance::protocols::Gribi.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Igmp igmp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Igmp.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::IgmpSnooping igmp_snooping [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::IgmpSnooping.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Isis isis [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Isis.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Ldp ldp [0:1]¶
Relation to parent container Peer relation: Container for LDP configuration and state.
other end:
nokia_srlinux::network_instance::protocols::Ldp.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Linux linux [0:1]¶
Relation to parent container Peer relation: Enables routing interaction with the Linux kernel
other end:
nokia_srlinux::network_instance::protocols::Linux.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Mld mld [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Mld.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::MldSnooping mld_snooping [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::MldSnooping.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Ospf ospf [0:1]¶
Relation to parent container Peer relation: Top-level configuration and operational state for Open Shortest Path First (OSPF)
other end:
nokia_srlinux::network_instance::protocols::Ospf.parent_protocols [1]
- relation nokia_srlinux::network_instance::protocols::Pim pim [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Pim.parent_protocols [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupProtocolsYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::SegmentRouting¶
Parents:
nokia_srlinux::Base
Container with segment routing configuration options Yang definition can be found here: srl_nokia-segment-routing.yang:L117
- Rel mpls:
Adding this container activates datapath support for SR-MPLS
- Rel parent_network_instance:
Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Container with segment routing configuration options
other end:
nokia_srlinux::NetworkInstance.segment_routing [0:1]
- relation nokia_srlinux::network_instance::segment_routing::Mpls mpls [0:1]¶
Relation to parent container Peer relation: Adding this container activates datapath support for SR-MPLS
other end:
nokia_srlinux::network_instance::segment_routing::Mpls.parent_segment_routing [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::StaticRoutes¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-static-routes.yang:L38
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
- Rel parent_network_instance:
Relation to parent container :rel route:
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::NetworkInstance.static_routes [0:1]
- relation nokia_srlinux::network_instance::static_routes::Route route [0:16384]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::static_routes::Route.parent_static_routes [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::network_instance::setupStaticRoutesYangContainer
constrainttrue
- entity nokia_srlinux::network_instance::TrafficEngineering¶
Parents:
nokia_srlinux::Base
Container with traffic engineering options for the network-instance Yang definition can be found here: srl_nokia-traffic-engineering.yang:L132
- attribute nokia_srlinux::types::srl_nokia_common::as_number? autonomous_system=null¶
The autonomous system number of the network-instance, for protocols and pseudo-protocols that do not have their own configuration of AS number.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? ipv4_te_router_id=null¶
A routable IPv4 address to identify the router uniquely in a TE domain.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? ipv6_te_router_id=null¶
A routable IPv6 address to identify the router uniquely in a TE domain. :rel admin_groups: Container for configuring admin groups :rel interface: List of routed subinterfaces that have associated TE information :rel parent_network_instance: Relation to parent container :rel pcep: Top-level configuration and operational state for Path Computation Element Protocol (PCEP) :rel shared_risk_link_groups: Container for configuring SRLGs
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Container with traffic engineering options for the network-instance
other end:
nokia_srlinux::NetworkInstance.traffic_engineering [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::AdminGroups admin_groups [0:1]¶
Relation to parent container Peer relation: Container for configuring admin groups
other end:
nokia_srlinux::network_instance::traffic_engineering::AdminGroups.parent_traffic_engineering [1]
- relation nokia_srlinux::network_instance::traffic_engineering::Interface interface [0:*]¶
Relation to parent container Peer relation: List of routed subinterfaces that have associated TE information
other end:
nokia_srlinux::network_instance::traffic_engineering::Interface.parent_traffic_engineering [1]
- relation nokia_srlinux::network_instance::traffic_engineering::Pcep pcep [0:1]¶
Relation to parent container Peer relation: Top-level configuration and operational state for Path Computation Element Protocol (PCEP)
other end:
nokia_srlinux::network_instance::traffic_engineering::Pcep.parent_traffic_engineering [1]
Relation to parent container Peer relation: Container for configuring SRLGs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::TrafficEngineeringPolicies¶
Parents:
nokia_srlinux::Base
Container with traffic engineering policies Yang definition can be found here: srl_nokia-te-policies.yang:L369
- Rel binding_sid:
Configuration and state related to the label block(s) used for the binding SIDs associated with TE policies
- Rel explicit_paths:
Named paths used to specify SR policy segment lists
- Rel parent_network_instance:
Relation to parent container
- Rel policy:
List of traffic engineering policies
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Container with traffic engineering policies
other end:
nokia_srlinux::NetworkInstance.traffic_engineering_policies [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::BindingSid binding_sid [0:1]¶
Relation to parent container Peer relation: Configuration and state related to the label block(s) used for the binding SIDs associated with TE policies
- relation nokia_srlinux::network_instance::traffic_engineering_policies::ExplicitPaths explicit_paths [0:1]¶
Relation to parent container Peer relation: Named paths used to specify SR policy segment lists
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy policy [0:*]¶
Relation to parent container Peer relation: List of traffic engineering policies
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::VxlanInterface¶
Parents:
nokia_srlinux::Base
List of vxlan-interfaces used by this network-instance Yang definition can be found here: srl_nokia-network-instance.yang:L551
- attribute nokia_srlinux::types::srl_nokia_network_instance::network_instance_vxlan_if_ref name¶
Identifier of vxlan-interface used in this network-instance :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: List of vxlan-interfaces used by this network-instance
other end:
nokia_srlinux::NetworkInstance.vxlan_interface [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::aggregate_routes::Route¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-aggregate-routes.yang:L36
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf contains the configured, desired state of the aggregate prefix.
- attribute bool? generate_icmp=null¶
When set to true the router generares ICMP unreachable messages for packets matching the aggregate route (and not a more specific route).
- attribute nokia_srlinux::network_instance::aggregate_routes::route_prefix_t prefix¶
- attribute bool? summary_only=null¶
When set to true the router blocks the advertisement of all contributing routes of this aggregate route in dynamic protocols such as BGP. :rel aggregator: :rel communities: :rel parent_aggregate_routes: Relation to parent container
- relation nokia_srlinux::network_instance::AggregateRoutes parent_aggregate_routes [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::AggregateRoutes.route [0:16384]
- relation nokia_srlinux::network_instance::aggregate_routes::route::Aggregator aggregator [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::aggregate_routes::route::Aggregator.parent_route [1]
- relation nokia_srlinux::network_instance::aggregate_routes::route::Communities communities [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::aggregate_routes::route::Communities.parent_route [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::aggregate_routes::route::Aggregator¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-aggregate-routes.yang:L71
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? address=null¶
Specifies the aggregator’s IP address.
- attribute nokia_srlinux::network_instance::aggregate_routes::route::aggregator_as_number_t? as_number=null¶
Specifies the aggregator’s ASN :rel parent_route: Relation to parent container
- relation nokia_srlinux::network_instance::aggregate_routes::Route parent_route [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::aggregate_routes::Route.aggregator [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::aggregate_routes::route::Communities¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-aggregate-routes.yang:L85
- attribute nokia_srlinux::network_instance::aggregate_routes::route::communities_add_t[]? add=null¶
- Rel parent_route:
Relation to parent container
- relation nokia_srlinux::network_instance::aggregate_routes::Route parent_route [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::aggregate_routes::Route.communities [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::MacDuplication¶
Parents:
nokia_srlinux::Base
Configuration of the MAC duplication procedures. Yang definition can be found here: srl_nokia-bridge-table-mac-duplication.yang:L28
- attribute nokia_srlinux::network_instance::bridge_table::mac_duplication_action_t? action=null¶
Action to take on the subinterface (if action is use-net-instance-action) upon detecting at least one mac addresses as duplicate on the subinterface. In particular: - oper-down: if configured, upon detecting a duplicate mac on the subinterface, the subinterface will be brought oper-down, with oper-down-reason mac-dup-detected. The duplicate macs on the interface will be kept in CPM though, and shown in the duplicate-entries state. In this case, arriving frames on a different subinterface with the duplicate mac as source mac are dropped. Arriving frames on a different subinterface with a destination mac matching the duplicate mac are dropped. - blackhole: upon detecting a duplicate mac on the subinterface, the mac will be blackholed. Any frame received on this or any other subinterface with source mac matching a blackhole mac will be discarded. Any frame received with destination mac matching the blackhole mac will be discarded, although still processed for source mac learning. - stop-learning: upon detecting a duplicate mac on the subinterface, existing macs are kept (and refreshed) but new macs are no longer learned on this subinterface. The duplicate mac will stay learned on the subinterface. Frames arriving to a different subinterface with a source mac matching the duplicate mac will be dropped. Frames arriving to a different subinterface with a destination mac matching the duplicate mac will be forwarded normally.
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the mac-duplication procedures. Mac-duplication detects duplicate macs that move between different subinterfaces or a subinterface and an evpn destination.
- attribute nokia_srlinux::network_instance::bridge_table::mac_duplication_hold_down_time_t? hold_down_time=null¶
Time to wait from the moment a mac is declared duplicate to the mac is flushed from the bridge table. When the duplicate mac is flushed, the monitoring process for the mac is restarted.
- attribute nokia_srlinux::network_instance::bridge_table::mac_duplication_monitoring_window_t? monitoring_window=null¶
Monitoring window for detecting duplication on a given mac address. A mac is declared as duplicate if it exceeds the num-moves within the monitoring-window.
- attribute nokia_srlinux::network_instance::bridge_table::mac_duplication_num_moves_t? num_moves=null¶
Number of moves a mac is allowed within the monitoring-window, before it is declared duplicate. :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation: Configuration of the MAC duplication procedures.
other end:
nokia_srlinux::network_instance::BridgeTable.mac_duplication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::MacLearning¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-mac-learning.yang:L24
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the learning procedures for dynamic mac addresses. If disabled, the existing macs in the bridge-table will be kept (and refreshed if new frames arrive for them) but no new mac addresses will be learned. Frames with unknown mac addresses are not dropped, unless discard-unknown-src-mac is configured. :rel aging: :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::BridgeTable.mac_learning [0:1]
- relation nokia_srlinux::network_instance::bridge_table::mac_learning::Aging aging [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::mac_learning::Aging.parent_mac_learning [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::MacLimit¶
Parents:
nokia_srlinux::Base
Bridge Table size and thresholds. Yang definition can be found here: srl_nokia-bridge-table-mac-limit.yang:L20
- attribute nokia_srlinux::network_instance::bridge_table::mac_limit_maximum_entries_t? maximum_entries=null¶
Maximum number of mac addresses allowed in the bridge-table.
- attribute nokia_srlinux::network_instance::bridge_table::mac_limit_warning_threshold_pct_t? warning_threshold_pct=null¶
Percentage of the configured max-number-macs over which a warning is triggered. The warning message is cleared when the percentage drops below the configured percentage minus 5% :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation: Bridge Table size and thresholds.
other end:
nokia_srlinux::network_instance::BridgeTable.mac_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::ProxyArp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L682
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the layer-2 proxy ARP/ND table
- attribute bool? process_arp_probes=null¶
Determines whether the router processes ARP probe messages. When set to true, ARP probe messages used by the hosts for Duplicate Address Detection are processed, replied if a proxy-arp entry is hit or reinjected into the data path. When set to false, ARP probe messages are flooded to the remote nodes if unknown-arp-requests are configured to be flooded. ARP probe messages are identified as ARP Requests that use IP address 0.0.0.0 as sender’s address.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp_table_size_t? table_size=null¶
Maximum number of entries allowed in the proxy table of the network-instance :rel dynamic_learning: :rel evpn: How proxy arp interacts with evpn :rel ip_duplication: Configuration of the proxy ARP/ND IP duplication procedures :rel parent_bridge_table: Relation to parent container :rel static_entries: :rel trace_options: Debug trace-options for Proxy-ARP
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::BridgeTable.proxy_arp [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::DynamicLearning dynamic_learning [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::DynamicLearning.parent_proxy_arp [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn evpn [0:1]¶
Relation to parent container Peer relation: How proxy arp interacts with evpn
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn.parent_proxy_arp [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::IpDuplication ip_duplication [0:1]¶
Relation to parent container Peer relation: Configuration of the proxy ARP/ND IP duplication procedures
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::IpDuplication.parent_proxy_arp [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::StaticEntries static_entries [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::StaticEntries.parent_proxy_arp [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Debug trace-options for Proxy-ARP
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::TraceOptions.parent_proxy_arp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::ProxyNd¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L966
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the layer-2 proxy ARP/ND table
- attribute bool? process_dad_neighbor_solicitations=null¶
Determines whether the router processes Neighbor Soliciation DAD messages When set to true, Neighbor Soliciation DAD messages used by the hosts for Duplicate Address Detection are processed, replied if a proxy ND entry is hit, or reinjected into the data path. When set to false, Neighbor Solicitation DAD messages are flooded to the remote nodes if unknown-neighbor-solicitation is configured so that unknown Neighbor Solicitation messages are flooded.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd_table_size_t? table_size=null¶
Maximum number of entries allowed in the proxy table of the network-instance :rel dynamic_learning: :rel evpn: How proxy ARP/ND interacts with EVPN :rel ip_duplication: Configuration of the proxy ARP/ND IP duplication procedures :rel parent_bridge_table: Relation to parent container :rel static_entries: :rel trace_options: Debug traceoptions for Proxy-ARP
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::BridgeTable.proxy_nd [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::DynamicLearning dynamic_learning [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::DynamicLearning.parent_proxy_nd [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn evpn [0:1]¶
Relation to parent container Peer relation: How proxy ARP/ND interacts with EVPN
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn.parent_proxy_nd [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::IpDuplication ip_duplication [0:1]¶
Relation to parent container Peer relation: Configuration of the proxy ARP/ND IP duplication procedures
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::IpDuplication.parent_proxy_nd [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::StaticEntries static_entries [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::StaticEntries.parent_proxy_nd [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Debug traceoptions for Proxy-ARP
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::TraceOptions.parent_proxy_nd [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::SplitHorizonGroup¶
Parents:
nokia_srlinux::Base
Split-horizon-group information. Yang definition can be found here: srl_nokia-bridge-table-shg.yang:L31
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A unique name identifying the split horizon group :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation: Split-horizon-group information.
other end:
nokia_srlinux::network_instance::BridgeTable.split_horizon_group [0:8]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::StaticMac¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-static-mac.yang:L34
- Rel mac:
static macs configured on the bridging instance
- Rel parent_bridge_table:
Relation to parent container
- relation nokia_srlinux::network_instance::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::BridgeTable.static_mac [0:1]
- relation nokia_srlinux::network_instance::bridge_table::static_mac::Mac mac [0:*]¶
Relation to parent container Peer relation: static macs configured on the bridging instance
other end:
nokia_srlinux::network_instance::bridge_table::static_mac::Mac.parent_static_mac [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::mac_learning::Aging¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-mac-learning.yang:L58
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the aging for the dynamic mac entries in the bridge table. If disabled, dynamically learned mac entries will be programmed in the bridge table until the network instance is disabled.
- attribute nokia_srlinux::network_instance::bridge_table::mac_learning::aging_age_time_t? age_time=null¶
Configurable aging time for dynamically learned mac addresses :rel parent_mac_learning: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::MacLearning parent_mac_learning [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::MacLearning.aging [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::DynamicLearning¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L270
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the learning procedures for dynamic ARP/ND entries The dynamic ARP/ND entries are learned out of snooped GARP/ARP/ND messages on bridged sub-interfaces. These entries will be shown as dynamic, as opposed to EVPN entries or static entries. If the admin-state is disabled, the existing ARP/ND entries in the proxy table will be kept (and refreshed).
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::dynamic_learning_age_time_t? age_time=null¶
Aging timer value for the proxy entries When the aging expires, the entry is flushed.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::dynamic_learning_send_refresh_t? send_refresh=null¶
Configures the proxy refresh interval The interval determines the frequency at which the system generates three ARP Requests or Neighbor Solicitations with the intend to refresh the proxy entry. The refresh is sent within the age-time window. :rel parent_proxy_arp: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyArp parent_proxy_arp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::ProxyArp.dynamic_learning [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn¶
Parents:
nokia_srlinux::Base
How proxy arp interacts with evpn Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L156
- Rel flood:
How ARP frames received on a proxy service are flooded into the EVPN network
- Rel internal_tags:
Configuration and state of internal tags
- Rel parent_proxy_arp:
Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyArp parent_proxy_arp [1]¶
Relation to parent container Peer relation: How proxy arp interacts with evpn
other end:
nokia_srlinux::network_instance::bridge_table::ProxyArp.evpn [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::Flood flood [0:1]¶
Relation to parent container Peer relation: How ARP frames received on a proxy service are flooded into the EVPN network
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::Flood.parent_evpn [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::InternalTags.parent_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::IpDuplication¶
Parents:
nokia_srlinux::Base
Configuration of the proxy ARP/ND IP duplication procedures Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L165
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? anti_spoof_mac=null¶
MAC address associated with the optional anti-spoofing mechanism
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::ip_duplication_hold_down_time_t? hold_down_time=null¶
Time to wait from the moment an IP is declared duplicate to the time the IP is removed from the proxy ARP/ND table When the duplicate IP is removed, the monitoring process for the IP address is restarted.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::ip_duplication_monitoring_window_t? monitoring_window=null¶
Monitoring window for detecting duplication on a given ip address in the proxy ARP/ND table An IP is declared duplicate if it exceeds the num-moves within the monitoring-window.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::ip_duplication_num_moves_t? num_moves=null¶
Number of moves in the proxy ARP/ND table that an IP is allowed within the monitoring-window When the number of moves exceeds this value, the IP address is declared duplicate.
- attribute bool? static_blackhole=null¶
Whether the anti-spoof MAC is programmed as a black hole static-mac in the mac-table :rel parent_proxy_arp: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyArp parent_proxy_arp [1]¶
Relation to parent container Peer relation: Configuration of the proxy ARP/ND IP duplication procedures
other end:
nokia_srlinux::network_instance::bridge_table::ProxyArp.ip_duplication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::StaticEntries¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L662
- Rel neighbor:
List of static proxy ARP entries that map an IPv4 address to a MAC address
To configure a static proxy ARP entry a value must be written into this leaf, as well as the link-layer-address leaf. :rel parent_proxy_arp: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyArp parent_proxy_arp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::ProxyArp.static_entries [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::static_entries::Neighbor neighbor [0:*]¶
Relation to parent container Peer relation: List of static proxy ARP entries that map an IPv4 address to a MAC address
To configure a static proxy ARP entry a value must be written into this leaf, as well as the link-layer-address leaf.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::TraceOptions¶
Parents:
nokia_srlinux::Base
Debug trace-options for Proxy-ARP Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L222
- Rel flag:
Tracing parameters
- Rel parent_proxy_arp:
Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyArp parent_proxy_arp [1]¶
Relation to parent container Peer relation: Debug trace-options for Proxy-ARP
other end:
nokia_srlinux::network_instance::bridge_table::ProxyArp.trace_options [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::trace_options::Flag flag [0:*]¶
Relation to parent container Peer relation: Tracing parameters
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::Flood¶
Parents:
nokia_srlinux::Base
How ARP frames received on a proxy service are flooded into the EVPN network Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L136
- attribute bool? gratuitous_arp=null¶
Whether to flood GARP requests or replies into EVPN
- attribute bool? unknown_arp_req=null¶
Whether to flood ARP requests (with source squelching) when there is no hit in the bridge-table-proxy-arp table :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn parent_evpn [1]¶
Relation to parent container Peer relation: How ARP frames received on a proxy service are flooded into the EVPN network
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn.flood [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L120
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn parent_evpn [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::Evpn.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::static_entries::Neighbor¶
Parents:
nokia_srlinux::Base
List of static proxy ARP entries that map an IPv4 address to a MAC address
To configure a static proxy ARP entry a value must be written into this leaf, as well as the link-layer-address leaf. Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L663
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address ipv4_address¶
IPv4 address resolved by the proxy ARP entry To configure a static neighbor entry a value must be written into this leaf, as well as the link-layer-address leaf.
- attribute nokia_srlinux::types::srl_nokia_common::unicast_mac_address? link_layer_address=null¶
The resolving MAC address of the proxy entry To configure a static proxy entry a value must be written into this leaf and the ip-address leaf. :rel parent_static_entries: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::StaticEntries parent_static_entries [1]¶
Relation to parent container Peer relation: List of static proxy ARP entries that map an IPv4 address to a MAC address
To configure a static proxy ARP entry a value must be written into this leaf, as well as the link-layer-address leaf.
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::StaticEntries.neighbor [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_arp::trace_options::Flag¶
Parents:
nokia_srlinux::Base
Tracing parameters Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L225
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::trace_options::flag_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::bridge_table::proxy_arp::trace_options::flag_name_t name¶
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_arp::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::bridge_table::proxy_arp::TraceOptions.flag [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::DynamicLearning¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L270
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the learning procedures for dynamic ARP/ND entries The dynamic ARP/ND entries are learned out of snooped GARP/ARP/ND messages on bridged sub-interfaces. These entries will be shown as dynamic, as opposed to EVPN entries or static entries. If the admin-state is disabled, the existing ARP/ND entries in the proxy table will be kept (and refreshed).
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::dynamic_learning_age_time_t? age_time=null¶
Aging timer value for the proxy entries When the aging expires, the entry is flushed.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::dynamic_learning_send_refresh_t? send_refresh=null¶
Configures the proxy refresh interval The interval determines the frequency at which the system generates three ARP Requests or Neighbor Solicitations with the intend to refresh the proxy entry. The refresh is sent within the age-time window. :rel parent_proxy_nd: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyNd parent_proxy_nd [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::ProxyNd.dynamic_learning [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn¶
Parents:
nokia_srlinux::Base
How proxy ARP/ND interacts with EVPN Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L875
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn_advertise_neighbor_type_t? advertise_neighbor_type=null¶
Whether to advertise router entries or host entries into EVPN MAC/IP routes It also specifies whether to reply to Neighbor Solicitations for EVPN entries with the router flag set or unset. :rel flood: How Neighbor Discovery frames received on a proxy service are flooded into the EVPN network :rel internal_tags: Configuration and state of internal tags :rel parent_proxy_nd: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyNd parent_proxy_nd [1]¶
Relation to parent container Peer relation: How proxy ARP/ND interacts with EVPN
other end:
nokia_srlinux::network_instance::bridge_table::ProxyNd.evpn [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::Flood flood [0:1]¶
Relation to parent container Peer relation: How Neighbor Discovery frames received on a proxy service are flooded into the EVPN network
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::Flood.parent_evpn [1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::InternalTags.parent_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::IpDuplication¶
Parents:
nokia_srlinux::Base
Configuration of the proxy ARP/ND IP duplication procedures Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L165
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? anti_spoof_mac=null¶
MAC address associated with the optional anti-spoofing mechanism
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::ip_duplication_hold_down_time_t? hold_down_time=null¶
Time to wait from the moment an IP is declared duplicate to the time the IP is removed from the proxy ARP/ND table When the duplicate IP is removed, the monitoring process for the IP address is restarted.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::ip_duplication_monitoring_window_t? monitoring_window=null¶
Monitoring window for detecting duplication on a given ip address in the proxy ARP/ND table An IP is declared duplicate if it exceeds the num-moves within the monitoring-window.
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::ip_duplication_num_moves_t? num_moves=null¶
Number of moves in the proxy ARP/ND table that an IP is allowed within the monitoring-window When the number of moves exceeds this value, the IP address is declared duplicate.
- attribute bool? static_blackhole=null¶
Whether the anti-spoof MAC is programmed as a black hole static-mac in the mac-table :rel parent_proxy_nd: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyNd parent_proxy_nd [1]¶
Relation to parent container Peer relation: Configuration of the proxy ARP/ND IP duplication procedures
other end:
nokia_srlinux::network_instance::bridge_table::ProxyNd.ip_duplication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::StaticEntries¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L815
- Rel neighbor:
List of static proxy ND entries that map an IPv6 address to a MAC address
To configure a static proxy ND entry a value must be written into this leaf, as well as the link-layer-address leaf. :rel parent_proxy_nd: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyNd parent_proxy_nd [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::bridge_table::ProxyNd.static_entries [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::static_entries::Neighbor neighbor [0:*]¶
Relation to parent container Peer relation: List of static proxy ND entries that map an IPv6 address to a MAC address
To configure a static proxy ND entry a value must be written into this leaf, as well as the link-layer-address leaf.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::TraceOptions¶
Parents:
nokia_srlinux::Base
Debug traceoptions for Proxy-ARP Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L903
- Rel flag:
Tracing parameters
- Rel parent_proxy_nd:
Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::ProxyNd parent_proxy_nd [1]¶
Relation to parent container Peer relation: Debug traceoptions for Proxy-ARP
other end:
nokia_srlinux::network_instance::bridge_table::ProxyNd.trace_options [0:1]
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::trace_options::Flag flag [0:*]¶
Relation to parent container Peer relation: Tracing parameters
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::Flood¶
Parents:
nokia_srlinux::Base
How Neighbor Discovery frames received on a proxy service are flooded into the EVPN network Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L849
- attribute bool? unknown_neighbor_advertise_host=null¶
Whether to flood Neighbor Advertisement (NA) replies, for type host, into the EVPN network
- attribute bool? unknown_neighbor_advertise_router=null¶
Whether to flood Neighbor Advertisement (NA) replies, for type router, into the EVPN network
- attribute bool? unknown_neighbor_solicitation=null¶
Whether to flood Neighbor Solicitation (NS) messages (with source squelching) into the EVPN network :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn parent_evpn [1]¶
Relation to parent container Peer relation: How Neighbor Discovery frames received on a proxy service are flooded into the EVPN network
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn.flood [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L120
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn parent_evpn [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::Evpn.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::static_entries::Neighbor¶
Parents:
nokia_srlinux::Base
List of static proxy ND entries that map an IPv6 address to a MAC address
To configure a static proxy ND entry a value must be written into this leaf, as well as the link-layer-address leaf. Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L816
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address ipv6_address¶
IPv6 address resolved by the proxy ND entry To configure a static neighbor entry a value must be written into this leaf, as well as the link-layer-address leaf.
- attribute nokia_srlinux::types::srl_nokia_common::unicast_mac_address? link_layer_address=null¶
The resolving MAC address of the proxy entry To configure a static proxy entry a value must be written into this leaf and the ip-address leaf.
- attribute nokia_srlinux::types::srl_nokia_bridge_table_proxy_arp_nd::neighbor_type? type=null¶
The type of the neighbor entry :rel parent_static_entries: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::StaticEntries parent_static_entries [1]¶
Relation to parent container Peer relation: List of static proxy ND entries that map an IPv6 address to a MAC address
To configure a static proxy ND entry a value must be written into this leaf, as well as the link-layer-address leaf.
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::StaticEntries.neighbor [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::proxy_nd::trace_options::Flag¶
Parents:
nokia_srlinux::Base
Tracing parameters Yang definition can be found here: srl_nokia-bridge-table-proxy-arp-nd.yang:L906
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::trace_options::flag_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::bridge_table::proxy_nd::trace_options::flag_name_t name¶
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::proxy_nd::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::bridge_table::proxy_nd::TraceOptions.flag [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::bridge_table::static_mac::Mac¶
Parents:
nokia_srlinux::Base
static macs configured on the bridging instance Yang definition can be found here: srl_nokia-bridge-table-static-mac.yang:L35
- attribute nokia_srlinux::types::srl_nokia_common::mac_address address¶
- attribute nokia_srlinux::network_instance::bridge_table::static_mac::mac_destination_t? destination=null¶
the destination where the mac is programmed against. :rel parent_static_mac: Relation to parent container
- relation nokia_srlinux::network_instance::bridge_table::StaticMac parent_static_mac [1]¶
Relation to parent container Peer relation: static macs configured on the bridging instance
other end:
nokia_srlinux::network_instance::bridge_table::StaticMac.mac [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::inter_instance_policies::ApplyPolicy¶
Parents:
nokia_srlinux::Base
Container for specifying route leaking import and export policies Yang definition can be found here: srl_nokia-network-instance.yang:L329
- attribute string? export_policy=null¶
Policy used to specify the routes of this NI that should be made available for leaking to other NIs
- attribute string? import_policy=null¶
Policy used to specify the routes leaked by other NIs that should be imported into this NI :rel parent_inter_instance_policies: Relation to parent container
- relation nokia_srlinux::network_instance::InterInstancePolicies parent_inter_instance_policies [1]¶
Relation to parent container Peer relation: Container for specifying route leaking import and export policies
other end:
nokia_srlinux::network_instance::InterInstancePolicies.apply_policy [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::interface::BridgeTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-network-instance.yang:L355
- attribute string? split_horizon_group=null¶
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Interface.bridge_table [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::interface::InterfaceRef¶
Parents:
nokia_srlinux::Base
Reference to a subinterface Yang definition can be found here: srl_nokia-network-instance.yang:L431
- attribute string? interface=null¶
Reference to a base interface, for example a port or LAG
- attribute nokia_srlinux::network_instance::interface::interface_ref_subinterface_t? subinterface=null¶
Reference to a subinterface This requires the base interface to be specified using the interface leaf in this container. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::Interface.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::ip_forwarding::LastResortLookup¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-network-instance.yang:L271
- attribute string? network_instance=null¶
A reference to another network-instance in which the system will try to find a matching IP route if this network instance does not have any route to the destination IP :rel parent_ip_forwarding: Relation to parent container
- relation nokia_srlinux::network_instance::IpForwarding parent_ip_forwarding [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::IpForwarding.last_resort_lookup [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::ip_load_balancing::ResilientHashPrefix¶
Parents:
nokia_srlinux::Base
List of IPv4 and IPv6 prefixes which should be programmed for resilient ECMP hashing. Yang definition can be found here: srl_nokia-network-instance.yang:L291
- attribute nokia_srlinux::network_instance::ip_load_balancing::resilient_hash_prefix_hash_buckets_per_path_t? hash_buckets_per_path=null¶
The number of times each next-hop is repeated in the fill pattern if there are max-paths ECMP next-hops A larger number consumes more resources but provides more granularity when flows need to be moved. Note that hash-buckets-per-path * max-paths must be less than or equal to 128.
- attribute nokia_srlinux::network_instance::ip_load_balancing::resilient_hash_prefix_ip_prefix_t ip_prefix¶
IPv4 or IPv6 prefix. Active routes in the FIB that exactly match this prefix or that are longer matches of this prefix are provided with resilient-hash programming.
- attribute nokia_srlinux::network_instance::ip_load_balancing::resilient_hash_prefix_max_paths_t? max_paths=null¶
The maximum number of ECMP next-hops per route associated with the resilient-hash prefix If a matching route has more than this number of ECMP next-hops only the first N are used, where N is the value of this parameter. Note that hash-buckets-per-path * max-paths must be less than or equal to 128. :rel parent_ip_load_balancing: Relation to parent container
- relation nokia_srlinux::network_instance::IpLoadBalancing parent_ip_load_balancing [1]¶
Relation to parent container Peer relation: List of IPv4 and IPv6 prefixes which should be programmed for resilient ECMP hashing.
other end:
nokia_srlinux::network_instance::IpLoadBalancing.resilient_hash_prefix [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::maintenance_policies::Policy¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-maintenance-policies.yang:L37
- attribute nokia_srlinux::types::srl_nokia_common::name maintenance_policy_name¶
A unique identifying name for the maintenance policy :rel parent_maintenance_policies: Relation to parent container :rel seamless_bfd: When present, this node attempts to setup a seamless BFD session on every segment-list of every SR policy that uses maintenance-policy, but only if that SR policy is a primary or standby (secondary) candidate path. The transition of an SBFD session from up to down is a trigger for rerouting traffic around a failed primary path.
- relation nokia_srlinux::network_instance::MaintenancePolicies parent_maintenance_policies [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::MaintenancePolicies.policy [0:*]
- relation nokia_srlinux::network_instance::maintenance_policies::policy::SeamlessBfd seamless_bfd [0:1]¶
Relation to parent container Peer relation: When present, this node attempts to setup a seamless BFD session on every segment-list of every SR policy that uses maintenance-policy, but only if that SR policy is a primary or standby (secondary) candidate path. The transition of an SBFD session from up to down is a trigger for rerouting traffic around a failed primary path.
other end:
nokia_srlinux::network_instance::maintenance_policies::policy::SeamlessBfd.parent_policy [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::maintenance_policies::policy::SeamlessBfd¶
Parents:
nokia_srlinux::Base
When present, this node attempts to setup a seamless BFD session on every segment-list of every SR policy that uses maintenance-policy, but only if that SR policy is a primary or standby (secondary) candidate path. The transition of an SBFD session from up to down is a trigger for rerouting traffic around a failed primary path. Yang definition can be found here: srl_nokia-maintenance-policies.yang:L44
- attribute nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_desired_minimum_transmit_interval_t? desired_minimum_transmit_interval=null¶
The minimum interval between transmission of BFD control packets This value is advertised to the peer, however the actual interval used is specified by taking the maximum of desired-minimum-transmit-interval and the value of the remote required-minimum-receive interval value. This value is specified as an integer number of microseconds.
- attribute nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_detection_multiplier_t? detection_multiplier=null¶
The number of packets that must be missed to declare this session as down The detection interval for the BFD session is calculated by multiplying the value of the negotiated transmission interval by this value.
- attribute yang::types::uint16? hold_down_timer=null¶
Specifies a hold-down timer value when seamless-bfd is enabled This timer is started whenever the SBFD session finishes a transition from up->down->up. While this timer is running the SBFD session state stays in hold-down and the corresponding segment-list stays in sbfd-down state. The default is 3 seconds.
- attribute nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_mode_t? mode=null¶
Specifies requested protection method ecmp-protected is valid for colored te-policies and programs all the valid segment lists and manages their availability using seamless-BFD for each segment list. Switchover between candidate paths is triggered by the node if number of segment-lists up is less than the threshold on the active policy.ecmp-protected is not valid for uncolored sr-policies. linear is valid for uncolored te-policies and triggers fail-over among active segment-lists, primary to standby / secondary.
- attribute yang::types::uint32? return_path_label=null¶
The MPLS label to be used to by the far-end device to return the BFD message This label is added as the bottom value in the segment routing label stack and will be used by the far-end device to return BFD message to the originator. This value could either be a MPLS label or a binding SID that will be used at the far-end to match an appropriate polciy to return the traffic.
- attribute nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_revert_timer_t? revert_timer=null¶
Revert timer for the segment-list
- attribute nokia_srlinux::network_instance::maintenance_policies::policy::seamless_bfd_threshold_t? threshold=null¶
Minimum number of up seamless-BFD sessions for up te-policy
- attribute yang::types::uint16? wait_for_up_timer=null¶
Specifies a wait-for-up timer value when seamless-bfd is enabled This timer is started whenever the sBFD session finishes a transition from down->up. While this timer is running the SBFD session state stays in hold-down and the corresponding segment-list stays in sbfd-down state. The default is 3 seconds. :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::maintenance_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation: When present, this node attempts to setup a seamless BFD session on every segment-list of every SR policy that uses maintenance-policy, but only if that SR policy is a primary or standby (secondary) candidate path. The transition of an SBFD session from up to down is a trigger for rerouting traffic around a failed primary path.
other end:
nokia_srlinux::network_instance::maintenance_policies::Policy.seamless_bfd [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::mpls::NdkLabelBlock¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mpls.yang:L98
- attribute string application_name¶
- attribute string? static_label_block=null¶
- Rel parent_mpls:
Relation to parent container
- relation nokia_srlinux::network_instance::Mpls parent_mpls [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Mpls.ndk_label_block [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::mpls::StaticEntry¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mpls.yang:L126
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to disable the entire static route and all its next-hops.
- attribute bool? collect_stats=null¶
When set to true, stats resources are used to count the number of incoming packets matching the top label value of this static MPLS route
- attribute string? next_hop_group=null¶
- attribute nokia_srlinux::network_instance::mpls::static_entry_operation_t? operation=null¶
The operation to be performed with the top label.
- attribute nokia_srlinux::network_instance::mpls::static_entry_preference_t preference¶
For a given top label value the entry with the lowest preference is selected as the active entry
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved top_label¶
A received MPLS packet, received on any subinterface, matches this static entry if its top label stack entry contains the label value specified by this leaf. :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::Mpls parent_mpls [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Mpls.static_entry [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::Bgp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L106
- Rel bgp_instance:
bgp l3 multicast vpn instances configured in net-instance
currently only single bgp-instance is supported. In future for segmented l3 mvpn multiple bgp instances can be supported :rel parent_multicast_l3_vpn: Relation to parent container
- relation nokia_srlinux::network_instance::MulticastL3Vpn parent_multicast_l3_vpn [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::MulticastL3Vpn.bgp [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::BgpInstance bgp_instance [0:1]¶
Relation to parent container Peer relation: bgp l3 multicast vpn instances configured in net-instance
currently only single bgp-instance is supported. In future for segmented l3 mvpn multiple bgp instances can be supported
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::bgp::BgpInstance.parent_bgp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L333
- Rel inclusive:
- Rel parent_multicast_l3_vpn:
Relation to parent container
- Rel selective:
- relation nokia_srlinux::network_instance::MulticastL3Vpn parent_multicast_l3_vpn [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::MulticastL3Vpn.provider_tunnel [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Inclusive inclusive [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Selective selective [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::bgp::BgpInstance¶
Parents:
nokia_srlinux::Base
bgp l3 multicast vpn instances configured in net-instance
currently only single bgp-instance is supported. In future for segmented l3 mvpn multiple bgp instances can be supported Yang definition can be found here: srl_nokia-mvpn-l3.yang:L107
- attribute string? export_policy=null¶
Policy used to specify the route types that should be made available for leaking to other Network Instances
- attribute nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance_id_t id¶
- attribute string? import_policy=null¶
Policy used to specify the route types to be imported into this network instance MVPN :rel parent_bgp: Relation to parent container :rel route_target: Route Target (RT) of the l3 multicast vpn instance
- relation nokia_srlinux::network_instance::multicast_l3_vpn::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: bgp l3 multicast vpn instances configured in net-instance
currently only single bgp-instance is supported. In future for segmented l3 mvpn multiple bgp instances can be supported
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::Bgp.bgp_instance [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::RouteTarget route_target [0:1]¶
Relation to parent container Peer relation: Route Target (RT) of the l3 multicast vpn instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::RouteTarget¶
Parents:
nokia_srlinux::Base
Route Target (RT) of the l3 multicast vpn instance Yang definition can be found here: srl_nokia-mvpn-l3.yang:L135
- Rel export_rt:
- Rel import_rt:
- Rel parent_bgp_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Route Target (RT) of the l3 multicast vpn instance
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::bgp::BgpInstance.route_target [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::ExportRt export_rt [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::ImportRt import_rt [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::ExportRt¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L141
- attribute nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::export_rt_rt_t? rt=null¶
Import this specific Route Target (RT) in the l3 multicast vpn instance
- attribute bool? unicast=null¶
Enable the unicast vrf-target for the MVPN When enabled, the l3 multicast vpn will export routes with bgp-vpn route target :rel parent_route_target: Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::RouteTarget parent_route_target [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::RouteTarget.export_rt [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::ImportRt¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L158
- attribute nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::import_rt_rt_t? rt=null¶
Import Route Target (RT) in the l3 multicast vpn instance
- attribute bool? unicast=null¶
Enable the unicast vrf-target for the MVPN when enabled the l3 multicast vpn will import routes with bgp-vpn route target :rel parent_route_target: Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::RouteTarget parent_route_target [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::RouteTarget.import_rt [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Inclusive¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L284
- Rel mldp:
multipoint ldp for provider tunnel
- Rel parent_provider_tunnel:
Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel parent_provider_tunnel [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel.inclusive [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::inclusive::Mldp mldp [0:1]¶
Relation to parent container Peer relation: multipoint ldp for provider tunnel
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Selective¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mvpn-l3.yang:L325
- Rel data_rate_threshold:
Enter the data-threshold context
- Rel mldp:
multipoint ldp for provider tunnel
- Rel parent_provider_tunnel:
Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel parent_provider_tunnel [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::ProviderTunnel.selective [0:1]
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::DataRateThreshold data_rate_threshold [0:1]¶
Relation to parent container Peer relation: Enter the data-threshold context
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::Mldp mldp [0:1]¶
Relation to parent container Peer relation: multipoint ldp for provider tunnel
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::inclusive::Mldp¶
Parents:
nokia_srlinux::Base
multipoint ldp for provider tunnel Yang definition can be found here: srl_nokia-mvpn-l3.yang:L181
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable mldp as a provider tunnel :rel parent_inclusive: Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Inclusive parent_inclusive [1]¶
Relation to parent container Peer relation: multipoint ldp for provider tunnel
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Inclusive.mldp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::DataRateThreshold¶
Parents:
nokia_srlinux::Base
Enter the data-threshold context Yang definition can be found here: srl_nokia-mvpn-l3.yang:L291
- Rel group_range:
The data rate threshold to switch an (c-s,c-g) from IPMSI to SPMSI
When an (c-s, c-g) surpasses this threshold, it switches from the inclusive provider tunnel to the selective provider tunnel. :rel parent_selective: Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Selective parent_selective [1]¶
Relation to parent container Peer relation: Enter the data-threshold context
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::GroupRange group_range [0:*]¶
Relation to parent container Peer relation: The data rate threshold to switch an (c-s,c-g) from IPMSI to SPMSI
When an (c-s, c-g) surpasses this threshold, it switches from the inclusive provider tunnel to the selective provider tunnel.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::Mldp¶
Parents:
nokia_srlinux::Base
multipoint ldp for provider tunnel Yang definition can be found here: srl_nokia-mvpn-l3.yang:L181
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable mldp as a provider tunnel :rel parent_selective: Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Selective parent_selective [1]¶
Relation to parent container Peer relation: multipoint ldp for provider tunnel
other end:
nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::Selective.mldp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::GroupRange¶
Parents:
nokia_srlinux::Base
The data rate threshold to switch an (c-s,c-g) from IPMSI to SPMSI
When an (c-s, c-g) surpasses this threshold, it switches from the inclusive provider tunnel to the selective provider tunnel. Yang definition can be found here: srl_nokia-mvpn-l3.yang:L294
- attribute nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::group_range_group_prefix_t group_prefix¶
A multicast IP v4 or v6 prefix for a group range
- attribute nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::group_range_rate_threshold_t? rate_threshold=null¶
Configured throughput rate for a (c-s, c-g) to switch from IPMSI to SPMSI If the rate for a (C-S, C-G) within the specified group range exceeds the threshold, traffic for the (C-S, C-G) is switched to the selective provider tunnel. Threshold 0 is supported. When threshold 0 is configured, the (C-S, C-G) switches to S-PMSI as soon as it is learned in the MVPN and without traffic flowing for that (C-S, C-G) :rel parent_data_rate_threshold: Relation to parent container
- relation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::DataRateThreshold parent_data_rate_threshold [1]¶
Relation to parent container Peer relation: The data rate threshold to switch an (c-s,c-g) from IPMSI to SPMSI
When an (c-s, c-g) surpasses this threshold, it switches from the inclusive provider tunnel to the selective provider tunnel.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::next_hop_groups::Group¶
Parents:
nokia_srlinux::Base
Specifies the next hop group. Yang definition can be found here: srl_nokia-next-hop-groups.yang:L52
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to enable or disable a next-hop group
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Specifies the next hop group name :rel blackhole: :rel nexthop: :rel parent_next_hop_groups: Relation to parent container
- relation nokia_srlinux::network_instance::NextHopGroups parent_next_hop_groups [1]¶
Relation to parent container Peer relation: Specifies the next hop group.
other end:
nokia_srlinux::network_instance::NextHopGroups.group [0:*]
- relation nokia_srlinux::network_instance::next_hop_groups::group::Blackhole blackhole [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::next_hop_groups::group::Blackhole.parent_group [1]
- relation nokia_srlinux::network_instance::next_hop_groups::group::Nexthop nexthop [0:128]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::next_hop_groups::group::Nexthop.parent_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::next_hop_groups::group::Blackhole¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-next-hop-groups.yang:L67
- attribute bool? generate_icmp=null¶
When set to true the router generates ICMP unreachable messages for the dropped packets :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::next_hop_groups::Group parent_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::next_hop_groups::Group.blackhole [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::next_hop_groups::group::Nexthop¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-next-hop-groups.yang:L76
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to enable or disable a particular next-hop
- attribute nokia_srlinux::network_instance::next_hop_groups::group::nexthop_ip_address_t? ip_address=null¶
The next-hop IPv4 or IPv6 address If the IPv6 address is a link-local address then the zoned format must be used
- attribute nokia_srlinux::network_instance::next_hop_groups::group::nexthop_pushed_mpls_label_stack_t[]? pushed_mpls_label_stack=null¶
A list of MPLS labels to push onto the packet when forwarding to this particular next-hop Default is none/empty. Pushing an MPLS label stack is not supported unless the resolve flag is set to false.
- attribute bool? resolve=null¶
When set to true, the router is allowed to use any route to resolve the nexthop address to an outgoing interface When set to false the router is only allowed to use a local route to resolve the next-hop address.
- attribute yang::types::uint16 x_index¶
Numerical index of the next-hop member :rel failure_detection: :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::next_hop_groups::Group parent_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::next_hop_groups::Group.nexthop [0:128]
- relation nokia_srlinux::network_instance::next_hop_groups::group::nexthop::FailureDetection failure_detection [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::next_hop_groups::group::nexthop::FailureDetection¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-next-hop-groups.yang:L123
- Rel enable_bfd:
- Rel parent_nexthop:
Relation to parent container
- relation nokia_srlinux::network_instance::next_hop_groups::group::Nexthop parent_nexthop [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::next_hop_groups::group::Nexthop.failure_detection [0:1]
- relation nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::EnableBfd enable_bfd [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::EnableBfd¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-next-hop-groups.yang:L124
- attribute nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::enable_bfd_local_address_t? local_address=null¶
The local address to be used for the associated BFD session
- attribute nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::enable_bfd_local_discriminator_t? local_discriminator=null¶
The local discriminator to be used for the associated BFD session
- attribute nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::enable_bfd_remote_discriminator_t? remote_discriminator=null¶
The remote discriminator to be used for the associated BFD session :rel parent_failure_detection: Relation to parent container
- relation nokia_srlinux::network_instance::next_hop_groups::group::nexthop::FailureDetection parent_failure_detection [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::next_hop_groups::group::nexthop::FailureDetection.enable_bfd [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::Interface¶
Parents:
nokia_srlinux::Base
List of subinterfaces that use the policy forwarding policy. Yang definition can be found here: srl_nokia-policy-forwarding.yang:L172
- attribute string? apply_forwarding_policy=null¶
The policy to be applied on the interface. Packets ingress on the referenced interface should be compared to the match criteria within the specified policy, and in the case that these criteria are met, the forwarding actions specified applied.
- attribute nokia_srlinux::types::srl_nokia_network_instance::network_instance_subintf_name subinterface¶
Name of the subinterface. :rel interface_ref: Reference to a subinterface :rel parent_policy_forwarding: Relation to parent container
- relation nokia_srlinux::network_instance::PolicyForwarding parent_policy_forwarding [1]¶
Relation to parent container Peer relation: List of subinterfaces that use the policy forwarding policy.
other end:
nokia_srlinux::network_instance::PolicyForwarding.interface [0:*]
- relation nokia_srlinux::network_instance::policy_forwarding::interface::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::policy_forwarding::interface::InterfaceRef.parent_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::Policy¶
Parents:
nokia_srlinux::Base
A forwarding policy is defined to have a set of match criteria, allowing particular fields of a packet’s header to be matched, and a set of forwarding actions which determines how the local system should forward the packet. Yang definition can be found here: srl_nokia-policy-forwarding.yang:L106
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the policy
- attribute nokia_srlinux::types::srl_nokia_common::name policy_id¶
A unique name identifying the forwarding policy. This name is used when applying the policy to a particular interface.
- attribute nokia_srlinux::network_instance::policy_forwarding::policy_type_t? type=null¶
The type of the policy :rel parent_policy_forwarding: Relation to parent container :rel rule: List of policy forwarding rules.
- relation nokia_srlinux::network_instance::PolicyForwarding parent_policy_forwarding [1]¶
Relation to parent container Peer relation: A forwarding policy is defined to have a set of match criteria, allowing particular fields of a packet’s header to be matched, and a set of forwarding actions which determines how the local system should forward the packet.
other end:
nokia_srlinux::network_instance::PolicyForwarding.policy [0:4]
- relation nokia_srlinux::network_instance::policy_forwarding::policy::Rule rule [0:*]¶
Relation to parent container Peer relation: List of policy forwarding rules.
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::Rule.parent_policy [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::interface::InterfaceRef¶
Parents:
nokia_srlinux::Base
Reference to a subinterface Yang definition can be found here: srl_nokia-policy-forwarding.yang:L181
- attribute string? interface=null¶
Reference to a base interface, for example a port or LAG
- attribute nokia_srlinux::network_instance::policy_forwarding::interface::interface_ref_subinterface_t? subinterface=null¶
Reference to a subinterface This requires the base interface to be specified using the interface leaf in this container. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::policy_forwarding::Interface parent_interface [1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::policy_forwarding::Interface.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::policy::Rule¶
Parents:
nokia_srlinux::Base
List of policy forwarding rules. Yang definition can be found here: srl_nokia-policy-forwarding.yang:L145
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description string for the rule
- attribute nokia_srlinux::types::srl_nokia_common::rule_sequence_id sequence_id¶
A number to indicate the relative evaluation order of the different entries; lower numbered entries are evaluated before higher numbered entries :rel action: Container for the actions to be applied to packets matching the policy forwarding rule. :rel match: Container for the conditions that determine whether a packet matches this entry :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::policy_forwarding::Policy parent_policy [1]¶
Relation to parent container Peer relation: List of policy forwarding rules.
other end:
nokia_srlinux::network_instance::policy_forwarding::Policy.rule [0:*]
- relation nokia_srlinux::network_instance::policy_forwarding::policy::rule::Action action [0:1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the policy forwarding rule.
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::rule::Action.parent_rule [1]
- relation nokia_srlinux::network_instance::policy_forwarding::policy::rule::Match match [0:1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::rule::Match.parent_rule [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::policy::rule::Action¶
Parents:
nokia_srlinux::Base
Container for the actions to be applied to packets matching the policy forwarding rule. Yang definition can be found here: srl_nokia-policy-forwarding.yang:L56
- attribute string? network_instance=null¶
When this leaf is set, packets matching the match criteria for the forwarding rule should be looked up in the network-instance that is referenced rather than the network-instance with which the interface is associated. :rel parent_rule: Relation to parent container
- relation nokia_srlinux::network_instance::policy_forwarding::policy::Rule parent_rule [1]¶
Relation to parent container Peer relation: Container for the actions to be applied to packets matching the policy forwarding rule.
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::Rule.action [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::policy::rule::Match¶
Parents:
nokia_srlinux::Base
Container for the conditions that determine whether a packet matches this entry Yang definition can be found here: srl_nokia-policy-forwarding.yang:L74
- Rel ipv4:
Container for match conditions associated with IPv4 header fields
If no match conditions are provided then no IPv4 packets are matched. :rel parent_rule: Relation to parent container
- relation nokia_srlinux::network_instance::policy_forwarding::policy::Rule parent_rule [1]¶
Relation to parent container Peer relation: Container for the conditions that determine whether a packet matches this entry
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::Rule.match [0:1]
- relation nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation: Container for match conditions associated with IPv4 header fields
If no match conditions are provided then no IPv4 packets are matched.
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::Ipv4.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::Ipv4¶
Parents:
nokia_srlinux::Base
Container for match conditions associated with IPv4 header fields
If no match conditions are provided then no IPv4 packets are matched. Yang definition can be found here: srl_nokia-policy-forwarding.yang:L77
- attribute nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4_dscp_set_t[]? dscp_set=null¶
A list of DSCP values to be matched for incoming packets. An OR match should be performed, such that a packet must match one of the values defined in this list. If the field is left empty then any DSCP value matches.
- attribute nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4_protocol_t? protocol=null¶
An IPv4 packet matches this condition if its IP protocol type field matches the specified value :rel parent_match: Relation to parent container :rel source_ip: Packet matching criteria based on source IPv4 address
- relation nokia_srlinux::network_instance::policy_forwarding::policy::rule::Match parent_match [1]¶
Relation to parent container Peer relation: Container for match conditions associated with IPv4 header fields
If no match conditions are provided then no IPv4 packets are matched.
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::rule::Match.ipv4 [0:1]
- relation nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4::SourceIp source_ip [0:1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4::SourceIp¶
Parents:
nokia_srlinux::Base
Packet matching criteria based on source IPv4 address Yang definition can be found here: srl_nokia-policy-forwarding.yang:L92
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix? prefix=null¶
Match a packet if its source IP address is within the specified IPv4 prefix. :rel parent_ipv4: Relation to parent container
- relation nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Packet matching criteria based on source IPv4 address
other end:
nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::Ipv4.source_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Bgp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2740
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the entire BGP instance Disable causes all BGP sessions to be taken down immediately, even if admin-state at the group or neighbor level of some of these sessions is still set as enable.
- attribute nokia_srlinux::types::srl_nokia_common::as_number? autonomous_system=null¶
The global AS number of the BGP instance Values greater than 65535 must be entered in ASPLAIN format.
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes
- attribute yang::types::uint32? local_preference=null¶
The value of the local-preference attribute that is added to received routes from EBGP peers It is also used to encode the local preference attribute for locally generated BGP routes.
- attribute nokia_srlinux::network_instance::protocols::bgp_max_ecmp_hash_buckets_per_next_hop_group_t? max_ecmp_hash_buckets_per_next_hop_group=null¶
Specifies the maximum number of ECMP hash buckets per next-hop-group Weighted ECMP weights are normalized based on this number of hash buckets.
- attribute nokia_srlinux::network_instance::protocols::bgp_router_id_t? router_id=null¶
The BGP identifier used by this BGP instance in all of its OPEN messages Any non-zero value is supported.
- attribute nokia_srlinux::types::srl_nokia_bgp::community_type[]? send_community_type=null¶
Specify the types of community that should be sent to all peers By default all three community types are sent to all peers :rel afi_safi: List of address families supported by the BGP instance :rel as_path_options: Options for handling the AS_PATH in received BGP routes :rel authentication: Container with authentication options that apply to all peers of the BGP instance :rel best_path_selection: Container with options that control the BGP decision process (tie break between routes for the same NLRI). :rel bgp_label: :rel convergence: Options for configuring address family independent BGP convergence parameters :rel dynamic_neighbors: Options related to the acceptance and initiation of dynamic BGP sessions :rel ebgp_default_policy: Options for controlling the default policies that apply to EBGP sessions :rel failure_detection: Options related to methods of detecting BGP session failure :rel graceful_restart: Options for controlling the behavior of the router as a graceful restart helper :rel group: Peer group templates :rel neighbor: Create a configured BGP session :rel parent_protocols: Relation to parent container :rel preference: Options for controlling the route table preference of BGP routes :rel rib_management: :rel route_advertisement: Options for controlling route advertisement behavior :rel route_reflector: Container with route reflection configuration options. :rel trace_options: Debug traceoptions for BGP :rel transport: Options related to the TCP transport of BGP sessions
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.bgp [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi afi_safi [0:*]¶
Relation to parent container Peer relation: List of address families supported by the BGP instance
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::AsPathOptions as_path_options [0:1]¶
Relation to parent container Peer relation: Options for handling the AS_PATH in received BGP routes
other end:
nokia_srlinux::network_instance::protocols::bgp::AsPathOptions.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container with authentication options that apply to all peers of the BGP instance
other end:
nokia_srlinux::network_instance::protocols::bgp::Authentication.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::BestPathSelection best_path_selection [0:1]¶
Relation to parent container Peer relation: Container with options that control the BGP decision process (tie break between routes for the same NLRI).
other end:
nokia_srlinux::network_instance::protocols::bgp::BestPathSelection.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::BgpLabel bgp_label [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::BgpLabel.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for configuring address family independent BGP convergence parameters
other end:
nokia_srlinux::network_instance::protocols::bgp::Convergence.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors dynamic_neighbors [0:1]¶
Relation to parent container Peer relation: Options related to the acceptance and initiation of dynamic BGP sessions
other end:
nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::EbgpDefaultPolicy ebgp_default_policy [0:1]¶
Relation to parent container Peer relation: Options for controlling the default policies that apply to EBGP sessions
other end:
nokia_srlinux::network_instance::protocols::bgp::EbgpDefaultPolicy.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::FailureDetection failure_detection [0:1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::bgp::FailureDetection.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::GracefulRestart graceful_restart [0:1]¶
Relation to parent container Peer relation: Options for controlling the behavior of the router as a graceful restart helper
other end:
nokia_srlinux::network_instance::protocols::bgp::GracefulRestart.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::Group group [0:*]¶
Relation to parent container Peer relation: Peer group templates
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor neighbor [0:*]¶
Relation to parent container Peer relation: Create a configured BGP session
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::Preference preference [0:1]¶
Relation to parent container Peer relation: Options for controlling the route table preference of BGP routes
other end:
nokia_srlinux::network_instance::protocols::bgp::Preference.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::RibManagement rib_management [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::RibManagement.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::RouteAdvertisement route_advertisement [0:1]¶
Relation to parent container Peer relation: Options for controlling route advertisement behavior
other end:
nokia_srlinux::network_instance::protocols::bgp::RouteAdvertisement.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::RouteReflector route_reflector [0:1]¶
Relation to parent container Peer relation: Container with route reflection configuration options.
other end:
nokia_srlinux::network_instance::protocols::bgp::RouteReflector.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Debug traceoptions for BGP
other end:
nokia_srlinux::network_instance::protocols::bgp::TraceOptions.parent_bgp [1]
- relation nokia_srlinux::network_instance::protocols::bgp::Transport transport [0:1]¶
Relation to parent container Peer relation: Options related to the TCP transport of BGP sessions
other end:
nokia_srlinux::network_instance::protocols::bgp::Transport.parent_bgp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::BgpEvpn¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-network-instance.yang:L597
- Rel bgp_instance:
bgp evpn instances configured in net-instance
- Rel parent_protocols:
Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.bgp_evpn [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance bgp_instance [0:1]¶
Relation to parent container Peer relation: bgp evpn instances configured in net-instance
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance.parent_bgp_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::BgpIpvpn¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-network-instance.yang:L604
- Rel bgp_instance:
bgp ipvpn instances configured in net-instance
- Rel parent_protocols:
Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.bgp_ipvpn [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance bgp_instance [0:1]¶
Relation to parent container Peer relation: bgp ipvpn instances configured in net-instance
other end:
nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance.parent_bgp_ipvpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::BgpVpn¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-vpn.yang:L46
- Rel bgp_instance:
List of bgp-vpn instances configured in the network-instance. Only one instance allowed in the current release.
- Rel parent_protocols:
Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.bgp_vpn [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance bgp_instance [0:2]¶
Relation to parent container Peer relation: List of bgp-vpn instances configured in the network-instance. Only one instance allowed in the current release.
other end:
nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance.parent_bgp_vpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::DirectlyConnected¶
Parents:
nokia_srlinux::Base
Container for handling directly connected routes as a pseudo-protocol Yang definition can be found here: srl_nokia-network-instance.yang:L611
- Rel parent_protocols:
Relation to parent container
- Rel te_database_install:
When present, local topology and TE information is installed into the TE database
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation: Container for handling directly connected routes as a pseudo-protocol
other end:
nokia_srlinux::network_instance::Protocols.directly_connected [0:1]
- relation nokia_srlinux::network_instance::protocols::directly_connected::TeDatabaseInstall te_database_install [0:1]¶
Relation to parent container Peer relation: When present, local topology and TE information is installed into the TE database
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Gribi¶
Parents:
nokia_srlinux::Base
Container for gRIBI configuration and state. Yang definition can be found here: srl_nokia-gribi-server.yang:L286
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable gRIBI support. The enable setting only has an effect when the network-instance type is ip-vrf or default. When this is set to disable all IP entries and next-hop-groups associated with the network-instance are deleted from the gRIBI server database and the recovery of this state depends on the gRIBI clients to re-signal all of the deleted entries. While in a disabled state, no entries are accepted for this network-instance. (This is the same behavior when the network-instance does not exist at all.)
- attribute yang::types::uint32? default_metric=null¶
Set the route table metric to use for all gRIBI-created IPv4 and IPv6 routes
- attribute nokia_srlinux::network_instance::protocols::gribi_default_preference_t? default_preference=null¶
Lower values indicate a higher degree of preference when deciding the route to use from different protocols.
- attribute nokia_srlinux::network_instance::protocols::gribi_max_ecmp_hash_buckets_per_next_hop_group_t? max_ecmp_hash_buckets_per_next_hop_group=null¶
Specifies the maximum number of ECMP hash buckets per next-hop-group. An error is returned to any gRIBI client that attempts to program more than this number of next-hops in a single next-hop-group. Weighted ECMP weights are normalized based on this number of hash buckets.
- attribute yang::types::uint32? maximum_routes=null¶
Specifies the maximum number of gRIBI routes (sum of IPv4 and IPv6 entries). A value of 0 signifies no limit. :rel parent_protocols: Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation: Container for gRIBI configuration and state.
other end:
nokia_srlinux::network_instance::Protocols.gribi [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Igmp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-igmp.yang:L875
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the IGMP instance
- attribute nokia_srlinux::network_instance::protocols::igmp_query_interval_t? query_interval=null¶
Interval at which the router sends the IGMP membership queries
- attribute nokia_srlinux::network_instance::protocols::igmp_query_last_member_interval_t? query_last_member_interval=null¶
Interval at which Group-Specific-Query packets are transmitted
- attribute nokia_srlinux::network_instance::protocols::igmp_query_response_interval_t? query_response_interval=null¶
Time to wait to receive a response to the IGMP membership query from the host
- attribute nokia_srlinux::network_instance::protocols::igmp_robust_count_t? robust_count=null¶
Tune IGMP robustness to allow for expected packet loss The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased. :rel interface: List of IGMP interfaces :rel parent_protocols: Relation to parent container :rel ssm: Container to configure Source specific multicast (SSM) options. :rel trace_options: Enter the trace-options context
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.igmp [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::Interface interface [0:*]¶
Relation to parent container Peer relation: List of IGMP interfaces
other end:
nokia_srlinux::network_instance::protocols::igmp::Interface.parent_igmp [1]
- relation nokia_srlinux::network_instance::protocols::igmp::Ssm ssm [0:1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options.
other end:
nokia_srlinux::network_instance::protocols::igmp::Ssm.parent_igmp [1]
- relation nokia_srlinux::network_instance::protocols::igmp::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::igmp::TraceOptions.parent_igmp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::IgmpSnooping¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-igmp-snooping.yang:L1056
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the IGMP instance
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping_query_interval_t? query_interval=null¶
Interval at which the router sends the IGMP membership queries
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? query_source_address=null¶
Source IP address used when generating IGMP queries
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? report_source_address=null¶
Source IP address used when generating IGMP reports
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping_robust_count_t? robust_count=null¶
Configures the IGMP robustness to allow for the expected IGMP packet loss The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased. :rel interface: List of IGMP interfaces :rel parent_protocols: Relation to parent container :rel trace_options: Enter the trace-options context
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.igmp_snooping [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::Interface interface [0:*]¶
Relation to parent container Peer relation: List of IGMP interfaces
other end:
nokia_srlinux::network_instance::protocols::igmp_snooping::Interface.parent_igmp_snooping [1]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::igmp_snooping::TraceOptions.parent_igmp_snooping [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Isis¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L3266
- attribute string? dynamic_label_block=null¶
Reference to a dynamic label block Configuration of this label block is mandatory in order to enable segment routing MPLS (SR-MPLS) in IS-IS. Dynamic adjacency SID labels come from this label block. This label block is not advertised as an SRLB in the router capabilities TLV. :rel instance: List of IS-IS protocol instances associated with this network-instance. Only a single instance is supported for now :rel non_stop_forwarding: :rel parent_protocols: Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.isis [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::Instance instance [0:*]¶
Relation to parent container Peer relation: List of IS-IS protocol instances associated with this network-instance. Only a single instance is supported for now
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.parent_isis [1]
- relation nokia_srlinux::network_instance::protocols::isis::NonStopForwarding non_stop_forwarding [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::NonStopForwarding.parent_isis [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Ldp¶
Parents:
nokia_srlinux::Base
Container for LDP configuration and state. Yang definition can be found here: srl_nokia-ldp.yang:L750
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable LDP.
- attribute string? dynamic_label_block=null¶
Reference to a dynamic label block
- attribute string? export_prefix_policy=null¶
Apply an export prefix policy to filter advertised label bindings.
- attribute string? import_prefix_policy=null¶
Apply an import prefix policy to filter received label bindings. :rel discovery: Neighbor discovery configuration and operational state. :rel entropy_label: Options for configuring control and data plane aspects of entropy label :rel graceful_restart: Attributes for graceful restart. :rel ipv4: Container for configuration and state related to the IPv4 address family. :rel loopfree_alternate: :rel multipath: Container with options to configure load-balancing over equal-cost paths :rel parent_protocols: Relation to parent container :rel peers: Configuration and state related to peers :rel static_fec: Configure static FEC.
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation: Container for LDP configuration and state.
other end:
nokia_srlinux::network_instance::Protocols.ldp [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::Discovery discovery [0:1]¶
Relation to parent container Peer relation: Neighbor discovery configuration and operational state.
other end:
nokia_srlinux::network_instance::protocols::ldp::Discovery.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::EntropyLabel entropy_label [0:1]¶
Relation to parent container Peer relation: Options for configuring control and data plane aspects of entropy label
other end:
nokia_srlinux::network_instance::protocols::ldp::EntropyLabel.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::GracefulRestart graceful_restart [0:1]¶
Relation to parent container Peer relation: Attributes for graceful restart.
other end:
nokia_srlinux::network_instance::protocols::ldp::GracefulRestart.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation: Container for configuration and state related to the IPv4 address family.
other end:
nokia_srlinux::network_instance::protocols::ldp::Ipv4.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::LoopfreeAlternate loopfree_alternate [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ldp::LoopfreeAlternate.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::Multipath multipath [0:1]¶
Relation to parent container Peer relation: Container with options to configure load-balancing over equal-cost paths
other end:
nokia_srlinux::network_instance::protocols::ldp::Multipath.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::Peers peers [0:1]¶
Relation to parent container Peer relation: Configuration and state related to peers
other end:
nokia_srlinux::network_instance::protocols::ldp::Peers.parent_ldp [1]
- relation nokia_srlinux::network_instance::protocols::ldp::StaticFec static_fec [0:*]¶
Relation to parent container Peer relation: Configure static FEC.
other end:
nokia_srlinux::network_instance::protocols::ldp::StaticFec.parent_ldp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Linux¶
Parents:
nokia_srlinux::Base
Enables routing interaction with the Linux kernel Yang definition can be found here: srl_nokia-linux.yang:L24
- attribute bool? export_neighbors=null¶
Export neighbors to linux routing table
- attribute bool? export_routes=null¶
Export routes to linux routing table
- attribute bool? import_routes=null¶
Import routes from linux routing table :rel parent_protocols: Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation: Enables routing interaction with the Linux kernel
other end:
nokia_srlinux::network_instance::Protocols.linux [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Mld¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mld.yang:L859
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the MLD instance
- attribute nokia_srlinux::network_instance::protocols::mld_query_interval_t? query_interval=null¶
Interval at which the router sends the mld membership queries
- attribute nokia_srlinux::network_instance::protocols::mld_query_last_member_interval_t? query_last_member_interval=null¶
Interval at which Group-Specific-Query packets are transmitted
- attribute nokia_srlinux::network_instance::protocols::mld_query_response_interval_t? query_response_interval=null¶
Time to wait to receive a response to the MLD membership query from the host
- attribute nokia_srlinux::network_instance::protocols::mld_robust_count_t? robust_count=null¶
Tune MLD robustness to allow for expected packet loss The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased. :rel interface: List of MLD interfaces :rel parent_protocols: Relation to parent container :rel ssm: Container to configure Source specific multicast (SSM) options :rel trace_options: Enter the trace-options context
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.mld [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::Interface interface [0:*]¶
Relation to parent container Peer relation: List of MLD interfaces
other end:
nokia_srlinux::network_instance::protocols::mld::Interface.parent_mld [1]
- relation nokia_srlinux::network_instance::protocols::mld::Ssm ssm [0:1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options
other end:
nokia_srlinux::network_instance::protocols::mld::Ssm.parent_mld [1]
- relation nokia_srlinux::network_instance::protocols::mld::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::mld::TraceOptions.parent_mld [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::MldSnooping¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mld-snooping.yang:L1038
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the MLD instance
- attribute nokia_srlinux::network_instance::protocols::mld_snooping_query_interval_t? query_interval=null¶
Interval at which the router sends the MLD membership queries
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? query_source_address=null¶
Source IP address used when generating MLD queries
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? report_source_address=null¶
Source IP address used when generating MLD reports
- attribute nokia_srlinux::network_instance::protocols::mld_snooping_robust_count_t? robust_count=null¶
Configures the MLD robustness to allow for the expected MLD packet loss The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased. :rel interface: List of MLD interfaces :rel parent_protocols: Relation to parent container :rel trace_options: Enter the trace-options context
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.mld_snooping [0:1]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::Interface interface [0:*]¶
Relation to parent container Peer relation: List of MLD interfaces
other end:
nokia_srlinux::network_instance::protocols::mld_snooping::Interface.parent_mld_snooping [1]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::mld_snooping::TraceOptions.parent_mld_snooping [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Ospf¶
Parents:
nokia_srlinux::Base
Top-level configuration and operational state for Open Shortest Path First (OSPF) Yang definition can be found here: srl_nokia-ospf.yang:L1994
- Rel instance:
List of OSPF protocol instances associated with this
network-instance. :rel parent_protocols: Relation to parent container
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation: Top-level configuration and operational state for Open Shortest Path First (OSPF)
other end:
nokia_srlinux::network_instance::Protocols.ospf [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::Instance instance [0:3]¶
Relation to parent container Peer relation: List of OSPF protocol instances associated with this network-instance.
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.parent_ospf [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::Pim¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-pim.yang:L1884
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable PIM
- attribute bool? ecmp_balance=null¶
Enables hashing balance for multicast streams This command enables multicast balancing of traffic over ECMP links based on the number of (S, G) distributed over each link. When enabled, each new multicast stream that needs to be forwarded over an ECMP link is compared to the count of (S, G) already using each link, so that the link with the fewest (S, G) is chosen.
- attribute nokia_srlinux::network_instance::protocols::pim_ecmp_balance_hold_t? ecmp_balance_hold=null¶
Hold period for ecmp balancing This command defines a hold period that applies after an interface has been added to the ECMP link. It is also used periodically to rebalance if channels have been removed from the ECMP link. If the ECMP interface has not changed in the hold period and if no multicast streams have been removed, then no action is taken when the timer triggers. This parameter should be used to avoid excessive changes to the multicast distribution.
- attribute bool? ecmp_hashing=null¶
Enables hashing for multicast streams This command enables hash-based multicast balancing of traffic over ECMP links and causes PIM joins to be distributed over the multiple ECMP paths based on a hash of S and G (and possibly next-hop IP address). When a link in the ECMP set is removed, the multicast flows that were using that link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set new joins may be allocated to the new link based on the hash algorithm, but existing. :rel interface: List of PIM interfaces :rel ipv4: IPv4 specific PIM parameters :rel ipv6: IPv6 specific PIM parameters :rel parent_protocols: Relation to parent container :rel rendezvous_points: Define rendezvous points for sparse mode multicast :rel spt_switchover: Define Shortest Path Tree (SPT) switchover threshold for multicast groups :rel ssm: Source Specific Multicast (SSM) configuration :rel trace_options: Enter the trace-options context
- relation nokia_srlinux::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::Protocols.pim [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::Interface interface [0:*]¶
Relation to parent container Peer relation: List of PIM interfaces
other end:
nokia_srlinux::network_instance::protocols::pim::Interface.parent_pim [1]
- relation nokia_srlinux::network_instance::protocols::pim::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation: IPv4 specific PIM parameters
other end:
nokia_srlinux::network_instance::protocols::pim::Ipv4.parent_pim [1]
- relation nokia_srlinux::network_instance::protocols::pim::Ipv6 ipv6 [0:1]¶
Relation to parent container Peer relation: IPv6 specific PIM parameters
other end:
nokia_srlinux::network_instance::protocols::pim::Ipv6.parent_pim [1]
- relation nokia_srlinux::network_instance::protocols::pim::RendezvousPoints rendezvous_points [0:1]¶
Relation to parent container Peer relation: Define rendezvous points for sparse mode multicast
other end:
nokia_srlinux::network_instance::protocols::pim::RendezvousPoints.parent_pim [1]
- relation nokia_srlinux::network_instance::protocols::pim::SptSwitchover spt_switchover [0:1]¶
Relation to parent container Peer relation: Define Shortest Path Tree (SPT) switchover threshold for multicast groups
other end:
nokia_srlinux::network_instance::protocols::pim::SptSwitchover.parent_pim [1]
- relation nokia_srlinux::network_instance::protocols::pim::Ssm ssm [0:1]¶
Relation to parent container Peer relation: Source Specific Multicast (SSM) configuration
other end:
nokia_srlinux::network_instance::protocols::pim::Ssm.parent_pim [1]
- relation nokia_srlinux::network_instance::protocols::pim::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::pim::TraceOptions.parent_pim [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::AfiSafi¶
Parents:
nokia_srlinux::Base
List of address families supported by the BGP instance Yang definition can be found here: srl_nokia-bgp.yang:L3096
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf indicates whether the AFI-SAFI is enabled for the instance
- attribute string afi_safi_name¶
The name of a BGP address family, which translates to a specific AFI value and a specific SAFI value
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes :rel add_paths: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI :rel evpn: Options related to the EVPN address family :rel ipv4_labeled_unicast: Options related to the labeled IPv4-unicast address family :rel ipv4_unicast: Options related to the IPv4-unicast address family :rel ipv6_labeled_unicast: Options related to the labeled IPv6-unicast address family :rel ipv6_unicast: Options related to the IPv6-unicast address family :rel l3vpn_ipv4_unicast: Options related to the VPN-IPv4 unicast address family :rel l3vpn_ipv6_unicast: Options related to the VPN-IPv6 unicast address family :rel multipath: Options related to BGP multipath :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: List of address families supported by the BGP instance
other end:
nokia_srlinux::network_instance::protocols::Bgp.afi_safi [0:*]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::AddPaths add_paths [0:1]¶
Relation to parent container Peer relation: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::AddPaths.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Options related to the EVPN address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Evpn.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast ipv4_labeled_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the labeled IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast ipv6_labeled_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the labeled IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv4Unicast l3vpn_ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv4 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv4Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv6Unicast l3vpn_ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv6 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv6Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Multipath multipath [0:1]¶
Relation to parent container Peer relation: Options related to BGP multipath
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Multipath.parent_afi_safi [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::AsPathOptions¶
Parents:
nokia_srlinux::Base
Options for handling the AS_PATH in received BGP routes Yang definition can be found here: srl_nokia-bgp.yang:L2816
- attribute yang::types::uint8? allow_own_as=null¶
The maximum number of times the global AS number or a local AS number of the BGP instance can appear in any received AS_PATH before it is considered a loop and considered invalid :rel parent_bgp: Relation to parent container :rel remove_private_as: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options for handling the AS_PATH in received BGP routes
other end:
nokia_srlinux::network_instance::protocols::Bgp.as_path_options [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::as_path_options::RemovePrivateAs remove_private_as [0:1]¶
Relation to parent container Peer relation: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::Authentication¶
Parents:
nokia_srlinux::Base
Container with authentication options that apply to all peers of the BGP instance Yang definition can be found here: srl_nokia-bgp.yang:L2867
- attribute string? keychain=null¶
Reference to a keychain. The keychain type must be tcp-md5.
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? password=null¶
Configures an MD5 authentication password for use with neighboring devices. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Container with authentication options that apply to all peers of the BGP instance
other end:
nokia_srlinux::network_instance::protocols::Bgp.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::BestPathSelection¶
Parents:
nokia_srlinux::Base
Container with options that control the BGP decision process (tie break between routes for the same NLRI). Yang definition can be found here: srl_nokia-bgp.yang:L2891
- attribute bool? always_compare_med=null¶
Compare multi-exit discriminator (MED) value from different ASes when selecting the best route. The default behavior is to only compare MEDs for paths received from the same AS. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Container with options that control the BGP decision process (tie break between routes for the same NLRI).
other end:
nokia_srlinux::network_instance::protocols::Bgp.best_path_selection [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::BgpLabel¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2685
- Rel labeled_unicast:
- Rel parent_bgp:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Bgp.bgp_label [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::bgp_label::LabeledUnicast labeled_unicast [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::bgp_label::LabeledUnicast.parent_bgp_label [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::Convergence¶
Parents:
nokia_srlinux::Base
Options for configuring address family independent BGP convergence parameters Yang definition can be found here: srl_nokia-bgp.yang:L2903
- attribute nokia_srlinux::network_instance::protocols::bgp::convergence_min_wait_to_advertise_t? min_wait_to_advertise=null¶
The minimum amount of time, in seconds, measured from the moment when the first session (configured or dynamic) comes up after a BGP restart, until BGP is allowed to advertise any routes to any peer The sessions that are established when this timer expires determines the set of peers from which EOR is expected in order to declare convergence for an address family. A value of 0 means the feature is disabled and all routes are advertised immediately. This timer and associated state machine are only restarted by one of the following triggers: - BGP instance admin disable/enable - tools clear network-instance protocols bgp reset-peer - bgp application restart - node reboot :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options for configuring address family independent BGP convergence parameters
other end:
nokia_srlinux::network_instance::protocols::Bgp.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors¶
Parents:
nokia_srlinux::Base
Options related to the acceptance and initiation of dynamic BGP sessions Yang definition can be found here: srl_nokia-bgp.yang:L2923
- Rel accept:
Options related to the acceptance of dynamic BGP sessions from remote peers
- Rel interface:
List of interfaces on which dynamic sessions based on IPv6 link-local address discovery are accepted and initiated.
- Rel parent_bgp:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options related to the acceptance and initiation of dynamic BGP sessions
other end:
nokia_srlinux::network_instance::protocols::Bgp.dynamic_neighbors [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::Accept accept [0:1]¶
Relation to parent container Peer relation: Options related to the acceptance of dynamic BGP sessions from remote peers
- relation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::Interface interface [0:*]¶
Relation to parent container Peer relation: List of interfaces on which dynamic sessions based on IPv6 link-local address discovery are accepted and initiated.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::EbgpDefaultPolicy¶
Parents:
nokia_srlinux::Base
Options for controlling the default policies that apply to EBGP sessions Yang definition can be found here: srl_nokia-bgp.yang:L3017
- attribute bool? export_reject_all=null¶
When set to true, all outbound routes towards any EBGP peer to which no explicit export policy is applied are treated as though they were rejected by policy
- attribute bool? import_reject_all=null¶
When set to true, all inbound routes from any EBGP peer to which no explicit import policy is applied are treated as though they were rejected by policy :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options for controlling the default policies that apply to EBGP sessions
other end:
nokia_srlinux::network_instance::protocols::Bgp.ebgp_default_policy [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::FailureDetection¶
Parents:
nokia_srlinux::Base
Options related to methods of detecting BGP session failure Yang definition can be found here: srl_nokia-bgp.yang:L3033
- attribute bool? enable_bfd=null¶
The true setting enables Bi-directional Forwarding Detection on BGP sessions belonging to the peer group
- attribute bool? fast_failover=null¶
The true setting causes EBGP and IBGP sessions to drop immediately (and not wait for hold timer expiry) when the local interface that they depend upon for neighbor reachability goes down :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::Bgp.failure_detection [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::GracefulRestart¶
Parents:
nokia_srlinux::Base
Options for controlling the behavior of the router as a graceful restart helper Yang definition can be found here: srl_nokia-bgp.yang:L3049
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable graceful restart helper for all address families
- attribute nokia_srlinux::network_instance::protocols::bgp::graceful_restart_requested_restart_time_t? requested_restart_time=null¶
The restart time encoded in this router’s GR capability. If the neighbor honors this request then this is the maximum time allowed for this router to re-establish its TCP connection after a restart. If this time is exceeded, the neighbor is expected to flush stale routes that it was maintaining on behalf of this router.
- attribute nokia_srlinux::network_instance::protocols::bgp::graceful_restart_stale_routes_time_t? stale_routes_time=null¶
The maximum number of seconds that routes received from a helped peer remain stale until they are deleted Routes of AFI/SAFI X received from peer Y are marked stale when peer Y goes down and its previous GR capability included AFI/SAFI X. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options for controlling the behavior of the router as a graceful restart helper
other end:
nokia_srlinux::network_instance::protocols::Bgp.graceful_restart [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::Group¶
Parents:
nokia_srlinux::Base
Peer group templates Yang definition can be found here: srl_nokia-bgp.yang:L280
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the peer group Disable will tear down all the BGP sessions in the group, even if they are administratively enabled at the neighbor level.
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user provided description string for the peer group
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute nokia_srlinux::network_instance::protocols::bgp::group_group_name_t group_name¶
The configured name of the peer group
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes
- attribute yang::types::uint32? local_preference=null¶
The value of the local-preference attribute that is added to received routes from EBGP peers in the group It is also used to encode the local preference attribute for locally generated BGP routes.
- attribute bool? next_hop_self=null¶
When set to true, the next-hop in all IPv4-unicast, IPv6-unicast, EVPN, VPN-IPv4 and VPN-IPv6 BGP routes advertised to all IBGP peers in the peer-group is set equal to the local-address used on each session (or to the router ID if the NLRI is IPv6 and there is no IPv6 local address to use). This is independent of the route origin (EBGP, IBGP-client, IBGP-non-client or redistributed direct/static/aggregate route). When set to false, normal BGP rules from RFC 4271 apply.
- attribute nokia_srlinux::types::srl_nokia_common::as_number? peer_as=null¶
The autonomous system number expected from each peer in the group A configured session with a peer does not come up if this value does not match the AS value reported by the peer in its OPEN message.
- attribute nokia_srlinux::types::srl_nokia_bgp::community_type[]? send_community_type=null¶
Specify the types of community that should be sent to peers in the group :rel afi_safi: List of address families supported by the BGP peer group :rel as_path_options: Options for handling the AS_PATH in received BGP routes :rel authentication: Container with authentication options that apply to all peers in this peer-group :rel failure_detection: Options related to methods of detecting BGP session failure :rel graceful_restart: Options related to router behavior as a graceful restart helper :rel local_as: Options related to the local autonomous-system number advertised by this router to its peers :rel multihop: Configuration parameters specifying the multihop behaviour for IBGP and EBGP peers in the peer group. :rel parent_bgp: Relation to parent container :rel route_reflector: Container with route reflection configuration options. :rel send_default_route: Options for controlling the generation of default routes towards group peers :rel timers: :rel trace_options: Debug traceoptions for BGP :rel transport:
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Peer group templates
other end:
nokia_srlinux::network_instance::protocols::Bgp.group [0:*]
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi afi_safi [0:*]¶
Relation to parent container Peer relation: List of address families supported by the BGP peer group
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::AsPathOptions as_path_options [0:1]¶
Relation to parent container Peer relation: Options for handling the AS_PATH in received BGP routes
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AsPathOptions.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container with authentication options that apply to all peers in this peer-group
other end:
nokia_srlinux::network_instance::protocols::bgp::group::Authentication.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::FailureDetection failure_detection [0:1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::bgp::group::FailureDetection.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::GracefulRestart graceful_restart [0:1]¶
Relation to parent container Peer relation: Options related to router behavior as a graceful restart helper
other end:
nokia_srlinux::network_instance::protocols::bgp::group::GracefulRestart.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::LocalAs local_as [0:1]¶
Relation to parent container Peer relation: Options related to the local autonomous-system number advertised by this router to its peers
other end:
nokia_srlinux::network_instance::protocols::bgp::group::LocalAs.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::Multihop multihop [0:1]¶
Relation to parent container Peer relation: Configuration parameters specifying the multihop behaviour for IBGP and EBGP peers in the peer group.
other end:
nokia_srlinux::network_instance::protocols::bgp::group::Multihop.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::RouteReflector route_reflector [0:1]¶
Relation to parent container Peer relation: Container with route reflection configuration options.
other end:
nokia_srlinux::network_instance::protocols::bgp::group::RouteReflector.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::SendDefaultRoute send_default_route [0:1]¶
Relation to parent container Peer relation: Options for controlling the generation of default routes towards group peers
other end:
nokia_srlinux::network_instance::protocols::bgp::group::SendDefaultRoute.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::Timers timers [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::group::Timers.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Debug traceoptions for BGP
other end:
nokia_srlinux::network_instance::protocols::bgp::group::TraceOptions.parent_group [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::Transport transport [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::group::Transport.parent_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::Neighbor¶
Parents:
nokia_srlinux::Base
Create a configured BGP session Yang definition can be found here: srl_nokia-bgp.yang:L1475
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the peer Disable will tear down the BGP session (return it to IDLE state).
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user provided description string for the peer
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes
- attribute yang::types::uint32? local_preference=null¶
The value of the local-preference attribute that is added to received routes from the peer, if it is EBGP It is also used to encode the local preference attribute for locally generated BGP routes.
- attribute bool? next_hop_self=null¶
When set to true, the next-hop in all IPv4-unicast, IPv6-unicast and EVPN BGP routes advertised to the peer, if IBGP, is set equal to the local-address used on this session (or to the router ID if the NLRI is IPv6 and there is no IPv6 local address to use). This is independent of the route origin (EBGP, IBGP-client, IBGP-non-client or redistributed direct/static/aggregate route). When set to false, normal BGP rules from RFC 4271 apply.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor_peer_address_t peer_address¶
The transport address of the BGP peer The peer-address must be a valid IPv4 unicast address, IPv6 global unicast address or IPv6 link-local address. An IPv6 link-local address requires the interface scope to be identified, using a format such as fe80::1234%ethernet-1/1.1
- attribute nokia_srlinux::types::srl_nokia_common::as_number? peer_as=null¶
The autonomous system number expected from the peer A configured session with a peer does not come up if this value does not match the AS value reported by the peer in its OPEN message.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor_peer_group_t? peer_group=null¶
A reference to the peer-group template to use for this BGP session This is not immutable.
- attribute nokia_srlinux::types::srl_nokia_bgp::community_type[]? send_community_type=null¶
Specify the types of community that should be sent to the peer :rel afi_safi: List of address families supported by the BGP neighbor :rel as_path_options: Options for handling the AS_PATH in received BGP routes :rel authentication: Container with authentication options that apply to this specific peer :rel failure_detection: Options related to methods of detecting BGP session failure :rel graceful_restart: Options related to router behavior as a graceful restart helper :rel local_as: Options related to the local autonomous-system number advertised by this router to the peer :rel multihop: Configuration parameters specifying the multihop behaviour for an EBGP peer. This is not applicable to an IBGP peer. :rel parent_bgp: Relation to parent container :rel route_reflector: Container with route reflection configuration options. :rel send_default_route: Options for controlling the generation of default routes towards the peer :rel timers: :rel trace_options: Debug traceoptions for BGP :rel transport:
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Create a configured BGP session
other end:
nokia_srlinux::network_instance::protocols::Bgp.neighbor [0:*]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi afi_safi [0:*]¶
Relation to parent container Peer relation: List of address families supported by the BGP neighbor
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AsPathOptions as_path_options [0:1]¶
Relation to parent container Peer relation: Options for handling the AS_PATH in received BGP routes
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AsPathOptions.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container with authentication options that apply to this specific peer
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::Authentication.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::FailureDetection failure_detection [0:1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::FailureDetection.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::GracefulRestart graceful_restart [0:1]¶
Relation to parent container Peer relation: Options related to router behavior as a graceful restart helper
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::GracefulRestart.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::LocalAs local_as [0:1]¶
Relation to parent container Peer relation: Options related to the local autonomous-system number advertised by this router to the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::LocalAs.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::Multihop multihop [0:1]¶
Relation to parent container Peer relation: Configuration parameters specifying the multihop behaviour for an EBGP peer. This is not applicable to an IBGP peer.
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::Multihop.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::RouteReflector route_reflector [0:1]¶
Relation to parent container Peer relation: Container with route reflection configuration options.
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::RouteReflector.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::SendDefaultRoute send_default_route [0:1]¶
Relation to parent container Peer relation: Options for controlling the generation of default routes towards the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::SendDefaultRoute.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::Timers timers [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::Timers.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Debug traceoptions for BGP
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::TraceOptions.parent_neighbor [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::Transport transport [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::Transport.parent_neighbor [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::Preference¶
Parents:
nokia_srlinux::Base
Options for controlling the route table preference of BGP routes Yang definition can be found here: srl_nokia-bgp.yang:L3371
- attribute nokia_srlinux::network_instance::protocols::bgp::preference_ebgp_t? ebgp=null¶
The default route table preference for all EBGP learned routes BGP import policies can override this preference value on a route by route basis.
- attribute nokia_srlinux::network_instance::protocols::bgp::preference_ibgp_t? ibgp=null¶
The default route table preference for all IBGP learned routes BGP import policies can override this preference value on a route by route basis. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options for controlling the route table preference of BGP routes
other end:
nokia_srlinux::network_instance::protocols::Bgp.preference [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::RibManagement¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2712
- Rel parent_bgp:
Relation to parent container
- Rel table:
List of RIB tables maintained by BGP running in this network-instance
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Bgp.rib_management [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::rib_management::Table table [0:*]¶
Relation to parent container Peer relation: List of RIB tables maintained by BGP running in this network-instance
other end:
nokia_srlinux::network_instance::protocols::bgp::rib_management::Table.parent_rib_management [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::RouteAdvertisement¶
Parents:
nokia_srlinux::Base
Options for controlling route advertisement behavior Yang definition can be found here: srl_nokia-bgp.yang:L3396
- attribute bool? rapid_withdrawal=null¶
The true setting enables rapid-withdraw towards BGP peers If there is only one BGP route for an NLRI in BGP RIB, and this route is withdrawn or becomes invalid, rapid-withdraw causes BGP to immediately send a withdrawal of the BGP route even if the min-route-advertisement timer has not expired.
- attribute bool? wait_for_fib_install=null¶
The true setting causes BGP to NOT advertise initial reachability to a prefix, or a change of reachability to a prefix, until it receives acknowledgment from FIB manager that the route change has been applied Does not apply to route withdrawals. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options for controlling route advertisement behavior
other end:
nokia_srlinux::network_instance::protocols::Bgp.route_advertisement [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::RouteReflector¶
Parents:
nokia_srlinux::Base
Container with route reflection configuration options. Yang definition can be found here: srl_nokia-bgp.yang:L3416
- attribute bool? client=null¶
When this is set to true all configured and dynamic sessions of the BGP instance are considered RR clients, subject to overrides at more specific levels of configuration.
- attribute nokia_srlinux::network_instance::protocols::bgp::route_reflector_cluster_id_t? cluster_id=null¶
The cluster-id to insert into the CLUSTER_LIST attribute when reflecting routes received by or sent to clients in this scope of this container. The default is the router-id. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Container with route reflection configuration options.
other end:
nokia_srlinux::network_instance::protocols::Bgp.route_reflector [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::TraceOptions¶
Parents:
nokia_srlinux::Base
Debug traceoptions for BGP Yang definition can be found here: srl_nokia-bgp.yang:L163
- Rel flag:
Tracing parameters
- Rel parent_bgp:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Debug traceoptions for BGP
other end:
nokia_srlinux::network_instance::protocols::Bgp.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::trace_options::Flag flag [0:*]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::protocols::bgp::trace_options::Flag.parent_trace_options [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::Transport¶
Parents:
nokia_srlinux::Base
Options related to the TCP transport of BGP sessions Yang definition can be found here: srl_nokia-bgp.yang:L3459
- attribute bool? mtu_discovery=null¶
Turns path mtu discovery for BGP TCP sessions on (true) or off (false) If this is unconfigured then the setting comes from network-instance/mtu/path-mtu-discovery. Changing the value of network-instance/mtu/path-mtu-discovery takes effect only for new connections established after the change
- attribute bool? single_hop_connected_check=null¶
Control whether a single-hop BGP session should be allowed to setup if its ‘related interface’ is down. If single-hop-connected-check is false, a single-hop BGP session (EBGP or IBGP) to any IPv4 or IPv6 neighbor address is permitted to establish if there is ANY valid (IPv6 global unicast, IPv4 link-local, or IPv4 global) route to that neighbor address, regardless of whether the ‘related interface’ is up or down. If single-hop-connected-check is true (default value), a single-hop BGP session (EBGP or IBGP) to any IPv4 or IPv6 neighbor address is only permitted to transition from idle to a higher state if the ‘related interface’ is up. The ‘related interface’ of a single hop peer is the subinterface associated with the IPv6 link local neighbor address or else the subinterface with a primary or secondary IP address and prefix-length that covers the neighbor address.
- attribute nokia_srlinux::network_instance::protocols::bgp::transport_tcp_mss_t? tcp_mss=null¶
The maximum segment size of BGP TCP packets The actual value used in the transmit direction towards a particular peer should be checked at the neighbor level. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Options related to the TCP transport of BGP sessions
other end:
nokia_srlinux::network_instance::protocols::Bgp.transport [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::AddPaths¶
Parents:
nokia_srlinux::Base
Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI Yang definition can be found here: srl_nokia-bgp.yang:L3129
- attribute bool? receive=null¶
Enable capability negotiation to receive multiple path advertisements from a single peer for a single NLRI belonging to the AFI/SAFI
- attribute bool? send=null¶
Enable capability negotiation to send multiple path advertisements to a single peer for a single NLRI belonging to the AFI/SAFI
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::add_paths_send_max_t? send_max=null¶
Send the N best paths for a single NLRI, or as many as possible until there are no more valid paths to send. This ensures the best path is advertised but does not limit the additional paths to being ‘used’ paths.
- attribute bool? send_multipath=null¶
Send the used paths for a single NLRI, including all paths that are multipaths. :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.add_paths [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::Evpn¶
Parents:
nokia_srlinux::Base
Options related to the EVPN address family Yang definition can be found here: srl_nokia-bgp.yang:L3324
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of EVPN routes with IPv6 next-hops to peers If this is set to true and the local-address used towards the peer is an IPv6 address and BGP is supposed to apply next-hop-self then the route is advertised with the IPv6 local-address as the BGP next-hop. If this is set to false, then the EVPN route is advertised with an IPv4 next-hop.
- attribute bool? inter_as_vpn=null¶
When set to true, received EVPN routes that are not imported by any network-instance are retained in the BGP RIB and considered ‘used’ so that they can be propagated to any EBGP or IBGP peer. This command supersedes the effect of keep-all-routes.
- attribute bool? keep_all_routes=null¶
When this is set to true all received EVPN routes are retained in the RIB-IN, even those not imported by any network-instance; these routes display as ‘rejected’ and cannot be propagated to other peers. When this is false, EVPN routes that are not imported by any network-instance are dropped and not retained in the BGP RIB-IN; policy changes affecting received EVPN routes will trigger the sending of ROUTE_REFRESH messages towards all EVPN family peers.
- attribute bool? rapid_update=null¶
When this is set to true, EVPN UPDATEs advertising reachability and withdrawals are advertised immediately, bypassing the session level min-route-advertisement-interval. When this is false, reachability updates and withdrawals are subject to the MRAI interval. :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the EVPN address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.evpn [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast¶
Parents:
nokia_srlinux::Base
Options related to the labeled IPv4-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L3192
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? rapid_update=null¶
When true, label-ipv4 update messages are advertised immediately, bypassing the MRAI When this is false, reachability updates and withdrawals are subject to the MRAI interval.
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel backup_paths: :rel convergence: Options for controlling and monitoring routing convergence of the relevant address family :rel next_hop_resolution: Options for controlling next-hop resolution procedures :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the labeled IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.ipv4_labeled_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::BackupPaths backup_paths [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast¶
Parents:
nokia_srlinux::Base
Options related to the IPv4-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L3185
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel convergence: Options for controlling and monitoring routing convergence of the relevant address family :rel next_hop_resolution: Options for controlling next-hop resolution procedures :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.ipv4_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast¶
Parents:
nokia_srlinux::Base
Options related to the labeled IPv6-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L3262
- attribute bool? rapid_update=null¶
When true, label-ipv6 update messages are advertised immediately, bypassing the MRAI When this is false, reachability updates and withdrawals are subject to the MRAI interval. :rel backup_paths: :rel convergence: Options for controlling and monitoring routing convergence of the relevant address family :rel next_hop_resolution: Options for controlling next-hop resolution procedures :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the labeled IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.ipv6_labeled_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::BackupPaths backup_paths [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast¶
Parents:
nokia_srlinux::Base
Options related to the IPv6-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L3256
- Rel convergence:
Options for controlling and monitoring routing convergence of the relevant address family
- Rel next_hop_resolution:
Options for controlling next-hop resolution procedures
- Rel parent_afi_safi:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.ipv6_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv4Unicast¶
Parents:
nokia_srlinux::Base
Options related to the VPN-IPv4 unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L3216
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? inter_as_vpn=null¶
When set to true, received VPN-IPv4 routes that are not imported by any network-instance are retained in the BGP RIB and considered ‘used’ so that they can be propagated to any EBGP or IBGP peer. This command supersedes the effect of keep-all-routes. This command triggers the programming of a VPN label swap operation for each received VPN-IPv4 route.
- attribute bool? next_hop_self_route_reflector=null¶
When set to true, received VPN-IPv4 routes are kept in the RIB and readvertised to the other route reflector clients with a local next-hop and VPN label This command triggers the programming of a VPN label swap operation for each received VPN-IPv4 route.
- attribute bool? rapid_update=null¶
When true, vpn-ipv4 update messages are advertised immediately, bypassing the MRAI When this is false, reachability updates and withdrawals are subject to the MRAI interval.
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel convergence: Options for controlling and monitoring routing convergence of the relevant address family :rel next_hop_resolution: Options for controlling next-hop resolution procedures :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv4 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.l3vpn_ipv4_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv6Unicast¶
Parents:
nokia_srlinux::Base
Options related to the VPN-IPv6 unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L3285
- attribute bool? inter_as_vpn=null¶
When set to true, received VPN-IPv6 routes that are not imported by any network-instance are retained in the BGP RIB and considered ‘used’ so that they can be propagated to any EBGP or IBGP peer. This command supersedes the effect of keep-all-routes. This command triggers the programming of a VPN label swap operation for each received VPN-IPv6 route.
- attribute bool? next_hop_self_route_reflector=null¶
When set to true, received VPN-IPv6 routes are kept in the RIB and readvertised to the other route reflector clients with a local next-hop and VPN label This command triggers the programming of a VPN label swap operation for each received VPN-IPv6 route.
- attribute bool? rapid_update=null¶
When true, vpn-ipv6 update messages are advertised immediately, bypassing the MRAI When this is false, reachability updates and withdrawals are subject to the MRAI interval. :rel convergence: Options for controlling and monitoring routing convergence of the relevant address family :rel next_hop_resolution: Options for controlling next-hop resolution procedures :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv6 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.l3vpn_ipv6_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::Convergence convergence [0:1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::Multipath¶
Parents:
nokia_srlinux::Base
Options related to BGP multipath Yang definition can be found here: srl_nokia-bgp.yang:L2494
- attribute bool? allow_multiple_as=null¶
When set to true, BGP is allowed to build a multipath set using BGP routes with different neighbor AS (most recent AS in the AS_PATH) When set to false, BGP is only allowed to use non-best paths for ECMP if they meet the multipath criteria and they have the same neighbor AS as the best path
- attribute nokia_srlinux::types::srl_nokia_bgp::ip_ecmp? max_paths_level_1=null¶
The maximum number of BGP ECMP next-hops for BGP routes with an NLRI belonging to the address family of this configuration context
- attribute nokia_srlinux::types::srl_nokia_bgp::ip_ecmp? max_paths_level_2=null¶
The maximum number of resolving ECMP next-hops per BGP next-hop associated with BGP routes having an NLRI belonging to the address family of this configuration context :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to BGP multipath
other end:
nokia_srlinux::network_instance::protocols::bgp::AfiSafi.multipath [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::BackupPaths¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L3197
- attribute bool? install=null¶
Install backup path for every NLRI in the address family, when a suitable one exists :rel parent_ipv4_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast parent_ipv4_labeled_unicast [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast.backup_paths [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::Convergence¶
Parents:
nokia_srlinux::Base
Options for controlling and monitoring routing convergence of the relevant address family Yang definition can be found here: srl_nokia-bgp.yang:L2405
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::convergence_max_wait_to_advertise_t? max_wait_to_advertise=null¶
The maximum amount of time, in seconds, measured from the time when the first session (configured or dynamic) that supports the address family comes up after a BGP restart, until BGP is allowed to advertise any routes in that address family to any peer The value of this leaf must always be greater than or equal to the operational value of min-wait-to-advertise. The default value is 3x the value of min-wait-to-advertise. A value of 0 means the feature is disabled and there is no additional delay before advertising routes of the address family. :rel parent_ipv4_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast parent_ipv4_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options for controlling next-hop resolution procedures Yang definition can be found here: srl_nokia-bgp.yang:L2580
- Rel ipv4_next_hops:
Options related to the resolution of BGP next-hops that are IPv4 addresses
- Rel ipv6_next_hops:
Options related to the resolution of BGP next-hops that are IPv6 addresses
- Rel parent_ipv4_labeled_unicast:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4LabeledUnicast parent_ipv4_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv4NextHops ipv4_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv6NextHops ipv6_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv4NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv4 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2583
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv6NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv6 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2617
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2586
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2602
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2620
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2636
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::Convergence¶
Parents:
nokia_srlinux::Base
Options for controlling and monitoring routing convergence of the relevant address family Yang definition can be found here: srl_nokia-bgp.yang:L2405
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::convergence_max_wait_to_advertise_t? max_wait_to_advertise=null¶
The maximum amount of time, in seconds, measured from the time when the first session (configured or dynamic) that supports the address family comes up after a BGP restart, until BGP is allowed to advertise any routes in that address family to any peer The value of this leaf must always be greater than or equal to the operational value of min-wait-to-advertise. The default value is 3x the value of min-wait-to-advertise. A value of 0 means the feature is disabled and there is no additional delay before advertising routes of the address family. :rel parent_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast parent_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options for controlling next-hop resolution procedures Yang definition can be found here: srl_nokia-bgp.yang:L2521
- Rel ipv4_next_hops:
Options related to the resolution of BGP next-hops that are IPv4 addresses
- Rel ipv6_next_hops:
Options related to the resolution of BGP next-hops that are IPv6 addresses
- Rel parent_ipv4_unicast:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast parent_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv4Unicast.next_hop_resolution [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::Ipv4NextHops ipv4_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::Ipv6NextHops ipv6_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::Ipv4NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv4 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2525
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::Ipv6NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv6 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2550
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2528
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv4_next_hops::tunnel_resolution_mode_t? mode=null¶
Mode to control the order of tunnel resolution compared to route resolution :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2554
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv6_next_hops::tunnel_resolution_mode_t? mode=null¶
Mode to control the order of tunnel resolution compared to route resolution :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::BackupPaths¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L3266
- attribute bool? install=null¶
Install backup path for every NLRI in the address family, when a suitable one exists :rel parent_ipv6_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast parent_ipv6_labeled_unicast [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast.backup_paths [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::Convergence¶
Parents:
nokia_srlinux::Base
Options for controlling and monitoring routing convergence of the relevant address family Yang definition can be found here: srl_nokia-bgp.yang:L2405
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::convergence_max_wait_to_advertise_t? max_wait_to_advertise=null¶
The maximum amount of time, in seconds, measured from the time when the first session (configured or dynamic) that supports the address family comes up after a BGP restart, until BGP is allowed to advertise any routes in that address family to any peer The value of this leaf must always be greater than or equal to the operational value of min-wait-to-advertise. The default value is 3x the value of min-wait-to-advertise. A value of 0 means the feature is disabled and there is no additional delay before advertising routes of the address family. :rel parent_ipv6_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast parent_ipv6_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options for controlling next-hop resolution procedures Yang definition can be found here: srl_nokia-bgp.yang:L2580
- Rel ipv4_next_hops:
Options related to the resolution of BGP next-hops that are IPv4 addresses
- Rel ipv6_next_hops:
Options related to the resolution of BGP next-hops that are IPv6 addresses
- Rel parent_ipv6_labeled_unicast:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6LabeledUnicast parent_ipv6_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv4NextHops ipv4_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv6NextHops ipv6_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv4NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv4 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2583
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv6NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv6 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2617
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2586
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2602
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2620
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2636
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::Convergence¶
Parents:
nokia_srlinux::Base
Options for controlling and monitoring routing convergence of the relevant address family Yang definition can be found here: srl_nokia-bgp.yang:L2405
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::convergence_max_wait_to_advertise_t? max_wait_to_advertise=null¶
The maximum amount of time, in seconds, measured from the time when the first session (configured or dynamic) that supports the address family comes up after a BGP restart, until BGP is allowed to advertise any routes in that address family to any peer The value of this leaf must always be greater than or equal to the operational value of min-wait-to-advertise. The default value is 3x the value of min-wait-to-advertise. A value of 0 means the feature is disabled and there is no additional delay before advertising routes of the address family. :rel parent_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast parent_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options for controlling next-hop resolution procedures Yang definition can be found here: srl_nokia-bgp.yang:L2521
- Rel ipv4_next_hops:
Options related to the resolution of BGP next-hops that are IPv4 addresses
- Rel ipv6_next_hops:
Options related to the resolution of BGP next-hops that are IPv6 addresses
- Rel parent_ipv6_unicast:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast parent_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::Ipv6Unicast.next_hop_resolution [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::Ipv4NextHops ipv4_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::Ipv6NextHops ipv6_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::Ipv4NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv4 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2525
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::Ipv6NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv6 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2550
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2528
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv4_next_hops::tunnel_resolution_mode_t? mode=null¶
Mode to control the order of tunnel resolution compared to route resolution :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2554
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv6_next_hops::tunnel_resolution_mode_t? mode=null¶
Mode to control the order of tunnel resolution compared to route resolution :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::Convergence¶
Parents:
nokia_srlinux::Base
Options for controlling and monitoring routing convergence of the relevant address family Yang definition can be found here: srl_nokia-bgp.yang:L2405
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::convergence_max_wait_to_advertise_t? max_wait_to_advertise=null¶
The maximum amount of time, in seconds, measured from the time when the first session (configured or dynamic) that supports the address family comes up after a BGP restart, until BGP is allowed to advertise any routes in that address family to any peer The value of this leaf must always be greater than or equal to the operational value of min-wait-to-advertise. The default value is 3x the value of min-wait-to-advertise. A value of 0 means the feature is disabled and there is no additional delay before advertising routes of the address family. :rel parent_l3vpn_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv4Unicast parent_l3vpn_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv4Unicast.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options for controlling next-hop resolution procedures Yang definition can be found here: srl_nokia-bgp.yang:L2580
- Rel ipv4_next_hops:
Options related to the resolution of BGP next-hops that are IPv4 addresses
- Rel ipv6_next_hops:
Options related to the resolution of BGP next-hops that are IPv6 addresses
- Rel parent_l3vpn_ipv4_unicast:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv4Unicast parent_l3vpn_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv4NextHops ipv4_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv6NextHops ipv6_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv4NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv4 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2583
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv6NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv6 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2617
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2586
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2602
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2620
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2636
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::Convergence¶
Parents:
nokia_srlinux::Base
Options for controlling and monitoring routing convergence of the relevant address family Yang definition can be found here: srl_nokia-bgp.yang:L2405
- attribute nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::convergence_max_wait_to_advertise_t? max_wait_to_advertise=null¶
The maximum amount of time, in seconds, measured from the time when the first session (configured or dynamic) that supports the address family comes up after a BGP restart, until BGP is allowed to advertise any routes in that address family to any peer The value of this leaf must always be greater than or equal to the operational value of min-wait-to-advertise. The default value is 3x the value of min-wait-to-advertise. A value of 0 means the feature is disabled and there is no additional delay before advertising routes of the address family. :rel parent_l3vpn_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv6Unicast parent_l3vpn_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for controlling and monitoring routing convergence of the relevant address family
other end:
nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv6Unicast.convergence [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options for controlling next-hop resolution procedures Yang definition can be found here: srl_nokia-bgp.yang:L2580
- Rel ipv4_next_hops:
Options related to the resolution of BGP next-hops that are IPv4 addresses
- Rel ipv6_next_hops:
Options related to the resolution of BGP next-hops that are IPv6 addresses
- Rel parent_l3vpn_ipv6_unicast:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::L3vpnIpv6Unicast parent_l3vpn_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for controlling next-hop resolution procedures
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv4NextHops ipv4_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv6NextHops ipv6_next_hops [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv4NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv4 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2583
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv4 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv6NextHops¶
Parents:
nokia_srlinux::Base
Options related to the resolution of BGP next-hops that are IPv6 addresses Yang definition can be found here: srl_nokia-bgp.yang:L2617
- Rel parent_next_hop_resolution:
Relation to parent container
- Rel route_resolution:
Options related to resolution using IP routes in the FIB
- Rel tunnel_resolution:
Options related to resolution using tunnels in the tunnel table
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::NextHopResolution parent_next_hop_resolution [1]¶
Relation to parent container Peer relation: Options related to the resolution of BGP next-hops that are IPv6 addresses
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution route_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution tunnel_resolution [0:1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv4_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2586
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv4_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2602
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv4_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv4NextHops parent_ipv4_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv6_next_hops::RouteResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using IP routes in the FIB Yang definition can be found here: srl_nokia-bgp.yang:L2620
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable route resolution if no resolving tunnel is found
- attribute bool? ignore_default_routes=null¶
Ignore default routes, regardless of route type :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using IP routes in the FIB
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv6_next_hops::TunnelResolution¶
Parents:
nokia_srlinux::Base
Options related to resolution using tunnels in the tunnel table Yang definition can be found here: srl_nokia-bgp.yang:L2636
- attribute string[]? allowed_tunnel_types=null¶
List of allowed tunnel types :rel parent_ipv6_next_hops: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::Ipv6NextHops parent_ipv6_next_hops [1]¶
Relation to parent container Peer relation: Options related to resolution using tunnels in the tunnel table
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::as_path_options::RemovePrivateAs¶
Parents:
nokia_srlinux::Base
Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers Yang definition can be found here: srl_nokia-bgp.yang:L2825
- attribute bool? ignore_peer_as=null¶
If set to true then do not delete or replace a private AS number that is the same as the peer AS number
- attribute bool? leading_only=null¶
If set to true then only delete or replace private AS numbers that appear before the first occurrence of a non-private ASN in the sequence of most recent ASNs in the AS path
- attribute nokia_srlinux::network_instance::protocols::bgp::as_path_options::remove_private_as_mode_t? mode=null¶
The method by which private AS numbers are removed from the advertised AS_PATH attribute :rel parent_as_path_options: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::AsPathOptions parent_as_path_options [1]¶
Relation to parent container Peer relation: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
other end:
nokia_srlinux::network_instance::protocols::bgp::AsPathOptions.remove_private_as [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::bgp_label::LabeledUnicast¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2687
- attribute string? dynamic_label_block=null¶
Reference to a dynamic label block :rel parent_bgp_label: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::BgpLabel parent_bgp_label [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::BgpLabel.labeled_unicast [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::Accept¶
Parents:
nokia_srlinux::Base
Options related to the acceptance of dynamic BGP sessions from remote peers Yang definition can be found here: srl_nokia-bgp.yang:L2926
- attribute yang::types::uint16? max_sessions=null¶
The maximum number of incoming BGP sessions that will be accepted by the router A value of 0 means no limit. :rel match: List of prefix and group-id combinations from which incoming TCP connections to port 179 will be accepted An incoming TCP connection to port 179 is matched to a list entry if: (a) the source IP does not match a configured BGP neighbor address (b) the list entry prefix is the longest prefix match of the source IP. (c) the source IP is not an IPv6 link-local address associated with an (unnumbered) interface configured for dynamic-neighbor sessions. :rel parent_dynamic_neighbors: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors parent_dynamic_neighbors [1]¶
Relation to parent container Peer relation: Options related to the acceptance of dynamic BGP sessions from remote peers
other end:
nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors.accept [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::Match match [0:*]¶
Relation to parent container Peer relation: List of prefix and group-id combinations from which incoming TCP connections to port 179 will be accepted
An incoming TCP connection to port 179 is matched to a list entry if: (a) the source IP does not match a configured BGP neighbor address (b) the list entry prefix is the longest prefix match of the source IP. (c) the source IP is not an IPv6 link-local address associated with an (unnumbered) interface configured for dynamic-neighbor sessions.
other end:
nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::Match.parent_accept [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::Interface¶
Parents:
nokia_srlinux::Base
List of interfaces on which dynamic sessions based on IPv6 link-local address discovery are accepted and initiated. Yang definition can be found here: srl_nokia-bgp.yang:L2974
- attribute nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::interface_allowed_peer_as_t[]? allowed_peer_as=null¶
Specifies the allowed AS numbers of dynamic BGP neighbors on this interface. If the OPEN message from a peer on this interface contains a MyAS number that is not in this allowed list then a NOTIFICATION is sent to the peer with the indication Bad Peer AS. Each entry in this list can be a single AS number or a range of AS numbers in the string format as1..as2.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index> The referenced subinterface should be enabled for IPv6 and should be configured to accept and send IPv6 router advertisement messages. The referenced subinterface does not need any IPv4 addresses or global-unicast IPv6 addresses (i.e. it can be an unnumbered interface). When a subinterface is present in this list, incoming TCP connections to the BGP well-known port that are received on this subinterface and sourced from an IPv6 link local address and destined for the IPv6 link local address of the subinterface are automatically accepted. When a subinterface is present in this list, received IPv6 router advertisement messages on this subinterface automatically trigger BGP session setup towards the sender of these messages, if there is not already an established session.
- attribute yang::types::uint16? max_sessions=null¶
The maximum number of dynamic sessions that are allowed to be setup on the interface as a result of accepting sessions from link-local addresses or initiating sessions by means of receiving IPv6 router advertisements.
- attribute nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::interface_peer_group_t? peer_group=null¶
Reference to a peer-group Specifies the peer-group to associate with dynamic BGP neighbors on this interface. The peer-group provides all the parameters needed to complete the establishment of the dynamic session. :rel parent_dynamic_neighbors: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors parent_dynamic_neighbors [1]¶
Relation to parent container Peer relation: List of interfaces on which dynamic sessions based on IPv6 link-local address discovery are accepted and initiated.
other end:
nokia_srlinux::network_instance::protocols::bgp::DynamicNeighbors.interface [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::Match¶
Parents:
nokia_srlinux::Base
List of prefix and group-id combinations from which incoming TCP connections to port 179 will be accepted
An incoming TCP connection to port 179 is matched to a list entry if: (a) the source IP does not match a configured BGP neighbor address (b) the list entry prefix is the longest prefix match of the source IP. (c) the source IP is not an IPv6 link-local address associated with an (unnumbered) interface configured for dynamic-neighbor sessions. Yang definition can be found here: srl_nokia-bgp.yang:L2929
- attribute nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::match_allowed_peer_as_t[]? allowed_peer_as=null¶
The allowed AS numbers that can establish incoming BGP sessions from this prefix and group-id-range combination If the OPEN message from a peer matched to this prefix contains a MyAS number that is not in this allowed list then a NOTIFICATION is sent to the peer with the indication Bad Peer AS. Each entry in this list can be a single AS number or a range of AS numbers in the format as1..as2
- attribute nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::match_peer_group_t? peer_group=null¶
Reference to a peer-group When an incoming session is matched to this list entry it is associated with the peer-group referenced by this leaf. The peer-group provides all the parameters needed to complete the establishment of the dynamic session. If the referenced peer-group has a configured peer-as this is ignored by dynamic BGP sessions using the group as a template.
- attribute nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::match_prefix_t prefix¶
The IP prefix used to match an incoming dynamic BGP session to a group. :rel parent_accept: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::Accept parent_accept [1]¶
Relation to parent container Peer relation: List of prefix and group-id combinations from which incoming TCP connections to port 179 will be accepted
An incoming TCP connection to port 179 is matched to a list entry if: (a) the source IP does not match a configured BGP neighbor address (b) the list entry prefix is the longest prefix match of the source IP. (c) the source IP is not an IPv6 link-local address associated with an (unnumbered) interface configured for dynamic-neighbor sessions.
other end:
nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::Accept.match [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi¶
Parents:
nokia_srlinux::Base
List of address families supported by the BGP peer group Yang definition can be found here: srl_nokia-bgp.yang:L499
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf indicates whether the AFI-SAFI is enabled for the peer group
- attribute string afi_safi_name¶
The name of a BGP address family, which translates to a specific AFI value and a specific SAFI value
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes :rel add_paths: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI :rel evpn: Options related to the EVPN address family :rel ipv4_labeled_unicast: Options related to the labeled-IPv4-unicast address family :rel ipv4_unicast: Options related to the IPv4-unicast address family :rel ipv6_labeled_unicast: Options related to the labeled IPv6-unicast address family :rel ipv6_unicast: Options related to the IPv6-unicast address family :rel l3vpn_ipv4_unicast: Options related to the VPN-IPv4 unicast address family :rel l3vpn_ipv6_unicast: Options related to the VPN-IPv6 unicast address family :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: List of address families supported by the BGP peer group
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.afi_safi [0:*]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::AddPaths add_paths [0:1]¶
Relation to parent container Peer relation: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::AddPaths.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Options related to the EVPN address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Evpn.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4LabeledUnicast ipv4_labeled_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the labeled-IPv4-unicast address family
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6LabeledUnicast ipv6_labeled_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the labeled IPv6-unicast address family
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::L3vpnIpv4Unicast l3vpn_ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv4 unicast address family
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::L3vpnIpv6Unicast l3vpn_ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv6 unicast address family
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::AsPathOptions¶
Parents:
nokia_srlinux::Base
Options for handling the AS_PATH in received BGP routes Yang definition can be found here: srl_nokia-bgp.yang:L350
- attribute yang::types::uint8? allow_own_as=null¶
The maximum number of times the global AS number or a local AS number of the BGP instance can appear in any received AS_PATH before it is considered a loop and considered invalid When this value is changed the new value applies only to the routes received after the change is committed.
- attribute bool? replace_peer_as=null¶
If set to true then replace every occurrence of the peer AS number that is present in the advertised AS path with the local AS number used towards the peer :rel parent_group: Relation to parent container :rel remove_private_as: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Options for handling the AS_PATH in received BGP routes
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.as_path_options [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::as_path_options::RemovePrivateAs remove_private_as [0:1]¶
Relation to parent container Peer relation: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::Authentication¶
Parents:
nokia_srlinux::Base
Container with authentication options that apply to all peers in this peer-group Yang definition can be found here: srl_nokia-bgp.yang:L408
- attribute string? keychain=null¶
Reference to a keychain. The keychain type must be tcp-md5.
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? password=null¶
Configures an MD5 authentication password for use with neighboring devices. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Container with authentication options that apply to all peers in this peer-group
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::FailureDetection¶
Parents:
nokia_srlinux::Base
Options related to methods of detecting BGP session failure Yang definition can be found here: srl_nokia-bgp.yang:L432
- attribute bool? enable_bfd=null¶
The true setting enables Bi-directional Forwarding Detection on BGP sessions belonging to the peer group
- attribute bool? fast_failover=null¶
The true setting causes EBGP and IBGP sessions in the peer group to drop immediately (and not wait for hold timer expiry) when the local interface that they depend upon for neighbor reachability goes down :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.failure_detection [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::GracefulRestart¶
Parents:
nokia_srlinux::Base
Options related to router behavior as a graceful restart helper Yang definition can be found here: srl_nokia-bgp.yang:L468
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable graceful restart helper for all address families
- attribute nokia_srlinux::network_instance::protocols::bgp::group::graceful_restart_requested_restart_time_t? requested_restart_time=null¶
The restart time encoded in this router’s GR capability. If the neighbor honors this request then this is the maximum time allowed for this router to re-establish its TCP connection after a restart. If this time is exceeded, the neighbor is expected to flush stale routes that it was maintaining on behalf of this router.
- attribute nokia_srlinux::network_instance::protocols::bgp::group::graceful_restart_stale_routes_time_t? stale_routes_time=null¶
The maximum number of seconds that routes received from a neighbor that is being helped remain stale until they are deleted. Routes of AFI/SAFI X received from peer Y are marked stale when peer Y goes down and its previous GR capability included AFI/SAFI X. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Options related to router behavior as a graceful restart helper
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.graceful_restart [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::LocalAs¶
Parents:
nokia_srlinux::Base
Options related to the local autonomous-system number advertised by this router to its peers Yang definition can be found here: srl_nokia-bgp.yang:L808
- attribute nokia_srlinux::types::srl_nokia_common::as_number? as_number=null¶
The local autonomous system number used to override the global ASN on this group of BGP sessions Sets the ASN value that this router sends in its OPEN message towards its peer in the group.
- attribute bool? prepend_global_as=null¶
When set to true, the global ASN value is prepended to the AS path in outbound routes towards each BGP peer in the group If a session is EBGP (peer-as is not equal to the local-as) then the local-as is prepended as the final step, so that the local-as is the first element in the AS_PATH received by the peer.
- attribute bool? prepend_local_as=null¶
When set to true, the local AS value is prepended to the AS path of inbound routes from each EBGP peer belonging to the group :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Options related to the local autonomous-system number advertised by this router to its peers
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.local_as [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::Multihop¶
Parents:
nokia_srlinux::Base
Configuration parameters specifying the multihop behaviour for IBGP and EBGP peers in the peer group. Yang definition can be found here: srl_nokia-bgp.yang:L446
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When enabled, IBGP and EBGP peers in the group are allowed to be indirectly connected by up to N hops, where N is controlled by the maximum-hops parameter. When disabled, only IBGP peers within the peer group support multihop. This can be overriden on a per neighbor basis. It is inherited by neighbors in the peer-group only if maximum-hops is also specified. By default this is disabled.
- attribute nokia_srlinux::network_instance::protocols::bgp::group::multihop_maximum_hops_t? maximum_hops=null¶
This sets the maximum number of routing hops towards each peer. It determines the IP TTL value in originated BGP TCP/IP packets. By default the TTL is set to 1 towards EBGP peers and 64 towards IBGP peers. This leaf sets a new IP TTL to use towards both EBGP and IBGP peers in the peer group. This can be overriden on a per neighbor basis. It is inherited by neighbors in the peer-group only if admin-state is also specified. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Configuration parameters specifying the multihop behaviour for IBGP and EBGP peers in the peer group.
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.multihop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::RouteReflector¶
Parents:
nokia_srlinux::Base
Container with route reflection configuration options. Yang definition can be found here: srl_nokia-bgp.yang:L837
- attribute bool? client=null¶
When this is set to true all configured and dynamic BGP sessions that belong to the peer-group are considered RR clients.
- attribute nokia_srlinux::network_instance::protocols::bgp::group::route_reflector_cluster_id_t? cluster_id=null¶
The cluster-id to insert into the CLUSTER_LIST attribute when reflecting routes received by or sent to each client in the peer-group. The default is inherited from instance level configuration. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Container with route reflection configuration options.
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.route_reflector [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::SendDefaultRoute¶
Parents:
nokia_srlinux::Base
Options for controlling the generation of default routes towards group peers Yang definition can be found here: srl_nokia-bgp.yang:L875
- attribute string? export_policy=null¶
The name of a policy that should be applied to the advertised default routes, in order to set their attributes to non-default values Only the default-action of this policy is parsed and applied.
- attribute bool? ipv4_unicast=null¶
Enables the sending of a synthetically generated default IPv4 route [0/0] to each peer in the group
- attribute bool? ipv6_unicast=null¶
Enables the sending of a synthetically generated default IPv6 route [::/0] to each peer in the group :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Options for controlling the generation of default routes towards group peers
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.send_default_route [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::Timers¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L900
- attribute nokia_srlinux::network_instance::protocols::bgp::group::timers_connect_retry_t? connect_retry=null¶
The time interval in seconds between successive attempts to establish a session with a peer
- attribute nokia_srlinux::network_instance::protocols::bgp::group::timers_hold_time_t? hold_time=null¶
The hold-time interval in seconds that the router proposes to the peer in its OPEN message The actual in-use hold-time is negotiated to the lowest value proposed by the two peers. A negotiated value of 0 suppresses the sending of keepalives by both peers.
- attribute nokia_srlinux::network_instance::protocols::bgp::group::timers_keepalive_interval_t? keepalive_interval=null¶
The interval in seconds between successive keepalive messages sent to the peer The period between one keepalive message and the next is the minimum of this configured value and 1/3 of the negotiated hold-time duration. A value of 0 suppresses the sending of keepalives to the peer.
- attribute nokia_srlinux::network_instance::protocols::bgp::group::timers_minimum_advertisement_interval_t? minimum_advertisement_interval=null¶
The value assigned to the MinRouteAdvertisementIntervalTimer of RFC 4271, for both EBGP and IBGP sessions Each session runs its own independent timer and the timer affects both route advertisements and route withdrawals, regardless of address family. For route withdrawals only, this timer is bypassed if rapid-withdrawal is set to true.
- attribute yang::types::uint16? prefix_limit_restart_timer=null¶
Time interval in seconds after which the BGP session is re-established after being torn down due to exceeding any prefix limit (of any address family) This only applies if prevent-teardown is false. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.timers [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::TraceOptions¶
Parents:
nokia_srlinux::Base
Debug traceoptions for BGP Yang definition can be found here: srl_nokia-bgp.yang:L163
- Rel flag:
Tracing parameters
- Rel parent_group:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation: Debug traceoptions for BGP
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::trace_options::Flag flag [0:*]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::protocols::bgp::group::trace_options::Flag.parent_trace_options [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::Transport¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L954
- attribute nokia_srlinux::network_instance::protocols::bgp::group::transport_local_address_t? local_address=null¶
The local TCP endpoint of used for all BGP sessions in the group This also the source address for next-hop-self, if it applies. The local-address can be specified as an IP address that is resolvable to a local interface. This address must be the primary address of an interface, otherwise the session will not come up.
- attribute bool? mtu_discovery=null¶
Turns path mtu discovery for BGP TCP sessions on (true) or off (false)
- attribute bool? passive_mode=null¶
The true setting causes BGP to wait for the peer to initiate the TCP connection The false setting causes BGP to initiate a TCP connection whenever the BGP session is started or restarted.
- attribute nokia_srlinux::network_instance::protocols::bgp::group::transport_tcp_mss_t? tcp_mss=null¶
The maximum segment size of BGP TCP packets The actual value used in the transmit direction towards a particular peer should be checked at the neighbor level. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Group parent_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::Group.transport [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::AddPaths¶
Parents:
nokia_srlinux::Base
Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI Yang definition can be found here: srl_nokia-bgp.yang:L531
- attribute bool? receive=null¶
Enable capability negotiation to receive multiple path advertisements from a single peer for a single NLRI belonging to the AFI/SAFI
- attribute bool? send=null¶
Enable capability negotiation to send multiple path advertisements to a single peer for a single NLRI belonging to the AFI/SAFI
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::add_paths_send_max_t? send_max=null¶
Send the N best paths for a single NLRI, or as many as possible until there are no more valid paths to send. This ensures the best path is advertised but does not limit the additional paths to being ‘used’ paths.
- attribute bool? send_multipath=null¶
Send the used paths for a single NLRI, including all paths that are multipaths. :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.add_paths [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Evpn¶
Parents:
nokia_srlinux::Base
Options related to the EVPN address family Yang definition can be found here: srl_nokia-bgp.yang:L769
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of EVPN routes with IPv6 next-hops to peers in the peer-group If this is set to true and the local-address used towards the peer is an IPv6 address and BGP is supposed to apply next-hop-self then the route is advertised with the IPv6 local-address as the BGP next-hop. If this is set to false, then the EVPN route is advertised with an IPv4 next-hop. :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of EVPN routes allowed to be received from each peer in the peer-group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the EVPN address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.evpn [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::evpn::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of EVPN routes allowed to be received from each peer in the peer-group
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::evpn::PrefixLimit.parent_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4LabeledUnicast¶
Parents:
nokia_srlinux::Base
Options related to the labeled-IPv4-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L605
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? next_hop_unchanged=null¶
When set to true, do not change the BGP next-hop towards group peers, even if next-hop-self is normally performed
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of label-IPv4 routes allowed to be received from each peer in the group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the labeled-IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.ipv4_labeled_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_labeled_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of label-IPv4 routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast¶
Parents:
nokia_srlinux::Base
Options related to the IPv4-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L574
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel link_bandwidth: :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of IPv4 routes allowed to be received from each peer in the group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.ipv4_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::LinkBandwidth link_bandwidth [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv4 routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6LabeledUnicast¶
Parents:
nokia_srlinux::Base
Options related to the labeled IPv6-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L703
- attribute bool? next_hop_unchanged=null¶
When set to true, do not change the BGP next-hop towards group peers, even if next-hop-self is normally performed :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of labeled IPv6 routes allowed to be received from each peer in the group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the labeled IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.ipv6_labeled_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_labeled_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of labeled IPv6 routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast¶
Parents:
nokia_srlinux::Base
Options related to the IPv6-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L673
- Rel link_bandwidth:
- Rel parent_afi_safi:
Relation to parent container
- Rel prefix_limit:
Options for configuring the maximum number of IPv6 routes allowed to be received from each peer in the group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.ipv6_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::LinkBandwidth link_bandwidth [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv6 routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::L3vpnIpv4Unicast¶
Parents:
nokia_srlinux::Base
Options related to the VPN-IPv4 unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L642
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from each peer in the group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv4 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.l3vpn_ipv4_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv4_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::L3vpnIpv6Unicast¶
Parents:
nokia_srlinux::Base
Options related to the VPN-IPv6 unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L739
- Rel parent_afi_safi:
Relation to parent container
- Rel prefix_limit:
Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from each peer in the group
- relation nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv6 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AfiSafi.l3vpn_ipv6_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv6_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::evpn::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of EVPN routes allowed to be received from each peer in the peer-group Yang definition can be found here: srl_nokia-bgp.yang:L782
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::evpn::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of EVPN routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of EVPN routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Evpn parent_evpn [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of EVPN routes allowed to be received from each peer in the peer-group
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Evpn.prefix_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_labeled_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of label-IPv4 routes allowed to be received from each peer in the group Yang definition can be found here: srl_nokia-bgp.yang:L616
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_labeled_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of label-IPv4 routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received label-IPv4 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of label-IPv4 routes received from any group peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv4_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4LabeledUnicast parent_ipv4_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of label-IPv4 routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::LinkBandwidth¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2657
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::link_bandwidth_add_next_hop_count_to_received_bgp_routes_t? add_next_hop_count_to_received_bgp_routes=null¶
Determines the weight that is internally added to the received PE-CE BGP routes The configured weight is added to all received BGP PE-CE routes for the purpose of EVPN unequal ECMP. This weight is internal and not added into any link-bandwidth extended community when readvertising the received routes to other ipv4 or ipv6 neighbors. :rel parent_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast parent_ipv4_unicast [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast.link_bandwidth [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of IPv4 routes allowed to be received from each peer in the group Yang definition can be found here: srl_nokia-bgp.yang:L578
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of IPv4 routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received IPv4 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of IPv4 routes received from any group peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast parent_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv4 routes allowed to be received from each peer in the group
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv4Unicast.prefix_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_labeled_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of labeled IPv6 routes allowed to be received from each peer in the group Yang definition can be found here: srl_nokia-bgp.yang:L713
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_labeled_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of labeled IPv6 routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received labeled IPv6 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of labeled IPv6 routes received from any group peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv6_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6LabeledUnicast parent_ipv6_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of labeled IPv6 routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::LinkBandwidth¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2657
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::link_bandwidth_add_next_hop_count_to_received_bgp_routes_t? add_next_hop_count_to_received_bgp_routes=null¶
Determines the weight that is internally added to the received PE-CE BGP routes The configured weight is added to all received BGP PE-CE routes for the purpose of EVPN unequal ECMP. This weight is internal and not added into any link-bandwidth extended community when readvertising the received routes to other ipv4 or ipv6 neighbors. :rel parent_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast parent_ipv6_unicast [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast.link_bandwidth [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of IPv6 routes allowed to be received from each peer in the group Yang definition can be found here: srl_nokia-bgp.yang:L676
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of IPv6 routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received IPv6 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of IPv6 routes received from any group peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast parent_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv6 routes allowed to be received from each peer in the group
other end:
nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::Ipv6Unicast.prefix_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv4_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from each peer in the group Yang definition can be found here: srl_nokia-bgp.yang:L647
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv4_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of VPN-IPv4 routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received VPN-IPv4 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of VPN-IPv4 routes received from any group peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_l3vpn_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::L3vpnIpv4Unicast parent_l3vpn_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv6_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from each peer in the group Yang definition can be found here: srl_nokia-bgp.yang:L743
- attribute nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv6_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of VPN-IPv6 routes that will be accepted from each neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received VPN-IPv6 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of VPN-IPv6 routes received from any group peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_l3vpn_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::L3vpnIpv6Unicast parent_l3vpn_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from each peer in the group
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::as_path_options::RemovePrivateAs¶
Parents:
nokia_srlinux::Base
Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers Yang definition can be found here: srl_nokia-bgp.yang:L360
- attribute bool? ignore_peer_as=null¶
If set to true then do not delete or replace a private AS number that is the same as the peer AS number
- attribute bool? leading_only=null¶
If set to true then only delete or replace private AS numbers that appear before the first occurrence of a non-private ASN in the sequence of most recent ASNs in the AS path
- attribute nokia_srlinux::network_instance::protocols::bgp::group::as_path_options::remove_private_as_mode_t? mode=null¶
The method by which private AS numbers are removed from the advertised AS_PATH attribute :rel parent_as_path_options: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::AsPathOptions parent_as_path_options [1]¶
Relation to parent container Peer relation: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
other end:
nokia_srlinux::network_instance::protocols::bgp::group::AsPathOptions.remove_private_as [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::group::trace_options::Flag¶
Parents:
nokia_srlinux::Base
Tracing parameters Yang definition can be found here: srl_nokia-bgp.yang:L166
- attribute nokia_srlinux::network_instance::protocols::bgp::group::trace_options::flag_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::bgp::group::trace_options::flag_name_t name¶
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::group::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::protocols::bgp::group::TraceOptions.flag [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi¶
Parents:
nokia_srlinux::Base
List of address families supported by the BGP neighbor Yang definition can be found here: srl_nokia-bgp.yang:L1764
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf indicates whether support for the AFI-SAFI is enabled/advertised to the neighbor
- attribute string afi_safi_name¶
The name of a BGP address family, which translates to a specific AFI value and a specific SAFI value
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes :rel add_paths: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI :rel evpn: Options related to the EVPN address family :rel ipv4_labeled_unicast: Options related to the labeled IPv4-unicast address family :rel ipv4_unicast: Options related to the IPv4-unicast address family :rel ipv6_labeled_unicast: Options related to the labeled-IPv6-unicast address family :rel ipv6_unicast: Options related to the IPv6-unicast address family :rel l3vpn_ipv4_unicast: Options related to the VPN-IPv4 unicast address family :rel l3vpn_ipv6_unicast: Options related to the VPN-IPv6 unicast address family :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: List of address families supported by the BGP neighbor
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.afi_safi [0:*]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::AddPaths add_paths [0:1]¶
Relation to parent container Peer relation: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::AddPaths.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Options related to the EVPN address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Evpn.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4LabeledUnicast ipv4_labeled_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the labeled IPv4-unicast address family
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4Unicast ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6LabeledUnicast ipv6_labeled_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the labeled-IPv6-unicast address family
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6Unicast ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6Unicast.parent_afi_safi [1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::L3vpnIpv4Unicast l3vpn_ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv4 unicast address family
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::L3vpnIpv6Unicast l3vpn_ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv6 unicast address family
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::AsPathOptions¶
Parents:
nokia_srlinux::Base
Options for handling the AS_PATH in received BGP routes Yang definition can be found here: srl_nokia-bgp.yang:L1570
- attribute yang::types::uint8? allow_own_as=null¶
The maximum number of times the global AS number or a local AS number of the BGP instance can appear in any received AS_PATH before it is considered a loop and considered invalid
- attribute bool? replace_peer_as=null¶
If set to true then replace every occurrence of the peer AS number that is present in the advertised AS path with the local AS number used towards the peer :rel parent_neighbor: Relation to parent container :rel remove_private_as: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Options for handling the AS_PATH in received BGP routes
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.as_path_options [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::as_path_options::RemovePrivateAs remove_private_as [0:1]¶
Relation to parent container Peer relation: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::Authentication¶
Parents:
nokia_srlinux::Base
Container with authentication options that apply to this specific peer Yang definition can be found here: srl_nokia-bgp.yang:L1626
- attribute string? keychain=null¶
Reference to a keychain. The keychain type must be tcp-md5.
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? password=null¶
Configures an MD5 authentication password for use with neighboring devices. :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Container with authentication options that apply to this specific peer
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::FailureDetection¶
Parents:
nokia_srlinux::Base
Options related to methods of detecting BGP session failure Yang definition can be found here: srl_nokia-bgp.yang:L1656
- attribute bool? enable_bfd=null¶
The true setting enables Bi-directional Forwarding Detection on BGP sessions belonging to the peer group
- attribute bool? fast_failover=null¶
The true setting the EBGP or IBGP session to drop immediately (and not wait for hold timer expiry) when the local interface that it depends upon for neighbor reachability goes down :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.failure_detection [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::GracefulRestart¶
Parents:
nokia_srlinux::Base
Options related to router behavior as a graceful restart helper Yang definition can be found here: srl_nokia-bgp.yang:L1670
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable graceful restart helper for all address families
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::graceful_restart_requested_restart_time_t? requested_restart_time=null¶
The restart time encoded in this router’s GR capability. If the neighbor honors this request then this is the maximum time allowed for this router to re-establish its TCP connection after a restart. If this time is exceeded, the neighbor is expected to flush stale routes that it was maintaining on behalf of this router.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::graceful_restart_stale_routes_time_t? stale_routes_time=null¶
The maximum number of seconds that routes received from a helped peer remain stale until they are deleted Routes of AFI/SAFI X received from peer Y are marked stale when peer Y goes down and its previous GR capability included AFI/SAFI X. :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Options related to router behavior as a graceful restart helper
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.graceful_restart [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::LocalAs¶
Parents:
nokia_srlinux::Base
Options related to the local autonomous-system number advertised by this router to the peer Yang definition can be found here: srl_nokia-bgp.yang:L2188
- attribute nokia_srlinux::types::srl_nokia_common::as_number? as_number=null¶
The local autonomous system number used to override the global ASN on this session Sets the ASN value that this router sends in its OPEN message towards its peer.
- attribute bool? prepend_global_as=null¶
When set to true, the global ASN value is prepended to the AS path in outbound routes towards the peer If a session is EBGP (peer-as is not equal to the local-as) then the local-as is prepended as the final step, so that the local-as is the first element in the AS_PATH received by the peer.
- attribute bool? prepend_local_as=null¶
When set to true, the local AS value is prepended to the AS path of inbound routes from the peer :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Options related to the local autonomous-system number advertised by this router to the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.local_as [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::Multihop¶
Parents:
nokia_srlinux::Base
Configuration parameters specifying the multihop behaviour for an EBGP peer. This is not applicable to an IBGP peer. Yang definition can be found here: srl_nokia-bgp.yang:L1744
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When enabled, the peer is allowed to be indirectly connected by up to N hops, where N is controlled by the maximum-hops parameter. When disabled, multihop is allowed only if the peer type is IBGP. This overrides the group setting for admin-state.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::multihop_maximum_hops_t? maximum_hops=null¶
This sets the maximum number of routing hops towards the peer. It determines the IP TTL value in originated BGP TCP/IP packets. By default the TTL is set to 1 towards an EBGP peer and 64 towards an IBGP peer. This overrides the group setting for maximum-hops. :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Configuration parameters specifying the multihop behaviour for an EBGP peer. This is not applicable to an IBGP peer.
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.multihop [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::RouteReflector¶
Parents:
nokia_srlinux::Base
Container with route reflection configuration options. Yang definition can be found here: srl_nokia-bgp.yang:L2217
- attribute bool? client=null¶
When this is set to true this BGP session is considered an RR client.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::route_reflector_cluster_id_t? cluster_id=null¶
The cluster-id to insert into the CLUSTER_LIST attribute when reflecting routes received by or sent to this client. The default is inherited from group or instance level configuration. :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Container with route reflection configuration options.
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.route_reflector [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::SendDefaultRoute¶
Parents:
nokia_srlinux::Base
Options for controlling the generation of default routes towards the peer Yang definition can be found here: srl_nokia-bgp.yang:L2255
- attribute string? export_policy=null¶
The name of a policy that should be applied to the advertised default routes, in order to set their attributes to non-default values Only the default-action of this policy is parsed and applied.
- attribute bool? ipv4_unicast=null¶
Enables the sending of a synthetically generated default IPv4 route [0/0] to the peer
- attribute bool? ipv6_unicast=null¶
Enables the sending of a synthetically generated default IPv6 route [::/0] to the peer :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Options for controlling the generation of default routes towards the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.send_default_route [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::Timers¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2278
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_connect_retry_t? connect_retry=null¶
The time interval in seconds between successive attempts to establish a session with a peer
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_hold_time_t? hold_time=null¶
The hold-time interval in seconds that the router proposes to the peer in its OPEN message The actual in-use hold-time is negotiated to the lowest value proposed by the two peers. A negotiated value of 0 suppresses the sending of keepalives by both peers.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_keepalive_interval_t? keepalive_interval=null¶
The interval in seconds between successive keepalive messages sent to the peer The period between one keepalive message and the next is the minimum of this configured (or inherited) value and 1/3 of the negotiated hold-time duration. A value of 0 suppresses the sending of keepalives to the peer.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::timers_minimum_advertisement_interval_t? minimum_advertisement_interval=null¶
The value assigned to the MinRouteAdvertisementIntervalTimer of RFC 4271, for both EBGP and IBGP sessions Each session runs its own independent timer and the timer affects both route advertisements and route withdrawals, regardless of address family. For route withdrawals only, this timer is bypassed if rapid-withdrawal is set to true.
- attribute yang::types::uint16? prefix_limit_restart_timer=null¶
Time interval in seconds after which the BGP session is re-established after being torn down due to exceeding any prefix limit (of any address family) This only applies if prevent-teardown is false. :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.timers [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::TraceOptions¶
Parents:
nokia_srlinux::Base
Debug traceoptions for BGP Yang definition can be found here: srl_nokia-bgp.yang:L163
- Rel flag:
Tracing parameters
- Rel parent_neighbor:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation: Debug traceoptions for BGP
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::trace_options::Flag flag [0:*]¶
Relation to parent container Peer relation: Tracing parameters
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::Transport¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2350
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::transport_local_address_t? local_address=null¶
The local TCP endpoint of used for the BGP session This also the source address for next-hop-self, if it applies. The local-address can be specified as an IP address that is resolvable to a local interface. This address must be the primary address of an interface, otherwise the session will not come up.
- attribute bool? mtu_discovery=null¶
Turns path mtu discovery on (true) or off (false)
- attribute bool? passive_mode=null¶
The true setting causes BGP to wait for the peer to initiate the TCP connection The false setting causes BGP to initiate a TCP connection whenever the BGP session is started or restarted.
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::transport_tcp_mss_t? tcp_mss=null¶
The maximum segment size of BGP TCP packets The configured value of this leaf is the TCP MSS value advertised to the peer during TCP connection setup (in the TCP MSS option), reduced if necessary to accommodate the outgoing interface IP MTU. The state value of this leaf is the operational TCP MSS used in the data transmit direction towards the peer. It may be less than the received TCP MSS option value due to adjustment for TCP options used in the transit direction and/or the path MTU discovery process (if enabled). :rel parent_neighbor: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::Neighbor parent_neighbor [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp::Neighbor.transport [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::AddPaths¶
Parents:
nokia_srlinux::Base
Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI Yang definition can be found here: srl_nokia-bgp.yang:L1809
- attribute bool? receive=null¶
Enable capability negotiation to receive multiple path advertisements from a single peer for a single NLRI belonging to the AFI/SAFI
- attribute bool? send=null¶
Enable capability negotiation to send multiple path advertisements to a single peer for a single NLRI belonging to the AFI/SAFI
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::add_paths_send_max_t? send_max=null¶
Send the N best paths for a single NLRI, or as many as possible until there are no more valid paths to send. This ensures the best path is advertised but does not limit the additional paths to being ‘used’ paths.
- attribute bool? send_multipath=null¶
Send the used paths for a single NLRI, including all paths that are multipaths. :rel parent_afi_safi: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Configure support for the advertisement and receipt of multiple paths for the AFI/SAFI
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.add_paths [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Evpn¶
Parents:
nokia_srlinux::Base
Options related to the EVPN address family Yang definition can be found here: srl_nokia-bgp.yang:L2145
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of EVPN routes with IPv6 next-hops to peers If this is set to true and the local-address used towards the peer is an IPv6 address and BGP is supposed to apply next-hop-self then the route is advertised with the IPv6 local-address as the BGP next-hop. If this is set to false, then the EVPN route is advertised with an IPv4 next-hop. :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of EVPN routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the EVPN address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.evpn [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::evpn::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of EVPN routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4LabeledUnicast¶
Parents:
nokia_srlinux::Base
Options related to the labeled IPv4-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L1920
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? next_hop_unchanged=null¶
When set to true, do not change the BGP next-hop towards group peers, even if next-hop-self is normally performed
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of label-IPv4 routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the labeled IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.ipv4_labeled_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_labeled_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of label-IPv4 routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4Unicast¶
Parents:
nokia_srlinux::Base
Options related to the IPv4-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L1876
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel link_bandwidth: :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of IPv4 routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the IPv4-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.ipv4_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::LinkBandwidth link_bandwidth [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv4 routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6LabeledUnicast¶
Parents:
nokia_srlinux::Base
Options related to the labeled-IPv6-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L2055
- attribute bool? next_hop_unchanged=null¶
When set to true, do not change the BGP next-hop towards group peers, even if next-hop-self is normally performed :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of label-IPv6 routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the labeled-IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.ipv6_labeled_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_labeled_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of label-IPv6 routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6Unicast¶
Parents:
nokia_srlinux::Base
Options related to the IPv6-unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L2012
- Rel link_bandwidth:
- Rel parent_afi_safi:
Relation to parent container
- Rel prefix_limit:
Options for configuring the maximum number of IPv6 routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the IPv6-unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.ipv6_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::LinkBandwidth link_bandwidth [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv6 routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::L3vpnIpv4Unicast¶
Parents:
nokia_srlinux::Base
Options related to the VPN-IPv4 unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L1970
- attribute bool? advertise_ipv6_next_hops=null¶
Enables advertisement of IPv4 routes with IPv6 next-hops
- attribute bool? receive_ipv6_next_hops=null¶
Enables the advertisement of the RFC 8950 capability to receive IPv4 routes with IPv6 next-hops When set to true, BGP advertises an extended NH encoding (RFC 8950) capability to its peers. This capability indicates that local router is prepared to accept BGP routes for the AFI/SAFI with IPv6 next-hops from peers in the scope of the command. When set to false, BGP handles received AFI/SAFI routes with IPv6 next-hops as an error and applies treat-as-withdraw. :rel parent_afi_safi: Relation to parent container :rel prefix_limit: Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv4 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.l3vpn_ipv4_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv4_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::L3vpnIpv6Unicast¶
Parents:
nokia_srlinux::Base
Options related to the VPN-IPv6 unicast address family Yang definition can be found here: srl_nokia-bgp.yang:L2104
- Rel parent_afi_safi:
Relation to parent container
- Rel prefix_limit:
Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from the peer
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi parent_afi_safi [1]¶
Relation to parent container Peer relation: Options related to the VPN-IPv6 unicast address family
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AfiSafi.l3vpn_ipv6_unicast [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv6_unicast::PrefixLimit prefix_limit [0:1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::evpn::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of EVPN routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L2158
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::evpn::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of EVPN routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of EVPN routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_evpn: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Evpn parent_evpn [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of EVPN routes allowed to be received from the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Evpn.prefix_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_labeled_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of label-IPv4 routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L1933
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_labeled_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of label-IPv4 routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received label-IPv4 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of label-IPv4 routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv4_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4LabeledUnicast parent_ipv4_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of label-IPv4 routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::LinkBandwidth¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2657
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::link_bandwidth_add_next_hop_count_to_received_bgp_routes_t? add_next_hop_count_to_received_bgp_routes=null¶
Determines the weight that is internally added to the received PE-CE BGP routes The configured weight is added to all received BGP PE-CE routes for the purpose of EVPN unequal ECMP. This weight is internal and not added into any link-bandwidth extended community when readvertising the received routes to other ipv4 or ipv6 neighbors. :rel parent_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4Unicast parent_ipv4_unicast [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of IPv4 routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L1880
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of IPv4 routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received IPv4 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of IPv4 routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4Unicast parent_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv4 routes allowed to be received from the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv4Unicast.prefix_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_labeled_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of label-IPv6 routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L2067
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_labeled_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of label-IPv6 routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received label-IPv6 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of label-IPv6 routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv6_labeled_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6LabeledUnicast parent_ipv6_labeled_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of label-IPv6 routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::LinkBandwidth¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L2657
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::link_bandwidth_add_next_hop_count_to_received_bgp_routes_t? add_next_hop_count_to_received_bgp_routes=null¶
Determines the weight that is internally added to the received PE-CE BGP routes The configured weight is added to all received BGP PE-CE routes for the purpose of EVPN unequal ECMP. This weight is internal and not added into any link-bandwidth extended community when readvertising the received routes to other ipv4 or ipv6 neighbors. :rel parent_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6Unicast parent_ipv6_unicast [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of IPv6 routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L2015
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of IPv6 routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received IPv6 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of IPv6 routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6Unicast parent_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of IPv6 routes allowed to be received from the peer
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::Ipv6Unicast.prefix_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv4_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L1975
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv4_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of VPN-IPv4 routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received VPN-IPv4 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of VPN-IPv4 routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_l3vpn_ipv4_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::L3vpnIpv4Unicast parent_l3vpn_ipv4_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv4 unicast routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv6_unicast::PrefixLimit¶
Parents:
nokia_srlinux::Base
Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from the peer Yang definition can be found here: srl_nokia-bgp.yang:L2108
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv6_unicast::prefix_limit_max_received_routes_t? max_received_routes=null¶
Maximum number of VPN-IPv6 routes that will be accepted from the neighbor, counting routes accepted and rejected by import policies
- attribute bool? prevent_teardown=null¶
When false the session is immediately torn down when the number of received VPN-IPv6 routes exceeds the configured limit.
- attribute nokia_srlinux::types::srl_nokia_bgp::percentage? warning_threshold_pct=null¶
When the number of VPN-IPv6 routes received from the peer (counting routes accepted and rejected by import policy) reaches this percentage of the max-received-routes limit, BGP raises a warning log event :rel parent_l3vpn_ipv6_unicast: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::L3vpnIpv6Unicast parent_l3vpn_ipv6_unicast [1]¶
Relation to parent container Peer relation: Options for configuring the maximum number of VPN-IPv6 unicast routes allowed to be received from the peer
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::as_path_options::RemovePrivateAs¶
Parents:
nokia_srlinux::Base
Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers Yang definition can be found here: srl_nokia-bgp.yang:L1578
- attribute bool? ignore_peer_as=null¶
If set to true then do not delete or replace a private AS number that is the same as the peer AS number
- attribute bool? leading_only=null¶
If set to true then only delete or replace private AS numbers that appear before the first occurrence of a non-private ASN in the sequence of most recent ASNs in the AS path
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::as_path_options::remove_private_as_mode_t? mode=null¶
The method by which private AS numbers are removed from the advertised AS_PATH attribute :rel parent_as_path_options: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::AsPathOptions parent_as_path_options [1]¶
Relation to parent container Peer relation: Container with options for removing private AS numbers (2-byte and 4-byte) from the advertised AS path towards all peers
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::AsPathOptions.remove_private_as [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::neighbor::trace_options::Flag¶
Parents:
nokia_srlinux::Base
Tracing parameters Yang definition can be found here: srl_nokia-bgp.yang:L166
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::trace_options::flag_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::bgp::neighbor::trace_options::flag_name_t name¶
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::neighbor::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::protocols::bgp::neighbor::TraceOptions.flag [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::rib_management::Table¶
Parents:
nokia_srlinux::Base
List of RIB tables maintained by BGP running in this network-instance Yang definition can be found here: srl_nokia-bgp.yang:L2714
- attribute string address_family¶
BGP address family
- attribute string? route_table_import=null¶
Apply a route policy to accept routes that should be installed in the BGP RIB table :rel parent_rib_management: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::RibManagement parent_rib_management [1]¶
Relation to parent container Peer relation: List of RIB tables maintained by BGP running in this network-instance
other end:
nokia_srlinux::network_instance::protocols::bgp::RibManagement.table [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp::trace_options::Flag¶
Parents:
nokia_srlinux::Base
Tracing parameters Yang definition can be found here: srl_nokia-bgp.yang:L166
- attribute nokia_srlinux::network_instance::protocols::bgp::trace_options::flag_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::bgp::trace_options::flag_name_t name¶
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameters
other end:
nokia_srlinux::network_instance::protocols::bgp::TraceOptions.flag [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance¶
Parents:
nokia_srlinux::Base
bgp evpn instances configured in net-instance Yang definition can be found here: srl_nokia-bgp-evpn.yang:L443
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the bgp evpn instance.
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance_ecmp_t? ecmp=null¶
The supported range of ECMP values for layer-2 aliasing (in mac-vrf instances) or layer-3 ecmp (in routed instances).
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance_encapsulation_type_t? encapsulation_type=null¶
encap type of the bgp evpn instance.
- attribute nokia_srlinux::types::srl_nokia_common::evi? evi=null¶
EVPN Instance identifier associated to the bgp-evpn instance. Used for auto-derivation of: - the bgp-instance route distinguisher in the format <ip-address>:evi (where ‘ip-address’ is the ipv4 address associated to the subinterface lo0.1. - the bgp-instance route target in the format <asn>:<evi>, where ‘asn’ is the autonomous-system configured in the network-instance default (under /protocols/bgp/autonomous-system). In addition, the evi value is used for the EVPN Multi-Homing Designated Forwarder (DF) Election.
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance_id_t id¶
- attribute string? vxlan_interface=null¶
Identifier of vxlan-interface used in this bgp-instance. :rel internal_tags: Configuration and state of internal tags :rel mpls: :rel parent_bgp_evpn: Relation to parent container :rel routes: :rel vpws_attachment_circuits:
- relation nokia_srlinux::network_instance::protocols::BgpEvpn parent_bgp_evpn [1]¶
Relation to parent container Peer relation: bgp evpn instances configured in net-instance
other end:
nokia_srlinux::network_instance::protocols::BgpEvpn.bgp_instance [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls mpls [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls.parent_bgp_instance [1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes routes [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes.parent_bgp_instance [1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::VpwsAttachmentCircuits vpws_attachment_circuits [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-bgp-evpn.yang:L407
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_bgp_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L537
- attribute bool? control_word=null¶
Configures the use of control-word for EVPN MPLS packets When set to true, the router pushes the control-word below the bottom of the stack label. This prevents the Provider routers from mistakenly decode the payload of EVPN packets as an IP header and misorder packets of the same flow. :rel bridge_table: :rel next_hop_resolution: Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels :rel parent_bgp_instance: Relation to parent container :rel route_table:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance.mpls [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::RouteTable route_table [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::RouteTable.parent_mpls [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L140
- Rel bridge_table:
- Rel parent_bgp_instance:
Relation to parent container
- Rel route_table:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance.routes [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::RouteTable route_table [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::VpwsAttachmentCircuits¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L307
- Rel local:
The local parameters of the VPWS
- Rel parent_bgp_instance:
Relation to parent container
- Rel remote:
The remote parameters of the VPWS
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::BgpInstance.vpws_attachment_circuits [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::Local local [0:1]¶
Relation to parent container Peer relation: The local parameters of the VPWS
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::Remote remote [0:1]¶
Relation to parent container Peer relation: The remote parameters of the VPWS
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::BridgeTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L250
- attribute string? split_horizon_group=null¶
The split-horizon-group associated to the evpn-mpls instance :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls parent_mpls [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls.bridge_table [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels Yang definition can be found here: srl_nokia-bgp-evpn.yang:L233
- attribute string[]? allowed_tunnel_types=null¶
list of allowed tunnel types :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls.next_hop_resolution [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::RouteTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L287
- Rel parent_mpls:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls parent_mpls [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Mpls.route_table [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::BridgeTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L141
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table_next_hop_t? next_hop=null¶
The ip-address that will be used as the bgp next-hop for all routes advertised in this evpn instance.
- attribute nokia_srlinux::types::srl_nokia_bgp_evpn::ethernet_tag_id? vlan_aware_bundle_eth_tag=null¶
Configures the Ethernet Tag ID to be encoded in the EVPN routes for control-plane interoperability mode with VLAN-aware bundle services. When set to a non-zero value, all the EVPN routes advertised for the MAC-VRF will be advertised with this value into the ethernet-tag-id field of the routes. On reception of EVPN routes with non-zero ethernet-tag-id, BGP will import the routes based on the import route-target as usual. However, the system checks the received ethernet-tag-id field and will process only those routes whose ethernet-tag-id match the local vlan-aware-bundle-eth-tag value. :rel inclusive_mcast: :rel mac_ip: :rel parent_routes: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes parent_routes [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes.bridge_table [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::InclusiveMcast inclusive_mcast [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::MacIp mac_ip [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::RouteTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L205
- Rel ip_prefix:
- Rel mac_ip:
- Rel parent_routes:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes parent_routes [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::Routes.route_table [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::IpPrefix ip_prefix [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::MacIp mac_ip [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::InclusiveMcast¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L168
- attribute bool? advertise=null¶
If set to true an inclusive multicast route will be advertised in this evpn instance.
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::inclusive_mcast_originating_ip_t? originating_ip=null¶
The originating ip-address that the inclusive multicast route will be advertised with in this evpn instance :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::MacIp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L146
- attribute bool? advertise=null¶
If set to true then local mac’s and local mac-ip pairs will be advertised in this evpn instance
- attribute bool? advertise_arp_nd_extended_community=null¶
ARP/ND extended community
- attribute bool? advertise_arp_nd_only_with_mac_table_entry=null¶
If set to true then local mac-ip records will be advertised in this evpn instance only when we have a local mac in the mac-table :rel parent_bridge_table: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::BridgeTable.mac_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::IpPrefix¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L223
- Rel evpn_link_bandwidth:
- Rel parent_route_table:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::RouteTable parent_route_table [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::EvpnLinkBandwidth evpn_link_bandwidth [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::MacIp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L210
- attribute bool? advertise_gateway_mac=null¶
If set to true in an ip-vrf where bgp-evpn is enabled, a MAC/IP route containing the gateway-MAC is advertised. This gateway-MAC matches the MAC advertised along with the EVPN IFL routes type 5 for the ip-vrf network-instance. This advertisement is needed so that the EVPN IFL (Interface-Less) model in the ip-vrf can interoperate with a remote system working in EVPN IFF (Interface-ful) Unnumbered mode. :rel parent_route_table: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::RouteTable parent_route_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::RouteTable.mac_ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::EvpnLinkBandwidth¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L72
- Rel advertise:
- Rel parent_ip_prefix:
Relation to parent container
- Rel weighted_ecmp:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::IpPrefix parent_ip_prefix [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::Advertise advertise [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::WeightedEcmp weighted_ecmp [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::Advertise¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L74
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::advertise_maximum_dynamic_weight_t? maximum_dynamic_weight=null¶
Determines the maximum weight to be advertised in the evpn-link-bandwidth extended community If weight ‘dynamic’ is configured, the actual advertised weight is the minimum of the number of BGP PE-CE paths for the prefix and the configured maximum weight.
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::advertise_weight_t? weight=null¶
Determines the weight to be advertised in the evpn-link-bandwidth extended community If set to dynamic, the weight is dynamically set based on the number of BGP PE-CE paths for the IP Prefix that is advertised in an EVPN IP Prefix route. Alternatively, the weight can be set to a fixed integer value in the range 1..128. The dynamic weight only considers BGP PE-CE paths. :rel parent_evpn_link_bandwidth: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::EvpnLinkBandwidth parent_evpn_link_bandwidth [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::WeightedEcmp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-evpn.yang:L108
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Setting enable triggers weighted ECMP programming for all elegible multipath EVPN IFL routes When set to enable, the router processes the evpn-link-bandwidth extended community when installing an ECMP set for an EVPN IP-Prefix route in the ip-vrf route table. Flows to an IP Prefix received with a weight and a zero-ESI are sprayed based on the weight. If the EVPN IP Prefix route received with the weight has a non-zero ESI, the weight is divided into the number of PEs attached to the Ethernet Segment (and rounded up if the result is not an integer). The command also enables the weighted ECMP functionality for BGP CEs that are configured with the parameter evpn-link-bandwidth add-weight-to-received-bgp-routes <weight>.
- attribute nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::weighted_ecmp_max_ecmp_hash_buckets_per_next_hop_group_t? max_ecmp_hash_buckets_per_next_hop_group=null¶
Specifies the maximum number of ECMP hash buckets per next-hop-group Weighted ECMP weights are normalized based on this number of hash buckets. :rel parent_evpn_link_bandwidth: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::EvpnLinkBandwidth parent_evpn_link_bandwidth [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::Local¶
Parents:
nokia_srlinux::Base
The local parameters of the VPWS Yang definition can be found here: srl_nokia-bgp-evpn.yang:L316
- Rel local_attachment_circuit:
A local attachment circuit in the VPWS
Each local attachment circuit is identified in EVPN with an Ethernet Tag that is advertised in the Auto Discovery per EVI route. Configurable on network instances of type vpws. :rel parent_vpws_attachment_circuits: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::VpwsAttachmentCircuits parent_vpws_attachment_circuits [1]¶
Relation to parent container Peer relation: The local parameters of the VPWS
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::local::LocalAttachmentCircuit local_attachment_circuit [0:1]¶
Relation to parent container Peer relation: A local attachment circuit in the VPWS
Each local attachment circuit is identified in EVPN with an Ethernet Tag that is advertised in the Auto Discovery per EVI route. Configurable on network instances of type vpws.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::Remote¶
Parents:
nokia_srlinux::Base
The remote parameters of the VPWS Yang definition can be found here: srl_nokia-bgp-evpn.yang:L363
- Rel parent_vpws_attachment_circuits:
Relation to parent container
- Rel remote_attachment_circuit:
A remote attachment circuit in the VPWS
Each remote attachment circuit is identified in EVPN with an Ethernet Tag that is received in the Auto Discovery per EVI route from the remote PE. Configurable on network instances of type vpws.
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::VpwsAttachmentCircuits parent_vpws_attachment_circuits [1]¶
Relation to parent container Peer relation: The remote parameters of the VPWS
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::remote::RemoteAttachmentCircuit remote_attachment_circuit [0:1]¶
Relation to parent container Peer relation: A remote attachment circuit in the VPWS
Each remote attachment circuit is identified in EVPN with an Ethernet Tag that is received in the Auto Discovery per EVI route from the remote PE. Configurable on network instances of type vpws.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::local::LocalAttachmentCircuit¶
Parents:
nokia_srlinux::Base
A local attachment circuit in the VPWS
Each local attachment circuit is identified in EVPN with an Ethernet Tag that is advertised in the Auto Discovery per EVI route. Configurable on network instances of type vpws. Yang definition can be found here: srl_nokia-bgp-evpn.yang:L319
- attribute string? connection_point=null¶
The connection-point associated to the local attachement circuit
- attribute nokia_srlinux::types::srl_nokia_bgp_evpn::ethernet_tag_id? ethernet_tag=null¶
The Ethernet Tag ID advertised in the Auto Discovery per EVI route The Ethernet Tag ID identifies the local attachment circuit in the EVPN control plane.
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The list of local attachment circuits in the network instance :rel parent_local: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::Local parent_local [1]¶
Relation to parent container Peer relation: A local attachment circuit in the VPWS
Each local attachment circuit is identified in EVPN with an Ethernet Tag that is advertised in the Auto Discovery per EVI route. Configurable on network instances of type vpws.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::remote::RemoteAttachmentCircuit¶
Parents:
nokia_srlinux::Base
A remote attachment circuit in the VPWS
Each remote attachment circuit is identified in EVPN with an Ethernet Tag that is received in the Auto Discovery per EVI route from the remote PE. Configurable on network instances of type vpws. Yang definition can be found here: srl_nokia-bgp-evpn.yang:L366
- attribute string? connection_point=null¶
The connection-point associated to the local attachement circuit
- attribute nokia_srlinux::types::srl_nokia_bgp_evpn::ethernet_tag_id? ethernet_tag=null¶
The Ethernet Tag ID received in the Auto Discovery per EVI route The Ethernet Tag ID identifies the remote attachment circuit in the EVPN control plane.
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The list of remote attachment circuits in the network instance :rel parent_remote: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::Remote parent_remote [1]¶
Relation to parent container Peer relation: A remote attachment circuit in the VPWS
Each remote attachment circuit is identified in EVPN with an Ethernet Tag that is received in the Auto Discovery per EVI route from the remote PE. Configurable on network instances of type vpws.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance¶
Parents:
nokia_srlinux::Base
bgp ipvpn instances configured in net-instance Yang definition can be found here: srl_nokia-bgp-ipvpn.yang:L88
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configurable state of the bgp-ipvpn instance.
- attribute nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance_ecmp_t? ecmp=null¶
The supported range of ECMP values for layer-3 ecmp.
- attribute nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance_encapsulation_type_t? encapsulation_type=null¶
Encap type of the bgp ipvpn instance.
- attribute nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance_id_t id¶
- Rel internal_tags:
Configuration and state of internal tags :rel mpls: :rel parent_bgp_ipvpn: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::BgpIpvpn parent_bgp_ipvpn [1]¶
Relation to parent container Peer relation: bgp ipvpn instances configured in net-instance
other end:
nokia_srlinux::network_instance::protocols::BgpIpvpn.bgp_instance [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::Mpls mpls [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::Mpls.parent_bgp_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-bgp-ipvpn.yang:L68
- attribute nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::internal_tags_tag_set_t[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_bgp_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::Mpls¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp-ipvpn.yang:L144
- Rel next_hop_resolution:
Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels
- Rel parent_bgp_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::bgp_ipvpn::BgpInstance.mpls [0:1]
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::mpls::NextHopResolution next_hop_resolution [0:1]¶
Relation to parent container Peer relation: Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::mpls::NextHopResolution¶
Parents:
nokia_srlinux::Base
Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels Yang definition can be found here: srl_nokia-bgp-ipvpn.yang:L49
- attribute string[]? allowed_tunnel_types=null¶
list of allowed tunnel types :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Options related to the resolution of IPv4 or IPv6 BGP next-hops to Tunnels
other end:
nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::Mpls.next_hop_resolution [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance¶
Parents:
nokia_srlinux::Base
List of bgp-vpn instances configured in the network-instance. Only one instance allowed in the current release. Yang definition can be found here: srl_nokia-bgp-vpn.yang:L54
- attribute string? export_policy=null¶
Apply an export policy to advertised BGP routes
- attribute nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance_id_t id¶
The index of the bgp-vpn instance
- attribute string? import_policy=null¶
Apply an import policy to received BGP routes :rel parent_bgp_vpn: Relation to parent container :rel route_distinguisher: Route Distinguisher (RD) of the bgp-vpn instance. :rel route_target: Route Target (RT) of the bgp-vpn instance.
- relation nokia_srlinux::network_instance::protocols::BgpVpn parent_bgp_vpn [1]¶
Relation to parent container Peer relation: List of bgp-vpn instances configured in the network-instance. Only one instance allowed in the current release.
other end:
nokia_srlinux::network_instance::protocols::BgpVpn.bgp_instance [0:2]
- relation nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::RouteDistinguisher route_distinguisher [0:1]¶
Relation to parent container Peer relation: Route Distinguisher (RD) of the bgp-vpn instance.
- relation nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::RouteTarget route_target [0:1]¶
Relation to parent container Peer relation: Route Target (RT) of the bgp-vpn instance.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::RouteDistinguisher¶
Parents:
nokia_srlinux::Base
Route Distinguisher (RD) of the bgp-vpn instance. Yang definition can be found here: srl_nokia-bgp-vpn.yang:L66
- attribute nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::route_distinguisher_rd_t? rd=null¶
Route Distinguisher (RD) in the bgp-vpn instance. When used for evpn and if not configured, the RD is auto-derived as <ip-address>:<evi> where ‘ip-address’ is the ipv4 address associated to the subinterface lo0.1. :rel parent_bgp_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Route Distinguisher (RD) of the bgp-vpn instance.
other end:
nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance.route_distinguisher [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::RouteTarget¶
Parents:
nokia_srlinux::Base
Route Target (RT) of the bgp-vpn instance. Yang definition can be found here: srl_nokia-bgp-vpn.yang:L95
- attribute nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::route_target_export_rt_t? export_rt=null¶
Export Route Target (RT) in the bgp-vpn instance. When used for evpn and if not configured, the RT is auto-derived with the format <asn>:<evi> where ‘asn’ is the autonomous-system configured in the network-instance default.
- attribute nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::route_target_import_rt_t? import_rt=null¶
Import Route Target (RT) in the bgp-vpn instance. When used for evpn and if not configured, the RT is auto-derived with the format <asn>:<evi> where ‘asn’ is the autonomous-system configured in the network-instance default. :rel parent_bgp_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Route Target (RT) of the bgp-vpn instance.
other end:
nokia_srlinux::network_instance::protocols::bgp_vpn::BgpInstance.route_target [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::directly_connected::TeDatabaseInstall¶
Parents:
nokia_srlinux::Base
When present, local topology and TE information is installed into the TE database Yang definition can be found here: srl_nokia-traffic-engineering.yang:L98
- Rel bgp_ls:
When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
- Rel parent_directly_connected:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::DirectlyConnected parent_directly_connected [1]¶
Relation to parent container Peer relation: When present, local topology and TE information is installed into the TE database
other end:
nokia_srlinux::network_instance::protocols::DirectlyConnected.te_database_install [0:1]
- relation nokia_srlinux::network_instance::protocols::directly_connected::te_database_install::BgpLs bgp_ls [0:1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::directly_connected::te_database_install::BgpLs¶
Parents:
nokia_srlinux::Base
When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes Yang definition can be found here: srl_nokia-traffic-engineering.yang:L78
- attribute yang::types::uint32? bgp_ls_identifier=null¶
BGP-LS identifier value that is sent in the BGP-LS NLRI
- attribute nokia_srlinux::network_instance::protocols::directly_connected::te_database_install::bgp_ls_igp_identifier_t? igp_identifier=null¶
Unique identifier of the IGP instance that is sent in the BGP-LS NLRI :rel parent_te_database_install: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::directly_connected::TeDatabaseInstall parent_te_database_install [1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
other end:
nokia_srlinux::network_instance::protocols::directly_connected::TeDatabaseInstall.bgp_ls [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::Interface¶
Parents:
nokia_srlinux::Base
List of IGMP interfaces Yang definition can be found here: srl_nokia-igmp.yang:L891
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the IGMP protocol for this interface Used to administratively enable or disable the IGMP protocol on a routed subinterface
- attribute string? import_policy=null¶
Apply an import policy. The lenght of the policy name should not exceed 32 charachters
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index>
- attribute nokia_srlinux::network_instance::protocols::igmp::interface_maximum_number_group_sources_t? maximum_number_group_sources=null¶
MAX number of IGMP group/source combinations for this interface, 0 means no limit
- attribute nokia_srlinux::network_instance::protocols::igmp::interface_maximum_number_groups_t? maximum_number_groups=null¶
MAX number of IGMP Groups for this interface, 0 means no limit
- attribute nokia_srlinux::network_instance::protocols::igmp::interface_maximum_number_sources_t? maximum_number_sources=null¶
MAX number of IGMP sources per group for this interface, 0 means no limit
- attribute nokia_srlinux::network_instance::protocols::igmp::interface_query_interval_t? query_interval=null¶
Interval at which the router sends the IGMP membership queries
- attribute nokia_srlinux::network_instance::protocols::igmp::interface_query_last_member_interval_t? query_last_member_interval=null¶
Interval at which Group-Specific-Query packets are transmitted
- attribute nokia_srlinux::network_instance::protocols::igmp::interface_query_response_interval_t? query_response_interval=null¶
Time to wait to receive a response to the IGMP membership query from the host
- attribute bool? router_alert_check=null¶
Enable or disable router alert checking for IGMP messages received on this interface
- attribute bool? subnet_check=null¶
This command enables subnet checking for IGMP messages received on this interface All IGMP packets with a source address that is not in the local subnet are dropped.
- attribute nokia_srlinux::types::srl_nokia_igmp::igmp_version? version=null¶
IGMP Version :rel parent_igmp: Relation to parent container :rel ssm: Container to configure Source specific multicast (SSM) options. :rel static_membership_groups: Container to configure static <S,G>s for this interface
- relation nokia_srlinux::network_instance::protocols::Igmp parent_igmp [1]¶
Relation to parent container Peer relation: List of IGMP interfaces
other end:
nokia_srlinux::network_instance::protocols::Igmp.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::igmp::interface::Ssm ssm [0:1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options.
other end:
nokia_srlinux::network_instance::protocols::igmp::interface::Ssm.parent_interface [1]
- relation nokia_srlinux::network_instance::protocols::igmp::interface::StaticMembershipGroups static_membership_groups [0:1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::Ssm¶
Parents:
nokia_srlinux::Base
Container to configure Source specific multicast (SSM) options. Yang definition can be found here: srl_nokia-igmp.yang:L125
- Rel mappings:
A list of source specific multicast (SSM) mappings
- Rel parent_igmp:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Igmp parent_igmp [1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options.
other end:
nokia_srlinux::network_instance::protocols::Igmp.ssm [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::ssm::Mappings mappings [0:1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::igmp::ssm::Mappings.parent_ssm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-igmp.yang:L244
- Rel parent_igmp:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::Igmp parent_igmp [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::Igmp.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace.parent_trace_options [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::Ssm¶
Parents:
nokia_srlinux::Base
Container to configure Source specific multicast (SSM) options. Yang definition can be found here: srl_nokia-igmp.yang:L125
- Rel mappings:
A list of source specific multicast (SSM) mappings
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options.
other end:
nokia_srlinux::network_instance::protocols::igmp::Interface.ssm [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::Mappings mappings [0:1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::igmp::interface::ssm::Mappings.parent_ssm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::StaticMembershipGroups¶
Parents:
nokia_srlinux::Base
Container to configure static <S,G>s for this interface Yang definition can be found here: srl_nokia-igmp.yang:L402
- Rel group_range:
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface
other end:
nokia_srlinux::network_instance::protocols::igmp::Interface.static_membership_groups [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::GroupRange group_range [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::ssm::Mappings¶
Parents:
nokia_srlinux::Base
A list of source specific multicast (SSM) mappings Yang definition can be found here: srl_nokia-igmp.yang:L128
- Rel group_range:
A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address. :rel parent_ssm: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::interface::Ssm parent_ssm [1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::igmp::interface::Ssm.mappings [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::GroupRange group_range [0:*]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::GroupRange¶
Parents:
nokia_srlinux::Base
A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address. Yang definition can be found here: srl_nokia-igmp.yang:L131
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address start¶
Start of the group range.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address x_end¶
End of the group range. :rel parent_mappings: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::Mappings parent_mappings [1]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address.
other end:
nokia_srlinux::network_instance::protocols::igmp::interface::ssm::Mappings.group_range [0:*]
- relation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::group_range::Source source [1:*]¶
Multicast source address list Peer relation: Relation to parent container
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::group_range::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-igmp.yang:L141
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address source¶
Multicast source address :rel parent_group_range: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::GroupRange parent_group_range [1]¶
Multicast source address list Peer relation: Relation to parent container
other end:
nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::GroupRange.source [1:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::GroupRange¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-igmp.yang:L405
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address start¶
Start of the group range.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address x_end¶
End of the group range. :rel parent_static_membership_groups: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::igmp::interface::StaticMembershipGroups parent_static_membership_groups [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::group_range::Source source [0:*]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::group_range::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-igmp.yang:L411
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address source¶
Multicast source address :rel parent_group_range: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::GroupRange parent_group_range [1]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::ssm::Mappings¶
Parents:
nokia_srlinux::Base
A list of source specific multicast (SSM) mappings Yang definition can be found here: srl_nokia-igmp.yang:L128
- Rel group_range:
A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address. :rel parent_ssm: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::Ssm parent_ssm [1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::igmp::Ssm.mappings [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::GroupRange group_range [0:*]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address.
other end:
nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::GroupRange.parent_mappings [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::GroupRange¶
Parents:
nokia_srlinux::Base
A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address. Yang definition can be found here: srl_nokia-igmp.yang:L131
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address start¶
Start of the group range.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address x_end¶
End of the group range. :rel parent_mappings: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::igmp::ssm::Mappings parent_mappings [1]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows IGMP v2 hosts to be able to join in SSM environments by translating IGMP v2 reports into IGMP v3 reports. The request in an IGMP v2 join is sent toward the source address found by matching the multicast address.
other end:
nokia_srlinux::network_instance::protocols::igmp::ssm::Mappings.group_range [0:*]
- relation nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::group_range::Source source [1:*]¶
Multicast source address list Peer relation: Relation to parent container
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::group_range::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-igmp.yang:L141
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address source¶
Multicast source address :rel parent_group_range: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::GroupRange parent_group_range [1]¶
Multicast source address list Peer relation: Relation to parent container
other end:
nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::GroupRange.source [1:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-igmp.yang:L247
- Rel interface:
Enable tracing interface events
- Rel packet:
Trace IGMP Packet types
Only one type can be enabled at a time :rel parent_trace_options: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::igmp::TraceOptions.trace [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Interface interface [0:1]¶
Relation to parent container Peer relation: Enable tracing interface events
other end:
nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Interface.parent_trace [1]
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Trace IGMP Packet types Only one type can be enabled at a time
other end:
nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Packet.parent_trace [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Interface¶
Parents:
nokia_srlinux::Base
Enable tracing interface events Yang definition can be found here: srl_nokia-igmp.yang:L250
- attribute bool? all=null¶
Trace for all interfaces
- attribute string? name=null¶
Trace for interface with this name :rel parent_trace: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Enable tracing interface events
other end:
nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace.interface [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Trace IGMP Packet types Only one type can be enabled at a time Yang definition can be found here: srl_nokia-igmp.yang:L161
- attribute nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::packet_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::packet_type_t? type=null¶
- Rel interface:
Enable interface filter for packets :rel parent_trace: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace IGMP Packet types Only one type can be enabled at a time
other end:
nokia_srlinux::network_instance::protocols::igmp::trace_options::Trace.packet [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::packet::Interface interface [0:1]¶
Relation to parent container Peer relation: Enable interface filter for packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::packet::Interface¶
Parents:
nokia_srlinux::Base
Enable interface filter for packets Yang definition can be found here: srl_nokia-igmp.yang:L166
- attribute bool? all=null¶
Trace for all interfaces
- attribute string? name=null¶
Trace for interface with this name :rel parent_packet: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: Enable interface filter for packets
other end:
nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::Packet.interface [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::Interface¶
Parents:
nokia_srlinux::Base
List of IGMP interfaces Yang definition can be found here: srl_nokia-igmp-snooping.yang:L1065
- attribute bool? fast_leave=null¶
Allow IGMP fast leave processing When enabled, the multicast state is removed immediately upon receiving an IGMP leave message.
- attribute string? import_policy=null¶
Apply an import policy. The lenght of the policy name should not exceed 32 charachters.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index>
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_maximum_number_group_sources_t? maximum_number_group_sources=null¶
Maximum number of IGMP group/source combinations for this interface
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_maximum_number_groups_t? maximum_number_groups=null¶
Maximum number of IGMP Groups for this interface
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_maximum_number_sources_t? maximum_number_sources=null¶
Maximum number of IGMP sources per group for this interface
- attribute bool? mrouter_port=null¶
Operate port as a multicast router port
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_query_interval_t? query_interval=null¶
Interval at which the router sends the IGMP membership queries
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_query_last_member_interval_t? query_last_member_interval=null¶
Interval at which Group-Specific-Query packets are transmitted
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_query_response_interval_t? query_response_interval=null¶
Time to wait to receive a response to the IGMP membership query from the host
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::interface_robust_count_t? robust_count=null¶
Tune IGMP robustness to allow for expected packet loss The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.
- attribute bool? router_alert_check=null¶
Enable or disable router alert checking for IGMP messages received on this interface
- attribute bool? send_queries=null¶
Generate IGMP general queries
- attribute nokia_srlinux::types::srl_nokia_igmp_snooping::igmp_version? version=null¶
IGMP Version :rel parent_igmp_snooping: Relation to parent container :rel static_membership_groups: Container to configure static <S,G>s for this interface.
- relation nokia_srlinux::network_instance::protocols::IgmpSnooping parent_igmp_snooping [1]¶
Relation to parent container Peer relation: List of IGMP interfaces
other end:
nokia_srlinux::network_instance::protocols::IgmpSnooping.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::StaticMembershipGroups static_membership_groups [0:1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-igmp-snooping.yang:L93
- Rel parent_igmp_snooping:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::IgmpSnooping parent_igmp_snooping [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::IgmpSnooping.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::interface::StaticMembershipGroups¶
Parents:
nokia_srlinux::Base
Container to configure static <S,G>s for this interface. Yang definition can be found here: srl_nokia-igmp-snooping.yang:L526
- Rel group:
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface.
other end:
nokia_srlinux::network_instance::protocols::igmp_snooping::Interface.static_membership_groups [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::Group group [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::Group¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-igmp-snooping.yang:L529
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address group¶
group address.
- attribute bool? starg=null¶
any source address (*,G) :rel parent_static_membership_groups: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::StaticMembershipGroups parent_static_membership_groups [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::group::Source source [0:*]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::group::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-igmp-snooping.yang:L535
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address source¶
Multicast source address. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::Group parent_group [1]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-igmp-snooping.yang:L96
- Rel packet:
Trace IGMP Packet types
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::igmp_snooping::TraceOptions.trace [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Trace IGMP Packet types
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Trace IGMP Packet types Yang definition can be found here: srl_nokia-igmp-snooping.yang:L99
- attribute nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet_modifier_t? modifier=null¶
- Rel interface:
List of interfaces to trace :rel parent_trace: Relation to parent container :rel source_mac: List of source mac addresses to trace
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace IGMP Packet types
other end:
nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::Trace.packet [0:1]
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet::Interface interface [0:8]¶
Relation to parent container Peer relation: List of interfaces to trace
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet::SourceMac source_mac [0:8]¶
Relation to parent container Peer relation: List of source mac addresses to trace
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet::Interface¶
Parents:
nokia_srlinux::Base
List of interfaces to trace Yang definition can be found here: srl_nokia-igmp-snooping.yang:L103
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index> :rel parent_packet: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: List of interfaces to trace
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet::SourceMac¶
Parents:
nokia_srlinux::Base
List of source mac addresses to trace Yang definition can be found here: srl_nokia-igmp-snooping.yang:L114
- attribute nokia_srlinux::types::srl_nokia_common::mac_address source_mac¶
- Rel parent_packet:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: List of source mac addresses to trace
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::Instance¶
Parents:
nokia_srlinux::Base
List of IS-IS protocol instances associated with this network-instance. Only a single instance is supported for now Yang definition can be found here: srl_nokia-isis.yang:L3280
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to administratively enable or disable the IS-IS instance
- attribute bool? enable_csnp_on_p2p_links=null¶
Enable/disable the transmission of periodic CSNP PDUs on point-to-point interfaces When this is set to false, CSNP PDUs will only be sent on a P2P interface when the adjacency is initialized. This setting has no effect on broadcast interfaces.
- attribute string? export_policy=null¶
Apply an export policy to redistribute non-ISIS routes into ISIS
- attribute nokia_srlinux::types::srl_nokia_isis::isis_hello_padding_type? hello_padding=null¶
Specifies the use of IS-IS Hello PDU padding all interfaces This can be overridden by interface configuration.
- attribute bool? iid_tlv=null¶
ISIS Instance Identifier TLV. When set to true, IID-TLV identifies the unique instance as well as the topology/topologies to which the PDU applies.
- attribute nokia_srlinux::network_instance::protocols::isis::instance_instance_id_t? instance_id=null¶
ISIS instance number
- attribute nokia_srlinux::types::srl_nokia_isis::isis_level? level_capability=null¶
The level-capability of the intermediate system (router)
- attribute nokia_srlinux::types::srl_nokia_isis::isis_ecmp? max_ecmp_paths=null¶
The maximum number of ECMP next-hops to program into the FIB for every IP prefix
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The name of the IS-IS instance
- attribute nokia_srlinux::types::srl_nokia_isis::isis_net_id[]? net=null¶
ISIS network entity title (NET)
- attribute bool? poi_tlv=null¶
When set to true, a TLV is added to purge to record the system ID of the IS generating the purge. :rel attached_bit: This container provides option for handling the ATTached bit in L1 LSPs :rel authentication: Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level. The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level. :rel auto_cost: :rel graceful_restart: Container for options related to IS-IS graceful restart :rel inter_level_propagation_policies: Container with options to control the propagation of prefixes between levels :rel interface: List of IS-IS interfaces :rel ipv4_unicast: Enables/disables IPv4 routing in this ISIS instance. :rel ipv6_unicast: Enables/disables IPv6 routing in this ISIS instance. :rel ldp_synchronization: Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled. :rel level: List of IS-IS levels supported by this IS (router) :rel loopfree_alternate: Loopfree-alternate related context for the instance. :rel overload: Specifies isis routing instance behavior regarding overload :rel parent_isis: Relation to parent container :rel segment_routing: :rel te_database_install: When present, topology and TE information related to this protocol instance is installed into the TE database :rel timers: Container for IS-IS timers applicable at the instance level :rel trace_options: Instance level debug trace options for IS-IS :rel traffic_engineering: Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces :rel transport: :rel weighted_ecmp:
- relation nokia_srlinux::network_instance::protocols::Isis parent_isis [1]¶
Relation to parent container Peer relation: List of IS-IS protocol instances associated with this network-instance. Only a single instance is supported for now
other end:
nokia_srlinux::network_instance::protocols::Isis.instance [0:*]
- relation nokia_srlinux::network_instance::protocols::isis::instance::AttachedBit attached_bit [0:1]¶
Relation to parent container Peer relation: This container provides option for handling the ATTached bit in L1 LSPs
other end:
nokia_srlinux::network_instance::protocols::isis::instance::AttachedBit.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level.
The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Authentication.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::AutoCost auto_cost [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::AutoCost.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::GracefulRestart graceful_restart [0:1]¶
Relation to parent container Peer relation: Container for options related to IS-IS graceful restart
other end:
nokia_srlinux::network_instance::protocols::isis::instance::GracefulRestart.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::InterLevelPropagationPolicies inter_level_propagation_policies [0:1]¶
Relation to parent container Peer relation: Container with options to control the propagation of prefixes between levels
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface interface [0:*]¶
Relation to parent container Peer relation: List of IS-IS interfaces
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Ipv4Unicast ipv4_unicast [0:1]¶
Relation to parent container Peer relation: Enables/disables IPv4 routing in this ISIS instance.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Ipv4Unicast.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Ipv6Unicast ipv6_unicast [0:1]¶
Relation to parent container Peer relation: Enables/disables IPv6 routing in this ISIS instance.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Ipv6Unicast.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::LdpSynchronization ldp_synchronization [0:1]¶
Relation to parent container Peer relation: Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::LdpSynchronization.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Level level [0:2]¶
Relation to parent container Peer relation: List of IS-IS levels supported by this IS (router)
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Level.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate loopfree_alternate [0:1]¶
Relation to parent container Peer relation: Loopfree-alternate related context for the instance.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Overload overload [0:1]¶
Relation to parent container Peer relation: Specifies isis routing instance behavior regarding overload
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Overload.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::SegmentRouting segment_routing [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::SegmentRouting.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::TeDatabaseInstall te_database_install [0:1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database
other end:
nokia_srlinux::network_instance::protocols::isis::instance::TeDatabaseInstall.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Timers timers [0:1]¶
Relation to parent container Peer relation: Container for IS-IS timers applicable at the instance level
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Timers.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Instance level debug trace options for IS-IS
other end:
nokia_srlinux::network_instance::protocols::isis::instance::TraceOptions.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::TrafficEngineering traffic_engineering [0:1]¶
Relation to parent container Peer relation: Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces
other end:
nokia_srlinux::network_instance::protocols::isis::instance::TrafficEngineering.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::Transport transport [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Transport.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::WeightedEcmp weighted_ecmp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::WeightedEcmp.parent_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::NonStopForwarding¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L3255
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to administratively enable or disable the IS-IS non-stop forwarding functionality. :rel parent_isis: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Isis parent_isis [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Isis.non_stop_forwarding [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::AttachedBit¶
Parents:
nokia_srlinux::Base
This container provides option for handling the ATTached bit in L1 LSPs Yang definition can be found here: srl_nokia-isis.yang:L1266
- attribute bool? ignore=null¶
When set to true, if the attached bit is set on an incoming Level 1 LSP, the local system ignores it. In this case the local system does not set a default route to the L1L2 router advertising the PDU with the attached bit set.
- attribute bool? suppress=null¶
When set to true, if the local IS acts as a L1L2 router, then the attached bit is not advertised in locally generated L1 LSPs. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: This container provides option for handling the ATTached bit in L1 LSPs
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.attached_bit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Authentication¶
Parents:
nokia_srlinux::Base
Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level.
The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level. Yang definition can be found here: srl_nokia-isis.yang:L544
- attribute string? keychain=null¶
Specifies a keychain to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy. :rel csnp_authentication: Container with options to control the authentication of CSNP PDUs :rel hello_authentication: Container with options to control the authentication of Hello PDUs :rel key: Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy :rel lsp_authentication: Container with options to control the authentication of Link State PDUs :rel parent_instance: Relation to parent container :rel psnp_authentication: Container with options to control the authentication of PSNP PDUs
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level.
The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level.
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.authentication [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::authentication::CsnpAuthentication csnp_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of CSNP PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::authentication::HelloAuthentication hello_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::authentication::Key key [0:1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy
- relation nokia_srlinux::network_instance::protocols::isis::instance::authentication::LspAuthentication lsp_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Link State PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::authentication::PsnpAuthentication psnp_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of PSNP PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::AutoCost¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1547
- attribute nokia_srlinux::network_instance::protocols::isis::instance::auto_cost_reference_bandwidth_t? reference_bandwidth=null¶
Configures the reference bandwidth that provides the basis for interface metrics based on link bandwidth. If the reference bandwidth is defined, then the cost is calculated using the following formula: cost = reference-bandwidth / bandwidth When a large reference-bandwidth value is configured, a metric calculation may result in a value higher than the supported protocol cost value. If this occurs, IS-IS automatically reverts to the maximum configurable cost metric. If the reference bandwidth is not configured then all interfaces have a default metric of 10. Note: To use metrics in excess of 63, wide metrics must be deployed :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.auto_cost [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::GracefulRestart¶
Parents:
nokia_srlinux::Base
Container for options related to IS-IS graceful restart Yang definition can be found here: srl_nokia-isis.yang:L1523
- attribute nokia_srlinux::network_instance::protocols::isis::instance::graceful_restart_acceptable_duration_t? acceptable_duration=null¶
Initial value of the Remaining Time that is advertised in the Restart TLV with Restart Acknowledgement flag set when this router starts to help another router that has just (re)entered Restart mode.
- attribute bool? helper_mode=null¶
Enable or disable the IS-IS graceful restart helper function When this leaf is set, the local system supports retaining forwarding information during a neighbor router’s restart. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container for options related to IS-IS graceful restart
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.graceful_restart [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::InterLevelPropagationPolicies¶
Parents:
nokia_srlinux::Base
Container with options to control the propagation of prefixes between levels Yang definition can be found here: srl_nokia-isis.yang:L1702
- Rel level1_to_level2:
Container with options to control the propagation of prefixes from level 1 to level 2.
By default all L1 prefixes are propagated without summarizarion into L2. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container with options to control the propagation of prefixes between levels
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.inter_level_propagation_policies [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::Level1ToLevel2 level1_to_level2 [0:1]¶
Relation to parent container Peer relation: Container with options to control the propagation of prefixes from level 1 to level 2.
By default all L1 prefixes are propagated without summarizarion into L2.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Interface¶
Parents:
nokia_srlinux::Base
List of IS-IS interfaces Yang definition can be found here: srl_nokia-isis.yang:L3292
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to administratively enable or disable the IS-IS protocol on a routed subinterface
- attribute nokia_srlinux::types::srl_nokia_isis::isis_circuit_type? circuit_type=null¶
Specifies the circuit type as either point-to-point or broadcast
- attribute nokia_srlinux::types::srl_nokia_isis::isis_hello_padding_type? hello_padding=null¶
Specifies the use of IS-IS Hello PDU padding on the interface
- attribute nokia_srlinux::types::srl_nokia_network_instance::network_instance_subintf_name interface_name¶
Name of the IS-IS interface
- attribute bool? loopfree_alternate_exclude=null¶
Enable/disable Loopfree Alternative at interface level.
- attribute bool? passive=null¶
When set to true the interface is configured as a passive interface and does not send IIH PDUs or try to form an adjacency with other routers. :rel authentication: Container for specifying authetication options that apply to the IS-IS instance. :rel delay: Enter the delay context :rel interface_ref: Reference to a subinterface :rel ipv4_unicast: :rel ipv6_unicast: :rel ldp_synchronization: Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface. :rel level: List of IS-IS levels supported by this interface :rel parent_instance: Relation to parent container :rel segment_routing: Container with interface-specific segment routing options :rel timers: :rel trace_options: Interface level debug trace options for IS-IS :rel weighted_ecmp:
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: List of IS-IS interfaces
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the IS-IS instance.
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Delay delay [0:1]¶
Relation to parent container Peer relation: Enter the delay context
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::Delay.parent_interface [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation: Reference to a subinterface
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Ipv4Unicast ipv4_unicast [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Ipv6Unicast ipv6_unicast [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::LdpSynchronization ldp_synchronization [0:1]¶
Relation to parent container Peer relation: Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface.
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Level level [0:2]¶
Relation to parent container Peer relation: List of IS-IS levels supported by this interface
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::Level.parent_interface [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::SegmentRouting segment_routing [0:1]¶
Relation to parent container Peer relation: Container with interface-specific segment routing options
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Timers timers [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::Timers.parent_interface [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Interface level debug trace options for IS-IS
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::WeightedEcmp weighted_ecmp [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Ipv4Unicast¶
Parents:
nokia_srlinux::Base
Enables/disables IPv4 routing in this ISIS instance. Yang definition can be found here: srl_nokia-isis.yang:L1493
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set to true, the IS-IS instance supports IPv4 unicast routing :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enables/disables IPv4 routing in this ISIS instance.
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.ipv4_unicast [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Ipv6Unicast¶
Parents:
nokia_srlinux::Base
Enables/disables IPv6 routing in this ISIS instance. Yang definition can be found here: srl_nokia-isis.yang:L1503
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set to true, the IS-IS instance supports IPv6 unicast routing
- attribute bool? multi_topology=null¶
When set to true, IS-IS multi-topology TLVs are used for IPv6 routing and support for native IPv6 TLVs is disabled. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enables/disables IPv6 routing in this ISIS instance.
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.ipv6_unicast [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::LdpSynchronization¶
Parents:
nokia_srlinux::Base
Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled. Yang definition can be found here: srl_nokia-ldp.yang:L1470
- attribute bool? end_of_lib=null¶
When set to true, the IGP restores the normal metric for the IGP adjacency when learning from LDP that all label-FEC mappings have been received from the LDP peer, even if there is remaining time on the hold-down-timer. When set to false, the IGP always waits for the full duration of the hold-down-timer to restore the normal metric for the IGP adjacency.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::ldp_synchronization_hold_down_timer_t? hold_down_timer=null¶
The maximum amount of time that the IGP advertises a maximum metric for an interface, measured from the time that the LDP adjacency is re-established after going down. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled.
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.ldp_synchronization [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Level¶
Parents:
nokia_srlinux::Base
List of IS-IS levels supported by this IS (router) Yang definition can be found here: srl_nokia-isis.yang:L3303
- attribute bool? bgp_ls_exclude=null¶
When set to true, topology and TE information related to this area or level should nkot be imported into the TE database in a format that supports export as BGP-LS routes
- attribute nokia_srlinux::types::srl_nokia_isis::isis_level_number level_number¶
Specifies the IS-IS protocol level to which these attributes are applied.
- attribute bool? loopfree_alternate_exclude=null¶
Enable/disable LFA at ISIS level.
- attribute nokia_srlinux::types::srl_nokia_isis::isis_metric_style? metric_style=null¶
Specifies the metric style to be wide or narrow for the level :rel authentication: Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level. The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level. :rel parent_instance: Relation to parent container :rel route_preference: Specify the route preference (admin distance) for IP routes asssociated with the level :rel trace_options: Level debug trace options for IS-IS
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: List of IS-IS levels supported by this IS (router)
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.level [0:2]
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level.
The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication.parent_level [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::RoutePreference route_preference [0:1]¶
Relation to parent container Peer relation: Specify the route preference (admin distance) for IP routes asssociated with the level
other end:
nokia_srlinux::network_instance::protocols::isis::instance::level::RoutePreference.parent_level [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Level debug trace options for IS-IS
other end:
nokia_srlinux::network_instance::protocols::isis::instance::level::TraceOptions.parent_level [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate¶
Parents:
nokia_srlinux::Base
Loopfree-alternate related context for the instance. Yang definition can be found here: srl_nokia-isis.yang:L606
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set, loopfree-alternate protection is enabled for the ISIS instance. Enables ability to seek for LFA, doesn’t guarantee LFA protection.
- attribute bool? augment_route_table=null¶
Extend remote LFA next-hop resolution path entry to RTM such that tunnel can be used in SPF decisions :rel exclude: Set the exclude context for LFA SPF computation :rel multi_homed_prefix: Multi-homed-prefix context :rel parent_instance: Relation to parent container :rel remote_lfa: Remote LFA context :rel ti_lfa: ti-lfa context
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Loopfree-alternate related context for the instance.
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.loopfree_alternate [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::Exclude exclude [0:1]¶
Relation to parent container Peer relation: Set the exclude context for LFA SPF computation
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::MultiHomedPrefix multi_homed_prefix [0:1]¶
Relation to parent container Peer relation: Multi-homed-prefix context
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::RemoteLfa remote_lfa [0:1]¶
Relation to parent container Peer relation: Remote LFA context
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::TiLfa ti_lfa [0:1]¶
Relation to parent container Peer relation: ti-lfa context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Overload¶
Parents:
nokia_srlinux::Base
Specifies isis routing instance behavior regarding overload Yang definition can be found here: srl_nokia-isis.yang:L1283
- attribute bool? advertise_external=null¶
When set to true, external (non-ISIS) routes continue to be advertised when the router is in overload.
- attribute bool? advertise_interlevel=null¶
When set to true, L1->L2 and L2->L1 inter-level routes continue to be advertised when the router is in overload. :rel immediate: Options for advertising an overloaded state immediately :rel on_boot: Options for advertising an overloaded state whenever the IS-IS process restarts :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Specifies isis routing instance behavior regarding overload
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.overload [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::overload::Immediate immediate [0:1]¶
Relation to parent container Peer relation: Options for advertising an overloaded state immediately
other end:
nokia_srlinux::network_instance::protocols::isis::instance::overload::Immediate.parent_overload [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::overload::OnBoot on_boot [0:1]¶
Relation to parent container Peer relation: Options for advertising an overloaded state whenever the IS-IS process restarts
other end:
nokia_srlinux::network_instance::protocols::isis::instance::overload::OnBoot.parent_overload [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::SegmentRouting¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1757
- Rel mpls:
Context used to configure SR-MPLS options
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.segment_routing [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::Mpls mpls [0:1]¶
Relation to parent container Peer relation: Context used to configure SR-MPLS options
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::TeDatabaseInstall¶
Parents:
nokia_srlinux::Base
When present, topology and TE information related to this protocol instance is installed into the TE database Yang definition can be found here: srl_nokia-traffic-engineering.yang:L110
- Rel bgp_ls:
When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.te_database_install [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::te_database_install::BgpLs bgp_ls [0:1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Timers¶
Parents:
nokia_srlinux::Base
Container for IS-IS timers applicable at the instance level Yang definition can be found here: srl_nokia-isis.yang:L1349
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers_lsp_lifetime_t? lsp_lifetime=null¶
Time interval in seconds that the LSPs originated by this IS (router) remain valid in the LSDB before they must be refreshed or else they are purged. :rel lsp_generation: Container with options for specifying LSP generation timer values :rel lsp_refresh: Configure LSP refresh timers. :rel parent_instance: Relation to parent container :rel spf: Container with options for specifying SPF timer values
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container for IS-IS timers applicable at the instance level
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.timers [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::timers::LspGeneration lsp_generation [0:1]¶
Relation to parent container Peer relation: Container with options for specifying LSP generation timer values
other end:
nokia_srlinux::network_instance::protocols::isis::instance::timers::LspGeneration.parent_timers [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::timers::LspRefresh lsp_refresh [0:1]¶
Relation to parent container Peer relation: Configure LSP refresh timers.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::timers::LspRefresh.parent_timers [1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::timers::Spf spf [0:1]¶
Relation to parent container Peer relation: Container with options for specifying SPF timer values
other end:
nokia_srlinux::network_instance::protocols::isis::instance::timers::Spf.parent_timers [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::TraceOptions¶
Parents:
nokia_srlinux::Base
Instance level debug trace options for IS-IS Yang definition can be found here: srl_nokia-isis.yang:L1457
- attribute nokia_srlinux::network_instance::protocols::isis::instance::trace_options_trace_t[]? trace=null¶
List of tracing options :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Instance level debug trace options for IS-IS
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::TrafficEngineering¶
Parents:
nokia_srlinux::Base
Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces Yang definition can be found here: srl_nokia-traffic-engineering.yang:L53
- attribute bool? advertisement=null¶
A setting of false means that no TE-related TLVs and subTLVs should be added to LSAs or LSPs originated by this IGP instance. A setting of true means that TE-related TLVs and subTLVs should be added to LSAs or LSPs originated by this IGP instance.
- attribute bool? legacy_link_attribute_advertisement=null¶
The advertisement mode for TE link attributes. A setting of true means that TE properties should be advertised in legacy mode as defined in RFC 8919 and RFC 8920. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.traffic_engineering [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::Transport¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1482
- attribute nokia_srlinux::network_instance::protocols::isis::instance::transport_lsp_mtu_size_t? lsp_mtu_size=null¶
Sets the maximum size of LSPs generated by this router :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.transport [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::WeightedEcmp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1198
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Setting enable triggers weighted ECMP programming for all eligible multipath IS-IS routes associated with the instance An IS-IS route is eligible for weighted ECMP if all the next-hop interfaces in the multipath set have a load-balancing-weight other than ‘none’. When weighted ECMP is disabled in an IS-IS instance all IS-IS multipath routes are programmed as normal ECMP, even if some or all of the next-hop interfaces in any particular multipath set have a load-balancing-weight other than ‘none’.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::weighted_ecmp_max_ecmp_hash_buckets_per_next_hop_group_t? max_ecmp_hash_buckets_per_next_hop_group=null¶
Specifies the maximum number of ECMP hash buckets per next-hop-group. Weighted ECMP weights are normalized based on this number of hash buckets. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::Instance parent_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::Instance.weighted_ecmp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::authentication::CsnpAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of CSNP PDUs Yang definition can be found here: srl_nokia-isis.yang:L549
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of CSNP PDUs
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Authentication.csnp_authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::authentication::HelloAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of Hello PDUs Yang definition can be found here: srl_nokia-isis.yang:L559
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::authentication::Key¶
Parents:
nokia_srlinux::Base
Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy Yang definition can be found here: srl_nokia-isis.yang:L584
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? auth_password=null¶
The secret key to use for authentication of PDUs
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_type? crypto_algorithm=null¶
The cryptographic algorithm used with the keying material to secure the messages. :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Authentication.key [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::authentication::LspAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of Link State PDUs Yang definition can be found here: srl_nokia-isis.yang:L564
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Link State PDUs
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Authentication.lsp_authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::authentication::PsnpAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of PSNP PDUs Yang definition can be found here: srl_nokia-isis.yang:L554
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of PSNP PDUs
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Authentication.psnp_authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::Level1ToLevel2¶
Parents:
nokia_srlinux::Base
Container with options to control the propagation of prefixes from level 1 to level 2.
By default all L1 prefixes are propagated without summarizarion into L2. Yang definition can be found here: srl_nokia-isis.yang:L1705
- Rel parent_inter_level_propagation_policies:
Relation to parent container
- Rel summary_address:
List of summarization prefixes
- relation nokia_srlinux::network_instance::protocols::isis::instance::InterLevelPropagationPolicies parent_inter_level_propagation_policies [1]¶
Relation to parent container Peer relation: Container with options to control the propagation of prefixes from level 1 to level 2.
By default all L1 prefixes are propagated without summarizarion into L2.
- relation nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::level1_to_level2::SummaryAddress summary_address [0:*]¶
Relation to parent container Peer relation: List of summarization prefixes
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::level1_to_level2::SummaryAddress¶
Parents:
nokia_srlinux::Base
List of summarization prefixes Yang definition can be found here: srl_nokia-isis.yang:L1710
- attribute nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::level1_to_level2::summary_address_ip_prefix_t ip_prefix¶
An IP prefix advertised into L2 that summarizes one or more L1 prefixes and causes them to be suppressed
- attribute nokia_srlinux::types::srl_nokia_isis::isis_admin_tag? route_tag=null¶
Specifies route tag value to assign to the summary route :rel parent_level1_to_level2: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::Level1ToLevel2 parent_level1_to_level2 [1]¶
Relation to parent container Peer relation: List of summarization prefixes
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::Authentication¶
Parents:
nokia_srlinux::Base
Container for specifying authetication options that apply to the IS-IS instance. Yang definition can be found here: srl_nokia-isis.yang:L748
- attribute string? keychain=null¶
Specifies a keychain to use for the authentication of Hello PDUs on this interface. :rel hello_authentication: Container with options to control the authentication of Hello PDUs :rel key: Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the IS-IS instance.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.authentication [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::authentication::HelloAuthentication hello_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::authentication::Key key [0:1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::Delay¶
Parents:
nokia_srlinux::Base
Enter the delay context Yang definition can be found here: srl_nokia-isis.yang:L905
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::delay_delay_selection_t? delay_selection=null¶
Delay source advertised by IGP for the interface :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Enter the delay context
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.delay [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::InterfaceRef¶
Parents:
nokia_srlinux::Base
Reference to a subinterface Yang definition can be found here: srl_nokia-isis.yang:L867
- attribute string? interface=null¶
Reference to a base interface, for example a port or LAG
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::interface_ref_subinterface_t? subinterface=null¶
Reference to a subinterface This requires the base interface to be specified using the interface leaf in this container. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::Ipv4Unicast¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L982
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set to true, the interface and level supports IPv4 unicast routing
- attribute bool? enable_bfd=null¶
Enable BFD for IPv4
- attribute bool? include_bfd_tlv=null¶
Specifies whether a BFD-enabled TLV is included for IPv4 on this IS-IS interface. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.ipv4_unicast [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::Ipv6Unicast¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1005
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set to true, the interface and level supports IPv6 unicast routing
- attribute bool? enable_bfd=null¶
Enable BFD for IPv6
- attribute bool? include_bfd_tlv=null¶
Specifies whether a BFD-enabled TLV is included for IPv6 on this IS-IS interface. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.ipv6_unicast [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::LdpSynchronization¶
Parents:
nokia_srlinux::Base
Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface. Yang definition can be found here: srl_nokia-ldp.yang:L1496
- attribute bool? disable=null¶
Disable LDP-IGP synchronization procedures on this interface, even if synchronization is enabled globally
- attribute bool? end_of_lib=null¶
When set to true, the IGP restores the normal metric for the IGP adjacency when learning from LDP that all label-FEC mappings have been received from the LDP peer, even if there is remaining time on the hold-down-timer. When set to false, the IGP always waits for the full duration of the hold-down-timer to restore the normal metric for the IGP adjacency. This overrides the global/instance level setting.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::ldp_synchronization_hold_down_timer_t? hold_down_timer=null¶
The maximum amount of time that the IGP advertises a maximum metric for an interface, measured from the time that the LDP adjacency is re-established after going down. This overrides the global/instance level setting. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.ldp_synchronization [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::Level¶
Parents:
nokia_srlinux::Base
List of IS-IS levels supported by this interface Yang definition can be found here: srl_nokia-isis.yang:L1149
- attribute bool? disable=null¶
Disable the Level for the interface.
- attribute nokia_srlinux::types::srl_nokia_isis::isis_wide_metric? ipv6_unicast_metric=null¶
Specifies the interface metric associated with the IPv6-unicast multi-topology. The default is based on reference-bandwidth, or else if this is not configured the default is 10.
- attribute nokia_srlinux::types::srl_nokia_isis::isis_level_number level_number¶
Specifies the IS-IS protocol level to which these attributes are applied.
- attribute nokia_srlinux::types::srl_nokia_isis::isis_wide_metric? metric=null¶
Specifies the interface metric associated with the native routing topology. The default is based on reference-bandwidth, or else if this is not configured the default is 10.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::level_priority_t? priority=null¶
ISIS neighbor priority for becoming Designated IS (LAN hello PDU only). :rel authentication: Container for specifying authetication options that apply to the IS-IS instance. :rel parent_interface: Relation to parent container :rel timers:
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: List of IS-IS levels supported by this interface
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.level [0:2]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the IS-IS instance.
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::Timers timers [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::SegmentRouting¶
Parents:
nokia_srlinux::Base
Container with interface-specific segment routing options Yang definition can be found here: srl_nokia-isis.yang:L1049
- Rel mpls:
SR-MPLS interface options
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container with interface-specific segment routing options
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.segment_routing [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::Mpls mpls [0:1]¶
Relation to parent container Peer relation: SR-MPLS interface options
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::Timers¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L954
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::timers_csnp_interval_t? csnp_interval=null¶
The interval, specified in seconds, at which periodic CSNP packets should be transmitted by the local IS on this interface.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::timers_lsp_pacing_interval_t? lsp_pacing_interval=null¶
Controls the interval between (bursts of) LSPs sent from the interface. The interval applies to all LSPs: LSPs generated by the router, and LSPs received from other routers and re-flooded. The burst interval is 100 ms if the lsp-pacing-interval < 100 ms and otherwise it is 1 second. For example, if the lsp-pacing-interval is 2 ms, at most 50 LSPs are sent every 100 ms. On the other hand, if the lsp-pacing-interval is 100 ms, at most 10 LSPs are sent every 1 second. If a value of 0 is configured, no LSPs are sent from the interface. The default pacing interval of 100 milliseconds means that a maximum of 10 LSPs are sent in a burst every second. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.timers [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::TraceOptions¶
Parents:
nokia_srlinux::Base
Interface level debug trace options for IS-IS Yang definition can be found here: srl_nokia-isis.yang:L1028
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::trace_options_trace_t[]? trace=null¶
List of tracing options :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation: Interface level debug trace options for IS-IS
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::WeightedEcmp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1126
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::weighted_ecmp_load_balancing_weight_t? load_balancing_weight=null¶
The load-balancing weight of the interface, which applies when weighted ECMP is enabled and the interface is part of a multipath set. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Interface.weighted_ecmp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::authentication::HelloAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of Hello PDUs Yang definition can be found here: srl_nokia-isis.yang:L751
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::authentication::Key¶
Parents:
nokia_srlinux::Base
Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface Yang definition can be found here: srl_nokia-isis.yang:L771
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? auth_password=null¶
The secret key to use for authentication of Hello PDUs
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_type? crypto_algorithm=null¶
The cryptographic algorithm used with the keying material to secure the messages. :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::Authentication.key [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::level::Authentication¶
Parents:
nokia_srlinux::Base
Container for specifying authetication options that apply to the IS-IS instance. Yang definition can be found here: srl_nokia-isis.yang:L748
- attribute string? keychain=null¶
Specifies a keychain to use for the authentication of Hello PDUs on this interface. :rel hello_authentication: Container with options to control the authentication of Hello PDUs :rel key: Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface :rel parent_level: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Level parent_level [1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the IS-IS instance.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::Level.authentication [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::authentication::HelloAuthentication hello_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::authentication::Key key [0:1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::level::Timers¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L819
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::level::timers_hello_interval_t? hello_interval=null¶
ISIS hello-interval value. The default is 3 seconds on Designated IS interfaces and 9 seconds for non-DIS and p2p interfaces
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::level::timers_hello_multiplier_t? hello_multiplier=null¶
ISIS hello-multiplier value. The neighbor hold time is (hello multiplier x hello interval) on non-designated intermediate system broadcast interfaces and point-to-point interfaces and (hello multiplier x hello interval / 3) on designated intermediate system broadcast interfaces. The hold time is the time in which the neighbor expects to receive the next Hello PDU. If the neighbor receives a Hello within this time, the hold time is reset. If the neighbor does not receive a Hello within the hold time, it brings the adjacency down. :rel parent_level: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::Level parent_level [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::Level.timers [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::level::authentication::HelloAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of Hello PDUs Yang definition can be found here: srl_nokia-isis.yang:L751
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::level::authentication::Key¶
Parents:
nokia_srlinux::Base
Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface Yang definition can be found here: srl_nokia-isis.yang:L771
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? auth_password=null¶
The secret key to use for authentication of Hello PDUs
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_type? crypto_algorithm=null¶
The cryptographic algorithm used with the keying material to secure the messages. :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of Hello PDUs on this interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::Mpls¶
Parents:
nokia_srlinux::Base
SR-MPLS interface options Yang definition can be found here: srl_nokia-isis.yang:L1057
- Rel ipv4_adjacency_sid:
The IPv4 adjacency SID associated with the interface
- Rel ipv4_node_sid:
Configuration of IPv4 node SID.
The (primary) IPv4 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container. :rel ipv6_adjacency_sid: The IPv6 adjacency SID associated with the interface :rel ipv6_node_sid: Configuration of IPv6 node SID.
The (primary) IPv6 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container. :rel parent_segment_routing: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::SegmentRouting parent_segment_routing [1]¶
Relation to parent container Peer relation: SR-MPLS interface options
other end:
nokia_srlinux::network_instance::protocols::isis::instance::interface::SegmentRouting.mpls [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv4AdjacencySid ipv4_adjacency_sid [0:1]¶
Relation to parent container Peer relation: The IPv4 adjacency SID associated with the interface
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv4NodeSid ipv4_node_sid [0:1]¶
Relation to parent container Peer relation: Configuration of IPv4 node SID.
The (primary) IPv4 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container.
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv6AdjacencySid ipv6_adjacency_sid [0:1]¶
Relation to parent container Peer relation: The IPv6 adjacency SID associated with the interface
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv6NodeSid ipv6_node_sid [0:1]¶
Relation to parent container Peer relation: Configuration of IPv6 node SID.
The (primary) IPv6 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv4AdjacencySid¶
Parents:
nokia_srlinux::Base
The IPv4 adjacency SID associated with the interface Yang definition can be found here: srl_nokia-isis.yang:L1104
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv4_adjacency_sid_assignment_t? assignment=null¶
The method that should be used to allocate an adjacency SID or multiple adjacency SIDs for this interface. This overrides the top level configuration to assign dynamic adjacency SIDs to all interfaces.
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? static=null¶
Configure a static adjacency SID represented by an MPLS label value. :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: The IPv4 adjacency SID associated with the interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv4NodeSid¶
Parents:
nokia_srlinux::Base
Configuration of IPv4 node SID.
The (primary) IPv4 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container. Yang definition can be found here: srl_nokia-isis.yang:L1060
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv4_node_sid_index_t? x_index=null¶
Label index to add to SRGB base. This causes the V-flag and L-flag in the prefix SID subTLV to be set to zero. :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Configuration of IPv4 node SID.
The (primary) IPv4 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv6AdjacencySid¶
Parents:
nokia_srlinux::Base
The IPv6 adjacency SID associated with the interface Yang definition can be found here: srl_nokia-isis.yang:L1114
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv6_adjacency_sid_assignment_t? assignment=null¶
The method that should be used to allocate an adjacency SID or multiple adjacency SIDs for this interface. This overrides the top level configuration to assign dynamic adjacency SIDs to all interfaces.
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? static=null¶
Configure a static adjacency SID represented by an MPLS label value. :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: The IPv6 adjacency SID associated with the interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::Ipv6NodeSid¶
Parents:
nokia_srlinux::Base
Configuration of IPv6 node SID.
The (primary) IPv6 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container. Yang definition can be found here: srl_nokia-isis.yang:L1082
- attribute nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::ipv6_node_sid_index_t? x_index=null¶
Label index to add to SRGB base. This causes the V-flag and L-flag in the prefix SID subTLV to be set to zero. :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Configuration of IPv6 node SID.
The (primary) IPv6 address of this interface is advertised as a prefix SID with the node-SID flag set. The associated label is derived from the label index configured in this container.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication¶
Parents:
nokia_srlinux::Base
Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level.
The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level. Yang definition can be found here: srl_nokia-isis.yang:L544
- attribute string? keychain=null¶
Specifies a keychain to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy. :rel csnp_authentication: Container with options to control the authentication of CSNP PDUs :rel hello_authentication: Container with options to control the authentication of Hello PDUs :rel key: Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy :rel lsp_authentication: Container with options to control the authentication of Link State PDUs :rel parent_level: Relation to parent container :rel psnp_authentication: Container with options to control the authentication of PSNP PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::Level parent_level [1]¶
Relation to parent container Peer relation: Container for specifying authetication options that apply to the entire IS-IS instance or to an entire level.
The settings in this container only apply to PDUs without an authentication behavior specified at a more granular level.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Level.authentication [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::CsnpAuthentication csnp_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of CSNP PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::HelloAuthentication hello_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::Key key [0:1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::LspAuthentication lsp_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Link State PDUs
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::PsnpAuthentication psnp_authentication [0:1]¶
Relation to parent container Peer relation: Container with options to control the authentication of PSNP PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::RoutePreference¶
Parents:
nokia_srlinux::Base
Specify the route preference (admin distance) for IP routes asssociated with the level Yang definition can be found here: srl_nokia-isis.yang:L1591
- attribute nokia_srlinux::network_instance::protocols::isis::instance::level::route_preference_external_t? external=null¶
Specify the route preference of external routes carried in this level. By default the route preference of external L1 routes is 160. By default the route preference of external L2 routes is 165.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::level::route_preference_internal_t? internal=null¶
Specify the route preference of internal routes carried in this level. By default the route preference of internal L1 routes is 15. By default the route preference of internal L2 routes is 18. :rel parent_level: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Level parent_level [1]¶
Relation to parent container Peer relation: Specify the route preference (admin distance) for IP routes asssociated with the level
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Level.route_preference [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::TraceOptions¶
Parents:
nokia_srlinux::Base
Level debug trace options for IS-IS Yang definition can be found here: srl_nokia-isis.yang:L1613
- attribute nokia_srlinux::network_instance::protocols::isis::instance::level::trace_options_trace_t[]? trace=null¶
List of tracing options :rel parent_level: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Level parent_level [1]¶
Relation to parent container Peer relation: Level debug trace options for IS-IS
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Level.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::CsnpAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of CSNP PDUs Yang definition can be found here: srl_nokia-isis.yang:L549
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of CSNP PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::HelloAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of Hello PDUs Yang definition can be found here: srl_nokia-isis.yang:L559
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Hello PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::Key¶
Parents:
nokia_srlinux::Base
Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy Yang definition can be found here: srl_nokia-isis.yang:L584
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? auth_password=null¶
The secret key to use for authentication of PDUs
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_type? crypto_algorithm=null¶
The cryptographic algorithm used with the keying material to secure the messages. :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container to specify the secret key and crypto algorithm to use for the authentication of PDUs when the behavior is controlled at this level of the configuration hierarchy
other end:
nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication.key [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::LspAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of Link State PDUs Yang definition can be found here: srl_nokia-isis.yang:L564
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of Link State PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::PsnpAuthentication¶
Parents:
nokia_srlinux::Base
Container with options to control the authentication of PSNP PDUs Yang definition can be found here: srl_nokia-isis.yang:L554
- attribute nokia_srlinux::types::srl_nokia_isis::isis_auth_check_type? check_received=null¶
Specifies the type of authentication checks done for received PDUs of the specified type.
- attribute bool? generate=null¶
When set to true, IS-IS is instructed to add an authentication TLV to every transmitted PDU of the specified type :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::level::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Container with options to control the authentication of PSNP PDUs
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::Exclude¶
Parents:
nokia_srlinux::Base
Set the exclude context for LFA SPF computation Yang definition can be found here: srl_nokia-isis.yang:L627
- attribute string[]? prefix_policy=null¶
Policy to exclude prefixes from LFA SPF calculation :rel parent_loopfree_alternate: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate parent_loopfree_alternate [1]¶
Relation to parent container Peer relation: Set the exclude context for LFA SPF computation
other end:
nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate.exclude [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::MultiHomedPrefix¶
Parents:
nokia_srlinux::Base
Multi-homed-prefix context Yang definition can be found here: srl_nokia-isis.yang:L640
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set, multi-homed prefix context is enabled for the ISIS instance
- attribute nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::multi_homed_prefix_preference_t? preference=null¶
Backup preference of a multi-homed prefix :rel parent_loopfree_alternate: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate parent_loopfree_alternate [1]¶
Relation to parent container Peer relation: Multi-homed-prefix context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::RemoteLfa¶
Parents:
nokia_srlinux::Base
Remote LFA context Yang definition can be found here: srl_nokia-isis.yang:L667
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set, remote lfa protection is enabled for the ISIS instance. Enables ability to seek for an eligible remote-LFA node (P,Q intersection), doesn’t guarantee existance of remote-LFA protection.
- attribute yang::types::uint32? max_pq_cost=null¶
Maximum cost of destination node during reverse SPF calculation :rel node_protect: Node protect context :rel parent_loopfree_alternate: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate parent_loopfree_alternate [1]¶
Relation to parent container Peer relation: Remote LFA context
other end:
nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate.remote_lfa [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::remote_lfa::NodeProtect node_protect [0:1]¶
Relation to parent container Peer relation: Node protect context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::TiLfa¶
Parents:
nokia_srlinux::Base
ti-lfa context Yang definition can be found here: srl_nokia-isis.yang:L710
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set, ti-lfa protection is enabled for the ISIS instance. ti-LFA seeks for a viable P,Q intersection based on constraints including max ti-lfa labels.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::ti_lfa_max_sr_policy_lfa_labels_t? max_sr_policy_lfa_labels=null¶
Maximum number of labels the TI-LFA backup path can use :rel node_protect: Node-protect context :rel parent_loopfree_alternate: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate parent_loopfree_alternate [1]¶
Relation to parent container Peer relation: ti-lfa context
other end:
nokia_srlinux::network_instance::protocols::isis::instance::LoopfreeAlternate.ti_lfa [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::ti_lfa::NodeProtect node_protect [0:1]¶
Relation to parent container Peer relation: Node-protect context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::remote_lfa::NodeProtect¶
Parents:
nokia_srlinux::Base
Node protect context Yang definition can be found here: srl_nokia-isis.yang:L688
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set, the IS-IS instance enables node protection using remote lfa. Remote LFA seeks for a viable P,Q intersection that can protect against node failures.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::remote_lfa::node_protect_max_pq_nodes_t? max_pq_nodes=null¶
Maximum number of PQ nodes found in the LFA SPFs. Value 0 disables node protect :rel parent_remote_lfa: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::RemoteLfa parent_remote_lfa [1]¶
Relation to parent container Peer relation: Node protect context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::ti_lfa::NodeProtect¶
Parents:
nokia_srlinux::Base
Node-protect context Yang definition can be found here: srl_nokia-isis.yang:L732
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set to enabled, the IS-IS instance enables ti-lfa node protection. :rel parent_ti_lfa: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::TiLfa parent_ti_lfa [1]¶
Relation to parent container Peer relation: Node-protect context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::overload::Immediate¶
Parents:
nokia_srlinux::Base
Options for advertising an overloaded state immediately Yang definition can be found here: srl_nokia-isis.yang:L1304
- attribute bool? max_metric=null¶
When set to true transit links are advertised with a wide metric of 0xffffffe and a narrow metric of 0x3f
- attribute bool? set_bit=null¶
When set to true, the Overload bit is set :rel parent_overload: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Overload parent_overload [1]¶
Relation to parent container Peer relation: Options for advertising an overloaded state immediately
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Overload.immediate [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::overload::OnBoot¶
Parents:
nokia_srlinux::Base
Options for advertising an overloaded state whenever the IS-IS process restarts Yang definition can be found here: srl_nokia-isis.yang:L1323
- attribute bool? max_metric=null¶
When set to true transit links are advertised with a wide metric of 0xffffffe and a narrow metric of 0x3f
- attribute bool? set_bit=null¶
When set to true, the Overload bit is set
- attribute nokia_srlinux::network_instance::protocols::isis::instance::overload::on_boot_timeout_t? timeout=null¶
Specifies the time that the router should remain in overload state after the IS-IS process restarts :rel parent_overload: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Overload parent_overload [1]¶
Relation to parent container Peer relation: Options for advertising an overloaded state whenever the IS-IS process restarts
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Overload.on_boot [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::Mpls¶
Parents:
nokia_srlinux::Base
Context used to configure SR-MPLS options Yang definition can be found here: srl_nokia-isis.yang:L1759
- attribute string? static_label_block=null¶
Reference to a static label block to use an SRLB. Configuration of this label block is mandatory in order to assign static adjacency SID labels. This label block is advertised as an SRLB in the router capabilities TLV. :rel dynamic_adjacency_sids: :rel parent_segment_routing: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::SegmentRouting parent_segment_routing [1]¶
Relation to parent container Peer relation: Context used to configure SR-MPLS options
other end:
nokia_srlinux::network_instance::protocols::isis::instance::SegmentRouting.mpls [0:1]
- relation nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::mpls::DynamicAdjacencySids dynamic_adjacency_sids [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::mpls::DynamicAdjacencySids¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-isis.yang:L1769
- attribute bool? all_interfaces=null¶
When true, IS-IS is instructed to assign a dynamic adjacency SID to all IS-IS interfaces in all levels, except for the interfaces configured with an adjacency SID assignment of ‘none’ or ‘static’.
- attribute nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::mpls::dynamic_adjacency_sids_hold_time_t? hold_time=null¶
Adjacency SID hold time that is applicable to dynamically allocated adjacency SIDs :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::te_database_install::BgpLs¶
Parents:
nokia_srlinux::Base
When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes Yang definition can be found here: srl_nokia-traffic-engineering.yang:L78
- attribute yang::types::uint32? bgp_ls_identifier=null¶
BGP-LS identifier value that is sent in the BGP-LS NLRI
- attribute nokia_srlinux::network_instance::protocols::isis::instance::te_database_install::bgp_ls_igp_identifier_t? igp_identifier=null¶
Unique identifier of the IGP instance that is sent in the BGP-LS NLRI :rel parent_te_database_install: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::TeDatabaseInstall parent_te_database_install [1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
other end:
nokia_srlinux::network_instance::protocols::isis::instance::TeDatabaseInstall.bgp_ls [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::timers::LspGeneration¶
Parents:
nokia_srlinux::Base
Container with options for specifying LSP generation timer values Yang definition can be found here: srl_nokia-isis.yang:L1419
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_generation_initial_wait_t? initial_wait=null¶
Time interval between the detection of topology change and when the new LSP is generated. The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_generation_max_wait_t? max_wait=null¶
Specifies the maximum interval between two consecutive generations of an LSP. The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_generation_second_wait_t? second_wait=null¶
Time interval between the the first and second LSP generation. The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms :rel parent_timers: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Timers parent_timers [1]¶
Relation to parent container Peer relation: Container with options for specifying LSP generation timer values
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Timers.lsp_generation [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::timers::LspRefresh¶
Parents:
nokia_srlinux::Base
Configure LSP refresh timers. Yang definition can be found here: srl_nokia-isis.yang:L1361
- attribute bool? half_lifetime=null¶
When set to true, the LSP refresh interval is half the lsp-lifetime
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::lsp_refresh_interval_t? interval=null¶
Time interval in seconds since the last advertisement of its LSP when the router attempts to refresh the LSP. Must not exceed 90% of the lsp-lifetime. This value is ignored when half-lifetime is set to true. :rel parent_timers: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Timers parent_timers [1]¶
Relation to parent container Peer relation: Configure LSP refresh timers.
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Timers.lsp_refresh [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::isis::instance::timers::Spf¶
Parents:
nokia_srlinux::Base
Container with options for specifying SPF timer values Yang definition can be found here: srl_nokia-isis.yang:L1382
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::spf_initial_wait_t? initial_wait=null¶
Time interval between the detection of topology change and when the SPF algorithm runs. The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::spf_max_wait_t? max_wait=null¶
Specifies the maximum interval between two consecutive SPF calculations in milliseconds. The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms
- attribute nokia_srlinux::network_instance::protocols::isis::instance::timers::spf_second_wait_t? second_wait=null¶
Time interval between the the first and second SPF run. The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms :rel parent_timers: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::isis::instance::Timers parent_timers [1]¶
Relation to parent container Peer relation: Container with options for specifying SPF timer values
other end:
nokia_srlinux::network_instance::protocols::isis::instance::Timers.spf [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::Discovery¶
Parents:
nokia_srlinux::Base
Neighbor discovery configuration and operational state. Yang definition can be found here: srl_nokia-ldp.yang:L1056
- Rel interfaces:
The complete set of interfaces used for LDP Basic Discovery.
- Rel parent_ldp:
Relation to parent container
- Rel targeted:
List of targeted peers for extended discovery.
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Neighbor discovery configuration and operational state.
other end:
nokia_srlinux::network_instance::protocols::Ldp.discovery [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces interfaces [0:1]¶
Relation to parent container Peer relation: The complete set of interfaces used for LDP Basic Discovery.
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces.parent_discovery [1]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::Targeted targeted [0:1]¶
Relation to parent container Peer relation: List of targeted peers for extended discovery.
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::Targeted.parent_discovery [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::EntropyLabel¶
Parents:
nokia_srlinux::Base
Options for configuring control and data plane aspects of entropy label Yang definition can be found here: srl_nokia-ldp.yang:L736
- attribute bool? advertise_capability=null¶
Advertise the Entropy Label Capability :rel parent_ldp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Options for configuring control and data plane aspects of entropy label
other end:
nokia_srlinux::network_instance::protocols::Ldp.entropy_label [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::GracefulRestart¶
Parents:
nokia_srlinux::Base
Attributes for graceful restart. Yang definition can be found here: srl_nokia-ldp.yang:L274
- attribute bool? helper_enable=null¶
Enable or disable graceful restart as a helper.
- attribute nokia_srlinux::network_instance::protocols::ldp::graceful_restart_max_reconnect_time_t? max_reconnect_time=null¶
Specifies the maximum time interval, in seconds, that this router is willing to wait for the remote LDP peer to reconnect after an LDP communication failure.
- attribute nokia_srlinux::network_instance::protocols::ldp::graceful_restart_max_recovery_time_t? max_recovery_time=null¶
Specifies the maximum time interval, in seconds, that this router is willing to preserve its MPLS forwarding state after receiving the Initialization message from the restarted LDP peer. :rel parent_ldp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Attributes for graceful restart.
other end:
nokia_srlinux::network_instance::protocols::Ldp.graceful_restart [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::Ipv4¶
Parents:
nokia_srlinux::Base
Container for configuration and state related to the IPv4 address family. Yang definition can be found here: srl_nokia-ldp.yang:L838
- Rel fec_resolution:
Container with options for controlling IPv4 prefix FEC resolution
- Rel parent_ldp:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Container for configuration and state related to the IPv4 address family.
other end:
nokia_srlinux::network_instance::protocols::Ldp.ipv4 [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::ipv4::FecResolution fec_resolution [0:1]¶
Relation to parent container Peer relation: Container with options for controlling IPv4 prefix FEC resolution
other end:
nokia_srlinux::network_instance::protocols::ldp::ipv4::FecResolution.parent_ipv4 [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::LoopfreeAlternate¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ldp.yang:L790
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable Loop Free Alternates. :rel parent_ldp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::Ldp.loopfree_alternate [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::Multipath¶
Parents:
nokia_srlinux::Base
Container with options to configure load-balancing over equal-cost paths Yang definition can be found here: srl_nokia-ldp.yang:L826
- attribute nokia_srlinux::network_instance::protocols::ldp::multipath_max_paths_t? max_paths=null¶
Specifies the maximum number of next-hops used for load-balancing toward towards a given FEC :rel parent_ldp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Container with options to configure load-balancing over equal-cost paths
other end:
nokia_srlinux::network_instance::protocols::Ldp.multipath [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::Peers¶
Parents:
nokia_srlinux::Base
Configuration and state related to peers Yang definition can be found here: srl_nokia-ldp.yang:L1291
- attribute nokia_srlinux::network_instance::protocols::ldp::peers_session_keepalive_holdtime_t? session_keepalive_holdtime=null¶
The time interval after which an inactive LDP session terminates and the corresponding TCP session closes. Inactivity is defined as not receiving LDP packets from the peer.
- attribute nokia_srlinux::network_instance::protocols::ldp::peers_session_keepalive_interval_t? session_keepalive_interval=null¶
The interval between successive transmissions of keepalive packets. Keepalive packets are only sent in the absence of other LDP packets transmitted over the LDP session. :rel parent_ldp: Relation to parent container :rel peer: List of peers. :rel trace_options: Configure event/packet tracing for all sessions (configured and dynamic).
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Configuration and state related to peers
other end:
nokia_srlinux::network_instance::protocols::Ldp.peers [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::peers::Peer peer [0:*]¶
Relation to parent container Peer relation: List of peers.
other end:
nokia_srlinux::network_instance::protocols::ldp::peers::Peer.parent_peers [1]
- relation nokia_srlinux::network_instance::protocols::ldp::peers::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Configure event/packet tracing for all sessions (configured and dynamic).
other end:
nokia_srlinux::network_instance::protocols::ldp::peers::TraceOptions.parent_peers [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::StaticFec¶
Parents:
nokia_srlinux::Base
Configure static FEC. Yang definition can be found here: srl_nokia-ldp.yang:L799
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix fec_prefix¶
Static FEC IP prefix.
- attribute bool? swap=null¶
Swap label. If false, label is popped. :rel parent_ldp: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Ldp parent_ldp [1]¶
Relation to parent container Peer relation: Configure static FEC.
other end:
nokia_srlinux::network_instance::protocols::Ldp.static_fec [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces¶
Parents:
nokia_srlinux::Base
The complete set of interfaces used for LDP Basic Discovery. Yang definition can be found here: srl_nokia-ldp.yang:L1059
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces_hello_holdtime_t? hello_holdtime=null¶
The time interval for which a LDP Hello adjacency is maintained in the absence of Hello messages from the LDP neighbor
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces_hello_interval_t? hello_interval=null¶
The interval between consecutive LDP Hello messages used in LDP discovery :rel interface: List of LDP interfaces used for LDP Basic Discovery. :rel parent_discovery: Relation to parent container :rel trace_options: Configure event/packet tracing for all LDP interfaces.
- relation nokia_srlinux::network_instance::protocols::ldp::Discovery parent_discovery [1]¶
Relation to parent container Peer relation: The complete set of interfaces used for LDP Basic Discovery.
other end:
nokia_srlinux::network_instance::protocols::ldp::Discovery.interfaces [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::Interface interface [0:*]¶
Relation to parent container Peer relation: List of LDP interfaces used for LDP Basic Discovery.
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Configure event/packet tracing for all LDP interfaces.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::Targeted¶
Parents:
nokia_srlinux::Base
List of targeted peers for extended discovery. Yang definition can be found here: srl_nokia-ldp.yang:L1187
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::targeted_hello_holdtime_t? hello_holdtime=null¶
The time interval for which a LDP Hello adjacency is maintained in the absence of Hello messages from the LDP neighbor
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::targeted_hello_interval_t? hello_interval=null¶
The interval between consecutive LDP Hello messages used in LDP discovery :rel ipv4: :rel parent_discovery: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::Discovery parent_discovery [1]¶
Relation to parent container Peer relation: List of targeted peers for extended discovery.
other end:
nokia_srlinux::network_instance::protocols::ldp::Discovery.targeted [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::Ipv4.parent_targeted [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::Interface¶
Parents:
nokia_srlinux::Base
List of LDP interfaces used for LDP Basic Discovery. Yang definition can be found here: srl_nokia-ldp.yang:L1079
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface_hello_holdtime_t? hello_holdtime=null¶
The time interval for which a LDP Hello adjacency is maintained in the absence of Hello messages from the LDP neighbor
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface_hello_interval_t? hello_interval=null¶
The interval between consecutive LDP Hello messages used in LDP discovery
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all name¶
Reference to a specific subinterface that is bound to the network instance :rel ipv4: :rel parent_interfaces: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces parent_interfaces [1]¶
Relation to parent container Peer relation: List of LDP interfaces used for LDP Basic Discovery.
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::TraceOptions¶
Parents:
nokia_srlinux::Base
Configure event/packet tracing for all LDP interfaces. Yang definition can be found here: srl_nokia-ldp.yang:L1070
- attribute nokia_srlinux::types::srl_nokia_ldp::interface_trace_option_flags[]? trace=null¶
Specifies the trace information to be captured. :rel parent_interfaces: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces parent_interfaces [1]¶
Relation to parent container Peer relation: Configure event/packet tracing for all LDP interfaces.
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::Interfaces.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::Ipv4¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ldp.yang:L1085
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable LDP discovery for IPv4 on a particular interface.
- attribute bool? enable_bfd=null¶
Enable BFD
- attribute bool? local_interface_lsr_id=null¶
Set to true to use the local interface IP address as the LSR ID. When set to false, the system interface IP address is used as the LSR ID :rel parent_interface: Relation to parent container :rel trace_options: Configure event/packet tracing for one specific LDP interface.
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::Interface.ipv4 [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::ipv4::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Configure event/packet tracing for one specific LDP interface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::ipv4::TraceOptions¶
Parents:
nokia_srlinux::Base
Configure event/packet tracing for one specific LDP interface. Yang definition can be found here: srl_nokia-ldp.yang:L1175
- attribute nokia_srlinux::types::srl_nokia_ldp::interface_trace_option_flags[]? trace=null¶
Specifies the trace information to be captured. :rel parent_ipv4: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Configure event/packet tracing for one specific LDP interface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::Ipv4¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ldp.yang:L1199
- Rel parent_targeted:
Relation to parent container
- Rel target:
List of configured targeted LDP peers.
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::Targeted parent_targeted [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::Targeted.ipv4 [0:1]
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::Target target [0:*]¶
Relation to parent container Peer relation: List of configured targeted LDP peers.
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::Target.parent_ipv4 [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::Target¶
Parents:
nokia_srlinux::Base
List of configured targeted LDP peers. Yang definition can be found here: srl_nokia-ldp.yang:L1200
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the targeted LDP adjacency.
- attribute bool? enable_bfd=null¶
Enable BFD
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::target_hello_holdtime_t? hello_holdtime=null¶
The time interval for which a LDP Hello adjacency is maintained in the absence of Hello messages from the LDP neighbor
- attribute nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::target_hello_interval_t? hello_interval=null¶
The interval between consecutive LDP Hello messages used in LDP discovery
- attribute string? override_interface_lsr_id=null¶
Reference to an LDP interface or loopback interface whose address is to be used as local LSR ID. If not specified, the LSR ID is derived from the IPv4 address of the system interface
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address remote_address¶
Configuration of neighbor address of the targeted LDP adjacency. :rel parent_ipv4: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: List of configured targeted LDP peers.
other end:
nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::Ipv4.target [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::ipv4::FecResolution¶
Parents:
nokia_srlinux::Base
Container with options for controlling IPv4 prefix FEC resolution Yang definition can be found here: srl_nokia-ldp.yang:L893
- attribute bool? longest_prefix=null¶
When this is set to true IPv4 prefix FECs can be resolved by less-specific IPv4 routes in the route table, as long as the prefix bits of the route match the prefix bits of the FEC; the IP route with the longest prefix match is the route that is used to resolve the FEC. When this is set to false, IPv4 prefix FECs can only be resolved by routes that are an exact match of the FEC in terms of prefix length. :rel parent_ipv4: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::Ipv4 parent_ipv4 [1]¶
Relation to parent container Peer relation: Container with options for controlling IPv4 prefix FEC resolution
other end:
nokia_srlinux::network_instance::protocols::ldp::Ipv4.fec_resolution [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::peers::Peer¶
Parents:
nokia_srlinux::Base
List of peers. Yang definition can be found here: srl_nokia-ldp.yang:L1304
- attribute string? export_prefix_policy=null¶
Apply an export prefix policy to filter advertised label bindings.
- attribute yang::types::uint32? fec_limit=null¶
The maximum number of FECs of all types combined that will be accepted from the peer. The value 0 implies no limit.
- attribute string? import_prefix_policy=null¶
Apply an import prefix policy to filter received label bindings.
- attribute yang::types::uint16 label_space_id¶
The Label Space ID of the peer, to identify a specific label space within the LSR. This is the last two octets of the LDP ID. This leaf is used together with the leaf ‘lsr-id’ to form the LDP ID.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address lsr_id¶
The LSR ID of the peer, to identify the globally unique LSR. This is the first four octets of the LDP ID. This leaf is used together with the leaf ‘label-space-id’ to form the LDP ID. :rel parent_peers: Relation to parent container :rel tcp_transport: :rel trace_options: Configure event/packet tracing for one specific session.
- relation nokia_srlinux::network_instance::protocols::ldp::Peers parent_peers [1]¶
Relation to parent container Peer relation: List of peers.
other end:
nokia_srlinux::network_instance::protocols::ldp::Peers.peer [0:*]
- relation nokia_srlinux::network_instance::protocols::ldp::peers::peer::TcpTransport tcp_transport [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ldp::peers::peer::TcpTransport.parent_peer [1]
- relation nokia_srlinux::network_instance::protocols::ldp::peers::peer::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Configure event/packet tracing for one specific session.
other end:
nokia_srlinux::network_instance::protocols::ldp::peers::peer::TraceOptions.parent_peer [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::peers::TraceOptions¶
Parents:
nokia_srlinux::Base
Configure event/packet tracing for all sessions (configured and dynamic). Yang definition can be found here: srl_nokia-ldp.yang:L1295
- attribute nokia_srlinux::types::srl_nokia_ldp::session_trace_option_flags[]? trace=null¶
Specifies the trace information to be captured. :rel parent_peers: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::Peers parent_peers [1]¶
Relation to parent container Peer relation: Configure event/packet tracing for all sessions (configured and dynamic).
other end:
nokia_srlinux::network_instance::protocols::ldp::Peers.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::peers::peer::TcpTransport¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ldp.yang:L1321
- Rel parent_peer:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::peers::Peer parent_peer [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ldp::peers::Peer.tcp_transport [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ldp::peers::peer::TraceOptions¶
Parents:
nokia_srlinux::Base
Configure event/packet tracing for one specific session. Yang definition can be found here: srl_nokia-ldp.yang:L1324
- attribute nokia_srlinux::types::srl_nokia_ldp::session_trace_option_flags[]? trace=null¶
Specifies the trace information to be captured. :rel parent_peer: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ldp::peers::Peer parent_peer [1]¶
Relation to parent container Peer relation: Configure event/packet tracing for one specific session.
other end:
nokia_srlinux::network_instance::protocols::ldp::peers::Peer.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::Interface¶
Parents:
nokia_srlinux::Base
List of MLD interfaces Yang definition can be found here: srl_nokia-mld.yang:L875
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the MLD protocol for this interface Used to administratively enable or disable the MLD protocol on a routed subinterface
- attribute string? import_policy=null¶
Apply an import policy. The lenght of the policy name should not exceed 32 charachters
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index>
- attribute nokia_srlinux::network_instance::protocols::mld::interface_maximum_number_group_sources_t? maximum_number_group_sources=null¶
MAX number of MLD group/source combinations for this interface, 0 means no limit
- attribute nokia_srlinux::network_instance::protocols::mld::interface_maximum_number_groups_t? maximum_number_groups=null¶
MAX number of MLD Groups for this interface, 0 means no limit
- attribute nokia_srlinux::network_instance::protocols::mld::interface_maximum_number_sources_t? maximum_number_sources=null¶
MAX number of MLD sources per group for this interface, 0 means no limit
- attribute nokia_srlinux::network_instance::protocols::mld::interface_query_interval_t? query_interval=null¶
Interval at which the router sends the mld membership queries
- attribute nokia_srlinux::network_instance::protocols::mld::interface_query_last_member_interval_t? query_last_member_interval=null¶
Interval at which Group-Specific-Query packets are transmitted
- attribute nokia_srlinux::network_instance::protocols::mld::interface_query_response_interval_t? query_response_interval=null¶
Time to wait to receive a response to the MLD membership query from the host
- attribute bool? router_alert_check=null¶
Enable or disable router alert checking for MLD messages received on this interface
- attribute nokia_srlinux::types::srl_nokia_mld::mld_version? version=null¶
MLD Version :rel parent_mld: Relation to parent container :rel ssm: Container to configure Source specific multicast (SSM) options :rel static_membership_groups: Container to configure static <S,G>s for this interface
- relation nokia_srlinux::network_instance::protocols::Mld parent_mld [1]¶
Relation to parent container Peer relation: List of MLD interfaces
other end:
nokia_srlinux::network_instance::protocols::Mld.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::mld::interface::Ssm ssm [0:1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options
other end:
nokia_srlinux::network_instance::protocols::mld::interface::Ssm.parent_interface [1]
- relation nokia_srlinux::network_instance::protocols::mld::interface::StaticMembershipGroups static_membership_groups [0:1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::Ssm¶
Parents:
nokia_srlinux::Base
Container to configure Source specific multicast (SSM) options Yang definition can be found here: srl_nokia-mld.yang:L125
- Rel mappings:
A list of source specific multicast (SSM) mappings
- Rel parent_mld:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Mld parent_mld [1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options
other end:
nokia_srlinux::network_instance::protocols::Mld.ssm [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::ssm::Mappings mappings [0:1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::mld::ssm::Mappings.parent_ssm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-mld.yang:L247
- Rel parent_mld:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::Mld parent_mld [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::Mld.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::mld::trace_options::Trace.parent_trace_options [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::Ssm¶
Parents:
nokia_srlinux::Base
Container to configure Source specific multicast (SSM) options Yang definition can be found here: srl_nokia-mld.yang:L125
- Rel mappings:
A list of source specific multicast (SSM) mappings
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container to configure Source specific multicast (SSM) options
other end:
nokia_srlinux::network_instance::protocols::mld::Interface.ssm [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::interface::ssm::Mappings mappings [0:1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::mld::interface::ssm::Mappings.parent_ssm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::StaticMembershipGroups¶
Parents:
nokia_srlinux::Base
Container to configure static <S,G>s for this interface Yang definition can be found here: srl_nokia-mld.yang:L405
- Rel group_range:
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface
other end:
nokia_srlinux::network_instance::protocols::mld::Interface.static_membership_groups [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::GroupRange group_range [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::ssm::Mappings¶
Parents:
nokia_srlinux::Base
A list of source specific multicast (SSM) mappings Yang definition can be found here: srl_nokia-mld.yang:L128
- Rel group_range:
A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address. :rel parent_ssm: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::interface::Ssm parent_ssm [1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::mld::interface::Ssm.mappings [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::GroupRange group_range [0:*]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::GroupRange¶
Parents:
nokia_srlinux::Base
A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address. Yang definition can be found here: srl_nokia-mld.yang:L131
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address start¶
start of the group range
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address x_end¶
end of the group range :rel parent_mappings: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::mld::interface::ssm::Mappings parent_mappings [1]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address.
other end:
nokia_srlinux::network_instance::protocols::mld::interface::ssm::Mappings.group_range [0:*]
- relation nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::group_range::Source source [1:*]¶
Multicast source address list Peer relation: Relation to parent container
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::group_range::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-mld.yang:L141
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address source¶
Multicast source address :rel parent_group_range: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::GroupRange parent_group_range [1]¶
Multicast source address list Peer relation: Relation to parent container
other end:
nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::GroupRange.source [1:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::GroupRange¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mld.yang:L408
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address start¶
start of the group range
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address x_end¶
end of the group range :rel parent_static_membership_groups: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::mld::interface::StaticMembershipGroups parent_static_membership_groups [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::mld::interface::StaticMembershipGroups.group_range [0:*]
- relation nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::group_range::Source source [0:*]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::group_range::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-mld.yang:L414
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address source¶
Multicast source address :rel parent_group_range: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::GroupRange parent_group_range [1]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::ssm::Mappings¶
Parents:
nokia_srlinux::Base
A list of source specific multicast (SSM) mappings Yang definition can be found here: srl_nokia-mld.yang:L128
- Rel group_range:
A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address. :rel parent_ssm: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::Ssm parent_ssm [1]¶
Relation to parent container Peer relation: A list of source specific multicast (SSM) mappings
other end:
nokia_srlinux::network_instance::protocols::mld::Ssm.mappings [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::ssm::mappings::GroupRange group_range [0:*]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address.
other end:
nokia_srlinux::network_instance::protocols::mld::ssm::mappings::GroupRange.parent_mappings [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::ssm::mappings::GroupRange¶
Parents:
nokia_srlinux::Base
A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address. Yang definition can be found here: srl_nokia-mld.yang:L131
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address start¶
start of the group range
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address x_end¶
end of the group range :rel parent_mappings: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::mld::ssm::Mappings parent_mappings [1]¶
Relation to parent container Peer relation: A Source Specific Multicast (SSM) mapping
This allows MLD v2 hosts to be able to join in SSM environments by translating MLD v1 reports into MLD v2 reports. The request in an MLD v1 join is sent toward the source address found by matching the multicast address.
other end:
nokia_srlinux::network_instance::protocols::mld::ssm::Mappings.group_range [0:*]
- relation nokia_srlinux::network_instance::protocols::mld::ssm::mappings::group_range::Source source [1:*]¶
Multicast source address list Peer relation: Relation to parent container
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::ssm::mappings::group_range::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-mld.yang:L141
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address source¶
Multicast source address :rel parent_group_range: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::ssm::mappings::GroupRange parent_group_range [1]¶
Multicast source address list Peer relation: Relation to parent container
other end:
nokia_srlinux::network_instance::protocols::mld::ssm::mappings::GroupRange.source [1:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-mld.yang:L250
- Rel interface:
Enable tracing interface events.
- Rel packet:
Trace MLD Packet types
Only one type can be enabled at a time :rel parent_trace_options: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::mld::TraceOptions.trace [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Interface interface [0:1]¶
Relation to parent container Peer relation: Enable tracing interface events.
other end:
nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Interface.parent_trace [1]
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Trace MLD Packet types Only one type can be enabled at a time
other end:
nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Packet.parent_trace [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Interface¶
Parents:
nokia_srlinux::Base
Enable tracing interface events. Yang definition can be found here: srl_nokia-mld.yang:L253
- attribute bool? all=null¶
Trace for all interfaces
- attribute string? name=null¶
Trace for interface with this name :rel parent_trace: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Enable tracing interface events.
other end:
nokia_srlinux::network_instance::protocols::mld::trace_options::Trace.interface [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Trace MLD Packet types Only one type can be enabled at a time Yang definition can be found here: srl_nokia-mld.yang:L169
- attribute nokia_srlinux::network_instance::protocols::mld::trace_options::trace::packet_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::mld::trace_options::trace::packet_type_t? type=null¶
- Rel interface:
Enable interface filter for packets :rel parent_trace: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace MLD Packet types Only one type can be enabled at a time
other end:
nokia_srlinux::network_instance::protocols::mld::trace_options::Trace.packet [0:1]
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::packet::Interface interface [0:1]¶
Relation to parent container Peer relation: Enable interface filter for packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld::trace_options::trace::packet::Interface¶
Parents:
nokia_srlinux::Base
Enable interface filter for packets Yang definition can be found here: srl_nokia-mld.yang:L174
- attribute bool? all=null¶
Trace for all interfaces
- attribute string? name=null¶
Trace for interface with this name :rel parent_packet: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: Enable interface filter for packets
other end:
nokia_srlinux::network_instance::protocols::mld::trace_options::trace::Packet.interface [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::Interface¶
Parents:
nokia_srlinux::Base
List of MLD interfaces Yang definition can be found here: srl_nokia-mld-snooping.yang:L1047
- attribute bool? fast_leave=null¶
Allow MLD fast leave processing When enabled, the multicast state is removed immediately upon receiving an MLD leave message.
- attribute string? import_policy=null¶
Apply an import policy. The lenght of the policy name should not exceed 32 charachters.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index>
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_maximum_number_group_sources_t? maximum_number_group_sources=null¶
Maximum number of MLD group/source combinations for this interface
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_maximum_number_groups_t? maximum_number_groups=null¶
Maximum number of MLD Groups for this interface
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_maximum_number_sources_t? maximum_number_sources=null¶
Maximum number of MLD sources per group for this interface
- attribute bool? mrouter_port=null¶
Operate port as a multicast router port
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_query_interval_t? query_interval=null¶
Interval at which the router sends the MLD membership queries
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_query_last_member_interval_t? query_last_member_interval=null¶
Interval at which Group-Specific-Query packets are transmitted
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_query_response_interval_t? query_response_interval=null¶
Time to wait to receive a response to the MLD membership query from the host
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::interface_robust_count_t? robust_count=null¶
Tune MLD robustness to allow for expected packet loss The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.
- attribute bool? router_alert_check=null¶
Enable or disable router alert checking for MLD messages received on this interface
- attribute bool? send_queries=null¶
Generate MLD general queries
- attribute nokia_srlinux::types::srl_nokia_mld_snooping::mld_version? version=null¶
MLD Version :rel parent_mld_snooping: Relation to parent container :rel static_membership_groups: Container to configure static <S,G>s for this interface
- relation nokia_srlinux::network_instance::protocols::MldSnooping parent_mld_snooping [1]¶
Relation to parent container Peer relation: List of MLD interfaces
other end:
nokia_srlinux::network_instance::protocols::MldSnooping.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::interface::StaticMembershipGroups static_membership_groups [0:1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-mld-snooping.yang:L97
- Rel parent_mld_snooping:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::MldSnooping parent_mld_snooping [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::MldSnooping.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::interface::StaticMembershipGroups¶
Parents:
nokia_srlinux::Base
Container to configure static <S,G>s for this interface Yang definition can be found here: srl_nokia-mld-snooping.yang:L523
- Rel group:
- Rel parent_interface:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld_snooping::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container to configure static <S,G>s for this interface
other end:
nokia_srlinux::network_instance::protocols::mld_snooping::Interface.static_membership_groups [0:1]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::Group group [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::Group¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mld-snooping.yang:L526
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address group¶
group address.
- attribute bool? starg=null¶
any source address (*,G) :rel parent_static_membership_groups: Relation to parent container :rel source: Multicast source address list
- relation nokia_srlinux::network_instance::protocols::mld_snooping::interface::StaticMembershipGroups parent_static_membership_groups [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::group::Source source [0:*]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::group::Source¶
Parents:
nokia_srlinux::Base
Multicast source address list Yang definition can be found here: srl_nokia-mld-snooping.yang:L532
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address source¶
Multicast source address. :rel parent_group: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::Group parent_group [1]¶
Relation to parent container Peer relation: Multicast source address list
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-mld-snooping.yang:L100
- Rel packet:
Trace MLD Packet types
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld_snooping::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::mld_snooping::TraceOptions.trace [0:1]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Trace MLD Packet types
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Trace MLD Packet types Yang definition can be found here: srl_nokia-mld-snooping.yang:L103
- attribute nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet_modifier_t? modifier=null¶
- Rel interface:
List of interfaces to trace :rel parent_trace: Relation to parent container :rel source_mac: List of source mac addresses to trace
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace MLD Packet types
other end:
nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::Trace.packet [0:1]
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet::Interface interface [0:8]¶
Relation to parent container Peer relation: List of interfaces to trace
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet::SourceMac source_mac [0:8]¶
Relation to parent container Peer relation: List of source mac addresses to trace
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet::Interface¶
Parents:
nokia_srlinux::Base
List of interfaces to trace Yang definition can be found here: srl_nokia-mld-snooping.yang:L107
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index> :rel parent_packet: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: List of interfaces to trace
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet::SourceMac¶
Parents:
nokia_srlinux::Base
List of source mac addresses to trace Yang definition can be found here: srl_nokia-mld-snooping.yang:L118
- attribute nokia_srlinux::types::srl_nokia_common::mac_address source_mac¶
- Rel parent_packet:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: List of source mac addresses to trace
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::Instance¶
Parents:
nokia_srlinux::Base
List of OSPF protocol instances associated with this network-instance. Yang definition can be found here: srl_nokia-ospf.yang:L2005
- attribute string? address_family=null¶
The address family that this instance supports. Only valid for OSPFv3.
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to administratively enable or disable the OSPF instance
- attribute nokia_srlinux::network_instance::protocols::ospf::instance_advertise_router_capability_t? advertise_router_capability=null¶
Scope to advertise router-capability.
- attribute string? export_policy=null¶
Apply an export policy to redistribute routes into OSPF
- attribute yang::types::uint8? external_preference=null¶
Configure the route preference associated with OSPF external routes
- attribute nokia_srlinux::network_instance::protocols::ospf::instance_instance_id_t? instance_id=null¶
The OSPF multi instance identity as defined in RFC6549 or RFC5838. Supported values are: For OSPFv2 it is between 0 and 31, default is 0. For OSPFv3 address-family ipv6-unicast it is between 0 and 31, default is 0. For OSPFv3 address-family ipv4-unicast it is between 64 and 95, default is 64.
- attribute nokia_srlinux::types::srl_nokia_ospf_types::ospf_ecmp? max_ecmp_paths=null¶
The maximum number of ECMP next-hops to program into the FIB for every IP prefix
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The name of the OSPF instance
- attribute nokia_srlinux::network_instance::protocols::ospf::instance_preference_t? preference=null¶
Sets the route prefence for OSPF sourced routes
- attribute nokia_srlinux::network_instance::protocols::ospf::instance_reference_bandwidth_t? reference_bandwidth=null¶
Configures the reference bandwidth that provides the basis for interface metrics based on link Bandwidth If the reference bandwidth is defined, then the cost is calculated using the following formula: cost = reference-bandwidth / bandwidth When a large reference-bandwidth value is configured, a metric calculation may result in a value higher than the supported protocol cost value. If this occurs, OSPF automatically reverts to the maximum configurable cost metric.
- attribute nokia_srlinux::types::ietf_yang_types::dotted_quad? router_id=null¶
- attribute string? version=null¶
The version that this ospf instance supports. :rel area: The OSPF areas within which the local system exists :rel asbr: Configure the router as an ASBR (Autonomous System Boundary Router) :rel export_limit: Enter the export-limit context :rel external_db_overflow: :rel graceful_restart: Container for options related to OSPF graceful restart :rel ldp_synchronization: Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled. :rel overload: :rel parent_ospf: Relation to parent container :rel te_database_install: When present, topology and TE information related to this protocol instance is installed into the TE database :rel timers: Enter the timers context :rel trace_options: Enter the trace-options context :rel traffic_engineering: Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces
- relation nokia_srlinux::network_instance::protocols::Ospf parent_ospf [1]¶
Relation to parent container Peer relation: List of OSPF protocol instances associated with this network-instance.
other end:
nokia_srlinux::network_instance::protocols::Ospf.instance [0:3]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Area area [0:*]¶
Relation to parent container Peer relation: The OSPF areas within which the local system exists
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Area.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Asbr asbr [0:1]¶
Relation to parent container Peer relation: Configure the router as an ASBR (Autonomous System Boundary Router)
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Asbr.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::ExportLimit export_limit [0:1]¶
Relation to parent container Peer relation: Enter the export-limit context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::ExportLimit.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::ExternalDbOverflow external_db_overflow [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::ExternalDbOverflow.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::GracefulRestart graceful_restart [0:1]¶
Relation to parent container Peer relation: Container for options related to OSPF graceful restart
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::GracefulRestart.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::LdpSynchronization ldp_synchronization [0:1]¶
Relation to parent container Peer relation: Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled.
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::LdpSynchronization.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Overload overload [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Overload.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::TeDatabaseInstall te_database_install [0:1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::TeDatabaseInstall.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Timers timers [0:1]¶
Relation to parent container Peer relation: Enter the timers context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Timers.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::TraceOptions.parent_instance [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::TrafficEngineering traffic_engineering [0:1]¶
Relation to parent container Peer relation: Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::TrafficEngineering.parent_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::Area¶
Parents:
nokia_srlinux::Base
The OSPF areas within which the local system exists Yang definition can be found here: srl_nokia-ospf.yang:L2028
- attribute bool? advertise_router_capability=null¶
Allow router advertisement capabilities
- attribute nokia_srlinux::types::srl_nokia_ospf_types::ospf_area_identifier area_id¶
the area identifier as a dotted-quad.
- attribute bool? bgp_ls_exclude=null¶
When set to true, topology and TE information related to this area or level should nkot be imported into the TE database in a format that supports export as BGP-LS routes
- attribute bool? blackhole_aggregate=null¶
Enables the creation of a blackhole for generated aggregates
- attribute string? export_policy=null¶
Apply an export policy when summarizing from this area to other areas.. Summary LSAs for prefixes matching the policy will still be in the linkstate database but are not flooded. :rel area_range: Enter the area-range context :rel interface: List of OSPF interfaces :rel nssa: This command creates the context to configure the associated OSPF or OSPF3 area as Not So Stubby Area (NSSA). NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is an NSSA has the capability to flood external routes that it learns throughout its area and via an ABR to the entire OSPF or OSPF3 domain. :rel parent_instance: Relation to parent container :rel stub:
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: The OSPF areas within which the local system exists
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.area [0:*]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::AreaRange area_range [0:*]¶
Relation to parent container Peer relation: Enter the area-range context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::AreaRange.parent_area [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface interface [0:*]¶
Relation to parent container Peer relation: List of OSPF interfaces
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface.parent_area [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa nssa [0:1]¶
Relation to parent container Peer relation: This command creates the context to configure the associated OSPF or OSPF3 area as Not So Stubby Area (NSSA).
NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is an NSSA has the capability to flood external routes that it learns throughout its area and via an ABR to the entire OSPF or OSPF3 domain.
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa.parent_area [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Stub stub [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Stub.parent_area [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::Asbr¶
Parents:
nokia_srlinux::Base
Configure the router as an ASBR (Autonomous System Boundary Router) Yang definition can be found here: srl_nokia-ospf.yang:L1286
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::asbr_trace_path_t? trace_path=null¶
Domain identity :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Configure the router as an ASBR (Autonomous System Boundary Router)
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.asbr [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::ExportLimit¶
Parents:
nokia_srlinux::Base
Enter the export-limit context Yang definition can be found here: srl_nokia-ospf.yang:L1309
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::export_limit_log_percent_t? log_percent=null¶
Export limit at which warning a log message and SNMP notification are sent
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::export_limit_number_t? number=null¶
Maximum number of routes or prefixes to be exported into IGP instance from route table :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enter the export-limit context
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.export_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::ExternalDbOverflow¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L1335
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::external_db_overflow_interval_t? interval=null¶
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::external_db_overflow_limit_t? limit=null¶
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.external_db_overflow [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::GracefulRestart¶
Parents:
nokia_srlinux::Base
Container for options related to OSPF graceful restart Yang definition can be found here: srl_nokia-ospf.yang:L1353
- attribute bool? helper_mode=null¶
Enable or disable the OSPF graceful restart helper function When this leaf is set, the local system supports retaining forwarding information during a neighbor router’s restart.
- attribute bool? strict_lsa_checking=null¶
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container for options related to OSPF graceful restart
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.graceful_restart [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::LdpSynchronization¶
Parents:
nokia_srlinux::Base
Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled. Yang definition can be found here: srl_nokia-ldp.yang:L1470
- attribute bool? end_of_lib=null¶
When set to true, the IGP restores the normal metric for the IGP adjacency when learning from LDP that all label-FEC mappings have been received from the LDP peer, even if there is remaining time on the hold-down-timer. When set to false, the IGP always waits for the full duration of the hold-down-timer to restore the normal metric for the IGP adjacency.
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::ldp_synchronization_hold_down_timer_t? hold_down_timer=null¶
The maximum amount of time that the IGP advertises a maximum metric for an interface, measured from the time that the LDP adjacency is re-established after going down. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enable LDP-IGP synchronization procedures on all P2P interfaces and all LAN interfaces with a single adjancency, except on interfaces where the functionality is explicitly disabled.
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.ldp_synchronization [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::Overload¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L1398
- attribute bool? active=null¶
- attribute bool? overload_include_ext_1=null¶
- attribute bool? overload_include_ext_2=null¶
- attribute bool? overload_include_stub=null¶
- Rel overload_on_boot:
- rel parent_instance:
Relation to parent container :rel rtr_adv_lsa_limit:
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.overload [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::overload::OverloadOnBoot overload_on_boot [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::ospf::instance::overload::RtrAdvLsaLimit rtr_adv_lsa_limit [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::TeDatabaseInstall¶
Parents:
nokia_srlinux::Base
When present, topology and TE information related to this protocol instance is installed into the TE database Yang definition can be found here: srl_nokia-traffic-engineering.yang:L110
- Rel bgp_ls:
When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.te_database_install [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::te_database_install::BgpLs bgp_ls [0:1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::Timers¶
Parents:
nokia_srlinux::Base
Enter the timers context Yang definition can be found here: srl_nokia-ospf.yang:L1056
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers_incremental_spf_wait_t? incremental_spf_wait=null¶
Delay time before an incremental SPF calculation is started
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers_lsa_accumulate_t? lsa_accumulate=null¶
Delay time for accumulating multiple LSAs before advertising them to neighbors
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers_lsa_arrival_t? lsa_arrival=null¶
Minimum delay between receipt of the same LSAs arriving from neighbors
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers_redistribute_delay_t? redistribute_delay=null¶
Hold down timer for external routes that are redistributed in OSPF :rel lsa_generate: Enter the lsa-generate context :rel parent_instance: Relation to parent container :rel spf_wait: Enter the spf-wait context
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enter the timers context
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.timers [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::timers::LsaGenerate lsa_generate [0:1]¶
Relation to parent container Peer relation: Enter the lsa-generate context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::timers::LsaGenerate.parent_timers [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::timers::SpfWait spf_wait [0:1]¶
Relation to parent container Peer relation: Enter the spf-wait context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::timers::SpfWait.parent_timers [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-ospf.yang:L1175
- Rel parent_instance:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::TrafficEngineering¶
Parents:
nokia_srlinux::Base
Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces Yang definition can be found here: srl_nokia-traffic-engineering.yang:L53
- attribute bool? advertisement=null¶
A setting of false means that no TE-related TLVs and subTLVs should be added to LSAs or LSPs originated by this IGP instance. A setting of true means that TE-related TLVs and subTLVs should be added to LSAs or LSPs originated by this IGP instance.
- attribute bool? legacy_link_attribute_advertisement=null¶
The advertisement mode for TE link attributes. A setting of true means that TE properties should be advertised in legacy mode as defined in RFC 8919 and RFC 8920. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::Instance parent_instance [1]¶
Relation to parent container Peer relation: Container with options for controlling the link-state advertisement of the TE properties of this network instance’s TE interfaces
other end:
nokia_srlinux::network_instance::protocols::ospf::Instance.traffic_engineering [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::AreaRange¶
Parents:
nokia_srlinux::Base
Enter the area-range context Yang definition can be found here: srl_nokia-ospf.yang:L1025
- attribute bool? advertise=null¶
Advertise summarized range of addresses to other areas
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::area_range_ip_prefix_mask_t ip_prefix_mask¶
ip-prefix with host bits set to 0 :rel parent_area: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Area parent_area [1]¶
Relation to parent container Peer relation: Enter the area-range context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Area.area_range [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface¶
Parents:
nokia_srlinux::Base
List of OSPF interfaces Yang definition can be found here: srl_nokia-ospf.yang:L2039
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the OSPF
- attribute bool? advertise_router_capability=null¶
Allow router advertisement capabilities
- attribute bool? advertise_subnet=null¶
Advertise point-to-point interfaces as subnet routes
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_dead_interval_t? dead_interval=null¶
Time OSPF waits without receiving Hello packets before declaring a neighbor down
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_hello_interval_t? hello_interval=null¶
Time between OSPF Hellos of this interface
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Router logical interface name.
- attribute nokia_srlinux::types::srl_nokia_ospf_types::interface_type? interface_type=null¶
Interface type to broadcast or point-to-point
- attribute nokia_srlinux::types::srl_nokia_ospf_types::lsa_filter_out? lsa_filter_out=null¶
LSA flooding reduction
- attribute nokia_srlinux::types::srl_nokia_ospf_types::ospf_metric? metric=null¶
Explicit route cost metric that is applied to the interface
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_mtu_t? mtu=null¶
MTU for the OSPF to use on the interface. For OSPFv3 this must be minimum 1280. If the MTU defined here exceeds the actual IP-MTU of the interface, then the IP-MTU of the interface is used.
- attribute bool? passive=null¶
Allow interface to be advertised as an OSPF interface without running the OSPF protocol
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_priority_t? priority=null¶
Priority of the interface to apply in the designated router election on the subnet
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_retransmit_interval_t? retransmit_interval=null¶
Time before OSPF retransmits an unacknowledged LSA to a neighbor
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface_transit_delay_t? transit_delay=null¶
Time required to transmit an LSA on the interface, virtual link, or sham link :rel authentication: Container with authentication options that apply to all peers in this peer-group :rel failure_detection: Options related to methods of detecting BGP session failure :rel ldp_synchronization: Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface. :rel parent_area: Relation to parent container :rel trace_options: Enter the trace-options context
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Area parent_area [1]¶
Relation to parent container Peer relation: List of OSPF interfaces
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Area.interface [0:*]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Container with authentication options that apply to all peers in this peer-group
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::FailureDetection failure_detection [0:1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::LdpSynchronization ldp_synchronization [0:1]¶
Relation to parent container Peer relation: Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface.
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Enter the trace-options context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa¶
Parents:
nokia_srlinux::Base
This command creates the context to configure the associated OSPF or OSPF3 area as Not So Stubby Area (NSSA).
NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is an NSSA has the capability to flood external routes that it learns throughout its area and via an ABR to the entire OSPF or OSPF3 domain. Yang definition can be found here: srl_nokia-ospf.yang:L954
- attribute bool? redistribute_external=null¶
Enables the redistribution of external routes into the Not So Stubby Area (NSSA) or an NSSA area border router (ABR) that is exporting the routes into non-NSSA areas
- attribute bool? summaries=null¶
Enables sending summary (type 3) advertisements into a stub area or Not So Stubby Area (NSSA) on an Area Border Router (ABR) :rel area_range: Enter the area-range context :rel originate_default_route: Enter the originate-default-route context :rel parent_area: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Area parent_area [1]¶
Relation to parent container Peer relation: This command creates the context to configure the associated OSPF or OSPF3 area as Not So Stubby Area (NSSA).
NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is an NSSA has the capability to flood external routes that it learns throughout its area and via an ABR to the entire OSPF or OSPF3 domain.
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Area.nssa [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::AreaRange area_range [0:*]¶
Relation to parent container Peer relation: Enter the area-range context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::AreaRange.parent_nssa [1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::OriginateDefaultRoute originate_default_route [0:1]¶
Relation to parent container Peer relation: Enter the originate-default-route context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::Stub¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L930
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::stub_default_metric_t? default_metric=null¶
Defines the default OSPF metric for associated stub area
- attribute bool? summaries=null¶
Enables sending summary (type 3) advertisements into a stub area or Not So Stubby Area (NSSA) on an Area Border Router (ABR) :rel parent_area: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Area parent_area [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Area.stub [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::Authentication¶
Parents:
nokia_srlinux::Base
Container with authentication options that apply to all peers in this peer-group Yang definition can be found here: srl_nokia-ospf.yang:L576
- attribute string? keychain=null¶
Reference to a keychain. The keychain type must be ospf :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container with authentication options that apply to all peers in this peer-group
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::FailureDetection¶
Parents:
nokia_srlinux::Base
Options related to methods of detecting BGP session failure Yang definition can be found here: srl_nokia-ospf.yang:L594
- attribute bool? enable_bfd=null¶
Enables the use of BFD for livliness detection :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface parent_interface [1]¶
Relation to parent container Peer relation: Options related to methods of detecting BGP session failure
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface.failure_detection [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::LdpSynchronization¶
Parents:
nokia_srlinux::Base
Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface. Yang definition can be found here: srl_nokia-ldp.yang:L1496
- attribute bool? disable=null¶
Disable LDP-IGP synchronization procedures on this interface, even if synchronization is enabled globally
- attribute bool? end_of_lib=null¶
When set to true, the IGP restores the normal metric for the IGP adjacency when learning from LDP that all label-FEC mappings have been received from the LDP peer, even if there is remaining time on the hold-down-timer. When set to false, the IGP always waits for the full duration of the hold-down-timer to restore the normal metric for the IGP adjacency. This overrides the global/instance level setting.
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::ldp_synchronization_hold_down_timer_t? hold_down_timer=null¶
The maximum amount of time that the IGP advertises a maximum metric for an interface, measured from the time that the LDP adjacency is re-established after going down. This overrides the global/instance level setting. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container with configuration options and state that pertains to the operation of LDP-IGP synchronization on this interface.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-ospf.yang:L464
- Rel parent_interface:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface parent_interface [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Interface.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-ospf.yang:L467
- attribute bool? adjacencies=null¶
Enable tracing all BGP events.
- attribute bool? interfaces=null¶
Enable tracing all interface events. :rel packet: Trace OSPF Packet types Only one type can be enabled at a time :rel parent_trace_options: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Trace OSPF Packet types Only one type can be enabled at a time
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Trace OSPF Packet types Only one type can be enabled at a time Yang definition can be found here: srl_nokia-ospf.yang:L360
- attribute bool? detail=null¶
To enable detailed tracing. Includes both received and sent packets.
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::trace::packet_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::trace::packet_type_t? type=null¶
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace OSPF Packet types Only one type can be enabled at a time
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::AreaRange¶
Parents:
nokia_srlinux::Base
Enter the area-range context Yang definition can be found here: srl_nokia-ospf.yang:L982
- attribute bool? advertise=null¶
Advertise summarized range of addresses to other areas
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::area_range_ip_prefix_mask_t ip_prefix_mask¶
ip-prefix with host bits set to 0 :rel parent_nssa: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa parent_nssa [1]¶
Relation to parent container Peer relation: Enter the area-range context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa.area_range [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::OriginateDefaultRoute¶
Parents:
nokia_srlinux::Base
Enter the originate-default-route context Yang definition can be found here: srl_nokia-ospf.yang:L1007
- attribute bool? adjacency_check=null¶
Default route to remove if there is no adjacency
- attribute bool? type_nssa=null¶
Generate a default route using NSSA-LSA type :rel parent_nssa: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa parent_nssa [1]¶
Relation to parent container Peer relation: Enter the originate-default-route context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::area::Nssa.originate_default_route [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::overload::OverloadOnBoot¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L1415
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::overload::overload_on_boot_timeout_t? timeout=null¶
- Rel parent_overload:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Overload parent_overload [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Overload.overload_on_boot [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::overload::RtrAdvLsaLimit¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L1425
- attribute bool? log_only=null¶
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::overload::rtr_adv_lsa_limit_max_lsa_count_t? max_lsa_count=null¶
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::overload::rtr_adv_lsa_limit_overload_timeout_t? overload_timeout=null¶
- attribute nokia_srlinux::types::srl_nokia_common::percentage? warning_threshold=null¶
- Rel parent_overload:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Overload parent_overload [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Overload.rtr_adv_lsa_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::te_database_install::BgpLs¶
Parents:
nokia_srlinux::Base
When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes Yang definition can be found here: srl_nokia-traffic-engineering.yang:L78
- attribute yang::types::uint32? bgp_ls_identifier=null¶
BGP-LS identifier value that is sent in the BGP-LS NLRI
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::te_database_install::bgp_ls_igp_identifier_t? igp_identifier=null¶
Unique identifier of the IGP instance that is sent in the BGP-LS NLRI :rel parent_te_database_install: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::TeDatabaseInstall parent_te_database_install [1]¶
Relation to parent container Peer relation: When present, topology and TE information related to this protocol instance is installed into the TE database in a format that supports export as BGP-LS routes
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::TeDatabaseInstall.bgp_ls [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::timers::LsaGenerate¶
Parents:
nokia_srlinux::Base
Enter the lsa-generate context Yang definition can be found here: srl_nokia-ospf.yang:L1091
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers::lsa_generate_lsa_initial_wait_t? lsa_initial_wait=null¶
First waiting period between link state advertisements LSA originates
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers::lsa_generate_lsa_second_wait_t? lsa_second_wait=null¶
Hold time between the first and second LSA generation
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers::lsa_generate_max_lsa_wait_t? max_lsa_wait=null¶
Maximum time between two consecutive occurrences of an LSA being generated :rel parent_timers: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Timers parent_timers [1]¶
Relation to parent container Peer relation: Enter the lsa-generate context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Timers.lsa_generate [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::timers::SpfWait¶
Parents:
nokia_srlinux::Base
Enter the spf-wait context Yang definition can be found here: srl_nokia-ospf.yang:L1122
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers::spf_wait_spf_initial_wait_t? spf_initial_wait=null¶
Initial SPF calculation delay after a topology change
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers::spf_wait_spf_max_wait_t? spf_max_wait=null¶
Maximum interval between two consecutive SPF calculations
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::timers::spf_wait_spf_second_wait_t? spf_second_wait=null¶
Hold time between the first and second SPF calculation :rel parent_timers: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::Timers parent_timers [1]¶
Relation to parent container Peer relation: Enter the spf-wait context
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::Timers.spf_wait [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-ospf.yang:L1178
- attribute bool? adjacencies=null¶
Enable tracing all BGP events.
- attribute bool? graceful_restart=null¶
Enable tracing all graceful-restart events.
- attribute bool? interfaces=null¶
Enable tracing all interface events.
- attribute bool? misc=null¶
Enable tracing all Config events. :rel lsdb: Trace OSPF LSDB events Only one type can be enabled at a time :rel packet: Trace OSPF Packet types Only one type can be enabled at a time :rel parent_trace_options: Relation to parent container :rel routes: :rel spf:
- relation nokia_srlinux::network_instance::protocols::ospf::instance::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::TraceOptions.trace [0:1]
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Lsdb lsdb [0:1]¶
Relation to parent container Peer relation: Trace OSPF LSDB events Only one type can be enabled at a time
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Trace OSPF Packet types Only one type can be enabled at a time
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Routes routes [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Spf spf [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Lsdb¶
Parents:
nokia_srlinux::Base
Trace OSPF LSDB events Only one type can be enabled at a time Yang definition can be found here: srl_nokia-ospf.yang:L288
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? link_state_id=null¶
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? router_id=null¶
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::lsdb_type_t? type=null¶
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace OSPF LSDB events Only one type can be enabled at a time
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace.lsdb [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Trace OSPF Packet types Only one type can be enabled at a time Yang definition can be found here: srl_nokia-ospf.yang:L360
- attribute bool? detail=null¶
To enable detailed tracing. Includes both received and sent packets.
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::packet_modifier_t? modifier=null¶
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::packet_type_t? type=null¶
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Trace OSPF Packet types Only one type can be enabled at a time
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace.packet [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Routes¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L1166
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::routes_dest_address_t? dest_address=null¶
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace.routes [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::Spf¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ospf.yang:L1157
- attribute nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::spf_dest_address_t? dest_address=null¶
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::Trace.spf [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::Interface¶
Parents:
nokia_srlinux::Base
List of PIM interfaces Yang definition can be found here: srl_nokia-pim.yang:L1911
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the PIM protocol for this interface
- attribute nokia_srlinux::network_instance::protocols::pim::interface_assert_interval_t? assert_interval=null¶
Interval at which the router sends PIM assert messages
- attribute nokia_srlinux::network_instance::protocols::pim::interface_dr_priority_t? dr_priority=null¶
Designated Router (DR) priority value on this interface The value of this object specifies the value sent in PIM Hello messages and used by routers to elect the Designated Router (DR).
- attribute nokia_srlinux::network_instance::protocols::pim::interface_hello_interval_t? hello_interval=null¶
Interval at which the router sends the PIM hello messages
- attribute nokia_srlinux::network_instance::protocols::pim::interface_hello_multiplier_t? hello_multiplier=null¶
Number of hello multiplier to determine the hold time This command configures the multiplier to determine the holdtime for a PIM neighbor on this interface. The hello-multiplier in conjunction with the hello-interval determines the holdtime for a PIM neighbor. The formula used to calculate the hello-holdtime is: (hello-interval * hello-multiplier) / 10.
- attribute bool? improved_assert=null¶
Whether the improved assert processing is enabled.
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all interface_name¶
Reference to a specific subinterface of the form <interface-name>.<subinterface-index>
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? ipv4_admin_state=null¶
Administratively enable or disable PIM IPv4 address family
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? ipv6_admin_state=null¶
Administratively enable or disable PIM IPv6 address family
- attribute nokia_srlinux::network_instance::protocols::pim::interface_maximum_number_groups_t? maximum_number_groups=null¶
Limit the number of accepted (S, G) and (*, G) PIM join states on the interface :rel parent_pim: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: List of PIM interfaces
other end:
nokia_srlinux::network_instance::protocols::Pim.interface [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::Ipv4¶
Parents:
nokia_srlinux::Base
IPv4 specific PIM parameters Yang definition can be found here: srl_nokia-pim.yang:L1899
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable PIM address family :rel parent_pim: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: IPv4 specific PIM parameters
other end:
nokia_srlinux::network_instance::protocols::Pim.ipv4 [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::Ipv6¶
Parents:
nokia_srlinux::Base
IPv6 specific PIM parameters Yang definition can be found here: srl_nokia-pim.yang:L1905
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable PIM address family :rel parent_pim: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: IPv6 specific PIM parameters
other end:
nokia_srlinux::network_instance::protocols::Pim.ipv6 [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::RendezvousPoints¶
Parents:
nokia_srlinux::Base
Define rendezvous points for sparse mode multicast Yang definition can be found here: srl_nokia-pim.yang:L122
- Rel parent_pim:
Relation to parent container
- Rel static:
Static rendezvous point (RP) configuration
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: Define rendezvous points for sparse mode multicast
other end:
nokia_srlinux::network_instance::protocols::Pim.rendezvous_points [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::Static static [0:1]¶
Relation to parent container Peer relation: Static rendezvous point (RP) configuration
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::SptSwitchover¶
Parents:
nokia_srlinux::Base
Define Shortest Path Tree (SPT) switchover threshold for multicast groups Yang definition can be found here: srl_nokia-pim.yang:L189
- Rel group:
Configure SPT switchover threshold for a multicast group prefix
- Rel parent_pim:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: Define Shortest Path Tree (SPT) switchover threshold for multicast groups
other end:
nokia_srlinux::network_instance::protocols::Pim.spt_switchover [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::spt_switchover::Group group [0:*]¶
Relation to parent container Peer relation: Configure SPT switchover threshold for a multicast group prefix
other end:
nokia_srlinux::network_instance::protocols::pim::spt_switchover::Group.parent_spt_switchover [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::Ssm¶
Parents:
nokia_srlinux::Base
Source Specific Multicast (SSM) configuration Yang definition can be found here: srl_nokia-pim.yang:L165
- Rel parent_pim:
Relation to parent container
- Rel ssm_ranges:
List of accepted Source Specific Multicast (SSM) address ranges
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: Source Specific Multicast (SSM) configuration
other end:
nokia_srlinux::network_instance::protocols::Pim.ssm [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::ssm::SsmRanges ssm_ranges [0:1]¶
Relation to parent container Peer relation: List of accepted Source Specific Multicast (SSM) address ranges
other end:
nokia_srlinux::network_instance::protocols::pim::ssm::SsmRanges.parent_ssm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::TraceOptions¶
Parents:
nokia_srlinux::Base
Enter the trace-options context Yang definition can be found here: srl_nokia-pim.yang:L1871
- Rel parent_pim:
Relation to parent container
- Rel trace:
Tracing parameter flags
- relation nokia_srlinux::network_instance::protocols::Pim parent_pim [1]¶
Relation to parent container Peer relation: Enter the trace-options context
other end:
nokia_srlinux::network_instance::protocols::Pim.trace_options [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::Trace trace [0:1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::Trace.parent_trace_options [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::rendezvous_points::Static¶
Parents:
nokia_srlinux::Base
Static rendezvous point (RP) configuration Yang definition can be found here: srl_nokia-pim.yang:L125
- Rel parent_rendezvous_points:
Relation to parent container
- Rel rendezvous_point:
List of static rendezvous points
- relation nokia_srlinux::network_instance::protocols::pim::RendezvousPoints parent_rendezvous_points [1]¶
Relation to parent container Peer relation: Static rendezvous point (RP) configuration
other end:
nokia_srlinux::network_instance::protocols::pim::RendezvousPoints.static [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::RendezvousPoint rendezvous_point [0:*]¶
Relation to parent container Peer relation: List of static rendezvous points
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::RendezvousPoint¶
Parents:
nokia_srlinux::Base
List of static rendezvous points Yang definition can be found here: srl_nokia-pim.yang:L128
- attribute nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::rendezvous_point_address_t address¶
IP address of the rendezvous point :rel group: List of multicast groups for the rendezvous point :rel parent_static: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::Static parent_static [1]¶
Relation to parent container Peer relation: List of static rendezvous points
other end:
nokia_srlinux::network_instance::protocols::pim::rendezvous_points::Static.rendezvous_point [0:*]
- relation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::rendezvous_point::Group group [0:*]¶
Relation to parent container Peer relation: List of multicast groups for the rendezvous point
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::rendezvous_point::Group¶
Parents:
nokia_srlinux::Base
List of multicast groups for the rendezvous point Yang definition can be found here: srl_nokia-pim.yang:L140
- attribute nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::rendezvous_point::group_prefix_t prefix¶
IP prefix of the multicast group :rel parent_rendezvous_point: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::RendezvousPoint parent_rendezvous_point [1]¶
Relation to parent container Peer relation: List of multicast groups for the rendezvous point
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::spt_switchover::Group¶
Parents:
nokia_srlinux::Base
Configure SPT switchover threshold for a multicast group prefix Yang definition can be found here: srl_nokia-pim.yang:L192
- attribute nokia_srlinux::network_instance::protocols::pim::spt_switchover::group_prefix_t prefix¶
IP prefix of the multicast group
- attribute nokia_srlinux::network_instance::protocols::pim::spt_switchover::group_threshold_t? threshold=null¶
SPT switchover threshold in kbps :rel parent_spt_switchover: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::SptSwitchover parent_spt_switchover [1]¶
Relation to parent container Peer relation: Configure SPT switchover threshold for a multicast group prefix
other end:
nokia_srlinux::network_instance::protocols::pim::SptSwitchover.group [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::ssm::SsmRanges¶
Parents:
nokia_srlinux::Base
List of accepted Source Specific Multicast (SSM) address ranges Yang definition can be found here: srl_nokia-pim.yang:L168
- Rel group_range:
Define an accepted SSM group range
- Rel parent_ssm:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::Ssm parent_ssm [1]¶
Relation to parent container Peer relation: List of accepted Source Specific Multicast (SSM) address ranges
other end:
nokia_srlinux::network_instance::protocols::pim::Ssm.ssm_ranges [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::ssm::ssm_ranges::GroupRange group_range [0:*]¶
Relation to parent container Peer relation: Define an accepted SSM group range
other end:
nokia_srlinux::network_instance::protocols::pim::ssm::ssm_ranges::GroupRange.parent_ssm_ranges [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::ssm::ssm_ranges::GroupRange¶
Parents:
nokia_srlinux::Base
Define an accepted SSM group range Yang definition can be found here: srl_nokia-pim.yang:L171
- attribute nokia_srlinux::network_instance::protocols::pim::ssm::ssm_ranges::group_range_ip_prefix_t ip_prefix¶
A multicast IP prefix for SSM group range :rel parent_ssm_ranges: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::ssm::SsmRanges parent_ssm_ranges [1]¶
Relation to parent container Peer relation: Define an accepted SSM group range
other end:
nokia_srlinux::network_instance::protocols::pim::ssm::SsmRanges.group_range [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::Trace¶
Parents:
nokia_srlinux::Base
Tracing parameter flags Yang definition can be found here: srl_nokia-pim.yang:L1874
- Rel events:
Enable the tracing of PIM events
- Rel packet:
Enable the tracing of PIM packets
- Rel parent_trace_options:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::TraceOptions parent_trace_options [1]¶
Relation to parent container Peer relation: Tracing parameter flags
other end:
nokia_srlinux::network_instance::protocols::pim::TraceOptions.trace [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events events [0:1]¶
Relation to parent container Peer relation: Enable the tracing of PIM events
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events.parent_trace [1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet packet [0:1]¶
Relation to parent container Peer relation: Enable the tracing of PIM packets
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet.parent_trace [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events¶
Parents:
nokia_srlinux::Base
Enable the tracing of PIM events Yang definition can be found here: srl_nokia-pim.yang:L1646
- Rel all_event_types:
Enable tracing for all events
- Rel event_types:
Enable tracing for selected event types only
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Enable the tracing of PIM events
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::Trace.events [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::AllEventTypes all_event_types [0:1]¶
Relation to parent container Peer relation: Enable tracing for all events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes event_types [0:1]¶
Relation to parent container Peer relation: Enable tracing for selected event types only
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet¶
Parents:
nokia_srlinux::Base
Enable the tracing of PIM packets Yang definition can be found here: srl_nokia-pim.yang:L1792
- Rel all_packet_types:
Enable tracing for all packet types
- Rel packet_types:
Enable tracing for selected packet types only
- Rel parent_trace:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::Trace parent_trace [1]¶
Relation to parent container Peer relation: Enable the tracing of PIM packets
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::Trace.packet [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::AllPacketTypes all_packet_types [0:1]¶
Relation to parent container Peer relation: Enable tracing for all packet types
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes packet_types [0:1]¶
Relation to parent container Peer relation: Enable tracing for selected packet types only
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::AllEventTypes¶
Parents:
nokia_srlinux::Base
Enable tracing for all events Yang definition can be found here: srl_nokia-pim.yang:L1653
- attribute bool? detail=null¶
Enable detail tracing.
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::all_event_types_group_address_t? group_address=null¶
The IP multicast group address for which to trace events
- attribute string? interface_name=null¶
Enable interface event tracing for a specific interface
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::all_event_types_source_address_t? source_address=null¶
The source address for which to trace events :rel parent_events: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events parent_events [1]¶
Relation to parent container Peer relation: Enable tracing for all events
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events.all_event_types [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes¶
Parents:
nokia_srlinux::Base
Enable tracing for selected event types only Yang definition can be found here: srl_nokia-pim.yang:L1669
- Rel adjacency:
Enable tracing for adjacency events
- Rel assert:
Enable tracing for assert events
- Rel data_exception:
Enable tracing for data events
- Rel database:
Enable tracing for db events
- Rel interface:
Enable tracing for interface events
- Rel join_prune:
Enable tracing for jp events
- Rel messaging:
Enable tracing for msg events
- Rel parent_events:
Relation to parent container
- Rel pim_route_table:
Enable tracing for rtm events
- Rel register:
Enable tracing for register events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events parent_events [1]¶
Relation to parent container Peer relation: Enable tracing for selected event types only
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Events.event_types [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Adjacency adjacency [0:1]¶
Relation to parent container Peer relation: Enable tracing for adjacency events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Assert assert [0:1]¶
Relation to parent container Peer relation: Enable tracing for assert events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::DataException data_exception [0:1]¶
Relation to parent container Peer relation: Enable tracing for data events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Database database [0:1]¶
Relation to parent container Peer relation: Enable tracing for db events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Interface interface [0:1]¶
Relation to parent container Peer relation: Enable tracing for interface events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::JoinPrune join_prune [0:1]¶
Relation to parent container Peer relation: Enable tracing for jp events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Messaging messaging [0:1]¶
Relation to parent container Peer relation: Enable tracing for msg events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::PimRouteTable pim_route_table [0:1]¶
Relation to parent container Peer relation: Enable tracing for rtm events
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Register register [0:1]¶
Relation to parent container Peer relation: Enable tracing for register events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Adjacency¶
Parents:
nokia_srlinux::Base
Enable tracing for adjacency events Yang definition can be found here: srl_nokia-pim.yang:L1672
- Rel parent_event_types:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for adjacency events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Assert¶
Parents:
nokia_srlinux::Base
Enable tracing for assert events Yang definition can be found here: srl_nokia-pim.yang:L1677
- attribute bool? detail=null¶
Enable detail tracing.
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::assert_group_address_t? group_address=null¶
The IP multicast group address for which to trace events
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::assert_source_address_t? source_address=null¶
The source address for which to trace events :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for assert events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::DataException¶
Parents:
nokia_srlinux::Base
Enable tracing for data events Yang definition can be found here: srl_nokia-pim.yang:L1684
- attribute bool? detail=null¶
Enable detail tracing.
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::data_exception_group_address_t? group_address=null¶
The IP multicast group address for which to trace events
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::data_exception_source_address_t? source_address=null¶
The source address for which to trace events :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for data events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Database¶
Parents:
nokia_srlinux::Base
Enable tracing for db events Yang definition can be found here: srl_nokia-pim.yang:L1691
- attribute bool? detail=null¶
Enable detail tracing.
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::database_group_address_t? group_address=null¶
The IP multicast group address for which to trace events
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::database_source_address_t? source_address=null¶
The source address for which to trace events :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for db events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Interface¶
Parents:
nokia_srlinux::Base
Enable tracing for interface events Yang definition can be found here: srl_nokia-pim.yang:L1698
- attribute bool? detail=null¶
Enable detail tracing.
- attribute string? interface_name=null¶
Enable interface event tracing for a specific interface :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for interface events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::JoinPrune¶
Parents:
nokia_srlinux::Base
Enable tracing for jp events Yang definition can be found here: srl_nokia-pim.yang:L1711
- attribute bool? detail=null¶
Enable detail tracing.
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::join_prune_group_address_t? group_address=null¶
The IP multicast group address for which to trace events
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::join_prune_source_address_t? source_address=null¶
The source address for which to trace events :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for jp events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Messaging¶
Parents:
nokia_srlinux::Base
Enable tracing for msg events Yang definition can be found here: srl_nokia-pim.yang:L1718
- Rel parent_event_types:
Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for msg events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::PimRouteTable¶
Parents:
nokia_srlinux::Base
Enable tracing for rtm events Yang definition can be found here: srl_nokia-pim.yang:L1730
- attribute bool? detail=null¶
Enable detail tracing. :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for rtm events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::Register¶
Parents:
nokia_srlinux::Base
Enable tracing for register events Yang definition can be found here: srl_nokia-pim.yang:L1723
- attribute bool? detail=null¶
Enable detail tracing.
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::register_group_address_t? group_address=null¶
The IP multicast group address for which to trace events
- attribute nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::register_source_address_t? source_address=null¶
The source address for which to trace events :rel parent_event_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::EventTypes parent_event_types [1]¶
Relation to parent container Peer relation: Enable tracing for register events
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::AllPacketTypes¶
Parents:
nokia_srlinux::Base
Enable tracing for all packet types Yang definition can be found here: srl_nokia-pim.yang:L1799
- attribute bool? all_interfaces=null¶
Enable packet tracing for all interfaces
- attribute bool? egress=null¶
Enable tracing for sent packets
- attribute bool? ingress=null¶
Enable tracing for received packets
- attribute string? interface_name=null¶
Enable packet tracing for a specific interface
- attribute bool? ipv4=null¶
Enable tracing for PIM ipv4 packets
- attribute bool? ipv6=null¶
Enable tracing for PIM ipv6 packets :rel parent_packet: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: Enable tracing for all packet types
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet.all_packet_types [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes¶
Parents:
nokia_srlinux::Base
Enable tracing for selected packet types only Yang definition can be found here: srl_nokia-pim.yang:L1826
- Rel assert:
Enable tracing for assert packets
- Rel hello:
Enable tracing for hello packets
- Rel join_prune:
Enable tracing for join-prune packets
- Rel parent_packet:
Relation to parent container
- Rel register:
Enable tracing for register packets
- Rel register_stop:
Enable tracing for register-stop packets
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet parent_packet [1]¶
Relation to parent container Peer relation: Enable tracing for selected packet types only
other end:
nokia_srlinux::network_instance::protocols::pim::trace_options::trace::Packet.packet_types [0:1]
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::Assert assert [0:1]¶
Relation to parent container Peer relation: Enable tracing for assert packets
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::Hello hello [0:1]¶
Relation to parent container Peer relation: Enable tracing for hello packets
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::JoinPrune join_prune [0:1]¶
Relation to parent container Peer relation: Enable tracing for join-prune packets
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::Register register [0:1]¶
Relation to parent container Peer relation: Enable tracing for register packets
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::RegisterStop register_stop [0:1]¶
Relation to parent container Peer relation: Enable tracing for register-stop packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::Assert¶
Parents:
nokia_srlinux::Base
Enable tracing for assert packets Yang definition can be found here: srl_nokia-pim.yang:L1857
- attribute bool? all_interfaces=null¶
Enable packet tracing for all interfaces
- attribute bool? egress=null¶
Enable tracing for sent packets
- attribute bool? ingress=null¶
Enable tracing for received packets
- attribute string? interface_name=null¶
Enable packet tracing for a specific interface
- attribute bool? ipv4=null¶
Enable tracing for PIM ipv4 packets
- attribute bool? ipv6=null¶
Enable tracing for PIM ipv6 packets :rel parent_packet_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes parent_packet_types [1]¶
Relation to parent container Peer relation: Enable tracing for assert packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::Hello¶
Parents:
nokia_srlinux::Base
Enable tracing for hello packets Yang definition can be found here: srl_nokia-pim.yang:L1829
- attribute bool? all_interfaces=null¶
Enable packet tracing for all interfaces
- attribute bool? egress=null¶
Enable tracing for sent packets
- attribute bool? ingress=null¶
Enable tracing for received packets
- attribute string? interface_name=null¶
Enable packet tracing for a specific interface
- attribute bool? ipv4=null¶
Enable tracing for PIM ipv4 packets
- attribute bool? ipv6=null¶
Enable tracing for PIM ipv6 packets :rel parent_packet_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes parent_packet_types [1]¶
Relation to parent container Peer relation: Enable tracing for hello packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::JoinPrune¶
Parents:
nokia_srlinux::Base
Enable tracing for join-prune packets Yang definition can be found here: srl_nokia-pim.yang:L1850
- attribute bool? all_interfaces=null¶
Enable packet tracing for all interfaces
- attribute bool? egress=null¶
Enable tracing for sent packets
- attribute bool? ingress=null¶
Enable tracing for received packets
- attribute string? interface_name=null¶
Enable packet tracing for a specific interface
- attribute bool? ipv4=null¶
Enable tracing for PIM ipv4 packets
- attribute bool? ipv6=null¶
Enable tracing for PIM ipv6 packets :rel parent_packet_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes parent_packet_types [1]¶
Relation to parent container Peer relation: Enable tracing for join-prune packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::Register¶
Parents:
nokia_srlinux::Base
Enable tracing for register packets Yang definition can be found here: srl_nokia-pim.yang:L1836
- attribute bool? all_interfaces=null¶
Enable packet tracing for all interfaces
- attribute bool? egress=null¶
Enable tracing for sent packets
- attribute bool? ingress=null¶
Enable tracing for received packets
- attribute string? interface_name=null¶
Enable packet tracing for a specific interface
- attribute bool? ipv4=null¶
Enable tracing for PIM ipv4 packets
- attribute bool? ipv6=null¶
Enable tracing for PIM ipv6 packets :rel parent_packet_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes parent_packet_types [1]¶
Relation to parent container Peer relation: Enable tracing for register packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::RegisterStop¶
Parents:
nokia_srlinux::Base
Enable tracing for register-stop packets Yang definition can be found here: srl_nokia-pim.yang:L1843
- attribute bool? all_interfaces=null¶
Enable packet tracing for all interfaces
- attribute bool? egress=null¶
Enable tracing for sent packets
- attribute bool? ingress=null¶
Enable tracing for received packets
- attribute string? interface_name=null¶
Enable packet tracing for a specific interface
- attribute bool? ipv4=null¶
Enable tracing for PIM ipv4 packets
- attribute bool? ipv6=null¶
Enable tracing for PIM ipv6 packets :rel parent_packet_types: Relation to parent container
- relation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::PacketTypes parent_packet_types [1]¶
Relation to parent container Peer relation: Enable tracing for register-stop packets
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::segment_routing::Mpls¶
Parents:
nokia_srlinux::Base
Adding this container activates datapath support for SR-MPLS Yang definition can be found here: srl_nokia-segment-routing.yang:L120
- Rel global_block:
Container with SRGB configuration that is applicable to all IGP protocol instances
- Rel local_prefix_sid:
List of configured protocol-independent prefix SIDs associated with the network-instance
- Rel parent_segment_routing:
Relation to parent container
- relation nokia_srlinux::network_instance::SegmentRouting parent_segment_routing [1]¶
Relation to parent container Peer relation: Adding this container activates datapath support for SR-MPLS
other end:
nokia_srlinux::network_instance::SegmentRouting.mpls [0:1]
- relation nokia_srlinux::network_instance::segment_routing::mpls::GlobalBlock global_block [0:1]¶
Relation to parent container Peer relation: Container with SRGB configuration that is applicable to all IGP protocol instances
other end:
nokia_srlinux::network_instance::segment_routing::mpls::GlobalBlock.parent_mpls [1]
- relation nokia_srlinux::network_instance::segment_routing::mpls::LocalPrefixSid local_prefix_sid [0:4]¶
Relation to parent container Peer relation: List of configured protocol-independent prefix SIDs associated with the network-instance
other end:
nokia_srlinux::network_instance::segment_routing::mpls::LocalPrefixSid.parent_mpls [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::segment_routing::mpls::GlobalBlock¶
Parents:
nokia_srlinux::Base
Container with SRGB configuration that is applicable to all IGP protocol instances Yang definition can be found here: srl_nokia-segment-routing.yang:L128
- attribute string? label_range=null¶
Reference to a static label range :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Container with SRGB configuration that is applicable to all IGP protocol instances
other end:
nokia_srlinux::network_instance::segment_routing::Mpls.global_block [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::segment_routing::mpls::LocalPrefixSid¶
Parents:
nokia_srlinux::Base
List of configured protocol-independent prefix SIDs associated with the network-instance Yang definition can be found here: srl_nokia-segment-routing.yang:L154
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all? interface=null¶
Reference to the subinterface that owns the prefix(es) to be advertised. If ipv4-label-index is assigned a value then the primary IPv4 address of the referenced subinterface is advertised as a prefix SID. If ipv6-label-index is assigned a value then the primary IPv6 address of the referenced subinterface is advertised as a prefix SID.
- attribute nokia_srlinux::network_instance::segment_routing::mpls::local_prefix_sid_ipv4_label_index_t? ipv4_label_index=null¶
Label index to add to SRGB base.
- attribute nokia_srlinux::network_instance::segment_routing::mpls::local_prefix_sid_ipv6_label_index_t? ipv6_label_index=null¶
Label index to add to SRGB base.
- attribute bool? node_sid=null¶
If set, the prefix SID(s) identity the router as a whole.
- attribute nokia_srlinux::network_instance::segment_routing::mpls::local_prefix_sid_prefix_sid_index_t prefix_sid_index¶
An index to enumerate the different prefix sids :rel parent_mpls: Relation to parent container
- relation nokia_srlinux::network_instance::segment_routing::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: List of configured protocol-independent prefix SIDs associated with the network-instance
other end:
nokia_srlinux::network_instance::segment_routing::Mpls.local_prefix_sid [0:4]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::static_routes::Route¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-static-routes.yang:L47
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to disable the static route.
- attribute yang::types::uint32? metric=null¶
IGP metric of the static route.
- attribute string? next_hop_group=null¶
- attribute nokia_srlinux::network_instance::static_routes::route_preference_t? preference=null¶
Route preference with lower values indicating a higher degree of preference.
- attribute nokia_srlinux::network_instance::static_routes::route_prefix_t prefix¶
- Rel parent_static_routes:
Relation to parent container
- relation nokia_srlinux::network_instance::StaticRoutes parent_static_routes [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::StaticRoutes.route [0:16384]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::AdminGroups¶
Parents:
nokia_srlinux::Base
Container for configuring admin groups Yang definition can be found here: srl_nokia-traffic-engineering.yang:L152
- Rel group:
List of admin groups defined for this network instance.
- Rel parent_traffic_engineering:
Relation to parent container
- relation nokia_srlinux::network_instance::TrafficEngineering parent_traffic_engineering [1]¶
Relation to parent container Peer relation: Container for configuring admin groups
other end:
nokia_srlinux::network_instance::TrafficEngineering.admin_groups [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::admin_groups::Group group [0:*]¶
Relation to parent container Peer relation: List of admin groups defined for this network instance.
other end:
nokia_srlinux::network_instance::traffic_engineering::admin_groups::Group.parent_admin_groups [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::Interface¶
Parents:
nokia_srlinux::Base
List of routed subinterfaces that have associated TE information Yang definition can be found here: srl_nokia-traffic-engineering.yang:L196
- attribute string[]? admin_group=null¶
The list of admin-groups generically associated with the interface (not application specific)
- attribute nokia_srlinux::types::srl_nokia_network_instance::network_instance_subintf_name interface_name¶
Name of a subinterface
- attribute string[]? srlg_membership=null¶
The list of srlgs generically associated with the interface (not application specific)
- attribute nokia_srlinux::network_instance::traffic_engineering::interface_te_metric_t? te_metric=null¶
The TE metric associated with the interface (not application specific) :rel delay: Container with options for assigning a TE delay value to the interface (not application specific) :rel interface_ref: Reference to a subinterface :rel parent_traffic_engineering: Relation to parent container
- relation nokia_srlinux::network_instance::TrafficEngineering parent_traffic_engineering [1]¶
Relation to parent container Peer relation: List of routed subinterfaces that have associated TE information
other end:
nokia_srlinux::network_instance::TrafficEngineering.interface [0:*]
- relation nokia_srlinux::network_instance::traffic_engineering::interface::Delay delay [0:1]¶
Relation to parent container Peer relation: Container with options for assigning a TE delay value to the interface (not application specific)
other end:
nokia_srlinux::network_instance::traffic_engineering::interface::Delay.parent_interface [1]
- relation nokia_srlinux::network_instance::traffic_engineering::interface::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::traffic_engineering::interface::InterfaceRef.parent_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::Pcep¶
Parents:
nokia_srlinux::Base
Top-level configuration and operational state for Path Computation Element Protocol (PCEP) Yang definition can be found here: srl_nokia-pcep.yang:L1247
- Rel parent_traffic_engineering:
Relation to parent container
- Rel pcc:
Configure Path Computation Client (PCC) parameters
- relation nokia_srlinux::network_instance::TrafficEngineering parent_traffic_engineering [1]¶
Relation to parent container Peer relation: Top-level configuration and operational state for Path Computation Element Protocol (PCEP)
other end:
nokia_srlinux::network_instance::TrafficEngineering.pcep [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc pcc [0:1]¶
Relation to parent container Peer relation: Configure Path Computation Client (PCC) parameters
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc.parent_pcep [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Parents:
nokia_srlinux::Base
Container for configuring SRLGs Yang definition can be found here: srl_nokia-traffic-engineering.yang:L176
- Rel group:
List of shared risk link groups defined for this network instance.
- Rel parent_traffic_engineering:
Relation to parent container
Relation to parent container Peer relation: Container for configuring SRLGs
other end:
nokia_srlinux::network_instance::TrafficEngineering.shared_risk_link_groups [0:1]
Relation to parent container Peer relation: List of shared risk link groups defined for this network instance.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::admin_groups::Group¶
Parents:
nokia_srlinux::Base
List of admin groups defined for this network instance. Yang definition can be found here: srl_nokia-traffic-engineering.yang:L155
- attribute nokia_srlinux::network_instance::traffic_engineering::admin_groups::group_bit_position_t? bit_position=null¶
The bit-position value for the admin-group. The value for the admin group is an integer that represents one of the bit positions in the admin-group bitmask.
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The name of the admin group :rel parent_admin_groups: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::AdminGroups parent_admin_groups [1]¶
Relation to parent container Peer relation: List of admin groups defined for this network instance.
other end:
nokia_srlinux::network_instance::traffic_engineering::AdminGroups.group [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::Delay¶
Parents:
nokia_srlinux::Base
Container with options for assigning a TE delay value to the interface (not application specific) Yang definition can be found here: srl_nokia-traffic-engineering.yang:L244
- attribute yang::types::uint32? static=null¶
A statically configured delay value :rel dynamic: :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::Interface parent_interface [1]¶
Relation to parent container Peer relation: Container with options for assigning a TE delay value to the interface (not application specific)
other end:
nokia_srlinux::network_instance::traffic_engineering::Interface.delay [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::Dynamic dynamic [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering::interface::delay::Dynamic.parent_delay [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::InterfaceRef¶
Parents:
nokia_srlinux::Base
Reference to a subinterface Yang definition can be found here: srl_nokia-traffic-engineering.yang:L208
- attribute string? interface=null¶
Reference to a base interface, for example a port or LAG
- attribute nokia_srlinux::network_instance::traffic_engineering::interface::interface_ref_subinterface_t? subinterface=null¶
Reference to a subinterface This requires the base interface to be specified using the interface leaf in this container. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::Interface parent_interface [1]¶
Relation to parent container Peer relation: Reference to a subinterface
other end:
nokia_srlinux::network_instance::traffic_engineering::Interface.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::delay::Dynamic¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-link-measurement.yang:L440
- Rel link_measurement:
The link-measurement dynamic measurement configuration for the interface
- Rel parent_delay:
Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::interface::Delay parent_delay [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering::interface::Delay.dynamic [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::LinkMeasurement link_measurement [0:1]¶
Relation to parent container Peer relation: The link-measurement dynamic measurement configuration for the interface
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::LinkMeasurement¶
Parents:
nokia_srlinux::Base
The link-measurement dynamic measurement configuration for the interface Yang definition can be found here: srl_nokia-link-measurement.yang:L441
- attribute string? measurement_template=null¶
The link measurement template assigned to the interface :rel parent_dynamic: Relation to parent container :rel stamp: The STAMP IP protocol configuration
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::Dynamic parent_dynamic [1]¶
Relation to parent container Peer relation: The link-measurement dynamic measurement configuration for the interface
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::Stamp stamp [0:1]¶
Relation to parent container Peer relation: The STAMP IP protocol configuration
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::Stamp¶
Parents:
nokia_srlinux::Base
The STAMP IP protocol configuration Yang definition can be found here: srl_nokia-link-measurement.yang:L461
- Rel ipv4:
The ipv4 address and administrative configuration
- Rel ipv6:
The ipv6 address and administrative configuration
- Rel parent_link_measurement:
Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::LinkMeasurement parent_link_measurement [1]¶
Relation to parent container Peer relation: The STAMP IP protocol configuration
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::stamp::Ipv4 ipv4 [0:1]¶
Relation to parent container Peer relation: The ipv4 address and administrative configuration
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::stamp::Ipv6 ipv6 [0:1]¶
Relation to parent container Peer relation: The ipv6 address and administrative configuration
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::stamp::Ipv4¶
Parents:
nokia_srlinux::Base
The ipv4 address and administrative configuration Yang definition can be found here: srl_nokia-link-measurement.yang:L464
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of IPv4 STAMP packets
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero? destination_ip=null¶
STAMP measurement packet destination IPv4 address When the destination address is not specified the system resolves the peer address when the prefix-length of the primary local interface has a length of 30 or 31. When the destination address is not specified and the prefix length is shorter than 30 the peer address cannot be determined and the invalid destination address will result.
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address_excluding_all_zero? source_ip=null¶
STAMP measurement packets source IPv4 address The primary local interface address will be used when this leaf is not configured. :rel parent_stamp: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: The ipv4 address and administrative configuration
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::stamp::Ipv6¶
Parents:
nokia_srlinux::Base
The ipv6 address and administrative configuration Yang definition can be found here: srl_nokia-link-measurement.yang:L494
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of IPv6 STAMP packets
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero? destination_ip=null¶
STAMP measurement packet destination IPv6 address When the destination address is not specified the system relies on ipv6-destination-discovery to resolves the address. If ipv6-destination-discovery is disabled or the discovery fails an invalid destination address will result.
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address_excluding_all_zero? source_ip=null¶
STAMP measurement packets source IPv6 address The link-local interface address will be used when this leaf is not configured. :rel parent_stamp: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: The ipv6 address and administrative configuration
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc¶
Parents:
nokia_srlinux::Base
Configure Path Computation Client (PCC) parameters Yang definition can be found here: srl_nokia-pcep.yang:L1227
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_dead_timer_t? dead_timer=null¶
Configure dead timer
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_keepalive_t? keepalive=null¶
Configure keepalive
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_max_pce_init_lsps_t? max_pce_init_lsps=null¶
Configure maximum PCE initiated LSPs
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_redelegation_timer_t? redelegation_timer=null¶
Configure redelegation-timer
- attribute bool? report_path_constraints=null¶
Specify whether to enable/disable path constraints in PCC report
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc_unknown_message_rate_t? unknown_message_rate=null¶
Configure unknown message rate :rel parent_pcep: Relation to parent container :rel pce_associations: Configure associations to be used with PCE :rel peer: Configure peer parameters for PCC :rel state_timer: Holds state timer information
- relation nokia_srlinux::network_instance::traffic_engineering::Pcep parent_pcep [1]¶
Relation to parent container Peer relation: Configure Path Computation Client (PCC) parameters
other end:
nokia_srlinux::network_instance::traffic_engineering::Pcep.pcc [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations pce_associations [0:1]¶
Relation to parent container Peer relation: Configure associations to be used with PCE
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations.parent_pcc [1]
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::Peer peer [0:2]¶
Relation to parent container Peer relation: Configure peer parameters for PCC
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::Peer.parent_pcc [1]
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::StateTimer state_timer [0:1]¶
Relation to parent container Peer relation: Holds state timer information
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::StateTimer.parent_pcc [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations¶
Parents:
nokia_srlinux::Base
Configure associations to be used with PCE Yang definition can be found here: srl_nokia-pcep.yang:L1066
- Rel diversity:
List of diversity association parameters
- Rel parent_pcc:
Relation to parent container
- Rel policy:
List of policies for PCC
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc parent_pcc [1]¶
Relation to parent container Peer relation: Configure associations to be used with PCE
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc.pce_associations [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::Diversity diversity [0:*]¶
Relation to parent container Peer relation: List of diversity association parameters
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::Policy policy [0:*]¶
Relation to parent container Peer relation: List of policies for PCC
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::Peer¶
Parents:
nokia_srlinux::Base
Configure peer parameters for PCC Yang definition can be found here: srl_nokia-pcep.yang:L1232
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of PCC peer
- attribute string? authentication_keychain=null¶
Specifies the keychain that will be used to sign and/or authenticate the PCEP protocol stream.
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_ip_address_t ip_address¶
The address of the PCE peer
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_local_address_t? local_address=null¶
Configure local IP
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_preference_t? preference=null¶
The preference value of this peer If a higher preference PCE is unavailable or not connected, the PCE with the next preference is used.
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_route_preference_t? route_preference=null¶
Route preference inband / outband
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_tls_client_profile_t? tls_client_profile=null¶
Specifies the profile name used by PCC.
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::peer_tls_wait_timer_t? tls_wait_timer=null¶
Configure tls-wait-timer :rel parent_pcc: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc parent_pcc [1]¶
Relation to parent container Peer relation: Configure peer parameters for PCC
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc.peer [0:2]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::StateTimer¶
Parents:
nokia_srlinux::Base
Holds state timer information Yang definition can be found here: srl_nokia-pcep.yang:L1031
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::state_timer_timer_t? timer=null¶
Configure state-timer
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::state_timer_timer_action_t? timer_action=null¶
State timer action remove/none :rel parent_pcc: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc parent_pcc [1]¶
Relation to parent container Peer relation: Holds state timer information
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::Pcc.state_timer [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::Diversity¶
Parents:
nokia_srlinux::Base
List of diversity association parameters Yang definition can be found here: srl_nokia-pcep.yang:L1069
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_association_id_t? association_id=null¶
Association-id for the diversity associaiton group
- attribute nokia_srlinux::types::srl_nokia_common::name association_name¶
Association name
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_association_source_t? association_source=null¶
Associaiton source for the association
- attribute bool? disjointness_reference=null¶
Refers to shortest path or not
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_disjointness_type_t? disjointness_type=null¶
Refers to strict or loose path
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::diversity_diversity_type_t? diversity_type=null¶
Refers to the choice of path node / link / srlg-node / srlg-link :rel parent_pce_associations: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations parent_pce_associations [1]¶
Relation to parent container Peer relation: List of diversity association parameters
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations.diversity [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::Policy¶
Parents:
nokia_srlinux::Base
List of policies for PCC Yang definition can be found here: srl_nokia-pcep.yang:L1076
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::policy_association_id_t? association_id=null¶
Association-id for the diversity associaiton group
- attribute nokia_srlinux::types::srl_nokia_common::name association_name¶
Association name
- attribute nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::policy_association_source_t? association_source=null¶
Associaiton Source for the association :rel parent_pce_associations: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations parent_pce_associations [1]¶
Relation to parent container Peer relation: List of policies for PCC
other end:
nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::PceAssociations.policy [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Parents:
nokia_srlinux::Base
List of shared risk link groups defined for this network instance. Yang definition can be found here: srl_nokia-traffic-engineering.yang:L179
The name of the shared risk link group
Group ID for the SRLG :rel parent_shared_risk_link_groups: Relation to parent container
Relation to parent container Peer relation: List of shared risk link groups defined for this network instance.
other end:
nokia_srlinux::network_instance::traffic_engineering::SharedRiskLinkGroups.group [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::BindingSid¶
Parents:
nokia_srlinux::Base
Configuration and state related to the label block(s) used for the binding SIDs associated with TE policies Yang definition can be found here: srl_nokia-te-policies.yang:L382
- attribute string? static_label_block=null¶
Reference to a static label range :rel parent_traffic_engineering_policies: Relation to parent container
- relation nokia_srlinux::network_instance::TrafficEngineeringPolicies parent_traffic_engineering_policies [1]¶
Relation to parent container Peer relation: Configuration and state related to the label block(s) used for the binding SIDs associated with TE policies
other end:
nokia_srlinux::network_instance::TrafficEngineeringPolicies.binding_sid [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::ExplicitPaths¶
Parents:
nokia_srlinux::Base
Named paths used to specify SR policy segment lists Yang definition can be found here: srl_nokia-te-policies.yang:L411
- Rel parent_traffic_engineering_policies:
Relation to parent container
- Rel path:
- relation nokia_srlinux::network_instance::TrafficEngineeringPolicies parent_traffic_engineering_policies [1]¶
Relation to parent container Peer relation: Named paths used to specify SR policy segment lists
other end:
nokia_srlinux::network_instance::TrafficEngineeringPolicies.explicit_paths [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::Path path [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::Policy¶
Parents:
nokia_srlinux::Base
List of traffic engineering policies Yang definition can be found here: srl_nokia-te-policies.yang:L493
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable/disable the traffic engineering policy
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_candidate_path_preference_t? candidate_path_preference=null¶
One sr-mpls-colored TE policy is considered better than another sr-mpls-colored for thesame (color, endpoint) if it has a higher preference than the other path.
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_color_t? color=null¶
Color associated with the sr-mpls-colored TE policy.
- attribute yang::types::uint32? distinguisher=null¶
Distinguisher value to make different sr-mpls-colored policies unique
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_endpoint_t? endpoint=null¶
Destination of the TE policy
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_head_end_t? head_end=null¶
Targeted head end address for an sr-mpls-colored policy
- attribute string? maintenance_policy=null¶
The maintenance policy to use with the TE policy
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_metric_t? metric=null¶
Metric for the TE Policy
- attribute nokia_srlinux::types::srl_nokia_common::name policy_name¶
The name of the traffic engineering policy
- attribute nokia_srlinux::types::srl_nokia_te_policies::te_policy_type? policy_type=null¶
Specifies the TE policy type TE Policy can be of type sr-mpls-colored where label based segment-list or segment-lists constitute a candidate path and color with endpoint is used to configure a path. TE Policy can be of type uncolored in which case a single primary LSP can be backed by one or more secondary LSPs
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_re_optimization_timer_t? re_optimization_timer=null¶
Re-optimizaion timer for the TE policy
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy_retry_timer_t? retry_timer=null¶
Time between TE policy re-establishment attempts after failure :rel application_bindings: Configurable bindings to the TE Policy :rel binding_sid: Identifier that opaquely represents the Uncolored Traffic Engineering Policy (a.k.a. SR-TE LSP) to upstream routers :rel egress_statistics: Enable the egress-statistics context :rel entropy_label: Options for configuring control and data plane aspects of entropy label :rel ingress_statistics: Enable the ingress-statistics context :rel parent_traffic_engineering_policies: Relation to parent container :rel segment_list:
- relation nokia_srlinux::network_instance::TrafficEngineeringPolicies parent_traffic_engineering_policies [1]¶
Relation to parent container Peer relation: List of traffic engineering policies
other end:
nokia_srlinux::network_instance::TrafficEngineeringPolicies.policy [0:*]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::ApplicationBindings application_bindings [0:1]¶
Relation to parent container Peer relation: Configurable bindings to the TE Policy
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::BindingSid binding_sid [0:1]¶
Relation to parent container Peer relation: Identifier that opaquely represents the Uncolored Traffic Engineering Policy (a.k.a. SR-TE LSP) to upstream routers
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::policy::BindingSid.parent_policy [1]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::EgressStatistics egress_statistics [0:1]¶
Relation to parent container Peer relation: Enable the egress-statistics context
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::EntropyLabel entropy_label [0:1]¶
Relation to parent container Peer relation: Options for configuring control and data plane aspects of entropy label
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::IngressStatistics ingress_statistics [0:1]¶
Relation to parent container Peer relation: Enable the ingress-statistics context
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList segment_list [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList.parent_policy [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::Path¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-te-policies.yang:L414
- attribute nokia_srlinux::types::srl_nokia_common::name explicit_path_name¶
A unique name to identify the explicit path :rel hop: :rel parent_explicit_paths: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::ExplicitPaths parent_explicit_paths [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::ExplicitPaths.path [0:*]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::Hop hop [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::Hop¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-te-policies.yang:L421
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? mpls_label=null¶
An MPLS label value representing a segment routing instruction
- attribute yang::types::uint8 x_index¶
The index number of the hop. Hops are processed in ascending sequence. :rel ip: :rel parent_path: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::Path parent_path [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::Path.hop [0:*]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::Ip ip [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::Ip¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-te-policies.yang:L428
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::ip_hop_type_t? hop_type=null¶
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::ip_ip_address_t? ip_address=null¶
An IPv4 or IPv6 address that is a hop to be visited on the way to the destination :rel parent_hop: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::Hop parent_hop [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::Hop.ip [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::ApplicationBindings¶
Parents:
nokia_srlinux::Base
Configurable bindings to the TE Policy Yang definition can be found here: srl_nokia-te-policies.yang:L645
- attribute bool? bgp_labeled_unicast=null¶
When true, the TE policy is available for next-hop resolution of BGP labeled-unicast routes
- attribute bool? bgp_unicast=null¶
When true, the TE policy is available for next-hop resolution of BGP unlabeled routes
- attribute bool? ip_vrf=null¶
When true, the TE policy is available for next-hop resolution of VPN-IP routes in an ip-vrf network-instance :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation: Configurable bindings to the TE Policy
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::Policy.application_bindings [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::BindingSid¶
Parents:
nokia_srlinux::Base
Identifier that opaquely represents the Uncolored Traffic Engineering Policy (a.k.a. SR-TE LSP) to upstream routers Yang definition can be found here: srl_nokia-te-policies.yang:L516
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? mpls_label=null¶
MPLS label that represents the Uncolored Traffic Engineering Policy to upstream routers :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation: Identifier that opaquely represents the Uncolored Traffic Engineering Policy (a.k.a. SR-TE LSP) to upstream routers
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::Policy.binding_sid [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::EgressStatistics¶
Parents:
nokia_srlinux::Base
Enable the egress-statistics context Yang definition can be found here: srl_nokia-te-policies.yang:L620
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the traffic statistics :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation: Enable the egress-statistics context
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::Policy.egress_statistics [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::EntropyLabel¶
Parents:
nokia_srlinux::Base
Options for configuring control and data plane aspects of entropy label Yang definition can be found here: srl_nokia-te-policies.yang:L472
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::entropy_label_transmit_t? transmit=null¶
Specify conditions for adding ELI/EL under the stack of labels comprising the segment-list :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation: Options for configuring control and data plane aspects of entropy label
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::Policy.entropy_label [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::IngressStatistics¶
Parents:
nokia_srlinux::Base
Enable the ingress-statistics context Yang definition can be found here: srl_nokia-te-policies.yang:L610
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the traffic statistics :rel parent_policy: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation: Enable the ingress-statistics context
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::Policy.ingress_statistics [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-te-policies.yang:L693
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable a segment list
- attribute string? explicit_path=null¶
- attribute bool? pce_control=null¶
Set to true for a PCE controlled segment-list
- attribute bool? pce_report=null¶
seto to true to enable reporting of the segment-list to the PCE
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list_segment_list_index_t segment_list_index¶
Index to enumerate the different segment lists of a TE policy.
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list_segment_list_preference_t? segment_list_preference=null¶
Preference value of this segment-list For an sr-mpls-uncolored TE policy one standby segment list is preferred over another if it has a lower preference value. The implicit default value is 100.
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list_segment_list_type_t? segment_list_type=null¶
Segment-list type: primary, standby or secondary Standby is programmed in datapath, consumes resources and is ready for a failover any time. Secondary is programmed upon failure of the previous active
- attribute yang::types::uint32? weight=null¶
Weight of this segment list, used for weighted ECMP between segment lists :rel dynamic: Configuration and state for dynamic segment lists :rel parent_policy: Relation to parent container :rel priority: Configure setup and hold priorities to be conveyed to the PCE for preemption purposes
- relation nokia_srlinux::network_instance::traffic_engineering_policies::Policy parent_policy [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::Policy.segment_list [0:*]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::Dynamic dynamic [0:1]¶
Relation to parent container Peer relation: Configuration and state for dynamic segment lists
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::Priority priority [0:1]¶
Relation to parent container Peer relation: Configure setup and hold priorities to be conveyed to the PCE for preemption purposes
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::Dynamic¶
Parents:
nokia_srlinux::Base
Configuration and state for dynamic segment lists Yang definition can be found here: srl_nokia-te-policies.yang:L790
- attribute nokia_srlinux::types::srl_nokia_te_policies::dynamic_segment_path_computation_type? path_algorithm=null¶
Path computation method :rel parent_segment_list: Relation to parent container :rel te_constraints:
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList parent_segment_list [1]¶
Relation to parent container Peer relation: Configuration and state for dynamic segment lists
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList.dynamic [0:1]
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::TeConstraints te_constraints [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::Priority¶
Parents:
nokia_srlinux::Base
Configure setup and hold priorities to be conveyed to the PCE for preemption purposes Yang definition can be found here: srl_nokia-te-policies.yang:L759
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::priority_hold_priority_t? hold_priority=null¶
Hold priority of a TE policy in relation to preemption action
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::priority_setup_priority_t? setup_priority=null¶
Setup priority of a TE policy in relation to preemption action :rel parent_segment_list: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList parent_segment_list [1]¶
Relation to parent container Peer relation: Configure setup and hold priorities to be conveyed to the PCE for preemption purposes
other end:
nokia_srlinux::network_instance::traffic_engineering_policies::policy::SegmentList.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::TeConstraints¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-te-policies.yang:L800
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_exclude_hop_t[]? exclude_hop=null¶
Excluded IP addresses from path computation
- attribute string[]? exclude_srlg=null¶
Excluded SRLGs during path computation
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_hop_limit_t? hop_limit=null¶
The maximum number of hops for the segment-list
- attribute bool? label_stack_reduction=null¶
Set to true to enable label stack reduction for local CSPF computed segment-lists
- attribute yang::types::uint32? latency_metric_limit=null¶
The maximum latency for the segment-list
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_local_sr_protection_t? local_sr_protection=null¶
Protection offered for local CSPF computed segment-lists
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints_metric_type_t? metric_type=null¶
Metric type used for segment-list computation
- attribute bool? secondary_srlg=null¶
Set to to true to consider SRLG for secondary and standby segment list of uncolored type :rel parent_dynamic: Relation to parent container :rel segment_depth: Configuration for the maximum number of SIDs/segments
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::Dynamic parent_dynamic [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::SegmentDepth segment_depth [0:1]¶
Relation to parent container Peer relation: Configuration for the maximum number of SIDs/segments
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::SegmentDepth¶
Parents:
nokia_srlinux::Base
Configuration for the maximum number of SIDs/segments Yang definition can be found here: srl_nokia-te-policies.yang:L828
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::segment_depth_additional_frr_segment_limit_t? additional_frr_segment_limit=null¶
The maximum number of additional segments used for FRR
- attribute nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::segment_depth_segment_limit_t? segment_limit=null¶
The maximum number of segments in the segment-list :rel parent_te_constraints: Relation to parent container
- relation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::TeConstraints parent_te_constraints [1]¶
Relation to parent container Peer relation: Configuration for the maximum number of SIDs/segments
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::Ethcfm¶
Parents:
nokia_srlinux::Base
OAM configuration and operational data for the management of Ethernet (ETH-CFM) Yang definition can be found here: srl_nokia-ethcfm.yang:L1014
- Rel domain:
Maintenance Domain list containing CFM Domain configuration elements
The Maintenance Domain includes all the configuration elements to define the individual domain behavior and scope of the CFM boundary. These are common elements that will be part of the related Maintenance Associations configured within the domain. :rel parent_oam: Relation to parent container :rel sender_id: Enter the sender-id context
- relation nokia_srlinux::Oam parent_oam [1]¶
Relation to parent container Peer relation: OAM configuration and operational data for the management of Ethernet (ETH-CFM)
other end:
nokia_srlinux::Oam.ethcfm [0:1]
- relation nokia_srlinux::oam::ethcfm::Domain domain [0:4000]¶
Relation to parent container Peer relation: Maintenance Domain list containing CFM Domain configuration elements
The Maintenance Domain includes all the configuration elements to define the individual domain behavior and scope of the CFM boundary. These are common elements that will be part of the related Maintenance Associations configured within the domain.
other end:
nokia_srlinux::oam::ethcfm::Domain.parent_ethcfm [1]
- relation nokia_srlinux::oam::ethcfm::SenderId sender_id [0:1]¶
Relation to parent container Peer relation: Enter the sender-id context
other end:
nokia_srlinux::oam::ethcfm::SenderId.parent_ethcfm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::setupEthcfmYangContainer
constrainttrue
- entity nokia_srlinux::oam::Ippm¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ippm-source-udp-pool.yang:L65
- Rel parent_oam:
Relation to parent container
- Rel source_udp_port_pools:
The source-udp-port-pools allocation
- relation nokia_srlinux::Oam parent_oam [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Oam.ippm [0:1]
- relation nokia_srlinux::oam::ippm::SourceUdpPortPools source_udp_port_pools [0:1]¶
Relation to parent container Peer relation: The source-udp-port-pools allocation
other end:
nokia_srlinux::oam::ippm::SourceUdpPortPools.parent_ippm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::setupIppmYangContainer
constrainttrue
- entity nokia_srlinux::oam::LinkMeasurement¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-link-measurement.yang:L914
- Rel measurement_template:
The measurement-template list instance
- Rel parent_oam:
Relation to parent container
- relation nokia_srlinux::Oam parent_oam [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Oam.link_measurement [0:1]
- relation nokia_srlinux::oam::link_measurement::MeasurementTemplate measurement_template [0:*]¶
Relation to parent container Peer relation: The measurement-template list instance
other end:
nokia_srlinux::oam::link_measurement::MeasurementTemplate.parent_link_measurement [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::setupLinkMeasurementYangContainer
constrainttrue
- entity nokia_srlinux::oam::PerformanceMonitoring¶
Parents:
nokia_srlinux::Base
OAM Performance Monitoring Yang definition can be found here: srl_nokia-oam.yang:L33
- Rel ethcfm:
- Rel ip:
- Rel parent_oam:
Relation to parent container
- relation nokia_srlinux::Oam parent_oam [1]¶
Relation to parent container Peer relation: OAM Performance Monitoring
- relation nokia_srlinux::oam::performance_monitoring::Ethcfm ethcfm [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::Ethcfm.parent_performance_monitoring [1]
- relation nokia_srlinux::oam::performance_monitoring::Ip ip [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::Ip.parent_performance_monitoring [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::setupPerformanceMonitoringYangContainer
constrainttrue
- entity nokia_srlinux::oam::Stamp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-stamp.yang:L139
- Rel parent_oam:
Relation to parent container
- Rel session_reflector:
STAMP Session-Reflector configuration and state
- relation nokia_srlinux::Oam parent_oam [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Oam.stamp [0:1]
- relation nokia_srlinux::oam::stamp::SessionReflector session_reflector [0:1]¶
Relation to parent container Peer relation: STAMP Session-Reflector configuration and state
other end:
nokia_srlinux::oam::stamp::SessionReflector.parent_stamp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::setupStampYangContainer
constrainttrue
- entity nokia_srlinux::oam::Twamp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-twamp.yang:L720
- Rel parent_oam:
Relation to parent container
- Rel server:
Configuration of the TWAMP Server logical entity
- relation nokia_srlinux::Oam parent_oam [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Oam.twamp [0:1]
- relation nokia_srlinux::oam::twamp::Server server [0:1]¶
Relation to parent container Peer relation: Configuration of the TWAMP Server logical entity
other end:
nokia_srlinux::oam::twamp::Server.parent_twamp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::setupTwampYangContainer
constrainttrue
- entity nokia_srlinux::oam::ethcfm::Domain¶
Parents:
nokia_srlinux::Base
Maintenance Domain list containing CFM Domain configuration elements
The Maintenance Domain includes all the configuration elements to define the individual domain behavior and scope of the CFM boundary. These are common elements that will be part of the related Maintenance Associations configured within the domain. Yang definition can be found here: srl_nokia-ethcfm.yang:L1042
- attribute nokia_srlinux::oam::ethcfm::domain_dns_t? dns=null¶
Maintenance Domain DNS like name for domain-format type ‘dns-like’
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::domain_format_type? domain_format=null¶
domain format
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::admin_name domain_id¶
A unique identifier of a Maintenance Domain
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::md_level_type? level=null¶
Integer identifying the Maintenance Domain Level Higher numbers correspond Maintenance Domains with the greatest physical reach. Lower numbers correspond to Maintenance Domains with more limited physical reach. CFM packets with higher levels will flow transparently across domains of lower level values.
- attribute nokia_srlinux::oam::ethcfm::domain_mac_t? mac=null¶
Maintenance Domain MAC address portion required for domain-format type ‘mac-address’
- attribute nokia_srlinux::oam::ethcfm::domain_name_t? name=null¶
Maintenance Domain name for domain-format ‘string’
- attribute yang::types::uint16? two_octet_int=null¶
Maintenance Domain 2-octet integer portion required for domain-format type ‘mac-address’ :rel association: The Maintenance Association list is a grouping of MEPs for the same network-instance :rel parent_ethcfm: Relation to parent container
- relation nokia_srlinux::oam::Ethcfm parent_ethcfm [1]¶
Relation to parent container Peer relation: Maintenance Domain list containing CFM Domain configuration elements
The Maintenance Domain includes all the configuration elements to define the individual domain behavior and scope of the CFM boundary. These are common elements that will be part of the related Maintenance Associations configured within the domain.
other end:
nokia_srlinux::oam::Ethcfm.domain [0:4000]
- relation nokia_srlinux::oam::ethcfm::domain::Association association [0:4000]¶
Relation to parent container Peer relation: The Maintenance Association list is a grouping of MEPs for the same network-instance
other end:
nokia_srlinux::oam::ethcfm::domain::Association.parent_domain [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::ethcfm::setupDomainYangContainer
constrainttrue
- entity nokia_srlinux::oam::ethcfm::SenderId¶
Parents:
nokia_srlinux::Base
Enter the sender-id context Yang definition can be found here: srl_nokia-ethcfm.yang:L1018
- attribute nokia_srlinux::oam::ethcfm::sender_id_chassis_local_name_t? chassis_local_name=null¶
Local name used for sender-id TLV chassis-component when chassis-type is ‘local’ This configuration is mandatory when ../chassis-type value is ‘local’ This configuration is optional when the ../chassis-type value is not ‘local’. In the latter case the chassis-local-name is not used in the sender-id TLV
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::chassis_id_subtype? chassis_type=null¶
Selection of chassis-component type to be included in CFM PDUs :rel parent_ethcfm: Relation to parent container
- relation nokia_srlinux::oam::Ethcfm parent_ethcfm [1]¶
Relation to parent container Peer relation: Enter the sender-id context
other end:
nokia_srlinux::oam::Ethcfm.sender_id [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::ethcfm::setupSenderIdYangContainer
constrainttrue
- entity nokia_srlinux::oam::ethcfm::domain::Association¶
Parents:
nokia_srlinux::Base
The Maintenance Association list is a grouping of MEPs for the same network-instance Yang definition can be found here: srl_nokia-ethcfm.yang:L1128
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::association_format_type? association_format=null¶
association format
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::admin_name association_id¶
A unique identifier of a Maintenance Association
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::ccm_interval_type? ccm_interval=null¶
The interval between CCM transmissions to be used by all MEPs in Maintenance Association
- attribute nokia_srlinux::oam::ethcfm::domain::association_icc_value_t? icc_value=null¶
Maintenance Association name in ICC-based format
- attribute nokia_srlinux::oam::ethcfm::domain::association_id_t? id=null¶
Maintenance Association VPN ID name When the VPN OUI is less than 6 hex characters the configured value will be prepended with the appropriate number of zeros. When the VPN INDEX is less than 8 hex characters the configured value will be prepended with the appropriate number of zeros.
- attribute nokia_srlinux::oam::ethcfm::domain::association_name_t? name=null¶
Maintenance Association name in string format
- attribute yang::types::uint16? number=null¶
Maintenance Association name in integer format
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::id_permission_type? sender_id_permission_type=null¶
Whether to include the Sender ID TLV with configured type Sender ID TLV will be sent when the id-permission is set to a value other than ‘none’. When transmitting the Sender ID TLV the information carried in the TLV will match the configured value. When id-permission is set to ‘chassis’ the chassis information (chassis-component or local) will be based on the /ethcfm/sender-id/chassis-type configuration.
- attribute nokia_srlinux::oam::ethcfm::domain::association_vid_t? vid=null¶
Maintenance association VLAN ID format :rel association_meps: :rel ccm_hold_time: Enter the ccm-hold-time context :rel mep: The list of Maintenance association End Points in a specific Maintance Association :rel network_instance: :rel parent_domain: Relation to parent container :rel remote_mep_auto_discovery: This set of data definitions describes the auto discovery behavior for remote MEPs
- relation nokia_srlinux::oam::ethcfm::Domain parent_domain [1]¶
Relation to parent container Peer relation: The Maintenance Association list is a grouping of MEPs for the same network-instance
other end:
nokia_srlinux::oam::ethcfm::Domain.association [0:4000]
- relation nokia_srlinux::oam::ethcfm::domain::association::AssociationMeps association_meps [0:64]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::ethcfm::domain::association::AssociationMeps.parent_association [1]
- relation nokia_srlinux::oam::ethcfm::domain::association::CcmHoldTime ccm_hold_time [0:1]¶
Relation to parent container Peer relation: Enter the ccm-hold-time context
other end:
nokia_srlinux::oam::ethcfm::domain::association::CcmHoldTime.parent_association [1]
- relation nokia_srlinux::oam::ethcfm::domain::association::Mep mep [0:*]¶
Relation to parent container Peer relation: The list of Maintenance association End Points in a specific Maintance Association
other end:
nokia_srlinux::oam::ethcfm::domain::association::Mep.parent_association [1]
- relation nokia_srlinux::oam::ethcfm::domain::association::NetworkInstance network_instance [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::ethcfm::domain::association::NetworkInstance.parent_association [1]
- relation nokia_srlinux::oam::ethcfm::domain::association::RemoteMepAutoDiscovery remote_mep_auto_discovery [0:1]¶
Relation to parent container Peer relation: This set of data definitions describes the auto discovery behavior for remote MEPs
other end:
nokia_srlinux::oam::ethcfm::domain::association::RemoteMepAutoDiscovery.parent_association [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::AssociationMeps¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ethcfm.yang:L1297
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::mep_id_type mep_id¶
A list of the MEP IDs expected for the MA :rel parent_association: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::Association parent_association [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::ethcfm::domain::Association.association_meps [0:64]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::CcmHoldTime¶
Parents:
nokia_srlinux::Base
Enter the ccm-hold-time context Yang definition can be found here: srl_nokia-ethcfm.yang:L1237
- attribute nokia_srlinux::oam::ethcfm::domain::association::ccm_hold_time_delay_timeout_t? delay_timeout=null¶
Additional time before a MEP declares a fault for peer CCM timeout conditions Each unit (centisecond) is the equivalent to 10ms, or one hundredth of a second in additional time added before the recognition of a peer time-out. This is applicable to MEPs with a CCM-interval 100ms and below. A value 0 means there is no additive delay :rel parent_association: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::Association parent_association [1]¶
Relation to parent container Peer relation: Enter the ccm-hold-time context
other end:
nokia_srlinux::oam::ethcfm::domain::Association.ccm_hold_time [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::Mep¶
Parents:
nokia_srlinux::Base
The list of Maintenance association End Points in a specific Maintance Association Yang definition can be found here: srl_nokia-ethcfm.yang:L1306
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The administrative state of the MEP
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::priority_type? ccm_ltm_priority=null¶
The dot1p priority for CCMs and LTMs transmitted by the MEP
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::mep_direction_type? direction=null¶
A value indicating the direction which the MEP faces on the interface/subinterface For all but MAC-VRF subinterfaces, the direction of the MEP must be ‘down’. The MAC-VRF is a bridging entity and therefore supports the direction ‘up’. The other entities are not bridging and therefore cannot support the direction ‘up’.
- attribute nokia_srlinux::types::srl_nokia_common::unicast_mac_address? mac_address=null¶
The optional unicast MAC address configuration for the MEP By default, the unicast MAC will be assigned based on the interface on which the MEP is configured. Any bridge that has UP MEPs on different subinterfaces that share the same interface (port) must have unique MAC. Design guidelines suggest that when multiple subinterfaces share a common interface (port) only one of the subinterfaces should be configured with an UP MEP. When UP MEPs on different subinterfaces share a common interface (port), and they use the default MAC address assignment based on the interface, a bridging service will experience MAC moves when CFM packets are sent from those MEPs.
- attribute int mep_id¶
The integer that uniquely identified the MEP in the Mainatenance Association :rel continuity_check: This set of data definitions describes the handling of Ethernet Continuity Check (ETH-CCM) :rel interface_ref: :rel parent_association: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::Association parent_association [1]¶
Relation to parent container Peer relation: The list of Maintenance association End Points in a specific Maintance Association
other end:
nokia_srlinux::oam::ethcfm::domain::Association.mep [0:*]
- relation nokia_srlinux::oam::ethcfm::domain::association::mep::ContinuityCheck continuity_check [0:1]¶
Relation to parent container Peer relation: This set of data definitions describes the handling of Ethernet Continuity Check (ETH-CCM)
other end:
nokia_srlinux::oam::ethcfm::domain::association::mep::ContinuityCheck.parent_mep [1]
- relation nokia_srlinux::oam::ethcfm::domain::association::mep::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::ethcfm::domain::association::mep::InterfaceRef.parent_mep [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::NetworkInstance¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ethcfm.yang:L1222
- attribute string? name=null¶
The network instance to which the information in this maintenance-association applies :rel parent_association: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::Association parent_association [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::ethcfm::domain::Association.network_instance [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::RemoteMepAutoDiscovery¶
Parents:
nokia_srlinux::Base
This set of data definitions describes the auto discovery behavior for remote MEPs Yang definition can be found here: srl_nokia-ethcfm.yang:L1255
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable the ability to auto-discover remote MEPs within the Maintenance Association When the admins-state is ‘enable’ unknown remote MEP peers which have the same Maintenance Association information will be automatically added to the remote-mep database and these unknown peer MEPS will not raise the defect error-ccm. When the admin-state is ‘disable’ unknown remote MEP peers will not automatically be added to the remote-mep database. Unknown MEPs will cause the defect error-ccm to be raised. If the admin-state value is changed from ‘enable’ to ‘disable’ all previously learned MEPs for the Maintenance Association will be removed from the remote-mep database and auto-discovery will be disabled.
- attribute nokia_srlinux::oam::ethcfm::domain::association::remote_mep_auto_discovery_aging_timer_t? aging_timer=null¶
Optional time in seconds the peer MEP remains in the remote-mep database after defect remote-ccm Peer MEPs added to the remote-mep database do not age out unless the optional aging-timer is configured. The aging-timer value is the additional time the remote peer MEP remains in the database since the recognition of the defect remote-ccm (peer timeout where no packets have arrived from the peer in 3.5 times the ccm-interval). A value of ‘none’ disables aging. :rel parent_association: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::Association parent_association [1]¶
Relation to parent container Peer relation: This set of data definitions describes the auto discovery behavior for remote MEPs
other end:
nokia_srlinux::oam::ethcfm::domain::Association.remote_mep_auto_discovery [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::mep::ContinuityCheck¶
Parents:
nokia_srlinux::Base
This set of data definitions describes the handling of Ethernet Continuity Check (ETH-CCM) Yang definition can be found here: srl_nokia-ethcfm.yang:L1385
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? ccm_transmit=null¶
An indicator of whether the MEP is configured to transmit CCM packets This only controls the MEPs ability to transmit CCM packets. A MEP has no administrative configuration to stop the processing of received CCM packets. The receive state machine for CCM will execute and packet processing will occur regardless of the ccm-transmit admin-state.
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::lowest_alarm_priority_type? lowest_fault_priority_defect=null¶
The lowest priority defect that will generate a Fault Alarm When the lowest fault priority defect is reached or exceeded, a fault alarm will be generated. This also drives the ../ccm-local-fault-action for down MEPs. When the lowest priority fault priority defect is reached the ../ccm-local-fault with a value ‘permit’ will operationally affect the interface or subinterface on which it is attached. :rel ccm_local_fault: Enter the ccm local fault action context :rel parent_mep: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::association::Mep parent_mep [1]¶
Relation to parent container Peer relation: This set of data definitions describes the handling of Ethernet Continuity Check (ETH-CCM)
other end:
nokia_srlinux::oam::ethcfm::domain::association::Mep.continuity_check [0:1]
- relation nokia_srlinux::oam::ethcfm::domain::association::mep::continuity_check::CcmLocalFault ccm_local_fault [0:1]¶
Relation to parent container Peer relation: Enter the ccm local fault action context
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::mep::InterfaceRef¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ethcfm.yang:L1317
- attribute string? interface=null¶
Reference to a base interface, for example a port
- attribute nokia_srlinux::oam::ethcfm::domain::association::mep::interface_ref_subinterface_t? subinterface=null¶
Reference to a subinterface This requires the base interface to be specified using the interface leaf in this container. :rel parent_mep: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::association::Mep parent_mep [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::ethcfm::domain::association::Mep.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ethcfm::domain::association::mep::continuity_check::CcmLocalFault¶
Parents:
nokia_srlinux::Base
Enter the ccm local fault action context Yang definition can be found here: srl_nokia-ethcfm.yang:L1408
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::action_type? action=null¶
Provides the ability to operationally affect the attachment where the down MEP is configured A down MEP that experiences a defect condition matching the lowest-fault-priority defect can affect the operational state of the interface/subinterface the down MEP is configured on when the ccm-local-fault value is ‘permit’. When the ccm-local-fault value is ‘deny’ there is no operational impact on the interface/subinterface. This leaf is only supported on down MEPs. :rel parent_continuity_check: Relation to parent container
- relation nokia_srlinux::oam::ethcfm::domain::association::mep::ContinuityCheck parent_continuity_check [1]¶
Relation to parent container Peer relation: Enter the ccm local fault action context
other end:
nokia_srlinux::oam::ethcfm::domain::association::mep::ContinuityCheck.ccm_local_fault [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::ippm::SourceUdpPortPools¶
Parents:
nokia_srlinux::Base
The source-udp-port-pools allocation Yang definition can be found here: srl_nokia-ippm-source-udp-pool.yang:L31
- Rel parent_ippm:
Relation to parent container
- Rel port:
The UDP port list instance
- relation nokia_srlinux::oam::Ippm parent_ippm [1]¶
Relation to parent container Peer relation: The source-udp-port-pools allocation
other end:
nokia_srlinux::oam::Ippm.source_udp_port_pools [0:1]
- relation nokia_srlinux::oam::ippm::source_udp_port_pools::Port port [0:*]¶
Relation to parent container Peer relation: The UDP port list instance
other end:
nokia_srlinux::oam::ippm::source_udp_port_pools::Port.parent_source_udp_port_pools [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::ippm::setupSourceUdpPortPoolsYangContainer
constrainttrue
- entity nokia_srlinux::oam::ippm::source_udp_port_pools::Port¶
Parents:
nokia_srlinux::Base
The UDP port list instance Yang definition can be found here: srl_nokia-ippm-source-udp-pool.yang:L34
- attribute nokia_srlinux::oam::ippm::source_udp_port_pools::port_application_assignment_t? application_assignment=null¶
Optionally assign an available reserved UDP port to a specific IPPM application
- attribute nokia_srlinux::oam::ippm::source_udp_port_pools::port_port_number_t port_number¶
IPPM source UDP port pools port number :rel parent_source_udp_port_pools: Relation to parent container
- relation nokia_srlinux::oam::ippm::SourceUdpPortPools parent_source_udp_port_pools [1]¶
Relation to parent container Peer relation: The UDP port list instance
other end:
nokia_srlinux::oam::ippm::SourceUdpPortPools.port [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::MeasurementTemplate¶
Parents:
nokia_srlinux::Base
The measurement-template list instance Yang definition can be found here: srl_nokia-link-measurement.yang:L49
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the measurement template This value can be changed while a subinterface is referencing the template. However, the value ‘disable’ will prevent any link measurement test for a subinterface referencing the template from becoming operational.
- attribute nokia_srlinux::oam::link_measurement::measurement_template_delay_t? delay=null¶
Delay measurement statistic type
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Text description for the template
- attribute nokia_srlinux::oam::link_measurement::measurement_template_interval_t? interval=null¶
Interval between test packet transmissions
- attribute nokia_srlinux::oam::link_measurement::measurement_template_last_reported_delay_hold_t? last_reported_delay_hold=null¶
Time to wait to flush the last reported delay This command configures the timer that specifies the wait time before the last reported delay measurement is flushed after a link measurement test enters the operationally down state. The aging timer delays the flushing of the last reported delay metric to the routing engine. This timer starts a countdown to zero when an administrative function causes the operational state of the test on that specific interface to transition from ‘up’ to ‘down’. If the timer expires before the operational state transitions to ‘up’, the previously reported value is flushed. The Delay Measurement Last Reported indicates ‘Cleared’. The timestamp indicates the time of the clear event. The Triggered By indicates ‘Expired’. If the administrative state recovers to operationally ‘up’ before the expiration of the timer, the previous reported value is not flushed. The aging timer does not apply to failure conditions that do not affect the administrative state of the interface, for example interface failure or routing changes. A value ‘0’ means the last reported delay is flushed immediately without delay.
- attribute bool? reporting=null¶
Report behavior for values reaching the configured threshold A value ‘true’ means the routing engine will be informed of the threshold event and the delay measurement. A value ‘false’ means a new value is not passed to the routing engine even if a threshold event has occurred.
- attribute nokia_srlinux::types::srl_nokia_common::name template_name¶
Measurement template name The template may be modified without having to change the admin state to ‘disable’. Any tests referencing the template that is changed on the fly will be terminated and restarted.
- attribute nokia_srlinux::oam::link_measurement::measurement_template_unidirectional_measurement_t? unidirectional_measurement=null¶
Method used to compute the unidirectional delay value The value ‘derived’ computes unidirectional measurements using roundtrip divide by 2. This method could be considered in environments without Time of Day (ToD) clock synchronization. The value ‘actual’ uses the traditional (T2-T1) computation for unidirectional delay. :rel parent_link_measurement: Relation to parent container :rel stamp: The STAMP protocol configuration
- relation nokia_srlinux::oam::LinkMeasurement parent_link_measurement [1]¶
Relation to parent container Peer relation: The measurement-template list instance
other end:
nokia_srlinux::oam::LinkMeasurement.measurement_template [0:*]
- relation nokia_srlinux::oam::link_measurement::measurement_template::Stamp stamp [0:1]¶
Relation to parent container Peer relation: The STAMP protocol configuration
other end:
nokia_srlinux::oam::link_measurement::measurement_template::Stamp.parent_measurement_template [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::Stamp¶
Parents:
nokia_srlinux::Base
The STAMP protocol configuration Yang definition can be found here: srl_nokia-link-measurement.yang:L156
- attribute bool? allow_egress_remark_dscp=null¶
Allow overwrite of DSCP value by the egress QoS policy
- attribute bool? allow_ipv6_udp_checksum_zero=null¶
Process IPv6 packets with UDP check sum zero for STAMP packets
- attribute nokia_srlinux::types::srl_nokia_common::port_number? destination_udp_port=null¶
Destination UDP port used by link measurement test
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp_dscp_t? dscp=null¶
DSCP used in IP header of the STAMP PDU
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp_pad_tlv_size_t? pad_tlv_size=null¶
Optional PAD TLV size
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp_source_udp_port_t? source_udp_port=null¶
Fixed source UDP port for link measurement tests This range of Source UDP ports is a common pool that must be administratively assigned to the applications that share this pool. Performance monitoring IP tests and link-measurement test can assign these UDP ports to their application. Once a UDP port in this range is assigned to one application it cannot be used by the other application. Allocation of these UDP ports can be found at srl_nokia-udp-source-pool.yang model (path oam ippm source-udp-pools).
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp_timestamp_format_t? timestamp_format=null¶
Format of the timestamp used in STAMP PDU This is used to encode the time of day information in the PDU. The value ‘ntp’ uses the 32seconds.32fractional seconds UTC timestamp format. Tha value ‘ptp’ uses the 32seconds.32nanoseconds UTC timestamp format.
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp_ttl_t? ttl=null¶
Time to live value used in the IP header of the STAMP test packet :rel aggregate_sample_window: The aggregate-sample-window configuration options The aggregate sample window is a collection of sample windows. It executes threshold comparisons based on the results passed from each sample window. :rel ipv6_destination_discovery: The ipv6-destination-discovery configuration options This uses a ping with a destination address of the well-known multicast address ff02::2 (all routers) to solicit a response from the peer. The source address of the peer’s response will be used as the IPv6 destination address for the test. This discovery method must only be used when there is a single IPv6 router reachable out this interface. :rel parent_measurement_template: Relation to parent container :rel return_path: The STAMP return-path TLV choice :rel sample_window: The sample-window configuration options The sample window is a collection of individual test packet results. It executes threshold comparisons using the results in the sample window.
- relation nokia_srlinux::oam::link_measurement::MeasurementTemplate parent_measurement_template [1]¶
Relation to parent container Peer relation: The STAMP protocol configuration
other end:
nokia_srlinux::oam::link_measurement::MeasurementTemplate.stamp [0:1]
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::AggregateSampleWindow aggregate_sample_window [0:1]¶
Relation to parent container Peer relation: The aggregate-sample-window configuration options
The aggregate sample window is a collection of sample windows. It executes threshold comparisons based on the results passed from each sample window.
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::Ipv6DestinationDiscovery ipv6_destination_discovery [0:1]¶
Relation to parent container Peer relation: The ipv6-destination-discovery configuration options
This uses a ping with a destination address of the well-known multicast address ff02::2 (all routers) to solicit a response from the peer. The source address of the peer’s response will be used as the IPv6 destination address for the test. This discovery method must only be used when there is a single IPv6 router reachable out this interface.
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::ReturnPath return_path [0:1]¶
Relation to parent container Peer relation: The STAMP return-path TLV choice
other end:
nokia_srlinux::oam::link_measurement::measurement_template::stamp::ReturnPath.parent_stamp [1]
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::SampleWindow sample_window [0:1]¶
Relation to parent container Peer relation: The sample-window configuration options
The sample window is a collection of individual test packet results. It executes threshold comparisons using the results in the sample window.
other end:
nokia_srlinux::oam::link_measurement::measurement_template::stamp::SampleWindow.parent_stamp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::stamp::AggregateSampleWindow¶
Parents:
nokia_srlinux::Base
The aggregate-sample-window configuration options
The aggregate sample window is a collection of sample windows. It executes threshold comparisons based on the results passed from each sample window. Yang definition can be found here: srl_nokia-link-measurement.yang:L315
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window_multiplier_t? multiplier=null¶
Number of sample windows in the aggregate sample window
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window_window_integrity_t? window_integrity=null¶
Sample percentage required for window integrity report The configured percentage translates to a required sample window count that must be included in the aggregate sample window. The number of samples is computed as follows: (window-integrity (%)) x (((aggregate-sample-window length (s)) / (sample-window length (s))) If the number of samples in the aggregate sample window is equal to or greater than the computed number of required samples, the sample window has integrity and the aggregate sample window result is compared to the configured sample window thresholds. If the count is less than the computed number of required samples, the aggregate sample window does not have integrity and the value is not considered as representative. In this case the aggregate sample window results are not compared to the configured sample window thresholds. If this option leaf is not configured, integrity checking is disabled and all results are compared to the configured thresholds. :rel parent_stamp: Relation to parent container :rel threshold: Threshold configuration options for aggregate sample window
- relation nokia_srlinux::oam::link_measurement::measurement_template::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: The aggregate-sample-window configuration options
The aggregate sample window is a collection of sample windows. It executes threshold comparisons based on the results passed from each sample window.
other end:
nokia_srlinux::oam::link_measurement::measurement_template::Stamp.aggregate_sample_window [0:1]
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window::Threshold threshold [0:1]¶
Relation to parent container Peer relation: Threshold configuration options for aggregate sample window
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::stamp::Ipv6DestinationDiscovery¶
Parents:
nokia_srlinux::Base
The ipv6-destination-discovery configuration options
This uses a ping with a destination address of the well-known multicast address ff02::2 (all routers) to solicit a response from the peer. The source address of the peer’s response will be used as the IPv6 destination address for the test. This discovery method must only be used when there is a single IPv6 router reachable out this interface. Yang definition can be found here: srl_nokia-link-measurement.yang:L267
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of IPv6 auto destination discovery
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::ipv6_destination_discovery_discovery_interval_t? discovery_interval=null¶
Transmission frequency for discovery packets while in discovery mode
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::ipv6_destination_discovery_discovery_timer_t? discovery_timer=null¶
Maximum time to remain in the discovery phase The discovery phase will end when the IPv6 peer is discovered or this timer expires.
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::ipv6_destination_discovery_update_interval_t? update_interval=null¶
Transmission frequency to maintain the peer address Once a peer is discovered further discovery packets will be sent at this interval. A value ‘0’ disables the continued validation and updating of changed peer information. If the discovery-timer counts down to zero and a peer has not been discovered and the value of this leaf is ‘0’. The peer will not be discovered and the test will need an admin-state change to restart the discovery process. :rel parent_stamp: Relation to parent container
- relation nokia_srlinux::oam::link_measurement::measurement_template::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: The ipv6-destination-discovery configuration options
This uses a ping with a destination address of the well-known multicast address ff02::2 (all routers) to solicit a response from the peer. The source address of the peer’s response will be used as the IPv6 destination address for the test. This discovery method must only be used when there is a single IPv6 router reachable out this interface.
other end:
nokia_srlinux::oam::link_measurement::measurement_template::Stamp.ipv6_destination_discovery [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::stamp::ReturnPath¶
Parents:
nokia_srlinux::Base
The STAMP return-path TLV choice Yang definition can be found here: srl_nokia-link-measurement.yang:L217
- attribute bool? link=null¶
Optional Return Path sub-TLV specifying link :rel parent_stamp: Relation to parent container
- relation nokia_srlinux::oam::link_measurement::measurement_template::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: The STAMP return-path TLV choice
other end:
nokia_srlinux::oam::link_measurement::measurement_template::Stamp.return_path [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::stamp::SampleWindow¶
Parents:
nokia_srlinux::Base
The sample-window configuration options
The sample window is a collection of individual test packet results. It executes threshold comparisons using the results in the sample window. Yang definition can be found here: srl_nokia-link-measurement.yang:L375
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window_multiplier_t? multiplier=null¶
Multiplier of interval used for sample window length
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window_window_integrity_t? window_integrity=null¶
Sample percentage required for window integrity report This command configures the percentage value that is used to determine whether the sample window has enough samples to be considered representative for that window (integrity), by comparing the number of samples received from the sample window to the percentage configured. The configured percentage considers the interval of probes and the length of the sample window to determine the number of packets required in the sample: (window-integrity (%)) x ((sample-window length (s)) / pps per test (interval)) If the count is less than the computed number of required samples, the sample window does not have integrity and the sample window results are not compared to configured sample window thresholds. If the count is equal to or greater than the computed number of required samples, the sample window has integrity and the aggregate sample window result is compared to the configured sample window thresholds. If this option leaf is not configured, integrity checking is disabled and all results are compared to the configured thresholds. :rel parent_stamp: Relation to parent container :rel threshold: Threshold configuration options for sample window
- relation nokia_srlinux::oam::link_measurement::measurement_template::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: The sample-window configuration options
The sample window is a collection of individual test packet results. It executes threshold comparisons using the results in the sample window.
other end:
nokia_srlinux::oam::link_measurement::measurement_template::Stamp.sample_window [0:1]
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::Threshold threshold [0:1]¶
Relation to parent container Peer relation: Threshold configuration options for sample window
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window::Threshold¶
Parents:
nokia_srlinux::Base
Threshold configuration options for aggregate sample window Yang definition can be found here: srl_nokia-link-measurement.yang:L354
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window::threshold_absolute_t? absolute=null¶
Absolute delta for delay measurement reporting
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window::threshold_relative_t? relative=null¶
Relative delta for measurement reporting, percentage of change :rel parent_aggregate_sample_window: Relation to parent container
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::AggregateSampleWindow parent_aggregate_sample_window [1]¶
Relation to parent container Peer relation: Threshold configuration options for aggregate sample window
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::Threshold¶
Parents:
nokia_srlinux::Base
Threshold configuration options for sample window Yang definition can be found here: srl_nokia-link-measurement.yang:L414
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::threshold_absolute_t? absolute=null¶
Absolute delta for delay measurement reporting
- attribute nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::threshold_relative_t? relative=null¶
Relative delta for measurement reporting, percentage of change :rel parent_sample_window: Relation to parent container
- relation nokia_srlinux::oam::link_measurement::measurement_template::stamp::SampleWindow parent_sample_window [1]¶
Relation to parent container Peer relation: Threshold configuration options for sample window
other end:
nokia_srlinux::oam::link_measurement::measurement_template::stamp::SampleWindow.threshold [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::Ethcfm¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L44
- Rel delay:
- Rel loss:
- Rel parent_performance_monitoring:
Relation to parent container
- Rel session:
Enter the session list instance which contains the test session configuration
- relation nokia_srlinux::oam::PerformanceMonitoring parent_performance_monitoring [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::PerformanceMonitoring.ethcfm [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Delay delay [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Delay.parent_ethcfm [1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Loss loss [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Loss.parent_ethcfm [1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Session session [0:*]¶
Relation to parent container Peer relation: Enter the session list instance which contains the test session configuration
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Session.parent_ethcfm [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::Ip¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L48
- Rel delay:
- Rel loss:
- Rel parent_performance_monitoring:
Relation to parent container
- Rel session:
Enter the session list instance which contains the test session configuration
- relation nokia_srlinux::oam::PerformanceMonitoring parent_performance_monitoring [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::PerformanceMonitoring.ip [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ip::Delay delay [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::Delay.parent_ip [1]
- relation nokia_srlinux::oam::performance_monitoring::ip::Loss loss [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::Loss.parent_ip [1]
- relation nokia_srlinux::oam::performance_monitoring::ip::Session session [0:*]¶
Relation to parent container Peer relation: Enter the session list instance which contains the test session configuration
other end:
nokia_srlinux::oam::performance_monitoring::ip::Session.parent_ip [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::performance_monitoring::setupIpYangContainer
constrainttrue
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::Delay¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L45
- Rel bin_group:
Enter the bin-group list instance
- Rel parent_ethcfm:
Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::Ethcfm parent_ethcfm [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::Ethcfm.delay [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::BinGroup bin_group [0:255]¶
Relation to parent container Peer relation: Enter the bin-group list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::delay::BinGroup.parent_delay [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::Loss¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L48
- Rel loss_events_template:
The delay-template list instance
- Rel parent_ethcfm:
Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::Ethcfm parent_ethcfm [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::Ethcfm.loss [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate loss_events_template [0:255]¶
Relation to parent container Peer relation: The delay-template list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate.parent_loss [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::Session¶
Parents:
nokia_srlinux::Base
Enter the session list instance which contains the test session configuration Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L51
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A description of the OAM-PM session
- attribute nokia_srlinux::types::srl_nokia_ethcfm_types::priority_type? priority=null¶
The priority used when generating CFM test frames
- attribute nokia_srlinux::types::srl_nokia_common::name session_name¶
The name of the OAM-PM session
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_session_type? session_type=null¶
Session scheduling type for the test sessions configured under this OAM-PM session A value ‘proactive’ means the protocol specific test session will be always on when admin-state is ‘enable’. A value ‘on-demand’ requires the tools start command to be issued for test session with admin-state ‘enable’
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session_target_t? target=null¶
Target MAC address or remote MEP ID for the test :rel eth_cfm_single_ended_dmm_test: :rel eth_cfm_single_ended_slm_test: :rel measurement_interval: The list of measurement intervals associated with the OAM-PM session :rel parent_ethcfm: Relation to parent container :rel source:
- relation nokia_srlinux::oam::performance_monitoring::Ethcfm parent_ethcfm [1]¶
Relation to parent container Peer relation: Enter the session list instance which contains the test session configuration
other end:
nokia_srlinux::oam::performance_monitoring::Ethcfm.session [0:*]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::EthCfmSingleEndedDmmTest eth_cfm_single_ended_dmm_test [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::EthCfmSingleEndedSlmTest eth_cfm_single_ended_slm_test [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::MeasurementInterval measurement_interval [0:4]¶
Relation to parent container Peer relation: The list of measurement intervals associated with the OAM-PM session
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::session::MeasurementInterval.parent_session [1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::Source source [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::session::Source.parent_session [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::delay::BinGroup¶
Parents:
nokia_srlinux::Base
Enter the bin-group list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L178
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the bin group
- attribute nokia_srlinux::types::srl_nokia_common::name bin_group_name¶
The name of the bin group The ‘default’ bin-group is created by the system. The ‘default’ bin-group is not configurable and has the following system values bin type counts and associated lower-bound values. These values are microseconds. bin-type fd bin 0 { lower-bound 0 } bin 1 { lower-bound 10000 } bin-type fdr bin 0 { lower-bound 0 } bin 1 { lower-bound 10000 } bin-type ifdv bin 0 { lower-bound 0 } bin 1 { lower-bound 10000 }
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A description of the bin group :rel bin_type: :rel parent_delay: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Delay parent_delay [1]¶
Relation to parent container Peer relation: Enter the bin-group list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Delay.bin_group [0:255]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType bin_type [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType.parent_bin_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm.yang:L219
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type_bin_count_t? bin_count=null¶
The number of bins for the bin type This will establish the contiguous bin numbers starting at 0 and increasing by the number specified
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::bin_metric_type bin_metric¶
Enter the bin-type list instance :rel bin: Enter the bin number list instance :rel delay_event: Enter the delay-event list instance :rel exclude_from_avg: Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average :rel parent_bin_group: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::BinGroup parent_bin_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::delay::BinGroup.bin_type [0:*]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::Bin bin [0:*]¶
Relation to parent container Peer relation: Enter the bin number list instance
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::DelayEvent delay_event [0:*]¶
Relation to parent container Peer relation: Enter the delay-event list instance
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::ExcludeFromAvg exclude_from_avg [0:*]¶
Relation to parent container Peer relation: Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::Bin¶
Parents:
nokia_srlinux::Base
Enter the bin number list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L236
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::bin_bin_number_t bin_number¶
The number of the bin
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::bin_lower_bound_t? lower_bound=null¶
Lower bound for the bin The lower-bound value between two adjacent bins represents the range of results that will be mapped to the bin. The lower-bound value for the bin represents the smallest value in the range. The lower-bound value of the adjacent higher bin represents the smallest value in its range. Bin 0 must have a lower-bound value of ‘0’. Bin numbers must not have conflicting lower-bound values. Higher bin numbers must not have lower-bound values less than any lower bin number. If the bin does not have a corresponding lower-bound value configured the defaults will be used. Bin 0 will have a default lower-bound of ‘0’. Each subsequent bin will increase the lower-bound value by 10000 microseconds. For example, a bin-count of 5 will result in the following default lower-bound values. Bin 0 lower-bound 0 Bin 1 lower-bound 10000 Bin 2 lower-bound 20000 Bin 3 lower-bound 30000 Bin 4 lower-bound 40000 If configuration of a lower bin will cause a conflict with a higher bin lower-bound value the commit will fail. A single commit would be required to avoid these conflicts. :rel parent_bin_type: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType parent_bin_type [1]¶
Relation to parent container Peer relation: Enter the bin number list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType.bin [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::DelayEvent¶
Parents:
nokia_srlinux::Base
Enter the delay-event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L282
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::delay_event_clear_threshold_t? clear_threshold=null¶
The not be exceeded value used to clear a previously triggered threshold crossing alarm Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria. A value ‘0’ means a subsequent measurement interval must have no results in the bins counted against the threshold.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::delay_direction_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘round-trip’ is the measurement of the complete path using four timestamps.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::delay_event_exclude_lowest_bin_t? exclude_lowest_bin=null¶
Lowest bin excluded from the threshold crossing alarm count This bin must be higher than the ../lowest-bin, which is used to specify which bins to consider for threshold crossing alarms
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::delay_event_lowest_bin_t? lowest_bin=null¶
The lowest bin number to include when comparing counts to thresholds The number of results in this bin and all higher bins are compared to the configured thresholds.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::delay_event_raise_threshold_t? raise_threshold=null¶
Raise threshold count for excessive delay A threshold crossing alarm is raised when the raise-threshold value is reached. The raise threshold is compared to the number of results the ../lowest-bin and all higher, excluding any results that would be excluded by the ../exclude-lowest-bin. :rel parent_bin_type: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType parent_bin_type [1]¶
Relation to parent container Peer relation: Enter the delay-event list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType.delay_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::ExcludeFromAvg¶
Parents:
nokia_srlinux::Base
Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average Yang definition can be found here: srl_nokia-oam-pm.yang:L353
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::exclude_from_avg_bins_t? bins=null¶
Bin numbers excluded from the average calculation Results mapped to these bins do not impact the delay metric average values.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::delay_direction_type direction¶
The direction of the measurement A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘round-trip’ is the measurement of the complete path using four timestamps. :rel parent_bin_type: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType parent_bin_type [1]¶
Relation to parent container Peer relation: Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::BinType.exclude_from_avg [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate¶
Parents:
nokia_srlinux::Base
The delay-template list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L824
- attribute nokia_srlinux::types::srl_nokia_common::name loss_events_template_name¶
A description of the template :rel avg_flr_event: Enter the avg-flr-event list instance :rel chli_event: Enter the Consecutive High Loss Interval list instance :rel hli_event: Enter the High Loss Interval list instance :rel parent_loss: Relation to parent container :rel unavailability_event: Enter the unavailability-event list instance :rel undetermined_availability_event: Enter the undetermined availability event list instance :rel undetermined_unavailability_event: Enter the undetermined unavailability event list instance
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Loss parent_loss [1]¶
Relation to parent container Peer relation: The delay-template list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Loss.loss_events_template [0:255]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::AvgFlrEvent avg_flr_event [0:*]¶
Relation to parent container Peer relation: Enter the avg-flr-event list instance
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::ChliEvent chli_event [0:*]¶
Relation to parent container Peer relation: Enter the Consecutive High Loss Interval list instance
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::HliEvent hli_event [0:*]¶
Relation to parent container Peer relation: Enter the High Loss Interval list instance
Relation to parent container Peer relation: Enter the unavailability-event list instance
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::UndeterminedAvailabilityEvent undetermined_availability_event [0:*]¶
Relation to parent container Peer relation: Enter the undetermined availability event list instance
Relation to parent container Peer relation: Enter the undetermined unavailability event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::AvgFlrEvent¶
Parents:
nokia_srlinux::Base
Enter the avg-flr-event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L834
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::avg_flr_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered Frame Loss Ratio alarm Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::avg_flr_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the average Frame Loss Ratio This event is computed and considered at the completion of the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the avg-flr-event list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate.avg_flr_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::ChliEvent¶
Parents:
nokia_srlinux::Base
Enter the Consecutive High Loss Interval list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L876
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::chli_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::chli_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the Consecutive High Loss Interval list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate.chli_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::HliEvent¶
Parents:
nokia_srlinux::Base
Enter the High Loss Interval list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L882
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::hli_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::hli_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the High Loss Interval list instance
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate.hli_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Parents:
nokia_srlinux::Base
Enter the unavailability-event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L888
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
Relation to parent container Peer relation: Enter the unavailability-event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::UndeterminedAvailabilityEvent¶
Parents:
nokia_srlinux::Base
Enter the undetermined availability event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L894
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::undetermined_availability_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::undetermined_availability_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the undetermined availability event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Parents:
nokia_srlinux::Base
Enter the undetermined unavailability event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L900
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
Relation to parent container Peer relation: Enter the undetermined unavailability event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::session::EthCfmSingleEndedDmmTest¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L98
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the single ended test
- attribute string? bin_group=null¶
Reference the bin group to be used for this session If not specified the ‘default’ bin-group will be used
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::data_tlv_size? data_tlv_size=null¶
The Data TLV byte count used to increase the size of the base CFM PDU A value ‘0’ means no Data TLV is added. Any other value represents the size of the Data TLV.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_interval? interval=null¶
The transmission rate of the CFM packets
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_dmm_test_test_duration_t? test_duration=null¶
Duration of an OAM-PM session with a session-type on-demand When this leaf is not specified the on-demand test will execute until manually stopped.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_dmm_test_test_id_t? test_id=null¶
Test ID of the test session Test IDs are protocol specific. The same value may be re-used for different protocols but not for the same protocol. When the value ‘auto’ is configured the test-id is dynamically assigned from the upper 32-bit range, [2147483648..4294967296] :rel parent_session: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Session parent_session [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Session.eth_cfm_single_ended_dmm_test [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::session::EthCfmSingleEndedSlmTest¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L157
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the single ended test
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::data_tlv_size? data_tlv_size=null¶
The Data TLV byte count used to increase the size of the base CFM PDU A value ‘0’ means no Data TLV is added. Any other value represents the size of the Data TLV.
- attribute nokia_srlinux::types::srl_nokia_common::percentage? flr_threshold=null¶
Frame Loss Ratio (FLR) is a percentage applied to the frame loss within a delta-t If the FLR is not reached the delta-t is not considered a High Loss Interval. If the FLR is reach the delta-t is considered a High Loss Interval.
- attribute bool? hli_force_count=null¶
Increment High Loss Interval and Consecutive High Loss Interval counters regardless of unavailability A value ‘false’ will not increment the HLI/CHLI counters during times of unavailability. A value ‘true’ will increment the HLI/CHLI counters during times of unavailability.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_interval_slm? interval=null¶
The transmission rate of the CFM packets
- attribute string? loss_event=null¶
The loss event template associated with this loss test session and measurement interval
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test_test_duration_t? test_duration=null¶
Duration of an OAM-PM session with a session-type on-demand When this leaf is not specified the on-demand test will execute until manually stopped.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test_test_id_t? test_id=null¶
Test ID of the test session Test IDs are protocol specific. The same value may be re-used for different protocols but not for the same protocol. When the value ‘auto’ is configured the test-id is dynamically assigned from the upper 32-bit range, [2147483648..4294967296] :rel parent_session: Relation to parent container :rel timing: Enter the timing context used to configure availability options
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Session parent_session [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Session.eth_cfm_single_ended_slm_test [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test::Timing timing [0:1]¶
Relation to parent container Peer relation: Enter the timing context used to configure availability options
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::session::MeasurementInterval¶
Parents:
nokia_srlinux::Base
The list of measurement intervals associated with the OAM-PM session Yang definition can be found here: srl_nokia-oam-pm.yang:L58
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_boundary_type? boundary_type=null¶
Aligning the start of the measurement interval A value ‘clock-aligned’ aligns the start and end of the sample window with the time-of-day clock. A value ‘test-aligned’ aligns the sample window with the start of the test session.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_clock_offset? clock_offset=null¶
Aligning the measurement interval using an offset for the start, considering the boundary-type The clock-offset must be ‘0’ when the boundary-type value is not ‘clock-aligned’. When the boundary-type is ‘clock-aligned’ the value of the clock-offset must be less than the duration of the measurement-interval
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_stored? intervals_stored=null¶
The number of completed measurement intervals stored in volatile memory before overwriting oldest The more intervals stored the more memory will be consumed. The values vary per measurement interval duration. 1-minute default 32 maximum 96 5-minutes default 32 maximum 96 15-minutes default 32 maximum 96 1-hour default 24 maximum 24 1-day default 2 maximum 3
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_duration_type mi_duration¶
Configure the measurement interval duration The measurement interval duration defines the length of the sample window over which the statistics are collected, computed, and stored. The system automatically instantiates a ‘raw’ measurement interval for each defined test session. The ‘raw’ measurement interval is unbounded and continually accumulates measurements while the test session admin-state has value ‘enable’. The ‘raw’ measurement interval can have result cleared to flush restart the accumulation of statistics. :rel parent_session: Relation to parent container :rel threshold_alerts: Enabling configured events for the measurement interval
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Session parent_session [1]¶
Relation to parent container Peer relation: The list of measurement intervals associated with the OAM-PM session
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Session.measurement_interval [0:4]
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::measurement_interval::ThresholdAlerts threshold_alerts [0:1]¶
Relation to parent container Peer relation: Enabling configured events for the measurement interval
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::session::Source¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ethcfm.yang:L57
- attribute string? association_id=null¶
The maintenance association identifier specific to the domain identifier
- attribute string? domain_id=null¶
The maintenance domain identifier
- attribute int? mep_id=null¶
The MEP identifier specific to the domain and association identifier :rel parent_session: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::Session parent_session [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::Session.source [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test::Timing¶
Parents:
nokia_srlinux::Base
Enter the timing context used to configure availability options Yang definition can be found here: srl_nokia-oam-pm.yang:L742
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test::timing_chli_threshold_t? chli_threshold=null¶
Consecutive High Loss Interval (CHLI) threshold The threshold of consecutive delta-ts within a sliding availability window that will cause this counter to increment. The CHLI counter will increment a maximum of one time for any given availability window. The values provide information on the number of consecutive HLIs that occurred in an availability window without meeting the unavailability criteria.
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test::timing_consecutive_delta_t_t? consecutive_delta_t=null¶
Number of consecutive delta-t that comprise the availability/unavailability sliding window Availability and unavailability state changes will occur when the sliding window is completely comprised of a different state values than the current state
- attribute nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test::timing_frames_per_delta_t_t? frames_per_delta_t=null¶
Number of frames that comprise one delta-t used for comparison to FLR configuration The lenght of the delta-t window is frames-per-delta-t * the probe interval. :rel parent_eth_cfm_single_ended_slm_test: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::EthCfmSingleEndedSlmTest parent_eth_cfm_single_ended_slm_test [1]¶
Relation to parent container Peer relation: Enter the timing context used to configure availability options
other end:
nokia_srlinux::oam::performance_monitoring::ethcfm::session::EthCfmSingleEndedSlmTest.timing [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ethcfm::session::measurement_interval::ThresholdAlerts¶
Parents:
nokia_srlinux::Base
Enabling configured events for the measurement interval Yang definition can be found here: srl_nokia-oam-pm.yang:L123
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? delay_event=null¶
Enable the delay events associated with the bin group assigned to this test session for this measurement interval
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? loss_event=null¶
Enable the loss events associated with the loss test session for this measurement interval :rel parent_measurement_interval: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ethcfm::session::MeasurementInterval parent_measurement_interval [1]¶
Relation to parent container Peer relation: Enabling configured events for the measurement interval
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::Delay¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L49
- Rel bin_group:
Enter the bin-group list instance
- Rel parent_ip:
Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::Ip parent_ip [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::Ip.delay [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::BinGroup bin_group [0:255]¶
Relation to parent container Peer relation: Enter the bin-group list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::BinGroup.parent_delay [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::Loss¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L52
- Rel loss_events_template:
The delay-template list instance
- Rel parent_ip:
Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::Ip parent_ip [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::Ip.loss [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate loss_events_template [0:255]¶
Relation to parent container Peer relation: The delay-template list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate.parent_loss [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::Session¶
Parents:
nokia_srlinux::Base
Enter the session list instance which contains the test session configuration Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L55
- attribute bool? allow_egress_remark_dscp=null¶
Allow DSCP modification by the egress QoS policy
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A description of the OAM-PM session
- attribute nokia_srlinux::oam::performance_monitoring::ip::session_destination_t? destination=null¶
Destination IP address for the IP test session
- attribute nokia_srlinux::types::srl_nokia_common::port_number? destination_udp_port=null¶
Destination UDP port for the test session This must match the UDP listening port on the Session Reflector.
- attribute bool? do_not_fragment=null¶
Do not allow packet fragmentation setting the DNF bit in the IPv4 header, or disallow IPv6 fragmentation at the source
- attribute string? network_instance=null¶
The name of the network instance specific to this test session
- attribute nokia_srlinux::types::srl_nokia_common::name session_name¶
The name of the OAM-PM session
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_session_type? session_type=null¶
Session scheduling type for the test sessions configured under this OAM-PM session A value ‘proactive’ means the protocol specific test session will be always on when admin-state is ‘enable’. A value ‘on-demand’ requires the tools start command to be issued for test session with admin-state ‘enable’
- attribute nokia_srlinux::oam::performance_monitoring::ip::session_source_ip_address_t? source_ip_address=null¶
Source IPv4 or IPv6 IP address to be used as the source address of the packet
- attribute nokia_srlinux::oam::performance_monitoring::ip::session_source_udp_port_t? source_udp_port=null¶
Configure a source UDP port instead of using an automatically assignment from the dynamic port range
- attribute nokia_srlinux::oam::performance_monitoring::ip::session_ttl_t? ttl=null¶
TTL value for the IP packet :rel forwarding: Control the local forwarding decision on the source :rel measurement_interval: The list of measurement intervals associated with the OAM-PM session :rel parent_ip: Relation to parent container :rel stamp:
- relation nokia_srlinux::oam::performance_monitoring::Ip parent_ip [1]¶
Relation to parent container Peer relation: Enter the session list instance which contains the test session configuration
other end:
nokia_srlinux::oam::performance_monitoring::Ip.session [0:*]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::Forwarding forwarding [0:1]¶
Relation to parent container Peer relation: Control the local forwarding decision on the source
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::Forwarding.parent_session [1]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::MeasurementInterval measurement_interval [0:4]¶
Relation to parent container Peer relation: The list of measurement intervals associated with the OAM-PM session
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::MeasurementInterval.parent_session [1]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::Stamp stamp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::Stamp.parent_session [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::delay::BinGroup¶
Parents:
nokia_srlinux::Base
Enter the bin-group list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L178
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the bin group
- attribute nokia_srlinux::types::srl_nokia_common::name bin_group_name¶
The name of the bin group The ‘default’ bin-group is created by the system. The ‘default’ bin-group is not configurable and has the following system values bin type counts and associated lower-bound values. These values are microseconds. bin-type fd bin 0 { lower-bound 0 } bin 1 { lower-bound 10000 } bin-type fdr bin 0 { lower-bound 0 } bin 1 { lower-bound 10000 } bin-type ifdv bin 0 { lower-bound 0 } bin 1 { lower-bound 10000 }
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A description of the bin group :rel bin_type: :rel parent_delay: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::Delay parent_delay [1]¶
Relation to parent container Peer relation: Enter the bin-group list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::Delay.bin_group [0:255]
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType bin_type [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType.parent_bin_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm.yang:L219
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type_bin_count_t? bin_count=null¶
The number of bins for the bin type This will establish the contiguous bin numbers starting at 0 and increasing by the number specified
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::bin_metric_type bin_metric¶
Enter the bin-type list instance :rel bin: Enter the bin number list instance :rel delay_event: Enter the delay-event list instance :rel exclude_from_avg: Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average :rel parent_bin_group: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::BinGroup parent_bin_group [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::BinGroup.bin_type [0:*]
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::Bin bin [0:*]¶
Relation to parent container Peer relation: Enter the bin number list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::Bin.parent_bin_type [1]
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::DelayEvent delay_event [0:*]¶
Relation to parent container Peer relation: Enter the delay-event list instance
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::ExcludeFromAvg exclude_from_avg [0:*]¶
Relation to parent container Peer relation: Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::Bin¶
Parents:
nokia_srlinux::Base
Enter the bin number list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L236
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::bin_bin_number_t bin_number¶
The number of the bin
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::bin_lower_bound_t? lower_bound=null¶
Lower bound for the bin The lower-bound value between two adjacent bins represents the range of results that will be mapped to the bin. The lower-bound value for the bin represents the smallest value in the range. The lower-bound value of the adjacent higher bin represents the smallest value in its range. Bin 0 must have a lower-bound value of ‘0’. Bin numbers must not have conflicting lower-bound values. Higher bin numbers must not have lower-bound values less than any lower bin number. If the bin does not have a corresponding lower-bound value configured the defaults will be used. Bin 0 will have a default lower-bound of ‘0’. Each subsequent bin will increase the lower-bound value by 10000 microseconds. For example, a bin-count of 5 will result in the following default lower-bound values. Bin 0 lower-bound 0 Bin 1 lower-bound 10000 Bin 2 lower-bound 20000 Bin 3 lower-bound 30000 Bin 4 lower-bound 40000 If configuration of a lower bin will cause a conflict with a higher bin lower-bound value the commit will fail. A single commit would be required to avoid these conflicts. :rel parent_bin_type: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType parent_bin_type [1]¶
Relation to parent container Peer relation: Enter the bin number list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType.bin [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::DelayEvent¶
Parents:
nokia_srlinux::Base
Enter the delay-event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L282
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_clear_threshold_t? clear_threshold=null¶
The not be exceeded value used to clear a previously triggered threshold crossing alarm Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria. A value ‘0’ means a subsequent measurement interval must have no results in the bins counted against the threshold.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::delay_direction_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘round-trip’ is the measurement of the complete path using four timestamps.
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_exclude_lowest_bin_t? exclude_lowest_bin=null¶
Lowest bin excluded from the threshold crossing alarm count This bin must be higher than the ../lowest-bin, which is used to specify which bins to consider for threshold crossing alarms
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_lowest_bin_t? lowest_bin=null¶
The lowest bin number to include when comparing counts to thresholds The number of results in this bin and all higher bins are compared to the configured thresholds.
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::delay_event_raise_threshold_t? raise_threshold=null¶
Raise threshold count for excessive delay A threshold crossing alarm is raised when the raise-threshold value is reached. The raise threshold is compared to the number of results the ../lowest-bin and all higher, excluding any results that would be excluded by the ../exclude-lowest-bin. :rel parent_bin_type: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType parent_bin_type [1]¶
Relation to parent container Peer relation: Enter the delay-event list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType.delay_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::ExcludeFromAvg¶
Parents:
nokia_srlinux::Base
Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average Yang definition can be found here: srl_nokia-oam-pm.yang:L353
- attribute nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::exclude_from_avg_bins_t? bins=null¶
Bin numbers excluded from the average calculation Results mapped to these bins do not impact the delay metric average values.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::delay_direction_type direction¶
The direction of the measurement A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘round-trip’ is the measurement of the complete path using four timestamps. :rel parent_bin_type: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType parent_bin_type [1]¶
Relation to parent container Peer relation: Enter the exclude-from-avg list instance used to exclude specified bins from their values being included in the average
other end:
nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::BinType.exclude_from_avg [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate¶
Parents:
nokia_srlinux::Base
The delay-template list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L824
- attribute nokia_srlinux::types::srl_nokia_common::name loss_events_template_name¶
A description of the template :rel avg_flr_event: Enter the avg-flr-event list instance :rel chli_event: Enter the Consecutive High Loss Interval list instance :rel hli_event: Enter the High Loss Interval list instance :rel parent_loss: Relation to parent container :rel unavailability_event: Enter the unavailability-event list instance :rel undetermined_availability_event: Enter the undetermined availability event list instance :rel undetermined_unavailability_event: Enter the undetermined unavailability event list instance
- relation nokia_srlinux::oam::performance_monitoring::ip::Loss parent_loss [1]¶
Relation to parent container Peer relation: The delay-template list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::Loss.loss_events_template [0:255]
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::AvgFlrEvent avg_flr_event [0:*]¶
Relation to parent container Peer relation: Enter the avg-flr-event list instance
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::ChliEvent chli_event [0:*]¶
Relation to parent container Peer relation: Enter the Consecutive High Loss Interval list instance
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::HliEvent hli_event [0:*]¶
Relation to parent container Peer relation: Enter the High Loss Interval list instance
Relation to parent container Peer relation: Enter the unavailability-event list instance
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::UndeterminedAvailabilityEvent undetermined_availability_event [0:*]¶
Relation to parent container Peer relation: Enter the undetermined availability event list instance
Relation to parent container Peer relation: Enter the undetermined unavailability event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::AvgFlrEvent¶
Parents:
nokia_srlinux::Base
Enter the avg-flr-event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L834
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::avg_flr_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered Frame Loss Ratio alarm Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source.
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::avg_flr_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the average Frame Loss Ratio This event is computed and considered at the completion of the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the avg-flr-event list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate.avg_flr_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::ChliEvent¶
Parents:
nokia_srlinux::Base
Enter the Consecutive High Loss Interval list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L876
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::chli_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::chli_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the Consecutive High Loss Interval list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate.chli_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::HliEvent¶
Parents:
nokia_srlinux::Base
Enter the High Loss Interval list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L882
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::hli_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::hli_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the High Loss Interval list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate.hli_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Parents:
nokia_srlinux::Base
Enter the unavailability-event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L888
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
Relation to parent container Peer relation: Enter the unavailability-event list instance
other end:
nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate.unavailability_event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::UndeterminedAvailabilityEvent¶
Parents:
nokia_srlinux::Base
Enter the undetermined availability event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L894
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::undetermined_availability_event_clear_threshold_t? clear_threshold=null¶
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::loss_direction_aggregate_type direction¶
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
- attribute nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::undetermined_availability_event_raise_threshold_t? raise_threshold=null¶
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::loss::LossEventsTemplate parent_loss_events_template [1]¶
Relation to parent container Peer relation: Enter the undetermined availability event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Parents:
nokia_srlinux::Base
Enter the undetermined unavailability event list instance Yang definition can be found here: srl_nokia-oam-pm.yang:L900
The value used to clear a previously triggered alarm for the metric of interest Two type of threshold crossing alarms; Stateless and Stateful. When the clear-threshold is not specified the type = stateless. Stateless alarms are not maintained across measurement interval boundaries. Each measurement interval is self-contained. When a clear-threshold is configured the type = stateful. Stateful alarms are maintained across measurement interval boundaries and cleared when a subsequent measurement interval completes and meets the clear threshold criteria.
The direction of the measurement of interest A value ‘forward’ is the measurement from source to reflector. A value ‘backward’ is the measurement from reflector to source. A value ‘aggregate’ sums the forward and backward counts into an aggregate.
Raise threshold for the metric of interest This event is computed and considered during the measurement interval. :rel parent_loss_events_template: Relation to parent container
Relation to parent container Peer relation: Enter the undetermined unavailability event list instance
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::Forwarding¶
Parents:
nokia_srlinux::Base
Control the local forwarding decision on the source Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L124
- attribute bool? bypass_routing=null¶
Only transmit the test packet using an interface directly connected to peer If no directly connected interface exists the packet will not be transmitted even if the route exists in the routing table.
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::forwarding_next_hop_t? next_hop=null¶
IP address of the next hop The next hop must have a valid route in the route-table of the network instance. :rel interface_ref: :rel parent_session: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::Session parent_session [1]¶
Relation to parent container Peer relation: Control the local forwarding decision on the source
other end:
nokia_srlinux::oam::performance_monitoring::ip::Session.forwarding [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::forwarding::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::MeasurementInterval¶
Parents:
nokia_srlinux::Base
The list of measurement intervals associated with the OAM-PM session Yang definition can be found here: srl_nokia-oam-pm.yang:L58
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_boundary_type? boundary_type=null¶
Aligning the start of the measurement interval A value ‘clock-aligned’ aligns the start and end of the sample window with the time-of-day clock. A value ‘test-aligned’ aligns the sample window with the start of the test session.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_clock_offset? clock_offset=null¶
Aligning the measurement interval using an offset for the start, considering the boundary-type The clock-offset must be ‘0’ when the boundary-type value is not ‘clock-aligned’. When the boundary-type is ‘clock-aligned’ the value of the clock-offset must be less than the duration of the measurement-interval
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_stored? intervals_stored=null¶
The number of completed measurement intervals stored in volatile memory before overwriting oldest The more intervals stored the more memory will be consumed. The values vary per measurement interval duration. 1-minute default 32 maximum 96 5-minutes default 32 maximum 96 15-minutes default 32 maximum 96 1-hour default 24 maximum 24 1-day default 2 maximum 3
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::measurement_interval_duration_type mi_duration¶
Configure the measurement interval duration The measurement interval duration defines the length of the sample window over which the statistics are collected, computed, and stored. The system automatically instantiates a ‘raw’ measurement interval for each defined test session. The ‘raw’ measurement interval is unbounded and continually accumulates measurements while the test session admin-state has value ‘enable’. The ‘raw’ measurement interval can have result cleared to flush restart the accumulation of statistics. :rel parent_session: Relation to parent container :rel threshold_alerts: Enabling configured events for the measurement interval
- relation nokia_srlinux::oam::performance_monitoring::ip::Session parent_session [1]¶
Relation to parent container Peer relation: The list of measurement intervals associated with the OAM-PM session
other end:
nokia_srlinux::oam::performance_monitoring::ip::Session.measurement_interval [0:4]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::measurement_interval::ThresholdAlerts threshold_alerts [0:1]¶
Relation to parent container Peer relation: Enabling configured events for the measurement interval
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::Stamp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L173
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of the STAMP test session
- attribute bool? allow_ipv6_udp_checksum_zero=null¶
Process IPv6 packets with a zero UDP checksum When the value of the leaf is ‘false’ IPv6 test sessions packets arriving with IPv6 UDP checksum 0 will be discarded. When the value is ‘true’ the Session-Reflector UDP port will be registered to allow test session packets arriving with IPv6 UDP checksum 0 to be processed by the Session-Reflector.
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::oam_pm_interval? interval=null¶
The transmission rate of the STAMP packets
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::stamp_pad_tlv_size_t? pad_tlv_size=null¶
The PAD TLV byte count used to increase the size of the base STAMP PDU A value ‘0’ means no PAD TLV is added. Any other value represents the size of the PAD TLV.
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::stamp_test_duration_t? test_duration=null¶
Duration of an OAM-PM session with a session-type on-demand When this leaf is not specified the on-demand test will execute until manually stopped.
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::stamp_test_id_t? test_id=null¶
Test ID of the test session Test IDs are protocol specific. The same value may be re-used for different protocols but not for the same protocol. When the value ‘auto’ is configured the test-id is dynamically assigned from the upper 32-bit range, [2147483648..4294967296]
- attribute nokia_srlinux::types::srl_nokia_oam_pm_types::timestamp_format? timestamp_format=null¶
Format of the timestamp bits in the STAMP test PDU If the value is ‘ntp’ the epoch January 1, 1900 at 00:00 will be used and 64-bit encoding of 32 seconds followed by 32 fractional seconds. The value of the z-bit in the error estimate field of the PDU will be set to 0. If the value is ‘ptp’ the epoch January 1, 1970 00:00 will be used and the 64-bit encoding of 32 seconds followed by 32 nanoseconds. The value of the z-bit in the error estimate field of the PDU with be set to 1. :rel delay: :rel loss: :rel parent_session: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::Session parent_session [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::Session.stamp [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Delay delay [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Delay.parent_stamp [1]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Loss loss [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Loss.parent_stamp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::forwarding::InterfaceRef¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L140
- attribute string? interface=null¶
Reference to a base interface, for example a port
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::forwarding::interface_ref_subinterface_t? subinterface=null¶
Subinterface to send the test packet The subinterface mut be a valid route to reach the destination :rel parent_forwarding: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::session::Forwarding parent_forwarding [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::Forwarding.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::measurement_interval::ThresholdAlerts¶
Parents:
nokia_srlinux::Base
Enabling configured events for the measurement interval Yang definition can be found here: srl_nokia-oam-pm.yang:L123
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? delay_event=null¶
Enable the delay events associated with the bin group assigned to this test session for this measurement interval
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? loss_event=null¶
Enable the loss events associated with the loss test session for this measurement interval :rel parent_measurement_interval: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::session::MeasurementInterval parent_measurement_interval [1]¶
Relation to parent container Peer relation: Enabling configured events for the measurement interval
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::MeasurementInterval.threshold_alerts [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Delay¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L235
- attribute string? bin_group=null¶
Reference the bin group to be used for this session. If not specified the ‘default’ bin-group will be used :rel parent_stamp: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::session::Stamp parent_stamp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::Stamp.delay [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Loss¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-oam-pm-ip.yang:L270
- attribute nokia_srlinux::types::srl_nokia_common::percentage? flr_threshold=null¶
Frame Loss Ratio (FLR) is a percentage applied to the frame loss within a delta-t If the FLR is not reached the delta-t is not considered a High Loss Interval. If the FLR is reach the delta-t is considered a High Loss Interval.
- attribute bool? hli_force_count=null¶
Increment High Loss Interval and Consecutive High Loss Interval counters regardless of unavailability A value ‘false’ will not increment the HLI/CHLI counters during times of unavailability. A value ‘true’ will increment the HLI/CHLI counters during times of unavailability.
- attribute string? loss_event=null¶
The loss event template associated with this loss test session and measurement interval :rel parent_stamp: Relation to parent container :rel timing: Enter the timing context used to configure availability options
- relation nokia_srlinux::oam::performance_monitoring::ip::session::Stamp parent_stamp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::Stamp.loss [0:1]
- relation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::Timing timing [0:1]¶
Relation to parent container Peer relation: Enter the timing context used to configure availability options
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::Timing.parent_loss [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::Timing¶
Parents:
nokia_srlinux::Base
Enter the timing context used to configure availability options Yang definition can be found here: srl_nokia-oam-pm.yang:L742
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::timing_chli_threshold_t? chli_threshold=null¶
Consecutive High Loss Interval (CHLI) threshold The threshold of consecutive delta-ts within a sliding availability window that will cause this counter to increment. The CHLI counter will increment a maximum of one time for any given availability window. The values provide information on the number of consecutive HLIs that occurred in an availability window without meeting the unavailability criteria.
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::timing_consecutive_delta_t_t? consecutive_delta_t=null¶
Number of consecutive delta-t that comprise the availability/unavailability sliding window Availability and unavailability state changes will occur when the sliding window is completely comprised of a different state values than the current state
- attribute nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::timing_frames_per_delta_t_t? frames_per_delta_t=null¶
Number of frames that comprise one delta-t used for comparison to FLR configuration The lenght of the delta-t window is frames-per-delta-t * the probe interval. :rel parent_loss: Relation to parent container
- relation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Loss parent_loss [1]¶
Relation to parent container Peer relation: Enter the timing context used to configure availability options
other end:
nokia_srlinux::oam::performance_monitoring::ip::session::stamp::Loss.timing [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::stamp::SessionReflector¶
Parents:
nokia_srlinux::Base
STAMP Session-Reflector configuration and state Yang definition can be found here: srl_nokia-stamp.yang:L141
- attribute nokia_srlinux::oam::stamp::session_reflector_inactivity_timer_t? inactivity_timer=null¶
STAMP test session timeout on inactivity The amount of time (ref-wait) a test session must be inactive, no packets arriving, before the test session is removed from the Session-Reflector stateful table. :rel network_instance: The list of network instances configured for STAMP Session-Reflector function :rel parent_stamp: Relation to parent container
- relation nokia_srlinux::oam::Stamp parent_stamp [1]¶
Relation to parent container Peer relation: STAMP Session-Reflector configuration and state
other end:
nokia_srlinux::oam::Stamp.session_reflector [0:1]
- relation nokia_srlinux::oam::stamp::session_reflector::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: The list of network instances configured for STAMP Session-Reflector function
other end:
nokia_srlinux::oam::stamp::session_reflector::NetworkInstance.parent_session_reflector [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::stamp::setupSessionReflectorYangContainer
constrainttrue
- entity nokia_srlinux::oam::stamp::session_reflector::NetworkInstance¶
Parents:
nokia_srlinux::Base
The list of network instances configured for STAMP Session-Reflector function Yang definition can be found here: srl_nokia-stamp.yang:L163
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This attribute specifies whether the STAMP Session-Reflector is enabled or disabled
- attribute bool? allow_ipv6_udp_checksum_zero=null¶
Process IPv6 packets with a zero UDP checksum When the value of the leaf is ‘false’ IPv6 test sessions packets arriving with IPv6 UDP checksum 0 will be discarded. When the value is ‘true’ the Session-Reflector UDP port will be registered to allow test session packets arriving with IPv6 UDP checksum 0 to be processed by the Session-Reflector.
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A string describing the STAMP Session-Reflector
- attribute string name¶
The name of the network instances to which the Session-Reflector state and configuration applies
- attribute nokia_srlinux::oam::stamp::session_reflector::network_instance_udp_port_t? udp_port=null¶
The UDP Port listening port of the STAMP Session-Reflector :rel ip_prefix: The list of IP source addresses or ranges allowed to send STAMP test packets to Session-Reflector :rel parent_session_reflector: Relation to parent container
- relation nokia_srlinux::oam::stamp::SessionReflector parent_session_reflector [1]¶
Relation to parent container Peer relation: The list of network instances configured for STAMP Session-Reflector function
other end:
nokia_srlinux::oam::stamp::SessionReflector.network_instance [0:*]
- relation nokia_srlinux::oam::stamp::session_reflector::network_instance::IpPrefix ip_prefix [0:*]¶
Relation to parent container Peer relation: The list of IP source addresses or ranges allowed to send STAMP test packets to Session-Reflector
other end:
nokia_srlinux::oam::stamp::session_reflector::network_instance::IpPrefix.parent_network_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::stamp::session_reflector::network_instance::IpPrefix¶
Parents:
nokia_srlinux::Base
The list of IP source addresses or ranges allowed to send STAMP test packets to Session-Reflector Yang definition can be found here: srl_nokia-stamp.yang:L195
- attribute nokia_srlinux::oam::stamp::session_reflector::network_instance::ip_prefix_ip_prefix_t ip_prefix¶
The IP address or range allowed to send STAMP test packets to the Session-Reflector :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::oam::stamp::session_reflector::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: The list of IP source addresses or ranges allowed to send STAMP test packets to Session-Reflector
other end:
nokia_srlinux::oam::stamp::session_reflector::NetworkInstance.ip_prefix [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::twamp::Server¶
Parents:
nokia_srlinux::Base
Configuration of the TWAMP Server logical entity Yang definition can be found here: srl_nokia-twamp.yang:L723
- Rel network_instance:
- Rel parent_twamp:
Relation to parent container
- relation nokia_srlinux::oam::Twamp parent_twamp [1]¶
Relation to parent container Peer relation: Configuration of the TWAMP Server logical entity
other end:
nokia_srlinux::oam::Twamp.server [0:1]
- relation nokia_srlinux::oam::twamp::server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::twamp::server::NetworkInstance.parent_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::oam::twamp::setupServerYangContainer
constrainttrue
- entity nokia_srlinux::oam::twamp::server::NetworkInstance¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-twamp.yang:L726
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
TWAMP Server administrative state A value ‘enable’ administratively starts the Server and Session-Reflector. A value ‘disable’ administratively stops the Server and Session-Reflector, dropping any active TWAMP-Control channels and terminating all TWAMP-Test sessions.
- attribute bool? allow_ipv6_udp_checksum_zero=null¶
Process IPv6 packets with a zero UDP checksum When the value of the leaf is ‘false’ IPv6 test sessions packets arriving with IPv6 UDP checksum 0 will be discarded. When the value is ‘true’ the Session-Reflector UDP port will be registered to allow test session packets arriving with IPv6 UDP checksum 0 to be processed by the Session-Reflector.
- attribute nokia_srlinux::oam::twamp::server::network_instance_control_packet_dscp_t? control_packet_dscp=null¶
The DSCP to be placed in the IP header of TWAMP-Control (TCP) packets generated by the Server
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
TWAMP Server common configuration
- attribute bool? enforce_test_session_start_time=null¶
Discard or process TWAMP-Test packets arriving before the negotiated session start time A Request-TW-Session includes a start-time value for the test session. A value ‘true’ enforces the server check that will drop the TWAMP-Test packets if the test session start-time is before the Server time of day. In environments where the TWAMP Client and TWAMP Servers are not synchronized the value ‘false’ can be used to skip this validation check and process TWAMP test packets that arrive before their indicated start time.
- attribute nokia_srlinux::oam::twamp::server::network_instance_maximum_connections_t? maximum_connections=null¶
The system wide maximum number of concurrent TWAMP-Control connections the Server supports
- attribute nokia_srlinux::oam::twamp::server::network_instance_maximum_sessions_t? maximum_sessions=null¶
The system wide maximum number of concurrent TWAMP-Test sessions the Server supports
- attribute string name¶
The name of the TWAMP Server network instance
- attribute nokia_srlinux::oam::twamp::server::network_instance_servwait_t? servwait=null¶
TWAMP-Control (TCP) session timeout, in seconds The length of time the Server maintains the TWAMP-Control channel in the absence of any activity for the channel. This state is entered when there is no TWAMP-Control messages between the Control-Client and Server, and all test sessions on the TWAMP-Control channel have been stopped, and the timeout following test session stop (REFWAIT) has expired. :rel client_connection: List of TWAMP Client IP prefixes that can establish TWAMP-Control connections with the Server :rel parent_server: Relation to parent container :rel session_reflector: Configuration and state for the TWAMP Session-Reflector
- relation nokia_srlinux::oam::twamp::Server parent_server [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::oam::twamp::Server.network_instance [0:*]
- relation nokia_srlinux::oam::twamp::server::network_instance::ClientConnection client_connection [0:*]¶
Relation to parent container Peer relation: List of TWAMP Client IP prefixes that can establish TWAMP-Control connections with the Server
other end:
nokia_srlinux::oam::twamp::server::network_instance::ClientConnection.parent_network_instance [1]
- relation nokia_srlinux::oam::twamp::server::network_instance::SessionReflector session_reflector [0:1]¶
Relation to parent container Peer relation: Configuration and state for the TWAMP Session-Reflector
other end:
nokia_srlinux::oam::twamp::server::network_instance::SessionReflector.parent_network_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::twamp::server::network_instance::ClientConnection¶
Parents:
nokia_srlinux::Base
List of TWAMP Client IP prefixes that can establish TWAMP-Control connections with the Server Yang definition can be found here: srl_nokia-twamp.yang:L542
- attribute nokia_srlinux::oam::twamp::server::network_instance::client_connection_maximum_connections_t? maximum_connections=null¶
The per Control-Client IP prefix maximum number of concurrent TWAMP-Control connections the Server supports
- attribute nokia_srlinux::oam::twamp::server::network_instance::client_connection_maximum_sessions_t? maximum_sessions=null¶
The per Control-Client IP prefix maximum number of oncurrent TWAMP-Test sessions the Server supports
- attribute nokia_srlinux::oam::twamp::server::network_instance::client_connection_prefix_t prefix¶
A TWAMP Client IP prefix the Server will accept TWAMP-Control connections from :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::oam::twamp::server::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: List of TWAMP Client IP prefixes that can establish TWAMP-Control connections with the Server
other end:
nokia_srlinux::oam::twamp::server::NetworkInstance.client_connection [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::oam::twamp::server::network_instance::SessionReflector¶
Parents:
nokia_srlinux::Base
Configuration and state for the TWAMP Session-Reflector Yang definition can be found here: srl_nokia-twamp.yang:L705
- Rel parent_network_instance:
Relation to parent container
- relation nokia_srlinux::oam::twamp::server::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Configuration and state for the TWAMP Session-Reflector
other end:
nokia_srlinux::oam::twamp::server::NetworkInstance.session_reflector [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::Chassis¶
Parents:
nokia_srlinux::Base
Top-level container for chassis configuration and state Yang definition can be found here: srl_nokia-platform-chassis.yang:L249
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? mac_address=null¶
The configured or derived MAC address of the chassis If not configured, this is set to the hw-mac-address, which is populated depending on system type: - For systems with a discoverable chassis MAC address (either populated by an external system or present in hardware) the discovered value is populated. - For systems without a discoverable MAC address, the address is generated from a hash of the systems UUID. When deleted, will revert back to the value of hw-mac-address. This MAC address is used by the system as a base to generate MAC addresses for interfaces (when needed).
- attribute nokia_srlinux::platform::chassis_mac_address_allocation_t? mac_address_allocation=null¶
The number of MAC addresses to generate from the chassis MAC address These MAC addresses are used for interfaces that need MAC addresses generated by the system.
- attribute nokia_srlinux::types::srl_nokia_common::unicast_mac_address? secondary_mac_address=null¶
MAC address programmed as a secondary terminating MAC address on every IP interface, across all network instances If an IP packet is received on a routed subinterface and it arrives with a DMAC equal to the secondary-mac-address then it is terminated and forwarded exactly the same way it would be forwarded if it had arrived on this subinterface with a DMAC equal to the subinterface MAC address.
- attribute nokia_srlinux::types::srl_nokia_common::uuid? uuid=null¶
The system-generated or user-configured UUID for the chassis :rel parent_platform: Relation to parent container :rel power: Top-level container for chassis-wide power state
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Top-level container for chassis configuration and state
other end:
nokia_srlinux::Platform.chassis [0:1]
- relation nokia_srlinux::platform::chassis::Power power [0:1]¶
Relation to parent container Peer relation: Top-level container for chassis-wide power state
other end:
nokia_srlinux::platform::chassis::Power.parent_chassis [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupChassisYangContainer
constrainttrue
- entity nokia_srlinux::platform::Control¶
Parents:
nokia_srlinux::Base
Top-level container for control module configuration and state Yang definition can be found here: srl_nokia-platform-control.yang:L194
- attribute nokia_srlinux::platform::control_slot_t slot¶
Slot identifier for the control module This is set to ‘A’ for systems without removable control modules. :rel interface: :rel parent_platform: Relation to parent container
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Top-level container for control module configuration and state
other end:
nokia_srlinux::Platform.control [0:*]
- relation nokia_srlinux::platform::control::Interface interface [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::control::Interface.parent_control [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupControlYangContainer
constrainttrue
- entity nokia_srlinux::platform::Fabric¶
Parents:
nokia_srlinux::Base
Top-level container for fabric configuration and state Yang definition can be found here: srl_nokia-platform-fabric.yang:L59
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The administrative state of this component
- attribute nokia_srlinux::platform::fabric_slot_t slot¶
Numeric identifier for the fabric module :rel parent_platform: Relation to parent container
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Top-level container for fabric configuration and state
other end:
nokia_srlinux::Platform.fabric [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupFabricYangContainer
constrainttrue
- entity nokia_srlinux::platform::Linecard¶
Parents:
nokia_srlinux::Base
Top-level container for linecard configuration and state Yang definition can be found here: srl_nokia-platform-lc.yang:L94
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The administrative state of this component
- attribute nokia_srlinux::platform::linecard_slot_t slot¶
Numeric identifier for the linecard :rel forwarding_complex: List of forwarding complexes on the linecard :rel parent_platform: Relation to parent container
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Top-level container for linecard configuration and state
other end:
nokia_srlinux::Platform.linecard [0:*]
- relation nokia_srlinux::platform::linecard::ForwardingComplex forwarding_complex [0:*]¶
Relation to parent container Peer relation: List of forwarding complexes on the linecard
other end:
nokia_srlinux::platform::linecard::ForwardingComplex.parent_linecard [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupLinecardYangContainer
constrainttrue
- entity nokia_srlinux::platform::Redundancy¶
Parents:
nokia_srlinux::Base
Top-level container for platform redundancy Yang definition can be found here: srl_nokia-platform-redundancy.yang:L141
- Rel parent_platform:
Relation to parent container
- Rel synchronization:
Top-level container for redundancy synchronization
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Top-level container for platform redundancy
other end:
nokia_srlinux::Platform.redundancy [0:1]
- relation nokia_srlinux::platform::redundancy::Synchronization synchronization [0:1]¶
Relation to parent container Peer relation: Top-level container for redundancy synchronization
other end:
nokia_srlinux::platform::redundancy::Synchronization.parent_redundancy [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupRedundancyYangContainer
constrainttrue
- entity nokia_srlinux::platform::ResourceManagement¶
Parents:
nokia_srlinux::Base
Container for managing resources in a system-wide context Yang definition can be found here: srl_nokia-platform-resource-mgmt.yang:L43
- Rel parent_platform:
Relation to parent container
- Rel tcam:
Container for managing the allocation of TCAM banks to different applications.
- Rel unified_forwarding_resources:
Container for managing Broadcom-specific UFT resources.
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Container for managing resources in a system-wide context
other end:
nokia_srlinux::Platform.resource_management [0:1]
- relation nokia_srlinux::platform::resource_management::Tcam tcam [0:1]¶
Relation to parent container Peer relation: Container for managing the allocation of TCAM banks to different applications.
other end:
nokia_srlinux::platform::resource_management::Tcam.parent_resource_management [1]
- relation nokia_srlinux::platform::resource_management::UnifiedForwardingResources unified_forwarding_resources [0:1]¶
Relation to parent container Peer relation: Container for managing Broadcom-specific UFT resources.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupResourceManagementYangContainer
constrainttrue
- entity nokia_srlinux::platform::ResourceMonitoring¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-platform-resource-monitoring.yang:L24
- Rel datapath:
Container for monitoring datapath resources system-wide
- Rel mtu:
- Rel parent_platform:
Relation to parent container
- Rel qos:
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Platform.resource_monitoring [0:1]
- relation nokia_srlinux::platform::resource_monitoring::Datapath datapath [0:1]¶
Relation to parent container Peer relation: Container for monitoring datapath resources system-wide
other end:
nokia_srlinux::platform::resource_monitoring::Datapath.parent_resource_monitoring [1]
- relation nokia_srlinux::platform::resource_monitoring::Mtu mtu [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::resource_monitoring::Mtu.parent_resource_monitoring [1]
- relation nokia_srlinux::platform::resource_monitoring::Qos qos [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::resource_monitoring::Qos.parent_resource_monitoring [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupResourceMonitoringYangContainer
constrainttrue
- entity nokia_srlinux::platform::Vxdp¶
Parents:
nokia_srlinux::Base
Top-level container for vXDP configuration and state Yang definition can be found here: srl_nokia-platform-vxdp.yang:L132
- attribute nokia_srlinux::platform::vxdp_cpu_set_t[]? cpu_set=null¶
The list of CPUs used for vXDP PMD threads These CPUs should be isolated out-of-band of SR Linux, and are used for forwarder and NIC threads for vhost-user, physical, and lif interfaces. It is expected that the sibling of a CPU is always passed to vXDP, and in order to enforce this if a single CPU of a core is passed, vXDP will derive and bind to the undefined sibling. vXDP supports the passing of both single and both siblings together, and will perform a merge to ensure all siblings are consumed. :rel parent_platform: Relation to parent container
- relation nokia_srlinux::Platform parent_platform [1]¶
Relation to parent container Peer relation: Top-level container for vXDP configuration and state
other end:
nokia_srlinux::Platform.vxdp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::setupVxdpYangContainer
constrainttrue
- entity nokia_srlinux::platform::chassis::Power¶
Parents:
nokia_srlinux::Base
Top-level container for chassis-wide power state Yang definition can be found here: srl_nokia-platform-chassis.yang:L188
- Rel parent_chassis:
Relation to parent container
- Rel redundancy:
Top-level container for power redundancy configuration and state
- relation nokia_srlinux::platform::Chassis parent_chassis [1]¶
Relation to parent container Peer relation: Top-level container for chassis-wide power state
other end:
nokia_srlinux::platform::Chassis.power [0:1]
- relation nokia_srlinux::platform::chassis::power::Redundancy redundancy [0:1]¶
Relation to parent container Peer relation: Top-level container for power redundancy configuration and state
other end:
nokia_srlinux::platform::chassis::power::Redundancy.parent_power [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::chassis::setupPowerYangContainer
constrainttrue
- entity nokia_srlinux::platform::chassis::power::Redundancy¶
Parents:
nokia_srlinux::Base
Top-level container for power redundancy configuration and state Yang definition can be found here: srl_nokia-platform-chassis.yang:L62
- attribute nokia_srlinux::platform::chassis::power::redundancy_mode_t? mode=null¶
Set the power redundancy mode in use This only sets the level at which power redundancy will be assumed unavailable, and will not result in the powering down of components unless there is insufficient non-redundant power available. :rel parent_power: Relation to parent container
- relation nokia_srlinux::platform::chassis::Power parent_power [1]¶
Relation to parent container Peer relation: Top-level container for power redundancy configuration and state
other end:
nokia_srlinux::platform::chassis::Power.redundancy [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::control::Interface¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-platform-control.yang:L130
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Set the administrative state of this interface
- attribute string name¶
Name of a specific control module interface :rel parent_control: Relation to parent container
- relation nokia_srlinux::platform::Control parent_control [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::platform::control::setupInterfaceYangContainer
constrainttrue
- entity nokia_srlinux::platform::linecard::ForwardingComplex¶
Parents:
nokia_srlinux::Base
List of forwarding complexes on the linecard Yang definition can be found here: srl_nokia-platform-lc.yang:L120
- attribute nokia_srlinux::platform::linecard::forwarding_complex_name_t name¶
The identifier of the forwarding complex :rel buffer_memory: Container for utilization statistics of the packet buffer memory :rel fabric: Top-level container for fabric configuration and state :rel p4rt: Top-level container for P4Runtime forwarding complex configuration and state :rel parent_linecard: Relation to parent container :rel pipeline: List of pipelines that make up one forwarding complex.
- relation nokia_srlinux::platform::Linecard parent_linecard [1]¶
Relation to parent container Peer relation: List of forwarding complexes on the linecard
other end:
nokia_srlinux::platform::Linecard.forwarding_complex [0:*]
- relation nokia_srlinux::platform::linecard::forwarding_complex::BufferMemory buffer_memory [0:1]¶
Relation to parent container Peer relation: Container for utilization statistics of the packet buffer memory
other end:
nokia_srlinux::platform::linecard::forwarding_complex::BufferMemory.parent_forwarding_complex [1]
- relation nokia_srlinux::platform::linecard::forwarding_complex::Fabric fabric [0:1]¶
Relation to parent container Peer relation: Top-level container for fabric configuration and state
other end:
nokia_srlinux::platform::linecard::forwarding_complex::Fabric.parent_forwarding_complex [1]
- relation nokia_srlinux::platform::linecard::forwarding_complex::P4rt p4rt [0:1]¶
Relation to parent container Peer relation: Top-level container for P4Runtime forwarding complex configuration and state
other end:
nokia_srlinux::platform::linecard::forwarding_complex::P4rt.parent_forwarding_complex [1]
- relation nokia_srlinux::platform::linecard::forwarding_complex::Pipeline pipeline [0:*]¶
Relation to parent container Peer relation: List of pipelines that make up one forwarding complex.
other end:
nokia_srlinux::platform::linecard::forwarding_complex::Pipeline.parent_forwarding_complex [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::linecard::forwarding_complex::BufferMemory¶
Parents:
nokia_srlinux::Base
Container for utilization statistics of the packet buffer memory Yang definition can be found here: srl_nokia-platform-qos.yang:L182
- Rel parent_forwarding_complex:
Relation to parent container
- relation nokia_srlinux::platform::linecard::ForwardingComplex parent_forwarding_complex [1]¶
Relation to parent container Peer relation: Container for utilization statistics of the packet buffer memory
other end:
nokia_srlinux::platform::linecard::ForwardingComplex.buffer_memory [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::linecard::forwarding_complex::Fabric¶
Parents:
nokia_srlinux::Base
Top-level container for fabric configuration and state Yang definition can be found here: srl_nokia-platform-lc.yang:L135
- Rel parent_forwarding_complex:
Relation to parent container
- relation nokia_srlinux::platform::linecard::ForwardingComplex parent_forwarding_complex [1]¶
Relation to parent container Peer relation: Top-level container for fabric configuration and state
other end:
nokia_srlinux::platform::linecard::ForwardingComplex.fabric [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::linecard::forwarding_complex::P4rt¶
Parents:
nokia_srlinux::Base
Top-level container for P4Runtime forwarding complex configuration and state Yang definition can be found here: srl_nokia-platform-p4rt.yang:L39
- attribute nokia_srlinux::platform::linecard::forwarding_complex::p4rt_id_t? id=null¶
The numeric ID used by the controller to address the forwarding complex This ID may be referred to as a ‘device’, ‘node’ or ‘target’ by the P4RT specification. Each ASIC is addressed by the client based on this numeric identifier. :rel parent_forwarding_complex: Relation to parent container
- relation nokia_srlinux::platform::linecard::ForwardingComplex parent_forwarding_complex [1]¶
Relation to parent container Peer relation: Top-level container for P4Runtime forwarding complex configuration and state
other end:
nokia_srlinux::platform::linecard::ForwardingComplex.p4rt [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::linecard::forwarding_complex::Pipeline¶
Parents:
nokia_srlinux::Base
List of pipelines that make up one forwarding complex. Yang definition can be found here: srl_nokia-platform-lc.yang:L143
- attribute nokia_srlinux::platform::linecard::forwarding_complex::pipeline_index_t x_index¶
The pipeline number (TH3 systems) or direction (J2 and J2C+ systems). :rel parent_forwarding_complex: Relation to parent container
- relation nokia_srlinux::platform::linecard::ForwardingComplex parent_forwarding_complex [1]¶
Relation to parent container Peer relation: List of pipelines that make up one forwarding complex.
other end:
nokia_srlinux::platform::linecard::ForwardingComplex.pipeline [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::redundancy::Synchronization¶
Parents:
nokia_srlinux::Base
Top-level container for redundancy synchronization Yang definition can be found here: srl_nokia-platform-redundancy.yang:L88
- Rel overlay:
Top-level container for overlay synchronization
- Rel parent_redundancy:
Relation to parent container
- relation nokia_srlinux::platform::Redundancy parent_redundancy [1]¶
Relation to parent container Peer relation: Top-level container for redundancy synchronization
other end:
nokia_srlinux::platform::Redundancy.synchronization [0:1]
- relation nokia_srlinux::platform::redundancy::synchronization::Overlay overlay [0:1]¶
Relation to parent container Peer relation: Top-level container for overlay synchronization
other end:
nokia_srlinux::platform::redundancy::synchronization::Overlay.parent_synchronization [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::redundancy::synchronization::Overlay¶
Parents:
nokia_srlinux::Base
Top-level container for overlay synchronization Yang definition can be found here: srl_nokia-platform-redundancy.yang:L103
- attribute nokia_srlinux::platform::redundancy::synchronization::overlay_synchronization_frequency_t? synchronization_frequency=null¶
Sets the frequency of overlay synchronizations This has no effect if overlay is not a configured synchronization mode. Changing this value results in the timer to the next synchronization being reset. :rel parent_synchronization: Relation to parent container
- relation nokia_srlinux::platform::redundancy::Synchronization parent_synchronization [1]¶
Relation to parent container Peer relation: Top-level container for overlay synchronization
other end:
nokia_srlinux::platform::redundancy::Synchronization.overlay [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_management::Tcam¶
Parents:
nokia_srlinux::Base
Container for managing the allocation of TCAM banks to different applications. Yang definition can be found here: srl_nokia-platform-resource-mgmt.yang:L46
- Rel parent_resource_management:
Relation to parent container
- relation nokia_srlinux::platform::ResourceManagement parent_resource_management [1]¶
Relation to parent container Peer relation: Container for managing the allocation of TCAM banks to different applications.
other end:
nokia_srlinux::platform::ResourceManagement.tcam [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_management::UnifiedForwardingResources¶
Parents:
nokia_srlinux::Base
Container for managing Broadcom-specific UFT resources. Yang definition can be found here: srl_nokia-platform-resource-mgmt.yang:L50
- attribute nokia_srlinux::platform::resource_management::unified_forwarding_resources_alpm_t? alpm=null¶
Controls the ALPM mode. If this is set to disabled then no UFT banks are allocated to ALPM. This mode is not supported by 7220 IXR-D4 or 7220 IXR-D5. If this is set to enabled then 4 UFT shared banks are allocated to ALPM. This mode is not supported by 7220 IXR-D2 or 7220 IXR-D3. If this is set to high-scale then 8 UFT shared banks are allocated to ALPM. This mode is not supported by 7220 IXR-D1.
- attribute nokia_srlinux::platform::resource_management::unified_forwarding_resources_ipv6_128bit_lpm_entries_t? ipv6_128bit_lpm_entries=null¶
Sets the value for num_ipv6_lpm_128b_entries, which affects IP FIB scale. H2/H3 range: 0-1024 D1 range: 0-4096 D2/D3 range: 0-8192
- attribute nokia_srlinux::platform::resource_management::unified_forwarding_resources_requested_extra_ip_host_entries_t? requested_extra_ip_host_entries=null¶
The extra number of host entries that are desired. The number of UFT shared banks that are reserved for IPv4 and IPv6 host entries is given by: min(N//X,P-A) where: N = configured value of requested-extra-ip-host-entries X = the size of each shared bank, which is platform specific P-A = platform-specific number of shared banks, subtracting the ALPM banks requested-extra-ip-host-entries is interpreted in terms of IPv4 hosts (single-wide entries). IPv6 host entries are double-wide so 1 IPv4 host entry + 1 IPv6 host-entry counts as 3 entries. All UFT shared banks that are not reserved by ALPM and not reserved for extra IP host entries are used for extra MAC entries. On D1 the default value is 48K entries, which provides 3 shared banks, max is 96K. On D2/D3 the default value is 128K entries, which provides 4 shared banks, max is 256K. :rel parent_resource_management: Relation to parent container
- relation nokia_srlinux::platform::ResourceManagement parent_resource_management [1]¶
Relation to parent container Peer relation: Container for managing Broadcom-specific UFT resources.
other end:
nokia_srlinux::platform::ResourceManagement.unified_forwarding_resources [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::Datapath¶
Parents:
nokia_srlinux::Base
Container for monitoring datapath resources system-wide Yang definition can be found here: srl_nokia-platform-datapath-resources.yang:L452
- Rel asic:
Container for monitoring datapath resources that are specific to a subset of the chipsets supported by SRLinux.
- Rel parent_resource_monitoring:
Relation to parent container
- Rel xdp:
Container for monitoring datapath resources that are generic in concept.
- relation nokia_srlinux::platform::ResourceMonitoring parent_resource_monitoring [1]¶
Relation to parent container Peer relation: Container for monitoring datapath resources system-wide
other end:
nokia_srlinux::platform::ResourceMonitoring.datapath [0:1]
- relation nokia_srlinux::platform::resource_monitoring::datapath::Asic asic [0:1]¶
Relation to parent container Peer relation: Container for monitoring datapath resources that are specific to a subset of the chipsets supported by SRLinux.
other end:
nokia_srlinux::platform::resource_monitoring::datapath::Asic.parent_datapath [1]
- relation nokia_srlinux::platform::resource_monitoring::datapath::Xdp xdp [0:1]¶
Relation to parent container Peer relation: Container for monitoring datapath resources that are generic in concept.
other end:
nokia_srlinux::platform::resource_monitoring::datapath::Xdp.parent_datapath [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::Mtu¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-platform-mtu.yang:L72
- Rel parent_resource_monitoring:
Relation to parent container
- Rel x_resource:
- relation nokia_srlinux::platform::ResourceMonitoring parent_resource_monitoring [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::ResourceMonitoring.mtu [0:1]
- relation nokia_srlinux::platform::resource_monitoring::mtu::XResource x_resource [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::resource_monitoring::mtu::XResource.parent_mtu [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::Qos¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-platform-qos.yang:L125
- Rel parent_resource_monitoring:
Relation to parent container
- Rel x_resource:
- relation nokia_srlinux::platform::ResourceMonitoring parent_resource_monitoring [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::ResourceMonitoring.qos [0:1]
- relation nokia_srlinux::platform::resource_monitoring::qos::XResource x_resource [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::resource_monitoring::qos::XResource.parent_qos [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::datapath::Asic¶
Parents:
nokia_srlinux::Base
Container for monitoring datapath resources that are specific to a subset of the chipsets supported by SRLinux. Yang definition can be found here: srl_nokia-platform-datapath-resources.yang:L487
- Rel parent_datapath:
Relation to parent container
- Rel x_resource:
List of ASIC-specific datapath resources
- relation nokia_srlinux::platform::resource_monitoring::Datapath parent_datapath [1]¶
Relation to parent container Peer relation: Container for monitoring datapath resources that are specific to a subset of the chipsets supported by SRLinux.
other end:
nokia_srlinux::platform::resource_monitoring::Datapath.asic [0:1]
- relation nokia_srlinux::platform::resource_monitoring::datapath::asic::XResource x_resource [0:*]¶
Relation to parent container Peer relation: List of ASIC-specific datapath resources
other end:
nokia_srlinux::platform::resource_monitoring::datapath::asic::XResource.parent_asic [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::datapath::Xdp¶
Parents:
nokia_srlinux::Base
Container for monitoring datapath resources that are generic in concept. Yang definition can be found here: srl_nokia-platform-datapath-resources.yang:L455
- Rel parent_datapath:
Relation to parent container
- Rel x_resource:
List of generic datapath resources
- relation nokia_srlinux::platform::resource_monitoring::Datapath parent_datapath [1]¶
Relation to parent container Peer relation: Container for monitoring datapath resources that are generic in concept.
other end:
nokia_srlinux::platform::resource_monitoring::Datapath.xdp [0:1]
- relation nokia_srlinux::platform::resource_monitoring::datapath::xdp::XResource x_resource [0:*]¶
Relation to parent container Peer relation: List of generic datapath resources
other end:
nokia_srlinux::platform::resource_monitoring::datapath::xdp::XResource.parent_xdp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::datapath::asic::XResource¶
Parents:
nokia_srlinux::Base
List of ASIC-specific datapath resources Yang definition can be found here: srl_nokia-platform-datapath-resources.yang:L490
- attribute nokia_srlinux::types::srl_nokia_common::percentage? falling_threshold_log=null¶
Sets the threshold that triggers the generation of a NOTICE log whenever the utilization of the datapath resource in any linecard (if applicable) or forwarding complex or pipeline (if applicable) reaches this value in a falling direction
- attribute string name¶
The name of the ASIC-specific datapath resource.
- attribute nokia_srlinux::types::srl_nokia_common::percentage? rising_threshold_log=null¶
Sets the threshold that triggers the generation of a WARNING log whenever the utilization of the datapath resource in any linecard (if applicable) or forwarding complex or pipeline (if applicable) reaches this value in a rising direction :rel parent_asic: Relation to parent container
- relation nokia_srlinux::platform::resource_monitoring::datapath::Asic parent_asic [1]¶
Relation to parent container Peer relation: List of ASIC-specific datapath resources
other end:
nokia_srlinux::platform::resource_monitoring::datapath::Asic.x_resource [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::datapath::xdp::XResource¶
Parents:
nokia_srlinux::Base
List of generic datapath resources Yang definition can be found here: srl_nokia-platform-datapath-resources.yang:L458
- attribute nokia_srlinux::types::srl_nokia_common::percentage? falling_threshold_log=null¶
Sets the threshold that triggers the generation of a NOTICE log whenever the utilization of the datapath resource in any linecard (if applicable) or forwarding complex or pipeline (if applicable) reaches this value in a falling direction
- attribute string name¶
The name of the XDP datapath resource. Some of these resources may be software only (i.e. no correspondence to a hardware table). Some of these resources may depend on multiple HW tables and when the utilization is reported it represents an aggregated or summarized view.
- attribute nokia_srlinux::types::srl_nokia_common::percentage? rising_threshold_log=null¶
Sets the threshold that triggers the generation of a WARNING log whenever the utilization of the datapath resource in any linecard (if applicable) or forwarding complex or pipeline (if applicable) reaches this value in a rising direction :rel parent_xdp: Relation to parent container
- relation nokia_srlinux::platform::resource_monitoring::datapath::Xdp parent_xdp [1]¶
Relation to parent container Peer relation: List of generic datapath resources
other end:
nokia_srlinux::platform::resource_monitoring::datapath::Xdp.x_resource [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::mtu::XResource¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-platform-mtu.yang:L73
- attribute nokia_srlinux::types::srl_nokia_common::percentage? falling_threshold_log=null¶
Sets the threshold that triggers the generation of a NOTICE log whenever the utilization of the MTU resource in any linecard/complex/core reaches this value in a falling direction and this is the first trigger since the last rising-threshold-log was triggered.
- attribute string name¶
The name of the MTU resource
- attribute nokia_srlinux::types::srl_nokia_common::percentage? rising_threshold_log=null¶
Sets the threshold that triggers the generation of a WARNING log whenever the utilization of the MTU resource in any linecard/complex/core reaches this value in a rising direction and this is the first trigger since the last restart or since the last falling-threshold-log was triggered. :rel parent_mtu: Relation to parent container
- relation nokia_srlinux::platform::resource_monitoring::Mtu parent_mtu [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::resource_monitoring::Mtu.x_resource [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::platform::resource_monitoring::qos::XResource¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-platform-qos.yang:L128
- attribute nokia_srlinux::types::srl_nokia_common::percentage? falling_threshold_log=null¶
Sets the threshold that triggers the generation of a NOTICE log whenever the utilization of the QoS resource in any linecard/complex/core falls reaches this value in a falling direction
- attribute string name¶
The name of the QoS resource
- attribute nokia_srlinux::types::srl_nokia_common::percentage? rising_threshold_log=null¶
Sets the threshold that triggers the generation of a WARNING log whenever the utilization of the QoS resource in any linecard/complex/core reaches this value in a rising direction :rel parent_qos: Relation to parent container
- relation nokia_srlinux::platform::resource_monitoring::Qos parent_qos [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::platform::resource_monitoring::Qos.x_resource [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::AsPathSet¶
Parents:
nokia_srlinux::Base
AS Path regular expressions for use in policy entries Yang definition can be found here: srl_nokia-routing-policy.yang:L101
- attribute nokia_srlinux::types::srl_nokia_policy_types::as_path_regexp? expression=null¶
A regular expression where each AS number is an elemental term
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A name used to identify the AS path regular expression :rel parent_routing_policy: Relation to parent container
- relation nokia_srlinux::RoutingPolicy parent_routing_policy [1]¶
Relation to parent container Peer relation: AS Path regular expressions for use in policy entries
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::routing_policy::setupAsPathSetYangContainer
constrainttrue
- entity nokia_srlinux::routing_policy::CommunitySet¶
Parents:
nokia_srlinux::Base
List of BGP community sets containing standard and large BGP communities Yang definition can be found here: srl_nokia-routing-policy.yang:L153
- attribute nokia_srlinux::routing_policy::community_set_member_t[]? member=null¶
A standard BGP community value, regular expression or well-known name or else a large BGP community value or regular expression
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A name used to identify the community set :rel parent_routing_policy: Relation to parent container
- relation nokia_srlinux::RoutingPolicy parent_routing_policy [1]¶
Relation to parent container Peer relation: List of BGP community sets containing standard and large BGP communities
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::routing_policy::setupCommunitySetYangContainer
constrainttrue
- entity nokia_srlinux::routing_policy::Policy¶
Parents:
nokia_srlinux::Base
List of policy definitions, keyed by unique name These policy definitions are expected to be referenced (by name) in policy in import-policy and/or export-policy statements. Yang definition can be found here: srl_nokia-routing-policy.yang:L575
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A name used to identify the policy :rel default_action: Actions for routes that do not match any policy entry :rel parent_routing_policy: Relation to parent container :rel statement: Policy statements group conditions and actions within a policy definition. They are evaluated in configuration order. WARNING: The model specifies that the order of the elements in this relation matters. This is not currently supported by this model.
- relation nokia_srlinux::RoutingPolicy parent_routing_policy [1]¶
Relation to parent container Peer relation: List of policy definitions, keyed by unique name These policy definitions are expected to be referenced (by name) in policy in import-policy and/or export-policy statements.
other end:
nokia_srlinux::RoutingPolicy.policy [0:*]
- relation nokia_srlinux::routing_policy::policy::DefaultAction default_action [0:1]¶
Relation to parent container Peer relation: Actions for routes that do not match any policy entry
other end:
nokia_srlinux::routing_policy::policy::DefaultAction.parent_policy [1]
- relation nokia_srlinux::routing_policy::policy::Statement statement [0:*]¶
Relation to parent container Peer relation: Policy statements group conditions and actions within a policy definition. They are evaluated in configuration order. WARNING: The model specifies that the order of the elements in this relation matters. This is not currently supported by this model.
other end:
nokia_srlinux::routing_policy::policy::Statement.parent_policy [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::routing_policy::setupPolicyYangContainer
constrainttrue
- entity nokia_srlinux::routing_policy::PrefixSet¶
Parents:
nokia_srlinux::Base
List of defined prefix sets Yang definition can be found here: srl_nokia-routing-policy.yang:L119
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A name used to identify the prefix set :rel parent_routing_policy: Relation to parent container :rel prefix: List of prefixes in the prefix set
- relation nokia_srlinux::RoutingPolicy parent_routing_policy [1]¶
Relation to parent container Peer relation: List of defined prefix sets
- relation nokia_srlinux::routing_policy::prefix_set::Prefix prefix [0:*]¶
Relation to parent container Peer relation: List of prefixes in the prefix set
other end:
nokia_srlinux::routing_policy::prefix_set::Prefix.parent_prefix_set [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::routing_policy::setupPrefixSetYangContainer
constrainttrue
- entity nokia_srlinux::routing_policy::TagSet¶
Parents:
nokia_srlinux::Base
List of administrative tag sets Yang definition can be found here: srl_nokia-routing-policy.yang:L169
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A name used to identify the tag set :rel parent_routing_policy: Relation to parent container
- relation nokia_srlinux::RoutingPolicy parent_routing_policy [1]¶
Relation to parent container Peer relation: List of administrative tag sets
other end:
nokia_srlinux::RoutingPolicy.tag_set [0:255]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::routing_policy::setupTagSetYangContainer
constrainttrue
- entity nokia_srlinux::routing_policy::policy::DefaultAction¶
Parents:
nokia_srlinux::Base
Actions for routes that do not match any policy entry Yang definition can be found here: srl_nokia-routing-policy.yang:L339
- attribute nokia_srlinux::types::srl_nokia_policy_types::policy_result_type? policy_result=null¶
Select the final disposition for the route. :rel bgp: :rel internal_tags: Configuration of internal tags :rel parent_policy: Relation to parent container :rel route_preference: Options for modifying route preference
- relation nokia_srlinux::routing_policy::Policy parent_policy [1]¶
Relation to parent container Peer relation: Actions for routes that do not match any policy entry
other end:
nokia_srlinux::routing_policy::Policy.default_action [0:1]
- relation nokia_srlinux::routing_policy::policy::default_action::Bgp bgp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::Bgp.parent_default_action [1]
- relation nokia_srlinux::routing_policy::policy::default_action::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration of internal tags
other end:
nokia_srlinux::routing_policy::policy::default_action::InternalTags.parent_default_action [1]
- relation nokia_srlinux::routing_policy::policy::default_action::RoutePreference route_preference [0:1]¶
Relation to parent container Peer relation: Options for modifying route preference
other end:
nokia_srlinux::routing_policy::policy::default_action::RoutePreference.parent_default_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::Statement¶
Parents:
nokia_srlinux::Base
Policy statements group conditions and actions within a policy definition. They are evaluated in configuration order. Yang definition can be found here: srl_nokia-routing-policy.yang:L557
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name given to the policy statement (rule). :rel action: Actions for routes that match the policy statement :rel match: Match conditions of the policy statement :rel parent_policy: Relation to parent container
- relation nokia_srlinux::routing_policy::Policy parent_policy [1]¶
Relation to parent container Peer relation: Policy statements group conditions and actions within a policy definition. They are evaluated in configuration order. WARNING: The model specifies that the order of the elements in this relation matters. This is not currently supported by this model.
other end:
nokia_srlinux::routing_policy::Policy.statement [0:*]
- relation nokia_srlinux::routing_policy::policy::statement::Action action [0:1]¶
Relation to parent container Peer relation: Actions for routes that match the policy statement
other end:
nokia_srlinux::routing_policy::policy::statement::Action.parent_statement [1]
- relation nokia_srlinux::routing_policy::policy::statement::Match match [0:1]¶
Relation to parent container Peer relation: Match conditions of the policy statement
other end:
nokia_srlinux::routing_policy::policy::statement::Match.parent_statement [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::Bgp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L227
- Rel as_path:
Modify AS Path attribute of routes
- Rel communities:
Modify BGP communities attached to routes
- Rel local_preference:
- Rel med:
- Rel origin:
- Rel parent_default_action:
Relation to parent container
- relation nokia_srlinux::routing_policy::policy::DefaultAction parent_default_action [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::DefaultAction.bgp [0:1]
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::AsPath as_path [0:1]¶
Relation to parent container Peer relation: Modify AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::AsPath.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::Communities communities [0:1]¶
Relation to parent container Peer relation: Modify BGP communities attached to routes
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::Communities.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::LocalPreference local_preference [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::LocalPreference.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::Med med [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::Med.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::Origin origin [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::Origin.parent_bgp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration of internal tags Yang definition can be found here: srl_nokia-routing-policy.yang:L192
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_default_action: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::DefaultAction parent_default_action [1]¶
Relation to parent container Peer relation: Configuration of internal tags
other end:
nokia_srlinux::routing_policy::policy::DefaultAction.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::RoutePreference¶
Parents:
nokia_srlinux::Base
Options for modifying route preference Yang definition can be found here: srl_nokia-routing-policy.yang:L208
- attribute yang::types::uint8? set=null¶
Overwrite the route preference with the specified value The IP route table preference is sometimes called the administrative distance of the route. In general, when comparing any two routes, the route with the lower preference is the one that is activated and used for forwarding. This action has an effect only in BGP import policies and VRF import policies :rel parent_default_action: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::DefaultAction parent_default_action [1]¶
Relation to parent container Peer relation: Options for modifying route preference
other end:
nokia_srlinux::routing_policy::policy::DefaultAction.route_preference [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::bgp::AsPath¶
Parents:
nokia_srlinux::Base
Modify AS Path attribute of routes Yang definition can be found here: srl_nokia-routing-policy.yang:L228
- attribute bool? remove=null¶
Clear the AS path to make it empty.
- attribute nokia_srlinux::types::srl_nokia_policy_types::as_number[]? replace=null¶
Clear the existing AS path and replace it a new AS_SEQUENCE containing the listed AS numbers. :rel parent_bgp: Relation to parent container :rel prepend: Prepend a BGP AS number to the AS Path attribute of routes
- relation nokia_srlinux::routing_policy::policy::default_action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Modify AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::default_action::Bgp.as_path [0:1]
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::as_path::Prepend prepend [0:1]¶
Relation to parent container Peer relation: Prepend a BGP AS number to the AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::as_path::Prepend.parent_as_path [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::bgp::Communities¶
Parents:
nokia_srlinux::Base
Modify BGP communities attached to routes Yang definition can be found here: srl_nokia-routing-policy.yang:L269
- attribute string? add=null¶
Reference to a community-set name All of the non-regex community members in the referenced community-set are added to the COMMUNTIES and LARGE_COMMUNITIES attributes.
- attribute string? remove=null¶
Reference to a community-set name The communities in the route are compared to all of the community members in the referenced community-set, and all matching communities are removed from the COMMUNITIES and LARGE_COMMUNITIES attributes.
- attribute string? replace=null¶
Reference to a community-set name All of the existing communities are deleted and then all of the non-regex community members in the referenced community-set are encoded in new COMMUNTIES and LARGE_COMMUNITIES attributes. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::default_action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Modify BGP communities attached to routes
other end:
nokia_srlinux::routing_policy::policy::default_action::Bgp.communities [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::bgp::LocalPreference¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L301
- attribute yang::types::uint32? set=null¶
The new value of LOCAL_PREF to write into the matching BGP routes :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::default_action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::Bgp.local_preference [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::bgp::Med¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L308
- attribute nokia_srlinux::routing_policy::policy::default_action::bgp::med_set_t? set=null¶
The new value of the Multi-Exit Discriminator attribute value to write into the matching BGP routes. The route-table-cost option derives the MED from the route metric. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::default_action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::Bgp.med [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::bgp::Origin¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L321
- attribute nokia_srlinux::routing_policy::policy::default_action::bgp::origin_set_t? set=null¶
The new value of the ORIGIN attribute to write into the matching BGP routes :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::default_action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::default_action::Bgp.origin [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::default_action::bgp::as_path::Prepend¶
Parents:
nokia_srlinux::Base
Prepend a BGP AS number to the AS Path attribute of routes Yang definition can be found here: srl_nokia-routing-policy.yang:L243
- attribute nokia_srlinux::routing_policy::policy::default_action::bgp::as_path::prepend_as_number_t? as_number=null¶
The AS number to prepend to the AS Path attributes If ‘auto’ is specified then the peer’s AS number is used in the context of an import policy and the local AS number is used in the context of an export policy.
- attribute nokia_srlinux::routing_policy::policy::default_action::bgp::as_path::prepend_repeat_n_t? repeat_n=null¶
The number of repetitions of the prepended AS number :rel parent_as_path: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::default_action::bgp::AsPath parent_as_path [1]¶
Relation to parent container Peer relation: Prepend a BGP AS number to the AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::default_action::bgp::AsPath.prepend [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::Action¶
Parents:
nokia_srlinux::Base
Actions for routes that match the policy statement Yang definition can be found here: srl_nokia-routing-policy.yang:L541
- attribute nokia_srlinux::types::srl_nokia_policy_types::policy_result_type? policy_result=null¶
Select the final disposition for the route. :rel bgp: :rel internal_tags: Configuration of internal tags :rel parent_statement: Relation to parent container :rel route_preference: Options for modifying route preference
- relation nokia_srlinux::routing_policy::policy::Statement parent_statement [1]¶
Relation to parent container Peer relation: Actions for routes that match the policy statement
other end:
nokia_srlinux::routing_policy::policy::Statement.action [0:1]
- relation nokia_srlinux::routing_policy::policy::statement::action::Bgp bgp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::Bgp.parent_action [1]
- relation nokia_srlinux::routing_policy::policy::statement::action::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration of internal tags
other end:
nokia_srlinux::routing_policy::policy::statement::action::InternalTags.parent_action [1]
- relation nokia_srlinux::routing_policy::policy::statement::action::RoutePreference route_preference [0:1]¶
Relation to parent container Peer relation: Options for modifying route preference
other end:
nokia_srlinux::routing_policy::policy::statement::action::RoutePreference.parent_action [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::Match¶
Parents:
nokia_srlinux::Base
Match conditions of the policy statement Yang definition can be found here: srl_nokia-routing-policy.yang:L527
- attribute nokia_srlinux::types::srl_nokia_policy_types::bgp_family_type[]? family=null¶
The name of an address family A route meets this condition if the prefix belongs to one of the indicated address families.
- attribute string? prefix_set=null¶
Reference to a prefix set name
- attribute string? protocol=null¶
The route type to match :rel bgp: Configuration for BGP-specific policy match criteria :rel internal_tags: Configuration and state of internal tags :rel isis: Configuration for ISIS-specific policy match criteria :rel ospf: Configuration for OSPF-specific policy match criteria :rel parent_statement: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::Statement parent_statement [1]¶
Relation to parent container Peer relation: Match conditions of the policy statement
other end:
nokia_srlinux::routing_policy::policy::Statement.match [0:1]
- relation nokia_srlinux::routing_policy::policy::statement::match::Bgp bgp [0:1]¶
Relation to parent container Peer relation: Configuration for BGP-specific policy match criteria
other end:
nokia_srlinux::routing_policy::policy::statement::match::Bgp.parent_match [1]
- relation nokia_srlinux::routing_policy::policy::statement::match::InternalTags internal_tags [0:1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::routing_policy::policy::statement::match::InternalTags.parent_match [1]
- relation nokia_srlinux::routing_policy::policy::statement::match::Isis isis [0:1]¶
Relation to parent container Peer relation: Configuration for ISIS-specific policy match criteria
other end:
nokia_srlinux::routing_policy::policy::statement::match::Isis.parent_match [1]
- relation nokia_srlinux::routing_policy::policy::statement::match::Ospf ospf [0:1]¶
Relation to parent container Peer relation: Configuration for OSPF-specific policy match criteria
other end:
nokia_srlinux::routing_policy::policy::statement::match::Ospf.parent_match [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::Bgp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L227
- Rel as_path:
Modify AS Path attribute of routes
- Rel communities:
Modify BGP communities attached to routes
- Rel local_preference:
- Rel med:
- Rel origin:
- Rel parent_action:
Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Action parent_action [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::Action.bgp [0:1]
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::AsPath as_path [0:1]¶
Relation to parent container Peer relation: Modify AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::AsPath.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::Communities communities [0:1]¶
Relation to parent container Peer relation: Modify BGP communities attached to routes
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::Communities.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::LocalPreference local_preference [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::LocalPreference.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::Med med [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::Med.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::Origin origin [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::Origin.parent_bgp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration of internal tags Yang definition can be found here: srl_nokia-routing-policy.yang:L192
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_action: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Action parent_action [1]¶
Relation to parent container Peer relation: Configuration of internal tags
other end:
nokia_srlinux::routing_policy::policy::statement::Action.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::RoutePreference¶
Parents:
nokia_srlinux::Base
Options for modifying route preference Yang definition can be found here: srl_nokia-routing-policy.yang:L208
- attribute yang::types::uint8? set=null¶
Overwrite the route preference with the specified value The IP route table preference is sometimes called the administrative distance of the route. In general, when comparing any two routes, the route with the lower preference is the one that is activated and used for forwarding. This action has an effect only in BGP import policies and VRF import policies :rel parent_action: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Action parent_action [1]¶
Relation to parent container Peer relation: Options for modifying route preference
other end:
nokia_srlinux::routing_policy::policy::statement::Action.route_preference [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::bgp::AsPath¶
Parents:
nokia_srlinux::Base
Modify AS Path attribute of routes Yang definition can be found here: srl_nokia-routing-policy.yang:L228
- attribute bool? remove=null¶
Clear the AS path to make it empty.
- attribute nokia_srlinux::types::srl_nokia_policy_types::as_number[]? replace=null¶
Clear the existing AS path and replace it a new AS_SEQUENCE containing the listed AS numbers. :rel parent_bgp: Relation to parent container :rel prepend: Prepend a BGP AS number to the AS Path attribute of routes
- relation nokia_srlinux::routing_policy::policy::statement::action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Modify AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::statement::action::Bgp.as_path [0:1]
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::Prepend prepend [0:1]¶
Relation to parent container Peer relation: Prepend a BGP AS number to the AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::Prepend.parent_as_path [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::bgp::Communities¶
Parents:
nokia_srlinux::Base
Modify BGP communities attached to routes Yang definition can be found here: srl_nokia-routing-policy.yang:L269
- attribute string? add=null¶
Reference to a community-set name All of the non-regex community members in the referenced community-set are added to the COMMUNTIES and LARGE_COMMUNITIES attributes.
- attribute string? remove=null¶
Reference to a community-set name The communities in the route are compared to all of the community members in the referenced community-set, and all matching communities are removed from the COMMUNITIES and LARGE_COMMUNITIES attributes.
- attribute string? replace=null¶
Reference to a community-set name All of the existing communities are deleted and then all of the non-regex community members in the referenced community-set are encoded in new COMMUNTIES and LARGE_COMMUNITIES attributes. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Modify BGP communities attached to routes
other end:
nokia_srlinux::routing_policy::policy::statement::action::Bgp.communities [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::bgp::LocalPreference¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L301
- attribute yang::types::uint32? set=null¶
The new value of LOCAL_PREF to write into the matching BGP routes :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::Bgp.local_preference [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::bgp::Med¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L308
- attribute nokia_srlinux::routing_policy::policy::statement::action::bgp::med_set_t? set=null¶
The new value of the Multi-Exit Discriminator attribute value to write into the matching BGP routes. The route-table-cost option derives the MED from the route metric. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::Bgp.med [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::bgp::Origin¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-routing-policy.yang:L321
- attribute nokia_srlinux::routing_policy::policy::statement::action::bgp::origin_set_t? set=null¶
The new value of the ORIGIN attribute to write into the matching BGP routes :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::action::Bgp parent_bgp [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::routing_policy::policy::statement::action::Bgp.origin [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::Prepend¶
Parents:
nokia_srlinux::Base
Prepend a BGP AS number to the AS Path attribute of routes Yang definition can be found here: srl_nokia-routing-policy.yang:L243
- attribute nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::prepend_as_number_t? as_number=null¶
The AS number to prepend to the AS Path attributes If ‘auto’ is specified then the peer’s AS number is used in the context of an import policy and the local AS number is used in the context of an export policy.
- attribute nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::prepend_repeat_n_t? repeat_n=null¶
The number of repetitions of the prepended AS number :rel parent_as_path: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::action::bgp::AsPath parent_as_path [1]¶
Relation to parent container Peer relation: Prepend a BGP AS number to the AS Path attribute of routes
other end:
nokia_srlinux::routing_policy::policy::statement::action::bgp::AsPath.prepend [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::match::Bgp¶
Parents:
nokia_srlinux::Base
Configuration for BGP-specific policy match criteria Yang definition can be found here: srl_nokia-routing-policy.yang:L379
- attribute string? as_path_set=null¶
Reference to an as-path-set name A route meets this condition if it matches the regular expression
- attribute string? community_set=null¶
Reference to a community-set name A route meets this condition if has any community value matching a community member in the referenced community-set :rel as_path_length: A BGP route matches this condition if the number of (unique) AS numbers in its AS_PATH matches this value or the range implied by the value+operator. :rel evpn: Container for match conditions that are specific to BGP EVPN routes. :rel parent_match: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Match parent_match [1]¶
Relation to parent container Peer relation: Configuration for BGP-specific policy match criteria
other end:
nokia_srlinux::routing_policy::policy::statement::Match.bgp [0:1]
- relation nokia_srlinux::routing_policy::policy::statement::match::bgp::AsPathLength as_path_length [0:1]¶
Relation to parent container Peer relation: A BGP route matches this condition if the number of (unique) AS numbers in its AS_PATH matches this value or the range implied by the value+operator.
other end:
nokia_srlinux::routing_policy::policy::statement::match::bgp::AsPathLength.parent_bgp [1]
- relation nokia_srlinux::routing_policy::policy::statement::match::bgp::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Container for match conditions that are specific to BGP EVPN routes.
other end:
nokia_srlinux::routing_policy::policy::statement::match::bgp::Evpn.parent_bgp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::match::InternalTags¶
Parents:
nokia_srlinux::Base
Configuration and state of internal tags Yang definition can be found here: srl_nokia-routing-policy.yang:L509
- attribute string[]? tag_set=null¶
Reference to a tag-set defined under routing-policy :rel parent_match: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Match parent_match [1]¶
Relation to parent container Peer relation: Configuration and state of internal tags
other end:
nokia_srlinux::routing_policy::policy::statement::Match.internal_tags [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::match::Isis¶
Parents:
nokia_srlinux::Base
Configuration for ISIS-specific policy match criteria Yang definition can be found here: srl_nokia-routing-policy.yang:L445
- attribute nokia_srlinux::routing_policy::policy::statement::match::isis_level_t? level=null¶
IS-IS route level
- attribute nokia_srlinux::routing_policy::policy::statement::match::isis_route_type_t? route_type=null¶
An IS-IS IPv4 prefix is external if it is signalled in TLV 130 or TLV135 with RFC 7794 X flag=1. An IS-IS IPv6 prefix is external if the TLV 236/TLV 237 external bit = 1. :rel parent_match: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Match parent_match [1]¶
Relation to parent container Peer relation: Configuration for ISIS-specific policy match criteria
other end:
nokia_srlinux::routing_policy::policy::statement::Match.isis [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::match::Ospf¶
Parents:
nokia_srlinux::Base
Configuration for OSPF-specific policy match criteria Yang definition can be found here: srl_nokia-routing-policy.yang:L471
- attribute nokia_srlinux::types::srl_nokia_ospf_types::ospf_area_identifier? area_id=null¶
The area identifier as a dotted-quad.
- attribute nokia_srlinux::routing_policy::policy::statement::match::ospf_instance_id_t? instance_id=null¶
OSPFv3 instance identifier
- attribute string? route_type=null¶
The OSPF route type. :rel parent_match: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::Match parent_match [1]¶
Relation to parent container Peer relation: Configuration for OSPF-specific policy match criteria
other end:
nokia_srlinux::routing_policy::policy::statement::Match.ospf [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::match::bgp::AsPathLength¶
Parents:
nokia_srlinux::Base
A BGP route matches this condition if the number of (unique) AS numbers in its AS_PATH matches this value or the range implied by the value+operator. Yang definition can be found here: srl_nokia-routing-policy.yang:L391
- attribute nokia_srlinux::types::srl_nokia_policy_types::comparison_operator_type? operator=null¶
The comparison operator that applies to the value
- attribute bool? unique=null¶
Count a repeated sequence of the same AS number as just 1 element
- attribute nokia_srlinux::routing_policy::policy::statement::match::bgp::as_path_length_value_t? value=null¶
The number of (unique) AS numbers in the AS path :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::match::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: A BGP route matches this condition if the number of (unique) AS numbers in its AS_PATH matches this value or the range implied by the value+operator.
other end:
nokia_srlinux::routing_policy::policy::statement::match::Bgp.as_path_length [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::policy::statement::match::bgp::Evpn¶
Parents:
nokia_srlinux::Base
Container for match conditions that are specific to BGP EVPN routes. Yang definition can be found here: srl_nokia-routing-policy.yang:L364
- attribute nokia_srlinux::routing_policy::policy::statement::match::bgp::evpn_route_type_t[]? route_type=null¶
An EVPN route meets this condition if the route-type field in the NLRI is one of the values provided in this list. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::routing_policy::policy::statement::match::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: Container for match conditions that are specific to BGP EVPN routes.
other end:
nokia_srlinux::routing_policy::policy::statement::match::Bgp.evpn [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::routing_policy::prefix_set::Prefix¶
Parents:
nokia_srlinux::Base
List of prefixes in the prefix set Yang definition can be found here: srl_nokia-routing-policy.yang:L76
- attribute nokia_srlinux::routing_policy::prefix_set::prefix_ip_prefix_t ip_prefix¶
The IPv4 or IPv6 prefix in CIDR notation
- attribute nokia_srlinux::routing_policy::prefix_set::prefix_mask_length_range_t mask_length_range¶
The range of prefix lengths to match Example: 10.3.192.0/21 through 10.3.192.0/24 would be expressed as prefix: 10.3.192.0/21, mask-length-range: 21..24. Example: 10.3.192.0/21 would be expressed as prefix: 10.3.192.0/21, mask-length-range: exact :rel parent_prefix_set: Relation to parent container
- relation nokia_srlinux::routing_policy::PrefixSet parent_prefix_set [1]¶
Relation to parent container Peer relation: List of prefixes in the prefix set
other end:
nokia_srlinux::routing_policy::PrefixSet.prefix [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::Aaa¶
Parents:
nokia_srlinux::Base
Top-level container for AAA services Yang definition can be found here: srl_nokia-aaa.yang:L849
- Rel accounting:
Top-level container for accounting
- Rel authentication:
Top-level container for global authentication data
- Rel authorization:
Top-level container for authorization configuration and operational state data
- Rel parent_system:
Relation to parent container
- Rel server_group:
List of AAA server-groups in the system
Each server group specifies a type, of which all servers must use. If using the ‘local’ type, then no servers may be specified.
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for AAA services
other end:
nokia_srlinux::System.aaa [0:1]
- relation nokia_srlinux::system::aaa::Accounting accounting [0:1]¶
Relation to parent container Peer relation: Top-level container for accounting
other end:
nokia_srlinux::system::aaa::Accounting.parent_aaa [1]
- relation nokia_srlinux::system::aaa::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Top-level container for global authentication data
other end:
nokia_srlinux::system::aaa::Authentication.parent_aaa [1]
- relation nokia_srlinux::system::aaa::Authorization authorization [0:1]¶
Relation to parent container Peer relation: Top-level container for authorization configuration and operational state data
other end:
nokia_srlinux::system::aaa::Authorization.parent_aaa [1]
- relation nokia_srlinux::system::aaa::ServerGroup server_group [0:3]¶
Relation to parent container Peer relation: List of AAA server-groups in the system
Each server group specifies a type, of which all servers must use. If using the ‘local’ type, then no servers may be specified.
other end:
nokia_srlinux::system::aaa::ServerGroup.parent_aaa [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupAaaYangContainer
constrainttrue
- entity nokia_srlinux::system::Authentication¶
Parents:
nokia_srlinux::Base
Container for protocol authentication options available system wide Yang definition can be found here: srl_nokia-keychains.yang:L125
- Rel keychain:
List of system keychains
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Container for protocol authentication options available system wide
other end:
nokia_srlinux::System.authentication [0:1]
- relation nokia_srlinux::system::authentication::Keychain keychain [0:1024]¶
Relation to parent container Peer relation: List of system keychains
other end:
nokia_srlinux::system::authentication::Keychain.parent_authentication [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupAuthenticationYangContainer
constrainttrue
- entity nokia_srlinux::system::Banner¶
Parents:
nokia_srlinux::Base
Contains configuration and state related to system banners Yang definition can be found here: srl_nokia-system-banner.yang:L24
- attribute string? login_banner=null¶
Banner to display before a user has authenticated
- attribute string? motd_banner=null¶
Banner to display after a user has authenticated :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Contains configuration and state related to system banners
other end:
nokia_srlinux::System.banner [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupBannerYangContainer
constrainttrue
- entity nokia_srlinux::system::Boot¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state data related to booting the system Yang definition can be found here: srl_nokia-boot.yang:L136
- Rel autoboot:
Top-level container for configuration and state data related to autobooting the system
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to booting the system
other end:
nokia_srlinux::System.boot [0:1]
- relation nokia_srlinux::system::boot::Autoboot autoboot [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to autobooting the system
other end:
nokia_srlinux::system::boot::Autoboot.parent_boot [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupBootYangContainer
constrainttrue
- entity nokia_srlinux::system::BridgeTable¶
Parents:
nokia_srlinux::Base
system bridge-table information Yang definition can be found here: srl_nokia-system-bridge-table.yang:L116
- Rel mac_learning:
- Rel mac_limit:
Bridge Table size and thresholds.
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: system bridge-table information
other end:
nokia_srlinux::System.bridge_table [0:1]
- relation nokia_srlinux::system::bridge_table::MacLearning mac_learning [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::bridge_table::MacLearning.parent_bridge_table [1]
- relation nokia_srlinux::system::bridge_table::MacLimit mac_limit [0:1]¶
Relation to parent container Peer relation: Bridge Table size and thresholds.
other end:
nokia_srlinux::system::bridge_table::MacLimit.parent_bridge_table [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupBridgeTableYangContainer
constrainttrue
- entity nokia_srlinux::system::Clock¶
Parents:
nokia_srlinux::Base
Top-level container for system clock configuration and state Yang definition can be found here: srl_nokia-ntp.yang:L192
- attribute nokia_srlinux::types::srl_nokia_timezone::tzdata_timezone? timezone=null¶
The timezone to use for the system Based on IANAs Time Zone database :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for system clock configuration and state
other end:
nokia_srlinux::System.clock [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupClockYangContainer
constrainttrue
- entity nokia_srlinux::system::Configuration¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state data related to the system configuration Yang definition can be found here: srl_nokia-configuration.yang:L312
- attribute bool? auto_checkpoint=null¶
Configuration checkpoint will be automatically created after every successful commit (if set to true).
- attribute yang::types::uint16? idle_timeout=null¶
The idle timeout of configuration candidates After this period of no activity, the candidate is emptied and removed from the system.
- attribute nokia_srlinux::system::configuration_max_candidates_t? max_candidates=null¶
The maximum number of combined private and shared candidates
- attribute nokia_srlinux::system::configuration_max_checkpoints_t? max_checkpoints=null¶
The number of checkpoints kept by the system :rel parent_system: Relation to parent container :rel role: List of roles configured in the system
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to the system configuration
other end:
nokia_srlinux::System.configuration [0:1]
- relation nokia_srlinux::system::configuration::Role role [0:32]¶
Relation to parent container Peer relation: List of roles configured in the system
other end:
nokia_srlinux::system::configuration::Role.parent_configuration [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupConfigurationYangContainer
constrainttrue
- entity nokia_srlinux::system::DhcpServer¶
Parents:
nokia_srlinux::Base
Configures the dhcp server Yang definition can be found here: srl_nokia-dhcp-server.yang:L260
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Globally enable or disable the dhcp server Disabling this will disable all dhcp servers. :rel network_instance: List of network instances to run a dhcp server in :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Configures the dhcp server
other end:
nokia_srlinux::System.dhcp_server [0:1]
- relation nokia_srlinux::system::dhcp_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network instances to run a dhcp server in
other end:
nokia_srlinux::system::dhcp_server::NetworkInstance.parent_dhcp_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupDhcpServerYangContainer
constrainttrue
- entity nokia_srlinux::system::Dns¶
Parents:
nokia_srlinux::Base
Top-level container for DNS configuration and state Yang definition can be found here: srl_nokia-dns.yang:L69
- attribute string? network_instance=null¶
Reference to a configured network-instance to source DNS requests from
- attribute nokia_srlinux::types::srl_nokia_common::domain_name[]? search_list=null¶
An ordered list of domains to search when resolving a host name
- attribute nokia_srlinux::system::dns_server_list_t[]? server_list=null¶
List of the DNS servers that the resolver should query :rel host_entry: List of static host entries :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for DNS configuration and state
other end:
nokia_srlinux::System.dns [0:1]
- relation nokia_srlinux::system::dns::HostEntry host_entry [0:*]¶
Relation to parent container Peer relation: List of static host entries
other end:
nokia_srlinux::system::dns::HostEntry.parent_dns [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupDnsYangContainer
constrainttrue
- entity nokia_srlinux::system::EventHandler¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state of event handler and event handling instances Yang definition can be found here: srl_nokia-event-handler.yang:L214
- attribute nokia_srlinux::system::event_handler_run_as_user_t? run_as_user=null¶
The user to run event handler instances as If no user is configured, scripts are executed as the ‘admin’ user. :rel instance: List of all event handler instances An event handler instance consists of a set of paths to be monitored for changes, and a Python script to execute if changes occur. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state of event handler and event handling instances
other end:
nokia_srlinux::System.event_handler [0:1]
- relation nokia_srlinux::system::event_handler::Instance instance [0:20]¶
Relation to parent container Peer relation: List of all event handler instances
An event handler instance consists of a set of paths to be monitored for changes, and a Python script to execute if changes occur.
other end:
nokia_srlinux::system::event_handler::Instance.parent_event_handler [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupEventHandlerYangContainer
constrainttrue
- entity nokia_srlinux::system::FtpServer¶
Parents:
nokia_srlinux::Base
Top-level container for FTP server configuration and state Yang definition can be found here: srl_nokia-ftp.yang:L93
- Rel network_instance:
List of network-instances to run an FTP server in
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for FTP server configuration and state
other end:
nokia_srlinux::System.ftp_server [0:1]
- relation nokia_srlinux::system::ftp_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network-instances to run an FTP server in
other end:
nokia_srlinux::system::ftp_server::NetworkInstance.parent_ftp_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupFtpServerYangContainer
constrainttrue
- entity nokia_srlinux::system::GnmiServer¶
Parents:
nokia_srlinux::Base
Configures the gNMI server access API Yang definition can be found here: srl_nokia-gnmi-server.yang:L262
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Globally enable or disable the gNMI server Disabling this will disable all gNMI servers.
- attribute nokia_srlinux::system::gnmi_server_commit_confirmed_timeout_t? commit_confirmed_timeout=null¶
Number of seconds to wait for confirmation. A value of 0 means commit confirmed is not used
- attribute bool? commit_save=null¶
Specifies whether to save startup configuration after every successful commit
- attribute bool? include_defaults_in_config_only_responses=null¶
Specifies whether to include field default values in get/subscribe responses when using configuration only datastore (for example running/intended datastore)
- attribute nokia_srlinux::system::gnmi_server_rate_limit_t? rate_limit=null¶
Set a limit on the number of connection attempts per minute
- attribute nokia_srlinux::system::gnmi_server_session_limit_t? session_limit=null¶
Set a limit on the number of simultaneous active gNMI sessions
- attribute nokia_srlinux::system::gnmi_server_timeout_t? timeout=null¶
Set the idle timeout in seconds on gNMI connections
- attribute nokia_srlinux::system::gnmi_server_trace_options_t[]? trace_options=null¶
gNMI trace options :rel network_instance: List of network instances to run a gNMI server in :rel parent_system: Relation to parent container :rel unix_socket: Top-level container for configuration and state related to unix sockets
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Configures the gNMI server access API
other end:
nokia_srlinux::System.gnmi_server [0:1]
- relation nokia_srlinux::system::gnmi_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network instances to run a gNMI server in
other end:
nokia_srlinux::system::gnmi_server::NetworkInstance.parent_gnmi_server [1]
- relation nokia_srlinux::system::gnmi_server::UnixSocket unix_socket [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::gnmi_server::UnixSocket.parent_gnmi_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupGnmiServerYangContainer
constrainttrue
- entity nokia_srlinux::system::GribiServer¶
Parents:
nokia_srlinux::Base
Configures the gRPC Routing Information Base Interface (gRIBI) service Yang definition can be found here: srl_nokia-gribi-server.yang:L170
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Globally enable or disable the gRIBI service Disabling this will disable all gRIBI sockets in all configured network-instances (including unix sockets).
- attribute nokia_srlinux::system::gribi_server_rate_limit_t? rate_limit=null¶
Set a limit on the number of connection attempts per minute
- attribute nokia_srlinux::system::gribi_server_session_limit_t? session_limit=null¶
Set a limit on the number of simultaneous active gRIBI sessions A session is defined as an individual RPC invocation, which could result in a single client generating multiple sessions.
- attribute nokia_srlinux::system::gribi_server_timeout_t? timeout=null¶
Set the idle timeout in seconds on gRIBI clients
- attribute nokia_srlinux::system::gribi_server_trace_options_t[]? trace_options=null¶
gRIBI trace options :rel network_instance: List of network instances to run a gRIBI socket in :rel parent_system: Relation to parent container :rel unix_socket: Top-level container for configuration and state related to unix sockets
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Configures the gRPC Routing Information Base Interface (gRIBI) service
other end:
nokia_srlinux::System.gribi_server [0:1]
- relation nokia_srlinux::system::gribi_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network instances to run a gRIBI socket in
other end:
nokia_srlinux::system::gribi_server::NetworkInstance.parent_gribi_server [1]
- relation nokia_srlinux::system::gribi_server::UnixSocket unix_socket [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::gribi_server::UnixSocket.parent_gribi_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupGribiServerYangContainer
constrainttrue
- entity nokia_srlinux::system::Information¶
Parents:
nokia_srlinux::Base
Top-level container for system information configuration and state Yang definition can be found here: srl_nokia-system-info.yang:L45
- attribute string? contact=null¶
The system contact This field represents contact information for the person or group that maintains the system. This field is exposed via SNMP at the sysContact OID.
- attribute string? location=null¶
The system location This field represents the location of the system, and is commonly used by inventory management systems to group elements together. This field is exposed via SNMP at the sysLocation OID. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for system information configuration and state
other end:
nokia_srlinux::System.information [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupInformationYangContainer
constrainttrue
- entity nokia_srlinux::system::JsonRpcServer¶
Parents:
nokia_srlinux::Base
Configures the JSON RPC access API Yang definition can be found here: srl_nokia-json-rpc.yang:L136
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Globally enable or disable the JSON RPC server Disabling this will disable all JSON RPC servers.
- attribute nokia_srlinux::system::json_rpc_server_commit_confirmed_timeout_t? commit_confirmed_timeout=null¶
Number of seconds to wait for confirmation. A value of 0 means commit confirmed is not used
- attribute nokia_srlinux::system::json_rpc_server_trace_options_t[]? trace_options=null¶
JSON RPC trace options :rel network_instance: List of network instances to run the JSON RPC server in :rel parent_system: Relation to parent container :rel unix_socket: Top-level container for configuration and state related to unix sockets
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Configures the JSON RPC access API
other end:
nokia_srlinux::System.json_rpc_server [0:1]
- relation nokia_srlinux::system::json_rpc_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network instances to run the JSON RPC server in
other end:
nokia_srlinux::system::json_rpc_server::NetworkInstance.parent_json_rpc_server [1]
- relation nokia_srlinux::system::json_rpc_server::UnixSocket unix_socket [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::json_rpc_server::UnixSocket.parent_json_rpc_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupJsonRpcServerYangContainer
constrainttrue
- entity nokia_srlinux::system::Lacp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-lacp.yang:L262
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? system_id=null¶
The MAC address portion of the node’s System ID. This is combined with the system priority to construct the 8-octet system-id
- attribute yang::types::uint16? system_priority=null¶
System priority used by the node on this LAG interface. Lower value is higher priority for determining which node is the controlling system. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::System.lacp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupLacpYangContainer
constrainttrue
- entity nokia_srlinux::system::License¶
Parents:
nokia_srlinux::Base
List of licenses configured on the system Yang definition can be found here: srl_nokia-license.yang:L111
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable the use of this license
- attribute string? data=null¶
Content of the license This content includes a preceding UUID, followed by a space and the license data. For example: 00000000-0000-0000-0000-000000000000 aACUAx…rYzNRPT0AAAAA
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user provided description for the license
- attribute nokia_srlinux::types::srl_nokia_common::name id¶
Unique identifier for this license
- attribute bool? preferred=null¶
Set a license as being preferred Amongst all valid licenses, the preferred license will be chosen to become active. If no license is set as preferred or the preferred license is not valid, the valid license with the most distant expiry is chosen to become active. Only a single license can be set as preferred. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: List of licenses configured on the system
other end:
nokia_srlinux::System.license [0:5]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupLicenseYangContainer
constrainttrue
- entity nokia_srlinux::system::Lldp¶
Parents:
nokia_srlinux::Base
Top-level container for LLDP configuration and state data Yang definition can be found here: srl_nokia-lldp.yang:L662
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable LLDP at the system level
- attribute yang::types::uint64? hello_timer=null¶
System level hello timer for the LLDP protocol
- attribute yang::types::uint8? hold_multiplier=null¶
System level hold multiplier, used to define neighbor aging This field defines how many hellos need to be missed before a neighbor is aged out. This field also is used along with the ‘hello-timer’ field to define the TTL TLV in outgoing LLDPDUs.
- attribute nokia_srlinux::system::lldp_trace_options_t[]? trace_options=null¶
LLDP trace options :rel bgp_auto_discovery: Top-level container for global LLDP BGP auto discovery :rel interface: List of interfaces on which LLDP can be enabled :rel management_address: List of subinterfaces to source management addresses from This list is sent in the management address TLV by LLDP. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for LLDP configuration and state data
other end:
nokia_srlinux::System.lldp [0:1]
- relation nokia_srlinux::system::lldp::BgpAutoDiscovery bgp_auto_discovery [0:1]¶
Relation to parent container Peer relation: Top-level container for global LLDP BGP auto discovery
other end:
nokia_srlinux::system::lldp::BgpAutoDiscovery.parent_lldp [1]
- relation nokia_srlinux::system::lldp::Interface interface [0:*]¶
Relation to parent container Peer relation: List of interfaces on which LLDP can be enabled
other end:
nokia_srlinux::system::lldp::Interface.parent_lldp [1]
- relation nokia_srlinux::system::lldp::ManagementAddress management_address [0:*]¶
Relation to parent container Peer relation: List of subinterfaces to source management addresses from
This list is sent in the management address TLV by LLDP.
other end:
nokia_srlinux::system::lldp::ManagementAddress.parent_lldp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupLldpYangContainer
constrainttrue
- entity nokia_srlinux::system::Logging¶
Parents:
nokia_srlinux::Base
System logging provides the interface to syslog services to setup output entities on a selection of log sources. Yang definition can be found here: srl_nokia-logging.yang:L319
- attribute string? network_instance=null¶
Reference to a configured network-instance to run rsyslogd in This network-instance will be used as a source for requests to remote syslog servers.
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type_subset? subsystem_facility=null¶
Linux facility that internal application subsystems will use
- attribute bool? use_fqdn=null¶
Use the FQDN instead of only the hostname for logging messages :rel buffer: Log files maintained in memory, non-persistent across system reboots These files are stored at directory /var/log/srlinux/buffer. Rotation into multiple files is available. :rel console: Hardware serial device normally used for bring-up and diagnostics :rel file: Log files maintained on disk, persistent across system reboots When a maximum file size is reached, the file is renamed and a maximum rotate number of them are kept. :rel filter: Describes a set of critieria that captured messages are required to fulfill :rel parent_system: Relation to parent container :rel remote_server: List of output remote syslog servers
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: System logging provides the interface to syslog services to setup output entities on a selection of log sources.
other end:
nokia_srlinux::System.logging [0:1]
- relation nokia_srlinux::system::logging::Buffer buffer [0:*]¶
Relation to parent container Peer relation: Log files maintained in memory, non-persistent across system reboots
These files are stored at directory /var/log/srlinux/buffer. Rotation into multiple files is available.
other end:
nokia_srlinux::system::logging::Buffer.parent_logging [1]
- relation nokia_srlinux::system::logging::Console console [0:1]¶
Relation to parent container Peer relation: Hardware serial device normally used for bring-up and diagnostics
other end:
nokia_srlinux::system::logging::Console.parent_logging [1]
- relation nokia_srlinux::system::logging::File file [0:*]¶
Relation to parent container Peer relation: Log files maintained on disk, persistent across system reboots
When a maximum file size is reached, the file is renamed and a maximum rotate number of them are kept.
other end:
nokia_srlinux::system::logging::File.parent_logging [1]
- relation nokia_srlinux::system::logging::Filter filter [0:*]¶
Relation to parent container Peer relation: Describes a set of critieria that captured messages are required to fulfill
other end:
nokia_srlinux::system::logging::Filter.parent_logging [1]
- relation nokia_srlinux::system::logging::RemoteServer remote_server [0:*]¶
Relation to parent container Peer relation: List of output remote syslog servers
other end:
nokia_srlinux::system::logging::RemoteServer.parent_logging [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupLoggingYangContainer
constrainttrue
- entity nokia_srlinux::system::Maintenance¶
Parents:
nokia_srlinux::Base
Top-level container for Maintenance Mode configuration Yang definition can be found here: srl_nokia-maintenance-mode.yang:L209
- Rel group:
List of user-configured maintenance groups
- Rel parent_system:
Relation to parent container
- Rel profile:
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for Maintenance Mode configuration
other end:
nokia_srlinux::System.maintenance [0:1]
- relation nokia_srlinux::system::maintenance::Group group [0:*]¶
Relation to parent container Peer relation: List of user-configured maintenance groups
other end:
nokia_srlinux::system::maintenance::Group.parent_maintenance [1]
- relation nokia_srlinux::system::maintenance::Profile profile [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::maintenance::Profile.parent_maintenance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupMaintenanceYangContainer
constrainttrue
- entity nokia_srlinux::system::Management¶
Parents:
nokia_srlinux::Base
Enclosing container for options relating to management server Yang definition can be found here: srl_nokia-system.yang:L39
- Rel openconfig:
Top-level container for options relating to OpenConfig
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Enclosing container for options relating to management server
other end:
nokia_srlinux::System.management [0:1]
- relation nokia_srlinux::system::management::Openconfig openconfig [0:1]¶
Relation to parent container Peer relation: Top-level container for options relating to OpenConfig
other end:
nokia_srlinux::system::management::Openconfig.parent_management [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupManagementYangContainer
constrainttrue
- entity nokia_srlinux::system::Mirroring¶
Parents:
nokia_srlinux::Base
Top level container for configuration and operational state for mirroring Yang definition can be found here: srl_nokia-mirroring.yang:L346
- Rel mirroring_instance:
Mirroring instances configured on the local system
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top level container for configuration and operational state for mirroring
other end:
nokia_srlinux::System.mirroring [0:1]
- relation nokia_srlinux::system::mirroring::MirroringInstance mirroring_instance [0:8]¶
Relation to parent container Peer relation: Mirroring instances configured on the local system
other end:
nokia_srlinux::system::mirroring::MirroringInstance.parent_mirroring [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupMirroringYangContainer
constrainttrue
- entity nokia_srlinux::system::Mpls¶
Parents:
nokia_srlinux::Base
Container for system wide MPLS label management Yang definition can be found here: srl_nokia-mpls-label-management.yang:L201
- Rel label_ranges:
Container for managing MPLS label blocks
- Rel parent_system:
Relation to parent container
- Rel services:
Container for system wide Services MPLS label management
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Container for system wide MPLS label management
other end:
nokia_srlinux::System.mpls [0:1]
- relation nokia_srlinux::system::mpls::LabelRanges label_ranges [0:1]¶
Relation to parent container Peer relation: Container for managing MPLS label blocks
other end:
nokia_srlinux::system::mpls::LabelRanges.parent_mpls [1]
- relation nokia_srlinux::system::mpls::Services services [0:1]¶
Relation to parent container Peer relation: Container for system wide Services MPLS label management
other end:
nokia_srlinux::system::mpls::Services.parent_mpls [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupMplsYangContainer
constrainttrue
- entity nokia_srlinux::system::Mtu¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state data related to the system MTU Yang definition can be found here: srl_nokia-mtu.yang:L106
- attribute nokia_srlinux::system::mtu_default_ip_mtu_t? default_ip_mtu=null¶
System default IP MTU in bytes including the IP header but excluding Ethernet overhead The 7220 IXR-D1, 7220 IXR-D2, 7220 IXR-D3, 7220 IXR-H2, and 7220 IXR-H3 systems support a maximum IP MTU of 9398 bytes.
- attribute nokia_srlinux::system::mtu_default_l2_mtu_t? default_l2_mtu=null¶
System default Layer-2 MTU in bytes including ethernet overhead and VLAN tags but excluding 4-bytes FCS The 7220 IXR-D1, 7220 IXR-D2, 7220 IXR-D3, 7220 IXR-H2, and 7220 IXR-H3 systems support a maximum L2 MTU of 9412 bytes.
- attribute nokia_srlinux::system::mtu_default_mpls_mtu_t? default_mpls_mtu=null¶
System default MPLS MTU in bytes including the size of the transmitted label stack.
- attribute nokia_srlinux::system::mtu_default_port_mtu_t? default_port_mtu=null¶
System default port MTU in bytes including ethernet overhead but excluding 4-bytes FCS The 7220 IXR-D1, 7220 IXR-D2, 7220 IXR-D3, 7220 IXR-H2, and 7220 IXR-H3 systems support a maximum port MTU of 9412 bytes.
- attribute nokia_srlinux::system::mtu_min_path_mtu_t? min_path_mtu=null¶
Sets the minimum path MTU to use when receiving an ICMP fragmentation needed message This is controlled via the kernel min_pmtu option. In the event an ICMP fragmentation needed message is received by the kernel, the system will drop the session to this MTU to allow packets to traverse the entire path. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to the system MTU
other end:
nokia_srlinux::System.mtu [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupMtuYangContainer
constrainttrue
- entity nokia_srlinux::system::Multicast¶
Parents:
nokia_srlinux::Base
system multicast information Yang definition can be found here: srl_nokia-system-multicast.yang:L98
- Rel multicast_ids:
system multicast id information
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: system multicast information
other end:
nokia_srlinux::System.multicast [0:1]
- relation nokia_srlinux::system::multicast::MulticastIds multicast_ids [0:1]¶
Relation to parent container Peer relation: system multicast id information
other end:
nokia_srlinux::system::multicast::MulticastIds.parent_multicast [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupMulticastYangContainer
constrainttrue
- entity nokia_srlinux::system::Name¶
Parents:
nokia_srlinux::Base
Contains configuration and state related to system naming Yang definition can be found here: srl_nokia-system-name.yang:L27
- attribute nokia_srlinux::types::srl_nokia_common::domain_name? domain_name=null¶
The system domain name
- attribute nokia_srlinux::system::name_host_name_t? host_name=null¶
The system host name :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Contains configuration and state related to system naming
other end:
nokia_srlinux::System.name [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupNameYangContainer
constrainttrue
- entity nokia_srlinux::system::NetworkInstance¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance.yang:L48
- Rel parent_system:
Relation to parent container
- Rel protocols:
The routing protocols that are enabled for this
network-instance.
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::System.network_instance [0:1]
- relation nokia_srlinux::system::network_instance::Protocols protocols [0:1]¶
Relation to parent container Peer relation: The routing protocols that are enabled for this network-instance.
other end:
nokia_srlinux::system::network_instance::Protocols.parent_network_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupNetworkInstanceYangContainer
constrainttrue
- entity nokia_srlinux::system::Ntp¶
Parents:
nokia_srlinux::Base
Top-level container for NTP configuration and state Yang definition can be found here: srl_nokia-ntp.yang:L141
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables the system NTP client and indicates that the system should attempt to synchronize the clock
- attribute string? network_instance=null¶
Reference to a configured network-instance
- attribute nokia_srlinux::system::ntp_source_address_t? source_address=null¶
Source address for NTP to use for messages sent to a remote server :rel parent_system: Relation to parent container :rel server: List of NTP servers to use for system clock synchronization
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for NTP configuration and state
other end:
nokia_srlinux::System.ntp [0:1]
- relation nokia_srlinux::system::ntp::Server server [0:*]¶
Relation to parent container Peer relation: List of NTP servers to use for system clock synchronization
other end:
nokia_srlinux::system::ntp::Server.parent_ntp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupNtpYangContainer
constrainttrue
- entity nokia_srlinux::system::P4rtServer¶
Parents:
nokia_srlinux::Base
Configures the P4Runtime service Yang definition can be found here: srl_nokia-p4rt-server.yang:L154
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Globally enable or disable the P4Runtime service Disabling this will disable all P4Runtime sockets in all configured network-instances (including unix sockets).
- attribute nokia_srlinux::system::p4rt_server_rate_limit_t? rate_limit=null¶
Set a limit on the number of connection attempts per minute
- attribute nokia_srlinux::system::p4rt_server_session_limit_t? session_limit=null¶
Set a limit on the number of simultaneous active P4Runtime sessions A session is defined as an individual RPC invocation, which could result in a single client generating multiple sessions.
- attribute nokia_srlinux::system::p4rt_server_timeout_t? timeout=null¶
Set the idle timeout in seconds on P4Runtime clients
- attribute nokia_srlinux::system::p4rt_server_trace_options_t[]? trace_options=null¶
P4Runtime trace options :rel network_instance: List of network instances to run a P4Runtime socket in :rel parent_system: Relation to parent container :rel unix_socket: Top-level container for configuration and state related to unix sockets
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Configures the P4Runtime service
other end:
nokia_srlinux::System.p4rt_server [0:1]
- relation nokia_srlinux::system::p4rt_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network instances to run a P4Runtime socket in
other end:
nokia_srlinux::system::p4rt_server::NetworkInstance.parent_p4rt_server [1]
- relation nokia_srlinux::system::p4rt_server::UnixSocket unix_socket [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::p4rt_server::UnixSocket.parent_p4rt_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupP4rtServerYangContainer
constrainttrue
- entity nokia_srlinux::system::PacketLinkQualification¶
Parents:
nokia_srlinux::Base
Top-level container for gNOI Packet Link Qualification profiles Yang definition can be found here: srl_nokia-packet-link-qual.yang:L40
- Rel parent_system:
Relation to parent container
- Rel profile:
List of configured Packet Link Qualification profiles
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for gNOI Packet Link Qualification profiles
other end:
nokia_srlinux::System.packet_link_qualification [0:1]
- relation nokia_srlinux::system::packet_link_qualification::Profile profile [0:*]¶
Relation to parent container Peer relation: List of configured Packet Link Qualification profiles
other end:
nokia_srlinux::system::packet_link_qualification::Profile.parent_packet_link_qualification [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupPacketLinkQualificationYangContainer
constrainttrue
- entity nokia_srlinux::system::Protocols¶
Parents:
nokia_srlinux::Base
The routing protocols that are supported by the system Yang definition can be found here: srl_nokia-system-protocols.yang:L26
- Rel bgp:
- Rel parent_system:
Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: The routing protocols that are supported by the system
other end:
nokia_srlinux::System.protocols [0:1]
- relation nokia_srlinux::system::protocols::Bgp bgp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::protocols::Bgp.parent_protocols [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupProtocolsYangContainer
constrainttrue
- entity nokia_srlinux::system::RaGuardPolicy¶
Parents:
nokia_srlinux::Base
List containing RA Guard Policy and parameters Yang definition can be found here: srl_nokia-ra_guard.yang:L47
- attribute nokia_srlinux::system::ra_guard_policy_action_t? action=null¶
Describes the RA Guard Policy action for RA Messages matching the specified attributes. RA Messages no matching the specified attributes will be handled in the opposite manner.
- attribute string? advertise_prefix_set=null¶
Reference to a prefix set to match advertised address within RA message
- attribute nokia_srlinux::system::ra_guard_policy_hop_limit_t? hop_limit=null¶
Verifies the minimum advertised hop count limit. If not specified the verification is skipped.
- attribute bool? managed_config_flag=null¶
Causes the RA Guard policy to match IPv6 RA messages with the M (Managed address) flag set. If not specified the verification is skipped.
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
RA Guard Policy name
- attribute bool? other_config_flag=null¶
Causes the RA Guard policy to match IPv6 RA messages with the O (Other config) flag set. If not specified the verification is skipped.
- attribute nokia_srlinux::system::ra_guard_policy_router_preference_t? router_preference=null¶
Verifies that the advertised default router preference parameter value is equal to or less than the specified limit. If not specified the verification is skipped.
- attribute string? source_prefix_set=null¶
Reference to a prefix set to match RA source address. If not specified the verification is skipped. :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: List containing RA Guard Policy and parameters
other end:
nokia_srlinux::System.ra_guard_policy [0:64]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupRaGuardPolicyYangContainer
constrainttrue
- entity nokia_srlinux::system::Sflow¶
Parents:
nokia_srlinux::Base
Context to configure sFlow Agent parameters and report sFlow state Yang definition can be found here: srl_nokia-sflow.yang:L61
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable sFlow for the system
- attribute nokia_srlinux::system::sflow_dscp_t? dscp=null¶
Specify sFlow DSCP value This value specifies the DSCP value used in IP header of samples sent to the associated collectors.
- attribute nokia_srlinux::system::sflow_sample_rate_t? sample_rate=null¶
Specify sFlow sample rate This value is the rate at which traffic will be sampled at a rate of 1:N received packets.
- attribute nokia_srlinux::system::sflow_sample_size_t? sample_size=null¶
Specify sFlow sample size This value specifies the number of bytes the sFlow agent samples from each frame.
- attribute nokia_srlinux::system::sflow_source_address_t? source_address=null¶
Specifies the IP address to be used as the source address in sFlow packets :rel collector: List of sFlow collectors to which sFlow sample data is sent :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Context to configure sFlow Agent parameters and report sFlow state
other end:
nokia_srlinux::System.sflow [0:1]
- relation nokia_srlinux::system::sflow::Collector collector [0:8]¶
Relation to parent container Peer relation: List of sFlow collectors to which sFlow sample data is sent
other end:
nokia_srlinux::system::sflow::Collector.parent_sflow [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupSflowYangContainer
constrainttrue
- entity nokia_srlinux::system::Snmp¶
Parents:
nokia_srlinux::Base
Top-level container for SNMP configuration and state Yang definition can be found here: srl_nokia-snmp.yang:L377
- attribute nokia_srlinux::types::srl_nokia_common::name? community=null¶
- Rel access_group:
List of configured SNMP access-groups :rel network_instance: List of network-instances to run an SNMP server in :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for SNMP configuration and state
other end:
nokia_srlinux::System.snmp [0:1]
- relation nokia_srlinux::system::snmp::AccessGroup access_group [0:*]¶
Relation to parent container Peer relation: List of configured SNMP access-groups
other end:
nokia_srlinux::system::snmp::AccessGroup.parent_snmp [1]
- relation nokia_srlinux::system::snmp::NetworkInstance network_instance [0:5]¶
Relation to parent container Peer relation: List of network-instances to run an SNMP server in
other end:
nokia_srlinux::system::snmp::NetworkInstance.parent_snmp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupSnmpYangContainer
constrainttrue
- entity nokia_srlinux::system::SshServer¶
Parents:
nokia_srlinux::Base
Top-level container for SSH server configuration and state Yang definition can be found here: srl_nokia-ssh.yang:L115
- attribute string[]? revoked_keys=null¶
List of revoked public keys Each items value should be the public key of a revoked keypair, e.g. ‘ssh-rsa AAAA<…>= comment’. Any keys provided here cannot be used for public key authentication. This sets the RevokedKeys option within each SSH servers configuration file.
- attribute string[]? trust_anchors=null¶
List of public keys used to verify user certificates during authentication Each items value should be the public key of a CA, e.g. ‘ssh-rsa AAAA<…>= comment’. If no trust anchors are configured, authentication using SSH certificates will not function. This sets the TrustedUserCAKeys option within each SSH servers configuration file. :rel host_key: :rel network_instance: List of network-instances to run an SSH server in :rel parent_system: Relation to parent container
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for SSH server configuration and state
other end:
nokia_srlinux::System.ssh_server [0:1]
- relation nokia_srlinux::system::ssh_server::HostKey host_key [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::ssh_server::HostKey.parent_ssh_server [1]
- relation nokia_srlinux::system::ssh_server::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network-instances to run an SSH server in
other end:
nokia_srlinux::system::ssh_server::NetworkInstance.parent_ssh_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupSshServerYangContainer
constrainttrue
- entity nokia_srlinux::system::Sync¶
Parents:
nokia_srlinux::Base
Context to configure sync parameters and report sessions state Yang definition can be found here: srl_nokia-sync.yang:L57
- Rel freq_clock:
- Rel freq_references:
- Rel gnss:
- Rel one_pps:
- Rel parent_system:
Relation to parent container
- Rel ptp:
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Context to configure sync parameters and report sessions state
other end:
nokia_srlinux::System.sync [0:1]
- relation nokia_srlinux::system::sync::FreqClock freq_clock [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::sync::FreqClock.parent_sync [1]
- relation nokia_srlinux::system::sync::FreqReferences freq_references [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::sync::FreqReferences.parent_sync [1]
- relation nokia_srlinux::system::sync::Gnss gnss [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::sync::Gnss.parent_sync [1]
- relation nokia_srlinux::system::sync::OnePps one_pps [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::sync::OnePps.parent_sync [1]
- relation nokia_srlinux::system::sync::Ptp ptp [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupSyncYangContainer
constrainttrue
- entity nokia_srlinux::system::Tls¶
Parents:
nokia_srlinux::Base
Top-level container for TLS configuration and state Yang definition can be found here: srl_nokia-tls.yang:L334
- Rel parent_system:
Relation to parent container
- Rel server_profile:
List of configured TLS server profiles
- relation nokia_srlinux::System parent_system [1]¶
Relation to parent container Peer relation: Top-level container for TLS configuration and state
other end:
nokia_srlinux::System.tls [0:1]
- relation nokia_srlinux::system::tls::ServerProfile server_profile [0:*]¶
Relation to parent container Peer relation: List of configured TLS server profiles
other end:
nokia_srlinux::system::tls::ServerProfile.parent_tls [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::setupTlsYangContainer
constrainttrue
- entity nokia_srlinux::system::aaa::Accounting¶
Parents:
nokia_srlinux::Base
Top-level container for accounting Yang definition can be found here: srl_nokia-aaa.yang:L721
- attribute string[]? accounting_method=null¶
Ordered list of server-groups to use for accounting in the system If accounting fails with one method, the next defined method is tried – failure of all methods results in the accounting request failing. :rel event: List of events subject to accounting :rel parent_aaa: Relation to parent container
- relation nokia_srlinux::system::Aaa parent_aaa [1]¶
Relation to parent container Peer relation: Top-level container for accounting
other end:
nokia_srlinux::system::Aaa.accounting [0:1]
- relation nokia_srlinux::system::aaa::accounting::Event event [0:*]¶
Relation to parent container Peer relation: List of events subject to accounting
other end:
nokia_srlinux::system::aaa::accounting::Event.parent_accounting [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::aaa::setupAccountingYangContainer
constrainttrue
- entity nokia_srlinux::system::aaa::Authentication¶
Parents:
nokia_srlinux::Base
Top-level container for global authentication data Yang definition can be found here: srl_nokia-aaa.yang:L817
- attribute string[]? authentication_method=null¶
Ordered list of server-groups to be used during user authentication If authentication fails with one method, the next defined method is tried – failure of all methods results in the user being denied access.
- attribute bool? exit_on_reject=null¶
Enable/disable exit-on-reject behaviour for authentication attempts With this behaviour enabled, when a reject is received from any server the system will not try further methods, and will reject the user authentication attempt. Default behaviour is to continue trying methods until one accepts the user, or the system runs out of methods to try.
- attribute yang::types::uint32? idle_timeout=null¶
Set the idle timeout of all CLI sessions After the timeout is reached, the session is disconnected from the system. :rel admin_user: Enclosing container for admin user :rel linuxadmin_user: Enclosing container for linuxadmin user :rel parent_aaa: Relation to parent container :rel password: Top-level container for policies around user passwords :rel user: List of local users configured on the system
- relation nokia_srlinux::system::Aaa parent_aaa [1]¶
Relation to parent container Peer relation: Top-level container for global authentication data
- relation nokia_srlinux::system::aaa::authentication::AdminUser admin_user [0:1]¶
Relation to parent container Peer relation: Enclosing container for admin user
other end:
nokia_srlinux::system::aaa::authentication::AdminUser.parent_authentication [1]
- relation nokia_srlinux::system::aaa::authentication::LinuxadminUser linuxadmin_user [0:1]¶
Relation to parent container Peer relation: Enclosing container for linuxadmin user
other end:
nokia_srlinux::system::aaa::authentication::LinuxadminUser.parent_authentication [1]
- relation nokia_srlinux::system::aaa::authentication::Password password [0:1]¶
Relation to parent container Peer relation: Top-level container for policies around user passwords
other end:
nokia_srlinux::system::aaa::authentication::Password.parent_authentication [1]
- relation nokia_srlinux::system::aaa::authentication::User user [0:128]¶
Relation to parent container Peer relation: List of local users configured on the system
other end:
nokia_srlinux::system::aaa::authentication::User.parent_authentication [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::aaa::setupAuthenticationYangContainer
constrainttrue
- entity nokia_srlinux::system::aaa::Authorization¶
Parents:
nokia_srlinux::Base
Top-level container for authorization configuration and operational state data Yang definition can be found here: srl_nokia-aaa.yang:L774
- Rel parent_aaa:
Relation to parent container
- Rel role:
List of local roles configured on the system
- relation nokia_srlinux::system::Aaa parent_aaa [1]¶
Relation to parent container Peer relation: Top-level container for authorization configuration and operational state data
- relation nokia_srlinux::system::aaa::authorization::Role role [0:*]¶
Relation to parent container Peer relation: List of local roles configured on the system
other end:
nokia_srlinux::system::aaa::authorization::Role.parent_authorization [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::aaa::setupAuthorizationYangContainer
constrainttrue
- entity nokia_srlinux::system::aaa::ServerGroup¶
Parents:
nokia_srlinux::Base
List of AAA server-groups in the system
Each server group specifies a type, of which all servers must use. If using the ‘local’ type, then no servers may be specified. Yang definition can be found here: srl_nokia-aaa.yang:L154
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
User defined name for the server group
- attribute bool? priv_lvl_authorization=null¶
Use TACACS+ priv-lvl based authorization If false, then authorization is skipped for TACACS+ users granting full admin access for those users.
- attribute nokia_srlinux::system::aaa::server_group_timeout_t? timeout=null¶
Set the timeout in seconds on responses from servers in this group
- attribute string? type=null¶
AAA server type – all servers in the group must be of this type :rel parent_aaa: Relation to parent container :rel server: List of AAA servers to use within this server-group Servers are tried in a round-robin fashion, with the first server always being tried if it is operationally available
- relation nokia_srlinux::system::Aaa parent_aaa [1]¶
Relation to parent container Peer relation: List of AAA server-groups in the system
Each server group specifies a type, of which all servers must use. If using the ‘local’ type, then no servers may be specified.
- relation nokia_srlinux::system::aaa::server_group::Server server [0:5]¶
Relation to parent container Peer relation: List of AAA servers to use within this server-group
Servers are tried in a round-robin fashion, with the first server always being tried if it is operationally available
other end:
nokia_srlinux::system::aaa::server_group::Server.parent_server_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::aaa::setupServerGroupYangContainer
constrainttrue
- entity nokia_srlinux::system::aaa::accounting::Event¶
Parents:
nokia_srlinux::Base
List of events subject to accounting Yang definition can be found here: srl_nokia-aaa.yang:L710
- attribute string event_type¶
The type of activity to record at the accounting server
- attribute string? record=null¶
Type of record to send to the accounting server for this activity type :rel parent_accounting: Relation to parent container
- relation nokia_srlinux::system::aaa::Accounting parent_accounting [1]¶
Relation to parent container Peer relation: List of events subject to accounting
other end:
nokia_srlinux::system::aaa::Accounting.event [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::aaa::accounting::setupEventYangContainer
constrainttrue
- entity nokia_srlinux::system::aaa::authentication::AdminUser¶
Parents:
nokia_srlinux::Base
Enclosing container for admin user Yang definition can be found here: srl_nokia-aaa.yang:L595
- attribute nokia_srlinux::types::srl_nokia_common::user_password? password=null¶
The admin password, supplied either as cleartext or as a hashed value If provided as cleartext, the system will hash the value on input, storing only the hashed value. If provided as a hashed value, the value should include any ‘$’ characters, for example ‘$ar2$aOvsuj0ALlU=$r750fMa3ZEA/Di8dIfU2fQ==’.
- attribute nokia_srlinux::system::aaa::authentication::admin_user_role_t[]? role=null¶
List of roles to assign to this user The most specific rule for a particular role takes precedence. Rules from all user roles are evaluated together, most permissive privilege taking precedence.
- attribute nokia_srlinux::system::aaa::authentication::admin_user_spiffe_ids_t[]? spiffe_ids=null¶
The SPIFFE ID list for the user, including the spiffe:// URI This list of IDs is evaluated by TLS-consuming servers (e.g. gNMI, JSON-RPC) that use a TLS server-profile with authenticate-client set to true. If a match is found in any incoming offered client certificates, the provider of the certificate is associated with this local user, and given resulting permissions.
- attribute string[]? ssh_key=null¶
SSH public key(s) for the user If defined, the user may login to the system over SSH with this key. This should use the SSH public authorized key format.
- attribute string[]? ssh_principals=null¶
List of principals to associate with this user If any of the principals in the list are matched in a SSH client’s certificate, and that clients username matches this user, and the certificate is verified, the client will authenticate.
- attribute bool? superuser=null¶
Indicates if the admin user is a superuser A superuser is granted implicit authorization to all YANG paths, has the ability to execute all CLI plugins, and by default is permitted to access the device through any interface. Additionally, users with the superuser attribute are able to execute ‘sudo’ in bash. A user may also be assigned a role or list of roles, but these are only evaluated for service authorization. :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::system::aaa::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Enclosing container for admin user
other end:
nokia_srlinux::system::aaa::Authentication.admin_user [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authentication::LinuxadminUser¶
Parents:
nokia_srlinux::Base
Enclosing container for linuxadmin user Yang definition can be found here: srl_nokia-aaa.yang:L647
- attribute string? password=null¶
The linuxadmin password, supplied either as cleartext or as a hashed value If provided as cleartext, the system will hash the value on input, storing only the hashed value. If provided as a hashed value, the value should include any ‘$’ characters, for example ‘$6$c66a15569d3f5952$kA2WPt9iqR5uMbaCUBNxsjKyXROQFdJtV1HX0CFY9wk7F326/yB3h.dERX9cH7YpeJ1N872hjzTb2tlaZFwwg0’.
- attribute string[]? ssh_key=null¶
SSH public key(s) for the user If defined, the user may login to the system over SSH with this key. This should use the SSH public authorized key format.
- attribute string[]? ssh_principals=null¶
List of principals to associate with this user If any of the principals in the list are matched in a SSH client’s certificate, and that clients username matches this user, and the certificate is verified, the client will authenticate. :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::system::aaa::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Enclosing container for linuxadmin user
other end:
nokia_srlinux::system::aaa::Authentication.linuxadmin_user [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authentication::Password¶
Parents:
nokia_srlinux::Base
Top-level container for policies around user passwords Yang definition can be found here: srl_nokia-aaa-password.yang:L174
- attribute nokia_srlinux::system::aaa::authentication::password_aging_t? aging=null¶
Expire user passwords after this period A value of 0 means that the user passwords do not expire
- attribute bool? change_on_first_login=null¶
Enable or disable a user being forced to change their password on first time login
- attribute nokia_srlinux::system::aaa::authentication::password_hash_method_t? hash_method=null¶
The hash type for the password entered as plain text
- attribute nokia_srlinux::system::aaa::authentication::password_history_t? history=null¶
Defines how many previous passwords a new password is matched against, such that a new password can’t be one of the previous n passwords
- attribute bool? require_ntp_sync=null¶
Enable or disable dependence of password aging and user lockout on NTP sync status :rel complexity_rules: Top-level container for password complexity rules :rel lockout_policy: Top-level container for lockout policy :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::system::aaa::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: Top-level container for policies around user passwords
other end:
nokia_srlinux::system::aaa::Authentication.password [0:1]
- relation nokia_srlinux::system::aaa::authentication::password::ComplexityRules complexity_rules [0:1]¶
Relation to parent container Peer relation: Top-level container for password complexity rules
other end:
nokia_srlinux::system::aaa::authentication::password::ComplexityRules.parent_password [1]
- relation nokia_srlinux::system::aaa::authentication::password::LockoutPolicy lockout_policy [0:1]¶
Relation to parent container Peer relation: Top-level container for lockout policy
other end:
nokia_srlinux::system::aaa::authentication::password::LockoutPolicy.parent_password [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authentication::User¶
Parents:
nokia_srlinux::Base
List of local users configured on the system Yang definition can be found here: srl_nokia-aaa.yang:L470
- attribute nokia_srlinux::types::srl_nokia_common::user_password? password=null¶
The user password, supplied either as cleartext or as a hashed value If provided as cleartext, the system will hash the value on input, storing only the hashed value. If provided as a hashed value, the value should include any ‘$’ characters, for example ‘$ar2$aOvsuj0ALlU=$r750fMa3ZEA/Di8dIfU2fQ==’.
- attribute nokia_srlinux::system::aaa::authentication::user_role_t[]? role=null¶
List of roles to assign to this user The most specific rule for a particular role takes precedence. Rules from all user roles are evaluated together, most permissive privilege taking precedence.
- attribute nokia_srlinux::system::aaa::authentication::user_spiffe_ids_t[]? spiffe_ids=null¶
The SPIFFE ID list for the user, including the spiffe:// URI This list of IDs is evaluated by TLS-consuming servers (e.g. gNMI, JSON-RPC) that use a TLS server-profile with authenticate-client set to true. If a match is found in any incoming offered client certificates, the provider of the certificate is associated with this local user, and given resulting permissions.
- attribute string[]? ssh_key=null¶
SSH public key(s) for the user If defined, the user may login to the system over SSH with this key. This should use the SSH public authorized key format.
- attribute string[]? ssh_principals=null¶
List of principals to associate with this user If any of the principals in the list are matched in a SSH client’s certificate, and that clients username matches this user, and the certificate is verified, the client will authenticate.
- attribute bool? superuser=null¶
Indicates that this user is a superuser A superuser is granted implicit authorization to all YANG paths, has the ability to execute all CLI plugins, and by default is permitted to access the device through any interface. Additionally, users with the superuser attribute are able to execute ‘sudo’ in bash. A user may also be assigned a role or list of roles, but these are only evaluated for service authorization.
- attribute nokia_srlinux::system::aaa::authentication::user_username_t username¶
Assigned username for this user :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::system::aaa::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: List of local users configured on the system
other end:
nokia_srlinux::system::aaa::Authentication.user [0:128]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authentication::password::ComplexityRules¶
Parents:
nokia_srlinux::Base
Top-level container for password complexity rules Yang definition can be found here: srl_nokia-aaa-password.yang:L36
- attribute bool? allow_username=null¶
Enable or disable using username as part of the user password
- attribute nokia_srlinux::system::aaa::authentication::password::complexity_rules_maximum_length_t? maximum_length=null¶
The maximum length of the password for local users, including admin and linuxadmin
- attribute nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_length_t? minimum_length=null¶
The minimum length of the password for local users, including admin and linuxadmin
- attribute nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_lowercase_t? minimum_lowercase=null¶
The minimum lowercase characters from (a-z) that the user password must include A value of 0 results in no minimum-lowercase being enforced.
- attribute nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_numeric_t? minimum_numeric=null¶
The minimum numeric digits that the user password must include A value of 0 results in no minimum-numeric being enforced.
- attribute nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_special_character_t? minimum_special_character=null¶
The minimum special characters that the user password must include A value of 0 results in no minimum-special-character being enforced.
- attribute nokia_srlinux::system::aaa::authentication::password::complexity_rules_minimum_uppercase_t? minimum_uppercase=null¶
The minimum uppercase characters from (A-Z) that the user password must include A value of 0 results in no minimum-uppercase being enforced. :rel parent_password: Relation to parent container
- relation nokia_srlinux::system::aaa::authentication::Password parent_password [1]¶
Relation to parent container Peer relation: Top-level container for password complexity rules
other end:
nokia_srlinux::system::aaa::authentication::Password.complexity_rules [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authentication::password::LockoutPolicy¶
Parents:
nokia_srlinux::Base
Top-level container for lockout policy Yang definition can be found here: srl_nokia-aaa-password.yang:L113
- attribute nokia_srlinux::system::aaa::authentication::password::lockout_policy_attempts_t? attempts=null¶
The number of failed login attempts that will lock the account A value of 0 means unlimited number of failed login attempts is allowed
- attribute nokia_srlinux::system::aaa::authentication::password::lockout_policy_lockout_t? lockout=null¶
The time duration in minutes the user account will be locked out A value of 0 means that the user account will be locked out/disabled indefinitely
- attribute nokia_srlinux::system::aaa::authentication::password::lockout_policy_time_t? time=null¶
The time period in minutes within which the failed login attempts occur :rel parent_password: Relation to parent container
- relation nokia_srlinux::system::aaa::authentication::Password parent_password [1]¶
Relation to parent container Peer relation: Top-level container for lockout policy
other end:
nokia_srlinux::system::aaa::authentication::Password.lockout_policy [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authorization::Role¶
Parents:
nokia_srlinux::Base
List of local roles configured on the system Yang definition can be found here: srl_nokia-aaa.yang:L583
- attribute nokia_srlinux::system::aaa::authorization::role_rolename_t rolename¶
Assigned rolename for this role
- attribute nokia_srlinux::system::aaa::authorization::role_services_t[]? services=null¶
Services that members of this role are authorized for Services are additive, if a user is a member of multiple roles, the available services are merged.
- attribute bool? superuser=null¶
Indicates if users with this role are given superuser A superuser is granted implicit authorization to all YANG paths, has the ability to execute all CLI plugins, and by default is permitted to access the device through any interface. Additionally, users with the superuser attribute are able to execute ‘sudo’ in bash. A user may also be assigned a role or list of roles, but these are only evaluated for service authorization. :rel cli: Top-level container for cli plugin configuration :rel parent_authorization: Relation to parent container :rel tacacs: Top-level container for configuration relating to TACACS+ interworking with roles
- relation nokia_srlinux::system::aaa::Authorization parent_authorization [1]¶
Relation to parent container Peer relation: List of local roles configured on the system
other end:
nokia_srlinux::system::aaa::Authorization.role [0:*]
- relation nokia_srlinux::system::aaa::authorization::role::Cli cli [0:1]¶
Relation to parent container Peer relation: Top-level container for cli plugin configuration
other end:
nokia_srlinux::system::aaa::authorization::role::Cli.parent_role [1]
- relation nokia_srlinux::system::aaa::authorization::role::Tacacs tacacs [0:1]¶
Relation to parent container Peer relation: Top-level container for configuration relating to TACACS+ interworking with roles
other end:
nokia_srlinux::system::aaa::authorization::role::Tacacs.parent_role [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authorization::role::Cli¶
Parents:
nokia_srlinux::Base
Top-level container for cli plugin configuration Yang definition can be found here: srl_nokia-aaa.yang:L538
- attribute string[]? allow_command_list=null¶
List of cli commands that are allowed for this role Python style regular expressions are supported. Every item is left anchored (it matches from the beginning of line). Empty allow-command-list means anything that is not in deny-command-list is allowed. If both lists are empty then everything is allowed.
- attribute string[]? deny_command_list=null¶
List of cli commands that are denied for this role Python style regular expressions are supported. Every item is left anchored (it matches from the beginning of line). Empty deny-command-list means anything that is not in allow-command-list is denied. If both lists are empty then everything is allowed.
- attribute bool? load_global_plugins=null¶
Specifies whether cli should load plugins from global plugin directory (from /etc/opt/srlinux/cli/plugins/).
- attribute bool? load_user_plugins=null¶
Specifies whether cli should load plugins from user home directory (from ~/cli/plugins/). :rel parent_role: Relation to parent container
- relation nokia_srlinux::system::aaa::authorization::Role parent_role [1]¶
Relation to parent container Peer relation: Top-level container for cli plugin configuration
other end:
nokia_srlinux::system::aaa::authorization::Role.cli [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::authorization::role::Tacacs¶
Parents:
nokia_srlinux::Base
Top-level container for configuration relating to TACACS+ interworking with roles Yang definition can be found here: srl_nokia-aaa.yang:L524
- attribute nokia_srlinux::system::aaa::authorization::role::tacacs_priv_lvl_t? priv_lvl=null¶
The TACACS+ priv-lvl to map to this role All roles matching each specific priv-lvl, and their lessers are merged together to create the final ruleset applied to the user. :rel parent_role: Relation to parent container
- relation nokia_srlinux::system::aaa::authorization::Role parent_role [1]¶
Relation to parent container Peer relation: Top-level container for configuration relating to TACACS+ interworking with roles
other end:
nokia_srlinux::system::aaa::authorization::Role.tacacs [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::server_group::Server¶
Parents:
nokia_srlinux::Base
List of AAA servers to use within this server-group
Servers are tried in a round-robin fashion, with the first server always being tried if it is operationally available Yang definition can be found here: srl_nokia-aaa.yang:L134
- attribute nokia_srlinux::system::aaa::server_group::server_address_t address¶
Address used to reach the server
- attribute nokia_srlinux::types::srl_nokia_common::name? name=null¶
User defined name assigned to the server
- attribute string? network_instance=null¶
Reference to a configured network-instance used for reachability to the server This network-instance must already exist in the system, and different servers within the same server-group may use difference network-instances for connectivity. :rel parent_server_group: Relation to parent container :rel radius: Top-level container for RADIUS server data :rel tacacs: Top-level container for TACACS+ server data
- relation nokia_srlinux::system::aaa::ServerGroup parent_server_group [1]¶
Relation to parent container Peer relation: List of AAA servers to use within this server-group
Servers are tried in a round-robin fashion, with the first server always being tried if it is operationally available
other end:
nokia_srlinux::system::aaa::ServerGroup.server [0:5]
- relation nokia_srlinux::system::aaa::server_group::server::Radius radius [0:1]¶
Relation to parent container Peer relation: Top-level container for RADIUS server data
other end:
nokia_srlinux::system::aaa::server_group::server::Radius.parent_server [1]
- relation nokia_srlinux::system::aaa::server_group::server::Tacacs tacacs [0:1]¶
Relation to parent container Peer relation: Top-level container for TACACS+ server data
other end:
nokia_srlinux::system::aaa::server_group::server::Tacacs.parent_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::server_group::server::Radius¶
Parents:
nokia_srlinux::Base
Top-level container for RADIUS server data Yang definition can be found here: srl_nokia-aaa-radius.yang:L81
- attribute nokia_srlinux::types::srl_nokia_common::port_number? acct_port=null¶
Port number for accounting requests
- attribute nokia_srlinux::types::srl_nokia_common::port_number? auth_port=null¶
Port number for authentication requests
- attribute yang::types::uint8? retransmit_attempts=null¶
Number of times the system may send a request to the unresponsive server
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? secret_key=null¶
The unencrypted shared key used between the system and server :rel parent_server: Relation to parent container
- relation nokia_srlinux::system::aaa::server_group::Server parent_server [1]¶
Relation to parent container Peer relation: Top-level container for RADIUS server data
other end:
nokia_srlinux::system::aaa::server_group::Server.radius [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::aaa::server_group::server::Tacacs¶
Parents:
nokia_srlinux::Base
Top-level container for TACACS+ server data Yang definition can be found here: srl_nokia-aaa-tacacs.yang:L71
- attribute nokia_srlinux::types::srl_nokia_common::port_number? port=null¶
The port number on which to contact the TACACS+ server
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? secret_key=null¶
The unencrypted shared key used between the system and server :rel parent_server: Relation to parent container
- relation nokia_srlinux::system::aaa::server_group::Server parent_server [1]¶
Relation to parent container Peer relation: Top-level container for TACACS+ server data
other end:
nokia_srlinux::system::aaa::server_group::Server.tacacs [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::authentication::Keychain¶
Parents:
nokia_srlinux::Base
List of system keychains Yang definition can be found here: srl_nokia-keychains.yang:L128
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
When set to disable, the keychain is inactive When a protocol refers to a keychain that is inactive, no authentication data is added to the outbound messages and/or all inbound messages with authentication data are dropped, depending on the context. A keychain is operationally disabled in a particular direction (send/receive) if: - the keychain is administratively disabled - no keys are configured - all of the keys are administratively disabled - all of the keys are inactive because their start-times are in the future - all of the keys are inactive because their end-times (plus tolerance) are in the past (applies only to receive direction)
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
The user configured description for the keychain
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The user configured name for the keychain
- attribute yang::types::uint32? tolerance=null¶
Tolerance for receive keys If tolerance is Z then all receive keys remain valid up to the configured/applicable end-time plus an additional Z seconds.
- attribute nokia_srlinux::types::srl_nokia_keychains::keychain_type? type=null¶
Specifies the intended use of the keychain The type constrains the set of crypto algorithms that are available to use with each key in the keychain. It is also used to ensure that this keychain is only used by protocols for which it is intended. :rel key: List of keys in the keychain :rel parent_authentication: Relation to parent container
- relation nokia_srlinux::system::Authentication parent_authentication [1]¶
Relation to parent container Peer relation: List of system keychains
other end:
nokia_srlinux::system::Authentication.keychain [0:1024]
- relation nokia_srlinux::system::authentication::keychain::Key key [0:*]¶
Relation to parent container Peer relation: List of keys in the keychain
other end:
nokia_srlinux::system::authentication::keychain::Key.parent_keychain [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::authentication::keychain::Key¶
Parents:
nokia_srlinux::Base
List of keys in the keychain Yang definition can be found here: srl_nokia-keychains.yang:L208
- attribute nokia_srlinux::types::srl_nokia_keychains::algorithm_type? algorithm=null¶
The cryptographic algorithm used with the keying material to secure the messages
- attribute nokia_srlinux::types::srl_nokia_common::routing_password? authentication_key=null¶
The secret key to use for authentication
- attribute yang::types::uint8 x_index¶
Each key in a keychain requires a unique identifier, the index value specifies this identifier :rel parent_keychain: Relation to parent container :rel receive_lifetime: :rel send_lifetime: Specifies the lifetime of the key for sending authentication information to the peer
- relation nokia_srlinux::system::authentication::Keychain parent_keychain [1]¶
Relation to parent container Peer relation: List of keys in the keychain
other end:
nokia_srlinux::system::authentication::Keychain.key [0:*]
- relation nokia_srlinux::system::authentication::keychain::key::ReceiveLifetime receive_lifetime [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::authentication::keychain::key::ReceiveLifetime.parent_key [1]
- relation nokia_srlinux::system::authentication::keychain::key::SendLifetime send_lifetime [0:1]¶
Relation to parent container Peer relation: Specifies the lifetime of the key for sending authentication information to the peer
other end:
nokia_srlinux::system::authentication::keychain::key::SendLifetime.parent_key [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::authentication::keychain::key::ReceiveLifetime¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-keychains.yang:L261
- attribute nokia_srlinux::system::authentication::keychain::key::receive_lifetime_end_time_t? end_time=null¶
The time at which the key becomes invalid for use in the receive direction The default is forever.
- attribute nokia_srlinux::types::srl_nokia_common::date_and_time? start_time=null¶
The time at which the key becomes valid for use in the receive direction If send-and-receive is true, this value is ignored. If send-and-receive is false the default is the Unix Epoch (Jan 1, 1970 00:00:00 UTC). If there are multiple keys in the keychain the one used for checking received authentication information is the key with the most recent receive-lifetime start-time that is earlier than the current date and time and that has not exceeded its receive-lifetime end-time by more than ‘tolerance’ seconds :rel parent_key: Relation to parent container
- relation nokia_srlinux::system::authentication::keychain::Key parent_key [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::authentication::keychain::Key.receive_lifetime [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::authentication::keychain::key::SendLifetime¶
Parents:
nokia_srlinux::Base
Specifies the lifetime of the key for sending authentication information to the peer Yang definition can be found here: srl_nokia-keychains.yang:L234
- attribute bool? send_and_receive=null¶
When this is set to true (the default value), the specified start-time also applies to the receive direction When set to false, router uses the specific start-time for the receive direction (asymmetric mode).
- attribute nokia_srlinux::types::srl_nokia_common::date_and_time? start_time=null¶
The time at which the key becomes valid for use in the send direction The default is the Unix Epoch (Jan 1, 1970 00:00:00 UTC). If there are multiple keys in the keychain the one used for sending authentication information is the key with the most recent send-lifetime start-time that is earlier than the current date and time :rel parent_key: Relation to parent container
- relation nokia_srlinux::system::authentication::keychain::Key parent_key [1]¶
Relation to parent container Peer relation: Specifies the lifetime of the key for sending authentication information to the peer
other end:
nokia_srlinux::system::authentication::keychain::Key.send_lifetime [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::boot::Autoboot¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state data related to autobooting the system Yang definition can be found here: srl_nokia-boot.yang:L85
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable autoboot functionality
- attribute nokia_srlinux::system::boot::autoboot_attempts_t? attempts=null¶
Sets the amount of executions to try autoboot, before rebooting the system
- attribute nokia_srlinux::types::srl_nokia_boot::client_id? client_id=null¶
The client ID to use on outgoing DHCP requests
- attribute string? interface=null¶
Sets the interface to use for autoboot functionality
- attribute string[]? mode=null¶
Ztp operation modes. One or more modes can passed
- attribute nokia_srlinux::system::boot::autoboot_timeout_t? timeout=null¶
Sets the timeout for each attempt to autoboot :rel parent_boot: Relation to parent container
- relation nokia_srlinux::system::Boot parent_boot [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state data related to autobooting the system
other end:
nokia_srlinux::system::Boot.autoboot [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::boot::setupAutobootYangContainer
constrainttrue
- entity nokia_srlinux::system::bridge_table::MacLearning¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-bridge-table.yang:L82
- Rel parent_bridge_table:
Relation to parent container
- relation nokia_srlinux::system::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::BridgeTable.mac_learning [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::bridge_table::MacLimit¶
Parents:
nokia_srlinux::Base
Bridge Table size and thresholds. Yang definition can be found here: srl_nokia-system-bridge-table.yang:L95
- Rel parent_bridge_table:
Relation to parent container
- relation nokia_srlinux::system::BridgeTable parent_bridge_table [1]¶
Relation to parent container Peer relation: Bridge Table size and thresholds.
other end:
nokia_srlinux::system::BridgeTable.mac_limit [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::bridge_table::setupMacLimitYangContainer
constrainttrue
- entity nokia_srlinux::system::configuration::Role¶
Parents:
nokia_srlinux::Base
List of roles configured in the system Yang definition can be found here: srl_nokia-configuration-role.yang:L53
- attribute nokia_srlinux::system::configuration::role_name_t name¶
- Rel parent_configuration:
Relation to parent container :rel rule: List of paths to perform access control against
- relation nokia_srlinux::system::Configuration parent_configuration [1]¶
Relation to parent container Peer relation: List of roles configured in the system
- relation nokia_srlinux::system::configuration::role::Rule rule [0:256]¶
Relation to parent container Peer relation: List of paths to perform access control against
other end:
nokia_srlinux::system::configuration::role::Rule.parent_role [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::configuration::setupRoleYangContainer
constrainttrue
- entity nokia_srlinux::system::configuration::role::Rule¶
Parents:
nokia_srlinux::Base
List of paths to perform access control against Yang definition can be found here: srl_nokia-configuration-role.yang:L64
- attribute nokia_srlinux::types::srl_nokia_configuration_role::path_action? action=null¶
Action to allow for this path
- attribute nokia_srlinux::system::configuration::role::rule_path_reference_t path_reference¶
Reference to a valid YANG path, in CLI notation This path may include keys, wildcards, ranges, and other management server supported constructs. Ranges will be expanded. The root path can be specified with ‘/’. E.g. / “/interface” “/acl ipv4-filter foo* description” :rel parent_role: Relation to parent container
- relation nokia_srlinux::system::configuration::Role parent_role [1]¶
Relation to parent container Peer relation: List of paths to perform access control against
other end:
nokia_srlinux::system::configuration::Role.rule [0:256]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network instances to run a dhcp server in Yang definition can be found here: srl_nokia-dhcp-server.yang:L240
- attribute string name¶
Reference to a configured network instance :rel dhcpv4: :rel dhcpv6: :rel parent_dhcp_server: Relation to parent container
- relation nokia_srlinux::system::DhcpServer parent_dhcp_server [1]¶
Relation to parent container Peer relation: List of network instances to run a dhcp server in
other end:
nokia_srlinux::system::DhcpServer.network_instance [0:*]
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4 dhcpv4 [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4.parent_network_instance [1]
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6 dhcpv6 [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6.parent_network_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L224
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the dhcp server :rel options: :rel parent_network_instance: Relation to parent container :rel static_allocation: :rel trace_options: Container for tracing DHCP server operations instance
- relation nokia_srlinux::system::dhcp_server::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::NetworkInstance.dhcpv4 [0:1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::Options options [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::Options.parent_dhcpv4 [1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::StaticAllocation static_allocation [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::StaticAllocation.parent_dhcpv4 [1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Container for tracing DHCP server operations instance
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::TraceOptions.parent_dhcpv4 [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L232
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the dhcp server :rel options: :rel parent_network_instance: Relation to parent container :rel static_allocation: :rel trace_options: Container for tracing DHCP server operations instance
- relation nokia_srlinux::system::dhcp_server::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::NetworkInstance.dhcpv6 [0:1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::Options options [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::Options.parent_dhcpv6 [1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::StaticAllocation static_allocation [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::StaticAllocation.parent_dhcpv6 [1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::TraceOptions trace_options [0:1]¶
Relation to parent container Peer relation: Container for tracing DHCP server operations instance
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::TraceOptions.parent_dhcpv6 [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::Options¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L133
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::options_bootfile_name_t? bootfile_name=null¶
The name of the configuration file the client will use during booting - option 67
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address[]? dns_server=null¶
An Ordered List of DNS servers to return to the dhcp client - option 6
- attribute nokia_srlinux::types::srl_nokia_common::domain_name? domain_name=null¶
The domain name to return to the dhcp client that the client should use when resolving hostnames via the Domain Name System - option 15
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::options_hostname_t? hostname=null¶
Host Name option of the dhcp client - option 12
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address[]? ntp_server=null¶
List of NTP Servers to return to the dhcp client - option 42
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? router=null¶
IPv4 address of the gateway for the dhcp client - option 3
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? server_id=null¶
IP address the dhcp server must match any address within the network_instance e.g. sub-interface primary address, loopback address, anycast gateway address in case of multihoming - option 54
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address[]? tftp_server_address=null¶
List of IP address of the TFTP servers the client will use to download bootfile/configuration script - option 150
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::options_tftp_server_name_t? tftp_server_name=null¶
FQDN of the TFTP server the client will use to download bootfile/configuration script - option 66 :rel parent_dhcpv4: Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4 parent_dhcpv4 [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4.options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::StaticAllocation¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L93
- Rel host:
host name for static ip allocations
- Rel parent_dhcpv4:
Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4 parent_dhcpv4 [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4.static_allocation [0:1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::Host host [0:*]¶
Relation to parent container Peer relation: host name for static ip allocations
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::TraceOptions¶
Parents:
nokia_srlinux::Base
Container for tracing DHCP server operations instance Yang definition can be found here: srl_nokia-dhcp-server.yang:L58
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::trace_options_trace_t[]? trace=null¶
List of events to trace :rel parent_dhcpv4: Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4 parent_dhcpv4 [1]¶
Relation to parent container Peer relation: Container for tracing DHCP server operations instance
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv4.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::Host¶
Parents:
nokia_srlinux::Base
host name for static ip allocations Yang definition can be found here: srl_nokia-dhcp-server.yang:L94
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_prefix_with_host_bits? ip_address=null¶
- attribute nokia_srlinux::types::srl_nokia_common::mac_address mac¶
- Rel options:
- rel parent_static_allocation:
Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::StaticAllocation parent_static_allocation [1]¶
Relation to parent container Peer relation: host name for static ip allocations
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::StaticAllocation.host [0:*]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::Options options [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::Options¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L133
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::options_bootfile_name_t? bootfile_name=null¶
The name of the configuration file the client will use during booting - option 67
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address[]? dns_server=null¶
An Ordered List of DNS servers to return to the dhcp client - option 6
- attribute nokia_srlinux::types::srl_nokia_common::domain_name? domain_name=null¶
The domain name to return to the dhcp client that the client should use when resolving hostnames via the Domain Name System - option 15
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::options_hostname_t? hostname=null¶
Host Name option of the dhcp client - option 12
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address[]? ntp_server=null¶
List of NTP Servers to return to the dhcp client - option 42
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? router=null¶
IPv4 address of the gateway for the dhcp client - option 3
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? server_id=null¶
IP address the dhcp server must match any address within the network_instance e.g. sub-interface primary address, loopback address, anycast gateway address in case of multihoming - option 54
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address[]? tftp_server_address=null¶
List of IP address of the TFTP servers the client will use to download bootfile/configuration script - option 150
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::options_tftp_server_name_t? tftp_server_name=null¶
FQDN of the TFTP server the client will use to download bootfile/configuration script - option 66 :rel parent_host: Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::Host parent_host [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::Host.options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::Options¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L210
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address[]? dns_server=null¶
An Ordered List of DNS servers to return to the dhcp client :rel parent_dhcpv6: Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6 parent_dhcpv6 [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6.options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::StaticAllocation¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L113
- Rel host:
host name for static ip allocations
- Rel parent_dhcpv6:
Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6 parent_dhcpv6 [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6.static_allocation [0:1]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::Host host [0:*]¶
Relation to parent container Peer relation: host name for static ip allocations
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::TraceOptions¶
Parents:
nokia_srlinux::Base
Container for tracing DHCP server operations instance Yang definition can be found here: srl_nokia-dhcp-server.yang:L58
- attribute nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::trace_options_trace_t[]? trace=null¶
List of events to trace :rel parent_dhcpv6: Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6 parent_dhcpv6 [1]¶
Relation to parent container Peer relation: Container for tracing DHCP server operations instance
other end:
nokia_srlinux::system::dhcp_server::network_instance::Dhcpv6.trace_options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::Host¶
Parents:
nokia_srlinux::Base
host name for static ip allocations Yang definition can be found here: srl_nokia-dhcp-server.yang:L114
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_prefix_with_host_bits? ip_address=null¶
- attribute nokia_srlinux::types::srl_nokia_common::mac_address mac¶
- Rel options:
- rel parent_static_allocation:
Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::StaticAllocation parent_static_allocation [1]¶
Relation to parent container Peer relation: host name for static ip allocations
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::StaticAllocation.host [0:*]
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::host::Options options [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::host::Options¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-dhcp-server.yang:L210
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address[]? dns_server=null¶
An Ordered List of DNS servers to return to the dhcp client :rel parent_host: Relation to parent container
- relation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::Host parent_host [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::Host.options [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::dns::HostEntry¶
Parents:
nokia_srlinux::Base
List of static host entries Yang definition can be found here: srl_nokia-dns.yang:L60
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? ipv4_address=null¶
IPv4 address for the host entry
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? ipv6_address=null¶
IPv6 address for the host entry
- attribute nokia_srlinux::types::srl_nokia_common::domain_name name¶
Name of host entry :rel parent_dns: Relation to parent container
- relation nokia_srlinux::system::Dns parent_dns [1]¶
Relation to parent container Peer relation: List of static host entries
other end:
nokia_srlinux::system::Dns.host_entry [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::dns::setupHostEntryYangContainer
constrainttrue
- entity nokia_srlinux::system::event_handler::Instance¶
Parents:
nokia_srlinux::Base
List of all event handler instances
An event handler instance consists of a set of paths to be monitored for changes, and a Python script to execute if changes occur. Yang definition can be found here: srl_nokia-event-handler.yang:L227
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable this event handler instance
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A user-defined name for this event handler instance
- attribute nokia_srlinux::system::event_handler::instance_paths_t[]? paths=null¶
List of valid YANG paths in CLI notation to monitor for changes If any events are received on any of the provided paths, the configured script will be executed. This path may include keys, wildcards, ranges, and other management server supported constructs. E.g. “interface * oper-state” “acl ipv4-filter foo* description”
- attribute nokia_srlinux::system::event_handler::instance_upython_script_t? upython_script=null¶
File name of a MicroPython script, including .py suffix This script should exist in /etc/opt/srlinux/eventmgr or /opt/srlinux/eventmgr already. Explicit paths outside of these two directories are not permitted. :rel options: Options to be passed on each execution of the script :rel parent_event_handler: Relation to parent container
- relation nokia_srlinux::system::EventHandler parent_event_handler [1]¶
Relation to parent container Peer relation: List of all event handler instances
An event handler instance consists of a set of paths to be monitored for changes, and a Python script to execute if changes occur.
other end:
nokia_srlinux::system::EventHandler.instance [0:20]
- relation nokia_srlinux::system::event_handler::instance::Options options [0:1]¶
Relation to parent container Peer relation: Options to be passed on each execution of the script
other end:
nokia_srlinux::system::event_handler::instance::Options.parent_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::event_handler::setupInstanceYangContainer
constrainttrue
- entity nokia_srlinux::system::event_handler::instance::Options¶
Parents:
nokia_srlinux::Base
Options to be passed on each execution of the script Yang definition can be found here: srl_nokia-event-handler.yang:L263
- Rel object:
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::system::event_handler::Instance parent_instance [1]¶
Relation to parent container Peer relation: Options to be passed on each execution of the script
other end:
nokia_srlinux::system::event_handler::Instance.options [0:1]
- relation nokia_srlinux::system::event_handler::instance::options::Object object [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::event_handler::instance::options::Object.parent_options [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::event_handler::instance::options::Object¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-event-handler.yang:L266
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The name of this object
- attribute string? value=null¶
A single value to associate with this object
- attribute string[]? values=null¶
List of values to associate with this object, these are serialized as a JSON array when provided as input to the script :rel parent_options: Relation to parent container
- relation nokia_srlinux::system::event_handler::instance::Options parent_options [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::event_handler::instance::Options.object [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::ftp_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network-instances to run an FTP server in Yang definition can be found here: srl_nokia-ftp.yang:L84
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables or disables the FTP server in this network-instance
- attribute string name¶
Reference to a configured network-instance
- attribute yang::types::uint8? session_limit=null¶
Set a limit on the number of simultaneous active FTP sessions
- attribute nokia_srlinux::system::ftp_server::network_instance_source_address_t? source_address=null¶
IPv4 or IPv6 address for the FTP server to listen on within the network-instance Default behavior is to listen on ‘::’, which will listen on all addresses for both IPv4 and IPv6. In order to listen on IPv4 only, this field should be set to ‘0.0.0.0’.
- attribute yang::types::uint16? timeout=null¶
Set the idle timeout in seconds on FTP connections :rel parent_ftp_server: Relation to parent container
- relation nokia_srlinux::system::FtpServer parent_ftp_server [1]¶
Relation to parent container Peer relation: List of network-instances to run an FTP server in
other end:
nokia_srlinux::system::FtpServer.network_instance [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::gnmi_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network instances to run a gNMI server in Yang definition can be found here: srl_nokia-gnmi-server.yang:L212
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the gNMI server
- attribute bool? default_tls_profile=null¶
Whether to use default TLS profile (generated by the system) if none is configured via tls-profile field
- attribute string name¶
Reference to a configured network instance
- attribute nokia_srlinux::types::srl_nokia_common::port_number? port=null¶
Port the gNMI server will listen on for incoming connections
- attribute string[]? services=null¶
The gRPC service definitions that should be enabled for the specified server. A target may support only specific sets of services being enabled on the same server (e.g., it may be possible to run gNMI and gNOI services on the same port, but not to run gRIBI and gNMI on the same port). The set of gRPC services that are available to be configured is defined through the grpc-service identity, which can be extended for each protocol that is based on gRPC that is available on the device.
- attribute nokia_srlinux::system::gnmi_server::network_instance_source_address_t[]? source_address=null¶
List of IP addresses the gNMI server will listen on within the network instance
- attribute nokia_srlinux::system::gnmi_server::network_instance_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the gNMI server If none is specified, then TLS is not used.
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every gNMI request
- attribute nokia_srlinux::system::gnmi_server::network_instance_yang_models_t? yang_models=null¶
Specify yang-models to be used when origin field is not present in the gnmi requests :rel parent_gnmi_server: Relation to parent container
- relation nokia_srlinux::system::GnmiServer parent_gnmi_server [1]¶
Relation to parent container Peer relation: List of network instances to run a gNMI server in
other end:
nokia_srlinux::system::GnmiServer.network_instance [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::gnmi_server::UnixSocket¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state related to unix sockets Yang definition can be found here: srl_nokia-gnmi-server.yang:L197
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the gNMI server
- attribute bool? default_tls_profile=null¶
Whether to use default TLS profile (generated by the system) if none is configured via tls-profile field
- attribute string[]? services=null¶
The gRPC service definitions that should be enabled for the specified server. A target may support only specific sets of services being enabled on the same server (e.g., it may be possible to run gNMI and gNOI services on the same port, but not to run gRIBI and gNMI on the same port). The set of gRPC services that are available to be configured is defined through the grpc-service identity, which can be extended for each protocol that is based on gRPC that is available on the device.
- attribute nokia_srlinux::system::gnmi_server::unix_socket_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the gNMI server If none is specified, then TLS is not used.
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every gNMI request
- attribute nokia_srlinux::system::gnmi_server::unix_socket_yang_models_t? yang_models=null¶
Specify yang-models to be used when origin field is not present in the gnmi requests :rel parent_gnmi_server: Relation to parent container
- relation nokia_srlinux::system::GnmiServer parent_gnmi_server [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::GnmiServer.unix_socket [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::gnmi_server::setupUnixSocketYangContainer
constrainttrue
- entity nokia_srlinux::system::gribi_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network instances to run a gRIBI socket in Yang definition can be found here: srl_nokia-gribi-server.yang:L113
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the gRIBI service
- attribute string name¶
Reference to a configured network instance
- attribute nokia_srlinux::types::srl_nokia_common::port_number? port=null¶
TCP port the gRIBI server will listen on for incoming connections
- attribute nokia_srlinux::system::gribi_server::network_instance_source_address_t[]? source_address=null¶
List of IP addresses the gRIBI server will listen on within the network instance By default the gRIBI server will listen on all addresses in the network-instance.
- attribute nokia_srlinux::system::gribi_server::network_instance_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the gRIBI server
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every gRIBI RPC request :rel parent_gribi_server: Relation to parent container
- relation nokia_srlinux::system::GribiServer parent_gribi_server [1]¶
Relation to parent container Peer relation: List of network instances to run a gRIBI socket in
other end:
nokia_srlinux::system::GribiServer.network_instance [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::gribi_server::UnixSocket¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state related to unix sockets Yang definition can be found here: srl_nokia-gribi-server.yang:L87
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the gRIBI service
- attribute nokia_srlinux::system::gribi_server::unix_socket_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the gRIBI unix socket server If none is specified, then TLS is not used.
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every gRIBI RPC request :rel parent_gribi_server: Relation to parent container
- relation nokia_srlinux::system::GribiServer parent_gribi_server [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::GribiServer.unix_socket [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::json_rpc_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network instances to run the JSON RPC server in Yang definition can be found here: srl_nokia-json-rpc.yang:L159
- attribute string name¶
Reference to a configured network-instance :rel http: Top-level container for the JSON RPC HTTP server :rel https: Top-level container for the JSON-RPC HTTPS server :rel parent_json_rpc_server: Relation to parent container
- relation nokia_srlinux::system::JsonRpcServer parent_json_rpc_server [1]¶
Relation to parent container Peer relation: List of network instances to run the JSON RPC server in
other end:
nokia_srlinux::system::JsonRpcServer.network_instance [0:*]
- relation nokia_srlinux::system::json_rpc_server::network_instance::Http http [0:1]¶
Relation to parent container Peer relation: Top-level container for the JSON RPC HTTP server
other end:
nokia_srlinux::system::json_rpc_server::network_instance::Http.parent_network_instance [1]
- relation nokia_srlinux::system::json_rpc_server::network_instance::Https https [0:1]¶
Relation to parent container Peer relation: Top-level container for the JSON-RPC HTTPS server
other end:
nokia_srlinux::system::json_rpc_server::network_instance::Https.parent_network_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::json_rpc_server::UnixSocket¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state related to unix sockets Yang definition can be found here: srl_nokia-json-rpc.yang:L82
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the JSON RPC server via unix socket This requires the JSON RPC server to be globally enabled
- attribute nokia_srlinux::system::json_rpc_server::unix_socket_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the JSON RPC unix socket server If none is specified, then TLS is not used.
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every JSON RPC request :rel parent_json_rpc_server: Relation to parent container
- relation nokia_srlinux::system::JsonRpcServer parent_json_rpc_server [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::JsonRpcServer.unix_socket [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::json_rpc_server::network_instance::Http¶
Parents:
nokia_srlinux::Base
Top-level container for the JSON RPC HTTP server Yang definition can be found here: srl_nokia-json-rpc.yang:L173
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the HTTP JSON RPC server This requires the JSON RPC server to be globally enabled
- attribute nokia_srlinux::types::srl_nokia_common::port_number? port=null¶
The port the HTTP JSON RPC server will listen on for incoming connections
- attribute nokia_srlinux::system::json_rpc_server::network_instance::http_session_limit_t? session_limit=null¶
The number of concurrent requests the server will allow If a request comes in while this limit is reached, the request will block until another request is finished.
- attribute nokia_srlinux::system::json_rpc_server::network_instance::http_source_address_t[]? source_address=null¶
List of IP addresses the JSON RPC server will listen on within the network instance
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every JSON RPC request :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::system::json_rpc_server::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Top-level container for the JSON RPC HTTP server
other end:
nokia_srlinux::system::json_rpc_server::NetworkInstance.http [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::json_rpc_server::network_instance::Https¶
Parents:
nokia_srlinux::Base
Top-level container for the JSON-RPC HTTPS server Yang definition can be found here: srl_nokia-json-rpc.yang:L194
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the HTTPS JSON RPC server This requires the JSON RPC server to be globally enabled
- attribute nokia_srlinux::types::srl_nokia_common::port_number? port=null¶
Port the HTTPS JSON RPC server will listen on for incoming connections
- attribute nokia_srlinux::system::json_rpc_server::network_instance::https_session_limit_t? session_limit=null¶
The number of concurrent requests the server will allow If a request comes in while this limit is reached, the request will block until another request is finished.
- attribute nokia_srlinux::system::json_rpc_server::network_instance::https_source_address_t[]? source_address=null¶
List of IP addresses the JSON RPC server will listen on within the network instance
- attribute nokia_srlinux::system::json_rpc_server::network_instance::https_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the HTTP JSON RPC server
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every JSON RPC request :rel parent_network_instance: Relation to parent container
- relation nokia_srlinux::system::json_rpc_server::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: Top-level container for the JSON-RPC HTTPS server
other end:
nokia_srlinux::system::json_rpc_server::NetworkInstance.https [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::lldp::BgpAutoDiscovery¶
Parents:
nokia_srlinux::Base
Top-level container for global LLDP BGP auto discovery Yang definition can be found here: srl_nokia-lldp.yang:L568
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable LLDP BGP auto discovery at the system level Setting this to disable will override any per-interface LLDP BGP autodiscovery configuration
- attribute yang::types::uint32? group_id=null¶
A four byte integer to send on outgoing LLDPDUs This value can be used on the remote end to do peer group association. This sub-TLV is not sent by default
- attribute string[]? network_instance=null¶
List of network instances to enable LLDP BGP auto discovery in Default is to run LLDP BGP auto discovery in all network instances :rel parent_lldp: Relation to parent container
- relation nokia_srlinux::system::Lldp parent_lldp [1]¶
Relation to parent container Peer relation: Top-level container for global LLDP BGP auto discovery
other end:
nokia_srlinux::system::Lldp.bgp_auto_discovery [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::lldp::setupBgpAutoDiscoveryYangContainer
constrainttrue
- entity nokia_srlinux::system::lldp::Interface¶
Parents:
nokia_srlinux::Base
List of interfaces on which LLDP can be enabled Yang definition can be found here: srl_nokia-lldp.yang:L555
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable LLDP on the interface
- attribute nokia_srlinux::types::srl_nokia_lldp::base_interface_ref name¶
Reference to the LLDP Ethernet interface :rel bgp_auto_discovery: Configuration and state related to LLDP BGP auto discovery on the interface :rel parent_lldp: Relation to parent container
- relation nokia_srlinux::system::Lldp parent_lldp [1]¶
Relation to parent container Peer relation: List of interfaces on which LLDP can be enabled
other end:
nokia_srlinux::system::Lldp.interface [0:*]
- relation nokia_srlinux::system::lldp::interface::BgpAutoDiscovery bgp_auto_discovery [0:1]¶
Relation to parent container Peer relation: Configuration and state related to LLDP BGP auto discovery on the interface
other end:
nokia_srlinux::system::lldp::interface::BgpAutoDiscovery.parent_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::lldp::setupInterfaceYangContainer
constrainttrue
- entity nokia_srlinux::system::lldp::ManagementAddress¶
Parents:
nokia_srlinux::Base
List of subinterfaces to source management addresses from
This list is sent in the management address TLV by LLDP. Yang definition can be found here: srl_nokia-lldp.yang:L174
- attribute nokia_srlinux::types::srl_nokia_common::subinterface_all subinterface¶
Reference to the subinterface to source management addresses
- attribute nokia_srlinux::types::srl_nokia_lldp_types::management_address_type[]? type=null¶
Types of addresses sent in the management address TLV The enumerated value for the network address type identified in this TLV. This enumeration is defined in the ‘Assigned Numbers’ RFC [RFC3232] and the ianaAddressFamilyNumbers object. :rel parent_lldp: Relation to parent container
- relation nokia_srlinux::system::Lldp parent_lldp [1]¶
Relation to parent container Peer relation: List of subinterfaces to source management addresses from
This list is sent in the management address TLV by LLDP.
other end:
nokia_srlinux::system::Lldp.management_address [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::lldp::setupManagementAddressYangContainer
constrainttrue
- entity nokia_srlinux::system::lldp::interface::BgpAutoDiscovery¶
Parents:
nokia_srlinux::Base
Configuration and state related to LLDP BGP auto discovery on the interface Yang definition can be found here: srl_nokia-lldp.yang:L471
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable LLDP BGP auto discovery on this interface
- attribute yang::types::uint32? group_id=null¶
A four byte integer to send on outgoing LLDPDUs This value can be used on the remote end to do peer group association. This sub-TLV is not sent by default.
- attribute nokia_srlinux::system::lldp::interface::bgp_auto_discovery_peering_address_t[]? peering_address=null¶
List of IP addresses to be sent for BGP auto discovery Default values for this sub-TLV is to populate the addresses of the first subinterface of the interface the LLDPDU is being generated from, along with a unicast AFI/SAFI for IPv4 if an IPv4 address exists, and/or IPv6 if an IPv6 address exists. If neither of these exist in the system, LLDP will not add the TLV to outgoing LLDPDUs, unless the peering-address is manually configured on a per-LLDP-port basis. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::system::lldp::Interface parent_interface [1]¶
Relation to parent container Peer relation: Configuration and state related to LLDP BGP auto discovery on the interface
other end:
nokia_srlinux::system::lldp::Interface.bgp_auto_discovery [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::Buffer¶
Parents:
nokia_srlinux::Base
Log files maintained in memory, non-persistent across system reboots
These files are stored at directory /var/log/srlinux/buffer. Rotation into multiple files is available. Yang definition can be found here: srl_nokia-logging.yang:L367
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::restricted_file_name_type buffer_name¶
Base name of the file(s) to be stored in memory
- attribute nokia_srlinux::system::logging::buffer_filter_t[]? filter=null¶
A set of all-matching criteria that messages must fulfill in order to be captured
- attribute string? format=null¶
Text format of the output syslog messages, in legacy syslog $template style
- attribute nokia_srlinux::system::logging::buffer_persist_t? persist=null¶
Time in seconds to shadow the buffer to persistent storage Setting this field to 0 results in the buffer not being persisted. A value other than 0 will result in the log being persisted to disk based on the configured value. Logs with a non-zero persist value are persisted automatically on rollover, or at the configured value.
- attribute yang::types::uint16? rotate=null¶
Number of files to keep in rotation when a maximum file size is reached
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::usage_capacity_size_type? size=null¶
Number of bytes an individual output file cannot exceed The field allows the ‘K, M, or G’ suffixes as shorthand. When reaching that size, a rotation happens and subsequent data is stored in a new file with the same base name. :rel facility: List of facilities to source messages from :rel parent_logging: Relation to parent container :rel subsystem: Entity or entities that may produce messages to be captured
- relation nokia_srlinux::system::Logging parent_logging [1]¶
Relation to parent container Peer relation: Log files maintained in memory, non-persistent across system reboots
These files are stored at directory /var/log/srlinux/buffer. Rotation into multiple files is available.
other end:
nokia_srlinux::system::Logging.buffer [0:*]
- relation nokia_srlinux::system::logging::buffer::Facility facility [0:*]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::buffer::Facility.parent_buffer [1]
- relation nokia_srlinux::system::logging::buffer::Subsystem subsystem [0:*]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::buffer::Subsystem.parent_buffer [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::logging::setupBufferYangContainer
constrainttrue
- entity nokia_srlinux::system::logging::Console¶
Parents:
nokia_srlinux::Base
Hardware serial device normally used for bring-up and diagnostics Yang definition can be found here: srl_nokia-logging.yang:L323
- attribute nokia_srlinux::system::logging::console_filter_t[]? filter=null¶
A set of all-matching criteria that messages must fulfill in order to be captured
- attribute string? format=null¶
Text format of the output syslog messages, in legacy syslog $template style :rel facility: List of facilities to source messages from :rel parent_logging: Relation to parent container :rel subsystem: Entity or entities that may produce messages to be captured
- relation nokia_srlinux::system::Logging parent_logging [1]¶
Relation to parent container Peer relation: Hardware serial device normally used for bring-up and diagnostics
other end:
nokia_srlinux::system::Logging.console [0:1]
- relation nokia_srlinux::system::logging::console::Facility facility [0:*]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::console::Facility.parent_console [1]
- relation nokia_srlinux::system::logging::console::Subsystem subsystem [0:*]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::console::Subsystem.parent_console [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::logging::setupConsoleYangContainer
constrainttrue
- entity nokia_srlinux::system::logging::File¶
Parents:
nokia_srlinux::Base
Log files maintained on disk, persistent across system reboots
When a maximum file size is reached, the file is renamed and a maximum rotate number of them are kept. Yang definition can be found here: srl_nokia-logging.yang:L395
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::directory_name_type? directory=null¶
Fully qualified path of a directory where the log file(s) shall be maintained
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::restricted_file_name_type file_name¶
Base name of the file(s) to be stored on disk
- attribute nokia_srlinux::system::logging::file_filter_t[]? filter=null¶
A set of all-matching criteria that messages must fulfill in order to be captured
- attribute string? format=null¶
Text format of the output syslog messages, in legacy syslog $template style
- attribute yang::types::uint16? rotate=null¶
Number of files to keep in rotation when a maximum file size is reached
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::usage_capacity_size_type? size=null¶
Number of bytes an individual output file cannot exceed The field allows the ‘K, M, or G’ suffixes as shorthand. When reaching that size, a rotation happens and subsequent data is stored in a new file with the same base name. :rel facility: List of facilities to source messages from :rel parent_logging: Relation to parent container :rel subsystem: Entity or entities that may produce messages to be captured
- relation nokia_srlinux::system::Logging parent_logging [1]¶
Relation to parent container Peer relation: Log files maintained on disk, persistent across system reboots
When a maximum file size is reached, the file is renamed and a maximum rotate number of them are kept.
other end:
nokia_srlinux::system::Logging.file [0:*]
- relation nokia_srlinux::system::logging::file::Facility facility [0:*]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::file::Facility.parent_file [1]
- relation nokia_srlinux::system::logging::file::Subsystem subsystem [0:*]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::file::Subsystem.parent_file [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::logging::setupFileYangContainer
constrainttrue
- entity nokia_srlinux::system::logging::Filter¶
Parents:
nokia_srlinux::Base
Describes a set of critieria that captured messages are required to fulfill Yang definition can be found here: srl_nokia-logging.yang:L331
- attribute string? contains=null¶
Text to find in the MSG property of messages to capture from the stream This is slower than prefix.
- attribute nokia_srlinux::system::logging::filter_filter_name_t filter_name¶
Name of the filter
- attribute string? prefix=null¶
Text to be present at the beginning of the MSG property of a message This is a fast lookup.
- attribute string? regex=null¶
Extended regular expression to search in the MSG property of messages
- attribute string? tag=null¶
Text to be searched in the SYSLOGTAG property of messages Usually a program name or part of it. :rel facility: List of facilities to source messages from :rel parent_logging: Relation to parent container
- relation nokia_srlinux::system::Logging parent_logging [1]¶
Relation to parent container Peer relation: Describes a set of critieria that captured messages are required to fulfill
other end:
nokia_srlinux::system::Logging.filter [0:*]
- relation nokia_srlinux::system::logging::filter::Facility facility [0:*]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::filter::Facility.parent_filter [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::logging::setupFilterYangContainer
constrainttrue
- entity nokia_srlinux::system::logging::RemoteServer¶
Parents:
nokia_srlinux::Base
List of output remote syslog servers Yang definition can be found here: srl_nokia-logging.yang:L419
- attribute nokia_srlinux::system::logging::remote_server_filter_t[]? filter=null¶
A set of all-matching criteria that messages must fulfill in order to be captured
- attribute nokia_srlinux::system::logging::remote_server_host_t host¶
Domain or IP address of a remote syslog server destination
- attribute yang::types::uint32? remote_port=null¶
Transport port for syslog to use for messages sent to a remote server
- attribute nokia_srlinux::system::logging::remote_server_source_address_t? source_address=null¶
Source address for syslog to use for messages sent to a remote server If no source address is provided, then packets will be sent to the remote server using the source address indicated by the routing table.
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::transport_type? transport=null¶
Transport protocol for syslog to use for messages sent to a remote server :rel facility: List of facilities to source messages from :rel parent_logging: Relation to parent container :rel subsystem: Entity or entities that may produce messages to be captured
- relation nokia_srlinux::system::Logging parent_logging [1]¶
Relation to parent container Peer relation: List of output remote syslog servers
other end:
nokia_srlinux::system::Logging.remote_server [0:*]
- relation nokia_srlinux::system::logging::remote_server::Facility facility [0:*]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::remote_server::Facility.parent_remote_server [1]
- relation nokia_srlinux::system::logging::remote_server::Subsystem subsystem [0:*]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::remote_server::Subsystem.parent_remote_server [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::logging::setupRemoteServerYangContainer
constrainttrue
- entity nokia_srlinux::system::logging::buffer::Facility¶
Parents:
nokia_srlinux::Base
List of facilities to source messages from Yang definition can be found here: srl_nokia-logging.yang:L248
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type facility_name¶
Name of a Linux syslog facility :rel parent_buffer: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::Buffer parent_buffer [1]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::Buffer.facility [0:*]
- relation nokia_srlinux::system::logging::buffer::facility::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::buffer::facility::Priority.parent_facility [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::buffer::Subsystem¶
Parents:
nokia_srlinux::Base
Entity or entities that may produce messages to be captured Yang definition can be found here: srl_nokia-logging.yang:L262
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::subsystem_name_type subsystem_name¶
Reference to an available subsystem to source messages from :rel parent_buffer: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::Buffer parent_buffer [1]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::Buffer.subsystem [0:*]
- relation nokia_srlinux::system::logging::buffer::subsystem::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::buffer::subsystem::Priority.parent_subsystem [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::buffer::facility::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_facility: Relation to parent container
- relation nokia_srlinux::system::logging::buffer::Facility parent_facility [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::buffer::Facility.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::buffer::subsystem::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_subsystem: Relation to parent container
- relation nokia_srlinux::system::logging::buffer::Subsystem parent_subsystem [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::buffer::Subsystem.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::console::Facility¶
Parents:
nokia_srlinux::Base
List of facilities to source messages from Yang definition can be found here: srl_nokia-logging.yang:L248
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type facility_name¶
Name of a Linux syslog facility :rel parent_console: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::Console parent_console [1]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::Console.facility [0:*]
- relation nokia_srlinux::system::logging::console::facility::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::console::facility::Priority.parent_facility [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::console::Subsystem¶
Parents:
nokia_srlinux::Base
Entity or entities that may produce messages to be captured Yang definition can be found here: srl_nokia-logging.yang:L262
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::subsystem_name_type subsystem_name¶
Reference to an available subsystem to source messages from :rel parent_console: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::Console parent_console [1]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::Console.subsystem [0:*]
- relation nokia_srlinux::system::logging::console::subsystem::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::console::subsystem::Priority.parent_subsystem [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::console::facility::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_facility: Relation to parent container
- relation nokia_srlinux::system::logging::console::Facility parent_facility [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::console::Facility.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::console::subsystem::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_subsystem: Relation to parent container
- relation nokia_srlinux::system::logging::console::Subsystem parent_subsystem [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::console::Subsystem.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::file::Facility¶
Parents:
nokia_srlinux::Base
List of facilities to source messages from Yang definition can be found here: srl_nokia-logging.yang:L248
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type facility_name¶
Name of a Linux syslog facility :rel parent_file: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::File parent_file [1]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::File.facility [0:*]
- relation nokia_srlinux::system::logging::file::facility::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::file::facility::Priority.parent_facility [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::logging::file::setupFacilityYangContainer
constrainttrue
- entity nokia_srlinux::system::logging::file::Subsystem¶
Parents:
nokia_srlinux::Base
Entity or entities that may produce messages to be captured Yang definition can be found here: srl_nokia-logging.yang:L262
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::subsystem_name_type subsystem_name¶
Reference to an available subsystem to source messages from :rel parent_file: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::File parent_file [1]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::File.subsystem [0:*]
- relation nokia_srlinux::system::logging::file::subsystem::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::file::subsystem::Priority.parent_subsystem [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::file::facility::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_facility: Relation to parent container
- relation nokia_srlinux::system::logging::file::Facility parent_facility [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::file::Facility.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::file::subsystem::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_subsystem: Relation to parent container
- relation nokia_srlinux::system::logging::file::Subsystem parent_subsystem [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::file::Subsystem.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::filter::Facility¶
Parents:
nokia_srlinux::Base
List of facilities to source messages from Yang definition can be found here: srl_nokia-logging.yang:L248
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type facility_name¶
Name of a Linux syslog facility :rel parent_filter: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::Filter parent_filter [1]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::Filter.facility [0:*]
- relation nokia_srlinux::system::logging::filter::facility::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::filter::facility::Priority.parent_facility [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::filter::facility::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_facility: Relation to parent container
- relation nokia_srlinux::system::logging::filter::Facility parent_facility [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::filter::Facility.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::remote_server::Facility¶
Parents:
nokia_srlinux::Base
List of facilities to source messages from Yang definition can be found here: srl_nokia-logging.yang:L248
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::facility_name_type facility_name¶
Name of a Linux syslog facility :rel parent_remote_server: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::RemoteServer parent_remote_server [1]¶
Relation to parent container Peer relation: List of facilities to source messages from
other end:
nokia_srlinux::system::logging::RemoteServer.facility [0:*]
- relation nokia_srlinux::system::logging::remote_server::facility::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::remote_server::facility::Priority.parent_facility [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::remote_server::Subsystem¶
Parents:
nokia_srlinux::Base
Entity or entities that may produce messages to be captured Yang definition can be found here: srl_nokia-logging.yang:L262
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::subsystem_name_type subsystem_name¶
Reference to an available subsystem to source messages from :rel parent_remote_server: Relation to parent container :rel priority: Narrows the capture to a given severity, a range or a specific set of severities
- relation nokia_srlinux::system::logging::RemoteServer parent_remote_server [1]¶
Relation to parent container Peer relation: Entity or entities that may produce messages to be captured
other end:
nokia_srlinux::system::logging::RemoteServer.subsystem [0:*]
- relation nokia_srlinux::system::logging::remote_server::subsystem::Priority priority [0:1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::remote_server::subsystem::Priority.parent_subsystem [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::remote_server::facility::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_facility: Relation to parent container
- relation nokia_srlinux::system::logging::remote_server::Facility parent_facility [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::remote_server::Facility.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::logging::remote_server::subsystem::Priority¶
Parents:
nokia_srlinux::Base
Narrows the capture to a given severity, a range or a specific set of severities Yang definition can be found here: srl_nokia-logging.yang:L231
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type? match_above=null¶
At a given severity and above
- attribute nokia_srlinux::types::srl_nokia_logging::logging_top::priority_type[]? match_exact=null¶
Individually specified severities :rel parent_subsystem: Relation to parent container
- relation nokia_srlinux::system::logging::remote_server::Subsystem parent_subsystem [1]¶
Relation to parent container Peer relation: Narrows the capture to a given severity, a range or a specific set of severities
other end:
nokia_srlinux::system::logging::remote_server::Subsystem.priority [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::Group¶
Parents:
nokia_srlinux::Base
List of user-configured maintenance groups Yang definition can be found here: srl_nokia-maintenance-mode.yang:L117
- attribute string? maintenance_profile=null¶
Leaf reference to /system/maintenance/profile/name
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the maintenance group. :rel maintenance_mode: Container with options for activating and deactivating maintenance mode for this group :rel members: Container for specifying the members of the maintenance group - i.e. the components that will eventually be taken out of service for repair or replacement. :rel parent_maintenance: Relation to parent container
- relation nokia_srlinux::system::Maintenance parent_maintenance [1]¶
Relation to parent container Peer relation: List of user-configured maintenance groups
- relation nokia_srlinux::system::maintenance::group::MaintenanceMode maintenance_mode [0:1]¶
Relation to parent container Peer relation: Container with options for activating and deactivating maintenance mode for this group
other end:
nokia_srlinux::system::maintenance::group::MaintenanceMode.parent_group [1]
- relation nokia_srlinux::system::maintenance::group::Members members [0:1]¶
Relation to parent container Peer relation: Container for specifying the members of the maintenance group - i.e. the components that will eventually be taken out of service for repair or replacement.
other end:
nokia_srlinux::system::maintenance::group::Members.parent_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::maintenance::setupGroupYangContainer
constrainttrue
- entity nokia_srlinux::system::maintenance::Profile¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-maintenance-mode.yang:L154
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the maintenance profile :rel bgp: Container for BGP policies used to achieve traffic draining :rel isis: Container for ISIS configurations. :rel parent_maintenance: Relation to parent container
- relation nokia_srlinux::system::Maintenance parent_maintenance [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::maintenance::profile::Bgp bgp [0:1]¶
Relation to parent container Peer relation: Container for BGP policies used to achieve traffic draining
other end:
nokia_srlinux::system::maintenance::profile::Bgp.parent_profile [1]
- relation nokia_srlinux::system::maintenance::profile::Isis isis [0:1]¶
Relation to parent container Peer relation: Container for ISIS configurations.
other end:
nokia_srlinux::system::maintenance::profile::Isis.parent_profile [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::maintenance::setupProfileYangContainer
constrainttrue
- entity nokia_srlinux::system::maintenance::group::MaintenanceMode¶
Parents:
nokia_srlinux::Base
Container with options for activating and deactivating maintenance mode for this group Yang definition can be found here: srl_nokia-maintenance-mode.yang:L126
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable maintenance mode for this group The enable setting is blocked if there is another maintenance group with at least one BGP session in its scope that overlaps with this maintenance group and that other maintenance group is currently in maintenance mode. While a maintenance group is in maintenance mode it is not possible to modify the BGP configuration of its members. :rel parent_group: Relation to parent container
- relation nokia_srlinux::system::maintenance::Group parent_group [1]¶
Relation to parent container Peer relation: Container with options for activating and deactivating maintenance mode for this group
other end:
nokia_srlinux::system::maintenance::Group.maintenance_mode [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::group::Members¶
Parents:
nokia_srlinux::Base
Container for specifying the members of the maintenance group - i.e. the components that will eventually be taken out of service for repair or replacement. Yang definition can be found here: srl_nokia-maintenance-mode.yang:L56
- Rel bgp:
Container for specifying the BGP members of the maintenance group
- Rel isis:
Container for specifying the ISIS members of the maintenance group
- Rel parent_group:
Relation to parent container
- relation nokia_srlinux::system::maintenance::Group parent_group [1]¶
Relation to parent container Peer relation: Container for specifying the members of the maintenance group - i.e. the components that will eventually be taken out of service for repair or replacement.
other end:
nokia_srlinux::system::maintenance::Group.members [0:1]
- relation nokia_srlinux::system::maintenance::group::members::Bgp bgp [0:1]¶
Relation to parent container Peer relation: Container for specifying the BGP members of the maintenance group
other end:
nokia_srlinux::system::maintenance::group::members::Bgp.parent_members [1]
- relation nokia_srlinux::system::maintenance::group::members::Isis isis [0:1]¶
Relation to parent container Peer relation: Container for specifying the ISIS members of the maintenance group
other end:
nokia_srlinux::system::maintenance::group::members::Isis.parent_members [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::group::members::Bgp¶
Parents:
nokia_srlinux::Base
Container for specifying the BGP members of the maintenance group Yang definition can be found here: srl_nokia-maintenance-mode.yang:L59
- Rel network_instance:
List of network instances with one or more peers to be placed in maintenance mode
- Rel parent_members:
Relation to parent container
- relation nokia_srlinux::system::maintenance::group::Members parent_members [1]¶
Relation to parent container Peer relation: Container for specifying the BGP members of the maintenance group
other end:
nokia_srlinux::system::maintenance::group::Members.bgp [0:1]
- relation nokia_srlinux::system::maintenance::group::members::bgp::NetworkInstance network_instance [0:*]¶
Relation to parent container Peer relation: List of network instances with one or more peers to be placed in maintenance mode
other end:
nokia_srlinux::system::maintenance::group::members::bgp::NetworkInstance.parent_bgp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::group::members::Isis¶
Parents:
nokia_srlinux::Base
Container for specifying the ISIS members of the maintenance group Yang definition can be found here: srl_nokia-maintenance-mode.yang:L99
- attribute string[]? network_instances=null¶
List of network instances that should be part of the maintenance group. :rel parent_members: Relation to parent container
- relation nokia_srlinux::system::maintenance::group::Members parent_members [1]¶
Relation to parent container Peer relation: Container for specifying the ISIS members of the maintenance group
other end:
nokia_srlinux::system::maintenance::group::Members.isis [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::group::members::bgp::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network instances with one or more peers to be placed in maintenance mode Yang definition can be found here: srl_nokia-maintenance-mode.yang:L62
- attribute string name¶
A unique name identifying the network instance
- attribute nokia_srlinux::system::maintenance::group::members::bgp::network_instance_neighbor_t[]? neighbor=null¶
List of BGP neighbors that belong to the network instance and that should be part of the maintenance group It is not necessary to list neighbors that are members of peer-groups that are already listed. If this list is empty and so is the group list, then the system interprets the meaning as ALL static and dynamic sessions belonging to the specified network-instance.
- attribute nokia_srlinux::system::maintenance::group::members::bgp::network_instance_peer_group_t[]? peer_group=null¶
List of BGP peer groups that belong to the network instance and that should be part of the maintenance group If this list is empty and so is the neighbor list, then the system interprets the meaning as ALL static and dynamic sessions belonging to the specified network-instance. :rel parent_bgp: Relation to parent container
- relation nokia_srlinux::system::maintenance::group::members::Bgp parent_bgp [1]¶
Relation to parent container Peer relation: List of network instances with one or more peers to be placed in maintenance mode
other end:
nokia_srlinux::system::maintenance::group::members::Bgp.network_instance [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::profile::Bgp¶
Parents:
nokia_srlinux::Base
Container for BGP policies used to achieve traffic draining Yang definition can be found here: srl_nokia-maintenance-mode.yang:L161
- attribute string? export_policy=null¶
A reference to the pre-configured routing policy to apply as an additional/final export policy on BGP sessions in the maintenance group
- attribute string? import_policy=null¶
A reference to the pre-configured routing policy to apply as an additional/final import policy on BGP sessions in the maintenance group :rel parent_profile: Relation to parent container
- relation nokia_srlinux::system::maintenance::Profile parent_profile [1]¶
Relation to parent container Peer relation: Container for BGP policies used to achieve traffic draining
other end:
nokia_srlinux::system::maintenance::Profile.bgp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::profile::Isis¶
Parents:
nokia_srlinux::Base
Container for ISIS configurations. Yang definition can be found here: srl_nokia-maintenance-mode.yang:L179
- Rel overload:
Container for ISIS overload configurations.
- Rel parent_profile:
Relation to parent container
- relation nokia_srlinux::system::maintenance::Profile parent_profile [1]¶
Relation to parent container Peer relation: Container for ISIS configurations.
other end:
nokia_srlinux::system::maintenance::Profile.isis [0:1]
- relation nokia_srlinux::system::maintenance::profile::isis::Overload overload [0:1]¶
Relation to parent container Peer relation: Container for ISIS overload configurations.
other end:
nokia_srlinux::system::maintenance::profile::isis::Overload.parent_isis [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::maintenance::profile::isis::Overload¶
Parents:
nokia_srlinux::Base
Container for ISIS overload configurations. Yang definition can be found here: srl_nokia-maintenance-mode.yang:L183
- attribute bool? max_metric=null¶
When set to true transit links are advertised with a wide metric of 0xffffffe and a narrow metric of 0x3f
- attribute bool? set_bit=null¶
When set to true, the Overload bit is set :rel parent_isis: Relation to parent container
- relation nokia_srlinux::system::maintenance::profile::Isis parent_isis [1]¶
Relation to parent container Peer relation: Container for ISIS overload configurations.
other end:
nokia_srlinux::system::maintenance::profile::Isis.overload [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::management::Openconfig¶
Parents:
nokia_srlinux::Base
Top-level container for options relating to OpenConfig Yang definition can be found here: srl_nokia-openconfig.yang:L38
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable or disable the OpenConfig management server This will disable OpenConfig throughout the system, and bring any gRPC servers that use it operationally down. :rel parent_management: Relation to parent container
- relation nokia_srlinux::system::Management parent_management [1]¶
Relation to parent container Peer relation: Top-level container for options relating to OpenConfig
other end:
nokia_srlinux::system::Management.openconfig [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::management::setupOpenconfigYangContainer
constrainttrue
- entity nokia_srlinux::system::mirroring::MirroringInstance¶
Parents:
nokia_srlinux::Base
Mirroring instances configured on the local system Yang definition can be found here: srl_nokia-mirroring.yang:L94
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf contains the configured, desired state of the mirroring instance.
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
A user-entered description of this mirroring instance.
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
A unique name identifying the mirroring instance :rel mirror_destination: Configure mirror destination :rel mirror_source: Configure mirror source(s) :rel parent_mirroring: Relation to parent container
- relation nokia_srlinux::system::Mirroring parent_mirroring [1]¶
Relation to parent container Peer relation: Mirroring instances configured on the local system
other end:
nokia_srlinux::system::Mirroring.mirroring_instance [0:8]
- relation nokia_srlinux::system::mirroring::mirroring_instance::MirrorDestination mirror_destination [0:1]¶
Relation to parent container Peer relation: Configure mirror destination
- relation nokia_srlinux::system::mirroring::mirroring_instance::MirrorSource mirror_source [0:1]¶
Relation to parent container Peer relation: Configure mirror source(s)
other end:
nokia_srlinux::system::mirroring::mirroring_instance::MirrorSource.parent_mirroring_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::MirrorDestination¶
Parents:
nokia_srlinux::Base
Configure mirror destination Yang definition can be found here: srl_nokia-mirroring.yang:L219
- Rel parent_mirroring_instance:
Relation to parent container
- Rel remote:
- relation nokia_srlinux::system::mirroring::MirroringInstance parent_mirroring_instance [1]¶
Relation to parent container Peer relation: Configure mirror destination
other end:
nokia_srlinux::system::mirroring::MirroringInstance.mirror_destination [0:1]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::Remote remote [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::MirrorSource¶
Parents:
nokia_srlinux::Base
Configure mirror source(s) Yang definition can be found here: srl_nokia-mirroring.yang:L140
- Rel acl:
- Rel parent_mirroring_instance:
Relation to parent container
- relation nokia_srlinux::system::mirroring::MirroringInstance parent_mirroring_instance [1]¶
Relation to parent container Peer relation: Configure mirror source(s)
other end:
nokia_srlinux::system::mirroring::MirroringInstance.mirror_source [0:1]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl acl [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl.parent_mirror_source [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::Remote¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L231
- attribute nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::remote_encap_t? encap=null¶
- attribute string? network_instance=null¶
network instance to intitiate remote mirror tunnel :rel parent_mirror_destination: Relation to parent container :rel tunnel_end_points:
- relation nokia_srlinux::system::mirroring::mirroring_instance::MirrorDestination parent_mirror_destination [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::MirrorDestination.remote [0:1]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::remote::TunnelEndPoints tunnel_end_points [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::remote::TunnelEndPoints¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L264
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
This leaf contains the configured, desired state of the remote mirror tunnel
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? dst_ipv4=null¶
remote mirror tunnel destination endpoint IPv4 address
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? dst_ipv6=null¶
remote mirror tunnel destination endpoint IPv6 adress
- attribute nokia_srlinux::types::srl_nokia_common::ipv4_address? src_ipv4=null¶
remote mirror tunnel source endpoint IPv4 address
- attribute nokia_srlinux::types::srl_nokia_common::ipv6_address? src_ipv6=null¶
remote mirror tunnel source endpoint IPv6 address :rel parent_remote: Relation to parent container
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::Remote parent_remote [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L179
- Rel ipv4_filter:
- Rel ipv6_filter:
- Rel parent_mirror_source:
Relation to parent container
- relation nokia_srlinux::system::mirroring::mirroring_instance::MirrorSource parent_mirror_source [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::MirrorSource.acl [0:1]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv4Filter ipv4_filter [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv4Filter.parent_acl [1]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv6Filter ipv6_filter [0:*]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv6Filter.parent_acl [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv4Filter¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L180
- attribute string name¶
- Rel entry:
- rel parent_acl:
Relation to parent container
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl parent_acl [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl.ipv4_filter [0:*]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv4_filter::Entry entry [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv6Filter¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L196
- attribute string name¶
- Rel entry:
- rel parent_acl:
Relation to parent container
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl parent_acl [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::Acl.ipv6_filter [0:*]
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv6_filter::Entry entry [0:*]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv4_filter::Entry¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L187
- attribute nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv4_filter::entry_sequence_id_t sequence_id¶
- Rel parent_ipv4_filter:
Relation to parent container
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv4Filter parent_ipv4_filter [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv4Filter.entry [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv6_filter::Entry¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-mirroring.yang:L203
- attribute nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv6_filter::entry_sequence_id_t sequence_id¶
- Rel parent_ipv6_filter:
Relation to parent container
- relation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv6Filter parent_ipv6_filter [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::Ipv6Filter.entry [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mpls::LabelRanges¶
Parents:
nokia_srlinux::Base
Container for managing MPLS label blocks Yang definition can be found here: srl_nokia-mpls-label-management.yang:L205
- Rel dynamic:
List of dynamic label blocks
When a client application binds its operation to a dynamic label block that client application is expected to just ask for the next available label within the dynamic label block.
At this time a dynamic label block cannot be shared by multiple different clients/protocols. Each protocol needing dynamic labels must have its own label block. :rel parent_mpls: Relation to parent container :rel static: List of static label blocks
When a client application binds its operation to a static label block that client application is expected to specify the exact label value it wants to use every time it requests a label within the static label block.
- relation nokia_srlinux::system::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Container for managing MPLS label blocks
- relation nokia_srlinux::system::mpls::label_ranges::Dynamic dynamic [0:*]¶
Relation to parent container Peer relation: List of dynamic label blocks
When a client application binds its operation to a dynamic label block that client application is expected to just ask for the next available label within the dynamic label block.
At this time a dynamic label block cannot be shared by multiple different clients/protocols. Each protocol needing dynamic labels must have its own label block.
other end:
nokia_srlinux::system::mpls::label_ranges::Dynamic.parent_label_ranges [1]
- relation nokia_srlinux::system::mpls::label_ranges::Static static [0:*]¶
Relation to parent container Peer relation: List of static label blocks
When a client application binds its operation to a static label block that client application is expected to specify the exact label value it wants to use every time it requests a label within the static label block.
other end:
nokia_srlinux::system::mpls::label_ranges::Static.parent_label_ranges [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::mpls::setupLabelRangesYangContainer
constrainttrue
- entity nokia_srlinux::system::mpls::Services¶
Parents:
nokia_srlinux::Base
Container for system wide Services MPLS label management Yang definition can be found here: srl_nokia-mpls-label-management.yang:L194
- Rel evpn:
Container for system wide Services EVPN MPLS label management
- Rel network_instance:
Container for system wide Service Network Instance MPLS label management
- Rel parent_mpls:
Relation to parent container
- relation nokia_srlinux::system::Mpls parent_mpls [1]¶
Relation to parent container Peer relation: Container for system wide Services MPLS label management
other end:
nokia_srlinux::system::Mpls.services [0:1]
- relation nokia_srlinux::system::mpls::services::Evpn evpn [0:1]¶
Relation to parent container Peer relation: Container for system wide Services EVPN MPLS label management
other end:
nokia_srlinux::system::mpls::services::Evpn.parent_services [1]
- relation nokia_srlinux::system::mpls::services::NetworkInstance network_instance [0:1]¶
Relation to parent container Peer relation: Container for system wide Service Network Instance MPLS label management
other end:
nokia_srlinux::system::mpls::services::NetworkInstance.parent_services [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::mpls::setupServicesYangContainer
constrainttrue
- entity nokia_srlinux::system::mpls::label_ranges::Dynamic¶
Parents:
nokia_srlinux::Base
List of dynamic label blocks
When a client application binds its operation to a dynamic label block that client application is expected to just ask for the next available label within the dynamic label block.
At this time a dynamic label block cannot be shared by multiple different clients/protocols. Each protocol needing dynamic labels must have its own label block. Yang definition can be found here: srl_nokia-mpls-label-management.yang:L227
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? end_label=null¶
The ending label value of the label block. When the status is not-ready or updating, the state value may be different from the configured value
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The name of the dynamic label block
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? start_label=null¶
The starting label value of the label block. When the status is not-ready or updating, the state value may be different from the configured value :rel parent_label_ranges: Relation to parent container
- relation nokia_srlinux::system::mpls::LabelRanges parent_label_ranges [1]¶
Relation to parent container Peer relation: List of dynamic label blocks
When a client application binds its operation to a dynamic label block that client application is expected to just ask for the next available label within the dynamic label block.
At this time a dynamic label block cannot be shared by multiple different clients/protocols. Each protocol needing dynamic labels must have its own label block.
other end:
nokia_srlinux::system::mpls::LabelRanges.dynamic [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mpls::label_ranges::Static¶
Parents:
nokia_srlinux::Base
List of static label blocks
When a client application binds its operation to a static label block that client application is expected to specify the exact label value it wants to use every time it requests a label within the static label block. Yang definition can be found here: srl_nokia-mpls-label-management.yang:L208
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? end_label=null¶
The ending label value of the label block. When the status is not-ready or updating, the state value may be different from the configured value
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
The name of the static label block
When set to true, the label block can be shared by multiple protoccols. When set to false, the label block is dedicated to one protocol.
- attribute nokia_srlinux::types::srl_nokia_common::mpls_label_non_reserved? start_label=null¶
The starting label value of the label block. When the status is not-ready or updating, the state value may be different from the configured value :rel parent_label_ranges: Relation to parent container
- relation nokia_srlinux::system::mpls::LabelRanges parent_label_ranges [1]¶
Relation to parent container Peer relation: List of static label blocks
When a client application binds its operation to a static label block that client application is expected to specify the exact label value it wants to use every time it requests a label within the static label block.
other end:
nokia_srlinux::system::mpls::LabelRanges.static [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::mpls::services::Evpn¶
Parents:
nokia_srlinux::Base
Container for system wide Services EVPN MPLS label management Yang definition can be found here: srl_nokia-mpls-services-evpn-label-management.yang:L36
- attribute string? dynamic_label_block=null¶
Reference to a dynamic label block :rel parent_services: Relation to parent container
- relation nokia_srlinux::system::mpls::Services parent_services [1]¶
Relation to parent container Peer relation: Container for system wide Services EVPN MPLS label management
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::mpls::services::setupEvpnYangContainer
constrainttrue
- entity nokia_srlinux::system::mpls::services::NetworkInstance¶
Parents:
nokia_srlinux::Base
Container for system wide Service Network Instance MPLS label management Yang definition can be found here: srl_nokia-mpls-services-network-instance-label-management.yang:L30
- attribute string? dynamic_label_block=null¶
Reference to the dynamic label block used by network-instances The label block is used by all the applications that require MPLS label allocation in a network-instance. For example, EVPN-MPLS services, IP-VPN or Pseudowires.
- attribute string? static_label_block=null¶
Reference to the static label block used by network-instances The label block is used by all the applications that require static MPLS label allocation in a network-instance. For example, Pseudowires with static vc labels. :rel parent_services: Relation to parent container
- relation nokia_srlinux::system::mpls::Services parent_services [1]¶
Relation to parent container Peer relation: Container for system wide Service Network Instance MPLS label management
other end:
nokia_srlinux::system::mpls::Services.network_instance [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::multicast::MulticastIds¶
Parents:
nokia_srlinux::Base
system multicast id information Yang definition can be found here: srl_nokia-system-multicast.yang:L90
- Rel parent_multicast:
Relation to parent container
- relation nokia_srlinux::system::Multicast parent_multicast [1]¶
Relation to parent container Peer relation: system multicast id information
other end:
nokia_srlinux::system::Multicast.multicast_ids [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::multicast::setupMulticastIdsYangContainer
constrainttrue
- entity nokia_srlinux::system::network_instance::Protocols¶
Parents:
nokia_srlinux::Base
The routing protocols that are enabled for this network-instance. Yang definition can be found here: srl_nokia-system-network-instance.yang:L50
- Rel bgp_vpn:
- Rel evpn:
- Rel parent_network_instance:
Relation to parent container
- relation nokia_srlinux::system::NetworkInstance parent_network_instance [1]¶
Relation to parent container Peer relation: The routing protocols that are enabled for this network-instance.
other end:
nokia_srlinux::system::NetworkInstance.protocols [0:1]
- relation nokia_srlinux::system::network_instance::protocols::BgpVpn bgp_vpn [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::protocols::BgpVpn.parent_protocols [1]
- relation nokia_srlinux::system::network_instance::protocols::Evpn evpn [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::protocols::Evpn.parent_protocols [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::BgpVpn¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-vpn.yang:L42
- Rel bgp_instance:
List of bgp-vpn instances configured in the system network-instance. Only one instance allowed in the current release.
- Rel parent_protocols:
Relation to parent container
- relation nokia_srlinux::system::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::Protocols.bgp_vpn [0:1]
- relation nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance bgp_instance [0:1]¶
Relation to parent container Peer relation: List of bgp-vpn instances configured in the system network-instance. Only one instance allowed in the current release.
other end:
nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance.parent_bgp_vpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::Evpn¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance.yang:L54
- Rel ethernet_segments:
- Rel parent_protocols:
Relation to parent container
- relation nokia_srlinux::system::network_instance::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::Protocols.evpn [0:1]
- relation nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments ethernet_segments [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments.parent_evpn [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance¶
Parents:
nokia_srlinux::Base
List of bgp-vpn instances configured in the system network-instance. Only one instance allowed in the current release. Yang definition can be found here: srl_nokia-system-network-instance-bgp-vpn.yang:L44
- attribute nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance_id_t id¶
The index of the bgp-vpn instance :rel parent_bgp_vpn: Relation to parent container :rel route_distinguisher: Route Distinguisher (RD) of the bgp-vpn instance. :rel route_target: Route Target (RT) of the system bgp-vpn instance.
- relation nokia_srlinux::system::network_instance::protocols::BgpVpn parent_bgp_vpn [1]¶
Relation to parent container Peer relation: List of bgp-vpn instances configured in the system network-instance. Only one instance allowed in the current release.
other end:
nokia_srlinux::system::network_instance::protocols::BgpVpn.bgp_instance [0:1]
- relation nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance::RouteDistinguisher route_distinguisher [0:1]¶
Relation to parent container Peer relation: Route Distinguisher (RD) of the bgp-vpn instance.
- relation nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance::RouteTarget route_target [0:1]¶
Relation to parent container Peer relation: Route Target (RT) of the system bgp-vpn instance.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance::RouteDistinguisher¶
Parents:
nokia_srlinux::Base
Route Distinguisher (RD) of the bgp-vpn instance. Yang definition can be found here: srl_nokia-system-network-instance-bgp-vpn.yang:L56
- Rel parent_bgp_instance:
Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Route Distinguisher (RD) of the bgp-vpn instance.
other end:
nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance.route_distinguisher [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance::RouteTarget¶
Parents:
nokia_srlinux::Base
Route Target (RT) of the system bgp-vpn instance. Yang definition can be found here: srl_nokia-system-network-instance-bgp-vpn.yang:L81
- Rel parent_bgp_instance:
Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Route Target (RT) of the system bgp-vpn instance.
other end:
nokia_srlinux::system::network_instance::protocols::bgp_vpn::BgpInstance.route_target [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L385
- Rel bgp_instance:
bgp global instances configured in net-instance
- Rel parent_evpn:
Relation to parent container
- Rel timers:
- relation nokia_srlinux::system::network_instance::protocols::Evpn parent_evpn [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::protocols::Evpn.ethernet_segments [0:1]
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::BgpInstance bgp_instance [0:1]¶
Relation to parent container Peer relation: bgp global instances configured in net-instance
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::Timers timers [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::BgpInstance¶
Parents:
nokia_srlinux::Base
bgp global instances configured in net-instance Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L389
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance_id_t id¶
- Rel ethernet_segment:
Ethernet Segment configuration and state. :rel parent_ethernet_segments: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments parent_ethernet_segments [1]¶
Relation to parent container Peer relation: bgp global instances configured in net-instance
other end:
nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments.bgp_instance [0:1]
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::EthernetSegment ethernet_segment [0:1024]¶
Relation to parent container Peer relation: Ethernet Segment configuration and state.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::Timers¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L139
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::timers_activation_timer_t? activation_timer=null¶
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::timers_boot_timer_t? boot_timer=null¶
Remaining time before running BGP EVPN multi-homing DF election algorithm :rel parent_ethernet_segments: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments parent_ethernet_segments [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::network_instance::protocols::evpn::EthernetSegments.timers [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::EthernetSegment¶
Parents:
nokia_srlinux::Base
Ethernet Segment configuration and state. Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L399
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Admin state of the ethernet segment
- attribute nokia_srlinux::types::srl_nokia_common::esi? esi=null¶
The 10-byte Ethernet Segment Identifier of the ethernet segment. ESI-0 or MAX-ESI values are not allowed. ESI values with bytes 1-6 all zeros are not allowed since they would produce a null ESI-import route-target.
- attribute nokia_srlinux::types::srl_nokia_system_network_instance_bgp_evpn_ethernet_segments::multi_homing_mode? multi_homing_mode=null¶
Multi-homing mode of the ethernet segment. The state of this leaf can be different than the configured value in cases where the configured value is ‘all-active’ and the multi-homing mode advertised by the ES peers in the AD per-ES routes is ‘single-active’. In this case, the state of this leaf will show ‘single-active’.
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment_name_t name¶
A unique name identifying the ethernet segment.
- attribute nokia_srlinux::types::srl_nokia_system_network_instance_bgp_evpn_ethernet_segments::es_type? type=null¶
Ethernet Segment type. :rel df_election: :rel interface: :rel next_hop: :rel parent_bgp_instance: Relation to parent container :rel routes:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::BgpInstance parent_bgp_instance [1]¶
Relation to parent container Peer relation: Ethernet Segment configuration and state.
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::DfElection df_election [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::Interface interface [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::NextHop next_hop [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::Routes routes [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::DfElection¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L177
- Rel algorithm:
- Rel interface_standby_signaling_on_non_df:
- Rel parent_ethernet_segment:
Relation to parent container
- Rel timers:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::EthernetSegment parent_ethernet_segment [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::Algorithm algorithm [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::InterfaceStandbySignalingOnNonDf interface_standby_signaling_on_non_df [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::Timers timers [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::Interface¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L463
- attribute string ethernet_interface¶
Interface associated with the ethernet segment. :rel parent_ethernet_segment: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::EthernetSegment parent_ethernet_segment [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::NextHop¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L483
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::next_hop_l3_next_hop_t l3_next_hop¶
Layer-3 next-hop associated with the ethernet segment. :rel evi: evi range for this ethernet-segment association :rel parent_ethernet_segment: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::EthernetSegment parent_ethernet_segment [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::next_hop::Evi evi [0:1]¶
Relation to parent container Peer relation: evi range for this ethernet-segment association
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::Routes¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L110
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes_next_hop_t? next_hop=null¶
The ip-address that will be used as the bgp-next hop for all ES and AD per-ES routes advertised for this Ethernet Segment. :rel ethernet_segment: :rel parent_ethernet_segment: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::EthernetSegment parent_ethernet_segment [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes::EthernetSegment ethernet_segment [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::Algorithm¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L200
- attribute nokia_srlinux::types::srl_nokia_system_network_instance_bgp_evpn_ethernet_segments::df_algorithm_type? type=null¶
Designated Forwarder algorithm type for this ethernet-segment. :rel manual_alg: :rel parent_df_election: Relation to parent container :rel preference_alg:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::DfElection parent_df_election [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::ManualAlg manual_alg [0:1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::PreferenceAlg preference_alg [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::InterfaceStandbySignalingOnNonDf¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L189
- Rel parent_df_election:
Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::DfElection parent_df_election [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::Timers¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L178
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::timers_activation_timer_t? activation_timer=null¶
Remaining activation timer per Ethernet segment :rel parent_df_election: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::DfElection parent_df_election [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::ManualAlg¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L273
- Rel parent_algorithm:
Relation to parent container
- Rel primary_evi_range:
evi range for this ethernet-segment
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::Algorithm parent_algorithm [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::manual_alg::PrimaryEviRange primary_evi_range [0:*]¶
Relation to parent container Peer relation: evi range for this ethernet-segment
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::PreferenceAlg¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L215
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg_preference_value_t? preference_value=null¶
Preference that is used to elect the designated forwarder :rel capabilities: :rel parent_algorithm: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::Algorithm parent_algorithm [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg::Capabilities capabilities [0:1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::manual_alg::PrimaryEviRange¶
Parents:
nokia_srlinux::Base
evi range for this ethernet-segment Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L278
- attribute nokia_srlinux::types::srl_nokia_common::evi? end_evi=null¶
end of the evi-range for this ethernet-segment
- attribute nokia_srlinux::types::srl_nokia_common::evi start_evi¶
start of the evi-range for this ethernet-segment :rel parent_manual_alg: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::ManualAlg parent_manual_alg [1]¶
Relation to parent container Peer relation: evi range for this ethernet-segment
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg::Capabilities¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L249
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg::capabilities_ac_df_t? ac_df=null¶
Attachment Circuit influenced DF Election.
- attribute bool? non_revertive=null¶
Non Revertive mode. If set to true, the ‘Don’t Preempt Me’ capability is advertised in the ES route. :rel parent_preference_alg: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::PreferenceAlg parent_preference_alg [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::next_hop::Evi¶
Parents:
nokia_srlinux::Base
evi range for this ethernet-segment association Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L494
- attribute nokia_srlinux::types::srl_nokia_common::evi start¶
start of the evi-range for this ethernet-segment :rel parent_next_hop: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::NextHop parent_next_hop [1]¶
Relation to parent container Peer relation: evi range for this ethernet-segment association
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes::EthernetSegment¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-system-network-instance-bgp-evpn-ethernet-segments.yang:L111
- attribute nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes::ethernet_segment_originating_ip_t? originating_ip=null¶
The originating ip-address that the inclusive multicast route will be advertised with in this evpn instance :rel parent_routes: Relation to parent container
- relation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::Routes parent_routes [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::ntp::Server¶
Parents:
nokia_srlinux::Base
List of NTP servers to use for system clock synchronization Yang definition can be found here: srl_nokia-ntp.yang:L132
- attribute nokia_srlinux::system::ntp::server_address_t address¶
Domain or IP address of the NTP server IP address may be either IPv4 or IPv6. Domain resolution requires working DNS configuration in the same network-instance.
- attribute bool? iburst=null¶
Indicates whether this server should enable burst synchronization or not iburst, or initial burst, improves the time taken for initial synchronization by sending a burst of eight packets instead of the usual one, these packets are spaced by a two second delay
- attribute bool? prefer=null¶
Indicates whether this server should be preferred or not All other things being equal, this host will be chosen for synchronization among a set of correctly operating NTP servers :rel parent_ntp: Relation to parent container
- relation nokia_srlinux::system::Ntp parent_ntp [1]¶
Relation to parent container Peer relation: List of NTP servers to use for system clock synchronization
other end:
nokia_srlinux::system::Ntp.server [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::ntp::setupServerYangContainer
constrainttrue
- entity nokia_srlinux::system::p4rt_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network instances to run a P4Runtime socket in Yang definition can be found here: srl_nokia-p4rt-server.yang:L97
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the P4Runtime service
- attribute string name¶
Reference to a configured network instance
- attribute nokia_srlinux::types::srl_nokia_common::port_number? port=null¶
TCP port the P4Runtime server will listen on for incoming connections
- attribute nokia_srlinux::system::p4rt_server::network_instance_source_address_t[]? source_address=null¶
List of IP addresses the P4Runtime server will listen on within the network instance By default the P4Runtime server will listen on all addresses in the network-instance.
- attribute nokia_srlinux::system::p4rt_server::network_instance_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the P4Runtime server
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every P4Runtime RPC request :rel parent_p4rt_server: Relation to parent container
- relation nokia_srlinux::system::P4rtServer parent_p4rt_server [1]¶
Relation to parent container Peer relation: List of network instances to run a P4Runtime socket in
other end:
nokia_srlinux::system::P4rtServer.network_instance [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::p4rt_server::UnixSocket¶
Parents:
nokia_srlinux::Base
Top-level container for configuration and state related to unix sockets Yang definition can be found here: srl_nokia-p4rt-server.yang:L71
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administratively enable or disable the P4Runtime service
- attribute nokia_srlinux::system::p4rt_server::unix_socket_tls_profile_t? tls_profile=null¶
Reference to the TLS profile to use on the P4Runtime unix socket server If none is specified, then TLS is not used.
- attribute bool? use_authentication=null¶
Enable or disable the use of username/password authentication for every P4Runtime RPC request :rel parent_p4rt_server: Relation to parent container
- relation nokia_srlinux::system::P4rtServer parent_p4rt_server [1]¶
Relation to parent container Peer relation: Top-level container for configuration and state related to unix sockets
other end:
nokia_srlinux::system::P4rtServer.unix_socket [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::p4rt_server::setupUnixSocketYangContainer
constrainttrue
- entity nokia_srlinux::system::packet_link_qualification::Profile¶
Parents:
nokia_srlinux::Base
List of configured Packet Link Qualification profiles Yang definition can be found here: srl_nokia-packet-link-qual.yang:L43
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the Packet Link Qualification profile :rel asic_loopback: ASIC loopback Use the ASIC loopback mode :rel ntp: :rel packet_generator: Packet generator endpoint :rel parent_packet_link_qualification: Relation to parent container :rel pmd_loopback: PMD loopback Use the PMD loopback mode :rel rpc:
- relation nokia_srlinux::system::PacketLinkQualification parent_packet_link_qualification [1]¶
Relation to parent container Peer relation: List of configured Packet Link Qualification profiles
other end:
nokia_srlinux::system::PacketLinkQualification.profile [0:*]
- relation nokia_srlinux::system::packet_link_qualification::profile::AsicLoopback asic_loopback [0:1]¶
Relation to parent container Peer relation: ASIC loopback
Use the ASIC loopback mode
other end:
nokia_srlinux::system::packet_link_qualification::profile::AsicLoopback.parent_profile [1]
- relation nokia_srlinux::system::packet_link_qualification::profile::Ntp ntp [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::packet_link_qualification::profile::Ntp.parent_profile [1]
- relation nokia_srlinux::system::packet_link_qualification::profile::PacketGenerator packet_generator [0:1]¶
Relation to parent container Peer relation: Packet generator endpoint
other end:
nokia_srlinux::system::packet_link_qualification::profile::PacketGenerator.parent_profile [1]
- relation nokia_srlinux::system::packet_link_qualification::profile::PmdLoopback pmd_loopback [0:1]¶
Relation to parent container Peer relation: PMD loopback
Use the PMD loopback mode
other end:
nokia_srlinux::system::packet_link_qualification::profile::PmdLoopback.parent_profile [1]
- relation nokia_srlinux::system::packet_link_qualification::profile::Rpc rpc [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::packet_link_qualification::profile::Rpc.parent_profile [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::packet_link_qualification::profile::AsicLoopback¶
Parents:
nokia_srlinux::Base
ASIC loopback
Use the ASIC loopback mode Yang definition can be found here: srl_nokia-packet-link-qual.yang:L143
- Rel parent_profile:
Relation to parent container
- relation nokia_srlinux::system::packet_link_qualification::Profile parent_profile [1]¶
Relation to parent container Peer relation: ASIC loopback
Use the ASIC loopback mode
other end:
nokia_srlinux::system::packet_link_qualification::Profile.asic_loopback [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::packet_link_qualification::profile::Ntp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-packet-link-qual.yang:L56
- attribute nokia_srlinux::types::srl_nokia_common::date_and_time? end_time=null¶
End time of the test
- attribute nokia_srlinux::types::srl_nokia_common::date_and_time? start_time=null¶
Start time of the test
- attribute nokia_srlinux::types::srl_nokia_common::date_and_time? teardown_time=null¶
Time at which the test should be torn down :rel parent_profile: Relation to parent container
- relation nokia_srlinux::system::packet_link_qualification::Profile parent_profile [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::packet_link_qualification::Profile.ntp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::packet_link_qualification::profile::PacketGenerator¶
Parents:
nokia_srlinux::Base
Packet generator endpoint Yang definition can be found here: srl_nokia-packet-link-qual.yang:L119
- attribute nokia_srlinux::system::packet_link_qualification::profile::packet_generator_packet_rate_t? packet_rate=null¶
Packet rate of the packet generator
- attribute nokia_srlinux::system::packet_link_qualification::profile::packet_generator_packet_size_t? packet_size=null¶
Packet size (in bytes) of the packet generator :rel parent_profile: Relation to parent container
- relation nokia_srlinux::system::packet_link_qualification::Profile parent_profile [1]¶
Relation to parent container Peer relation: Packet generator endpoint
other end:
nokia_srlinux::system::packet_link_qualification::Profile.packet_generator [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::packet_link_qualification::profile::PmdLoopback¶
Parents:
nokia_srlinux::Base
PMD loopback
Use the PMD loopback mode Yang definition can be found here: srl_nokia-packet-link-qual.yang:L152
- Rel parent_profile:
Relation to parent container
- relation nokia_srlinux::system::packet_link_qualification::Profile parent_profile [1]¶
Relation to parent container Peer relation: PMD loopback
Use the PMD loopback mode
other end:
nokia_srlinux::system::packet_link_qualification::Profile.pmd_loopback [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::packet_link_qualification::profile::Rpc¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-packet-link-qual.yang:L77
- attribute yang::types::uint32? duration=null¶
Duration of the test
- attribute yang::types::uint32? post_sync_duration=null¶
Duration of the post-sync phase
- attribute yang::types::uint32? pre_sync_duration=null¶
Duration of the pre-sync phase
- attribute yang::types::uint32? setup_duration=null¶
Duration of the setup phase
- attribute yang::types::uint32? teardown_duration=null¶
Duration of the teardown phase :rel parent_profile: Relation to parent container
- relation nokia_srlinux::system::packet_link_qualification::Profile parent_profile [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::packet_link_qualification::Profile.rpc [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::protocols::Bgp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-bgp.yang:L3558
- attribute nokia_srlinux::system::protocols::bgp_restart_max_wait_t? restart_max_wait=null¶
The maximum amount of time that BGP will wait to receive End of RIB markers from all peers and for all address families that were up prior to restart. After this time elapses BGP declares that convergence has occurred and sends its own EOR markers to its peers. :rel parent_protocols: Relation to parent container
- relation nokia_srlinux::system::Protocols parent_protocols [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::Protocols.bgp [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::protocols::setupBgpYangContainer
constrainttrue
- entity nokia_srlinux::system::sflow::Collector¶
Parents:
nokia_srlinux::Base
List of sFlow collectors to which sFlow sample data is sent Yang definition can be found here: srl_nokia-sflow.yang:L77
- attribute nokia_srlinux::system::sflow::collector_collector_address_t? collector_address=null¶
The IP address for an sFlow collector
- attribute nokia_srlinux::system::sflow::collector_collector_id_t collector_id¶
Specify the collector ID
- attribute string? network_instance=null¶
Reference to a configured network-instance
- attribute yang::types::uint16? port=null¶
Specifies the destination UDP port number to be used in sFlow packets
- attribute nokia_srlinux::system::sflow::collector_source_address_t? source_address=null¶
Specifies the IP address to be used as the source address in sFlow packets :rel parent_sflow: Relation to parent container
- relation nokia_srlinux::system::Sflow parent_sflow [1]¶
Relation to parent container Peer relation: List of sFlow collectors to which sFlow sample data is sent
other end:
nokia_srlinux::system::Sflow.collector [0:8]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sflow::setupCollectorYangContainer
constrainttrue
- entity nokia_srlinux::system::snmp::AccessGroup¶
Parents:
nokia_srlinux::Base
List of configured SNMP access-groups Yang definition can be found here: srl_nokia-snmp.yang:L309
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables the SNMP access-group
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description for this access-group
- attribute nokia_srlinux::types::srl_nokia_common::name_without_space name¶
Name of the SNMP access-group
- attribute nokia_srlinux::types::srl_nokia_snmp::security_level? security_level=null¶
Minimum security level required for this access-group. :rel community_entry: List of configured SNMPv1 and v2 communities :rel parent_snmp: Relation to parent container :rel security_entry: List of configured SNMPv3 users
- relation nokia_srlinux::system::Snmp parent_snmp [1]¶
Relation to parent container Peer relation: List of configured SNMP access-groups
- relation nokia_srlinux::system::snmp::access_group::CommunityEntry community_entry [0:*]¶
Relation to parent container Peer relation: List of configured SNMPv1 and v2 communities
other end:
nokia_srlinux::system::snmp::access_group::CommunityEntry.parent_access_group [1]
- relation nokia_srlinux::system::snmp::access_group::SecurityEntry security_entry [0:*]¶
Relation to parent container Peer relation: List of configured SNMPv3 users
other end:
nokia_srlinux::system::snmp::access_group::SecurityEntry.parent_access_group [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::snmp::setupAccessGroupYangContainer
constrainttrue
- entity nokia_srlinux::system::snmp::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network-instances to run an SNMP server in Yang definition can be found here: srl_nokia-snmp.yang:L367
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables the SNMP server in this network-instance
- attribute nokia_srlinux::types::srl_nokia_snmp::engine_id? engine_id=null¶
The local SNMP engine’s administratively assigned unique identifier. If this leaf is not set, the device automatically calculates an engine ID, as described in RFC 3411.
- attribute string name¶
Reference to a configured network-instance
- attribute nokia_srlinux::system::snmp::network_instance_source_address_t[]? source_address=null¶
List of IP addresses for the SNMP server to listen on within the network-instance :rel parent_snmp: Relation to parent container
- relation nokia_srlinux::system::Snmp parent_snmp [1]¶
Relation to parent container Peer relation: List of network-instances to run an SNMP server in
other end:
nokia_srlinux::system::Snmp.network_instance [0:5]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::snmp::setupNetworkInstanceYangContainer
constrainttrue
- entity nokia_srlinux::system::snmp::access_group::CommunityEntry¶
Parents:
nokia_srlinux::Base
List of configured SNMPv1 and v2 communities Yang definition can be found here: srl_nokia-snmp.yang:L182
- attribute nokia_srlinux::types::srl_nokia_common::name_without_space? community=null¶
SNMPv1 and SNMPv2c community
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description for the SNMP community
- attribute nokia_srlinux::types::srl_nokia_common::name_without_space name¶
Unique name for the SNMP community.
- attribute nokia_srlinux::system::snmp::access_group::community_entry_prefix_list_t[]? prefix_list=null¶
Prefixes where this community can be used, both IPv4 and IPv6 addresses. A /32 or /128 mask can be used to limit it to a single ip-address :rel parent_access_group: Relation to parent container
- relation nokia_srlinux::system::snmp::AccessGroup parent_access_group [1]¶
Relation to parent container Peer relation: List of configured SNMPv1 and v2 communities
other end:
nokia_srlinux::system::snmp::AccessGroup.community_entry [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::snmp::access_group::SecurityEntry¶
Parents:
nokia_srlinux::Base
List of configured SNMPv3 users Yang definition can be found here: srl_nokia-snmp.yang:L273
- attribute nokia_srlinux::types::srl_nokia_common::description? description=null¶
Description for this user
- attribute nokia_srlinux::types::srl_nokia_common::name_without_space name¶
Name of the SNMPv3 user :rel authentication: Authentication parameters for this user. :rel parent_access_group: Relation to parent container :rel privacy: Privacy parameters for this user.
- relation nokia_srlinux::system::snmp::AccessGroup parent_access_group [1]¶
Relation to parent container Peer relation: List of configured SNMPv3 users
other end:
nokia_srlinux::system::snmp::AccessGroup.security_entry [0:*]
- relation nokia_srlinux::system::snmp::access_group::security_entry::Authentication authentication [0:1]¶
Relation to parent container Peer relation: Authentication parameters for this user.
other end:
nokia_srlinux::system::snmp::access_group::security_entry::Authentication.parent_security_entry [1]
- relation nokia_srlinux::system::snmp::access_group::security_entry::Privacy privacy [0:1]¶
Relation to parent container Peer relation: Privacy parameters for this user.
other end:
nokia_srlinux::system::snmp::access_group::security_entry::Privacy.parent_security_entry [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::snmp::access_group::security_entry::Authentication¶
Parents:
nokia_srlinux::Base
Authentication parameters for this user. Yang definition can be found here: srl_nokia-snmp.yang:L212
- attribute nokia_srlinux::system::snmp::access_group::security_entry::authentication_password_t? password=null¶
The user authentication password, supplied either as cleartext or as a hashed value. If provided as cleartext, the system will hash the value on input, storing only the hashed value. If provided as a hashed value, the value should include any ‘$’ characters, for example ‘$ar2$aOvsuj0ALlU=$r750fMa3ZEA/Di8dIfU2fQ==’.
- attribute nokia_srlinux::types::srl_nokia_snmp::auth_protocol? protocol=null¶
Authentication protocol used by this user. :rel parent_security_entry: Relation to parent container
- relation nokia_srlinux::system::snmp::access_group::SecurityEntry parent_security_entry [1]¶
Relation to parent container Peer relation: Authentication parameters for this user.
other end:
nokia_srlinux::system::snmp::access_group::SecurityEntry.authentication [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::snmp::access_group::security_entry::Privacy¶
Parents:
nokia_srlinux::Base
Privacy parameters for this user. Yang definition can be found here: srl_nokia-snmp.yang:L234
- attribute nokia_srlinux::system::snmp::access_group::security_entry::privacy_password_t? password=null¶
The user privacy password, supplied either as cleartext or as a hashed value. If not provided, authentication/password will be used. If provided as cleartext, the system will hash the value on input, storing only the hashed value. If provided as a hashed value, the value should include any ‘$’ characters, for example ‘$ar2$aOvsuj0ALlU=$r750fMa3ZEA/Di8dIfU2fQ==’.
- attribute nokia_srlinux::types::srl_nokia_snmp::priv_protocol? protocol=null¶
Privacy protocol used by this user. :rel parent_security_entry: Relation to parent container
- relation nokia_srlinux::system::snmp::access_group::SecurityEntry parent_security_entry [1]¶
Relation to parent container Peer relation: Privacy parameters for this user.
other end:
nokia_srlinux::system::snmp::access_group::SecurityEntry.privacy [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::ssh_server::HostKey¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-ssh.yang:L128
- attribute string? certificate=null¶
The SSH servers host key certificate The value should be the host key certificate as read from the *-cert.pub file generated by the CA including the certificate type, e.g. ‘ssh-rsa-cert-v01@openssh.com AAAA<…> comment’. This certificate is returned to clients during SSH init for the client to verify the host it is communicating with. This sets the HostCertificate option within each SSH servers configuration file. The certificate should be generated by first extracting the systems current public key and having this signed by a CA.
- attribute bool? preserve=null¶
Indicates whether the SSH server host keys should be preserved on reboots Setting this to true will result in host keys in /etc/sshd not being cleared on a reboot. Alternatively setting this to false will result in host keys being removed and regenerated on each reboot of the system. :rel parent_ssh_server: Relation to parent container
- relation nokia_srlinux::system::SshServer parent_ssh_server [1]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::ssh_server::setupHostKeyYangContainer
constrainttrue
- entity nokia_srlinux::system::ssh_server::NetworkInstance¶
Parents:
nokia_srlinux::Base
List of network-instances to run an SSH server in Yang definition can be found here: srl_nokia-ssh.yang:L106
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enables the SSH server in this network-instance
- attribute string name¶
Reference to a configured network-instance
- attribute yang::types::uint16? rate_limit=null¶
Set a limit on the number of unauthenticated sessions to the SSH server after this number is met, the server will start dropping connection attempts
- attribute nokia_srlinux::system::ssh_server::network_instance_source_address_t[]? source_address=null¶
List of IP addresses for the SSH server to listen on within the network-instance
- attribute yang::types::uint16? timeout=null¶
Set the idle timeout in seconds on SSH connections :rel parent_ssh_server: Relation to parent container
- relation nokia_srlinux::system::SshServer parent_ssh_server [1]¶
Relation to parent container Peer relation: List of network-instances to run an SSH server in
other end:
nokia_srlinux::system::SshServer.network_instance [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::FreqClock¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-sync.yang:L64
- attribute nokia_srlinux::system::sync::freq_clock_network_type_t? network_type=null¶
Configures SyncE for SSM code-type as SONET or SDH mode sdh specifies the values corresponding to ITU-T G.781 Option 1 compliant networks. sonet specifies the values corresponding to ITU-T G.781 Option 2 compliant networks.
- attribute nokia_srlinux::types::srl_nokia_sync_types::settable_ql_values? ql_input_threshold=null¶
This command configures the minimum acceptable QL value Frequency references with lower QL will not be considered for selection by the system timing module. Options: unused, prs, stu, st2, tnc, st3e, st3, prc, ssua, ssub, sec, eec1, eec2
- attribute bool? ql_selection=null¶
Configures if frequency reference selection takes the QL (Quality Level) into account When enabled, the selection of system timing reference and BITS output timing reference takes into account quality level. Quality level is conveyed via the SSM or forced using the ql-override command..
- attribute bool? revert=null¶
This command configures if the frequency clock is in revertive mode In revertive mode, when a failed reference becomes operational, the system will automatically switch to the recovered reference if it is of higher priority and/or QL. When the mode is non-revertive, a failed clock source is not automatically selected.
- attribute nokia_srlinux::system::sync::freq_clock_wait_to_restore_t? wait_to_restore=null¶
This command configures the time for the Wait to Restore timer A previously failed input reference must be valid for the time specified before it is used for the clock input reference. :rel parent_sync: Relation to parent container
- relation nokia_srlinux::system::Sync parent_sync [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::Sync.freq_clock [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::setupFreqClockYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::FreqReferences¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-sync.yang:L61
- Rel instance:
List of line references configured for frequency
- Rel parent_sync:
Relation to parent container
- relation nokia_srlinux::system::Sync parent_sync [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::Sync.freq_references [0:1]
- relation nokia_srlinux::system::sync::freq_references::Instance instance [0:*]¶
Relation to parent container Peer relation: List of line references configured for frequency
other end:
nokia_srlinux::system::sync::freq_references::Instance.parent_freq_references [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::setupFreqReferencesYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::Gnss¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-sync.yang:L70
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configure the administrative state of the GNSS port :rel constellation: Selects which constellations to be used for GNSS :rel gnss_a: Specific configuration and states of a specific receiver This may be the sole GNSS receiver or GNSS-A receiver in routers with redundant CPMs :rel gnss_b: Specific configuration and states of GNSS-B receiver in routers with redundant CPMs :rel parent_sync: Relation to parent container
- relation nokia_srlinux::system::Sync parent_sync [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::Sync.gnss [0:1]
- relation nokia_srlinux::system::sync::gnss::Constellation constellation [0:1]¶
Relation to parent container Peer relation: Selects which constellations to be used for GNSS
other end:
nokia_srlinux::system::sync::gnss::Constellation.parent_gnss [1]
- relation nokia_srlinux::system::sync::gnss::GnssA gnss_a [0:1]¶
Relation to parent container Peer relation: Specific configuration and states of a specific receiver
This may be the sole GNSS receiver or GNSS-A receiver in routers with redundant CPMs
other end:
nokia_srlinux::system::sync::gnss::GnssA.parent_gnss [1]
- relation nokia_srlinux::system::sync::gnss::GnssB gnss_b [0:1]¶
Relation to parent container Peer relation: Specific configuration and states of GNSS-B receiver in routers with redundant CPMs
other end:
nokia_srlinux::system::sync::gnss::GnssB.parent_gnss [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::setupGnssYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::OnePps¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-sync.yang:L74
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configure the administrative state of the 1PPS (50 ohm) output port When enabled, output is enabled. Otherwise, the output is disabled. :rel parent_sync: Relation to parent container
- relation nokia_srlinux::system::Sync parent_sync [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::Sync.one_pps [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::setupOnePpsYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::Ptp¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-sync.yang:L67
- attribute nokia_srlinux::system::sync::ptp_ptp_profile_t? ptp_profile=null¶
Specifies the PTP profile mode for the PTP clock :rel instance: List of one or more PTP instances in the product (PTP Node) Each PTP instance represents a distinct instance of PTP implementation (i.e. distinct Ordinary Clock, Boundary Clock, or Transparent Clock), maintaining a distinct time. :rel parent_sync: Relation to parent container
- relation nokia_srlinux::system::Sync parent_sync [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::Sync.ptp [0:1]
- relation nokia_srlinux::system::sync::ptp::Instance instance [0:*]¶
Relation to parent container Peer relation: List of one or more PTP instances in the product (PTP Node)
Each PTP instance represents a distinct instance of PTP implementation (i.e. distinct Ordinary Clock, Boundary Clock, or Transparent Clock), maintaining a distinct time.
other end:
nokia_srlinux::system::sync::ptp::Instance.parent_ptp [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::setupPtpYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::freq_references::Instance¶
Parents:
nokia_srlinux::Base
List of line references configured for frequency Yang definition can be found here: srl_nokia-sync-freq.yang:L50
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Configure the administrative state of this frequency reference instance
- attribute nokia_srlinux::system::sync::freq_references::instance_instance_number_t instance_number¶
The instance number of the each line reference
- attribute nokia_srlinux::system::sync::freq_references::instance_priority_t? priority=null¶
Sets the priority of this line timing reference for the system timing selection process 1 = highest priority 5 = lowest priority Duplicate numbers are not allowed
- attribute nokia_srlinux::types::srl_nokia_sync_types::settable_ql_values? ql_override=null¶
Override the incoming QL/SSM value for this line reference Quality level override of a timing reference Options are unused, prs, stu, st2, tnc, st3e, st3, prc, ssua, ssub, sec, eec1, eec2 :rel parent_freq_references: Relation to parent container :rel source: Source for this input frequency reference This shall be either a leafref to an interface or an application. The leafref must point to an existing physical ethernet interface.
- relation nokia_srlinux::system::sync::FreqReferences parent_freq_references [1]¶
Relation to parent container Peer relation: List of line references configured for frequency
other end:
nokia_srlinux::system::sync::FreqReferences.instance [0:*]
- relation nokia_srlinux::system::sync::freq_references::instance::Source source [0:1]¶
Relation to parent container Peer relation: Source for this input frequency reference
This shall be either a leafref to an interface or an application. The leafref must point to an existing physical ethernet interface.
other end:
nokia_srlinux::system::sync::freq_references::instance::Source.parent_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::freq_references::instance::Source¶
Parents:
nokia_srlinux::Base
Source for this input frequency reference
This shall be either a leafref to an interface or an application. The leafref must point to an existing physical ethernet interface. Yang definition can be found here: srl_nokia-sync-freq.yang:L76
- attribute string? interface=null¶
- Rel parent_instance:
Relation to parent container
- relation nokia_srlinux::system::sync::freq_references::Instance parent_instance [1]¶
Relation to parent container Peer relation: Source for this input frequency reference
This shall be either a leafref to an interface or an application. The leafref must point to an existing physical ethernet interface.
other end:
nokia_srlinux::system::sync::freq_references::Instance.source [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::gnss::Constellation¶
Parents:
nokia_srlinux::Base
Selects which constellations to be used for GNSS Yang definition can be found here: srl_nokia-sync-interfaces.yang:L238
- attribute bool? galileo=null¶
- Rel parent_gnss:
Relation to parent container
- relation nokia_srlinux::system::sync::Gnss parent_gnss [1]¶
Relation to parent container Peer relation: Selects which constellations to be used for GNSS
other end:
nokia_srlinux::system::sync::Gnss.constellation [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::gnss::GnssA¶
Parents:
nokia_srlinux::Base
Specific configuration and states of a specific receiver
This may be the sole GNSS receiver or GNSS-A receiver in routers with redundant CPMs Yang definition can be found here: srl_nokia-sync-interfaces.yang:L251
- attribute nokia_srlinux::system::sync::gnss::gnss_a_antenna_cable_delay_t? antenna_cable_delay=null¶
Sets the cable delay value (integer) in ns to the GNSS antenna
- attribute nokia_srlinux::system::sync::gnss::gnss_a_elevation_mask_angle_t? elevation_mask_angle=null¶
Sets the elevation mask angle This provides a method of filtering satellites low on the horizon to be used by the system. :rel parent_gnss: Relation to parent container :rel sats_in_use: The list of satelites currenlty in use
- relation nokia_srlinux::system::sync::Gnss parent_gnss [1]¶
Relation to parent container Peer relation: Specific configuration and states of a specific receiver
This may be the sole GNSS receiver or GNSS-A receiver in routers with redundant CPMs
- relation nokia_srlinux::system::sync::gnss::gnss_a::SatsInUse sats_in_use [0:1]¶
Relation to parent container Peer relation: The list of satelites currenlty in use
other end:
nokia_srlinux::system::sync::gnss::gnss_a::SatsInUse.parent_gnss_a [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::gnss::setupGnssAYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::gnss::GnssB¶
Parents:
nokia_srlinux::Base
Specific configuration and states of GNSS-B receiver in routers with redundant CPMs Yang definition can be found here: srl_nokia-sync-interfaces.yang:L258
- attribute nokia_srlinux::system::sync::gnss::gnss_b_antenna_cable_delay_t? antenna_cable_delay=null¶
Sets the cable delay value (integer) in ns to the GNSS antenna
- attribute nokia_srlinux::system::sync::gnss::gnss_b_elevation_mask_angle_t? elevation_mask_angle=null¶
Sets the elevation mask angle This provides a method of filtering satellites low on the horizon to be used by the system. :rel parent_gnss: Relation to parent container :rel sats_in_use: The list of satelites currenlty in use
- relation nokia_srlinux::system::sync::Gnss parent_gnss [1]¶
Relation to parent container Peer relation: Specific configuration and states of GNSS-B receiver in routers with redundant CPMs
- relation nokia_srlinux::system::sync::gnss::gnss_b::SatsInUse sats_in_use [0:1]¶
Relation to parent container Peer relation: The list of satelites currenlty in use
other end:
nokia_srlinux::system::sync::gnss::gnss_b::SatsInUse.parent_gnss_b [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::gnss::setupGnssBYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::gnss::gnss_a::SatsInUse¶
Parents:
nokia_srlinux::Base
The list of satelites currenlty in use Yang definition can be found here: srl_nokia-sync-interfaces.yang:L187
- Rel parent_gnss_a:
Relation to parent container
- relation nokia_srlinux::system::sync::gnss::GnssA parent_gnss_a [1]¶
Relation to parent container Peer relation: The list of satelites currenlty in use
other end:
nokia_srlinux::system::sync::gnss::GnssA.sats_in_use [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::gnss::gnss_b::SatsInUse¶
Parents:
nokia_srlinux::Base
The list of satelites currenlty in use Yang definition can be found here: srl_nokia-sync-interfaces.yang:L187
- Rel parent_gnss_b:
Relation to parent container
- relation nokia_srlinux::system::sync::gnss::GnssB parent_gnss_b [1]¶
Relation to parent container Peer relation: The list of satelites currenlty in use
other end:
nokia_srlinux::system::sync::gnss::GnssB.sats_in_use [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::ptp::Instance¶
Parents:
nokia_srlinux::Base
List of one or more PTP instances in the product (PTP Node)
Each PTP instance represents a distinct instance of PTP implementation (i.e. distinct Ordinary Clock, Boundary Clock, or Transparent Clock), maintaining a distinct time. Yang definition can be found here: srl_nokia-sync-ptp.yang:L1636
- attribute nokia_srlinux::system::sync::ptp::instance_instance_index_t instance_index¶
The instance index of the current PTP instance This instance index is used for management purposes only. This instance index does not represent the PTP domain number and is not used in PTP messages. :rel default_ds: The default data set of the PTP instance In the context of the protocol, this data set is required for an Ordinary Clock or Boundary Clock :rel network_instances: Per network instance PTP configuration and state :rel parent_ptp: Relation to parent container :rel port_ds_list: List of port data sets of the clock
- relation nokia_srlinux::system::sync::Ptp parent_ptp [1]¶
Relation to parent container Peer relation: List of one or more PTP instances in the product (PTP Node)
Each PTP instance represents a distinct instance of PTP implementation (i.e. distinct Ordinary Clock, Boundary Clock, or Transparent Clock), maintaining a distinct time.
- relation nokia_srlinux::system::sync::ptp::instance::DefaultDs default_ds [0:1]¶
Relation to parent container Peer relation: The default data set of the PTP instance
In the context of the protocol, this data set is required for an Ordinary Clock or Boundary Clock
other end:
nokia_srlinux::system::sync::ptp::instance::DefaultDs.parent_instance [1]
- relation nokia_srlinux::system::sync::ptp::instance::NetworkInstances network_instances [0:*]¶
Relation to parent container Peer relation: Per network instance PTP configuration and state
other end:
nokia_srlinux::system::sync::ptp::instance::NetworkInstances.parent_instance [1]
- relation nokia_srlinux::system::sync::ptp::instance::PortDsList port_ds_list [0:*]¶
Relation to parent container Peer relation: List of port data sets of the clock
other end:
nokia_srlinux::system::sync::ptp::instance::PortDsList.parent_instance [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::sync::ptp::setupInstanceYangContainer
constrainttrue
- entity nokia_srlinux::system::sync::ptp::instance::DefaultDs¶
Parents:
nokia_srlinux::Base
The default data set of the PTP instance
In the context of the protocol, this data set is required for an Ordinary Clock or Boundary Clock Yang definition can be found here: srl_nokia-sync-ptp.yang:L574
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_announce_receipt_timeout_t? announce_receipt_timeout=null¶
Sets the time limit for missed Announce packets before the master clock is deemed down This command configures the announceReceiptTimeout value for all peer associations. This defines the number of Announce message intervals that must expire with no received Announce messages before declaring an ANNOUNCE_RECEIPT_TIMEOUT event.
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_domain_number_t? domain_number=null¶
The IEEE Std 1588 domainNumber of the PTP instance A domain consists of one or more PTP instances communicating with each other as defined by the protocol. A domain shall define the scope of PTP message communication, state, operations, data sets, and timescale. Therefore, each domain represents a distinct time. The default domain number is defined by the profile. itug8275dot1: 24 itug8275dot2: 44
- attribute bool? instance_enable=null¶
Enable PTP clock
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_instance_type_t? instance_type=null¶
The type of PTP instance as per IEEE1588 standard For G.8275.1: oc is for T-GM, bc is for T-BC; T-TSC not supported since T-BC can be used for this role For G.8275.2: oc is for T-GM, bc is for T-BC-A and T-BC-P; T-TSC-A and T-TSC-P are not supported since T-BC-A or T-BC-P can be used for this role
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_local_priority_t? local_priority=null¶
The IEEE Std 1588 priority2 of the PTP instance The priority2 member is compared by the Best Master Clock Algorithm (BMCA) after priority1 and clockQuality. Lower values take precedence.
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_log_announce_interval_t? log_announce_interval=null¶
The base-2 logarithm of the mean announceInterval This is the mean time interval between successive Announce messages. The default log announce interval is defined by the profile. itug8275dot1: -3 (8 messages per second) itug8275dot2: 1 (1 message every two seconds)
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_priority1_t? priority1=null¶
The IEEE Std 1588 priority1 of the PTP instance Since priority1 is one of the first comparisons performed by the Best Master Clock Algorithm (BMCA). Range is 0-255.
- attribute nokia_srlinux::system::sync::ptp::instance::default_ds_priority2_t? priority2=null¶
The IEEE Std 1588 priority2 of the PTP instance The priority2 member is compared by the Best Master Clock Algorithm (BMCA) after priority1 and clockQuality. Lower values take precedence. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::system::sync::ptp::Instance parent_instance [1]¶
Relation to parent container Peer relation: The default data set of the PTP instance
In the context of the protocol, this data set is required for an Ordinary Clock or Boundary Clock
other end:
nokia_srlinux::system::sync::ptp::Instance.default_ds [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::ptp::instance::NetworkInstances¶
Parents:
nokia_srlinux::Base
Per network instance PTP configuration and state Yang definition can be found here: srl_nokia-sync-ptp.yang:L1463
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Administrative state of PTP on the network-instance
- attribute string network_instance¶
Network instance that owns the PTP peer
- attribute nokia_srlinux::system::sync::ptp::instance::network_instances_peer_limit_t? peer_limit=null¶
Number of discovered peers allowed for network-instance If not defined then the number is not restricted within this network-instance.
- attribute nokia_srlinux::system::sync::ptp::instance::network_instances_source_address_t? source_address=null¶
Source address to be used for PTP messages sent in this network-instance Only unicast IP supported. :rel parent_instance: Relation to parent container
- relation nokia_srlinux::system::sync::ptp::Instance parent_instance [1]¶
Relation to parent container Peer relation: Per network instance PTP configuration and state
other end:
nokia_srlinux::system::sync::ptp::Instance.network_instances [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::ptp::instance::PortDsList¶
Parents:
nokia_srlinux::Base
List of port data sets of the clock Yang definition can be found here: srl_nokia-sync-ptp.yang:L1149
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The administrative state of the ptp port
- attribute nokia_srlinux::system::sync::ptp::instance::port_ds_list_dest_mac_t? dest_mac=null¶
Configure the MAC address associated with forwardable or non-forwardable This leaf is not used with PTP special ports (gnss).
- attribute nokia_srlinux::system::sync::ptp::instance::port_ds_list_local_priority_t? local_priority=null¶
Specifies the local priority of the ptp port
- attribute nokia_srlinux::system::sync::ptp::instance::port_ds_list_log_min_delay_req_interval_t? log_min_delay_req_interval=null¶
The base-2 logarithm of the minDelayReqInterval The minimum permitted mean time interval between successive Delay_Req messages. The default log-min-delay-req-interval is defined by the profile. itug8275dot1: -4 (16 messages per second) itug8275dot2: -6 (64 messages per second) This leaf is not used with PTP special ports (gnss).
- attribute nokia_srlinux::system::sync::ptp::instance::port_ds_list_log_sync_interval_t? log_sync_interval=null¶
The base-2 logarithm of the mean SyncInterval for multicast messages The default log sync interval is defined by the profile. itug8275dot1: -4 (16 messages per second) itug8275dot2: -6 (64 messages per second) The rates for unicast transmissions are negotiated separately on a per-port basis and are not constrained by this attribute. This leaf is not used with PTP special ports (gnss).
- attribute bool? master_only=null¶
Specifies the masterOnly attribute of the ptp port
- attribute nokia_srlinux::system::sync::ptp::instance::port_ds_list_port_index_t port_index¶
Index into the port-ds list This is not the PTP port number. Configurable ports use port indices 1 through 999 but there is a limit on the overall number of these configured ports based on the platform and software release. Non-configurable ports are created based on Unicast negotiation. These use port numbers starting from 1001. One PTP port is defined for the embedded gnss module(s). This port uses port index of 1000. The one ptp port represents gnss-a and gnss-b (where applicable). This is a Special Port as defined in the PTP standard and as such there are leaves if this port-ds that are not relevant for this port. One PTP port is defined for each sync0 interface. The data sets (i.e., information model) of IEEE Std 1588-2008 specify a member portDS.portIdentity, which uses a typed struct with members clockIdentity and portNumber. In this YANG data model, portIdentity is not modeled in the port-ds. However, its members are provided as follows: portIdentity.portNumber is provided as this ptp-port-number leaf in port-ds, and portIdentity.clockIdentity is provided as the clock-identity leaf in default-ds of the instance (i.e., ../../default-ds/clock-identity). :rel parent_instance: Relation to parent container :rel source: Source for the PTP session for this PTP port This shall be either a leafref to an interface, gnss module, dedicated sync port, or an external IP peer.
- relation nokia_srlinux::system::sync::ptp::Instance parent_instance [1]¶
Relation to parent container Peer relation: List of port data sets of the clock
other end:
nokia_srlinux::system::sync::ptp::Instance.port_ds_list [0:*]
- relation nokia_srlinux::system::sync::ptp::instance::port_ds_list::Source source [0:1]¶
Relation to parent container Peer relation: Source for the PTP session for this PTP port
This shall be either a leafref to an interface, gnss module, dedicated sync port, or an external IP peer.
other end:
nokia_srlinux::system::sync::ptp::instance::port_ds_list::Source.parent_port_ds_list [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::ptp::instance::port_ds_list::Source¶
Parents:
nokia_srlinux::Base
Source for the PTP session for this PTP port
This shall be either a leafref to an interface, gnss module, dedicated sync port, or an external IP peer. Yang definition can be found here: srl_nokia-sync-ptp.yang:L1216
- attribute string? interface=null¶
- Rel parent_port_ds_list:
Relation to parent container :rel peer:
- relation nokia_srlinux::system::sync::ptp::instance::PortDsList parent_port_ds_list [1]¶
Relation to parent container Peer relation: Source for the PTP session for this PTP port
This shall be either a leafref to an interface, gnss module, dedicated sync port, or an external IP peer.
other end:
nokia_srlinux::system::sync::ptp::instance::PortDsList.source [0:1]
- relation nokia_srlinux::system::sync::ptp::instance::port_ds_list::source::Peer peer [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::sync::ptp::instance::port_ds_list::source::Peer.parent_source [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::sync::ptp::instance::port_ds_list::source::Peer¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-sync-ptp.yang:L1246
- attribute nokia_srlinux::system::sync::ptp::instance::port_ds_list::source::peer_ip_address_t? ip_address=null¶
IP address for the PTP peer Only Unicast addresses are supported
- attribute string? network_instance=null¶
Network instance that owns the PTP peer :rel parent_source: Relation to parent container
- relation nokia_srlinux::system::sync::ptp::instance::port_ds_list::Source parent_source [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::system::sync::ptp::instance::port_ds_list::Source.peer [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::system::tls::ServerProfile¶
Parents:
nokia_srlinux::Base
List of configured TLS server profiles Yang definition can be found here: srl_nokia-tls.yang:L251
- attribute bool? authenticate_client=null¶
Defines if the server should authenticate the identity of connecting clients using the trust anchor
- attribute string? certificate=null¶
Base64 encoded certificate to use with the private key This includes the ‘—–BEGIN CERTIFICATE—–’ and ‘—–END CERTIFICATE—–’ header and footer
- attribute string? certificate_revocation_list=null¶
Base64 encoded certificate revocation list This includes the ‘—–BEGIN X509 CRL’ and ‘—–END X509 CRL’ header and footer
- attribute string[]? cipher_list=null¶
List of ciphers to use when negotiating TLS 1.2 with clients TLS 1.3 cipher suites are always enabled: tls_aes_256_gcm_sha384, tls_aes_128_gcm_sha256, tls_chacha20_poly1305_sha256
- attribute string? key=null¶
Base64 encoded key to use with the server certificate This includes the ‘—–BEGIN PRIVATE KEY—–’, and ‘—–END PRIVATE KEY—–’ header and footer The value is hashed, and only the hashed value is kept
- attribute nokia_srlinux::system::tls::server_profile_name_t name¶
Name of the TLS server-profile
- attribute string? trust_anchor=null¶
Base64 encoded certificate to use as a trust anchor This includes the ‘—–BEGIN CERTIFICATE—–’ and ‘—–END CERTIFICATE—–’ header and footer :rel parent_tls: Relation to parent container
- relation nokia_srlinux::system::Tls parent_tls [1]¶
Relation to parent container Peer relation: List of configured TLS server profiles
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::system::tls::setupServerProfileYangContainer
constrainttrue
- entity nokia_srlinux::transport_security::Macsec¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-macsec.yang:L1061
- Rel interface:
List of interfaces on which MACsec is enabled / available
Either an interface or its subinterface can be programmed under macsec. When interface is configured the entire enterface is protected via macsec. When a subinterface is programmed only that subinterface is encrypted. :rel mka: The MKA :rel parent_transport_security: Relation to parent container
- relation nokia_srlinux::TransportSecurity parent_transport_security [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::transport_security::macsec::Interface interface [0:*]¶
Relation to parent container Peer relation: List of interfaces on which MACsec is enabled / available
Either an interface or its subinterface can be programmed under macsec. When interface is configured the entire enterface is protected via macsec. When a subinterface is programmed only that subinterface is encrypted.
other end:
nokia_srlinux::transport_security::macsec::Interface.parent_macsec [1]
- relation nokia_srlinux::transport_security::macsec::Mka mka [0:1]¶
Relation to parent container Peer relation: The MKA
other end:
nokia_srlinux::transport_security::macsec::Mka.parent_macsec [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::transport_security::setupMacsecYangContainer
constrainttrue
- entity nokia_srlinux::transport_security::macsec::Interface¶
Parents:
nokia_srlinux::Base
List of interfaces on which MACsec is enabled / available
Either an interface or its subinterface can be programmed under macsec. When interface is configured the entire enterface is protected via macsec. When a subinterface is programmed only that subinterface is encrypted. Yang definition can be found here: srl_nokia-macsec.yang:L1007
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Enable MACsec on an interface
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the interface being created for the MACSec
- attribute yang::types::uint16? replay_protection=null¶
MACsec window size, as defined by the number of out-of-order frames that are accepted. A value of 0 means that frames are accepted only in the correct order.
- attribute bool? rx_must_be_encrypted=null¶
when true; only accept encrypted packets, If false accept a mix of encrypted and clear text packets :rel exclude_mac: list of destination macs to be excluded from the macsec encryption :rel exclude_protocols: protocols to be excluded from macsec :rel interface_ref: :rel mka: Enclosing container for the MKA interface :rel parent_macsec: Relation to parent container
- relation nokia_srlinux::transport_security::Macsec parent_macsec [1]¶
Relation to parent container Peer relation: List of interfaces on which MACsec is enabled / available
Either an interface or its subinterface can be programmed under macsec. When interface is configured the entire enterface is protected via macsec. When a subinterface is programmed only that subinterface is encrypted.
other end:
nokia_srlinux::transport_security::Macsec.interface [0:*]
- relation nokia_srlinux::transport_security::macsec::interface::ExcludeMac exclude_mac [0:*]¶
Relation to parent container Peer relation: list of destination macs to be excluded from the macsec encryption
other end:
nokia_srlinux::transport_security::macsec::interface::ExcludeMac.parent_interface [1]
- relation nokia_srlinux::transport_security::macsec::interface::ExcludeProtocols exclude_protocols [0:*]¶
Relation to parent container Peer relation: protocols to be excluded from macsec
other end:
nokia_srlinux::transport_security::macsec::interface::ExcludeProtocols.parent_interface [1]
- relation nokia_srlinux::transport_security::macsec::interface::InterfaceRef interface_ref [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::transport_security::macsec::interface::InterfaceRef.parent_interface [1]
- relation nokia_srlinux::transport_security::macsec::interface::Mka mka [0:1]¶
Relation to parent container Peer relation: Enclosing container for the MKA interface
other end:
nokia_srlinux::transport_security::macsec::interface::Mka.parent_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::transport_security::macsec::Mka¶
Parents:
nokia_srlinux::Base
The MKA Yang definition can be found here: srl_nokia-macsec.yang:L1052
- Rel parent_macsec:
Relation to parent container
- Rel policy:
List of MKA policies
- relation nokia_srlinux::transport_security::Macsec parent_macsec [1]¶
Relation to parent container Peer relation: The MKA
other end:
nokia_srlinux::transport_security::Macsec.mka [0:1]
- relation nokia_srlinux::transport_security::macsec::mka::Policy policy [0:*]¶
Relation to parent container Peer relation: List of MKA policies
other end:
nokia_srlinux::transport_security::macsec::mka::Policy.parent_mka [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::transport_security::macsec::setupMkaYangContainer
constrainttrue
- entity nokia_srlinux::transport_security::macsec::interface::ExcludeMac¶
Parents:
nokia_srlinux::Base
list of destination macs to be excluded from the macsec encryption Yang definition can be found here: srl_nokia-macsec.yang:L631
- attribute nokia_srlinux::types::srl_nokia_common::mac_address destination_mac¶
exclude this destination mac from encryptino :rel parent_interface: Relation to parent container
- relation nokia_srlinux::transport_security::macsec::Interface parent_interface [1]¶
Relation to parent container Peer relation: list of destination macs to be excluded from the macsec encryption
other end:
nokia_srlinux::transport_security::macsec::Interface.exclude_mac [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::transport_security::macsec::interface::ExcludeProtocols¶
Parents:
nokia_srlinux::Base
protocols to be excluded from macsec Yang definition can be found here: srl_nokia-macsec.yang:L621
- attribute nokia_srlinux::types::srl_nokia_macsec::protocols protocol¶
exclude this protocol :rel parent_interface: Relation to parent container
- relation nokia_srlinux::transport_security::macsec::Interface parent_interface [1]¶
Relation to parent container Peer relation: protocols to be excluded from macsec
other end:
nokia_srlinux::transport_security::macsec::Interface.exclude_protocols [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::transport_security::macsec::interface::InterfaceRef¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-macsec.yang:L1018
- attribute string? interface=null¶
Reference to a base interface, for example a port or LAG
- attribute nokia_srlinux::transport_security::macsec::interface::interface_ref_subinterface_t? subinterface=null¶
Reference to a subinterface This requires the base interface to be specified using the interface leaf in this container. :rel parent_interface: Relation to parent container
- relation nokia_srlinux::transport_security::macsec::Interface parent_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::transport_security::macsec::Interface.interface_ref [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::transport_security::macsec::interface::Mka¶
Parents:
nokia_srlinux::Base
Enclosing container for the MKA interface Yang definition can be found here: srl_nokia-macsec.yang:L998
- attribute string? key_chain=null¶
- attribute string? mka_policy=null¶
Apply MKA policy on the interface :rel parent_interface: Relation to parent container
- relation nokia_srlinux::transport_security::macsec::Interface parent_interface [1]¶
Relation to parent container Peer relation: Enclosing container for the MKA interface
other end:
nokia_srlinux::transport_security::macsec::Interface.mka [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::transport_security::macsec::mka::Policy¶
Parents:
nokia_srlinux::Base
List of MKA policies Yang definition can be found here: srl_nokia-macsec.yang:L652
- attribute nokia_srlinux::types::srl_nokia_macsec::tag_mode? clear_tag_mode=null¶
Specifies the number of tags that will be in clear infront of the sectag
- attribute nokia_srlinux::types::srl_nokia_macsec::confidentiality_offset? confidentiality_offset=null¶
The confidentiality offset specifies a number of octets in an Ethernet frame that are sent in unencrypted and in plain-text
- attribute bool? delay_protection=null¶
Traffic delayed longer than 2 seconds is rejected by the interfaces enabled with delay protection
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? eapol_destination_address=null¶
This command can be used to set eap over lan destination mac to a unicast mac for L2 multiple hop networks
- attribute bool? encrypt=null¶
Enable or disable PDU encryption, if enabled the PDUs are encrypted and authenticated if disabled the PDU is only authenticated and not encrypted
- attribute nokia_srlinux::transport_security::macsec::mka::policy_hello_interval_t? hello_interval=null¶
MKA hello interval, the intervals are 500 ms and 1 to 6 seconds, configuration of 0 is for 500ms
- attribute yang::types::uint8? key_server_priority=null¶
Specifies the key server priority used by the macsec Macsec Key Agreement (MKA) advertises and selects a key server. The node with the lower priority-number is selected as the key server. If the priority-number is identical on both sides of a point-to-point link, the MKA protocol selects the device with the lower MAC address as the key server
- attribute nokia_srlinux::types::srl_nokia_macsec::macsec_cipher_suite[]? macsec_cipher_suite=null¶
Set cipher suite(s) for security association key (SAK) derivation
- attribute nokia_srlinux::transport_security::macsec::mka::policy_maximum_number_of_peers_t? maximum_number_of_peers=null¶
Max mka peers allowed
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Name of the MKA policy
- attribute bool? sak_rekey_on_live_peer_loss=null¶
Security association key, re-key on peer loss :rel parent_mka: Relation to parent container
- relation nokia_srlinux::transport_security::macsec::Mka parent_mka [1]¶
Relation to parent container Peer relation: List of MKA policies
other end:
nokia_srlinux::transport_security::macsec::Mka.policy [0:*]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel::VxlanTunnel¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-vxlan-tunnel-vtep.yang:L167
- Rel parent_tunnel:
Relation to parent container
- Rel statistics:
Container for vxlan-tunnel global statistics.
- relation nokia_srlinux::Tunnel parent_tunnel [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::Tunnel.vxlan_tunnel [0:1]
- relation nokia_srlinux::tunnel::vxlan_tunnel::Statistics statistics [0:1]¶
Relation to parent container Peer relation: Container for vxlan-tunnel global statistics.
other end:
nokia_srlinux::tunnel::vxlan_tunnel::Statistics.parent_vxlan_tunnel [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
nokia_srlinux::tunnel::setupVxlanTunnelYangContainer
constrainttrue
- entity nokia_srlinux::tunnel::vxlan_tunnel::Statistics¶
Parents:
nokia_srlinux::Base
Container for vxlan-tunnel global statistics. Yang definition can be found here: srl_nokia-vxlan-tunnel-vtep.yang:L41
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
The configured state of the VXLAN statistics on the router The default value is disable. No statistics are collected on VXLAN when the admin-state is disable. When enabled, the router starts collecting VXLAN statistics at both, global and VTEP level, however, the total number of layer-2 subinterfaces is decreased. A change in the configuration of this command also resets the statistic counters on layer-2 subinterfaces as a side effect, before resuming the collection of statistics (on these layer-2 subinterfaces). :rel parent_vxlan_tunnel: Relation to parent container
- relation nokia_srlinux::tunnel::VxlanTunnel parent_vxlan_tunnel [1]¶
Relation to parent container Peer relation: Container for vxlan-tunnel global statistics.
other end:
nokia_srlinux::tunnel::VxlanTunnel.statistics [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::VxlanInterface¶
Parents:
nokia_srlinux::Base
The list of vxlan-interfaces. Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L95
- attribute string? type=null¶
The value of this leaf indicates the context in which the vxlan-interface will be used in.
- attribute nokia_srlinux::tunnel_interface::vxlan_interface_index_t x_index¶
The index of the vxlan-tunnel. :rel bridge_table: :rel egress: :rel ingress: :rel parent_tunnel_interface: Relation to parent container
- relation nokia_srlinux::TunnelInterface parent_tunnel_interface [1]¶
Relation to parent container Peer relation: The list of vxlan-interfaces.
other end:
nokia_srlinux::TunnelInterface.vxlan_interface [0:16384]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::BridgeTable bridge_table [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::BridgeTable.parent_vxlan_interface [1]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::Egress egress [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::Egress.parent_vxlan_interface [1]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::Ingress ingress [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::Ingress.parent_vxlan_interface [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::BridgeTable¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L275
- Rel parent_vxlan_interface:
Relation to parent container
- relation nokia_srlinux::tunnel_interface::VxlanInterface parent_vxlan_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::VxlanInterface.bridge_table [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::Egress¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L155
- attribute nokia_srlinux::tunnel_interface::vxlan_interface::egress_source_ip_t? source_ip=null¶
The ip-address that will be used as the source-ip for all vxlan traffic egressing this vxlan-interface. :rel destination_groups: :rel inner_ethernet_header: Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf. :rel parent_vxlan_interface: Relation to parent container
- relation nokia_srlinux::tunnel_interface::VxlanInterface parent_vxlan_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::VxlanInterface.egress [0:1]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::DestinationGroups destination_groups [0:1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::egress::DestinationGroups.parent_egress [1]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::InnerEthernetHeader inner_ethernet_header [0:1]¶
Relation to parent container Peer relation: Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf.
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::egress::InnerEthernetHeader.parent_egress [1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::Ingress¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L142
- attribute nokia_srlinux::tunnel_interface::vxlan_interface::ingress_vni_t? vni=null¶
Ingress VXLAN Network Identifier of the VXLAN subinterface. The egress VNI is determined by the static egress-vni configured in the associated destination or by the dynamic egress-vni learned from the control plane. :rel parent_vxlan_interface: Relation to parent container
- relation nokia_srlinux::tunnel_interface::VxlanInterface parent_vxlan_interface [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::VxlanInterface.ingress [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::egress::DestinationGroups¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L203
- Rel group:
Specifies the destination group.
- Rel parent_egress:
Relation to parent container
- relation nokia_srlinux::tunnel_interface::vxlan_interface::Egress parent_egress [1]¶
Relation to parent container Peer relation:
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::Egress.destination_groups [0:1]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::Group group [0:*]¶
Relation to parent container Peer relation: Specifies the destination group.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::egress::InnerEthernetHeader¶
Parents:
nokia_srlinux::Base
Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf. Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L168
- attribute nokia_srlinux::tunnel_interface::vxlan_interface::egress::inner_ethernet_header_source_mac_t? source_mac=null¶
VXLAN inner ethernet source mac-address. Present when the VXLAN tunnel is associated with a ip-vrf network-instance. :rel parent_egress: Relation to parent container
- relation nokia_srlinux::tunnel_interface::vxlan_interface::Egress parent_egress [1]¶
Relation to parent container Peer relation: Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf.
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::Egress.inner_ethernet_header [0:1]
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::Group¶
Parents:
nokia_srlinux::Base
Specifies the destination group. Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L205
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to enable or disable a destination group
- attribute nokia_srlinux::types::srl_nokia_common::esi? esi=null¶
The 10-byte Ethernet Segment Identifier of the ethernet segment. ESI-0 or MAX-ESI values are not allowed.
- attribute nokia_srlinux::types::srl_nokia_common::name name¶
Specifies the destination group name :rel destination: :rel parent_destination_groups: Relation to parent container
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::DestinationGroups parent_destination_groups [1]¶
Relation to parent container Peer relation: Specifies the destination group.
other end:
nokia_srlinux::tunnel_interface::vxlan_interface::egress::DestinationGroups.group [0:*]
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::Destination destination [0:128]¶
Relation to parent container Peer relation:
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::Destination¶
Parents:
nokia_srlinux::Base
Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L230
- attribute nokia_srlinux::types::srl_nokia_common::admin_state? admin_state=null¶
Used to enable or disable a particular destination.
- attribute nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::destination_vni_t? vni=null¶
Egress VXLAN Network Identifier of the vxlan-interface. The egress VNI is statically configured or dynamically learned from the control plane.
- attribute yang::types::uint16 x_index¶
Numerical index of the destination member :rel inner_ethernet_header: Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf. :rel parent_group: Relation to parent container
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::Group parent_group [1]¶
Relation to parent container Peer relation:
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::destination::InnerEthernetHeader inner_ethernet_header [0:1]¶
Relation to parent container Peer relation: Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
- entity nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::destination::InnerEthernetHeader¶
Parents:
nokia_srlinux::Base
Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf. Yang definition can be found here: srl_nokia-tunnel-interfaces.yang:L253
- attribute nokia_srlinux::types::srl_nokia_common::mac_address? destination_mac=null¶
VXLAN inner ethernet destination mac-address. Configured when the VXLAN tunnel is associated with a ip-vrf network-instance and the egress-vtep and egress-vni are statically configured. If not configured, the destination mac-address is obtained from one of the EVPN IP Prefix routes for the destination, out of the Router’s MAC extended community. :rel parent_destination: Relation to parent container
- relation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::Destination parent_destination [1]¶
Relation to parent container Peer relation: Parameters of the inner VXLAN ethernet payload when the VXLAN tunnel is used in an ip-vrf.
The following implementations are defined for this entity:
The following implements statements select implementations for this entity:
Implementations¶
- implementation nokia_srlinux::setupAclYangContainer¶
- implementation nokia_srlinux::setupBfdYangContainer¶
- implementation nokia_srlinux::setupInterfaceYangContainer¶
- implementation nokia_srlinux::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::setupOamYangContainer¶
- implementation nokia_srlinux::setupPlatformYangContainer¶
- implementation nokia_srlinux::setupRoutingPolicyYangContainer¶
- implementation nokia_srlinux::setupSystemYangContainer¶
- implementation nokia_srlinux::setupTransportSecurityYangContainer¶
- implementation nokia_srlinux::setupTunnelInterfaceYangContainer¶
- implementation nokia_srlinux::setupTunnelYangContainer¶
- implementation nokia_srlinux::yangBaseEntity¶
- implementation nokia_srlinux::yangDevice¶
Setup the device root container and the agent.
- implementation nokia_srlinux::acl::setupCpmFilterYangContainer¶
- implementation nokia_srlinux::acl::setupIpv4FilterYangContainer¶
- implementation nokia_srlinux::acl::setupIpv6FilterYangContainer¶
- implementation nokia_srlinux::acl::setupMacFilterYangContainer¶
- implementation nokia_srlinux::acl::setupPolicersYangContainer¶
- implementation nokia_srlinux::acl::setupSystemFilterYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::setupIpv4FilterYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::setupIpv6FilterYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::setupMacFilterYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::action::accept::setupRateLimitYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::setupDestinationIpYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::setupDestinationPortYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::setupIcmpYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::setupSourceIpYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::setupSourcePortYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::destination_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv4_filter::entry::match::source_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::action::accept::setupRateLimitYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::setupDestinationIpYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::setupDestinationPortYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::setupIcmp6YangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::setupSourceIpYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::setupSourcePortYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::destination_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::ipv6_filter::entry::match::source_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::action::accept::setupRateLimitYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::setupDestinationMacYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::setupSourceMacYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::setupVlanYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::setupOutermostVlanIdYangContainer¶
- implementation nokia_srlinux::acl::cpm_filter::mac_filter::entry::match::vlan::outermost_vlan_id::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::action::accept::setupForwardYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::action::accept::forward::setupNextHopYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::setupDestinationIpYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::setupDestinationPortYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::setupIcmpYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::setupSourceIpYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::setupSourcePortYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::destination_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::ipv4_filter::entry::match::source_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::action::accept::setupForwardYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::action::accept::forward::setupNextHopYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::setupDestinationIpYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::setupDestinationPortYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::setupIcmp6YangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::setupSourceIpYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::setupSourcePortYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::destination_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::ipv6_filter::entry::match::source_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::action::accept::setupForwardYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::action::accept::forward::setupNextHopYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::match::setupDestinationMacYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::match::setupSourceMacYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::match::setupVlanYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::match::vlan::setupOutermostVlanIdYangContainer¶
- implementation nokia_srlinux::acl::mac_filter::entry::match::vlan::outermost_vlan_id::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::policers::setupSystemCpuPolicerYangContainer¶
- implementation nokia_srlinux::acl::system_filter::setupIpv4FilterYangContainer¶
- implementation nokia_srlinux::acl::system_filter::setupIpv6FilterYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::setupDestinationIpYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::setupDestinationPortYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::setupIcmpYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::setupSourceIpYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::setupSourcePortYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::destination_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv4_filter::entry::match::source_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::setupActionYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::setupMatchYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::setupAcceptYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::action::setupDropYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::setupDestinationIpYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::setupDestinationPortYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::setupIcmp6YangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::setupSourceIpYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::setupSourcePortYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::destination_port::setupRangeYangContainer¶
- implementation nokia_srlinux::acl::system_filter::ipv6_filter::entry::match::source_port::setupRangeYangContainer¶
- implementation nokia_srlinux::bfd::setupMicroBfdSessionsYangContainer¶
- implementation nokia_srlinux::bfd::setupSubinterfaceYangContainer¶
- implementation nokia_srlinux::bfd::micro_bfd_sessions::setupLagInterfaceYangContainer¶
- implementation nokia_srlinux::interface::setupBreakoutModeYangContainer¶
- implementation nokia_srlinux::interface::setupEthernetYangContainer¶
- implementation nokia_srlinux::interface::setupLagYangContainer¶
- implementation nokia_srlinux::interface::setupLinuxYangContainer¶
- implementation nokia_srlinux::interface::setupP4rtYangContainer¶
- implementation nokia_srlinux::interface::setupSflowYangContainer¶
- implementation nokia_srlinux::interface::setupSubinterfaceYangContainer¶
- implementation nokia_srlinux::interface::setupTransceiverYangContainer¶
- implementation nokia_srlinux::interface::setupVhostYangContainer¶
- implementation nokia_srlinux::interface::ethernet::setupFlowControlYangContainer¶
- implementation nokia_srlinux::interface::ethernet::setupHoldTimeYangContainer¶
- implementation nokia_srlinux::interface::ethernet::setupL2cpTransparencyYangContainer¶
- implementation nokia_srlinux::interface::ethernet::setupStormControlYangContainer¶
- implementation nokia_srlinux::interface::ethernet::setupSynceYangContainer¶
- implementation nokia_srlinux::interface::ethernet::l2cp_transparency::setupDot1xYangContainer¶
- implementation nokia_srlinux::interface::ethernet::l2cp_transparency::setupLacpYangContainer¶
- implementation nokia_srlinux::interface::ethernet::l2cp_transparency::setupLldpYangContainer¶
- implementation nokia_srlinux::interface::ethernet::l2cp_transparency::setupPtpYangContainer¶
- implementation nokia_srlinux::interface::ethernet::l2cp_transparency::setupXstpYangContainer¶
- implementation nokia_srlinux::interface::ethernet::synce::setupSsmYangContainer¶
- implementation nokia_srlinux::interface::lag::setupLacpYangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupAclYangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupAnycastGwYangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupEthCfmYangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupIpv4YangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupIpv6YangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupRaGuardYangContainer¶
- implementation nokia_srlinux::interface::subinterface::setupVlanYangContainer¶
- implementation nokia_srlinux::interface::subinterface::acl::setupInputYangContainer¶
- implementation nokia_srlinux::interface::subinterface::acl::setupOutputYangContainer¶
- implementation nokia_srlinux::interface::subinterface::bridge_table::setupMacDuplicationYangContainer¶
- implementation nokia_srlinux::interface::subinterface::bridge_table::setupMacLearningYangContainer¶
- implementation nokia_srlinux::interface::subinterface::bridge_table::setupMacLimitYangContainer¶
- implementation nokia_srlinux::interface::subinterface::bridge_table::mac_learning::setupAgingYangContainer¶
- implementation nokia_srlinux::interface::subinterface::eth_cfm::setupIngressSquelchingYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::setupAddressYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::setupArpYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::setupDhcpClientYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::setupDhcpRelayYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::setupDhcpServerYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::setupUnnumberedYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::address::setupVrrpYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::setupVrrpGroupYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::setupInterfaceTrackingYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::setupStatisticsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::address::vrrp::vrrp_group::interface_tracking::setupTrackInterfaceYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::setupEvpnYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::setupHostRouteYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::setupNeighborYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::setupVirtualIpv4DiscoveryYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::evpn::setupAdvertiseYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::evpn::advertise::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::host_route::setupPopulateYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::host_route::populate::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::arp::virtual_ipv4_discovery::setupAddressYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::dhcp_client::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv4::dhcp_relay::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::setupAddressYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::setupDhcpClientYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::setupDhcpRelayYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::setupDhcpv6ServerYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::setupNeighborDiscoveryYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::setupRouterAdvertisementYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::address::setupVrrpYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::setupVrrpGroupYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::setupInterfaceTrackingYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::setupStatisticsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::address::vrrp::vrrp_group::interface_tracking::setupTrackInterfaceYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::dhcp_client::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::dhcp_relay::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::setupEvpnYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::setupHostRouteYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::setupLimitYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::setupNeighborYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::setupVirtualIpv6DiscoveryYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::setupAdvertiseYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::evpn::advertise::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::setupPopulateYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::host_route::populate::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::neighbor_discovery::virtual_ipv6_discovery::setupAddressYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::router_advertisement::setupRouterRoleYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ipv6::router_advertisement::router_role::setupPrefixYangContainer¶
- implementation nokia_srlinux::interface::subinterface::ra_guard::setupVlanListYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::setupEncapYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::setupVlanDiscoveryYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::encap::setupDoubleTaggedYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::encap::setupSingleTaggedRangeYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::encap::setupSingleTaggedYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::encap::setupUntaggedYangContainer¶
- implementation nokia_srlinux::interface::subinterface::vlan::encap::single_tagged_range::setupLowVlanIdYangContainer¶
- implementation nokia_srlinux::network_instance::setupAggregateRoutesYangContainer¶
- implementation nokia_srlinux::network_instance::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::network_instance::setupConnectionPointYangContainer¶
- implementation nokia_srlinux::network_instance::setupInterInstancePoliciesYangContainer¶
- implementation nokia_srlinux::network_instance::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::setupIpForwardingYangContainer¶
- implementation nokia_srlinux::network_instance::setupIpLoadBalancingYangContainer¶
- implementation nokia_srlinux::network_instance::setupMaintenancePoliciesYangContainer¶
- implementation nokia_srlinux::network_instance::setupMplsForwardingYangContainer¶
- implementation nokia_srlinux::network_instance::setupMplsYangContainer¶
- implementation nokia_srlinux::network_instance::setupMtuYangContainer¶
- implementation nokia_srlinux::network_instance::setupMulticastL3VpnYangContainer¶
- implementation nokia_srlinux::network_instance::setupNextHopGroupsYangContainer¶
- implementation nokia_srlinux::network_instance::setupPolicyForwardingYangContainer¶
- implementation nokia_srlinux::network_instance::setupProtocolsYangContainer¶
- implementation nokia_srlinux::network_instance::setupSegmentRoutingYangContainer¶
- implementation nokia_srlinux::network_instance::setupStaticRoutesYangContainer¶
- implementation nokia_srlinux::network_instance::setupTrafficEngineeringPoliciesYangContainer¶
- implementation nokia_srlinux::network_instance::setupTrafficEngineeringYangContainer¶
- implementation nokia_srlinux::network_instance::setupVxlanInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::aggregate_routes::setupRouteYangContainer¶
- implementation nokia_srlinux::network_instance::aggregate_routes::route::setupAggregatorYangContainer¶
- implementation nokia_srlinux::network_instance::aggregate_routes::route::setupCommunitiesYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupMacDuplicationYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupMacLearningYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupMacLimitYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupProxyArpYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupProxyNdYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupSplitHorizonGroupYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::setupStaticMacYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::mac_learning::setupAgingYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::setupDynamicLearningYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::setupEvpnYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::setupIpDuplicationYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::setupStaticEntriesYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::setupFloodYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::evpn::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::static_entries::setupNeighborYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_arp::trace_options::setupFlagYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::setupDynamicLearningYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::setupEvpnYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::setupIpDuplicationYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::setupStaticEntriesYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::setupFloodYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::evpn::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::static_entries::setupNeighborYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::proxy_nd::trace_options::setupFlagYangContainer¶
- implementation nokia_srlinux::network_instance::bridge_table::static_mac::setupMacYangContainer¶
- implementation nokia_srlinux::network_instance::inter_instance_policies::setupApplyPolicyYangContainer¶
- implementation nokia_srlinux::network_instance::interface::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::network_instance::interface::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::network_instance::ip_forwarding::setupLastResortLookupYangContainer¶
- implementation nokia_srlinux::network_instance::ip_load_balancing::setupResilientHashPrefixYangContainer¶
- implementation nokia_srlinux::network_instance::maintenance_policies::setupPolicyYangContainer¶
- implementation nokia_srlinux::network_instance::maintenance_policies::policy::setupSeamlessBfdYangContainer¶
- implementation nokia_srlinux::network_instance::mpls::setupNdkLabelBlockYangContainer¶
- implementation nokia_srlinux::network_instance::mpls::setupStaticEntryYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::setupBgpYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::setupProviderTunnelYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::setupBgpInstanceYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::setupRouteTargetYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::setupExportRtYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::bgp::bgp_instance::route_target::setupImportRtYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::setupInclusiveYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::setupSelectiveYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::inclusive::setupMldpYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::setupDataRateThresholdYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::setupMldpYangContainer¶
- implementation nokia_srlinux::network_instance::multicast_l3_vpn::provider_tunnel::selective::data_rate_threshold::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::next_hop_groups::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::next_hop_groups::group::setupBlackholeYangContainer¶
- implementation nokia_srlinux::network_instance::next_hop_groups::group::setupNexthopYangContainer¶
- implementation nokia_srlinux::network_instance::next_hop_groups::group::nexthop::setupFailureDetectionYangContainer¶
- implementation nokia_srlinux::network_instance::next_hop_groups::group::nexthop::failure_detection::setupEnableBfdYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::setupPolicyYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::interface::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::policy::setupRuleYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::policy::rule::setupActionYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::policy::rule::setupMatchYangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::setupIpv4YangContainer¶
- implementation nokia_srlinux::network_instance::policy_forwarding::policy::rule::match::ipv4::setupSourceIpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupBgpEvpnYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupBgpIpvpnYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupBgpVpnYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupBgpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupDirectlyConnectedYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupGribiYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupIgmpSnoopingYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupIgmpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupIsisYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupLdpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupLinuxYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupMldSnoopingYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupMldYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupOspfYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::setupPimYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupAfiSafiYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupAsPathOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupBestPathSelectionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupBgpLabelYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupDynamicNeighborsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupEbgpDefaultPolicyYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupFailureDetectionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupGracefulRestartYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupNeighborYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupPreferenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupRibManagementYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupRouteAdvertisementYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupRouteReflectorYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::setupTransportYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupAddPathsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupEvpnYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupIpv4LabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupIpv6LabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupL3vpnIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupL3vpnIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::setupMultipathYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::setupBackupPathsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::setupIpv4NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::setupIpv6NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv4_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv4_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv6_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_labeled_unicast::next_hop_resolution::ipv6_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::setupIpv4NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::setupIpv6NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv4_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv4_unicast::next_hop_resolution::ipv6_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::setupBackupPathsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::setupIpv4NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::setupIpv6NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv4_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv4_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv6_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_labeled_unicast::next_hop_resolution::ipv6_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::setupIpv4NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::setupIpv6NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv4_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::ipv6_unicast::next_hop_resolution::ipv6_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::setupIpv4NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::setupIpv6NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv4_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv4_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv6_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv4_unicast::next_hop_resolution::ipv6_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::setupConvergenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::setupIpv4NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::setupIpv6NextHopsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv4_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv4_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv6_next_hops::setupRouteResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::afi_safi::l3vpn_ipv6_unicast::next_hop_resolution::ipv6_next_hops::setupTunnelResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::as_path_options::setupRemovePrivateAsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::bgp_label::setupLabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::setupAcceptYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::dynamic_neighbors::accept::setupMatchYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupAfiSafiYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupAsPathOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupFailureDetectionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupGracefulRestartYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupLocalAsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupMultihopYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupRouteReflectorYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupSendDefaultRouteYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupTimersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::setupTransportYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupAddPathsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupEvpnYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupIpv4LabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupIpv6LabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupL3vpnIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::setupL3vpnIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::evpn::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_labeled_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::setupLinkBandwidthYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv4_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_labeled_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::setupLinkBandwidthYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::ipv6_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv4_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::afi_safi::l3vpn_ipv6_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::as_path_options::setupRemovePrivateAsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::group::trace_options::setupFlagYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupAfiSafiYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupAsPathOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupFailureDetectionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupGracefulRestartYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupLocalAsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupMultihopYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupRouteReflectorYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupSendDefaultRouteYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupTimersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::setupTransportYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupAddPathsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupEvpnYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupIpv4LabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupIpv6LabeledUnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupL3vpnIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::setupL3vpnIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::evpn::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_labeled_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::setupLinkBandwidthYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv4_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_labeled_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::setupLinkBandwidthYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::ipv6_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv4_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::afi_safi::l3vpn_ipv6_unicast::setupPrefixLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::as_path_options::setupRemovePrivateAsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::neighbor::trace_options::setupFlagYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::rib_management::setupTableYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp::trace_options::setupFlagYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::setupBgpInstanceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::setupMplsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::setupRoutesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::setupVpwsAttachmentCircuitsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::mpls::setupRouteTableYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::setupRouteTableYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::setupInclusiveMcastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::bridge_table::setupMacIpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::setupIpPrefixYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::setupMacIpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::setupEvpnLinkBandwidthYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::setupAdvertiseYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::routes::route_table::ip_prefix::evpn_link_bandwidth::setupWeightedEcmpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::setupLocalYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::setupRemoteYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::local::setupLocalAttachmentCircuitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_evpn::bgp_instance::vpws_attachment_circuits::remote::setupRemoteAttachmentCircuitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_ipvpn::setupBgpInstanceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::setupMplsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_ipvpn::bgp_instance::mpls::setupNextHopResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_vpn::setupBgpInstanceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::setupRouteDistinguisherYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::bgp_vpn::bgp_instance::setupRouteTargetYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::directly_connected::setupTeDatabaseInstallYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::directly_connected::te_database_install::setupBgpLsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::setupSsmYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::setupSsmYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::setupStaticMembershipGroupsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::setupMappingsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::ssm::mappings::group_range::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::interface::static_membership_groups::group_range::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::ssm::setupMappingsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::ssm::mappings::group_range::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp::trace_options::trace::packet::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::setupStaticMembershipGroupsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::interface::static_membership_groups::group::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::igmp_snooping::trace_options::trace::packet::setupSourceMacYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::setupInstanceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::setupNonStopForwardingYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupAttachedBitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupAutoCostYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupGracefulRestartYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupInterLevelPropagationPoliciesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupLdpSynchronizationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupLevelYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupLoopfreeAlternateYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupOverloadYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupSegmentRoutingYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupTeDatabaseInstallYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupTimersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupTrafficEngineeringYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupTransportYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::setupWeightedEcmpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::authentication::setupCsnpAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::authentication::setupHelloAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::authentication::setupKeyYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::authentication::setupLspAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::authentication::setupPsnpAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::setupLevel1ToLevel2YangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::inter_level_propagation_policies::level1_to_level2::setupSummaryAddressYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupDelayYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupIpv4UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupIpv6UnicastYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupLdpSynchronizationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupLevelYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupSegmentRoutingYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupTimersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::setupWeightedEcmpYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::authentication::setupHelloAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::authentication::setupKeyYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::setupTimersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::authentication::setupHelloAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::level::authentication::setupKeyYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::setupMplsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::setupIpv4AdjacencySidYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::setupIpv4NodeSidYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::setupIpv6AdjacencySidYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::interface::segment_routing::mpls::setupIpv6NodeSidYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::setupRoutePreferenceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::setupCsnpAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::setupHelloAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::setupKeyYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::setupLspAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::level::authentication::setupPsnpAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::setupExcludeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::setupMultiHomedPrefixYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::setupRemoteLfaYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::setupTiLfaYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::remote_lfa::setupNodeProtectYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::loopfree_alternate::ti_lfa::setupNodeProtectYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::overload::setupImmediateYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::overload::setupOnBootYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::setupMplsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::segment_routing::mpls::setupDynamicAdjacencySidsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::te_database_install::setupBgpLsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::timers::setupLspGenerationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::timers::setupLspRefreshYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::isis::instance::timers::setupSpfYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupDiscoveryYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupEntropyLabelYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupGracefulRestartYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupIpv4YangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupLoopfreeAlternateYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupMultipathYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupPeersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::setupStaticFecYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::setupInterfacesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::setupTargetedYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::setupIpv4YangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::interfaces::interface::ipv4::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::setupIpv4YangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::discovery::targeted::ipv4::setupTargetYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::ipv4::setupFecResolutionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::peers::setupPeerYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::peers::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::peers::peer::setupTcpTransportYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ldp::peers::peer::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::setupSsmYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::setupSsmYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::setupStaticMembershipGroupsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::ssm::setupMappingsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::ssm::mappings::group_range::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::interface::static_membership_groups::group_range::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::ssm::setupMappingsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::ssm::mappings::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::ssm::mappings::group_range::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld::trace_options::trace::packet::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::interface::setupStaticMembershipGroupsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::interface::static_membership_groups::group::setupSourceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::mld_snooping::trace_options::trace::packet::setupSourceMacYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::setupInstanceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupAreaYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupAsbrYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupExportLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupExternalDbOverflowYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupGracefulRestartYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupLdpSynchronizationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupOverloadYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupTeDatabaseInstallYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupTimersYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::setupTrafficEngineeringYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::setupAreaRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::setupNssaYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::setupStubYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::setupFailureDetectionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::setupLdpSynchronizationYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::interface::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::setupAreaRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::area::nssa::setupOriginateDefaultRouteYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::overload::setupOverloadOnBootYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::overload::setupRtrAdvLsaLimitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::te_database_install::setupBgpLsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::timers::setupLsaGenerateYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::timers::setupSpfWaitYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::setupLsdbYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::setupRoutesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::ospf::instance::trace_options::trace::setupSpfYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupIpv4YangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupIpv6YangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupRendezvousPointsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupSptSwitchoverYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupSsmYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::setupStaticYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::setupRendezvousPointYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::rendezvous_points::static::rendezvous_point::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::spt_switchover::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::ssm::setupSsmRangesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::ssm::ssm_ranges::setupGroupRangeYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::setupTraceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::setupEventsYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::setupPacketYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::setupAllEventTypesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::setupEventTypesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupAdjacencyYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupAssertYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupDataExceptionYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupDatabaseYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupJoinPruneYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupMessagingYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupPimRouteTableYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::events::event_types::setupRegisterYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::setupAllPacketTypesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::setupPacketTypesYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::setupAssertYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::setupHelloYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::setupJoinPruneYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::setupRegisterStopYangContainer¶
- implementation nokia_srlinux::network_instance::protocols::pim::trace_options::trace::packet::packet_types::setupRegisterYangContainer¶
- implementation nokia_srlinux::network_instance::segment_routing::setupMplsYangContainer¶
- implementation nokia_srlinux::network_instance::segment_routing::mpls::setupGlobalBlockYangContainer¶
- implementation nokia_srlinux::network_instance::segment_routing::mpls::setupLocalPrefixSidYangContainer¶
- implementation nokia_srlinux::network_instance::static_routes::setupRouteYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::setupAdminGroupsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::setupInterfaceYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::setupPcepYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::admin_groups::setupGroupYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::setupDelayYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::delay::setupDynamicYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::setupLinkMeasurementYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::setupStampYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::stamp::setupIpv4YangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::interface::delay::dynamic::link_measurement::stamp::setupIpv6YangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::pcep::setupPccYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::setupPceAssociationsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::setupPeerYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::setupStateTimerYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::setupDiversityYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering::pcep::pcc::pce_associations::setupPolicyYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::setupBindingSidYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::setupExplicitPathsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::setupPolicyYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::setupPathYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::setupHopYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::explicit_paths::path::hop::setupIpYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::setupApplicationBindingsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::setupBindingSidYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::setupEgressStatisticsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::setupEntropyLabelYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::setupIngressStatisticsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::setupSegmentListYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::setupDynamicYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::setupPriorityYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::setupTeConstraintsYangContainer¶
- implementation nokia_srlinux::network_instance::traffic_engineering_policies::policy::segment_list::dynamic::te_constraints::setupSegmentDepthYangContainer¶
- implementation nokia_srlinux::oam::setupEthcfmYangContainer¶
- implementation nokia_srlinux::oam::setupIppmYangContainer¶
- implementation nokia_srlinux::oam::setupLinkMeasurementYangContainer¶
- implementation nokia_srlinux::oam::setupPerformanceMonitoringYangContainer¶
- implementation nokia_srlinux::oam::setupStampYangContainer¶
- implementation nokia_srlinux::oam::setupTwampYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::setupDomainYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::setupSenderIdYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::setupAssociationYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::setupAssociationMepsYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::setupCcmHoldTimeYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::setupMepYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::setupRemoteMepAutoDiscoveryYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::mep::setupContinuityCheckYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::mep::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::oam::ethcfm::domain::association::mep::continuity_check::setupCcmLocalFaultYangContainer¶
- implementation nokia_srlinux::oam::ippm::setupSourceUdpPortPoolsYangContainer¶
- implementation nokia_srlinux::oam::ippm::source_udp_port_pools::setupPortYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::setupMeasurementTemplateYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::setupStampYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::stamp::setupAggregateSampleWindowYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::stamp::setupIpv6DestinationDiscoveryYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::stamp::setupReturnPathYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::stamp::setupSampleWindowYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::stamp::aggregate_sample_window::setupThresholdYangContainer¶
- implementation nokia_srlinux::oam::link_measurement::measurement_template::stamp::sample_window::setupThresholdYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::setupEthcfmYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::setupIpYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::setupDelayYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::setupLossYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::setupSessionYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::setupBinGroupYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::setupBinTypeYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::setupBinYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::setupDelayEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::delay::bin_group::bin_type::setupExcludeFromAvgYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::setupLossEventsTemplateYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::setupAvgFlrEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::setupChliEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::setupHliEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::loss::loss_events_template::setupUndeterminedAvailabilityEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::session::setupEthCfmSingleEndedDmmTestYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::session::setupEthCfmSingleEndedSlmTestYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::session::setupMeasurementIntervalYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::session::setupSourceYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::session::eth_cfm_single_ended_slm_test::setupTimingYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ethcfm::session::measurement_interval::setupThresholdAlertsYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::setupDelayYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::setupLossYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::setupSessionYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::delay::setupBinGroupYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::setupBinTypeYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::setupBinYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::setupDelayEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::delay::bin_group::bin_type::setupExcludeFromAvgYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::loss::setupLossEventsTemplateYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::setupAvgFlrEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::setupChliEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::setupHliEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::loss::loss_events_template::setupUndeterminedAvailabilityEventYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::setupForwardingYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::setupMeasurementIntervalYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::setupStampYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::forwarding::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::measurement_interval::setupThresholdAlertsYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::setupDelayYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::setupLossYangContainer¶
- implementation nokia_srlinux::oam::performance_monitoring::ip::session::stamp::loss::setupTimingYangContainer¶
- implementation nokia_srlinux::oam::stamp::setupSessionReflectorYangContainer¶
- implementation nokia_srlinux::oam::stamp::session_reflector::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::oam::stamp::session_reflector::network_instance::setupIpPrefixYangContainer¶
- implementation nokia_srlinux::oam::twamp::setupServerYangContainer¶
- implementation nokia_srlinux::oam::twamp::server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::oam::twamp::server::network_instance::setupClientConnectionYangContainer¶
- implementation nokia_srlinux::oam::twamp::server::network_instance::setupSessionReflectorYangContainer¶
- implementation nokia_srlinux::platform::setupChassisYangContainer¶
- implementation nokia_srlinux::platform::setupControlYangContainer¶
- implementation nokia_srlinux::platform::setupFabricYangContainer¶
- implementation nokia_srlinux::platform::setupLinecardYangContainer¶
- implementation nokia_srlinux::platform::setupRedundancyYangContainer¶
- implementation nokia_srlinux::platform::setupResourceManagementYangContainer¶
- implementation nokia_srlinux::platform::setupResourceMonitoringYangContainer¶
- implementation nokia_srlinux::platform::setupVxdpYangContainer¶
- implementation nokia_srlinux::platform::chassis::setupPowerYangContainer¶
- implementation nokia_srlinux::platform::chassis::power::setupRedundancyYangContainer¶
- implementation nokia_srlinux::platform::control::setupInterfaceYangContainer¶
- implementation nokia_srlinux::platform::linecard::setupForwardingComplexYangContainer¶
- implementation nokia_srlinux::platform::linecard::forwarding_complex::setupBufferMemoryYangContainer¶
- implementation nokia_srlinux::platform::linecard::forwarding_complex::setupFabricYangContainer¶
- implementation nokia_srlinux::platform::linecard::forwarding_complex::setupP4rtYangContainer¶
- implementation nokia_srlinux::platform::linecard::forwarding_complex::setupPipelineYangContainer¶
- implementation nokia_srlinux::platform::redundancy::setupSynchronizationYangContainer¶
- implementation nokia_srlinux::platform::redundancy::synchronization::setupOverlayYangContainer¶
- implementation nokia_srlinux::platform::resource_management::setupTcamYangContainer¶
- implementation nokia_srlinux::platform::resource_management::setupUnifiedForwardingResourcesYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::setupDatapathYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::setupMtuYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::setupQosYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::datapath::setupAsicYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::datapath::setupXdpYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::datapath::asic::setupXResourceYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::datapath::xdp::setupXResourceYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::mtu::setupXResourceYangContainer¶
- implementation nokia_srlinux::platform::resource_monitoring::qos::setupXResourceYangContainer¶
- implementation nokia_srlinux::routing_policy::setupAsPathSetYangContainer¶
- implementation nokia_srlinux::routing_policy::setupCommunitySetYangContainer¶
- implementation nokia_srlinux::routing_policy::setupPolicyYangContainer¶
- implementation nokia_srlinux::routing_policy::setupPrefixSetYangContainer¶
- implementation nokia_srlinux::routing_policy::setupTagSetYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::setupDefaultActionYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::setupStatementYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::setupBgpYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::setupRoutePreferenceYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::bgp::setupAsPathYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::bgp::setupCommunitiesYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::bgp::setupLocalPreferenceYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::bgp::setupMedYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::bgp::setupOriginYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::default_action::bgp::as_path::setupPrependYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::setupActionYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::setupMatchYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::setupBgpYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::setupRoutePreferenceYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::bgp::setupAsPathYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::bgp::setupCommunitiesYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::bgp::setupLocalPreferenceYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::bgp::setupMedYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::bgp::setupOriginYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::action::bgp::as_path::setupPrependYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::match::setupBgpYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::match::setupInternalTagsYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::match::setupIsisYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::match::setupOspfYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::match::bgp::setupAsPathLengthYangContainer¶
- implementation nokia_srlinux::routing_policy::policy::statement::match::bgp::setupEvpnYangContainer¶
- implementation nokia_srlinux::routing_policy::prefix_set::setupPrefixYangContainer¶
- implementation nokia_srlinux::system::setupAaaYangContainer¶
- implementation nokia_srlinux::system::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::system::setupBannerYangContainer¶
- implementation nokia_srlinux::system::setupBootYangContainer¶
- implementation nokia_srlinux::system::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::system::setupClockYangContainer¶
- implementation nokia_srlinux::system::setupConfigurationYangContainer¶
- implementation nokia_srlinux::system::setupDhcpServerYangContainer¶
- implementation nokia_srlinux::system::setupDnsYangContainer¶
- implementation nokia_srlinux::system::setupEventHandlerYangContainer¶
- implementation nokia_srlinux::system::setupFtpServerYangContainer¶
- implementation nokia_srlinux::system::setupGnmiServerYangContainer¶
- implementation nokia_srlinux::system::setupGribiServerYangContainer¶
- implementation nokia_srlinux::system::setupInformationYangContainer¶
- implementation nokia_srlinux::system::setupJsonRpcServerYangContainer¶
- implementation nokia_srlinux::system::setupLacpYangContainer¶
- implementation nokia_srlinux::system::setupLicenseYangContainer¶
- implementation nokia_srlinux::system::setupLldpYangContainer¶
- implementation nokia_srlinux::system::setupLoggingYangContainer¶
- implementation nokia_srlinux::system::setupMaintenanceYangContainer¶
- implementation nokia_srlinux::system::setupManagementYangContainer¶
- implementation nokia_srlinux::system::setupMirroringYangContainer¶
- implementation nokia_srlinux::system::setupMplsYangContainer¶
- implementation nokia_srlinux::system::setupMtuYangContainer¶
- implementation nokia_srlinux::system::setupMulticastYangContainer¶
- implementation nokia_srlinux::system::setupNameYangContainer¶
- implementation nokia_srlinux::system::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::setupNtpYangContainer¶
- implementation nokia_srlinux::system::setupP4rtServerYangContainer¶
- implementation nokia_srlinux::system::setupPacketLinkQualificationYangContainer¶
- implementation nokia_srlinux::system::setupProtocolsYangContainer¶
- implementation nokia_srlinux::system::setupRaGuardPolicyYangContainer¶
- implementation nokia_srlinux::system::setupSflowYangContainer¶
- implementation nokia_srlinux::system::setupSnmpYangContainer¶
- implementation nokia_srlinux::system::setupSshServerYangContainer¶
- implementation nokia_srlinux::system::setupSyncYangContainer¶
- implementation nokia_srlinux::system::setupTlsYangContainer¶
- implementation nokia_srlinux::system::aaa::setupAccountingYangContainer¶
- implementation nokia_srlinux::system::aaa::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::system::aaa::setupAuthorizationYangContainer¶
- implementation nokia_srlinux::system::aaa::setupServerGroupYangContainer¶
- implementation nokia_srlinux::system::aaa::accounting::setupEventYangContainer¶
- implementation nokia_srlinux::system::aaa::authentication::setupAdminUserYangContainer¶
- implementation nokia_srlinux::system::aaa::authentication::setupLinuxadminUserYangContainer¶
- implementation nokia_srlinux::system::aaa::authentication::setupPasswordYangContainer¶
- implementation nokia_srlinux::system::aaa::authentication::setupUserYangContainer¶
- implementation nokia_srlinux::system::aaa::authentication::password::setupComplexityRulesYangContainer¶
- implementation nokia_srlinux::system::aaa::authentication::password::setupLockoutPolicyYangContainer¶
- implementation nokia_srlinux::system::aaa::authorization::setupRoleYangContainer¶
- implementation nokia_srlinux::system::aaa::authorization::role::setupCliYangContainer¶
- implementation nokia_srlinux::system::aaa::authorization::role::setupTacacsYangContainer¶
- implementation nokia_srlinux::system::aaa::server_group::setupServerYangContainer¶
- implementation nokia_srlinux::system::aaa::server_group::server::setupRadiusYangContainer¶
- implementation nokia_srlinux::system::aaa::server_group::server::setupTacacsYangContainer¶
- implementation nokia_srlinux::system::authentication::setupKeychainYangContainer¶
- implementation nokia_srlinux::system::authentication::keychain::setupKeyYangContainer¶
- implementation nokia_srlinux::system::authentication::keychain::key::setupReceiveLifetimeYangContainer¶
- implementation nokia_srlinux::system::authentication::keychain::key::setupSendLifetimeYangContainer¶
- implementation nokia_srlinux::system::boot::setupAutobootYangContainer¶
- implementation nokia_srlinux::system::bridge_table::setupMacLearningYangContainer¶
- implementation nokia_srlinux::system::bridge_table::setupMacLimitYangContainer¶
- implementation nokia_srlinux::system::configuration::setupRoleYangContainer¶
- implementation nokia_srlinux::system::configuration::role::setupRuleYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::setupDhcpv4YangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::setupDhcpv6YangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::setupOptionsYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::setupStaticAllocationYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::setupHostYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv4::static_allocation::host::setupOptionsYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::setupOptionsYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::setupStaticAllocationYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::setupTraceOptionsYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::setupHostYangContainer¶
- implementation nokia_srlinux::system::dhcp_server::network_instance::dhcpv6::static_allocation::host::setupOptionsYangContainer¶
- implementation nokia_srlinux::system::dns::setupHostEntryYangContainer¶
- implementation nokia_srlinux::system::event_handler::setupInstanceYangContainer¶
- implementation nokia_srlinux::system::event_handler::instance::setupOptionsYangContainer¶
- implementation nokia_srlinux::system::event_handler::instance::options::setupObjectYangContainer¶
- implementation nokia_srlinux::system::ftp_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::gnmi_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::gnmi_server::setupUnixSocketYangContainer¶
- implementation nokia_srlinux::system::gribi_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::gribi_server::setupUnixSocketYangContainer¶
- implementation nokia_srlinux::system::json_rpc_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::json_rpc_server::setupUnixSocketYangContainer¶
- implementation nokia_srlinux::system::json_rpc_server::network_instance::setupHttpYangContainer¶
- implementation nokia_srlinux::system::json_rpc_server::network_instance::setupHttpsYangContainer¶
- implementation nokia_srlinux::system::lldp::setupBgpAutoDiscoveryYangContainer¶
- implementation nokia_srlinux::system::lldp::setupInterfaceYangContainer¶
- implementation nokia_srlinux::system::lldp::setupManagementAddressYangContainer¶
- implementation nokia_srlinux::system::lldp::interface::setupBgpAutoDiscoveryYangContainer¶
- implementation nokia_srlinux::system::logging::setupBufferYangContainer¶
- implementation nokia_srlinux::system::logging::setupConsoleYangContainer¶
- implementation nokia_srlinux::system::logging::setupFileYangContainer¶
- implementation nokia_srlinux::system::logging::setupFilterYangContainer¶
- implementation nokia_srlinux::system::logging::setupRemoteServerYangContainer¶
- implementation nokia_srlinux::system::logging::buffer::setupFacilityYangContainer¶
- implementation nokia_srlinux::system::logging::buffer::setupSubsystemYangContainer¶
- implementation nokia_srlinux::system::logging::buffer::facility::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::buffer::subsystem::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::console::setupFacilityYangContainer¶
- implementation nokia_srlinux::system::logging::console::setupSubsystemYangContainer¶
- implementation nokia_srlinux::system::logging::console::facility::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::console::subsystem::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::file::setupFacilityYangContainer¶
- implementation nokia_srlinux::system::logging::file::setupSubsystemYangContainer¶
- implementation nokia_srlinux::system::logging::file::facility::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::file::subsystem::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::filter::setupFacilityYangContainer¶
- implementation nokia_srlinux::system::logging::filter::facility::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::remote_server::setupFacilityYangContainer¶
- implementation nokia_srlinux::system::logging::remote_server::setupSubsystemYangContainer¶
- implementation nokia_srlinux::system::logging::remote_server::facility::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::logging::remote_server::subsystem::setupPriorityYangContainer¶
- implementation nokia_srlinux::system::maintenance::setupGroupYangContainer¶
- implementation nokia_srlinux::system::maintenance::setupProfileYangContainer¶
- implementation nokia_srlinux::system::maintenance::group::setupMaintenanceModeYangContainer¶
- implementation nokia_srlinux::system::maintenance::group::setupMembersYangContainer¶
- implementation nokia_srlinux::system::maintenance::group::members::setupBgpYangContainer¶
- implementation nokia_srlinux::system::maintenance::group::members::setupIsisYangContainer¶
- implementation nokia_srlinux::system::maintenance::group::members::bgp::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::maintenance::profile::setupBgpYangContainer¶
- implementation nokia_srlinux::system::maintenance::profile::setupIsisYangContainer¶
- implementation nokia_srlinux::system::maintenance::profile::isis::setupOverloadYangContainer¶
- implementation nokia_srlinux::system::management::setupOpenconfigYangContainer¶
- implementation nokia_srlinux::system::mirroring::setupMirroringInstanceYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::setupMirrorDestinationYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::setupMirrorSourceYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::setupRemoteYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_destination::remote::setupTunnelEndPointsYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::setupAclYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::setupIpv4FilterYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::setupIpv6FilterYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv4_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::system::mirroring::mirroring_instance::mirror_source::acl::ipv6_filter::setupEntryYangContainer¶
- implementation nokia_srlinux::system::mpls::setupLabelRangesYangContainer¶
- implementation nokia_srlinux::system::mpls::setupServicesYangContainer¶
- implementation nokia_srlinux::system::mpls::label_ranges::setupDynamicYangContainer¶
- implementation nokia_srlinux::system::mpls::label_ranges::setupStaticYangContainer¶
- implementation nokia_srlinux::system::mpls::services::setupEvpnYangContainer¶
- implementation nokia_srlinux::system::mpls::services::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::multicast::setupMulticastIdsYangContainer¶
- implementation nokia_srlinux::system::network_instance::setupProtocolsYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::setupBgpVpnYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::setupEvpnYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::bgp_vpn::setupBgpInstanceYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance::setupRouteDistinguisherYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::bgp_vpn::bgp_instance::setupRouteTargetYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::setupEthernetSegmentsYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::setupBgpInstanceYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::setupTimersYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::setupEthernetSegmentYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::setupDfElectionYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::setupInterfaceYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::setupNextHopYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::setupRoutesYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::setupAlgorithmYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::setupInterfaceStandbySignalingOnNonDfYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::setupTimersYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::setupManualAlgYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::setupPreferenceAlgYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::manual_alg::setupPrimaryEviRangeYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::df_election::algorithm::preference_alg::setupCapabilitiesYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::next_hop::setupEviYangContainer¶
- implementation nokia_srlinux::system::network_instance::protocols::evpn::ethernet_segments::bgp_instance::ethernet_segment::routes::setupEthernetSegmentYangContainer¶
- implementation nokia_srlinux::system::ntp::setupServerYangContainer¶
- implementation nokia_srlinux::system::p4rt_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::p4rt_server::setupUnixSocketYangContainer¶
- implementation nokia_srlinux::system::packet_link_qualification::setupProfileYangContainer¶
- implementation nokia_srlinux::system::packet_link_qualification::profile::setupAsicLoopbackYangContainer¶
- implementation nokia_srlinux::system::packet_link_qualification::profile::setupNtpYangContainer¶
- implementation nokia_srlinux::system::packet_link_qualification::profile::setupPacketGeneratorYangContainer¶
- implementation nokia_srlinux::system::packet_link_qualification::profile::setupPmdLoopbackYangContainer¶
- implementation nokia_srlinux::system::packet_link_qualification::profile::setupRpcYangContainer¶
- implementation nokia_srlinux::system::protocols::setupBgpYangContainer¶
- implementation nokia_srlinux::system::sflow::setupCollectorYangContainer¶
- implementation nokia_srlinux::system::snmp::setupAccessGroupYangContainer¶
- implementation nokia_srlinux::system::snmp::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::snmp::access_group::setupCommunityEntryYangContainer¶
- implementation nokia_srlinux::system::snmp::access_group::setupSecurityEntryYangContainer¶
- implementation nokia_srlinux::system::snmp::access_group::security_entry::setupAuthenticationYangContainer¶
- implementation nokia_srlinux::system::snmp::access_group::security_entry::setupPrivacyYangContainer¶
- implementation nokia_srlinux::system::ssh_server::setupHostKeyYangContainer¶
- implementation nokia_srlinux::system::ssh_server::setupNetworkInstanceYangContainer¶
- implementation nokia_srlinux::system::sync::setupFreqClockYangContainer¶
- implementation nokia_srlinux::system::sync::setupFreqReferencesYangContainer¶
- implementation nokia_srlinux::system::sync::setupGnssYangContainer¶
- implementation nokia_srlinux::system::sync::setupOnePpsYangContainer¶
- implementation nokia_srlinux::system::sync::setupPtpYangContainer¶
- implementation nokia_srlinux::system::sync::freq_references::setupInstanceYangContainer¶
- implementation nokia_srlinux::system::sync::freq_references::instance::setupSourceYangContainer¶
- implementation nokia_srlinux::system::sync::gnss::setupConstellationYangContainer¶
- implementation nokia_srlinux::system::sync::gnss::setupGnssAYangContainer¶
- implementation nokia_srlinux::system::sync::gnss::setupGnssBYangContainer¶
- implementation nokia_srlinux::system::sync::gnss::gnss_a::setupSatsInUseYangContainer¶
- implementation nokia_srlinux::system::sync::gnss::gnss_b::setupSatsInUseYangContainer¶
- implementation nokia_srlinux::system::sync::ptp::setupInstanceYangContainer¶
- implementation nokia_srlinux::system::sync::ptp::instance::setupDefaultDsYangContainer¶
- implementation nokia_srlinux::system::sync::ptp::instance::setupNetworkInstancesYangContainer¶
- implementation nokia_srlinux::system::sync::ptp::instance::setupPortDsListYangContainer¶
- implementation nokia_srlinux::system::sync::ptp::instance::port_ds_list::setupSourceYangContainer¶
- implementation nokia_srlinux::system::sync::ptp::instance::port_ds_list::source::setupPeerYangContainer¶
- implementation nokia_srlinux::system::tls::setupServerProfileYangContainer¶
- implementation nokia_srlinux::transport_security::setupMacsecYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::setupInterfaceYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::setupMkaYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::interface::setupExcludeMacYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::interface::setupExcludeProtocolsYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::interface::setupInterfaceRefYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::interface::setupMkaYangContainer¶
- implementation nokia_srlinux::transport_security::macsec::mka::setupPolicyYangContainer¶
- implementation nokia_srlinux::tunnel::setupVxlanTunnelYangContainer¶
- implementation nokia_srlinux::tunnel::vxlan_tunnel::setupStatisticsYangContainer¶
- implementation nokia_srlinux::tunnel_interface::setupVxlanInterfaceYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::setupBridgeTableYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::setupEgressYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::setupIngressYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::egress::setupDestinationGroupsYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::egress::setupInnerEthernetHeaderYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::setupGroupYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::setupDestinationYangContainer¶
- implementation nokia_srlinux::tunnel_interface::vxlan_interface::egress::destination_groups::group::destination::setupInnerEthernetHeaderYangContainer¶