Cisco Cisco Transport Manager 9.1 Technical References
6
Cisco Transport Manager Release 9.1 ML Provisioning Methodology
OL-19365-01
CLI Configuration Details
Caution
Do not remove any of the information from the barebone file provided by CTM. You can customize the
username and password, but do not remove them; the username cannot be blank. Do not add the
enable password <password> command, because CTM cannot interactively enable a password.
username and password, but do not remove them; the username cannot be blank. Do not add the
enable password <password> command, because CTM cannot interactively enable a password.
Reset the ML-series card after loading the barebone file and wait for 5 minutes before provisioning
topologies and services. The login and password are reported in the Control Panel window. You can
create other profiles on ML-series cards by using the IOS Users table (available under Administration >
CTC-Based NEs > IOS Users Table).
topologies and services. The login and password are reported in the Control Panel window. You can
create other profiles on ML-series cards by using the IOS Users table (available under Administration >
CTC-Based NEs > IOS Users Table).
After entering command-line interface (CLI) commands through the Telnet session, CTM issues a write
or copy run start command to write the Cisco IOS configuration file to the Timing, Communications
and Control (TCC) flash. When the Cisco IOS configuration file is written to the TCC flash (by CTM or
by another user), CTM is notified. To verify that CTM has been notified, enter the write command after
any CLI change.
or copy run start command to write the Cisco IOS configuration file to the Timing, Communications
and Control (TCC) flash. When the Cisco IOS configuration file is written to the TCC flash (by CTM or
by another user), CTM is notified. To verify that CTM has been notified, enter the write command after
any CLI change.
CTM provides a GUI wizard to facilitate provisioning of L2 topologies and related L1 circuits. See the
section “Provisioning Data Services” in Chapter 7, “Provisioning Services and Connections” in the
section “Provisioning Data Services” in Chapter 7, “Provisioning Services and Connections” in the
. Create an RPR or point-to-point topology involving
some of the ML-series cards in the network. Based on the L2 topology circuit type and size that you
specify, CTM creates related L1 circuits and installs a base card configuration on each ML-series card
in the RPR ring.
specify, CTM creates related L1 circuits and installs a base card configuration on each ML-series card
in the RPR ring.
The Create Layer 2 Service wizard guides you through the VLAN creation. There is no CLI to create a
circuit VLAN. An RPR supports from 1 to 4095 VLANs, and these VLANs are enabled at all times. All
that is required is to configure the endpoint to connect a ring VLAN to a port VLAN that is either an
Ethernet port or a port channel. Only ML devices are supported on an RPR.
circuit VLAN. An RPR supports from 1 to 4095 VLANs, and these VLANs are enabled at all times. All
that is required is to configure the endpoint to connect a ring VLAN to a port VLAN that is either an
Ethernet port or a port channel. Only ML devices are supported on an RPR.
Point-to-point topologies are supported for ML-ML, ML-G1000, ML-OC, and ML-CE cards.
Point-to-point topology creation is similar to RPR creation in that based on the L2 topology circuit type
and size that you specify, CTM creates related L1 circuits and installs a base card configuration on each
ML-series card in the point-to-point topology.
Point-to-point topology creation is similar to RPR creation in that based on the L2 topology circuit type
and size that you specify, CTM creates related L1 circuits and installs a base card configuration on each
ML-series card in the point-to-point topology.
Note
To remove NEs from an L2 topology, mark the NEs Out of Service, and wait an appropriate amount of
time for the L2 topology and corresponding links to be automatically deleted. Once automatic deletion
is confirmed, delete the NEs.
time for the L2 topology and corresponding links to be automatically deleted. Once automatic deletion
is confirmed, delete the NEs.
CLI Configuration Details
Note the following CLI conventions:
•
Notes are reported within brackets (
[ ]
). For example:
[notes]
•
Optional commands or parameters are reported within brackets ( [ ] ). For example:
[match any]
•
Configurable parameters are reported within left and right angle brackets (< >). For example:
<parameter>