Nexus, configure sync and Interface VLAN

We have a pair of Nexus 5548's. Not everything is dual-homed. For example,
only one of them has a 10-gig link to our main office (along with a 100 meg
link elsewhere). I'd like to set up a switch profile between these switches
so I can set up vPC's with our UCS fabric interconnects as well as a pair of
Fex Modules we have.
As it stands, we have SVI's on each switch, with hsrp between them, so the
secondary switch takes over as gateway if the primary fails.
Is it possible (and if so, best practice) after creating a switch profile,
and then going into configure sync mode to create SVI's (eg `interface vlan x`)
so that the SVI's are shared between the two switches, rather than creating
an SVI on each using hsrp in the event one of the switches fails?
Also, again, can we leave some ports out of the dual switch profile, if not
everything is dual-homed?

That is correct. It is that easy. Don't forget that te physical port has to be configured as a layer 2 port (switchport).
You could create sub interfaces under the GigE interface if you were to configure that same physical interface as a layer 3 port (no switchport).
Hope this helps,

Similar Messages

Configure Voice and Data VLAN in CISCO SF 300 8P

I have a couple of Cisco SF 300 8P and 24 P Switches. I have voice and Data VLAN configured as :
Data VLAN : Default 145.17.59.0/24
Voice VLAN : VLAN 20 172.22.20.0/24
I have different DHCP servers as for Data VLAN we have physical server which is configured for 145.17.59.* IP Scope and Voice VLAN DHCP Server is configured in Gateway router with option 150.
This configuation works fine with other cisco swiches like 2960 and 3750 etc except CISCO SF 300 8P and 24P. I was trying to configure both voice and Data VLAN in these CISCO Switches so that CISCO phone (Model 6941) shold get IP from Voice VLAN and PC should get IP from Data VLAN DHCP Server. I have tried several techniques like LLDP, Port to VLAN Config etc.
Can anyone please guide me/help on this.
Regards,
A K.M.Sayeed

Hi A.K.M., with Cisco phones you should be able to simply set auto voice VLAN to be VLAN20.
voice vlan id 20
You should ensure CDP and/or LLDP are enabled as well. I would check this in web GUI. DHCP for the phones can come from the switch, a DHCP server on a VLAN20 access port or you can use dhcp helper to redirect DHCP to server elsewhere.
If you prefer or have issues with CDP or LLDP you can also program ports as trunks and add tagged VLAN 20 to them. In this scenario you need to insure inter-vlan routing is working and that phones download config file with corrrect VLAN config.
These switches do not run ios so they are similar but different than catalyst switches you referred to.
-- please remember to rate helpful posts --

Interface VLAN down

I add VLAN and interface vlan with no shutdown command on MSFC but when i put show ip interface brief comand I have down and down. What cause this problem ??

I guess I should have been more clear in my answer but didn't want to cause confusion.
Now I have not tried this lately on a catos box so it may be different
If a port is down/down it means there is no entry in the vlan database for it. It normally also means that there is no port assigned to that vlan also but you can accomplish this by assigning a port and then deleteing the vlan database. Either way you will get a down/down condition.
Once you add the vlan to the database the interface will go UP/DOWN. This means there is no active access port on the switch and the vlan is not allowed on any trunks that may be up.
Once a vlan becomes active either on a trunk or access port it goes to up/up
Part of the confusion with this is that cisco adds entries to the vlan database automatially when you add access ports to a unkown vlan.
The problems come when someone sees this down/down condition on a switch and checks that they allow all vlans on a active trunk port and it still doesn't work. In this case all you do is add the vlan database entry and it will come up.

Configuring ssid and vlans on autonomous access point ?

here is an a demonstration of how to configure vlans and ssid on a auto-ap , what i dont understand is when i configure the ssid under (interface dot11radio0) and the vlan under that command , why do i need to configure sub-interfaces for the "fastethernet" and the "dot11radio0" if i already configured it under the "interface dot11radio0" , why do i need the "encapsulation dotq x" ? and what is bridge-group ?

