bbxie Thu, 09/11/2008 - 19:34
User Badges:
  • Silver, 250 points or more

The service-port interface is reserved for out-of-band management of the controller and

system recovery and maintenance in the event of a network failure. It is also the only port that is active when the controller is in boot mode. WiSM use the service port for internal protocol communication between the

controllers and the Supervisor 720. For example, if you want to use "session slot x proc 1" to access WiSM's CLI through sup720, you have to enable a service VLAN which is local to the chassis and is used for

communication between Cisco WiSM and Catalyst Supervisor 720 over a Gigabit Interface on the Supervisor and a service port in the Cisco WiSM. See following link for more detail:

mmelbourne Fri, 12/05/2008 - 11:12
User Badges:
  • Silver, 250 points or more

Can the service-port interface be placed in its own VRF if it's only used for intra-chassis communication between the Sup720 and the WiSM(s)?

gamccall Sat, 12/06/2008 - 07:21
User Badges:
  • Silver, 250 points or more

It's not "only" used for intra-chassis communication - or at least, it doesn't have to be. Although no default gateway can be assigned on the service port interface, so it has no way to get off-subnet, you can certainly spread that vlan around as far as you want and communicate directly with the wism from your desk or wherever the service vlan is trunked to.

No idea on your VRF question, though.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode