SNMP cpuload SF200-24P

Hi,
I'm trying to get CPU Load information from my SF200-24P switch by SNMP.
Software Information
Firmware Version (Active Image):
1.3.2.02
SNMP is enabled and working:
/usr/bin/snmpget -t 1 -r 5 -m RFC1213-MIB -v 2c [authpriv] 172.26.34.6:161 ifOperStatus.1
RFC1213-MIB::ifOperStatus.1 = INTEGER: up(1)
Processing oid 1 (line 1)
oidname: RFC1213-MIB::ifOperStatus.1
response: = INTEGER: up(1)
Have downladed CISCOSB-CPU-COUNTERS-MIB, CISCOSB-MIB, CISCOSB-rndMng, but not success.
/usr/bin/snmpget -t 1 -r 5 -m CISCOSB-rndMng -v 2c [authpriv] 172.26.34.6:161 rlCpuUtilDuringLastSecond
CISCOSB-rndMng::rlCpuUtilDuringLastSecond = No Such Instance currently exists at this OID
Processing oid 1 (line 1)
oidname: CISCOSB-rndMng::rlCpuUtilDuringLastSecond
response: = No Such Instance currently exists at this OID
Which MIB file must be downloaded for proper operation?
Thank you in advance!
Raul

Hi,
First upgrade to version sx200_fw_1.3.7.18.ros and Boot code sx200_boot-13506.rfb.After that upgrade to latest firmware sx200_fw-14088.ros .Not required to upgrade the boot code .since boot code is same for both version firmware.
regards
Moorthy

Similar Messages

SG200-26P + SF200-24P, LAG? Trunking?