If you want to use multiple SSID with multiple vlan, then you have to configure subinterfaces on Radio interfaces (in both Radio 0 & Radio 1 if you want to use both 2.4GHz & 5GHz band) & Ethernet interfaces.
AP simply bridge wireless traffic to wired interface using these sub-interfaces. To specify which radio sub-interface traffic to map to ethernet sub-interface, a Bridge-Group number (1-255) is used.
Bridge-Group 1 always used for native vlan traffic & usually used for AP management.
HTH
Rasika
**** Pls rate all useful responses ****

Configure interface vlan on switch 3524 XL

Hi all,
I have an old switch C3524 running image "C3500XL-c3h2s-mz-120.5.2-xu". I had successfully created vlan 120 but when I config "interface vlan 120" as follows:
swicth # conf t
switch(config-subif)#interface vlan 120
switch(config-subif)#ip address 172.10.10.1 255.255.255.0
switch(config-subif)#no shut
then show run does not see this interface. Show vlan indicates vlan 120 is active.
Please help. thank you.

you're right. I just shut down interface vlan 10 (interface vlan 1 is down already) then interface vlan 120 comes up. Question is: if I need to configure several ports: some in vlan 10 and some in vlan 120 then should I have interface vlan 10 up too ?
Thank you very much.

Outbound and Abstract Sync message Interface difference

Hi Experts,
Is there any difference between the input and output messagetype for Outbound/Inbound Synch Message Interface and Abstract Sync Message Interface.
Do we need to mention the same input and output messagetype for both outbound and Abstract or it should be otherway around?
Regards
Sara

---Is there any difference between the input and output messagetype for Outbound/Inbound Synch Message Interface and Abstract Sync Message Interface.
No there is not. U can select any message type irrespective of the type of message interface.
---Do we need to mention the same input and output messagetype for both outbound and Abstract or it should be otherway around?
Yes. As per ur requirement u can specify the same.
Regards,
Prateek

HT2329 I have a Nexus 7 Tablet and would like to sync my music off of Itunes, knowing I have google product.

I have a Nexus 7 Tablet and would like to sync my music off of itunes, knowing I have a google prodiuct.

iTunes does not support devices other than Apple's own. You'll have to use whatever method for synching provided for your Nexus, getting the tracks directly from the iTunes folder. This presumes that the Nexus supports industry-standard AAC files; if not, you'll have to convert them to a format the Nexus does support.
Regards.

Sync and problem with .mac configuration

Hi
I am having the following problem with Sync Now to my .mac account
Following the initialisation of Sync, the following message appears.
"There was a problem with the sync operation
Could not retrieve .Mac configuration."
And another message says
".Mac login failed."
The syncing to I mac has not functioned since Oct 2nd
Can someone advise how to rectify this problem
G5 Mac OS X (10.4.8)

Can you log into .mac mail? That will tell you if your username and password are OK.
I recently had a similar problem, so I unregistered my work and home computers (using the Advanced tab of .mac preferences) from .mac then re-registered them. At that point, you are offered the initial sync choices like the first time you connected to .mac.
Be careful that you don't overwrite your data. I highly suggest making backups of your Address Book, Safari Bookmarks, iCal, iDisk files, etc. on all computers before starting the process.
- Wayne
PowerMac G5 Mac OS X (10.4.8)

Idoc Configuration and interfaces related to 810

Hi,
Can any one tell me the entire configuration of ALE and EDI810 supported tools?
Thanks
Shobi

<b>Hi,
ALE
To develop a new custom ALE scenario, comprises 5 steps:
1.     Design and develop the custom IDoc with its segments and a new message type
2.     Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
3.     Develop the outbound process which does the following:
     Populates the custom IDoc with control info and functional data
     Sends the IDoc to the ALE layer for distribution
     Updates status and handles errors
4.     Configure the ALE inbound side (partner profiles with inbound process code)
5.     Develop the inbound process which does the following:
     Reads the IDoc into a BDC table; selects other data that is required
     Runs transaction using call transaction or BDC session
     Updates status and handles errors
