Cisco SF300-24 IP Configuration Issue

Hi,
I have purchased Cisco SF300-24 few days before. I have created 3nos of new Vlan. I am not able to assign IP to each Vlan.
When ever I aggign the IP to the next vlan, previouly assigned ip is not visible.
need help.

Hello,
Do you have the switch in Layer 2 or Layer 3 mode. In layer 2 mode the switch can have only one IP address. This can either be static or DHCP. The switch must be in layer 3 mode to assign IP addresses to each VLAN. Please see page 258 of the admin guide for how to set IP address for each VLAN. If you need to set to layer 3 please see page 61. Also, please make sure your device is on the latest firmware version 1.3.0.59. If you still have trouble try using a different browser. I tried this using Firefox and experienced a similar issue to what you describe. I switched to IE9 and it worked fine.
If you have completed these steps and are still having difficulties please call the Cisco SBSC at 866-606-1866 between 9am and 6pm your local time for further assistance.
~Mike Vandergrift
SBSC Engineer

Similar Messages

Cisco ASA 8.6 configuration issues

Hello all ,
                                             internet router-----------outside------------- ASA -------inside-------------cisco 3750 (----A----)
                                                                                                        |
                                                                                                        |
                                                                                                     DMZ
                                                                                                         |
                                                                                                         |
                                                                                                         Cisco 3750 (-----B---)
1- switch A -- wireless User + Cisco Wireless Ip phones
2- Switch B -- CUCM
Problem discriptiom :
--- from switch A i can not ping SwitchB (DMZ) so ip phones can not reached to CUCM
--- on switchA 4 VLANS are configured with Different SSIDs and internet is working fine .
--- on Switch A   i want 2 VLANs (vlan60 and vlan 80) to communicate with DMZ also (Not working )
## some relevent Config is as under :
SWITCH A CONFIG
===============
vlan internal allocation policy ascending
          interface FastEthernet0
           no ip address
           no ip route-cache cef
           no ip route-cache
           shutdown
          interface GigabitEthernet1/0/1
           switchport access vlan 60
           switchport mode access
           spanning-tree portfast
|
|
|
|
|
|
          interface GigabitEthernet1/0/23
           description **connected to ASA-Inside**
           switchport access vlan 100
           switchport mode access
interface Vlan10
           ip address X.X.100.5 255.255.255.0
          interface Vlan50
           ip address X.X.6.12 255.255.255.0
          interface Vlan60
           ip address X.X.8.251 255.255.255.0
          interface Vlan80
           ip address X.X.10.251 255.255.255.0
          interface Vlan100
           ip address X.X.20.1 255.255.255.0
          ip classless
          ip route 0.0.0.0 0.0.0.0 X.X.20.2
=========================================
ASA CONFIG
interface GigabitEthernet0/0
nameif inside
security-level 100
ip address X.X.20.2 255.255.255.0
|
|
interface GigabitEthernet0/2
nameif DMZ
security-level 50
ip address X.X.21.2 255.255.255.0
|
|
interface GigabitEthernet0/5
nameif outside
security-level 0
ip address 192.168.2.5 255.255.255.0
|
|
object network IN-OUT
subnet 0.0.0.0 0.0.0.0
object network W-PHONE
subnet X.X.10.0 255.255.255.0
object network BECA-WIRELESS-USER
subnet X.X.8.0 255.255.255.0
pager lines 24
|
|
nat (inside,outside) source dynamic IN-OUT interface
nat (inside,DMZ) source dynamic W-PHONE interface
nat (inside,DMZ) source dynamic BECA-WIRELESS-USER interface
route outside 0.0.0.0 0.0.0.0 192.168.2.1 1
route inside X.X.6.0 255.255.255.0 X.X.20.1 1
route inside X.X.7.0 255.255.255.0 X.X.20.1 1
route inside X.X.8.0 255.255.255.0 X.X.20.1 1
route inside X.X.10.0 255.255.255.0 X.X.20.1 1
timeout xlate 3:00:00
============================================
switch B
interface GigabitEthernet1/0/17
         switchport access vlan 50
         switchport mode access
         switchport voice vlan 20
         spanning-tree portfast
        interface GigabitEthernet1/0/18
         switchport access vlan 50
         switchport mode access
interface Vlan10
         ip address X.X.100.1 255.255.255.0
        interface Vlan20
         ip address X.X.7.1 255.255.255.0
         ip helper-address X.X.6.6
        interface Vlan50
         ip address X.X.6.30 255.255.255.0
         ip helper-address X.X.6.6
        interface Vlan60
         ip address X.X.8.252 255.255.255.0
        interface Vlan101
         ip address X.X.21.1 255.255.255.0
        ip forward-protocol nd
        ip http server
        ip http secure-server
        ip route 0.0.0.0 0.0.0.0 X.X.6.4
        ip route X.X.6.0 255.255.255.0 X.X.21.2
        ip route X.X.7.0 255.255.255.0 X.X.21.2

