The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Guru has already answered what's different, but to clarify, an Avaya phone can work on tagged or non-tagged VLANs. When working with tagged frames, it needs to know what the expected tag will be.
When you connect your Avaya phone to your first port configuration, and it works, it then expects VoIP traffic to be tagged with VLAN 18. If frames are not so tagged, it will ignore the frame (which is why it will ignore the non-tagged port data traffic on VLAN 16).
If you connect the same Avaya phone to your second port configuration, the Avaya phone will still ignore the non-tagged frames, even though they are VoIP frames. I.e. your Avaya phone's configuration needs to be changed to accept VoIP frames as non-tagged.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...