Below is a pictorial representation of the flow of a complete ALE scenario from the sending system to the receiving system.
Figure 1: ALE Scenario model
1.1.     ALE Example
For the purposes of this example we will develop a small ALE scenario. This scenario is described below.
The receiver of an internal service must be able to reverse (cancel) the invoice receipt which will then cancel the applicable billing document automatically on the service providers system.
Figure 2: Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
     Working ALE environment - See ALE Basis Configuration Guide;
     ALE scenario design together with the business requirement;
     Development access; and
     ALE configuration access.
NOTES:
1.     All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2.     This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3.     Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2.     OUTBOUND PROCESSING
2.1.     Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV     P&S - Segment 1
     Segment fields
          LIFNR     Vendor account number
          XBLNR     Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
     Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
     Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
     Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
     Click on ZINVRV01 and then on the Create icon
     Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
     Enter a description for your segment type and create
     Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
     Save and generate, press back
     To release the segment choose Goto, Release from the menu
     Check the box on the line of your new segment
     Save, back and enter
     Your IDoc type structure should be displayed with your new segment
     Save and back
     To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2.     Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
     Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
     Choose Create logical message type by double clicking on it
     Click on change icon to enter change mode
     Click on New entries to add a new type
     Enter the required message type, in our case it is ZINVRV and an appropriate description
     Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1.     Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
     Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
     Click on change icon to enter change mode
     Click on New entries to create the link
     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
     Save and exit
     Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
     Click on change icon to enter change mode
     Click on New entries to create the link
     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
     Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2.     Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
     Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
     Type in your message type ZINVRV and press enter
     Click on New entries
     Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
     Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3.     Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1.     Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
     Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
     Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
     Choose the receiving systems to which the sending system must forward message type ZINVRV to.
     For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
     Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
     Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2.     Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1.     Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
     Make the settings for the communication with the other decentral systems, you have not set them yet.
     Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
     Create the output partner profile.
     Distribute the customer model
     Specify the name of the customer model.
     You must specify the target system to which you want to distribute the customer model.
     You must repeat this function for every distributed logical system.
2.3.2.2.     Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
     Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
     The customer model must be maintained.
     RFC destinations must be maintained.
     The customer model must be distributed.
     To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4.     Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1.     Example code
The code displayed below does the following:
     populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
     populates the control record info with the message type and IDoc type; and
     calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
*--- Data declaration statements
DATA:          C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
          C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
          C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
          Z1INVRV LIKE Z1INVRV,
          C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
          IDOC_CONTROL LIKE EDIDC,
          T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
          IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*--- Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
*--- Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
*--- Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR.          Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR.          Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME.     Segment name
IDOC_DATA-SDATA = Z1INVRV.               Segment data
APPEND IDOC_DATA.                    Populate IDoc internal table
*--- Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
*--- Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
          EXPORTING
               MASTER_IDOC_CONTROL          = IDOC_CONTROL
          TABLES
               COMMUNICATION_IDOC_CONTROL     = T_COMM_CONTROL
               MASTER_IDOC_DATA               = IDOC_DATA
          EXCEPTIONS
               ERROR_IN_IDOC_CONTROL               = 1
               ERROR_WRITING_IDOC_STATUS          = 2
               ERROR_IN_IDOC_DATA               = 3
               SENDING_LOGICAL_SYSTEM_UNKNOWN      = 4
               OTHERS                         = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3.     INBOUND PROCESSING
3.1.     Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters     Reference field     Opt Y/N
INPUT_METHOD     BDWFAP_PAR-INPUTMETHD     N
MASS_PROCESSING     BDWFAP_PAR-MASS_PROC     N
Export Parameters     Reference field     Opt Y/N
WORKFLOW_RESULT     BDWFAP_PAR-RESULT     N
APPLICATION_VARIABLE     BDWFAP_PAR-APPL_VAR     N
IN_UPDATE_TASK     BDWFAP_PAR-UPDATETASK     N
CALL_TRANSACTION_DONE     BDWFAP_PAR-CALLTRANS     N
Table Parameters     Reference field     Optional Y/N
IDOC_CONTRL     EDIDC
IDOC_DATA          EDIDD
IDOC_STATUS     BDIDOCSTAT
RETURN_VARIABLES     BDWFRETVAR
SERIALIZATION_INFO     BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
     populates a BDC table with the IDoc info;
     calls the transaction via a BDC call; and
     updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
