In a Virtual Circuit Network how does a packet gets a VCI ? I read in Data Communication and Networking book by B.A.Forouzan that a packet with a VCI comes at a switch but there is no mention on how or who gives this VCI to
the packet. I have also read that VCI gets changed on passing through the
switch ? How is it done ? I am confused . Please help .
Virtual Circuit Identifier – Understanding VCI
switchvirtual
Related Solutions
In my opinion, pyatka's solution looks like overkill. I like the hub-and-spoke topology though. Your initial topology is redundant, but leaves you highly dependent on Spanning Tree being configured and working properly in order to prevent network loops.
I don't think you need IP's on the inter-switch links. Simply uplink each access switch (PoE SW1, PoE SW2, and SW3 in the graphic) with your new "core," SW 4, with trunk ports with the default VLAN allow settings which allow all VLAN traffic.
Each of the switches can have a port-by-port vlan assignment based on need. All the vlan routing is done on SW4. This means that SW4 will be the default gateway for each VLAN. For example on the user VLAN 20, your hosts will be configured with default gateway of 10.1.1.254 and then on SW2: (this is how on a Cisco IOS switch, check you HP documentation for exact syntax):
SW4# vlan 20
description users
ip address 10.1.1.254 255.255.255.0
ip helper-address X.X.X.X <- DHCP server, if present
SW4 will also then have a default route for 0.0.0.0 that sends outbound traffic out G1/1/4 to the ASA.
Use copper (or fiber if >100M) GBICs for your trunk ports from the access switches to SW4. Then you can still have 24 Ethernet ports on SW4 for end devices.
Obviously, you manage the switches on a dedicated management VLAN.
I think this is a setup that gives you the most flexibility and ease of management.
Chime in if you need more details on switch configuration options.
Great topic. I'd like to preface my answers with some relevant information, then answer your questions as you've asked. "Roaming" is defined as a wireless client migrating from one access point to another. "Seamless" roaming (aka Fast Roaming, aka Zero Handoff, aka IEEE 802.11r) is defined as a wireless client migrating from one base station to another in a fast, seamless, and "secure" manner.
Now to your questions. You asked, "I expect that somehow the new AP must inform the old one the station has roamed successfully and I suspect it must be done with packets sent through the switch. I really wanted to know: How It's done in practice?". Answer: The new AP does not inform the old ap that the station has roamed successfully. In fact, the two access points do not communicate to eachother at all. Even if they were the same model, they don't communicate to eachother. A wireless network designed as described above is not capable of "fast roaming", just "roaming". A real-world test to prove this to yourself is to connect a wireless VOIP phone to the wireless network, then have a phone conversation on it while roaming. You will hear a signifigant interruption in your conversation. Fast roaming would be achieved with another wireless design using a wireless controller (or a bridge). But your question is, "How is it done in practice" ("it" being how the communication occurs for a successful wireless client migration from one ap to another). Here's how it happens in the network you have designed, which is a normal SOHO network. The client is already connected to an access point. As it physically moves, the client wirelessly probes and finds that another access point also has the BSSID it uses AND has a stronger wireless signal (aka RSSI value) than the one it's currently connected to. Before we continue, let's state one fact. A wireless client can only be associated to one access point at a time. So knowing this, it must "disassociate" from the one it's connected to now before it can "associate" to the stronger one. So the wireless client sends it's current access point a "disassociation request" (aka Disassociation Frame) and disconnects from it. Then, the wireless client connects to the new access point by going through its association and authentication process. Once the wireless client is accepted onto the new access point, that access point communicates to the switch that the mac address can now be found on this switchport. The switch updates its mac address table and moves the wireless client's mac from the old access point's switchport (in the table) to the new switchport belonging to the new ap. At this point, the wireless client begins network communication. All of that was done and the two ap's did not communicate to eachother at all.
Your second question is: (translated) What would those packets look like? Answer: On your wireless client, load the latest version of Wireshark and begin a packet capture before you roam. After you roam, stop the capture. You can analyze your traffic to whatever degree you are comfortable with. NOTE: It would be best to make sure you have the latest wireless "driver" on your device first. You mentioned that you tried sniffing on the switch and saw nothing. You now know that to see the migration, you need to sniff on your wlan adapter.
Your last question is: "I read a CISCO networking book about this topic, but It only contains a recommendation about this process, and It says implementation depends on the manufacturer. But what if the APs made by different manufacturer?". Answer: Cisco is correct. The implementation does depend on the manufacturer. Each manufacturer thinks they have a better way for a wireless access point to handle clients. As such, they program their devices in their engineering vision. So if the ap's are made by a different manufacturer, that's OK. Here's why. The access points themselves do not have discussions with eachother in any way, no matter if they're "autonomous ap's" (like the ones you setup in your network) or "thin ap's" that are directed by a controller. So in your scenario, having two different ap manufacturer's is OK because both MUST follow IEEE standards when communicating with the wireless client(s) and the switch.
SOURCES CITED:
WIFI ROAMING ANALYSIS: http://www.revolutionwifi.net/revolutionwifi/2011/12/wi-fi-roaming-analysis-part-1.html
802.11 ASSOCIATION PROCESS EXPLAINED: https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/802.11_Association_process_explained
Best Answer
The Virtual Circuit Identifier (VCI) is used for reliably transferring packets by L2/L3 virtual circuits and allows higher level protocols to avoid dealing with the division of data into segments, packets, or frames.
The VCI is added by the intermediate routers/switches running protocols such as X.25, Frame Relay, Asynchronous Transfer Mode (ATM), GPRS, Multiprotocol Label Switching etc. Less overhead is required, since the packets are not routed individually and complete addressing information is not provided in the header of each data packet. Only a small virtual channel identifier (VCI) is required in each packet. Routing information is only transferred to the network nodes during the connection establishment phase.
How it works differs protocol to protocol. Read this link to better understand how VCI changes at every hop and what if the network routers doesn't support any such protocol.
At transport layer TCP and SCTP are responsible for providing virtual Circuits.