I'm not a network person by any means and have no problem admitting that. That's why I'm here.
I have a SG200-26P that is already configured and working properly. It is connected to an ASA5505 that is acting as the DHCP server. We currently have 3 VLANs: 10, 20 & 40.
We are adding in a SF200-24P and I wanted to LAG & Trunk (I think that's the correct terms) to the 26P and the VLANs would go across both switches. I set up the LAG through the GUI on both devices with GE25/GE26 on the SG200-26P and GE1/GE2 on the SF200-24P as the LAG ports. When I connect them together I can not get an IP address, nor can I ping the 26P from a device connected to the 24P (after setting a static IP to just be able to access the GUI on the 24P).
SG200-26P = 192.168.1.3
SF200-24P = 192.168.1.4
Thanks for any help you can provide. I'm sure this is actually a simple setup but I can't figure it out.

Hi MHPL, you're correct a LAG and trunk is accurate. When you think about a LAG think of it exactly the same as a single link. You must config it like any singular port and you will observe when configuring the VLAN properties that there is an option for the LAG.
Moving past that, there are 2 types of LAG, static and dynamic. I recommend that you use static LAG where each side does not use any protocol to negotiate the LAG. So when you go to the port management -> LAG setting simple add the port and click apply (do not click LACP) and make the same configuration on the other switch and connect them. Just ensure that the switches are essentially identical.

Upgrading SF200-24P firmware questions

I have an SF200-24P running FW 1.2.7.76 and boot 1.1.0.6. I wanted to update the firmware in hopes it would help with a weird problem I'm having with a UC320 phone system so I downloaded from Cisco Sx200_FW_Boot_1.4.0.88.zip.
The instructions say if I'm upgrading from something earlier than 1.3.5, I first need to upgrade the device image to "to image 1.3.5 or 1.3.7 and the latest boot file (1.4.0.x)."
In the ZIP file I downloaded from Cisco are two files:
sx200_boot-13506.rfb
sx200_fw-14088.ros
Are they just saying I first need to load the sx200_boot-13506.rfb, then load the
sx200_fw-14088.ros file?
Or do I need to download a previous copy of the firmware? If that is the case, do I just download 1.3.5.58 and install the .ros file in that archive, wait for the switch to become ready, and load the .ros file from the 1.4.0.88 archive?
I'm unclear on the process of getting my switch with old firmware updated to the newest firmware. So any tips would be appreciated.

Hi,
First upgrade to version sx200_fw_1.3.7.18.ros and Boot code sx200_boot-13506.rfb.After that upgrade to latest firmware sx200_fw-14088.ros .Not required to upgrade the boot code .since boot code is same for both version firmware.
regards
Moorthy

SNMP WS-C2960-24PS-L

Hi
I have a problem with adding a Cisco switch to the NMS (Smarts). When I start a discovery process from the snmp manager (Smarts NMS) it does resolve the ip address into the hostname but once the discovery process is completed the device in question is not added in the list of managed devices. Please view attached basic configuration and advice if anyone can spot a problem.
Kind regards
Mpho

Hi
I have tried to use different IP addresses and the behaviour is still the same, though I knew that changing an ip address won't help but I tried because I ran out of ideas.
I also reset both the snmp agent and manager, and other types of switches that I had in the labs were discovered correctly but these latest 2960S are the ones that are giving me problems.
Question: Can you ping?
Answer: yes i can ping the device
Question: Can you SNMPWalk the device from the SMARTs server?
Ans: Yes I could do an snmp walk but I don't really know how to interpret the output(results), what is the snmp oid that should be entailed on the snmp output which is used for the devices to be managed (added to the list of managed devices)?
Kind regards
Mpho

SF200-24P config to use DSL

Hi all,
Recently purchased device to use in small 'satellite' office/garage application. Interested in eliminating points of failure and would like to see if we are able to integrate device to directly manage DSL modem, DHCP etc. so effectively offloading the functions of a Cable/DSL router to it.
Suggestions?

This is an excerpt from Snow Leopard Help on how the network preference pane works:
"You can connect to the Internet or a network in several ways (using a modem, AirPort, or Ethernet, for example). If you have multiple active network port configurations, Mac OS X tries the configuration at the top of the list first, and then tries the other port configurations in descending order when you attempt to connect to the Internet."
I connect with a DSL using PPoE, and I have a port for PPoE and a separate one for Ethernet in my network preference pane. You may find FAQ on your provider's site that will give you the type of connection you have.

SF200 switch freeze

We have been deploying Cisco SF200-24P switches for our systems for over a year now. They connect to a Cisco 881 router. In many cases we are also deploying Cisco AP541s.
Over the last few months, on an intermittent basis, the switches will simply freeze, blocking all traffic flow. The power LED also goes dark. It appears the switch has frozen. The only thing that seems to revive the switch is a hard reboot by pulling the power cord. In the last couple of weeks, one site in particular has gone down a handful of times. That client of our is fed up. Our patience is running thin too.
I cannot see any indications in the logs to any event that might give a clue as to the problem. We definitely see this problem with the 1.2.7.76 firmware and the 1.2.9.44 (latest as of typing this). Not sure if with earlier 1.1.2 firmware.
Without a fix, we likely will have to change switches and possibly vendors as we need a reliable switch.
Our standard config is.
Multiple VLANs;
2
11 (default)
12
- switch set to static IP on VLAN 11 and gateway set
- most ports set to Access ports (untagged)
- 4 set to trunk ports, for connecting the 541APs with VLANs tagged
- G1 & G2 set to trunk ports with VLANS tagged (to Cisco 881 and/or additional switches)
- Bonjour unchecked
I see some vague references to a similar problem. And one reference to a SG300 series having what sounds like the same issue.

That's interesting. Most of the freeze/lock issues are related to SSH and or Bonjour. On the 1.1.1.8 firmware the switch had a bug where it would flood TCP out all ports due to losing the address entries. However that is long resolved and does not pertain to actual connectivity.
Were you at one point using a 1.2.5.7 software? Or did you go from the 1.1.2.0 to the 1.2.7.76 software and then 1.2.9.44 software?
When upgrading from the 1.1.2.0 firmware to the later 1.2.7.76 and 1.2.9.44, this changed the internal XML. This may correspond to unexpected crashes as the older settings may not update correctly to the newer write to the XML.
If it's possible can you default the switch after an upgrade to the 1.2.7.76 or 1.2.9.44?
-Tom
Please mark answered for helpful posts

SF200 port mirroring function

Hello,
i was able to configure (via SF200 web interface) a port mirroring from port FE17 to FE7.
i have supressed this port mirroring.
when i try to reconfigure a port mirroring from port FE17 to FE3. The SF200 web interface crash. the SF200 seems to reboot.
i have updated the SF200 firmware from V1.1.2.0 to V1.1.2.9.44
when i was able to configure (via SF200 web interface) a port mirroring from port FE17 to FE7.
But after having suppressed this port mirroring again, i was not able to reconfigure a new port mirroring from port FE1 to FE3 (the SF200 hangs).
i have also tried to return to default factory setting but this does not solve the issue.
i am working on SF200-24P
Thanks for helping !
Regards,
Christophe

Hi Chris, are you connecting the computer to the source port or destination port? When you run the port monitor, the port receiving information (destination) will not function and drop all connectivity).
With that said, when you modified the port mirror, can you move the computer to a completely unrelated port such as fe10 and get connectivity?
Or, if the monitor port is an uplink to such a device as a router, can you move that port connection to something entirely unrelated like port 20 to see if you gain connectivity?
-Tom
Please mark answered for helpful posts