*--- Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
     LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
          CASE IDOC_DATA-SEGNAM.
               WHEN C_SEGNAM.
*                    Here we get the info from the idoc table
                    IT_Z1INVRV = IDOC_DATA-SDATA.
          ENDCASE.
          PERFORM REV_INV.
     ENDLOOP.
     PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV               "Reverse invoice form
*--- Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
*--- Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO   = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
*--- Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR.     "Billing document number
APPEND BDC_TAB.
*--- OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
*--- Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
*--- Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
*--- Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
     CALL FUNCTION 'BDC_OPEN_GROUP'
          EXPORTING
               CLIENT = SY-MANDT
               GROUP = 'ZINVRV'
               USER   = C_ALE_USER
               KEEP   = 'X'.
     CALL FUNCTION 'BDC_INSERT'
          EXPORTING
               TCODE     = C_TCODE
          TABLES
               DYNPROTAB = BDC_TAB.
     CALL FUNCTION 'BDC_CLOSE_GROUP'
          EXCEPTIONS
               NOT_OPEN    = 1
               QUEUE_ERROR = 2
               OTHERS      = 3.
ELSE.                              "No problems
     C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
     SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
    Select from the sales document table to get user status number
          SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
               POSNR = VBRP-AUPOS.
    Select from the status table to change the user status to pending
          SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
               STAT LIKE C_USER_STATUS.
               IF JEST-STAT = C_US_PENDING.   "User status is pending
                    JEST-INACT = C_UNCHECKED.    "Make pending the active status
                    UPDATE JEST.
                    C_EXISTS = 'Y'.            "I.E. An entry is already in table
               ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
                    JEST-INACT = C_CHECKED.      "Make everything else inactive
                    UPDATE JEST.
               ENDIF.
          ENDSELECT.
          IF C_EXISTS = 'N'.    "I.E. Pending has never been a status before
               JEST-OBJNR = VBAP-OBJNR.
               JEST-STAT = C_US_PENDING.
               JEST-INACT = C_UNCHECKED.      "Make pending the active status
               INSERT JEST.
          ENDIF.
     ENDSELECT.       "Select from VBRP (Billing document table)
ENDIF.
ENDFORM.                               " REV_INV
FORM UPDATE_IDOC_STATUS.
*--- Now we check the CALL TRANSACTION return code and set IDOC status
     CLEAR IDOC_STATUS.
     IF RETURN_CODE = 0.
          WORKFLOW_RESULT = '0'.
          IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
          IDOC_STATUS-STATUS = '53'.
          IDOC_STATUS-UNAME = SY-UNAME.
          IDOC_STATUS-REPID = SY-REPID.
          IDOC_STATUS-MSGTY = SY-MSGTY.
          IDOC_STATUS-MSGID = SY-MSGID.
          IDOC_STATUS-MSGNO = SY-MSGNO.
          IDOC_STATUS-MSGV1 = SY-MSGV1.
          IDOC_STATUS-MSGV2 = SY-MSGV2.
          IDOC_STATUS-MSGV3 = SY-MSGV3.
          IDOC_STATUS-MSGV4 = SY-MSGV4.
          RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
          RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
          APPEND RETURN_VARIABLES.
     ELSE.
          WORKFLOW_RESULT = '99999'.
          IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
          IDOC_STATUS-STATUS = '51'.
          IDOC_STATUS-UNAME = SY-UNAME.
          IDOC_STATUS-REPID = SY-REPID.
          IDOC_STATUS-MSGTY = SY-MSGTY.
          IDOC_STATUS-MSGID = SY-MSGID.
          IDOC_STATUS-MSGNO = SY-MSGNO.
          IDOC_STATUS-MSGV1 = SY-MSGV1.
          IDOC_STATUS-MSGV2 = SY-MSGV2.
          IDOC_STATUS-MSGV3 = SY-MSGV3.
          IDOC_STATUS-MSGV4 = SY-MSGV4.
          RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
          RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
          APPEND RETURN_VARIABLES.
     ENDIF.
     APPEND IDOC_STATUS.