We would also need to see the ACL configuration of the ASA as this is what actually controls the flow of traffic, that is if routing is correct which it seems to be from your configuration.
What you can do is run a packet-tracer on the ASA to see if the packet is allowed through the ASA:
packet-tracer input inside tcp 12345 detail
This should give you an indication where or if there is a misconfiguration on the ASA.
Please post the output here if you require further assistance. Also a full ASA configuration (remove public IPs and passwords) would help to identify the issue.
Please remember to rate and select a correct answer

Trunking on Cisco SF300 Issue

Hello Friends,
Issue: I have 3 Cisco SF300 multilayer switches, I have configured one switch as a core switch and changed the mode to Router (from layer2 to Layer3) and configured Vlans and DHCP pools accordingly, but when i am trying to connect another SF300 to this switch by using VTP it's giving error then i tried searching a solution and found that it does not support VTP protocol, can someone please help me on that, how i can connect other SF300 to this core switch by using trunking.
My goal is to connect the Switch1 and Switch2 to the CoreSwitch by using trunking so that CoreSwitch can advertise all Vlan information to Switch1 and 2. and PC connected to Switch1 & 2 on different Vlans can communicate to each other.
Network Diagram:
CoreSwitch fast-Ethernet port 1 to 8 are connected to Huwai Router Port 1 to 8 using a dedicated physical enter phase to connect each Vlan to the internet. using Nat overload. CoreSwitch's fastethernet Port 9 to 24 are disabled, gigabit port 1 to 4 are trunk port and allowed vlan are 11, 12,13,14,15,16,17 and 20.
Note: All 3 switches are in Layer3 mode.
CoreSwitch Gigabit ethernet Port1 connected to = Switch1 gigabit ethernet port 1
CoreSwitch Gigabit ethernet Port2 connected to = Switch2 gigabit ethernet port 2
Switch1 Gigabit ethernet Port4 connected to = Switch2 gigabit ethernet port 4
Configuration:
CoreSwitch:
User Name:cisco
Password:XXXXXXX
Welcome to CoreSwitch.
Regards,
Sandy
CoreSwitch#show run
config-file-header
CoreSwitch
v1.3.7.18 / R750_NIK_1_35_647_358
CLI v1.0
set system mode router
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
spanning-tree priority 0
vlan database
vlan 11-17,20
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______________
gvrp enable
ip dhcp excluded-address 192.168.11.1 192.168.11.2
ip dhcp excluded-address 192.168.12.1 192.168.12.2
ip dhcp excluded-address 192.168.13.1 192.168.13.2
ip dhcp excluded-address 192.168.14.1 192.168.14.2
ip dhcp excluded-address 192.168.15.1 192.168.15.2
ip dhcp excluded-address 192.168.16.1 192.168.16.2
ip dhcp excluded-address 192.168.17.1 192.168.17.2
ip dhcp pool network CashOfficedepo
address low 192.168.12.1 high 192.168.12.254 255.255.255.0
default-router 192.168.12.1
dns-server 192.168.20.3 192.168.20.4
exit
ip dhcp pool network Churn5StarPayrollWeb
address low 192.168.11.1 high 192.168.11.254 255.255.255.0
default-router 192.168.11.1
dns-server 192.168.20.3 192.168.20.4
exit
ip dhcp pool network Commission
address low 192.168.13.1 high 192.168.13.254 255.255.255.0
default-router 192.168.13.1
dns-server 192.168.20.3 192.168.20.4
exit
ip dhcp pool network Inventory
address low 192.168.15.1 high 192.168.15.254 255.255.255.0
default-router 192.168.15.1
dns-server 192.168.20.3 192.168.20.4
exit
ip dhcp pool network Managers
address low 192.168.17.1 high 192.168.17.254 255.255.255.0
default-router 192.168.17.1
dns-server 192.168.20.3 192.168.20.4
exit
ip dhcp pool network ReportingAccount
address low 192.168.14.1 high 192.168.14.254 255.255.255.0
default-router 192.168.14.1
dns-server 192.168.20.3 192.168.20.4
exit
ip dhcp pool network TechDept
address low 192.168.16.1 high 192.168.16.254 255.255.255.0
default-router 192.168.16.1
dns-server 192.168.20.3 192.168.20.4
exit
bonjour interface range vlan 1
hostname CoreSwitch
snmp-server location
snmp-server contact
clock timezone " " 0 minutes 0
ip name-server 202.XXX.XXX.XXX
ip telnet server
interface vlan 1
ip address 192.168.10.3 255.255.255.0
no ip address dhcp
interface vlan 11
name Churn5StarPayrollWeb
ip address 192.168.11.1 255.255.255.0
interface vlan 12
name CashOfficedepo
ip address 192.168.12.1 255.255.255.0
interface vlan 13
name Commission
ip address 192.168.13.1 255.255.255.0
interface vlan 14
name ReportingAccount
ip address 192.168.14.1 255.255.255.0
interface vlan 15
name Inventory
ip address 192.168.15.1 255.255.255.0
interface vlan 16
name TechDept
ip address 192.168.16.1 255.255.255.0
interface vlan 17
name Managers
ip address 192.168.17.1 255.255.255.0
interface vlan 20
name SERVERS
ip address 192.168.20.1 255.255.255.0
interface fastethernet1
switchport trunk allowed vlan add 11
interface fastethernet2
switchport trunk allowed vlan add 12
interface fastethernet3
switchport trunk allowed vlan add 13
interface fastethernet4
switchport trunk allowed vlan add 14
interface fastethernet5
switchport trunk allowed vlan add 15
interface fastethernet6
switchport trunk allowed vlan add 16
interface fastethernet7
switchport trunk allowed vlan add 17
interface fastethernet8
switchport trunk allowed vlan add 20
interface fastethernet9
shutdown
interface fastethernet10
shutdown
interface fastethernet11
shutdown
interface fastethernet12
shutdown
interface fastethernet13
shutdown
interface fastethernet14
shutdown
interface fastethernet15
shutdown
interface fastethernet16
shutdown
interface fastethernet17
shutdown
interface fastethernet18
shutdown
interface fastethernet19
shutdown
interface fastethernet20
shutdown
interface fastethernet21
shutdown
interface fastethernet22
shutdown
interface fastethernet23
shutdown
interface fastethernet24
shutdown
interface gigabitethernet1
gvrp enable
switchport trunk allowed vlan add 11-17,20
interface gigabitethernet2
switchport trunk allowed vlan add 11-17,20
interface gigabitethernet3
switchport trunk allowed vlan add 11-17,20
interface gigabitethernet4
switchport trunk allowed vlan add 11-17,20
exit
banner login ^C
Welcome to CoreSwitch.
Regards,
Sandy
^C
banner exec ^C
Welcome to CoreSwitch.
Regards,
Sandy
^C
ip default-gateway 192.168.11.2   (huwai router's fast ethernet port1 ip address)
ip default-gateway 192.168.12.2   (huwai router's fast ethernet port2 ip address)
ip default-gateway 192.168.13.2   (huwai router's fast ethernet port3 ip address)
ip default-gateway 192.168.14.2   (huwai router's fast ethernet port4 ip address)
ip default-gateway 192.168.15.2   (huwai router's fast ethernet port5 ip address)
ip default-gateway 192.168.16.2   (huwai router's fast ethernet port6 ip address)
ip default-gateway 192.168.17.2   (huwai router's fast ethernet port7 ip address)
ip default-gateway 192.168.20.2   (huwai router's fast ethernet port8 ip address)
CoreSwitch#
=====================
Switch1: no configuration yet (Tried configuring VTP but got no luck, it's not supported so i turned on the GVRP...running RSTP and spanning-tree priority is 4096)
=====================
Switch2: no configuration yet.....
Thanks,
Sandy

Please find the below mentioned show vlan output of both the Switches :
CoreSwitch#show vlan
Created by: D-Default, S-Static, G-GVRP, R-Radius Assigned VLAN
Vlan       Name                   Ports               Created by
1           1             fa1-24,gi1-4,Po1-8             D
11 Churn5StarPayroll          fa1,gi1-4                 S
     Web
12   CashOfficedepo            fa2,gi1-4                 S
13     Commission              fa3,gi1-4                 S
14 ReportingAccount           fa4,gi1-4                 S
15      Inventory              fa5,gi1-4                 S
16      TechDept               fa6,gi1-4                 S
17      Managers               fa7,gi1-4                 S
20       SERVERS               fa8,gi1-4                 S
AccessLayer1#show vlan
Vlan       Name                   Ports                Type     Authorization
1           1             fa1-24,gi1-4,Po1-8        Default      Required
AccessLayer1#
I just wondering that i have enabled GVRP on both side and made them trunk then why Switch1 is not showing me the Vlan i created on CoreSwitch :(
Thanks,
Sandy

LAG configuration issue on Cisco SG300 52 Switch

Hi everybody,
I am having an issue with LAG configuration on a Cisco SG300 52 switch. I have connected four Ge ports on the switch to the four NICs of a Dell R710 Server on which I installed Windows Server 2008 R2. Without LAG configured, these ports would forward traffic to and from the Dell server fine. However, if I configure LAG on the ports with LACP enabled, then they would not forward any network traffic. Debugging shows that the ports are up but their forwarding status show N/A. Am I missing any configuration? Can I configure LAG on edgeports? Or is there any compatibility issue?
Any help from you guys will be greatly appreciated.
Thank you.
Vishal

Hi Dave,
Thank you for your quick response and sorry to have looked at it late. Well, I already resolved the issue and like you pointed out, it was the configuration of the Dell NICs. I had to configure NIC teaming and there was a bug with the Broadcom NIC management software. I had to download this piece of software again and I was then able to configure NIC teaming on it. I initially thought that it was already configured because we got the Dell server "pre-installed with pretty much everything".
Anyway thank you for your assistance. Oh I have a question though if you don't mind clearing my doubt. We have bought 7 of these SG300 Switches and I would like to use all of them
in a hierarchical design as core, distribution and access layer switches because I believe this switch has got all the qualities to be used at all the three layers. We have about 100 users in our company at the moment but expecting growth of about 10-20 employees per year. Would you think a hierarchical network design for a 100 users is a bit of an overkill? Would you think these SG300 switches can handle network traffic at the distribution and core layers? I worked out the average daily traffic is only about 4 Mbps.
Thank you for your valuable guidance.
Kind regards,
Vishal
Date: Mon, 12 Sep 2011 08:09:40 -0600
From: [email protected]
To: [email protected]
Subject: - Re: LAG configuration issue on Cisco SG300 52 Switch
Cisco Support Community
Re: LAG configuration issue on Cisco SG300 52 Switch created by David Hornstein in Small Business Switches - View the full discussion
Hi Chundunsing,
Thank you for the purchase of my switch.
Chundunsing, I love the way you worded your question ; "I am having an issue with LAG configuration on a Cisco SG300 52 switch." ,but seriously you are having a problem with interfacing the dell with my switch.
You have LAG working to the Dell R710 teamed NICs and god knows what NICs or drivers you are using to acheive this.
Now LAG is providing , load balancing between the LAG ports.
Now LAG is providing , link redundancy for connectibity to the Dell R710.
If there is a configuration issue , it sure seems the way you have it configured without LACP is still working. But you have the option when you create a LAP group to enable LACP. You can see this as a tick box in the LAG group.
But might i also install, recently firmware version 1.1.1.8, just came out.
Please be sure to;
Step 1. update the firmware on the switch and
Step 2. select it as the 'active image.'
Step 3 rebbot the switch to utilize this active image.
If you are having any trouble doing this the admin guide references how to achieve this. for your concenience I have atteched the guide to this posting.
regards Dave
Reply to this message by going to Cisco Support Community
Start a new discussion in Small Business Switches at Cisco Support Community

VLAN trunking from Cisco Catalyst 3750 to Cisco SF300-48P issue and related

Hello expert,
I'm having difficulties to configure VLAN trunking between Cisco Catalyst 3750 switch with Cisco SF300-48P switch and my workstation unable to get any DHCP IP from our DHCP server via Cisco SF300-48P switch. Below is the snippet of configuration on both switches:
[Cisco Catalyst 3750 Switch]
interface GigabitEthernet1/0/45
description NCC-CC-1stFlr
no switchport trunk encapsulation dot1q
no switchport trunk allowed vlan 101-103
spanning-tree portfast
[Cisco SF300-48P Switch]
interface fastethernet48
spanning-tree link-type point-to-point
switchport trunk allowed vlan add 101-103
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
interface fastethernet29
switchport mode general
switchport general allowed vlan add 103 tagged
switchport general pvid 103
Are these are correct? Kindly advice!
Thank you very much!
Regards,
Alex

Hi Alex,
for the trunk port on Catalyst on port GE 1/0/45, we need to enable the trunk and for on encapsulation dot1q because this catalyst model is ISL capable also and the SF300 working only with Dot1q Encapsultion
The configuration on catalyst should :
#config terminal
#interface Gi 1/0/45
# switchport encapsulation
#switchport trunk encapsulation dot1q
#switchport mode trunk
#switchport trunk allowed vlan 101-103
#spanning-tree portfast
For SF300 the port trunk it looks fine but for the port where the PC should receive an IP address
#interface fastethernet29
#switchport mode access
#switchport ccess vlan 103
Please let me know after this configuration
Thanks
Mehdi
Please rate or mark as answered to help other Cisco Customers

DNS Server does not resolve new generic Top Level Domain names- CNR configuration issue?

Hi all,
I am not sure if this is the correct community to post this question, but I will give it a try. I noticed that the users of my network cannot resolve web sites using new top level domain names, like ".education", ".international", etc. I have an internal DNS server made by Infoblox and a Cisco CNR v6.3.3.1 as an external DNS server. Infoblox uses CNR as its forwarder and CNR uses the root DNS servers for queries.
I would think that CNR was the problem because it is an obsolete product but after speaking with a fellow engineer at another organization where they still use an older version of CNR than mine, they have no problems at all. So now I am thinking it is a setting either on Infoblox, or on CNR I need to change. I can see Infoblox is forwarding the requests to CNR but that's about it. I am not sure if CNR is discarding the request. When I do an nslookup from a PC in my network it does not matter if I set my DNS server to be the Infoblox or the CNR. Neither resolves the URL.
Then again, no matter what I lookup using the CNR as my DNS, I only get a response with the root DNS names and IPs!
Any help is appreciated!

Hi Constantinos,
Have you taken a look at the infoblox community site? We've just reposted your question there and alerted some internal SMEs that should provide a solution soon.
https://community.infoblox.com/forum/ddi/dns-server-does-not-resolve-new-generic-top-level-domain-names-cnr-configuration-issue
Best,
Eric

Cisco 4500X IOS upgrade through ISSU

Hi,
I am having 2 number of cisco 4500x switch and configured with VSS
so one switch is active and another switch is standby.
I am panning to upgrade IOS through ISSU
i read in document that it required auto boot enable in switch.
My switch current Configuration register = 0x2101
do i need to change config register or this will ok. If need to change then what will be auto boot and after IOS upgrade do i need to change it again.
Please help....

Hello Tarun,
Please find below the steps to perform the ISSU:
ISSU Prerequisites
Before one can perform an ISSU, there are a few prerequisites one must verify for a successful ISSU. The following list explains what is initially required.
• Must be using a redundant Cisco Catalyst 4500 switch with symmetric hardware (that is, supervisors, memory, rommon, NFL daughter card, and so on).
• Both new and old Cisco IOS Software images must be preloaded to the file system on both supervisors.
• SSO must be configured and working properly.
• Config register must be configured to autoboot (that is, the value should have a "2" in the lowest byte).
45010R-203# sh bootvar | i register
Configuration register is 0x2102
Standby Configuration register is 0x2102
Several commands are available to verify if SSO is enabled:
4510R-203# sh module | b Redundancy
Mod Redundancy role Operating mode Redundancy status
----+-------------------+-------------------+-------------------
1 Standby Supervisor SSO Standby hot
2 Active Supervisor SSO Active
45010R-203# sh redundancy states
 my state = 13 -ACTIVE
 peer state = 8 -STANDBY HOT
 Mode = Duplex
 Unit = Secondary
 Unit ID = 2
Redundancy Mode (Operational) = Stateful Switchover
Redundancy Mode (Configured) = Stateful Switchover
Redundancy State = Stateful Switchover
 <snip>
4507R-ISSU# sh run | b redundancy
redundancy
mode sso
As a step prior to the beginning of the ISSU process, the new version of the Cisco IOS Software image needs to be loaded into both the active and standby supervisors' file systems. Both active and standby supervisor need to contain both the new and old images in the file system. In order to store both new and old images, the supervisors should be upgraded to contain sufficient amounts of flash memory prior to the ISSU process.
The new images can be downloaded into both supervisors using commands such as:
copy tftp: bootflash:
copy tftp: slavebootflash:
The example below illustrates this verification:
4510R-203#dir
Directory of bootflash:/
1 -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
2 -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
4510R-203#dir slavebootflash:
Directory of slavebootflash:/
1 -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
2 -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
Once this check is verified, one can now proceed with the ISSU process.
The ISSU process is started by typing the "issu loadversion" command on the active supervisor. This command directs the active supervisor to begin the ISSU process. The active supervisor, through intersupervisor communications, checks that the requested image has been downloaded into both the active and standby supervisors' file systems. If the required images are not present, the command is rejected, and an appropriate warning is generated.
If the "issu loadversion" command is successful, the switch transitions into the "Load Version" ISSU state. The standby supervisor will reset and boot with the new version of the Cisco IOS Software image loaded into the file system.
The following actions take place when the command is implemented:
1. The standby supervisor (B) is reset.
2. The standby supervisor (B) is booted with the new Cisco IOS Software image: Release 12.2(31)SGA1.
3. If both Cisco IOS Software images are declared as compatible, the standby supervisor moves into SSO mode and is fully stateful for all compatible clients and applications. Compatibility allows for in-service software upgrade or downgrade between two versions to succeed with minimal service effect.
4. If both Cisco IOS Software images are incompatible, the system moves into RPR mode, and the ISSU process is terminated with an appropriate message to the user. Images are declared incompatible when "required" clients or applications are not interoperable between two Cisco IOS Software releases.
5. Standby "B" reaches the standby HOT state.
6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
7. The "issu loadversion" command also supports a "forced" option that allows the operator to force the system into entering RPR mode when incompatibility is detected.
Note: When performing an ISSU, disable manual switchovers. Performing manual switchovers during the issu process is strongly discouraged. The current implementation does not prevent it, but it does display a warning to the user.
An example of the CLI for implementing the issu loadversion command is displayed below.
On the active supervisor, one would issue the following command:
4510R-203#issu loadversion 1 bootflash:cat4500-entservices-mz.122-31.SGA1 2 slavebootflash: cat4500-entservices-mz.122-31.SGA1
Syntax - issu loadversion active-slot active-image-new standby-slot standby-image-new
The second step of the ISSU process is to perform the issu runversion CLI.
The user can issue the " issu runversion" command when:
1. The ISSU state is "Load Version"; this can be verified with the "show issu state detail" CLI.
2. The standby supervisor is running the new version of the software.
3. The standby supervisor has moved into the "Standby Hot " state.
The following actions take place when the " issu runversion" command is executed:
1. A switchover occurs; that is, the standby (B) becomes the new active, and the old active (A) is rebooted and comes up as a standby.
2. A timer called "Rollback Timer" is started with a previously configured value.
3. Move both supervisors to "Run Version" state.
4. If the command "issu acceptversion" is not issued before the "Rollback timer" fires, then the entire ISSU process is aborted via the automatic rollback.
5. If the active supervisor console connectivity is established and the "issu acceptversion" command is issued, then the rollback timer is stopped.
6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
An example of the CLI for implementing the issu runversion command is displayed below:
On the active supervisor, one would issue the following command:
4510R-203#issu runversion 2 slavebootflash:cat4500-entservices-mz.122-31.SGA1
Syntax - issu runversion standby-slot [standby-image-new]
Prior to issuing the `issu acceptversion' command the system will be counting down the rollback timer. If `issu acceptversion' is not completed before rollback timer expires an automatic abort will occur. This command stops the "Rollback Timer." This command serves as a feedback mechanism. This is an optional command and can be skipped in the ISSU process with the "issu commitversion" CLI.
If this command is not issued within 45 minutes (default) from the time the standby supervisor moves into the "Standby Hot" state, it is assumed that the new active supervisor is not reachable and the entire ISSU process is rolled back to the previous version of the software. The acceptversion is not intended for long-term network operation. It is also important to note that none of the features available on the new version will work yet.
The following actions take place when the command is implemented:
1. The "Rollback Timer" is terminated. This means that the rollback timer is not looked at anymore. Therefore, the system can run in this state for an extended period.
2. The user has an option to abort the ISSU process by issuing the command "issu abortversion."
Aborting the ISSU process now causes the newly active supervisor (B) to fail over to the standby supervisor (A) running the old image and will also cause the rebooting supervisor (B) to load the original image. The issu acceptversion halts the rollback timer and helps ensure the ISSU process is not automatically aborted during the process.
An example of the CLI for implementing the issu acceptversion command is displayed below:
On the "New" active supervisor, one would issue the following command:
4510R-203#issu acceptversion 2
% Rollback timer stopped. Please issue the commitversion command.
Syntax - issu acceptversion active-slot-number
This is the last stage of the ISSU procedure. Once the user is satisfied with the new version of software, this must be committed by issuing the "issu commitversion" command. This command resets the standby supervisor and boots it with a new version of the software (same as the active supervisor). This concludes the ISSU process, and the new version of software is permanently committed on both supervisors. Since this is the conclusion of the ISSU process, the system can not be reverted back to the previous version of the software from this point onward as a part of this upgrade cycle. However, if for any reason users wish to go back to the previous version of the software, they can do so by starting a new upgrade/downgrade process.
The following actions take place if the command is implemented:
1. The standby supervisor (A) is reset and booted with the new version of Cisco IOS Software image.
2. The standby supervisor (A) moves into the "Standby Hot" state in SSO mode and is fully stateful for all clients/applications that are compatible.
3. Both supervisors are moved into "Final State," which is the same as "Initial State."
4. Users can initiate switchovers from this point onward.
An example of the CLI for implementing the issu commitversion command is displayed below:
4510R-203#issu commitversion 1
Syntax - issu commitversion standby-slot-number
ISSU Process: issu abortversion
One can abort the ISSU process at any stage manually (prior to issuing the issu commitversion command) by issuing the exec-level issu abortversion command. The ISSU process also aborts on its own if the software detects a failure.
If a user aborts the process after issuing the issu loadversion command, then the standby supervisor engine is reset and reloaded with the original software.
If the process is aborted after a user enters either the issu runversion or issu acceptversion command, then a second switchover is performed to the new standby supervisor engine that is still running the original software version.
The supervisor engine that had been running the new software is reset and reloaded with the original software version. The command is accepted only in "Load Version" or "Run Version" states. In "Load Version" state, the active supervisor is running an old image and the standby supervisor is running new image.
Syntax - issu abortversion active-slot [active-image-new]
Let me know if you have any questions.

How to setup a static multicast ARP entry with Cisco SF300-08?

We're running a cluster in multicast mode as a loadbalancer.
We have Cisco SF300-08 and when we adding a static ARP entry results in an error message telling the user that the hardware address needs to be a valid unicast MAC address.
So how to setup a static multicast in Cisco SF300 or maybe someone know other solution to setup multicastes mode in Cisco SF300.

Hi, Tom!
We have two watchguard xtm505(cluster active-active) in our network. Watchguard interfaces have one ip and one mac adresses. IP 192.168.111.1(Unicast) and MAC 01:00:5e:02:02:03(multicast). Cisco SF300 is router to outside networks(to internet). Cisco IP adresss is 192.168.111.254. There are another some hosts in this network.
Ping from hosts to 192.168.111.254 works well. Ping from hosts to 192.168.111.1 works well too. But there is no ping from watchguard cluster(192.168.111.1) to Cisco(192.168.111.254). And there is no routing to internet
This is well-known situation. We need to do following(example for cisco 3750):
1. Start the Cisco 3750 command line interface.
2. Add a static ARP entry for the multicast MAC address of the FireCluster interface.
Type this command:
arp arpa
For this example, type:
arp 192.168.111.1 01:00:5e:02:02:03 arpa
3. Add an entry to the MAC address table.
Type this command:
mac-address-table static vlan interface <#>
For this example, type:
mac-address-table static 01:00:5e:02:02:03 vlan 1 interface gi1/0/11
But we can't add arp entry on Cisco SF300. CLI tells us "MAC address illegal"!
We tried enable igmp snooping, but is not helps.
Could you tell more detailed about MAC groups?

Configuration Issue in User Mapping ..

Hi,
Pls help resolve this issue..
When i go to " UserMapping " option using the "Personalize " link , i get the following error msg..
"There is a configuration issue which leads to problem when accessing user mapping data for the selected backend system"
Also , if i go thru "User Administration -> User Mapping "
then it says,
--"There is a configuration issue which leads to problem when accessing user mapping data for the selected backend system .
Usually reason is user mapping being configured for Strong encryption, but necessary additional files might be missing.Check Security log file for information "--
I am not able to solve this problem..Pls help
Thanks in advance

Hi Venkat,
Here the quick and dirty solution:
In your portal go to 'System Administration' -> 'System Configuration' -> 'UM Configuration' -> 'Direct Editing'.
There locate the parameter 'ume.usermapping.unsecure', set it to 'TRUE' and restart your server.
I would rather recommend to install the unlimited strength jurisdiction policy files.
For more info on this, check this thread:
JCE Jurisdiction does not allow Portal to start
Hope this helps,
Robert

Configuration issue of syslog.conf

Dear All,
My client is facing a configuration issue of syslog.conf.
They have set a cacti on a Linux server for monitoring of all servers snmp & syslog.
The part of snmp has set up successfully but cannot send the syslog to the cacti.
My client want the syslog can keep on the localhost and send to cacti for monitoring
we have tried to do the following things for make it work:
Insert the information (*.* @10.251.99.74) in /etc/syslog.conf
Restart service of system-log
Deleted all word of loghost in the /etc/hosts file
But still not work. Anyone can give me suggestion or idea about this?

Thank you for your reply.
It is tab. But I think the problem is solaris cannot use *.* to represent all logs.
I have used the following is work
*.err;ker.debug;daemon.notice;mail.crit @10.251.99.74
If that is not the mail reason, please put me right.

Anti-relay filter configuration issues

Configuration issues with the anti-relay filter in Messaging Server 4.1x.
The following information addresses common questions about configuration issues
with the anti-relay filter in Messaging Server 4.1x: 

<OL>
<LI>Question: 
What is the difference between the delivery
and submission
options? 

Answer: 
The submission option
allows specified users to send email to any email address in the world.
These users are typically internal users.

The delivery option
allows specified users to receive email from anybody. These users
are also typically internal users.

A standard filter will appear something as follows: 

# This is the anti-relay config file written by Jay at iPlanet
# The first section sets default conditions
resolvehostnames:0
useauthinfo:0
advertiseauthinfo:1
# This section sets domains to be delivered to by anybody
delivery:*@my.domain.com
# This section sets domains that can send any place
submission:129.12.4.*


<LI>Question: 
The delivery
option works properly. However, why doesn't the
submission option
appear to be allowing emails from specified users to pass through?

Answer: 
The problem with the submission behavior could be due to the setting of the
the resolvehostnames
parameter. If this parameter is turned on
(resolvehostnames:1),
then all entries in this configuration file must be fully qualified
host names. Although wildcards will work, you cannot specify IP
addresses with this configuration setting.


<LI>Question: 
Is it possible to allow people outside of my network to connect to the server
and send mail out?

Answer: 
Yes. To allow outside users to connect to the server and send mail
to any address, without granting the same privilege to the rest of the world,
activate the authenticated SMTP portion of the filter via the
useauthinfo option.
Setting this parameter to "1" (i.e., useauthinfo:1
) will require a user who is not in a
submission address and who is attempting to send email to an address not in
the delivery range to authenticate with a user ID and password.
</OL>

For additional information on the anti-relay filter, please refer to the
Messaging Server 4.1 Administrator's Guide at 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/ubefiltr.htm#1073677

Prashant:
Are you using a UBE filter to configure domain-based anti-relayinging? We had better luck with the anti-relay plug-in. There is some info on this (for 4.15) at
http://docs.sun.com/source/816-6044-10/ubefiltr.htm#1069973
You have to enable the plug-in using configutil, per the above. The anti-relay plug-in is controlled by antirelay.conf. Be aware that the pattern matching rules are very limited, and not well documented. Fortunately, the source code to the plug-in is included, and you can see what it is doing. To pass the tests we had to add a hard-coded test for a "%" in the source and recompile:
*** antirelay.c.orig Thu Oct 31 04:42:13 2002
--- antirelay.c Thu Oct 31 04:22:07 2002
*** 934,939 ****
--- 934,940 ----
* Weight must be non-zero to begin with so that matches on just "*"
* will work.
+ if( strchr(text,'%') != NULL ) return ABORT;
weight = TRUE;
for ( ; *p; text++, p++) {
if (*text == '\0' && p != '')
Not a really elegant hack, but we didn't need a fully functional regex engine.

Oracle 11g Fusion Middleware (11.1.1.3.0) Report Configuration Issue

Oracle 11g Fusion Middleware (11.1.1.3.0) Report Configuration Issue
=============================================
Hi All,
I have installed Oracle 11g Fusion Middleware (11.1.1.3.0) on Oracle Linux 5 and getting some issues while configuring. What's happening is that when I run my report, it looks for the library attached to it. If I define the REPORTS_PATH in reports.sh, it works fine.
What I want to achieve is to push reports to use REPORTS_PATH environment variable from rwserver.conf instead of reports.sh
Someone told me to remove the REPORTS_PATH from reports.sh and add the REPORTS_PATH from reports.sh to a default.env in rwserver.conf, but it didn't worked.
What I know about the report server stuff in 11g Fusion Middleware is that it consists of two different servers (Standalone and In Process). Our application runs report using SRW.RUN_REPORT which basically use In Process report server setting in rwserver.conf to run the report.
The heirarchy in which reports try to look for the REPORTS_PATH is
1) REPORTS.sh
2) rwserver.conf
3) Settings as per Oracle Enterprise Manager Configuration Settings.
My standalone report server name is ReportsServer_hostname_asinst_F and the In Process Server name is rep_wls_reports_hostname_asinst_frd. When I define rep_wls_reports_hostname_asinst_frd (In process Report Server Name) for the server name parameter, I do not get any results for the report run using srw.run_report. Also I can't see the reason behind the report executed because of the following issue
http://hostname:8888/reports/rwservlet/showjobs?server=rep_wls_reports_hostname_asinst_frd
REP-51019: System user authentication is missing.
** the Singlesignon in rwservlet.properties is defined as no
But when I define ReportsServer_hostname_asinst_F (Standalone Report Server Name) as server parameter and ran the report using srw.run_report, I get result with the REPORTS_PATH defined in reports.sh not using rwserver.conf file.
http://hostname:8888/reports/rwservlet/showjobs?server=ReportsServer_hostname_asinst_F
(which shows the report just run).
Can someone who did Report Server configuration using ENV files (changing rwserver.conf), pls. send me the screenshots. Want to make sure if I am changing the correct files under correct location.
Pls. feel free to ask me questions related to the environment set up.
Thanks

Your question belongs in {forum:id=84}
John

Profit cebter and copany code configuration issue

i am making one sales order in which the item number level when i put profit center GB03100004 earlier i was getting company
code in profit segment as GB03, but now i am getting as GB01.
is this related to any configuration issue, please let me know.

Hi,
Goto the T.Code KE53.
Enter the Controlling area.
Enter the profit centre.
Click on Company Codes.
Check for which company code the field "Assigned" is ticked.
Please check with your FICO consultant for more information and modifications.
Regards,
Krishna.

EM Configuration issue.

I have installed grid agent on different server. When i ran emctl status agent i am getting below error.
EM Configuration issue. /u01/app/oracle/product/10g/hostname.com_ORCL.
OS is AIX
Thanks in advance...

I am in AGENT_HOME.You are under Agent installation that's one thing. You also need to make sure your environment variable ORACLE_HOME point to AGENT_HOME not the database installation.

OC4J Configuration issue

Hi,
I tried to put my database in Archivelog mode through EM , at the time of restarting the database it didnt start... instance is starting but database is not opening....
I tried this command but its giving error... ( I am running 10g r2 , on RHEL 5 which is install on Oracle virtual toolbox )
emctl start dbconsole
OC4J Configuration issue. /opt/oracle/oraclehome_112/db_1/oc4j/j2ee/OC4J_DBConsole_myhostname_orcl not found.
where orcl is the instance name.
and this directory, OC4J_DBConsole_myhostname_orcl, does not exist on the file system.
In some article I read ... the solution I tried to type...
http://kamranagayev.com/2011/03/21/step-by-step-installing-oracle11g-on-linux/
Feedback no. 19
./emca -deconfig dbcontrol db -repos drop
bash : ./emca : No Such file or Directory
./emca -config dbcontrol db -repos create
Thanks and regards...

Hello;
I'm thinking this step was either missed of you have a typo :
Change the entry of .bash_profile file of the oracle user and add following lines:
vi /home/oracle/.bash_profile
export ORACLE_HOME=/u01/home/oracle/product/11.2.0/db_1
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
export PATH=$ORACLE_HOME/bin:$PATHIf your ORACLE_HOME is set it should find the "emca".
You can test by running these export commands at the Linux prompt.
The which command is your friend
which emca
/u01/app/oracle/product/11.2.0.2/bin/emcaBest Regards
mseberg
Edited by: mseberg on Feb 29, 2012 2:52 PM

Cisco SF300-24 IP Configuration Issue

Similar Messages

Maybe you are looking for