ccm -> 6513 -> fiber -> 6509All set to run on VLAN 100. In Bldg A, vlan 100 is routed, ip address 10.100.1.1. CCM server in Bldg A is 10.100.1.2.In Bldg B, connected to Bldg A via fiber trunk, phones will not pick up DHCP config.
We've upgraded from CCM 3.14b to 3.3. After the upgrade, we lost all DHCP settings. DHCP configuration has been re-inserted, but we can't get the gateway to register or show it's IP address, although DHCP Manager shows that the gateway HAS taken an ...
Yes, we currently have vlan 100 set aside for voice. Vlan 100 will come up in building B, but when we put an IP on it to try to route, we can't ping Vlan 100 in building A. Using the default Vlan 1 as native.
No, as a matter of fact, none of the PCs we tried to put on VLANs originating in Bldg A seem to be working. The only difference is that we're using dot1q to trunk over here. Our other sites aren't having any problems. Could the dot1q trunk somehow be...