ENDFORM.                               " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1.     Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2.     Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1.     Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
     Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
     Select an entry (EG. IDOC_INPUT_ORDERS) and copy
     Type in module name Z_IDOC_INPUT_ZINVRV
     Type in basic IDoc type as ZINVRV01
     Type in message type as ZINVRV
     Type object type as IDOCINVOIC (Invoice document) - Used for workflow
     Direction should be set to 2 for inbound
     Enter and save
3.2.2.     Define FM settings (BD51) Client independent
     Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
     Click on New entries
     Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
     Enter 0 for mass processing in the output column
     Save and Exit
3.2.3.     Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
     Log on to the appropriate receiving system client
     Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
     Choose Inbound with ALE service
     Choose Processing with function module
     Click on Processing with function module and choose create icon
     Click on New Entries
     Type in process code ZINR and give it a description and save
     Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
     Enter your process code ZINR
     Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
     Enter IDPKFIDCMT in object type
     Enter MASSINPUTFINISHED in End event
     Enter IDOCINVOIC in IDoc object type
     Enter INPUTERROROCCURREDFI in IDoc start event
     Enter INPUTFINISHEDFI in IDoc End event
     Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3.     Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1.     Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
     Add the message type ZINVRV with process code ZINR.
     Enter the output mode (background, immediately) for inbound processing and NO message code.
     Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4.     Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.</b>
Foe EDI 810 Mapping Refer <b>http://www.altova.com/videos.asp?type=0&video=edimapping</b>.
Online demo you can see,
Thanks
Manju

Nexus 5548 mgmt 0 interface

I'm new to the Nexus line and I was just wondering do I need to be cautious about connecting the mgmt 0 interface to a production network? As far as spanning-tree or changing the priority of the root bridge? I know bringing on a new switch you always want to be cautious of the configuration, along with what the switch will be used for.
I don't think it would cause a problem, especially if the port is configured for its own VLAN, but I just wanted to be sure.
Cheers,

No, you don't need to worry about spanning-tree on the mgmt0 port. It is just like a host port and it is in its own vrf.
HTH

Nexus 5548 UP and FCoE an brocade

Hi,
I need help.
Architecture :
I have got two Nexus 5548UP .
The nexus are linked to 2 brocade 200e.
Esxi are conrected to Nexus 2248PP, Fcoe and Data >>> interface 101/1/9
Problem:
I try configured Fcoe to Esxi 5.0 but the interface vfc 1 still down.
My configuration :
fex 101
pinning max-links 1
description "FEX101-N2232PP-S12"
fcoe
fex 102
pinning max-links 1
description "FEX102-N2232PP-Sxx"
fcoe
slot 1
port 31-32 type fc
vlan 2900
fcoe vsan 2900
vsan database
vsan 2900
feature npv
interface fc1/31
no shutdown
interface fc1/32
interface Ethernet101/1/9
descri TO-ESXI
switchport mode trunk
vfc1 is down (Error disabled)
    Bound interface is Ethernet101/1/9
    Hardware is Ethernet
    Port WWN is 20:00:54:7f:ee:b6:4b:bf
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port vsan is 2900
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
Help me,
Cdlt,

Hi,
I had same configuration on both N5K.
I have removed the configuration Fcoe on second N5k.
Interface vfc1 seems to be Ok.
But i have another problem, On esxi the Emulex One command plug-in says ethernet's interfaces is up.
But Vcenter sees them down !!
Emulex One command :
In the distibuted Vswitch :
But LLDP seems Ok :

How do I route multiple SB302 switches at different sites and their VLANs?

