Chapter 40
More About....
Reasons Why an ATM Interface or Subinterface
Configuration May Be Read-Only
OL-4015-12
Reasons Why an ATM Interface or Subinterface Configuration May Be Read-Only
The interface is configured with the encapsulation frame-relay command
•
with an IP address on the main interface.
The interface encapsulation is not "hdlc," "ppp," or "frame-relay."
•
The encapsulation frame-relay ... command contains the mfr ... option.
•
The interface is configured with the encapsulation ppp command, but the
•
PPP configuration contains unsupported commands.
The interface is configured with the encapsulation frame-relay and
•
frame-relay map ... commands.
The main interface is configured with the encapsulation frame-relay and
•
frame-relay interface-dlci ... commands.
The main interface is configured with the encapsulation frame-relay
•
command and the subinterface is configured with the frame-relay
priority-dlci-group ... command.
The subinterface is configured with the interface-dlci ... command that
•
contains any of the keywords "ppp," "protocol," or "switched."
The subinterface type is "multipoint," instead of "point-to-point."
•
The subinterface is configured with any encapsulation other than
•
"frame-relay."
A previously configured ATM interface or subinterface will be read-only and will
not be configurable in the following cases:
It has a
PVC
with the dialer pool-member command.
•
It has a PVC in which the protocol specified in the protocol command is not
•
ip.
It has a PVC with multiple protocol ip commands.
•
The encapsulation on the PVC is neither "aal5mux," nor "aal5snap."
•
If the encapsulation protocol on aal5mux is not "ip."
•
If the IP Address is not configured on the PVC in the protocol ip command.
•
Cisco Router and Security Device Manager 2.5 User's Guide
40-25