Firmware Best practices

Any suggestions on best practices for firmware upgrading. Currently using a combination of SF200 switches (SF200-48, SF200-24, SF200-24P, SF200-24FP), WAP561, and WAP321. The question is should I step the updates from the current to the most recent or can I just update to newest release?

Hello,
For the switches please bear in mind the following upgrade steps:
https://supportforums.cisco.com/document/12321266/firmware-upgrade-troubleshooting-300-and-500-series-managed-switches
Please note that with boot code 1.3.5.06 there are quite important change in file system so before proceeding to 1.4.0.88 you will have to upgrade switch to 1.3.7 firmware not boot code 1.3.5.06.
For the access points it is not the same case however please always check release notes of the latest firmware for special instructions.
Regards,
Aleksandra

SF302-08P Switch VLAN Problem

Hello
I have a problem configuring a SF 302-08P switch for VLAN. Here is my setup. I have two switches that are configured almost the same. The first switch is a SF200-24P with 12 ports on VLAN1 and twelve ports on VLAN2. The G1 port is the incoming trunk with 1UP, 2T and the G2 port set to 1UP, 2T connecting to the G1 port on the SF302-8 switch. Both Vlans work OK on the SF200-24 switch. The port on the SF200-24 is set to trunk 1UP,2T and the G1 port on the SF302-8 is set to trunk 1UP,2T. The VLAN port membership on the SF302-8 is set to VLAN 1 port 1-4 is 1UP and VLAN 2 port 5-8 is set to 2UP. Ports 1-4 work OK but the 5-8 will not connect to vlan 2. I have downloaded the latest firmware for the SF302 but it did not make any difference. Any suggestions on what I am missing?

Tom
Ok maybe I can explain this a little different. I inherited this project that two parts were built prior to me. The router is a Sonicwall that has too LAN connections with 192.168.1.x on one LAN and 192.168.2.x on the second LAN. That router is connected to a Cisco SF20024P switch on the first floor of a building. The first floor is connected to a second floor switch which is a SF20024P with the same configuration. Both first floor and second floor works great. There is a third floor which is a much small area that only needed an eight port switch. This is where I came in and installed the third switch which is the SF302-8P. The first floor switch passes traffic up to the second floor switch using a trunk with vlan 1 untagged and vlan 2 tagged. The second floor switch takes in traffic fine and works great. Why should the second switch not pass the vlan 2 traffic to the third switch? It should pass it up to the third switch using the same tagging method. As I said the traffic on vlan 1 works on the third switch, just vlan 2 will not.
Thanks

Plse...help me on the communicating between CLEAN ACCESS MANAGER and Switch 3560E-24Ps by snmp

Dear All,
I try to configure in both Clean Access Manager and Switch 3560E-24Ps on SNMP Version 2 protocol but I can't make it working together (For CAM and Switch 3560G-48Ps I can do that). Plse give me any suggestion to solve that problem. All configuration is as below:

http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/412/cam/412_cam_book.html

SNMP on SF-200 24P

Hi, I need to SNMP on Cisco Smart switch SF-200 24p. I cannot find any option on administration to turn snmp service on. Thanks in advice

Hi Roman, this device does not support SNMP. The SX200E model does.
-Tom
Please mark answered for helpful posts

SF300-24P - SNMP question