Hello Cisco Support Community,
First thank you for any replies.
The video posted today on 302's and multiple VLAN's on one switch was nice.
Thank you, I have that working but it's not really what I need.
Though pictures are worth a 1000 words so I hope someone will post something similar to my question.
I have 7 - SB 302-08 switches with the most recent firmware. (updated firmware today, thanks to the video, and TG for the CLI)
All 302's are configured for layer 3.
This is my first experience with the SMB line of switches.
I have a main office and several satellite branch offices.
All locations are connected back with a "Q to Q" circuit on individual ports to a vendor supplied switch at the main office.
I need to link all branch office 302 switches back to the main office 302 switch and allow traffic amongst them.
Mainly traffic between each branch office and the main office.
There maybe a future need to incorporate VoIP on them as well, but that is a back burner issue.
These locations will have an individual VLAN and 302 switch but need to receive data from the main VLAN and possibly others.
I have a "core" SB 302 setup at the main office with its own VLAN.
Each branch switch has its own VLAN.
I would also like to have a centralized management VLAN for the switches.
In trying to configure the core 302 I keep losing connectivity and having to reset it.
On the branch switches I end up getting them to only link to themselves with different IP's and not the core.
I'm assuming this is caused by my not configuring interconnectivity using ACL.
Please let me know if you need additional information.
Thanks

Alllan,
Well first you want to make sure you are running latest firmware 1.1.1.8 I do believe
Next either console into the switch or you can turn on SSH/Telnet under Web gui (Security••àTCP/UDP services and make sure SSH/Telent is enabled)
Now we configure the switch via Cli
We need to enter global configuration mode.
Configure Terminal
(next add our vlans)
Vlan database
Vlan 10
Vlan 20
Vlan 30
Exit
(you can run show command to see your vlans)
do show vlan
(Now configure the port how you would like)
Interface GE1
Switchport mode access (this is making Gigabit port 1 an access port)
Switchport access vlan 20 (this command is changing access port vlan from 1 to 20)
(less configure a trunk port)
Interface GE2
Switchport mode trunk (this makes port 2 for trunking)
(Now less add our Vlans)
Switchport trunk native vlan 1
Switchport trunk allowed vlan add 10,20,30
Exit global configuration
(Use this command to copy your settings to startup)
Copy running-config startup-config
(Some screen shots attached)
I see you have a WRT54G router which i don't think support vlans unless you have 3rd party OS installed.
So currently is the SG300 swtich operating in layer 2 or layer 3 , guessing this is why you choose to move up to 300 series switch?
If the switch is not in layer 3 mode but in layer2 when setting it to layer3 the switch will default all pervious settings.
If the switch is set in layer 3 mode you might have forgot your default route
(Command setting default route)
configure terminal
ip route 0.0.0.0 0.0.0.0 192.168.1.1 (192.168.1.1 being address of your WRT54G)
Now you would need to set up ACL's to deny and allow what traffic you wanted to filter on the SG300
Also reading your post we would need you to call into support center SBSC @ 1-866-606-1866
This way we could get a better idea of your current configuration and assist with fixing or finding a solution for you.
you have 1 year phone support with this product
Thanks,
Jasbryan

Can't configure sync my contacts & calendar on iTunes (10.1.0.56)

The ability to configure Sync my contacts is not avaliable. When I select sync my contacts the configure button does not respond.
As for Sync my calendars - this one I even can't select, the option to select the check box is disabled.
I have iPhone 4 OS 4.2.1
I am using Outlook 2007 on windows XP.
I have re-installed iTunes, I have restored my iPhone, I have configured the iTunes Add in in my outlook, outlook is my default mail account, I basicly did everything that is possible.
Any idea on how to fix that?
Worth mention that previously I had iPhone 3G sync on this laptop, but I have managed to remove all the old backups.
I can sync photos and application but that's all.
Thanks.
Message was edited by: yaelzk

