The node is shipped with the default bof.cfg file. The operator must stage the node and execute auto-boot ospf and the NEID accordingly.
At bootup, the application reads the ospf flag and performs the following functions:
The node discovers and provisions the chassis and the cards according to the connectivity requirement for the chassis.
The card and slot discovery and provisioning depend on whether the port option is set under auto-boot ospf. If the port option is set, the corresponding IOM or MDAs are discovered.
It does not load any configuration file.
If the user has set only the option neid for auto-boot ospf, the following occurs.
A vendor-id-value of 140 is assigned automatically.
Vendor ID is the most significant byte in the NEIP. By default, it is set to 140.
Default ports and default MTUs are set up automatically.
The configuration is set up based on these default values.
If the user has set additional options for auto-boot ospf, the following occurs:
These values are used to generate the configuration as described in CLI generation of the loopback address and router ID from auto-boot ospf and its options.
Vendor ID is the most significant byte in the NEIP. By default, it is set to 140.
Either all or some of these options can be set. The options that are not set remain at their default values.
These configured options generate the configuration as described in CLI generation of the loopback address and router ID from auto-boot ospf and its options.
The configure system network-element-discovery generate-traps option should always be disabled because this feature applies only to non-aggregation nodes.
This configuration process forces the node to generate its auto-discovery profile and to advertise it through OSPF to the rest of the network.
An aggregation node must be configured manually and cannot be auto-discovered. This is because the node is connected to the NMS and must have an SNMP configuration to connect to the NMS.
The node can be configured to generate the NEIP automatically using configuration under the NE profile:
config>system>network-element-discovery
generate traps
profile <profile name>
neid <value>
neip ipv4 auto-generate or
neip ipv6 auto-generateIf auto-boot ospf vendor-id 140 or configure system network-element-discovery profile profile-name vendor-id Nokia is set, the IP address is 140.9.c.d.
When the NMS has discovered the nodes, the NMS or the user can SSH to the node and clear the auto-boot ospf flag manually. In addition, the following operational guidelines apply:
After node discovery, all management and operations are performed through Telnet, SSH, or SNMP.
The NE profile and management VPRN and its configuration that was autogenerated (as described in Autogenerate configuration) are not deleted, unless explicitly deleted by the user. These are valid configurations generated automatically during auto-provisioning. They should perform the following actions to manage these valid, autogenerated configuration.
Execute an admin save to save these configurations in the configuration file. If a previous configuration file exists, the existing configuration file is backed up and a new configuration file with the current configuration is saved on the compact flash (CF).
Run the already existing configuration file. The management VPRN configuration should not overlap with the existing configuration file that is being executed.