Hi,
I've a script that does the check of port status asking OIDs
.1.3.6.1.2.1.17.4.3.1.2
.1.3.6.1.2.1.17.4.3.1.1
.1.3.6.1.2.1.2.2.1.8
after a firmware upgrade, all these OIDs are not available.
for example:
snmpwalk -v 2c -c public 192.168.1.197 .1.3.6.1.2.1.17.4.3.1.2iso.3.6.1.2.1.17.4.3.1.2 = No Such Instance currently exists at this OID
I also tried to follows procedures like:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801c9199.shtml
using the community string indexing (I don't think that it applies to small business switches) but for desperation...
Have you any suggestion?
Thank you very much in advance,
and sorry if it's an already asked question, I've tried the search button, but without finding a definitive answer.
Best Regards,
Franceco

Hi Tom,
thanks for your answer,
on my first switch (firmware 1.0.0.27)
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 iso.3.6.1.4.1.9.6.1.101.53.4.1.5.1iso.3.6.1.4.1.9.6.1.101.53.4.1.5.1 = STRING: "1.0.0.27"francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 iso.3.6.1.4.1.9.6.1.101.53.4.1.6.1iso.3.6.1.4.1.9.6.1.101.53.4.1.6.1 = STRING: "SF 300-24P"francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.17.4.3.1.1iso.3.6.1.2.1.17.4.3.1.1.0.1.108.10.28.67 = Hex-STRING: 00 01 6C xx xx xxiso.3.6.1.2.1.17.4.3.1.1.0.5.51.63.126.18 = Hex-STRING: 00 05 33 xx xx xx...iso.3.6.1.2.1.17.4.3.1.1.228.31.19.196.116.24 = Hex-STRING: E4 1F 13 xx xx xxiso.3.6.1.2.1.17.4.3.1.1.228.31.19.196.116.26 = Hex-STRING: E4 1F 13 xx xx xxfrancesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.17.4.3.1.2iso.3.6.1.2.1.17.4.3.1.2.0.1.108.10.28.67 = INTEGER: 1000iso.3.6.1.2.1.17.4.3.1.2.0.5.51.63.126.18 = INTEGER: 1000...iso.3.6.1.2.1.17.4.3.1.2.228.31.19.196.116.24 = INTEGER: 1000iso.3.6.1.2.1.17.4.3.1.2.228.31.19.196.116.26 = INTEGER: 1000francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.2.2.1.8iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2...iso.3.6.1.2.1.2.2.1.8.100000 = INTEGER: 1iso.3.6.1.2.1.2.2.1.8.300000 = INTEGER: 1
On firmware 1.1.1.8 same output.
If you need somthing else, please let me know.
Best Regards,
Francesco

SF300-24P unstable traffic

Hello,
I've installed and configured 2 SF300-24P switches on Layer 3 mode in my company.
Since I've made this installation, I accounter some problems of stability in my LAN communication.
Here is the running config of the 2 switches:
First Switch
SW-WIFI#show running-config
config-file-header
SW-WIFI
v1.2.9.44 / R750_NIK_1_2_584_002
CLI v1.0
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
no cdp run
no spanning-tree
vlan database
vlan 2
exit
voice vlan state disabled
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
ip dhcp relay address 172.16.0.2
ip dhcp relay enable
ip dhcp information option
bonjour interface range vlan 1
hostname SW-WIFI
username cisco password encrypted 18c7e97c305303ec56fbb3105666d85721208731 privilege 15
ip ssh server
snmp-server server
clock timezone " " 0 minutes 0
ip telnet server
interface vlan 1
ip address 172.16.0.249 255.255.0.0
no ip address dhcp
interface vlan 2
name POSTES
ip address 192.168.1.245 255.255.255.0
ip dhcp relay enable
interface fastethernet1
ip dhcp relay enable
switchport trunk native vlan 2
interface fastethernet2
switchport trunk allowed vlan add 2
interface fastethernet3
switchport trunk allowed vlan add 2
interface fastethernet4
switchport trunk allowed vlan add 2
interface fastethernet5
switchport trunk allowed vlan add 2
interface fastethernet6
switchport trunk allowed vlan add 2
interface fastethernet7
switchport trunk allowed vlan add 2
interface fastethernet8
switchport trunk allowed vlan add 2
interface fastethernet9
switchport trunk native vlan 2
interface fastethernet10
switchport trunk native vlan 2
interface fastethernet11
switchport trunk allowed vlan add 2
interface fastethernet12
switchport trunk allowed vlan add 2
interface fastethernet13
switchport trunk allowed vlan add 2
interface fastethernet14
switchport trunk allowed vlan add 2
interface fastethernet15
switchport trunk allowed vlan add 2
interface fastethernet16
switchport trunk allowed vlan add 2
interface fastethernet17
switchport trunk allowed vlan add 2
interface fastethernet18
switchport trunk allowed vlan add 2
interface fastethernet19
switchport trunk allowed vlan add 2
interface fastethernet20
switchport trunk allowed vlan add 2
interface fastethernet21
switchport trunk allowed vlan add 2
interface fastethernet22
switchport trunk native vlan 2
interface fastethernet23
switchport trunk allowed vlan add 2
interface fastethernet24
switchport trunk native vlan 2
ip helper-address all 172.16.0.2 37 42 49 53 137 138
ip route 0.0.0.0 0.0.0.0 172.16.0.150
ip route 10.30.31.0 255.255.255.0 172.16.0.250
Second switch
SW-SRV#show running-config
config-file-header
SW-SRV
v1.2.9.44 / R750_NIK_1_2_584_002
CLI v1.0
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
no cdp run
no spanning-tree
vlan database
vlan 2
exit
voice vlan state disabled
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
ip dhcp relay address 172.16.0.2
ip dhcp relay enable
bonjour interface range vlan 1
hostname SW-SRV
line telnet
password 18c7e97c305303ec56fbb3105666d85721208731 encrypted
exit
line ssh
password 18c7e97c305303ec56fbb3105666d85721208731 encrypted
exit
username cisco password encrypted 18c7e97c305303ec56fbb3105666d85721208731 privilege 15
ip ssh server
snmp-server server
clock timezone " " 0 minutes 0
ip telnet server
interface vlan 1
ip address 172.16.0.248 255.255.0.0
no ip address dhcp
interface vlan 2
name POSTE
ip address 192.168.1.248 255.255.255.0
ip dhcp relay enable
interface fastethernet1
switchport trunk allowed vlan add 2
interface fastethernet2
switchport trunk allowed vlan add 2
interface fastethernet3
switchport trunk allowed vlan add 2
interface fastethernet4
switchport trunk allowed vlan add 2
interface fastethernet5
switchport trunk allowed vlan add 2
interface fastethernet6
switchport trunk allowed vlan add 2
interface fastethernet7
switchport trunk allowed vlan add 2
interface fastethernet8
switchport trunk allowed vlan add 2
interface fastethernet9
switchport trunk allowed vlan add 2
interface fastethernet10
switchport trunk allowed vlan add 2
interface fastethernet11
switchport trunk allowed vlan add 2
interface fastethernet12
switchport trunk allowed vlan add 2
interface fastethernet13
switchport trunk allowed vlan add 2
interface fastethernet14
switchport trunk allowed vlan add 2
interface fastethernet15
switchport trunk allowed vlan add 2
interface fastethernet16
switchport trunk allowed vlan add 2
interface fastethernet17
switchport trunk allowed vlan add 2
interface fastethernet18
switchport trunk allowed vlan add 2
interface fastethernet19
switchport trunk allowed vlan add 2
interface fastethernet20
switchport trunk allowed vlan add 2
interface fastethernet21
switchport trunk allowed vlan add 2
interface fastethernet22
switchport trunk allowed vlan add 2
interface fastethernet23
switchport mode access
switchport access vlan 2
switchport general pvid 2
interface fastethernet24
switchport mode access
switchport access vlan 2
switchport general pvid 2
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route 10.30.31.0 255.255.255.0 172.16.0.250
ip route 10.42.2.0 255.255.255.0 192.168.1.251
Here is what I want to do with these switches:
Uplink between the 2 switches on fa 13 for the first and fa 12 on the second
Behind the fa 23 on the second switch, I have a SDSL line between my company and a datacenter wich is hosting my main software.
Behind the fa 24 on the second switch, I have my Firewall wich hosts the ADSL for Internet and which is translating all addresses of the VLAN 1 to the address 192.168.1.254 in order to communicate with the datacenter via the SDSL.
On the native VLAN 1, I have some PCs, servers, the firewal and WiFi controllers.
On the VLAN 2, I have only PCs.
My final objective is to migrate all of the WiFi controllers and PCs in VLAN 2 and to only have servers in VLAN 1.
VLAN 1 and 2 must communicate between them, so I activated IP routing.
I wonder why I accounter some problems of stability for the connection on the SDSL.
In fact: between 7:30 and 10:00 I have no problems of communication between my LAN and the datacenter, passed 10:00 some problems of communications are appearing.
These problems didn't happened before I changed my old SF200 for the SF300, so I really think the problem is coming from the switches configuration.
I turned off CDP because I had some messages about Native VLAN mismatch on fa23 (SDSL).
I hope someone could give me some clue about what goes wrong.

I'll try an update of the firmware tomorrow.
The duplex mode is set to auto negociation and in fact on the port fa 23 autoset to full.
Yesterday, I set all ports to mode access except for the uplink ones wich still set to trunk and I moved uplink to the gigabits ports.
Before I do the firmware update from v1.2.9.44 to 1.3.0.62, could you tell me how long this update should take, and, by the way, does it need to rebuild the configuration of the switch?
I'll update the post after the firmware update is done.

No longer able to access Web Management after Firmware Update [SF200]

Hello!
Today I was attempting to set up SNMP on our SF200-48 switch. I realized we were running old firmware which does not support SNMP and that the most current version (1.4.0.88) does support it. I attempted to upgrade the firmware but it failed, so I decided to install the 1.1.2.0 firmware because I read that the firmware flash process has changed before 1.4
Unfortunately, after rebooting I was no longer able to access web management on the switch. Unfortunately SF200 switches do not support CLI.
The switch is functional and responds to ping, but I cannot get into management to do anything, is there any steps we can try or will I need to reset the switch? After resetting the switch, will I lose any configuration but still not be able to access management? We do not have any other switches to drop in place of this one, and I'd like to minimize downtime as much as possible.
thanks,
Graham Rounds

Hi Graham,
if you are sure that the ping response is coming from the switch then I guess the only thing you could try is the factory reset but you will loose all the configuration. You might call also Small Business Team and open a ticket so they will proceed with RMA if necessary:
http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
Regards,
Aleksandra

TROUBLE with SF300-24P

Hi
Actually we have the follow diagrame:
When put the SF300-24P on the remote node we have troubles with pass the vlan tag from voice and data on the same port but when put on access port to the vlan voice and data the dispositives have the correct funtion.
someone have something about of this trouble?
the firmeware actually on the switch es 1.2
Best Regards

Hi,
We follow the procedure as You said Us, and now the CP3905 learned the vlan correctly through CDP.
This is the Show Run now:
#sh run
interface gi1
spanning-tree link-type point-to-point
exit
vlan database
vlan 320-322
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
no lldp run
interface fastethernet2
lldp med disable
exit
interface vlan 322
ip address 10.1.208.100 255.255.240.0
exit
ip route 0.0.0.0 0.0.0.0 10.1.208.1
[0mMore: , Quit: q or CTRL+Z, One line:
bonjour interface range vlan 1
hostname switch06e3d7
ip ssh server
no snmp-server server
ip telnet server
interface fastethernet2
macro description "ip_phone_desktop | no_ip_phone_desktop"
exit
interface fastethernet3
macro description "ip_phone_desktop | no_ip_phone_desktop"
exit
interface gigabitethernet1
macro description "switch | no_switch | switch"
exit
interface fastethernet2
no macro auto smartport
switchport trunk allowed vlan add 321
switchport trunk native vlan 320
exit
interface gigabitethernet1
!next command is internal.
macro auto smartport dynamic_type switch
[0mMore: , Quit: q or CTRL+Z, One line:
switchport trunk allowed vlan add 320-322
exit
Thanks for Your support
Best Regards,
AJ

SNMP cpuload SF200-24P

Similar Messages

Maybe you are looking for