I have resolved this.
For anyone having the issue, here's what appears to be happening based on running iTunes setup with verbose logging turned on and watching the time when the network interface dies.
Issue:
During the installation, iTunes installs some network components related to mobile device support over ethernet(Apple Mobile Device Ethernet Service - netaapl.inf). At the same time, according the logs, the install process removed OEM18.inf. This almost exactly coincided with the time that I saw the network connection die (preceded it by a few seconds).
Basically, iTunes appears to be removing a required network component.
Resolution:
After installing iTunes and the network connection breaking, remove the network device from Device Manager and allow Windows to reinstall it automatically.
The following instructions are for Windows 7, but they are close enough to follow for other versions of Windows.
1. Click the Start button (Jewel in Vista and Win7).
2. Right-click Computer and click Manage in the menu that appears (type your password or click Yes if prompted).
3. On the left side of hte Computer Management window, click Device Manager.
4. Click the arrow (or plus sign) next to Network Adapters to expand that section.
5. Right-click your network adapter and click Uninstall in the menu that appears.
6. Click OK.
7. Reboot.
Windows should automatically detect and reinstall your network device on boot.

CSM-S "Configuration Sync is not supported by this card"

This is the message everytime I try to sync the cards.
NETCSP01#hw-module contentSwitchingModule 5 standby config-sync
Configuration Sync is not supported by this card
NETCSP01#
The are both installed into the same 6513.
Here are the configs
module ContentSwitchingModule 4
ft group 1 vlan 400
priority 30 alt 20
vlan 200 client
description Client Facing CSM Interface
ip address 192.168.100.6 255.255.254.0 alt 192.168.100.7 255.255.254.0
alias 192.168.100.8 255.255.254.0
vlan 100 server
description Server Facing CSM Interface
ip address 172.18.10.6 255.255.254.0 alt 172.18.10.7 255.255.254.0
alias 172.18.10.8 255.255.254.0
module ContentSwitchingModule 5
ft group 1 vlan 400
priority 20 alt 30
I am running the following version
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXE4, RELEASE SOFTWARE (fc2)
What am I missing?
Thank you!!

The configuration synch feature is supported from CSM-S version 2.1.1. I suggest you upgrade your device for using that feature.

Ask the Expert: Cisco Nexus 2000, 5000, and 6000 Series Switches

with Cisco Expert Vinayak Sudame
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions how to configure and troubleshoot the Cisco Nexus 2000, 5000 and 6000 Series Switches with Cisco subject matter expert Vinayak Sudame. You can ask any question on configuration, troubleshooting, features, design and Fiber Channel over Ethernet (FCoE).
Vinayak Sudame is a Technical Lead in Data Center Switching Support Team within Cisco's Technical Services in RTP, North Carolina. His current responsibilities include but are not limited to Troubleshooting Technical support problems and Escalations in the areas of Nexus 5000, Nexus 2000, FCoE. Vinayak is also involved in developing technical content for Cisco Internal as well as external. eg, Nexus 5000 Troubleshooting Guide (CCO), Nexus 5000 portal (partners), etc. This involves cross team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in CAE (Customer Assurance Engineering) bootcamp dealing with Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting MDS platform (Fiber Channel Technologies) and work with EMC support on Escalated MDS cases. Vinayak was the Subject Matter Expert for Santap Technologies before moving to Nexus 5000 support. Vinayak holds a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas. He also holds Cisco Certification CCIE (#20672) in Routing and Switching.
Remember to use the rating system to let Vinayak know if you have received an adequate response.
Vinayak might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community, Other Data Center Topics discussion forum shortly after the event.
This event last through Friday July 12, 2013. Visit the community often to view responses to youe questions of other community members.

