Admin Guide

If you want out-of-band management, Avaya recommends that you define a specific static route in
the Management Router VRF to the IP subnet where your management application resides.
When you specify a static route in the Management Router VRF, it enables the client management
applications originating from the switch to perform out-of-band management without affecting in-
band management. This enables in-band management applications to operate in the Global Router
VRF.
Non-virtualized client management applications originating from the switch, such as Telnet, SSH,
and FTP, follow the behavior listed below:
1. Look at the Management Router VRF route table
2. If no route is found, the applications will proceed to look in the Global Router VRF table
Non-virtualized client management applications include:
• DHCP Relay
• DNS
• FTP client with the copy command
• IPFIX
• NTP
• rlogin
• RADIUS authentication and accounting
• SSH
• SNMP clients in the form of traps
• SYSLOG
• TACACS+
• Telnet
• TFTP client
For management applications that originate outside the switch, the initial incoming packets establish
a VRF context that limits the return path to the same VRF context.
Virtualized management applications
Virtualized management applications, such as ping and traceroute, operate using the specified VRF
context. To operate ping or traceroute you must specify the desired VRF context. If not specified,
ping defaults to the Global Router VRF. For example, if you want to ping a device through the out-
of-band management port you must select the Management Router VRF.
VSP-8284:1(config)#ping 192.0.2.1 vrf MgmtRouter
192.0.2.1 is alive
Software lock-up detection
The software lock-up detect feature monitors processes on the CPU to limit situations where the
device stops functioning because of a software process issue. Monitored issues include
• software that enters a dead-lock state
Chassis operations
January 2017 Administering Avaya VSP 7200 Series and 8000 Series 68
Comments on this document? [e-mail]