I had saw some discuss in other forum said that a voice vlan port in 3550 must be a trunk port, and the data traffic vlan should be the native vlan of the trunk. But some body that the port need not be a trunk. Also the doc of 3550 does not say that the port must be a trunk. And I tried to use command "switchport mode access" "switchport access vlan x" "switchport voice vlan y" in a same port and there is no error. but at that time when I try to use command "show vlan" to verify the config, the display just showed that the port is in vlan x. Is there any body knows the answer? And can I use "switchport mode access" in a voice vlan port? Thank You!
I've heard that Cisco phones can act as a mini-switch, taking an ethernet connection from the network, and providing an ethernet connection to the desktop. This allows both voice and data to ride the same network connection. The way that the phone differentiates between voice and data is by accepting a trunk from the network, switching data from the data VLAN to the data port, and keeping traffic in the voice VLAN for itself. This would only be necessary if your VOIP design includes separate network lines for voice and data.
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 ...