Telnet, HTTP, and SSH limitations and considerations

Telnet, HTTP, and SSH limitations and considerations are as follows:

• By default, SSH and Telnet services are associated and started on mgmt-vrf and default-vrf.
• You cannot remove mgmt-vrf from the SSH and Telnet services.
• Telnet and SSH server can be enabled on a maximum number of 32 VRFs.
• SSH and Telnet Services started on VRF context is applicable for both IPv4 and IPv6 addresses.
• A maximum of 32 user logins are allowed in the device. These sessions are a cumulative count of login sessions through SSH and Telnet across all the configured VRFs.
• Inter-VRF route leaking is not supported for SSH, HTTP, HTTPS, and Telnet. When you try to use any of these services to access a leaked VRF (user-vrf), the connection is refused. In addition, the access service ceases to function correctly on the local VRF (mgmt-vrf) and you must restart it; for example, to restart the SSH service on the local VRF, run the ssh server restart command.