Hi Vinayak,
Output of "show cfs internal ethernet-peer database"
Switch 1
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b7:c2:80 [Local]
20:00:54:7f:ee:b6:3f:80 16000005
Total number of entries = 2
Switch 2
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b6:3f:80 [Local]
20:00:54:7f:ee:b7:c2:80 16000005
Total number of entries = 2
Output of "show system internal csm info trace"
Switch 1 in which "show cfs peers" show proper output
Mon Jul 1 05:46:19.145339 (CSM_T) csm_sp_buf_cmd_tbl_expand_range(8604): No range command in buf_cmd_tbl.
Mon Jul 1 05:46:19.145280 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Mon Jul 1 05:46:19.145188 (CSM_T) csm_sp_handle_local_verify_commit(4291):
Mon Jul 1 05:46:19.145131 csm_continue_verify_ac[597]: peer is not reachable over CFS so continuing with local verify/commit
Mon Jul 1 05:46:19.145071 csm_tl_lock(766): Peer information not found for IP address: '172.16.1.54'
Mon Jul 1 05:46:19.145011 csm_tl_lock(737):
Mon Jul 1 05:46:19.144955 (CSM_EV) csm_sp_build_tl_lock_req_n_send(941): sending lock-request for CONF_SYNC_TL_SESSION_TYPE_VERIFY subtype 0 to Peer ip = (172.16.1.54)
Mon Jul 1 05:46:19.143819 (CSM_T) csm_copy_image_and_internal_versions(788): sw_img_ver: 5.2(1)N1(2a), int_rev: 1
Mon Jul 1 05:46:19.143761 (CSM_T) csm_sp_get_peer_sync_rev(329): found the peer with address=172.16.1.54 and sync_rev=78
Mon Jul 1 05:46:19.143699 (CSM_T) csm_sp_get_peer_sync_rev(315):
Mon Jul 1 05:46:19.143641 (CSM_EV) csm_sp_build_tl_lock_req_n_send(838): Entered fn
Mon Jul 1 05:46:19.143582 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Switch 2 in which "show cfs peers" does not show proper output
Mon Jul 1 06:13:11.885354 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 77 seq 482
Mon Jul 1 06:13:11.884992 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 357 seq 369
Mon Jul 1 06:13:11.884932 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 357 seq 368
Mon Jul 1 06:13:11.884872 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 357 seq 367
Mon Jul 1 06:13:11.884811 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 357 seq 366
Mon Jul 1 06:13:11.884750 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 352 seq 365
Mon Jul 1 06:13:11.884690 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 352 seq 364
Mon Jul 1 06:13:11.884630 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 352 seq 363
Mon Jul 1 06:13:11.884568 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 352 seq 362
Mon Jul 1 06:13:11.884207 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733916569.txt
Mon Jul 1 06:13:11.878695 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:13:11.878638 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 06:12:29.527840 (CSM_T) csm_pss_del_seq_tbl(1989): Freeing seq tbl data
Mon Jul 1 06:12:29.513255 (CSM_T) csm_sp_acfg_gen_handler(3106): Done acfg file write
Mon Jul 1 06:12:29.513179 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733911262.txt
Mon Jul 1 06:12:29.508859 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:12:29.508803 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 05:53:17.651236 Collecting peer info
Mon Jul 1 05:53:17.651181 Failed to get the argumentvalue for 'ip-address'
Mon Jul 1 05:40:59.262736 DB Unlocked Successfully
Mon Jul 1 05:40:59.262654 Unlocking DB, Lock Owner Details:Client:1 ID:1
Mon Jul 1 05:40:59.262570 (CSM_T) csm_sp_del_buf_cmd(1713): Deleting comand with Id = 1
Mon Jul 1 05:40:59.262513 DB Lock Successful by Client:1 ID:1
Mon Jul 1 05:40:59.262435 Recieved lock request by Client:1 ID:1
Mon Jul 1 05:40:41.741224 ssnmgr_ssn_handle_create_get: Session FSM already present, ID:1
Mon Jul 1 05:40:41.741167 ssnmgr_handle_mgmt_request: Create/Get request received for session[process_n5kprof]
show cfs lock gives no output.
Just to further clarify, we have 4 5548UP switches in the same management vlan. 2 switches are in one location lets say location A and they are CFS peers and are working fine.
These two switches which are having problem are in location B. All the switches are in the same vlan. Essentially the all CFS multicast messages will be seen by all 5548 switches as they are in the same vlan. I am assuming that this might not create any problems as we specify the peers in the respective configurations. Or do we have to change the CFSoIPv4 multicast addresses in location B or may be configure a different region.
Regards.

Nexus, configure sync and Interface VLAN

Similar Messages

Maybe you are looking for