FSP 150CC-GE-V1.0 Course - 4 - Management
FSP 150CC-GE-V1.0 Course - 4 - Management
Product Training
Course 4 - Management
• DHCP Role:
• DHCP Client
• Supported on Mgmt Tunnels and Local Mgmt Port
• DHCP Server – the system will serve ALL host addresses that are
implied by the IP Address/subnet mask range.
• Supported only on Local Management port
• With DHCP client enabled, the system allows the user to configure the use
of Client ID in the DHCP messages. Default is Disabled.
• The system allows the serial number as an option for the DHCP
Client ID. The supported values are:
• MAC address
• System Name
• Serial Number
• User Defined String
• R8.1.1
• GE112/GE114 ONLY:
• Vlan Based: C-Tag, (C-Tag and S-Tag), or S-Tag only.
• Advantages:
• Single IP address per EDD
• Quick notification of loss of mgmt connectivity
• VLAN ID provides separation of customer and
management traffic
• Disadvantages:
• Potential issue reaching devices in the same subnet
• User or DHCP assigned IP address is not supported
SNE
MGMT WAN
LAN
GNE
• Typically all devices on the same subnet are physically connected to each
other.
• PROXY ARP allows a subnet to be extended beyond the same physical LAN.
• Proxying for ARP requests is only done on the MGMT LAN port.
10.10.1.5/24
WAN
GNE
MGMT
LAN
10.10.1.4/24
• Used when the GNE or SNE needs to respond to a frame that comes
from an IP address outside of the defined subnet(s) it has direct
knowledge of.
172.34.10.2/24
SNE
10.10.1.2/24 10.10.1.3/24
10.10.1.5/24
Gateway: 10.10.1.254
WAN
172.34.10.254/24
10.10.1.254/24 GNE
MGMT
LAN
10.10.1.4/24
Gateway: 10.10.1.254
• Traversed from most specific to least specific looking for best fit.
Search
Destination Subnet Mask Gateway/Interface Metric
Order
0.0.0.0 0.0.0.0 10.10.1.254 1 3
10.10.1.5 255.255.255.255 E1000-N-1 1 1
10.10.1.0 255.255.255.0 eth0 1 2
10.10.1.5
10.10.1.10
Remote Management Network
tunnels on same Manager
subnet
• DHCP options:
• Available for Eth0 and Access/Network Management tunnels
• DHCP options are currently supported on IPV4
• Note: When any of the above options are changed, the DHCP process will
be restarted
Option 61
Option 60
Option 7
Option 12
Option 42
• If you change the name of the system from the main menu, and dhcp host
name type is set to “system name” and host name control is “enabled”, this
will cause the DHCP client to restart.
** NOTE: The Class ID for the vendor string can be “ADVA”, “FNC”, or “JDSU”
depending on OEM
• IPv6 routing
• Supports static route entries
• Supports static neighbor entries
• Supports static proxy ND entries
• Supports dynamic routing
• RIPng (RIP next generation)
IPv4
IPv4/IPv6
Dual Stack
IPv4
IPv6
IPv6
IPv4/IPv6 Dual
Stack IPv4/IPv6 Dual
Stack
IPv4
IPv6
IPv6 over IPv4 Tunnel
Include:
• RPC invocations (<rpc> messages) - supported
• RPC results (<rpc-reply> messages) - supported
• event notifications (<notification> messages) – not supported in 8.1
• The <rpc-error> element is sent in <rpc-reply> messages if an
error occurs during the processing of an <rpc> request.
• All NETCONF messages shall be well-formed XML, encoded in UTF-
8. If a peer receives an <rpc> message that is not well-formed
XML or not encoded in UTF-8, it shall reply with a "malformed-
message" error. If a reply cannot be sent for any reason, the
server shall terminate the session.
Operation Description
<get> Retrieve running configuration and device state information
<get-config> Retrieve all or part of a specified configuration datastore
<edit-config> Edit a configuration datastore by creating, deleting, merging or replacing content
<copy-config> Copy an entire configuration datastore to another configuration datastore
<delete-config> Delete a configuration datastore
<lock> Lock an entire configuration datastore of a device
<unlock> Release a configuration datastore lock previously obtained with the <lock> operation
<close-session> Request graceful termination of a NETCONF session
<kill-session> Force the termination of a NETCONF session
• Prior to 8.1.1
• 8.1.1
IMPORTANT NOTICE
The content of this presentation is strictly confidential. ADVA Optical Networking is the exclusive owner or licensee of the content,
material, and information in this presentation. Any reproduction, publication or reprint, in whole or in part, is strictly prohibited.
The information in this presentation may not be accurate, complete or up to date, and is provided without warranties or representations
of any kind, either express or implied. ADVA Optical Networking shall not be responsible for and disclaims any liability for any loss or
damages, including without limitation, direct, indirect, incidental, consequential and special damages, alleged to have been caused by
or in connection with using and/or relying on the information contained in this presentation.
Copyright © for the entire content of this presentation: ADVA Optical Networking.