The first thing that jumps out at me is that you appear to be shaping everything to 4 Mbps. I imagine that the rate changes on routers/sites with different circuit speeds, but you generally want to avoid shaping when dealing with latency-sensitive applications like VoIP and RDP as it can cause excessive buffering and jitter during periods of congestion.
To answer your questions:
RDP traffic should get up to the 25% of the remaining bandwidth. Where the already reserved bandwidth is the 35% ( class-default gets 25% by default and EF get 10% ). So, if i'm right, you assigned ~665Kbps to RDP. Anyway you should check if you're dropping packets issuing the command below:
show policy-map <your wan interface&...
I don't know how to show it in the CLI, it's not in the output of show interfaces verbose or show port-statistics afaik...
Another option could be to query it using SNMP. Avaya supports the IF-MIB, and the ifTable entries contain an ifLastChange value (.18.104.22.168.22.214.171.124.1.9):
The value of sysUpTime at the time the interface entered its current
If the huntstop attribute is set, an incoming call does not roll over (hunt) to another ephone-dn when the called ephone-dn is busy or does not answer and a hunting strategy has been established that includes this ephone-dn.
When the no huntstop command is used on the ephone-dn, the call would ring on the first ephone-dn and go through any hunting defined ...
The Telco still has the numbers associated with your PRI trunk group. Calls from other locations will be routed to analog lines, however when you call out on your PRI the 5ESS switch bounces the call back down the trunk group as a DID. The Telco needs to remove the numbers from the DID list on their switch.
This type of thing is very common actually. C/O ...
The only way to backup the configuration is with CLI commands. The switch has no "cron" capability. And as I recall, v5 software doesn't have an ASCII configuration -- tftp gives you a binary blob. show running-config will provide a text configuration, but v5 is rather dumb and includes a mountain of defaults.
You'll need an external script to telnet into ...
According to the Installation Manual, only USB 1.1 and USB 2.0 are supported, along with FAT and FAT32 file systems. If I were you, I'd try to find a USB 2.0 2-4 GB stick and format it with FAT32.
The switches feature a Universal Serial Bus (USB) port on the front
panel. Switch administrators can use the USB port to perform tasks,
previously performed ...
You need to at least take a look at the Cisco configs - if they use RPVST+ and the Avayas can't, the protocol must be changed to something both sides support - MSTP or RSTP. RPVST does not interoperate with RSTP/MSTP when using VLAN trunking. Without any config on the Cisco side ("Unman"?) it won't ever work.
If you can't get either RPVST or R/MSTP on all ...
1) Enable STP on your switches
2) Access cisco SWs and check:
if STP is enabled and if it is compatible.
Check if portfast is enabled and disable it on trunk interfaces
Disable spanning tree bpdufilter on trunk interfaces
3) Try to bundle the links between Avaya and Cisco SW
I don't know about the 4900, but on the 5000 (5xxx) line I use the following:
interface FastEthernet ALL
spanning-tree rstp port 21-22 learning disable
(21 is a cablemodem, 22 is the router)
STP will show the ports as Discarding, but they aren't:
troz-5510-1#show spanning-tree rstp port role 21-22
Port Role State STP Status Oper ...
First, enable lldp globally:
Then also configre lldp on each interface. The native vlan should be vlan 1 (data) and the voice vlan should be 2, like this:
switchport access vlan 1
switchport mode access
switchport voice vlan 2
ip dhcp relay information check-reply