LSB in two switch 6500 series
i need to configure one lsb virtual address in two switchs 6500, it is for a server farm backup and they might respond to the same IP address.
check out the following link for configuring virtual address on catalyst 6500 series :
http://www.cisco.com/en/US/products/hw/switches/ps708/products_installation_and_configuration_guide_chapter09186a00801c589b.html
Similar Messages
-
How to remove the WiSM2 from the Catalyst 6500 series switch?
Hello, can you explain to me how to safely remove the WiSM2 from the Catalyst 6500 series switch?
According to the documentation "Catalyst 6500 Series Wireless Services Module 2 Installation and Verification Note":
To remove the WiSM2, perform these steps:
Step1 Shut down the module by one of these methods:
In privileged mode from the router prompt, enter the hw-mod module mod shutdown command. NoteIf you enter this command to shut down the module, you must enter the following commands in global configuration mode to restart (power down, and then power up) the module:
Router# no power enable module modRouter# power enable module mod
If the module does not respond to any commands, press the SHUTDOWN button located on the front panel of the module.
Step2 Verify that the WiSM2 shuts down. Do not remove the module from the switch until the POWER LEDis off.
But, in the case of Step1 (1st methods) I do not see a option "shutdown" in the command "hw-mod module 3"...
All I prompted to enter is:
c6500#hw-module module 3 ?
boot Specify boot options for the module through Power Management Bus control register
reset Reset specified component
simulate Simulate options for the module
Is it hidden options? IOS version of c6500 is 12.2(33)SXJ1
In the case of Step2 (2nd methods) there is not any button on the front panel of the module?
And yet, it is better to remove the module configuration manually or use the command module clear-config prior to removing the module?Good catch.
Which one is true, will get back to you on this if i've something soon.
http://www.cisco.com/en/US/docs/wireless/module/wism2/installation/note/WiSM_2.html#wp34727
The above link is procedure to remove wism2. This procedure doesn’t look like wism2 is hot swapable.
http://www.cisco.com/en/US/docs/wireless/module/wism2/installation/note/WiSM_2.html#wp34621
All modules, including the supervisor engine (if you have redundant supervisor engines), support hot swapping. You can add, replace, or remove modules without interrupting the system power or causing other software or interfaces to shut down. For more information about hot-swapping modules, see the Catalyst 6500 Series Switch Module Installation Guide. -
APs unable to receive IP address from DHCP (core 6500 series switch)
Dear Friends,
a week ago I had stable wireless network APs were getting IPS from 6500 series switch (DHCP) but unfortunately some WISM got rebooted and now APs are unable to receive IP address from Core 6500 DHCP, to cater this issue I have another DHCP server configured on windows 2008 i created another subnet and and put APs in that vlan now all APs are are successfully receiving IPS from windows DHCP server I don't know why APs are not able to receive IPs from core 6500 series DHCP.
please advice
Thanks
FaysalThanks george for stepping up here is DHCP config
ip dhcp excluded-address 10.10.30.1 10.10.30.20
ip dhcp excluded-address 10.10.8.1 10.10.8.10
ip dhcp excluded-address 192.168.10.1 192.168.10.5
ip dhcp excluded-address 10.9.20.1 10.9.20.30
ip dhcp pool vlan_30
network 10.10.30.0 255.255.254.0
default-router 10.10.30.1
option 60 ascii """"""""""""""""""""""""CiscoAPc1250""""""""""""""""""""""""
option 43 hex f110.0a0a.1e0b.0a0a.1e0d.0a0a.1e0f.0a0a.1e11
dns-server 10.10.2.11
lease infinite
ip dhcp pool WiSM1_SP
network 192.168.10.0 255.255.255.248
default-router 192.168.10.1 -
Multicast in 6500 series switch
We have one customer who have config Ipsec over GRE end to end for all remote locations.Now customer want to upload large file to all remote locations.So we have to config multicast in our backbone network.
We have 6500 Series Switch thorough which all routing is done.But how multicast traffic will flow thorough IPsec tunnel.Is any one having such case pls let me know.
TIA
Regards
SAMcheck out the following link Multicast over IPsec VPN Design Guide, this should help :
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns656/c649/cdccont_0900aecd80402f07.pdf -
Maximum 29XX switches on a 6500 series
Hello,
is there a recommended maximum of user ports i can connect directly to a 6500 series core switch?
So I have a situation with about 80 24-ports switches (in stacks of 2 or 3) connected with fiber to the core switch. Now one of the network managers states we need a distribution layer cause performance in the 6500 will drop. Reason for this is that the 29XX series switches do not support layer 3.
Is this correct? And does the added layer 3 functionality in a (extra) distribution layer increase performance in the core? Even though almost all traffic is user - server traffic and servers are connected to core?
Anyone know? THanks!Hi Friend,
Which sup engine do you have and is there any switch fabric module you are running. Cat6500' are cross-fabric chassis which gives 32GBPS backplane switch capacity bedefualt. If you have SFM (switch fabric module) installed then it will give 256 GBPS of backplane capacity.
If you are running Sup720, you have 720 GBPS backplane capacity and you will see a greater performance by cat65K.
If you dont have SFM or sup 720, then yes with direct access switches uplink to Core might slow down the performance of the core switch.
If that's the case I would suggest to got for hierarchical design and add another layer of the architecture i.e distribution layer.Now what you can do with this additional layer, is that you can uplink your access layer to it, have your inter-vlan routing done on thius layer, have to access control policy deployed at this layer.
This addtion layer and the above functionalities will off load the processing of traffic at core and core will be efficient enough to process the traffic as fast as it can. This is a abosultely correct approach.
Please, write back for any qurstions.
HTH, Please rate if it does.
-amit singh -
Hi All,
I am having issue specifally doing QOS configuration on 6503 or 6524 or 6509 switches. I am unable to match any EF(voice) traffic for eompls(vlan based) on 6503 cisco switch. If i use any other router as 2811 or 2821 my QOS configuration works perfect but if i put 6503 as PE2 it does not work.i am using vlan based eompls.
Below is the scenario & configuration which i am having issue.
CE1(2821 router)(dot1Q)--------->PE1(2821 router)------->P(6524 switch)-------->PE2(6503 switch)------->(dot1Q)(2821 switch)CE2.
On CE1 i can match ip-precedence 5 traffic and mark that traffic to cos5 on outbound port.On PE1 i can match cos5 packet and mark with mpls exp top5 on inbound port, on outbound port i can match mpls exp 5.
On PE2(6503) i am unable to match that mpls exp5 packet on inbound port. none of the configuration worked on 6500 series switches with mls qos, ,mls qos trust dscp,mls qos trust cos etc. Although i can match cos5 traffic on CE2 on inbound interface.i can not match mpls exp 5 traffic on 6503 and all i can see traffic as default-class on 6503 switch. I tried many things and many configurations on 6503 but nothing worked.If i put 2821 router as PE2 instead of 6503 my qos configuration works. but why if i put 6503 my same qos configuration does not work?
---match means=classification or classify
Can anyone tell me how qos works on 6500 series switches or where i am having issue in my scenario.
i am using this ios on 6503: s72033-advipservicesk9_wan-mz.122-33.SXI3.bin.
below r my questions for 6503 qos:
1.do i need to use some other map tables,am i using correct map tables on 6503 as cos-dscp,dscp-cos,exp-dscp etc.
2.any other configutaion of qos needed on 6503?
3.i am unable to match anything on outbound port of 6503.
4.on 6503 i am using sup720 and PFC3BXL.any specific configuration needed for PFC3bxl.
5. 6503 not allowing me to match qos-group on inbound interface, not allowing me to set cos5 on outbound interface. not allowing me to set cos5 as an inbound interface.
CE1(2821) config:
class-map match-any EF
match ip precedence 5
class-map match-any data
match ip precedence 3
policy-map ip2mpls
class EF
set cos 5
class data
set cos 3
interface FastEthernet0/0
no ip address
duplex auto
speed auto
interface FastEthernet0/0.455
encapsulation dot1Q 455
ip address 172.16.15.1 255.255.255.252
service-policy output EF
PE1(2821) config:
mls qos map cos-dscp 0 8 16 24 32 40 48 56
class-map match-all exp_3
match mpls experimental topmost 3
class-map match-all mpls_exp
match mpls experimental topmost 5
class-map match-any cos3
match cos 3
class-map match-any LOO1
match cos 5
policy-map EF
class LOO1
set mpls experimental imposition 5
class cos3
set mpls experimental imposition 3
policy-map QOS_G_5
class mpls_exp
priority
class exp_3
bandwidth 500
interface Loopback0
ip address 3.3.3.3 255.255.255.255
interface FastEthernet0/0
ip address 192.168.23.2 255.255.255.0
ip ospf network point-to-point
duplex auto
speed auto
mpls ip
service-policy output QOS_G_5
interface FastEthernet0/1.455
encapsulation dot1Q 455
xconnect 5.5.5.5 455 encapsulation mpls
service-policy input EF
PE2(6503 qos):
R1#show module
Mod Ports Card Type Model Serial No.
1 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL09401U2L
2 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL114247YN
3 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAL0712AM69
4 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL10019J4N
5 2 Supervisor Engine 720 (Hot) WS-SUP720-3BXL SAD102805VM
6 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD0846060F
Mod Sub-Module Model Serial Hw Status
1 Distributed Forwarding Card WS-F6700-DFC3BXL SAD102504EF 5.3 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAD111300PD 3.1 Ok
4 Centralized Forwarding Card WS-F6700-CFC SAL1004BQ2A 2.0 Ok
5 Policy Feature Card 3 WS-F6K-PFC3BXL SAD10270189 1.8 Ok
5 MSFC3 Daughterboard WS-SUP720 SAD102801G5 2.5 Ok
6 Policy Feature Card 3 WS-F6K-PFC3BXL SAL1415FE95 1.11 Ok
6 MSFC3 Daughterboard WS-SUP720 SAD08440794 2.4 Ok
R1#show mls qos maps
Normal Burst Policed-dscp map: (dscp= d1d2)
d1 : d2 0 1 2 3 4 5 6 7 8 9
0 : 01 01 02 03 04 05 06 07 08 09
1 : 10 11 12 13 14 15 16 17 18 19
2 : 20 21 22 23 24 25 26 27 28 29
3 : 30 31 32 33 34 35 36 37 38 39
4 : 40 41 42 43 44 45 01 47 48 49
5 : 50 51 52 53 54 55 56 57 58 59
6 : 60 61 62 63
Maximum Burst Policed-dscp map: (dscp= d1d2)
d1 : d2 0 1 2 3 4 5 6 7 8 9
0 : 00 01 02 03 04 05 06 07 08 09
1 : 10 11 12 13 14 15 16 17 18 19
2 : 20 21 22 23 24 25 26 27 28 29
3 : 30 31 32 33 34 35 36 37 38 39
4 : 40 41 42 43 44 45 46 47 48 49
5 : 50 51 52 53 54 55 56 57 58 59
6 : 60 61 62 63
Dscp-cos map: (dscp= d1d2)
d1 : d2 0 1 2 3 4 5 6 7 8 9
0 : 00 00 00 00 00 00 00 00 01 01
1 : 01 01 01 01 01 01 02 02 02 02
2 : 02 02 02 02 03 03 03 03 03 03
3 : 03 03 04 04 04 04 04 04 04 04
4 : 05 05 05 05 05 05 05 05 06 06
5 : 06 06 06 06 06 06 07 07 07 07
6 : 07 07 07 07
Dscp-exp map: (dscp= d1d2)
d1 : d2 0 1 2 3 4 5 6 7 8 9
0 : 00 00 00 00 00 00 00 00 01 01
1 : 01 01 01 01 01 01 02 02 02 02
2 : 02 02 02 02 03 03 03 03 03 03
3 : 03 03 04 04 04 04 04 04 04 04
4 : 05 05 05 05 05 05 05 05 06 06
5 : 06 06 06 06 06 06 07 07 07 07
6 : 07 07 07 07
Cos-dscp map:
cos: 0 1 2 3 4 5 6 7
dscp: 0 10 18 24 34 46 48 56
IpPrecedence-dscp map:
ipprec: 0 1 2 3 4 5 6 7
dscp: 0 8 16 24 32 40 48 56
Exp-dscp map:
exp: 0 1 2 3 4 5 6 7
dscp: 0 8 16 24 32 40 48 56
mls netflow interface
mls qos map cos-dscp 0 10 18 24 34 46 48 56
mls qos
class-map match-all exp_3
match mpls experimental topmost 3
class-map match-all EXP_5
match mpls experimental topmost 5
class-map match-all QOS_GROUP_5
match qos-group 5
class-map match-all prec5
match ip precedence 5
class-map match-all cos5
match cos 5
policy-map mpls2ip
class QOS_GROUP_5
set cos 5
policy-map IN_FROM_R3
class EXP_5
set qos-group 5
interface Loopback0
ip address 5.5.5.5 255.255.255.255
interface GigabitEthernet2/2
mls qos trust cos
or <------------ (tried both individually but none worked)
mls qos trust dscp
interface GigabitEthernet2/2.455
encapsulation dot1Q 455
xconnect 3.3.3.3 455 encapsulation mpls
service-policy output mpls2ip
interface GigabitEthernet2/1
ip address 192.168.34.4 255.255.255.0
ip ospf network point-to-point
mls qos trust cos
or <------------ (tried both individually but none worked)
mls qos trust dscp
mpls ip
service-policy input IN_FROM_R4
Thanks & regards,
Ahsan RasheedHi All,.
I am still having issue on 6503 or 6524 Cisco Switch.
" Can any one give me any sample of 6524 or 6503 QOS working configuration, i would be really thankful "
As i have mentioned in my prevoius post of configuration of 6503. I am unable to match mpls exp 5 packet on 6503. My qos configuration on PE1(2811 router) is working perfectly. I am unable to classify mpls ex5 or mpls exp3 on 6503 switch. Am i missing something on configuration?
PE2 config:"6503 switch"
class-map match-all mpls_exp
match mpls experimental topmost 5
policy-map EF
class mpls_exp
R!#mls qos
int Gi2/4
service-policy input EF
mls qos trust cos
dscp: 0 10 18 24 34 46 48 56
Exp-dscp map:
exp: 0 1 2 3 4 5 6 7
dscp: 0 10 18 24 34 46 48 56
Thanks,
Ahsan Rasheed -
5508 WLC-6500 Series Switch Etherchannel
Hi,
I have a 5508 controller connected to a 6500 VSS pair. Below is the port channel configuration and port configuration. I am just wondering whether we still have to configure a load balancing method as cisco recommends “port-channel load-balance src-dst-ip” as best practice.
Does this still applicable for 5508 controller-6500 Series uplink as the etherchannel is L2 etherchannel?
Port Channel Config:
interface Port-channel1
description To 5508 WLC
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 9
switchport trunk allowed vlan 10,11,12
switchport mode trunk
mls qos trust dscp
end
Interface Config:
interface GigabitEthernet1/1/42
description To 5508 WLC
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 9
switchport trunk allowed vlan 10,11,12
switchport mode trunk
wrr-queue bandwidth 5 25 70
wrr-queue queue-limit 5 25 40
wrr-queue random-detect min-threshold 1 80 100 100 100 100 100 100 100
wrr-queue random-detect min-threshold 2 80 100 100 100 100 100 100 100
wrr-queue random-detect min-threshold 3 50 60 70 80 90 100 100 100
wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100
wrr-queue random-detect max-threshold 2 100 100 100 100 100 100 100 100
wrr-queue random-detect max-threshold 3 60 70 80 90 100 100 100 100
wrr-queue cos-map 1 1 1
wrr-queue cos-map 2 1 0
wrr-queue cos-map 3 1 4
wrr-queue cos-map 3 2 2
wrr-queue cos-map 3 3 3
wrr-queue cos-map 3 4 6
wrr-queue cos-map 3 5 7
mls qos trust dscp
channel-group 1 mode on
endHello,
Please check to following link regarding load balancing between 5508 and WLC 6500:
http://www.learnios.com/viewtopic.php?f=5&t=34555 -
Can MPLS aware Netflow ver. 9 be enabled on the catalyst switches 6500
HI, I'm working for KOREA TELECOM, and currently providing MPLS VPN.
We're planning to provide our customer with traffic report using NetFlow..
I read some documents which reads Netflow ver.9 can be enabled on Cisco GSR 12000 Series, but no mention about catalyst switches. So, I ' m curious about that Netflow ver 9 can be activated on catalyst 6500 series.. because the point where switch is located already have mpls encapsulated packet ( mpls vpn packet).
Thank you , in advance.NetFlow is now integral to Cisco 6500. A configuration we recommend is as below:
mls netflow // This enables NetFlow on the Supervisor.
mls nde sender version 7
mls aging long 64 // This breaks up long-lived flows into (roughly) one-minute segments.
mls aging normal 32 // This ensures that flows that have finished are exported in a timely manner.
mls flow ip interface-full
mls nde interface
The next two commands will help to enable NetFlow data export for bridged traffic which is optional. You can specify the list of VLANs here to enable bridged traffic.
ip flow ingress layer2-switched vlan
ip flow export layer2-switched vlan
Apart from this, NetFlow has to be enabled on the MSFC using the below commands.
ip flow egress // This command has to be executed on all the L3/VLAN interfaces.
ip flow-export destination {hostname|ip_address} 9996 // The hostname or IP address of the flow server
ip flow-export source {interface} // The interface through which NetFlow packets are exported. eg: Loopback0
ip flow-export version 9
ip flow-cache timeout active 1
snmp-server ifindex persist
The new Cisco Flexible NetFlow actually allows for export of MPLS specific information (I believe it is stack lables) in addition to information on IP Address, port, etc. But you will need a tool that can support these additional fields. Otherwise you can view IP, port, protocol, etc related information from MPLS links.
Regards,
Don Thomas Jacob
ManageEngine NetFlow Analyzer -
Networking Best Practices - Connecting Two Switches
Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
For more details on the difference between Access, General, and Trunk modes, follow this link.
http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
http://support.dell.com/support/edocs/network/
Layer 2
Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
We will use 3 VLANs for the following scenario.
VLAN 1=Management
VLAN 2=Client
VLAN 3=Server
To create these VLANs we do the following commands (VLAN 1 is already created by default)
console(config)# vlan database
console(config-vlan)# VLAN 2
console(config-vlan)# VLAN 3
console(config-vlan)# exit
We can then name the VLANs to help keep things organized.
console(config)# interface vlan 2
console(config-vlan)# name Client
console(config-vlan)# exit
console(config)# interface vlan 3
console(config-vlan)# name Server
console(config-vlan)# exit
Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
For the port e1 that connect the two switches to each other would be configured like this.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3. Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
Layer 3 + Layer 2
Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches. Then we will add to the configuration.
We can assign an IP address to each switch with the following command.
Switch A
console(config)#ip address 172.16.1.1 255.255.255.0
Switch B
console(config)#ip address 172.16.2.1 255.255.255.0
Then we will enable routing only on Switch A
console(config)# ip routing
Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
console(config)# interface vlan 2
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
console(config-if-vlan2)# exit
Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
console(config)# interface vlan 3
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.11
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.11
Default Gateway:172.16.30.1
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.12
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.12
Default Gateway:172.16.30.1
External Connection
At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
console(config)# vlan database
console(config-vlan)# VLAN 7
console(config-vlan)# exit
console(config)# interface vlan 7
console(config-vlan)# name WAN
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
console(config-if-vlan2)# exit
On our router we will assign an IP address of 10.10.10.1
Then place the port connecting the switch and router into access mode for VLAN 7. In this case we use port e4.
console(config)# interface ethernet 1/e4
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 7
console(config-if)# exit
We will then need to put in a default route with the next hop as the router IP address. This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A. Generally adding a static route on most routers is done with the following command:
ip route {Network} {Wildcard Mask} {Next Hop-IP}
In our case here are the 2 static routes we could use.
Ip route 172.16.20.0 0.0.0.255 10.10.10.2
Ip route 172.16.30.0 0.0.0.255 10.10.10.2
The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
Layer 3 + Layer 3
In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
To create this VLAN we will run the following commands on both switch A and B
console(config)# vlan database
console(config-vlan)# vlan 6
console(config-vlan)# exit
console(config)# interface vlan 6
console(config-vlan)# name Connection
console(config-vlan)# exit
On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
console(config-if-vlan2)# exit
On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and B we place the connecting ports into Access mode for VLAN 6.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 6
console(config-if)# exit
We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
We will enable routing on Switch B
console(config)# ip routing
What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
console(config)# interface vlan 4
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
console(config-if-vlan2)# exit
Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
console(config)# interface vlan 5
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
console(config-if-vlan2)# exit
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 4.
IP Address:172.16.40.11
Default Gateway:172.16.40.1
Client connected to access port for VLAN 5.
IP Address:172.16.50.11
Default Gateway:172.16.50.1
The end result should look like this.
Troubleshooting
If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
The external router will also need a path defined back to all networks/VLANs.
To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
console# show interfaces detail ethernet 1/g48
To check routing paths:
console# show ip route
The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
-Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
-Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
-Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
-ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
-ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
-ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
-ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow. -
HIGH CPU IOS REACH 100 % - 6500 Series
Hi, please help us how can we minimize the cpu usage of our 6500 series core switch.. below is the cpu usage and the version.. i think we need upgrade the ios . please teach us detailed steps for opening ticket. thanks. attached here is the cpu ios usage.
CPU PROCESS
91.5% 90.3% 90.3% ios base
Version
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-IPSERVICES_WAN-VM), Version 12.2(18)SXF14
, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Thu 08-May-08 03:25 by kellythw
Image text-base: 0x01020150, data-base: 0x01021000
ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)
BOOTLDR:
XXXXXXXX uptime is 17 hours, 39 minutes
Time since RM-NT3-BB1 switched to active is 17 hours, 39 minutes
System returned to ROM by reload at 21:01:56 GMT Mon May 5 2014 (SP by reload)
System restarted at 21:05:06 GMT Mon May 5 2014
System image file is "sup-bootdisk:s72033-ipservices_wan-vz.122-18.SXF14.bin"
cisco WS-C6506-E (R7000) processor (revision 1.1) with 491520K/32768K bytes of m
emory.
Processor board ID SAL12351U4Q
SR71000 CPU at 600Mhz, Implementation 1284, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
391 Virtual Ethernet/IEEE 802.3 interfaces
146 Gigabit Ethernet/IEEE 802.3 interfaces
1917K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102Sir Navevenk,
Please check bellow thanks.
1. sh proc cpu sorted
XXXXX#sh proc cpu sorted ?
% Unrecognized command
XXXXX#sh proc cpu ?
detailed Show CPU use per process detailed
history Show CPU history in graph format
| Output modifiers
2. sh proc cpu de ios-base | ex 0.0
CPU utilization for five seconds: 37%; one minute: 38%; five minutes: 39%
PID/TID 5Sec 1Min 5Min Process Prio STATE CPU
16408 33.1% 31.4% 31.4% ios-base 1d05h
1 0.2% 0.3% 0.4% 10 Receive 19m12s
3 4.6% 3.7% 3.2% 10 Receive 1h38m
7 5.6% 5.4% 6.0% 21 Intr 9h39m
8 3.0% 1.8% 1.8% 22 Intr 1h10m
12 0.6% 1.1% 2.1% 10 Receive 1h44m
13 5.3% 3.6% 1.4% 10 Receive 1h42m
14 3.6% 3.2% 2.1% 10 Reply 1h36m
15 1.5% 3.2% 1.3% 10 Receive 1h35m
19 6.9% 4.2% 3.5% 10 Receive 1h39m
20 1.8% 3.7% 3.2% 10 Reply 1h43m
Process sbin/ios-base, type IOS, PID = 16408
CPU utilization for five seconds: 14%/6%; one minute: 22%; five minutes: 22%
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
3 1613034 32981487 48 0.39% 0.54% 0.55% 0 Service Task
4 1116381 11672688 95 0.31% 0.43% 0.44% 0 Service Task
17 1079952 702528 1537 0.71% 0.51% 0.44% 0 ARP Input
32 313016 507290 617 0.15% 0.14% 0.14% 0 RPCP Slave
41 549787 59949 9170 0.21% 0.19% 0.21% 0 HC Counter Timer
93 757717 199397 3800 0.21% 0.27% 0.28% 0 Compute load avg
125 1151381 13529847 85 0.15% 0.44% 0.46% 0 ION IP output
126 34179777 23406153 1460 8.00% 13.82% 13.29% 0 IP Input
131 5195876 9372573 554 0.71% 0.64% 1.15% 0 IP NAT Ager
168 3852539 25022469 153 0.95% 1.44% 1.49% 0 Standby (HSRP)
223 3494398 13872600 251 0.95% 1.45% 1.45% 0 Port manager per
3. Sh proc cpu
PID 5Sec 1Min 5Min Process
1 0.0% 0.5% 0.6% kernel
3 0.0% 0.0% 0.0% qdelogger
4 0.0% 0.0% 0.0% devc-pty
5 0.0% 0.0% 0.0% devc-mistral.proc
6 0.0% 0.0% 0.0% pipe
7 0.0% 0.0% 0.0% dumper.proc
4104 0.0% 0.0% 0.0% bflash_driver.proc
12297 0.0% 0.0% 0.0% pcmcia_driver.proc
12298 0.0% 0.0% 0.0% mqueue
12299 0.0% 0.0% 0.0% flashfs_hes.proc
12300 0.0% 0.0% 0.0% dfs_bootdisk.proc
12301 0.0% 0.0% 0.0% ldcache.proc
12302 0.0% 0.0% 0.0% watchdog.proc
12303 0.0% 0.0% 0.0% syslogd.proc
12304 0.0% 0.0% 0.0% name_svr.proc
12305 0.1% 0.0% 0.0% wdsysmon.proc
12306 0.0% 0.0% 0.0% sysmgr.proc
16386 0.0% 0.0% 0.0% chkptd.proc
16403 0.0% 0.0% 0.0% sysmgr.proc
16404 0.0% 0.0% 0.0% syslog_dev.proc
16405 0.0% 0.0% 0.0% itrace_exec.proc
16406 0.0% 0.0% 0.0% packet.proc
16407 0.0% 0.0% 0.0% installer.proc
16408 36.8% 30.7% 30.8% ios-base
16409 0.0% 0.0% 0.0% fh_fd_rf.proc
16410 0.0% 0.0% 0.0% fh_fd_oir.proc
16411 0.0% 0.0% 0.0% fh_fd_cli.proc
16412 0.0% 0.0% 0.0% fh_metric_dir.proc
16413 0.0% 0.0% 0.0% fh_fd_snmp.proc
16414 0.0% 0.0% 0.0% fh_fd_none.proc
16415 0.0% 0.0% 0.0% fh_fd_intf.proc
16416 0.0% 0.0% 0.0% fh_fd_gold.proc
16417 0.0% 0.0% 0.0% fh_fd_counter.proc
16418 0.0% 0.0% 0.0% fh_fd_timer.proc
16419 0.0% 0.0% 0.0% fh_fd_ioswd.proc
16420 0.0% 0.0% 0.0% fh_server.proc
16421 0.0% 0.0% 0.0% fh_policy_dir.proc
16422 0.0% 0.0% 0.0% ipfs_daemon.proc
16423 0.4% 0.4% 0.4% raw_ip.proc
16424 0.0% 0.0% 0.0% inetd.proc
16425 0.1% 0.1% 0.1% tcp.proc
16426 1.2% 1.5% 2.2% udp.proc
16427 0.7% 0.9% 1.1% iprouting.iosproc
16428 0.3% 0.5% 0.5% cdp2.iosproc
4.sh proc cpu detailed 16408
CPU utilization for five seconds: 29%; one minute: 34%; five minutes: 37%
PID/TID 5Sec 1Min 5Min Process Prio STATE CPU
16408 26.2% 27.9% 30.0% ios-base 1d05h
1 0.3% 0.3% 0.4% 10 Receive 19m13s
2 0.0% 0.0% 0.0% 5 Condvar 0.000
3 4.4% 3.2% 3.1% 10 Reply 1h38m
4 0.0% 0.0% 0.9% 10 Receive 1h35m
5 0.0% 0.0% 0.0% 11 Nanosleep 1.456
6 0.4% 1.5% 1.7% 10 Reply 1h32m
7 6.3% 5.7% 5.9% 21 Intr 9h40m
8 1.1% 1.7% 1.8% 22 Intr 1h10m
9 0.0% 0.0% 0.0% 23 Intr 3m14s
10 0.0% 0.0% 0.0% 25 Intr 0.000
11 0.0% 0.0% 0.0% 10 Reply 10.284
12 2.6% 1.4% 1.8% 10 Receive 1h44m
13 0.3% 2.6% 1.9% 10 Receive 1h42m
14 1.9% 2.7% 2.1% 10 Receive 1h36m
15 4.0% 3.6% 2.2% 10 Receive 1h35m
16 0.0% 0.0% 1.1% 10 Receive 1h38m
17 0.0% 0.0% 1.0% 10 Receive 1h33m
18 0.0% 0.0% 0.0% 20 Sigwaitin 0.068
19 4.2% 2.5% 3.0% 10 Receive 1h39m
20 0.7% 2.7% 3.1% 10 Receive 1h43m
Process sbin/ios-base, type IOS, PID = 16408
CPU utilization for five seconds: 16%/7%; one minute: 19%; five minutes: 21%
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
1 264 1931 136 0.00% 0.00% 0.00% 1 Hot Service Task
2 2734366 47825930 57 0.87% 0.93% 1.03% 0 Service Task
3 1613598 32998937 48 0.23% 0.47% 0.53% 0 Service Task
4 1116773 11678121 95 0.15% 0.33% 0.40% 0 Service Task
5 1548 3907 396 0.00% 0.00% 0.00% 0 Chunk Manager
6 0 1 0 0.00% 0.00% 0.00% 0 Connection Mgr
7 68 2013 33 0.00% 0.00% 0.00% 0 DHCPD Timer
8 0 1 0 0.00% 0.00% 0.00% 0 PF Redun ICC Req
9 5296 48248 109 0.00% 0.00% 0.00% 0 Load Meter
10 276 231 1194 0.00% 0.13% 0.05% 1 Virtual Exec
11 820407 55486 14785 0.00% 0.39% 0.31% 0 Check heaps
12 0 1 0 0.00% 0.00% 0.00% 0 Pool Manager
13 0 2 0 0.00% 0.00% 0.00% 0 Timers
14 32864 105392 311 0.00% 0.00% 0.00% 0 EnvMon
15 0 1 0 0.00% 0.00% 0.00% 0 AAA_SERVER_DEADT
16 0 2 0 0.00% 0.00% 0.00% 0 AAA high-capacit
17 1080472 702876 1537 0.23% 0.42% 0.44% 0 ARP Input
18 0 2 0 0.00% 0.00% 0.00% 0 Serial Backgroun
19 935 89 10505 0.00% 0.00% 0.00% 0 Entity MIB API
20 320 24146 13 0.00% 0.00% 0.00% 0 Compute SRP rate
21 0 2 0 0.00% 0.00% 0.00% 0 DDR Timers
22 0 2 0 0.00% 0.00% 0.00% 0 Dialer event
23 0 1 0 0.00% 0.00% 0.00% 0 IFS Agent Manage
24 68 4026 16 0.00% 0.00% 0.00% 0 IPC Dynamic Cach
25 20 49 408 0.00% 0.00% 0.00% 0 PF_Split Sync Pr
26 0 1 0 0.00% 0.00% 0.00% 0 IPC Punt Process
27 4840 238240 20 0.00% 0.00% 0.00% 0 IPC Periodic Tim
28 2792 238239 11 0.00% 0.00% 0.00% 0 IPC Deferred Por
29 149640 419666 356 0.00% 0.04% 0.05% 0 IPC Seat Manager
30 0 1 0 0.00% 0.00% 0.00% 0 IPC Stdby Update
31 24 198 121 0.00% 0.00% 0.00% 0 EEM ED Syslog
32 313156 507543 617 0.31% 0.13% 0.13% 0 RPCP Slave
33 81072 162088 500 0.07% 0.03% 0.01% 0 RPCP Slave
34 14900 34458 432 0.00% 0.00% 0.00% 0 RPCP Slave
35 5000 12573 397 0.00% 0.00% 0.00% 0 RPCP Slave
36 1320 3539 372 0.00% 0.00% 0.00% 0 RPCP Slave
37 0 1 0 0.00% 0.00% 0.00% 0 Snmp ICC Process
38 4 83 48 0.00% 0.00% 0.00% 0 Cat6k SNMP
39 59 461 127 0.00% 0.00% 0.00% 0 Cat6k SNMP Trap
40 0 1 0 0.00% 0.00% 0.00% 0 SERIAL A'detect
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
41 550027 59977 9170 0.21% 0.19% 0.21% 0 HC Counter Timer
42 4412 238241 18 0.00% 0.00% 0.00% 0 Dynamic ARP Insp
43 68 462 147 0.00% 0.00% 0.00% 0 rf proxy rp agen
44 16 11 1454 0.00% 0.00% 0.00% 0 NSP:IPC Task
45 51664 499624 103 0.07% 0.01% 0.00% 0 Net Critical I/O
46 0 1 0 0.00% 0.00% 0.00% 0 Critical Bkgnd
47 45528 562754 80 0.00% 0.00% 0.00% 0 Net Background
48 32 132 242 0.00% 0.00% 0.00% 0 Logger
49 6392 238199 26 0.00% 0.00% 0.00% 0 TTY Background
50 52012 267518 194 0.00% 0.00% 0.00% 0 Per-Second Jobs
51 84607 6042 14003 0.00% 0.02% 0.00% 0 Per-minute Jobs
52 8 11 727 0.00% 0.00% 0.00% 0 RPC Sync
53 0 3 0 0.00% 0.00% 0.00% 0 RPC rpc-slave-15
54 0 1 0 0.00% 0.00% 0.00% 0 PF Sync process
55 0 2 0 0.00% 0.00% 0.00% 0 SCP Multicast
56 0 7 0 0.00% 0.00% 0.00% 0 draco-oir-proces
57 396 896 441 0.00% 0.00% 0.00% 0 RPCP Slave
58 0 1 0 0.00% 0.00% 0.00% 0 EOBC Monitor Pro
59 76 513 148 0.00% 0.00% 0.00% 0 Env action
60 4 330 12 0.00% 0.00% 0.00% 0 svclc
61 0 5 0 0.00% 0.00% 0.00% 0 RPC rf_rfmib_not
62 885605 1935944 457 0.00% 0.00% 0.00% 0 Net Input
63 0 5 0 0.00% 0.00% 0.00% 0 MWAM CONFIG ON S
64 12 407 29 0.00% 0.00% 0.00% 0 itasca
65 0 2 0 0.00% 0.00% 0.00% 0 Flash ICC Server
66 0 2 0 0.00% 0.00% 0.00% 0 Const ICC reques
67 0 1 0 0.00% 0.00% 0.00% 0 Const ICC event
68 0 1 0 0.00% 0.00% 0.00% 0 Const ICC except
69 0 1 0 0.00% 0.00% 0.00% 0 ICC Local Reques
70 416 3328 125 0.00% 0.00% 0.00% 0 ICC Async mcast
71 0 1 0 0.00% 0.00% 0.00% 0 ICC_REQ Debug Pr
72 0 1 0 0.00% 0.00% 0.00% 0 ICC FC Process
73 0 1 0 0.00% 0.00% 0.00% 0 ICC FC Test Send
74 0 1 0 0.00% 0.00% 0.00% 0 ICC FC Test Low
75 0 1 0 0.00% 0.00% 0.00% 0 IfIndex Bulk Syn
76 0 1 0 0.00% 0.00% 0.00% 0 CWRP SPA TSM HA
77 0 1 0 0.00% 0.00% 0.00% 0 CWAN APS HA Proc
78 0 1 0 0.00% 0.00% 0.00% 0 CWAN IF EVENT HA
79 0 1 0 0.00% 0.00% 0.00% 0 CWAN LTL Mgr HA
80 0 1 0 0.00% 0.00% 0.00% 0 CWAN SRP HA Proc
81 0 1 0 0.00% 0.00% 0.00% 0 CWAN HA VLAN SYN
82 212 4060 52 0.00% 0.00% 0.00% 0 RF CWAN HA Proce
83 24520 239411 102 0.00% 0.00% 0.00% 0 Heartbeat Proces
84 0 2 0 0.00% 0.00% 0.00% 0 Switch IP Host T
85 0 14 0 0.00% 0.00% 0.00% 0 EEM RF Event Det
86 0 1 0 0.00% 0.00% 0.00% 0 Mistral Reset Pr
87 0 1 0 0.00% 0.00% 0.00% 0 ECC correctable
88 0 19 0 0.00% 0.00% 0.00% 0 PF_Init Process
89 12 21 571 0.00% 0.00% 0.00% 0 RPC pf-split-rp
90 20 19 1052 0.00% 0.00% 0.00% 0 RPC idprom-MP
91 0 1 0 0.00% 0.00% 0.00% 0 RTTYS Process
92 0 1 0 0.00% 0.00% 0.00% 0 BACK CHECK
93 758089 199450 3800 0.23% 0.30% 0.29% 0 Compute load avg
94 338541 2791511 121 0.07% 0.08% 0.08% 0 Service Task
95 0 1 0 0.00% 0.00% 0.00% 0 chkpt message ha
96 0 2 0 0.00% 0.00% 0.00% 0 cpf_process_msg_
97 0 1 0 0.00% 0.00% 0.00% 0 cpf_process_ipcQ
98 0 1 0 0.00% 0.00% 0.00% 0 IPC Apps Task
99 0 1 0 0.00% 0.00% 0.00% 0 RPCP Slave
100 0 26 0 0.00% 0.00% 0.00% 0 AggMgr Process
101 0 1 0 0.00% 0.00% 0.00% 0 SFF8472
102 0 1 0 0.00% 0.00% 0.00% 0 Remote Console P
103 0 1 0 0.00% 0.00% 0.00% 0 RTTYS Process
104 0 2 0 0.00% 0.00% 0.00% 0 CWAN OIR Handler
105 0 1 0 0.00% 0.00% 0.00% 0 spa_oir_audit_pr
106 0 1 0 0.00% 0.00% 0.00% 0 FPD Management P
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
107 0 1 0 0.00% 0.00% 0.00% 0 FPD Action Proce
108 0 1 0 0.00% 0.00% 0.00% 0 DSX3MIB ll handl
109 0 1 0 0.00% 0.00% 0.00% 0 POS APS Event Pr
110 0 2 0 0.00% 0.00% 0.00% 0 CWAN port channe
111 0 1 0 0.00% 0.00% 0.00% 0 CE3 Mailbox
112 0 1 0 0.00% 0.00% 0.00% 0 CT3 Mailbox
113 0 2 0 0.00% 0.00% 0.00% 0 MIP Mailbox
114 0 1 0 0.00% 0.00% 0.00% 0 vcq_proc
115 0 1 0 0.00% 0.00% 0.00% 0 Earl NDE Task
116 3672 238244 15 0.00% 0.00% 0.00% 0 CWAN CHOCX PROCE
117 4496 238242 18 0.00% 0.00% 0.00% 0 CWAN CHDSX PROCE
118 0 1 0 0.00% 0.00% 0.00% 0 HAL Mailbox
119 0 1 0 0.00% 0.00% 0.00% 0 CWRP SPA ATM OIR
120 0 15 0 0.00% 0.00% 0.00% 0 Gemini L3 forwar
121 186288 323021 576 0.15% 0.06% 0.05% 0 esw_vlan_stat_pr
122 0 2 0 0.00% 0.00% 0.00% 0 Spanning Tree
123 0 2 0 0.00% 0.00% 0.00% 0 AAA Dictionary R
124 1015 401 2531 0.00% 0.00% 0.00% 0 SW VLAN RP
125 1151665 13536983 85 0.15% 0.23% 0.38% 0 ION IP output
126 34194165 23417270 1460 9.83% 11.61% 12.80% 0 IP Input
127 0 1 0 0.00% 0.00% 0.00% 0 Socket Timers
128 308 23714 12 0.00% 0.00% 0.00% 0 QOS Stats Gather
129 9636 24804 388 0.00% 0.00% 0.00% 0 CEF Scanner
130 96 2244 42 0.00% 0.00% 0.00% 0 DHCP Snooping
131 5196652 9375380 554 0.47% 0.66% 0.99% 0 IP NAT Ager
132 45100 1908039 23 0.07% 0.01% 0.00% 0 CEF RP IPC Backg
133 0 1 0 0.00% 0.00% 0.00% 0 MLS FIB RP
134 0 1 0 0.00% 0.00% 0.00% 0 mcast_rp_icc Pro
135 12 5 2400 0.00% 0.00% 0.00% 0 Const Rate Limit
136 0 1 0 0.00% 0.00% 0.00% 0 CWAN LTL manager
137 528 1699 310 0.00% 0.00% 0.00% 0 HWIF QoS Process
138 0 2 0 0.00% 0.00% 0.00% 0 AAA Server
139 0 1 0 0.00% 0.00% 0.00% 0 AAA ACCT Proc
140 0 1 0 0.00% 0.00% 0.00% 0 ACCT Periodic Pr
141 0 2 0 0.00% 0.00% 0.00% 0 QOS Stats Export
142 0 1 0 0.00% 0.00% 0.00% 0 SSS Manager
143 308 32181 9 0.00% 0.00% 0.00% 0 SSS Test Client
144 0 2 0 0.00% 0.00% 0.00% 0 Switch IP Host T
145 0 1 0 0.00% 0.00% 0.00% 0 Switch IP Admiss
146 0 1 0 0.00% 0.00% 0.00% 0 ARP HA
147 0 1 0 0.00% 0.00% 0.00% 0 HDLC HA
148 0 1 0 0.00% 0.00% 0.00% 0 RPCP Slave
149 0 1 0 0.00% 0.00% 0.00% 0 PPPATM Session d
150 0 2 0 0.00% 0.00% 0.00% 0 PASVC create VA
151 12364 7189 1719 0.00% 0.00% 0.00% 0 MOP Protocols
152 0 2 0 0.00% 0.00% 0.00% 0 IP Hdr Comp Proc
153 0 1 0 0.00% 0.00% 0.00% 0 AC Mgr
154 0 1 0 0.00% 0.00% 0.00% 0 DMLP Counter
155 8 14 571 0.00% 0.00% 0.00% 0 EAPoUDP Process
156 0 3 0 0.00% 0.00% 0.00% 0 cfib v6 per pref
157 0 2 0 0.00% 0.00% 0.00% 0 const ipfib per-
158 0 1 0 0.00% 0.00% 0.00% 0 RPCP Slave
159 0 1 0 0.00% 0.00% 0.00% 0 IP IRDP
160 584 68359 8 0.00% 0.00% 0.00% 0 DHCPD Database
161 219 1924 113 0.00% 0.00% 0.00% 1 Hot Service Task
162 208 1924 108 0.00% 0.00% 0.00% 1 Hot Service Task
163 251 1922 130 0.00% 0.00% 0.00% 1 Hot Service Task
164 0 2 0 0.00% 0.00% 0.00% 0 CWPA QoS
165 0 2 0 0.00% 0.00% 0.00% 0 Const TCAM Mgr R
166 0 1 0 0.00% 0.00% 0.00% 0 HTTP Timer
167 209768 103078 2035 0.00% 0.06% 0.07% 0 IPC LC Message H
168 3853927 25036944 153 0.47% 1.12% 1.36% 0 Standby (HSRP)
169 116 608 190 0.00% 0.00% 0.00% 0 IP SNMP
170 249944 404013 618 0.00% 0.05% 0.06% 0 CEF process
171 28888 120725 239 0.07% 0.01% 0.00% 0 HIDDEN VLAN Proc
172 252327 66898 3771 0.05% 0.08% 0.07% 0 Adj Manager
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
173 172 4023 42 0.00% 0.00% 0.00% 0 IP Cache Ager
174 0 1 0 0.00% 0.00% 0.00% 0 CWAN-RP SCP Proc
175 0 15 0 0.00% 0.00% 0.00% 0 CWAN-RP SCP Inpu
176 8940 249596 35 0.00% 0.00% 0.00% 0 L3 Manager
177 0 1 0 0.00% 0.00% 0.00% 0 MLSM-CC Process
178 0 6 0 0.00% 0.00% 0.00% 0 mfib-const-rp Pr
179 275065 514397 534 0.00% 0.05% 0.11% 0 FM core
180 0 38 0 0.00% 0.00% 0.00% 0 SNMP Timers
181 3 1 3000 0.00% 0.00% 0.00% 0 PPP IP Add Route
182 101408 422029 240 0.39% 0.06% 0.05% 0 DHCPD Receive
183 0 1 0 0.00% 0.00% 0.00% 0 VFI Mgr
184 0 1 0 0.00% 0.00% 0.00% 0 PAD InCall
185 0 2 0 0.00% 0.00% 0.00% 0 X.25 Background
186 0 1 0 0.00% 0.00% 0.00% 0 X.25 Encaps Mana
187 0 1 0 0.00% 0.00% 0.00% 0 Inspect Timer
188 0 1 0 0.00% 0.00% 0.00% 0 Auth-proxy AAA B
189 28 806 34 0.00% 0.00% 0.00% 0 IP Admin SM Proc
190 0 1 0 0.00% 0.00% 0.00% 0 SLB CF process
191 0 1 0 0.00% 0.00% 0.00% 0 PPP HA
192 0 1 0 0.00% 0.00% 0.00% 0 IDS Timer
193 0 2 0 0.00% 0.00% 0.00% 0 MWAM_CONSOLE Tim
194 0 3 0 0.00% 0.00% 0.00% 0 L2TRACE SERVER
195 0 4 0 0.00% 0.00% 0.00% 0 IPv6 CEF process
196 0 1 0 0.00% 0.00% 0.00% 0 RARP Input
197 0 1 0 0.00% 0.00% 0.00% 0 PDU DISPATCHER
198 0 1 0 0.00% 0.00% 0.00% 0 Probe Input
199 0 1 0 0.00% 0.00% 0.00% 0 FR HA
200 0 75 0 0.00% 0.00% 0.00% 0 CWAN QinQ tasks
201 0 1 0 0.00% 0.00% 0.00% 0 COPS
202 0 1 0 0.00% 0.00% 0.00% 0 CHKPT DevTest
203 0 1 0 0.00% 0.00% 0.00% 0 ATM HA
204 0 2 0 0.00% 0.00% 0.00% 0 ATIP_UDP_TSK
205 0 2 0 0.00% 0.00% 0.00% 0 AAA Cached Serve
206 0 2 0 0.00% 0.00% 0.00% 0 LOCAL AAA
207 0 1 0 0.00% 0.00% 0.00% 0 SNMP ENGINE
208 0 1 0 0.00% 0.00% 0.00% 0 SNMP ConfCopyPro
209 0 1 0 0.00% 0.00% 0.00% 0 Laminar Icc Eve
210 0 2 0 0.00% 0.00% 0.00% 0 Laminar Config C
211 0 2 0 0.00% 0.00% 0.00% 0 SLB Main CPU pro
212 7912 1885 4197 0.00% 0.00% 0.00% 0 SNMP Traps
213 3 1 3000 0.00% 0.00% 0.00% 0 CCSWVOICE
214 0 2 0 0.00% 0.00% 0.00% 0 Rommon upgrade p
215 0 3 0 0.00% 0.00% 0.00% 0 RADIUS TEST CMD
216 0 2 0 0.00% 0.00% 0.00% 0 AAA SEND STOP EV
217 4 7 571 0.00% 0.00% 0.00% 0 RPC fabman_sp
218 0 14 0 0.00% 0.00% 0.00% 0 RPC lcc_sp
219 23224 329953 70 0.00% 0.00% 0.00% 0 NTP
220 988 2080 475 0.00% 0.00% 0.00% 0 RPC pm-mp
221 17856 830863 21 0.00% 0.00% 0.00% 0 PM Callback
222 4 11 363 0.00% 0.00% 0.00% 0 EC-Card-Cfg
223 3496382 13880531 251 0.00% 1.51% 1.50% 0 Port manager per
224 792 48148 16 0.00% 0.00% 0.00% 0 Max CPU utilizat
225 72 214 336 0.00% 0.00% 0.00% 0 RPC capi_rp
226 0 2 0 0.00% 0.00% 0.00% 0 RPC dot1x_aaa_rp
227 0 2 0 0.00% 0.00% 0.00% 0 RPC epld_sp2rp
228 40 205 195 0.00% 0.00% 0.00% 0 RPC idbman_sp2mp
229 111455 27328 4078 0.00% 0.04% 0.03% 0 RPC online_diag_
230 0 2 0 0.00% 0.00% 0.00% 0 RPC online_wan_d
231 32 16 2000 0.00% 0.00% 0.00% 0 RPC pagp_switch_
232 0 80 0 0.00% 0.00% 0.00% 0 RPC pm_switch_sp
233 0 2 0 0.00% 0.00% 0.00% 0 RPC psecure_rp
234 0 2 0 0.00% 0.00% 0.00% 0 RPC pt_switch_sp
235 12 79 151 0.00% 0.00% 0.00% 0 RPC qnq_switch_s
236 0 2 0 0.00% 0.00% 0.00% 0 RPC rf_cli_sp2rp
237 0 2 0 0.00% 0.00% 0.00% 0 RPC snmp_notify
238 0 6 0 0.00% 0.00% 0.00% 0 RPC snmp_stackli
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
239 0 2 0 0.00% 0.00% 0.00% 0 RPC span_switch_
240 268 1289 207 0.00% 0.00% 0.00% 0 RPC stp_sp2mp_ap
241 0 2 0 0.00% 0.00% 0.00% 0 RPC sw_backup_in
242 104 672 154 0.00% 0.00% 0.00% 0 RPC sw_vlan_rp
243 0 6 0 0.00% 0.00% 0.00% 0 RPC udld_rp
244 156 620 251 0.00% 0.00% 0.00% 0 RPC vtp_const_ap
245 0 2 0 0.00% 0.00% 0.00% 0 VTPMIB EDIT BUFF
246 0 1 0 0.00% 0.00% 0.00% 0 RPCP Slave
247 24 31 774 0.00% 0.00% 0.00% 0 RPC c6k_power_rp
248 8 37 216 0.00% 0.00% 0.00% 0 RPC c6k_rp_envir
250 0 2 0 0.00% 0.00% 0.00% 0 Module enable-di
251 0 2 0 0.00% 0.00% 0.00% 0 RPC pikachu_rp
252 0 1 0 0.00% 0.00% 0.00% 0 RP L2 Applicatio
253 0 1 0 0.00% 0.00% 0.00% 0 Const FIB MAC
254 236 842 280 0.00% 0.00% 0.00% 0 Constellation Ba
255 24 57 421 0.00% 0.00% 0.00% 0 RPC pclc_g2_fw_r
256 0 2 0 0.00% 0.00% 0.00% 0 RPC chapi_rp
257 0 1 0 0.00% 0.00% 0.00% 0 CONST AFL
258 0 5 0 0.00% 0.00% 0.00% 0 PAgP-MP Process
259 0 5 0 0.00% 0.00% 0.00% 0 LACP-MP Process
260 8 34 235 0.00% 0.00% 0.00% 0 Logger ICC Proce
261 112 52 2153 0.00% 0.00% 0.00% 0 Syslog Traps
262 12 69 173 0.00% 0.00% 0.00% 0 rp to lc clock u
263 0 1 0 0.00% 0.00% 0.00% 0 LC Registry Expo
264 0 2 0 0.00% 0.00% 0.00% 0 RPC pclc_g2_agsm
265 96 112 857 0.00% 0.00% 0.00% 0 Online Diag EEM
266 0 1 0 0.00% 0.00% 0.00% 0 L3MM Process
267 0 2 0 0.00% 0.00% 0.00% 0 RPC itasca_rp
268 0 1 0 0.00% 0.00% 0.00% 0 HW Capacity ICC
269 0 2 0 0.00% 0.00% 0.00% 0 RPC error_detect
270 916 40190 22 0.00% 0.00% 0.00% 0 RP Error Detecti
271 0 2 0 0.00% 0.00% 0.00% 0 WiSM Process
272 0 1 0 0.00% 0.00% 0.00% 0 SONET Traps
273 0 10 0 0.00% 0.00% 0.00% 0 RPC aapi_rp
274 44 208 211 0.00% 0.00% 0.00% 0 QM Process on RP
275 0 2 0 0.00% 0.00% 0.00% 0 QM Reply Process
276 0 2 0 0.00% 0.00% 0.00% 0 QM Timer ACL Pro
277 0 3 0 0.00% 0.00% 0.00% 0 CWAN Bridge task
278 40 4027 9 0.00% 0.00% 0.00% 0 VACL Logger
279 0 1 0 0.00% 0.00% 0.00% 0 DHCP Snooping Sw
280 0 2 0 0.00% 0.00% 0.00% 0 SIP10G QM Proces
281 0 1 0 0.00% 0.00% 0.00% 0 Online Diag CNS
282 0 1 0 0.00% 0.00% 0.00% 0 Online Diag CNS
284 232 1922 120 0.00% 0.00% 0.00% 1 Hot Service Task
286 0 1 0 0.00% 0.00% 0.00% 0 NetFlow Agg Task
287 0 1 0 0.00% 0.00% 0.00% 0 CWAN OIR IPC Rea
288 0 1 0 0.00% 0.00% 0.00% 0 PF Clock Process
Thanks. -
Does a 2504 WLC support mobility group with WiSM1 on 6500 Series
if a 2504 WLC support mobility group with WiSM1 on 6500 Series.
Model: WLC 2504
Software version: 7.3.101.0
Model: WiSM1
Software verion: 7.x.x.xYes and no.
Yes, mobility is supported.
No because I personally won't recommend inter-controller roaming. This is more true when you're dealing with 4400/WiSM-1. This is even more true when you've got WLC running two (or more) different codes. -
Cisco switch 6500 configuration to support the DCM
hi all
If I need to connect DCM to 6500 I think in two model of configuration:
The first model:
ip multicast-routing
vlan 16
name DCM
exit
interface Vlan16
description *** DCM ***
ip address 10.16.0.1 255.255.0.0
Inter gi 1/1/1
description "TO DCM”
ip address 10.16.0.2 255.255.0.0
ip igmp version 3
ip igmp join-group 239.10.10.10
ip pim sparse-mode
Inter gi 2/1/1
description "TO DCM”
ip address 10.16.0.4 255.255.0.0
ip igmp version 3
ip igmp join-group 239.10.10.10
ip pim sparse-mode
The second model
ip multicast-routing
vlan 16
name DCM
exit
interface Vlan16
description *** DCM ***
ip address 10.16.0.1 255.255.0.0
ip igmp version 3
ip igmp join-group 239.10.10.10
ip pim sparse-mode
Inter gi 1/1/1
description "TO DCM”
switchport
switchport mode access
switchport access vlan 16
Inter gi 2/1/1
description "TO DCM”
switchport
switchport mode access
switchport access vlan 16
which one is the correct and what is the required other than these configuration ?
please advice
thanks in advanceHi
Are you taking about cisco digital content manager .
Configuring IP address by your first model on your catalyst switch 6500 is not possible , On your second model check on your DCM whether you are able to assign same subnet IP address on your Gi interface .
Even I dont see you can assign same IP subnet to multiple GI interface , you need to go with multiple IP subnets for connectivity between DCM and your catalyst switch .
http://www.cisco.com/c/dam/en/us/td/docs/video/headend/DNCS/78-4003867-01_B.pdf
http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/28745-44.html#qa15
Q. Can I configure two interfaces in the same subnet (t0 = 142.10.46.250/24 and t1 142.10.46.251/24)?
A. No. For the routing to work, each interface should be on a different subnet. However, if you are only bridging, and not doing IP routing, then you can configure the two interfaces on the same subnet.
HTH
Sandy -
Can I connect two switches to a server?
We share an office with another company but we currently have separate servers and networks.
I'm looking into the possibility of us sharing their server.
The thing is we both have our own switches and and I want to avoid any rewiring of the network. Will I be able to use two switches?
It's a 2x 2.8 GHz quad core intel xeon (with dual ethernet). So is it just a matter of connecting both switches to the server and configuring them in some way?Hi Christiaan,
I end up doing this quite often. You have a few options, the simplest is below...
How many users and devices that require network connections does each company have? If it's under 254 which it sounds like it is and your happy to have the users on the same network, sharing the same ISP. Then the easiest option is going to be your company sharing their network. You'd save a bit of money on your internet connection which could be used to increase the bandwidth on the other companies line if needed.
You would do following. Make sure all devices that need a fixed IP address such as printers/mfds'/switches/WiFI/phone system (if applicable) are changed to a fixed IP address with the relevant subnet mask, dns and gateway from the other companies network. You'd obviously need to get the relevant numbers from their IT guy.
Then you could use your switch as extra capacity on their network by linking it with their switch. Obviously you'd want to use the fastest possible connection between the switches or look to buying something new with more ports. If you both have something like the HP 1810G ProCurve or a compatible switch you can buy two fibre transceivers and connect them with a fibre cable, this will free up more ports for users on the switch or simply connect them via an ethernet cable. On the 1800 series you can use LACP which allows you to use up to 4 ethernet ports to improve the bandwidth thus giving you a 4gigabit connection to their network. Depending on how much traffic there is going to be you might want to skip that as there might be no need.
Then it's just a case of creating your users on their server and creating an area for your company that only you have the access rights to and creating a shared area inter-company area if you want to easily ping them over files.
What do you both use for email? Are you going to look to share a server for it?
Hope that helps
Beatle -
Difference between 6500 series WLSM & 6500 series WiSM.
Hi , I would like to know the difference between 6500 series WLSM & 6500 series WiSM.
& also let me know, how many controllers will be physically inside the 6500 series WiSM.Hello Selvaraj,
As per your query i can suggest you the following solution-
WLSM and WiSM are two completely different architectures, and seamless
mobility between them, if at all possible would probably not be worth the
effort.
For more information please refer to the link-
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_configuration_example09186a008073614c.shtml
Hope this will help you. -
Can I print from my 4s iphone using my 6500 series hp photosmart all in one 709e printer?
Can I print documents from my 4S Iphone with my HP 6500 series all in one 709E printer? It states that it cannot locate printer when I attempt to print.
Thanks,
ToddIf the printer is not AirPrint compatible but is wi-fi capable, you will need to get one of the many wi-fi printing apps available at the app store. HP has an app. Some of the wi-fi printing apps have more capabilities than others.
Maybe you are looking for
-
Remote access and network services problem
I have a Mac Pro with two IP configs: Ethernet 1: 69.##.##.## /255.255.255.248 [hidden for public forum security] Ethernet 2: 10.0.0.20/255.255.255.0 My primary needs: Able to remotely access the Mac via Remote Desktop using the public IP. Local LAN
-
Syntax error while creating Calculation view script based
Hi Folks, I'm creating Calc view based on script and drafted a simple code but I'm getting syntax error. Its just fetching few coloumns from two tables products and purchaseorderitem. /********* Begin Procedure Script ************/ BEGIN var_out =
-
It looks like my phone contacts were updated to my gmail contacts? I lost phone numbers I know I had and now I have all these stupid email addresses in my contacts. Will I be able to get my numbers back from my verizon backup? can they reload from a
-
Nokia X6 simple question to start with
Hi, just bought a X6 and struggling like many. I think I know how to use the GPS (will try this weekend) but I am used to the GPS pointing towards the actual position, not the north. A car GPS or a Tomtom point in the direction you're going or pointi
-
Hi, I would like some assistance, I have an ADR for endpoint protection configured that works about 90% on all the devices I am managing. I would like assistance with a Configuration Baseline that tackles the rest of the Devices, Here is my Discovery